Bug#846188: marked as done (python-distro: Missing depends on lsb-release)

[Debian Bug Tracking System]

Your message dated Tue, 06 Dec 2016 07:51:12 +
with message-id <58466df0.90...@p10link.net>
and subject line python-distro: Missing depends on lsb-release
has caused the Debian Bug report #846188,
regarding python-distro: Missing depends on lsb-release
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
846188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-distro
Version: 1.0.1-1
Severity: grave
Justification: renders package unusable

The package popens lsb_release, so it's essentially unusable without
lsb-release.

Scott K
--- End Message ---
--- Begin Message ---

Version: 1.0.1-2

From looking at the changelog and the information on 
packages.debian.org this seems to have been fixed.--- End Message ---

Bug#838778: libatk still causes crashes

[Sebastian Humenda]

Hi

Samuel Thibault schrieb am 05.12.2016,  2:21 +0100:
>Sebastian Humenda, on Fri 02 Dec 2016 18:09:48 +0100, wrote:
>> I've attached a full back trace (pretty long) taken with "thread apply all bt
>> full". I've also attached the hs_err log file.
>
>Thanks for the trace!  I have found the corresponding culprit.  Could you
>try with version -12 which I have just uploaded?
Thanks, that fixes the issue!

Sebastian


signature.asc
Description: PGP signature

Bug#847157: gitlab: CVE-2016-9469

[Pirate Praveen]

control: tags -1 pending

On 2016, ഡിസംബർ 6 11:52:00 AM IST, Salvatore Bonaccorso  
wrote:
>According to upstream all 8.13.0 through 8.13.7 are affected.

Updated in git and people.debian.org/~praveen/gitlab. I'm waiting for current 
version in unstable to migrate before I upload it.

Processed: Re: Bug#847157: gitlab: CVE-2016-9469

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #847157 [src:gitlab] gitlab: CVE-2016-9469
Added tag(s) pending.

-- 
847157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847157: gitlab: CVE-2016-9469

[Salvatore Bonaccorso]

Source: gitlab
Version: 8.13.3+dfsg1-2
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for gitlab.

CVE-2016-9469[0]:
|Denial-of-Service and Data Corruption Vulnerability in Issue and Merge
|Request Trackers

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9469
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9469
[1] https://about.gitlab.com/2016/12/05/cve-2016-9469/

According to upstream all 8.13.0 through 8.13.7 are affected.

Regards,
Salvatore

Bug#844962: marked as done (prometheus-alertmanager: FTBFS: dh_auto_build: go install -v -p 1 -ldflags -X […] returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 6 Dec 2016 06:32:40 +0100
with message-id <96dc224c-3ec1-0eba-d985-53515a81e...@tincho.org>
and subject line already fixed
has caused the Debian Bug report #844962,
regarding prometheus-alertmanager: FTBFS: dh_auto_build: go install -v -p 1 
-ldflags -X […] returned exit code 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
844962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-alertmanager
Version: 0.3.0+ds-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/prometheus-alertmanager-0.3.0+ds'
> dh_auto_build -- -ldflags " -X 
> github.com/prometheus/common/version.Version=0.3.0+ds -X 
> github.com/prometheus/common/version.Revision=0.3.0+ds-2 -X 
> github.com/prometheus/common/version.Branch=debian/sid -X 
> github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
>  -X github.com/prometheus/common/version.BuildDate=20160715-12:56:49 -X 
> github.com/prometheus/common/version.GoVersion=go1.7.3"
>   cd build
>   go install -v -p 1 -ldflags " -X 
> github.com/prometheus/common/version.Version=0.3.0+ds -X 
> github.com/prometheus/common/version.Revision=0.3.0+ds-2 -X 
> github.com/prometheus/common/version.Branch=debian/sid -X 
> github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
>  -X github.com/prometheus/common/version.BuildDate=20160715-12:56:49 -X 
> github.com/prometheus/common/version.GoVersion=go1.7.3" 
> github.com/prometheus/alertmanager github.com/prometheus/alertmanager/config 
> github.com/prometheus/alertmanager/notify 
> github.com/prometheus/alertmanager/provider 
> github.com/prometheus/alertmanager/provider/boltmem 
> github.com/prometheus/alertmanager/provider/sqlite 
> github.com/prometheus/alertmanager/template 
> github.com/prometheus/alertmanager/template/internal/deftmpl 
> github.com/prometheus/alertmanager/test 
> github.com/prometheus/alertmanager/types 
> github.com/prometheus/alertmanager/vendor/github.com/prometheus/client_golang/api/alertmanager
> github.com/prometheus/common/model
> gopkg.in/yaml.v2
> github.com/prometheus/alertmanager/config
> github.com/cenkalti/backoff
> github.com/prometheus/alertmanager/types
> github.com/prometheus/alertmanager/provider
> github.com/prometheus/alertmanager/template
> github.com/beorn7/perks/quantile
> github.com/golang/protobuf/proto
> github.com/prometheus/client_model/go
> github.com/matttproud/golang_protobuf_extensions/pbutil
> github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
> github.com/prometheus/common/expfmt
> github.com/prometheus/procfs
> github.com/prometheus/client_golang/prometheus
> github.com/Sirupsen/logrus
> github.com/prometheus/common/log
> golang.org/x/net/context
> golang.org/x/net/context/ctxhttp
> github.com/prometheus/alertmanager/notify
> github.com/boltdb/bolt
> github.com/prometheus/alertmanager/provider/boltmem
> github.com/julienschmidt/httprouter
> github.com/prometheus/common/route
> github.com/prometheus/common/version
> github.com/prometheus/alertmanager
> # github.com/prometheus/alertmanager
> src/github.com/prometheus/alertmanager/main.go:192: not enough arguments in 
> call to route.New
> github.com/mattn/go-sqlite3
> github.com/prometheus/alertmanager/provider/sqlite
> github.com/prometheus/alertmanager/template/internal/deftmpl
> github.com/prometheus/alertmanager/vendor/github.com/prometheus/client_golang/api/alertmanager
> github.com/prometheus/alertmanager/test
> dh_auto_build: go install -v -p 1 -ldflags  -X 
> github.com/prometheus/common/version.Version=0.3.0+ds -X 
> github.com/prometheus/common/version.Revision=0.3.0+ds-2 -X 
> github.com/prometheus/common/version.Branch=debian/sid -X 
> github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
>  -X github.com/prometheus/common/version.BuildDate=20160715-12:56:49 -X 
> github.com/prometheus/common/version.GoVersion=go1.7.3 
> github.com/prometheus/alertmanager github.com/prometheus/alertmanager/config 
> github.com/prometheus/alertmanager/notify 
> github.com/prometheus/alertmanager/provider 
> github.com/prometheus/alertmanager/provider/boltmem 
> github.com/prometheus/alertmanager/provider/sqlite 
> github.com/prometheus/alertmanager/template 
> github.com/prometh

Bug#844121: CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are *NOT* valid bug reports

[Sam Trenholme]

Thank you for verifying this is not a bug. I would rather have a false
bug report than have a real security issue out there that I’m not
aware of.

I should explain why the MaraDNS code is so messy and hard to follow:

Back in 2001, there was precisely one and only one open-source DNS
server: BIND. This was an issue, so there was a call to arms to have
another open source DNS server out there:
http://old.lwn.net/2001/0208/

That in mind, I quickly wrote up a DNS server; within two months I had
a usable authoritative server, and within a year I had a usable
recursive server. This rapid development came at a cost: The code
worked, was remarkably secure considering how quickly I wrote it, but
it was a mess to maintain. I had planned for years to rewrite MaraDNS,
and five years after the initial recursive server, I started a project
to rewrite the recursive code. My plan was to have a recursive server
within a year; while I had a usable caching server with cleaner code
within six months, it took me three years to make it a fully recursive
server.

My original plan was to rewrite the recursive component, than rewrite
the authoritative component. That never happened, for a number of
reasons, including the fact that DjbDNS became open-source after I
started MaraDNS 2.0’s recursive server, and NSD/Unbound came on to the
scene. With the excellent Knot DNS and Knot Resolver now also carrying
the torch for open source DNS servers, and with my life having a lot
less free time than I did a decade and a half ago when I started
MaraDNS, MaraDNS is in deep freeze maintenance mode.

I still take responsibility for security issues in the code I wrote a
long time ago, since there’s a contingent of users who feel MaraDNS is
more lightweight on “low end boxes” such as virtual machines with only
128 megs of memory (and are willing to give up DNSsec support to have
something that lightweight). But, beyond that, I don’t have time to
even fix things like resolution issues caused because the way DNS
servers handle out-of-bailiwick glue in CNAME records has changed
since 2001. Forget about adding DNSsec to MaraDNS.

Anyway, I do welcome security reports to MaraDNS and do take them very
seriously. There may not be a “packet of death” bug in the MaraDNS
codebase — João Antunes did a pretty through audit of the
authoritative codebase back in 2007 and probably would have found a
“packet of death” back then if there was one.

— Sam

On Mon, Dec 5, 2016 at 5:27 AM, Ondřej Surý  wrote:
> Sam and others,
>
> I most deeply apologize, you are right in your assessment.
>
> I somehow missed the extra four additional sanity checks at the
> beginning of the getudp() function that seems to catch the error
> conditions on those input buffers.
>
> Cheers,
> --
> Ondřej Surý 
> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
> Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
> fast DNS(SEC) resolver
> Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
> pečení chleba všeho druhu
>
> On Sat, Dec 3, 2016, at 16:47, Sam Trenholme wrote:
>> CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are *NOT* valid bug
>> reports.
>>
>> Here’s the deal: The reporter had to patch MaraDNS before he was able
>> to crash her.
>>
>> The patch, however, treats MaraDNS’ special buffer-overflow-resistant
>> “js_string” as if it were an ordinary string — but it’s not. Here’s
>> the offending code patched in to MaraDNS from the reporter’s “bug
>> report”:
>>
>> sock_num = read(0, incoming, 512);
>>
>> As per the man page for read:
>>
>> ssize_t read(int fd, void *buf, size_t count);
>>
>> DESCRIPTION
>>read()  attempts to read up to count bytes from file descriptor fd
>>into
>>the buffer starting at buf.
>>
>> However, incoming is not a raw string buffer: It’s a special js_string
>> object which MaraDNS uses to be buffer overflow resistant, as can be
>> seen here in server/MaraDNS.c:
>>
>> int main(int argc, char **argv) {
>>
>> js_string *mararc_loc = 0, *errors = 0,
>>   *bind_address = 0, *ipv6_bind_address = 0,
>>   *csv2_synthip_address = 0,
>>   *ipv4_bind_address = 0, *incoming = 0,
>>   *uncomp = 0, *verbstr = 0;
>>
>> The js_string structure (I guess I would call it an object here in
>> 2016) is defined in libs/JsStr.h:
>>
>> typedef struct {
>> unsigned char *string;   /* Actual physical string */
>> unsigned int unit_size;  /* The size of a single character in the
>> string */
>> unsigned int unit_count; /* The length of the string, in units */
>> unsigned int max_count;  /* The maximum allowable size of the string,
>>also in units */
>> int encoding;   /* The type of language/encoding the string is in */
>> int is_good;/* This is checked to make sure the data structure is
>>sane */
>> } js_string;
>>
>> Point being, if we patch MaraDNS t

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

[Tianon Gravi]

On 5 December 2016 at 21:01, Tianon Gravi  wrote:
> Now to try and figure out exactly which new conflicts/breaks are
> necessary...  :x

I _think_ adding "golang-doc (<< 2:1.6.1+1~)" to the existing "Breaks"
on "golang-go" might actually be the solution to this issue (since the
"golang-doc" package in jessie provides "/usr/lib/go/doc" as a
symlink, but "golang-go" in sid/stretch changed all of "/usr/lib/go"
to a symlink instead).


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

[Tianon Gravi]

On 20 November 2016 at 18:45, Tianon Gravi  wrote:
> Any thoughts or hrefs on the "correct" way to fix this in the
> packaging?  (Or a simple way to figure out _which_ files don't belong
> so we can evaluate more clearly?)
>
> I don't want to just add "rm -rf" to the preinst, but if piuparts is
> noticing the problem, it's bound to be something we've done wrong in
> the jessie packaging of "golang-go". :(

I've reproduced, and I think this might actually be a case of
insufficient Conflicts/Breaks -- if I first purge golang-*, then the
new packages install fine.

Now to try and figure out exactly which new conflicts/breaks are
necessary...  :x


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#845565: [pkg-gnupg-maint] Bug#845565: anything outside the X session

[Daniel Kahn Gillmor]

interesting, i see you're not using dbus or gnome3 at all, Adam.

On Mon 2016-12-05 22:45:19 -0500, Adam Borowski wrote:
> Curiously, after I logged in via vnc (pinentry did pop up in that session)
> then killed vnc, pinentry on ssh started working again.  I expect this will
> stop once I restart the regular graphic session.

how is gpg-agent being managed?  is it autostarted within your sessions
as needed? 

or, if you've got systemd installed, does it get launched by the systemd
user session?

if it's being autostarted as-needed, then it will inherit the
environment of whichever process happened to start it up first
(e.g. with $DISPLAY if within X11, or without, if only a text-mode
console session or ssh session).  This is a lot of non-determinism,
which can make things difficult to track down.

Please see /usr/share/doc/gnupg-agent/README.Debian for information
about auto-launching the daemon from your systemd user session.

  --dkg


signature.asc
Description: PGP signature

Bug#845565: [pkg-gnupg-maint] Bug#845565: anything outside the X session

[Adam Borowski]

Curiously, after I logged in via vnc (pinentry did pop up in that session)
then killed vnc, pinentry on ssh started working again.  I expect this will
stop once I restart the regular graphic session.


Meow!
-- 
u-boot problems can be solved with the help of your old SCSI manuals, the
parts that deal with goat termination.  You need a black-handled knife, and
an appropriate set of candles (number and color matters).  Or was it a
silver-handled knife?  Crap, need to look that up.

Bug#845565: [pkg-gnupg-maint] Bug#845565: anything outside the X session

[Adam Borowski]

On Mon, Dec 05, 2016 at 08:53:36PM -0500, Daniel Kahn Gillmor wrote:
> On Mon 2016-12-05 18:23:14 -0500, Adam Borowski wrote:
> > Same if you have a running X session but try to sign from the console;
> > killing the gpg-agent doesn't help.
> 
> Please see https://bugs.debian.org/842015 for a very lengthy discussion
> of this issue.  I think this is the same thing, so i'm inclined to merge
> it in with that bug report (and the other three bug reports already
> merged there).
[...]
> So I think the problem you're describing is only happening when:
> 
>  0) pinentry-gnome3 is the default pinentry on the system, and

[~]$ dpkg -l 'pinentry*'
un  pinentry (no description available)
ii  pinentry-curses  0.9.7-9   amd64 curses-based PIN or 
pass-phrase entry
un  pinentry-doc (no description available)
ii  pinentry-gtk20.9.7-9   amd64 GTK+-2-based PIN or 
pass-phrase entry
un  pinentry-x11 (no description available)

>  1) dbus-user-session is installed and configured, and

[~]$ dpkg -l 'dbus*'
ii  dbus 1.10.14-1.0no amd64 simple interprocess messaging 
system 
un  dbus-session-bus (no description available)
ii  dbus-x11 1.10.14-1.0no amd64 simple interprocess messaging 
system 

>  2) the user is logged into the system via ssh, and

Same happens on the text console.
 
On the other hand, logging in graphically again (via vnc) lets me sign
inside that session.

>  3) the user is *also* logged into the graphical console, and

Yeah.

>  4) the graphical console is not screenlocked.

It is locked.


> This is an worrisome way to operate the agent, since it grants access to
> your keys to anyone sitting at the unlocked console

The graphical console is locked, so is my home.


Meow!
-- 
u-boot problems can be solved with the help of your old SCSI manuals, the
parts that deal with goat termination.  You need a black-handled knife, and
an appropriate set of candles (number and color matters).  Or was it a
silver-handled knife?  Crap, need to look that up.

Bug#847152: cubemap: Job for cubemap.service failed because the control process exited with error code

[Jonas Smedegaard]

Package: cubemap
Version: 1.3.1-2
Severity: grave
Justification: renders package unusable

Fails to install the package:

Setting up cubemap (1.3.1-2) ...
Job for cubemap.service failed because the control process exited with error 
code.
See "systemctl status cubemap.service" and "journalctl -xe" for details.
invoke-rc.d: initscript cubemap, action "start" failed.
● cubemap.service - Cubemap stream relay
   Loaded: loaded (/lib/systemd/system/cubemap.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Tue 2016-12-06 04:26:48 CET; 20ms 
ago
  Process: 3304 ExecStart=/usr/bin/cubemap /etc/cubemap.config (code=exited, 
status=217/USER)
 Main PID: 3304 (code=exited, status=217/USER)

Dec 06 04:26:48 auryn systemd[1]: Starting Cubemap stream relay...
Dec 06 04:26:48 auryn systemd[1]: cubemap.service: Main process exited, 
code=exited, status=217/USER
Dec 06 04:26:48 auryn systemd[1]: Failed to start Cubemap stream relay.
Dec 06 04:26:48 auryn systemd[1]: cubemap.service: Unit entered failed state.
Dec 06 04:26:48 auryn systemd[1]: cubemap.service: Failed with result 
'exit-code'.
dpkg: error processing package cubemap (--configure):
 subprocess installed post-installation script returned error exit status 1


 - Jonas


-- System Information:
Debian Release: stretch/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cubemap depends on:
ii  adduser  3.115
ii  init-system-helpers  1.46
ii  libc62.24-8
ii  libgcc1  1:6.2.1-5
ii  libprotobuf103.0.0-9
ii  libstdc++6   6.2.1-5
ii  libsystemd0  232-7
ii  lsb-base 9.20161125

cubemap recommends no packages.

Versions of packages cubemap suggests:
ii  logrotate   3.8.7-2
pn  munin-node  

-- no debconf information

Processed: Re: mergechanges: doesn't know about new .buildinfo files

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #843470 [devscripts] mergechanges: doesn't know about new .buildinfo files
Severity set to 'serious' from 'normal'

-- 
843470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#845565: [pkg-gnupg-maint] Bug#845565: anything outside the X session

[Daniel Kahn Gillmor]

Hi Adam, Julien--

On Mon 2016-12-05 18:23:14 -0500, Adam Borowski wrote:
> Same if you have a running X session but try to sign from the console;
> killing the gpg-agent doesn't help.

Please see https://bugs.debian.org/842015 for a very lengthy discussion
of this issue.  I think this is the same thing, so i'm inclined to merge
it in with that bug report (and the other three bug reports already
merged there).

The issue is:

 a) user has a graphical session
 
 b) gpg-agent is running, and knows it is associated with that session

 c) user connects to the same machine over SSH, and shares part of that
session (e.g. via dbus-user-session), and asks the agent for use of
secret key material.

 d) if the agent already has the passphrase cached, it continues on its
way.  if not, the agent needs to prompt the user, so it asks
pinentry to do that job.

 e) depending on the pinentry installed, pinentry can prompt the user
via one of three different ways, all of which are passed by gpg to
gpg-agent via environment variables:

  * the terminal in use ($GPG_TTY)
  * the X11 display connected to ($DISPLAY)
  * the d-bus session ($DBUS_SESSION_BUS_ADDRESS)

 f) in the event that the prompting is done via d-bus (pinentry-gnome3's
default), the prompt is displayed in the graphical session, because
there is exactly one graphical session in use.


in the scenario where the user only has access to the ssh session,
prompting graphically doesn't help.  however, if the GNOME graphical
session is locked, or the user is not logged in on the graphical
console, then the prompting falls back to the terminal in use.

So I think the problem you're describing is only happening when:

 0) pinentry-gnome3 is the default pinentry on the system, and

 1) dbus-user-session is installed and configured, and

 2) the user is logged into the system via ssh, and

 3) the user is *also* logged into the graphical console, and

 4) the graphical console is not screenlocked.


This is an worrisome way to operate the agent, since it grants access to
your keys to anyone sitting at the unlocked console, but i understand
that it is something that happens in some cases.  Does this describe
your use case, or is there something different?

 --dkg


signature.asc
Description: PGP signature

Bug#838327: marked as done (dune-pdelab: FTBFS in testing (error: cannot convert 'mem_usage_t*' to 'GlobalLU_t*'))

[Debian Bug Tracking System]

Your message dated Tue, 06 Dec 2016 01:48:39 +
with message-id 
and subject line Bug#838327: fixed in dune-pdelab 2.5.0~20161204gdb53a76-1
has caused the Debian Bug report #838327,
regarding dune-pdelab: FTBFS in testing (error: cannot convert 'mem_usage_t*' 
to 'GlobalLU_t*')
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
838327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dune-pdelab
Version: 2.4.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
/usr/bin/dunecontrol autogen
WARNING: could not find module dune-alugrid,
   module is also unknown to pkg-config.
   Maybe you need to adjust PKG_CONFIG_PATH!
   dune-alugrid is suggested by dune-pdelab
Skipping dune-alugrid!
--- going to build dune-pdelab  ---

[... snipped ...]

libtool: link: g++ -std=c++11 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fpermissive -pthread 
-pthread -Wl,-z -Wl,relro -o .libs/testgridfunctionspace 
testgridfunctionspace.o -pthread -Wl,-rpath -Wl,/usr/lib/openmpi/lib 
-Wl,--enable-new-dtags  ../../../lib/.libs/libdunepdelab.so -ldunegrid 
-ldunegeometry -ldunecommon -L/usr/lib/openmpi/lib -lmpi -lugS2 -lugS3 -ldevS 
-lm -pthread
g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../../..  -pthread  -I./ -I./  -I./ -I./  
-I./ -I./  -I./ -I./  -I./ -I./  -I./ -I./ -DENABLE_POSIX_CLOCK -I../../.. 
-DGRIDSDIR="\"./grids\"" -DENABLE_UG   -pthread  -I./ -I./  -I./ -I./  -I./ 
-I./  -I./ -I./  -I./ -I./  -I./ -I./ -DENABLE_POSIX_CLOCK 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include 
-I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi -pthread 
-DMPIPP_H -DENABLE_MPI=1  -I/usr/include/superlu -DENABLE_SUPERLU -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fpermissive -c -o 
testelasticity-testelasticity.o `test -f 'testelasticity.cc' || echo 
'./'`testelasticity.cc
In file included from /usr/include/dune/istl/paamg/amg.hh:13:0,
 from 
../../../dune/pdelab/backend/istl/seqistlsolverbackend.hh:15,
 from ../../../dune/pdelab/backend/istl/istlsolverbackend.hh:6,
 from ../../../dune/pdelab/backend/istl.hh:7,
 from testelasticity.cc:20:
/usr/include/dune/istl/superlu.hh: In static member function 'static void 
Dune::SuperLUSolveChooser::solve(superlu_options_t*, SuperMatrix*, 
int*, int*, int*, char*, double*, double*, SuperMatrix*, SuperMatrix*, void*, 
int, SuperMatrix*, SuperMatrix*, double*, double*, double*, double*, 
mem_usage_t*, SuperLUStat_t*, int*)':
/usr/include/dune/istl/superlu.hh:172:34: error: cannot convert 'mem_usage_t*' 
to 'GlobalLU_t*' for argument '19' to 'void dgssvx(superlu_options_t*, 
SuperMatrix*, int*, int*, int*, char*, double*, double*, SuperMatrix*, 
SuperMatrix*, void*, int, SuperMatrix*, SuperMatrix*, double*, double*, 
double*, double*, GlobalLU_t*, mem_usage_t*, SuperLUStat_t*, int*)'
  memusage, stat, info);
  ^
Makefile:1646: recipe for target 'testelasticity-testelasticity.o' failed
make[7]: *** [testelasticity-testelasticity.o] Error 1
make[7]: Leaving directory '/<>/dune/pdelab/test'
Makefile:2231: recipe for target 'check-am' failed
make[6]: *** [check-am] Error 2
make[6]: Leaving directory '/<>/dune/pdelab/test'
Makefile:1808: recipe for target 'check-recursive' failed
make[5]: *** [check-recursive] Error 1
make[5]: Leaving directory '/<>/dune/pdelab/test'
Makefile:638: recipe for target 'check-recursive' failed
make[4]: *** [check-recursive] Error 1
make[4]: Leaving directory '/<>/dune/pdelab'
Makefile:620: recipe for target 'check-recursive' failed
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory '/<>/dune'
Makefile:798: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
/usr/share/dune/dune-debian

Bug#847146: libeccodes-tools: fails to upgrade from 'testing' - trying to overwrite /usr/bin/bufr_filter

[Andreas Beckmann]

Package: libeccodes-tools
Version: 2.0.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libeccodes-tools.
  Preparing to unpack .../6-libeccodes-tools_2.0.2-2+b1_amd64.deb ...
  Unpacking libeccodes-tools (2.0.2-2+b1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-i5Twn9/6-libeccodes-tools_2.0.2-2+b1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/bufr_filter', which is also in package 
libemos-bin 2:4.4.4-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-i5Twn9/6-libeccodes-tools_2.0.2-2+b1_amd64.deb


cheers,

Andreas


libemos-bin=2%4.4.4-1_libeccodes-tools=2.0.2-2+b1.log.gz
Description: application/gzip

Processed: tagging 843631, tagging 843414, found 845926 in 0.99.2-1, found 846504 in 113.00.00-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 843631 + sid stretch
Bug #843631 {Done: Jonas Smedegaard } [python-openssl] 
Downstream incompatibilities due to SSL_ST_*
Bug #843783 {Done: Jonas Smedegaard } [python-openssl] 
deluge-gtk: fails to start: AttributeError: 'module' object has no attribute 
'SSL_ST_INIT'
Ignoring request to alter tags of bug #843631 to the same tags previously set
Ignoring request to alter tags of bug #843783 to the same tags previously set
> tags 843414 + sid stretch
Bug #843414 {Done: Yaroslav Halchenko } 
[src:statsmodels] statsmodels build-depends on non-existent ipython-notebook 
package
Ignoring request to alter tags of bug #843414 to the same tags previously set
> found 845926 0.99.2-1
Bug #845926 {Done: Andriy Grytsenko } [lxde-common] Cannot 
install package openbox-lxde-session: trying to overwrite 
'/etc/xdg/lxsession/LXDE/autostart', which is also in package lxde-common 
0.99.2-1
Marked as found in versions lxde-common/0.99.2-1.
> found 846504 113.00.00-1
Bug #846504 {Done: Hilko Bengen } [typerep] typerep 
build-depends on obsolete package libbin-prot-camlp4-dev
There is no source info for the package 'typerep' at version '113.00.00-1' with 
architecture ''
Unable to make a source version for version '113.00.00-1'
Marked as found in versions 113.00.00-1.
> found 846961 1.12.1+dfsg-1
Bug #846961 [libjs-jquery-ui] recent update of libjs-jquery-ui broke gitlab
Marked as found in versions jqueryui/1.12.1+dfsg-1.
> found 847082 1.9-4
Bug #847082 {Done: Andreas Tille } [python-cogent] 
python-cogent: FTBFS: Fails to build from source with ncbi-data>=6.1.20160908-1
Marked as found in versions python-cogent/1.9-4.
> notfound 847074 3.0.1
Bug #847074 [postfixadmin] postfixadmin: Files missing in 3.0.1
There is no source info for the package 'postfixadmin' at version '3.0.1' with 
architecture ''
Unable to make a source version for version '3.0.1'
No longer marked as found in versions 3.0.1.
> found 847074 3.0-1
Bug #847074 [postfixadmin] postfixadmin: Files missing in 3.0.1
Marked as found in versions postfixadmin/3.0-1.
> tags 845728 + sid stretch
Bug #845728 [xserver-xorg-video-dummy] undefined symbol: ChangeWindowProperty
Added tag(s) sid and stretch.
> tags 846916 + sid stretch
Bug #846916 [ruby-jquery-rails] provide jquery2: jquery3 breaks diaspora
Added tag(s) stretch and sid.
> tags 837510 + sid stretch
Bug #837510 [src:mozart] mozart: Please replace build dependency on sp with 
opensp
Added tag(s) stretch and sid.
> tags 797547 + jessie
Bug #797547 {Done: Debian FTP Masters } 
[pgsnap] pgsnap seems too old in Jessie
Added tag(s) jessie.
> found 846424 0.5~rc2-4
Bug #846424 [src:fim] fim: add libfl-dev to Build-Depends
Marked as found in versions fim/0.5~rc2-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
797547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797547
837510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837510
843414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843414
843631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843631
843783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843783
845728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845728
845926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845926
846424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846424
846504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846504
846916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846916
846961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846961
847074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847074
847082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#845565: anything outside the X session

[Adam Borowski]

Same if you have a running X session but try to sign from the console;
killing the gpg-agent doesn't help.

-- 
u-boot problems can be solved with the help of your old SCSI manuals, the
parts that deal with goat termination.  You need a black-handled knife, and
an appropriate set of candles (number and color matters).  Or was it a
silver-handled knife?  Crap, need to look that up.

Bug#847145: libopencc2-data: fails to upgrade from 'testing' - trying to overwrite /usr/share/opencc/doc/html/_binary_dict_8hpp_source.html

[Andreas Beckmann]

Package: libopencc2-data
Version: 1.0.4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libopencc2-data.
  Preparing to unpack .../1-libopencc2-data_1.0.4-3_all.deb ...
  Unpacking libopencc2-data (1.0.4-3) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-7aswWT/1-libopencc2-data_1.0.4-3_all.deb (--unpack):
   trying to overwrite 
'/usr/share/opencc/doc/html/_binary_dict_8hpp_source.html', which is also in 
package libopencc-dev:amd64 1.0.4-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-7aswWT/1-libopencc2-data_1.0.4-3_all.deb


cheers,

Andreas


libopencc-dev=1.0.4-1_libopencc2-data=1.0.4-3.log.gz
Description: application/gzip

Bug#847141: marked as done (ruby-json-pure,ruby-json: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 23:48:56 +
with message-id 
and subject line Bug#847141: fixed in ruby-json-pure 2.0.2+dfsg-3
has caused the Debian Bug report #847141,
regarding ruby-json-pure,ruby-json: error when trying to install together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-json-pure,ruby-json
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 2.0.1+dfsg-2
Control: found -1 2.0.2+dfsg-2

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

Selecting previously unselected package ruby-json-pure.
(Reading database ... 18235 files and directories currently installed.)
Preparing to unpack .../ruby-json-pure_2.0.2+dfsg-2_all.deb ...
Unpacking ruby-json-pure (2.0.2+dfsg-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/ruby-json-pure_2.0.2+dfsg-2_all.deb (--unpack):
 trying to overwrite '/usr/lib/ruby/vendor_ruby/json/add/bigdecimal.rb', which 
is also in package ruby-json 2.0.1+dfsg-2
Errors were encountered while processing:
 /var/cache/apt/archives/ruby-json-pure_2.0.2+dfsg-2_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

usr/lib/ruby/vendor_ruby/json.rb
usr/lib/ruby/vendor_ruby/json/add/bigdecimal.rb
usr/lib/ruby/vendor_ruby/json/add/complex.rb
usr/lib/ruby/vendor_ruby/json/add/core.rb
usr/lib/ruby/vendor_ruby/json/add/date.rb
usr/lib/ruby/vendor_ruby/json/add/date_time.rb
usr/lib/ruby/vendor_ruby/json/add/exception.rb
usr/lib/ruby/vendor_ruby/json/add/ostruct.rb
usr/lib/ruby/vendor_ruby/json/add/range.rb
usr/lib/ruby/vendor_ruby/json/add/rational.rb
usr/lib/ruby/vendor_ruby/json/add/regexp.rb
usr/lib/ruby/vendor_ruby/json/add/struct.rb
usr/lib/ruby/vendor_ruby/json/add/symbol.rb
usr/lib/ruby/vendor_ruby/json/add/time.rb
usr/lib/ruby/vendor_ruby/json/common.rb
usr/lib/ruby/vendor_ruby/json/ext.rb
usr/lib/ruby/vendor_ruby/json/generic_object.rb
usr/lib/ruby/vendor_ruby/json/pure.rb
usr/lib/ruby/vendor_ruby/json/pure/generator.rb
usr/lib/ruby/vendor_ruby/json/pure/parser.rb
usr/lib/ruby/vendor_ruby/json/version.rb

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html
--- End Message ---
--- Begin Message ---
Source: ruby-json-pure
Source-Version: 2.0.2+dfsg-3

We believe that the bug you reported is fixed in the latest version of
ruby-json-pure, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 847...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Micah Anderson  (supplier of updated ruby-json-pure package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Dec 2016 18:27:35 -0500
Source: ruby-json-pure
Binary: ruby-json-pure
Architecture: source
Version: 2.0.2+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Micah Anderson 
Desc

Bug#847141: marked as done (ruby-json-pure,ruby-json: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 23:48:51 +
with message-id 
and subject line Bug#847141: fixed in ruby-json 2.0.1+dfsg-3
has caused the Debian Bug report #847141,
regarding ruby-json-pure,ruby-json: error when trying to install together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-json-pure,ruby-json
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 2.0.1+dfsg-2
Control: found -1 2.0.2+dfsg-2

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

Selecting previously unselected package ruby-json-pure.
(Reading database ... 18235 files and directories currently installed.)
Preparing to unpack .../ruby-json-pure_2.0.2+dfsg-2_all.deb ...
Unpacking ruby-json-pure (2.0.2+dfsg-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/ruby-json-pure_2.0.2+dfsg-2_all.deb (--unpack):
 trying to overwrite '/usr/lib/ruby/vendor_ruby/json/add/bigdecimal.rb', which 
is also in package ruby-json 2.0.1+dfsg-2
Errors were encountered while processing:
 /var/cache/apt/archives/ruby-json-pure_2.0.2+dfsg-2_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

usr/lib/ruby/vendor_ruby/json.rb
usr/lib/ruby/vendor_ruby/json/add/bigdecimal.rb
usr/lib/ruby/vendor_ruby/json/add/complex.rb
usr/lib/ruby/vendor_ruby/json/add/core.rb
usr/lib/ruby/vendor_ruby/json/add/date.rb
usr/lib/ruby/vendor_ruby/json/add/date_time.rb
usr/lib/ruby/vendor_ruby/json/add/exception.rb
usr/lib/ruby/vendor_ruby/json/add/ostruct.rb
usr/lib/ruby/vendor_ruby/json/add/range.rb
usr/lib/ruby/vendor_ruby/json/add/rational.rb
usr/lib/ruby/vendor_ruby/json/add/regexp.rb
usr/lib/ruby/vendor_ruby/json/add/struct.rb
usr/lib/ruby/vendor_ruby/json/add/symbol.rb
usr/lib/ruby/vendor_ruby/json/add/time.rb
usr/lib/ruby/vendor_ruby/json/common.rb
usr/lib/ruby/vendor_ruby/json/ext.rb
usr/lib/ruby/vendor_ruby/json/generic_object.rb
usr/lib/ruby/vendor_ruby/json/pure.rb
usr/lib/ruby/vendor_ruby/json/pure/generator.rb
usr/lib/ruby/vendor_ruby/json/pure/parser.rb
usr/lib/ruby/vendor_ruby/json/version.rb

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html
--- End Message ---
--- Begin Message ---
Source: ruby-json
Source-Version: 2.0.1+dfsg-3

We believe that the bug you reported is fixed in the latest version of
ruby-json, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 847...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Micah Anderson  (supplier of updated ruby-json package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Dec 2016 18:33:24 -0500
Source: ruby-json
Binary: ruby-json
Architecture: source
Version: 2.0.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Micah Anderson 
Description:
 ruby-json  - JSON 

Bug#847142: marked as done (libdune-common-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/dune/common/concept.hh)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 23:04:27 +
with message-id 
and subject line Bug#847142: fixed in dune-common 2.5.0~rc2-2
has caused the Debian Bug report #847142,
regarding libdune-common-dev: fails to upgrade from 'sid' - trying to overwrite 
/usr/include/dune/common/concept.hh
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdune-common-dev
Version: 2.5.0~rc1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../3-libdune-common-dev_2.5.0~rc1-3_amd64.deb ...
  Unpacking libdune-common-dev:amd64 (2.5.0~rc1-3) over (2.4.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-6NB7R6/3-libdune-common-dev_2.5.0~rc1-3_amd64.deb 
(--unpack):
   trying to overwrite '/usr/include/dune/common/concept.hh', which is also in 
package libdune-functions-dev 2.4~20160825g0fd5975-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-6NB7R6/3-libdune-common-dev_2.5.0~rc1-3_amd64.deb


cheers,

Andreas


libdune-functions-dev=2.4~20160825g0fd5975-1_libdune-common-dev=2.5.0~rc1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dune-common
Source-Version: 2.5.0~rc2-2

We believe that the bug you reported is fixed in the latest version of
dune-common, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 847...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ansgar Burchardt  (supplier of updated dune-common package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Dec 2016 23:41:24 +0100
Source: dune-common
Binary: libdune-common-dev libdune-common-dbg libdune-common-doc
Architecture: all amd64 source
Version: 2.5.0~rc2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ansgar Burchardt 
Closes: 847142
Description: 
 libdune-common-dbg - toolbox for solving PDEs -- basic classes (debug symbols)
 libdune-common-dev - toolbox for solving PDEs -- basic classes (development 
files)
 libdune-common-doc - toolbox for solving PDEs -- basic classes (documentation)
Changes:
 dune-common (2.5.0~rc2-2) unstable; urgency=medium
 .
   * Add Breaks+Replaces: libdune-functions-dev (<< 2.5.0~)
 (Closes: #847142)
Checksums-Sha1: 
 ad79e3a8d254fa73b1d5639523c9846ed7ee2460 2709 dune-common_2.5.0~rc2-2.dsc
 d5365db5f60f3a1776d5a26d975b9a7f1c79ac18 8628 
dune-common_2.5.0~rc2-2.debian.tar.xz
 b200ec5b08de6ad29ab1a3360cf33e1346340e47 10568 
dune-common_2.5.0~rc2-2_amd64.buildinfo
 b51e3d966f6f3adb8d05695cfabebdb5574ccba3 384250 
libdune-common-dbg_2.5.0~rc2-2_amd64.deb
 c426cfe279d6e0faff4aa15b40831f5c3fae 270822 
libdune-common-dev_2.5.0~rc2-2_amd64.deb
 fd229ff758a15eb2ff6cc12f0e836a51f697e06e 2027320 
libdune-common-doc_2.5.0~rc2-2_all.deb
Checksums-Sha256: 
 cf338e232719a369b8d4bfe13d04227da73326716324681085e045c45fd9ebea 2709 
dune-common_2.5.0~rc2-2.dsc
 e736ff3d44004a44720b2acbadd3d91eff5dc67115528ea118208a502a3d8e2b 8628 
dune-common_2.5.0~rc2-2.debian.tar.xz
 75749f4e4ddd0c39a2f7718d6b2796bc771462fe07b5a360bbfdbb2f29f06f21 10568 
dune-common_2.5.0~rc2-2_amd64.buildinfo
 cefec80ff1dc6270adabb7c296fe18532c59dcca247588fa1f4004dbcafa282f 384250 
libdune-common-dbg_2.5.0~rc2-2_amd64.deb
 0b2ee157e9737c1d5e1fc458c4bc877a8ecf05c73b4daf83a7cd73bedbbb71c4 270822 
libdune-common-dev_2.5.0~rc2-2_amd64.deb
 5fe1fa63b8d49187134024c48f45a843919989c987c765137bb3e51b9e9d0158 2027320 
libdune-common-doc_2.5.0~rc2-2_all.deb
Files: 
 cc449cc68c28794c3711771fa3f5eef1 2709 libs optional du

Bug#846421: marked as done (dicelab: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 23:03:53 +
with message-id 
and subject line Bug#846421: fixed in dicelab 0.7-4
has caused the Debian Bug report #846421,
regarding dicelab: add libfl-dev to Build-Depends
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
846421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dicelab
Severity: important
User: helm...@debian.org
Usertags: libfldep

dicelab will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since dicelab uses parts of libfl-dev (e.g.
libl.a, libfl.a or FlexLexer.h), it should add libfl-dev to its
Build-Depends. This change was previously announced[1] to
debian-devel in accordance with DevRef 7.1.1. Please add the missing
dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: dicelab
Source-Version: 0.7-4

We believe that the bug you reported is fixed in the latest version of
dicelab, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 846...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert Lemmen  (supplier of updated dicelab package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Dec 2016 21:58:27 +
Source: dicelab
Binary: dicelab
Architecture: source amd64
Version: 0.7-4
Distribution: unstable
Urgency: medium
Maintainer: Robert Lemmen 
Changed-By: Robert Lemmen 
Description:
 dicelab- evaluate the statistical distribution of dice rolls
Closes: 846421
Changes:
 dicelab (0.7-4) unstable; urgency=medium
 .
   * Add build-dep to libfl-dev (closes: #846421)
Checksums-Sha1:
 52f4ef49fa58660ac1e24e3e2606bdfd33f2e7d4 1646 dicelab_0.7-4.dsc
 5c9d078949ce5966d6319b62ad655fcbe4335861 3679 dicelab_0.7-4.diff.gz
 a02376ae6ddbf3d09fcff24dc2efcd81e0ec30a1 69356 dicelab-dbgsym_0.7-4_amd64.deb
 b6a10add63e3f5a5ba67a7b19f99f392643453f6 8024 dicelab_0.7-4_amd64.buildinfo
 2574923357dd1a269a43bcc1fdc8f5e4c0550be9 224112 dicelab_0.7-4_amd64.deb
Checksums-Sha256:
 5b3a4a4b71206d47780c9446462e01ebeb3e1693a03167af562e0beda02e13e9 1646 
dicelab_0.7-4.dsc
 334b293ef405b32a9f199b0f5b000acddbc3d7494a59327f1edd435e1bc8ce05 3679 
dicelab_0.7-4.diff.gz
 65229fce1dcffcf899babf95457392d6e6ff383e78f24613243cf575043d5af5 69356 
dicelab-dbgsym_0.7-4_amd64.deb
 8ed6deeab73aa02460956cd3e7ae7c13eeebc69e4e2d05eeb782b0385a6f431b 8024 
dicelab_0.7-4_amd64.buildinfo
 2f6bdb3c75e42adae12802278b049ffb02efeea85656b36202852c27019e 224112 
dicelab_0.7-4_amd64.deb
Files:
 9ff22e24d2987b9c03307438afbf4d8c 1646 math extra dicelab_0.7-4.dsc
 4ddbb4fd51576629dec60370db83450b 3679 math extra dicelab_0.7-4.diff.gz
 be37ed9d2d1fd52f4326e063de976d0a 69356 debug extra 
dicelab-dbgsym_0.7-4_amd64.deb
 7bddb060f69322e9ba04a568f4233e25 8024 math extra dicelab_0.7-4_amd64.buildinfo
 a814614a014ee75c02e8c33233384c73 224112 math extra dicelab_0.7-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQI1BAEBCAAfBQJYRe0uGBxyb2JlcnRsZUBzZW1pc3RhYmxlLmNvbQAKCRCG9fuH
kXdhFTQED/9SyAiW2W30S1nJYmLeTTINdMbI0RPh4v7XXcPt2aRGQUFeWxB0SCUp
3PG5Qp0lybtXqXUNLKw8CZOGmcWYHx5hiSTnRgtcsIqYZYk+f7pbQIwKDEUuc4+d
Ayq/Ca3u5e3nVH95OOg44YkCtZUPXpgNa+ZwDOOxVH8SeaApLnbJWgSDGkPHa1jP
1lnzclP4+4Uz7WMtEoyKY1cVDUNj5jvPcIajwHMpcZfHEYG7VBN3edR4LN5J3wF/
ao3Xk9Y9TtbqMN+iuUGhi0/oVBO2MOiRH1L56/AUKoCl1MS2ZJ+qXZD2qdDLtwEW
fLwBIdD7Fl/OOJQ4wbQCwp22zRgUvUIKTad2h41zu89ZelBTDtnAeC1noPfLh9Kg
ZaOaEcwCtKaNSfVxT/1wbBxotF4TONgACOrgou910+BSIGX4IfEp127DskeF85sy
w4dN5C6yizwBE1/b+Aug200TlKaxZ7MZscBkhlACfuTbNzeCsLXER5Q1HM2VEyiV
4/mnMvLXuntu8Uh60/0NweseLUKugJP6nGkuvZL8V38EKpweQFa8uS+QoxVExMA6
e+76RpR/YDk4Ap4JnPeY0keT6BQTc27iCQRhuYVpSphLoEa+3ebAv5v/s4XDIiE9
sUzK9T+FdZpumiTDd9spwI9VzUWGjKdjF+S9Yp8lUK5ZJG9DGHWGWA==
=pBY+
-END PGP SIGNATURE End Message ---

Bug#847143: speech-dispatcher-*: missing Breaks+Replaces for package split

[Andreas Beckmann]

Package: 
speech-dispatcher-cicero,speech-dispatcher-espeak-ng,speech-dispatcher-espeak,speech-dispatcher-flite
Version: 0.8.5-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package speech-dispatcher-cicero.
  Preparing to unpack .../1-speech-dispatcher-cicero_0.8.5-5_amd64.deb ...
  Unpacking speech-dispatcher-cicero (0.8.5-5) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-BPRrOo/1-speech-dispatcher-cicero_0.8.5-5_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/speech-dispatcher-modules/sd_cicero', which is 
also in package speech-dispatcher 0.8.5-4
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-BPRrOo/1-speech-dispatcher-cicero_0.8.5-5_amd64.deb


cheers,

Andreas

Bug#847142: libdune-common-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/dune/common/concept.hh

[Andreas Beckmann]

Package: libdune-common-dev
Version: 2.5.0~rc1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../3-libdune-common-dev_2.5.0~rc1-3_amd64.deb ...
  Unpacking libdune-common-dev:amd64 (2.5.0~rc1-3) over (2.4.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-6NB7R6/3-libdune-common-dev_2.5.0~rc1-3_amd64.deb 
(--unpack):
   trying to overwrite '/usr/include/dune/common/concept.hh', which is also in 
package libdune-functions-dev 2.4~20160825g0fd5975-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-6NB7R6/3-libdune-common-dev_2.5.0~rc1-3_amd64.deb


cheers,

Andreas


libdune-functions-dev=2.4~20160825g0fd5975-1_libdune-common-dev=2.5.0~rc1-3.log.gz
Description: application/gzip

Processed: ruby-json-pure,ruby-json: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.0.1+dfsg-2
Bug #847141 [ruby-json-pure,ruby-json] ruby-json-pure,ruby-json: error when 
trying to install together
There is no source info for the package 'ruby-json-pure' at version 
'2.0.1+dfsg-2' with architecture ''
Marked as found in versions ruby-json/2.0.1+dfsg-2.
> found -1 2.0.2+dfsg-2
Bug #847141 [ruby-json-pure,ruby-json] ruby-json-pure,ruby-json: error when 
trying to install together
There is no source info for the package 'ruby-json' at version '2.0.2+dfsg-2' 
with architecture ''
Marked as found in versions ruby-json-pure/2.0.2+dfsg-2.

-- 
847141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847141: ruby-json-pure,ruby-json: error when trying to install together

[Andreas Beckmann]

Package: ruby-json-pure,ruby-json
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 2.0.1+dfsg-2
Control: found -1 2.0.2+dfsg-2

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

Selecting previously unselected package ruby-json-pure.
(Reading database ... 18235 files and directories currently installed.)
Preparing to unpack .../ruby-json-pure_2.0.2+dfsg-2_all.deb ...
Unpacking ruby-json-pure (2.0.2+dfsg-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/ruby-json-pure_2.0.2+dfsg-2_all.deb (--unpack):
 trying to overwrite '/usr/lib/ruby/vendor_ruby/json/add/bigdecimal.rb', which 
is also in package ruby-json 2.0.1+dfsg-2
Errors were encountered while processing:
 /var/cache/apt/archives/ruby-json-pure_2.0.2+dfsg-2_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

usr/lib/ruby/vendor_ruby/json.rb
usr/lib/ruby/vendor_ruby/json/add/bigdecimal.rb
usr/lib/ruby/vendor_ruby/json/add/complex.rb
usr/lib/ruby/vendor_ruby/json/add/core.rb
usr/lib/ruby/vendor_ruby/json/add/date.rb
usr/lib/ruby/vendor_ruby/json/add/date_time.rb
usr/lib/ruby/vendor_ruby/json/add/exception.rb
usr/lib/ruby/vendor_ruby/json/add/ostruct.rb
usr/lib/ruby/vendor_ruby/json/add/range.rb
usr/lib/ruby/vendor_ruby/json/add/rational.rb
usr/lib/ruby/vendor_ruby/json/add/regexp.rb
usr/lib/ruby/vendor_ruby/json/add/struct.rb
usr/lib/ruby/vendor_ruby/json/add/symbol.rb
usr/lib/ruby/vendor_ruby/json/add/time.rb
usr/lib/ruby/vendor_ruby/json/common.rb
usr/lib/ruby/vendor_ruby/json/ext.rb
usr/lib/ruby/vendor_ruby/json/generic_object.rb
usr/lib/ruby/vendor_ruby/json/pure.rb
usr/lib/ruby/vendor_ruby/json/pure/generator.rb
usr/lib/ruby/vendor_ruby/json/pure/parser.rb
usr/lib/ruby/vendor_ruby/json/version.rb

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html

Bug#847139: tcsh: /usr/bin/tcsh no longer in package

[Michael Stone]

Package: tcsh
Version: 6.20.00-1
Severity: critical
Justification: breaks unrelated software

/usr/bin/tcsh is no longer being provided by the tcsh package. This prevents
logins from users with a shell of /usr/bin/tcsh, and breaks active sessions in
various ways (when software attempts to use $SHELL).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tcsh depends on:
ii  libc6  2.24-7
ii  libtinfo5  6.0+20161126-1

tcsh recommends no packages.

tcsh suggests no packages.

-- no debconf information

Bug#828564: sx: FTBFS with openssl 1.1.0

[Török Edwin]

On 2016-12-05 23:36, László Böszörményi (GCS) wrote:
> Hi Sebastian,
> 
> On Mon, Dec 5, 2016 at 10:20 PM, Sebastian Andrzej Siewior
>  wrote:
>> On 2016-10-09 11:38:37 [+0300], Török Edwin wrote:
>>> Patches to build with both OpenSSL 1.0.x, and 1.1.0 are available in the 
>>> upstream git repository:
>>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=5acd940e97aa1f2bd1b3fdd41f4c98a5783fcb44
>>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=0dcacbab63325a83668d000dc8ed7da3bf0e4f7d
>>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=86e06686a5fe10fd823dff805f8439a791290c5b
>>>
>>> They apply on top of SX 2.2.
>>
>> Okay. What do we do here? Any idea Laszlo?
>> I could try to cherry-pick the three patches into the currect 2.0 but I
>> can't look at them because the git server seems to be down at the moment.
>  I'm a bit confused to be honest. Upstream has a note that SX support
> (or the entire SX) is closed down.
> Edwin, does it mean that SX is no longer developed?

SX is no longer supported commercially, but it would be nice if the last 
version (2.3) would be available in Debian (it is open-source after all)

> 
>> Upstream asked about packaging 2.3 which makes sense (I think) but there
>> is something regarding the update path If I read this correctly. And 2.3
>> works with openssl 1.1 but needs to go via NEW due to libsxclient4 and I
>> hope this "transition" is okay because libsxclient3 has no rdeps.
>  I've packaged SX 2.3 and it looks fine - the upgrade path needs
> testing. I had a plan to do it in a virtual machine (don't want to
> hurt my real data), but then I didn't have time. Now I'm on holidays
> for three days - I may need to go home sooner, but I can share the
> packaging then.

Sounds good, thanks!

Bug#828564: sx: FTBFS with openssl 1.1.0

[Török Edwin]

On 2016-12-05 23:20, Sebastian Andrzej Siewior wrote:
> On 2016-10-09 11:38:37 [+0300], Török Edwin wrote:
>> Dear Maintainer,
>>
>> Patches to build with both OpenSSL 1.0.x, and 1.1.0 are available in the 
>> upstream git repository:
>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=5acd940e97aa1f2bd1b3fdd41f4c98a5783fcb44
>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=0dcacbab63325a83668d000dc8ed7da3bf0e4f7d
>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=86e06686a5fe10fd823dff805f8439a791290c5b
>>
>> They apply on top of SX 2.2.
> 
> Okay. What do we do here? Any idea Laszlo?
> I could try to cherry-pick the three patches into the currect 2.0 but I
> can't look at them because the git server seems to be down at the moment.

Sorry about that, here is a mirror (of the git repo, and those patches in 
particular):
https://github.com/enospc/sx/commit/5acd940e97aa1f2bd1b3fdd41f4c98a5783fcb44
https://github.com/enospc/sx/commit/0dcacbab63325a83668d000dc8ed7da3bf0e4f7d
https://github.com/enospc/sx/commit/86e06686a5fe10fd823dff805f8439a791290c5b

Bug#828564: sx: FTBFS with openssl 1.1.0

[GCS]

Hi Sebastian,

On Mon, Dec 5, 2016 at 10:20 PM, Sebastian Andrzej Siewior
 wrote:
> On 2016-10-09 11:38:37 [+0300], Török Edwin wrote:
>> Patches to build with both OpenSSL 1.0.x, and 1.1.0 are available in the 
>> upstream git repository:
>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=5acd940e97aa1f2bd1b3fdd41f4c98a5783fcb44
>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=0dcacbab63325a83668d000dc8ed7da3bf0e4f7d
>> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=86e06686a5fe10fd823dff805f8439a791290c5b
>>
>> They apply on top of SX 2.2.
>
> Okay. What do we do here? Any idea Laszlo?
> I could try to cherry-pick the three patches into the currect 2.0 but I
> can't look at them because the git server seems to be down at the moment.
 I'm a bit confused to be honest. Upstream has a note that SX support
(or the entire SX) is closed down.
Edwin, does it mean that SX is no longer developed?

> Upstream asked about packaging 2.3 which makes sense (I think) but there
> is something regarding the update path If I read this correctly. And 2.3
> works with openssl 1.1 but needs to go via NEW due to libsxclient4 and I
> hope this "transition" is okay because libsxclient3 has no rdeps.
 I've packaged SX 2.3 and it looks fine - the upgrade path needs
testing. I had a plan to do it in a virtual machine (don't want to
hurt my real data), but then I didn't have time. Now I'm on holidays
for three days - I may need to go home sooner, but I can share the
packaging then.

Regards,
Laszlo/GCS

Bug#846675: [pkg-gnupg-maint] Bug#846675: zeroinstall-injector: FTBFS: Test failures

[Daniel Kahn Gillmor]

Hi Thomas--

On Sat 2016-12-03 10:33:11 -0500, Thomas Leonard wrote:
> I can reproduce this on sid. It appears that GnuPG has started
> reporting incorrect error values. I have reported it here:
>
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846834
>
> If that doesn't get fixed soon, I could work around it by masking off
> the top bits of the error code.

I plan on uploading fixes to GnuPG in sid in the next few day or two
that should address this.

thanks for the heads-up!

 --dkg


signature.asc
Description: PGP signature

Bug#846708: FastQC should adapt to new htsjdk API which has dropped SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))

[olivier sallou]

Le lun. 5 déc. 2016 à 17:00, Andreas Tille  a écrit :

> Hi folks,
>
> does anybody feel able to rather patch FactQC than reintroducing the
> outdated API to htsjdk?


I have some work on biojava which requires quite a lot of patch updates for
the moment, but after this I can try to have a look



Olivier


>   Same is valid for Artemis.  I admit while
> reintroducing the old API works I'd consider this only the second best
> solution for the problem.
>
> Kind regards
>
>  Andreas.
>
> On Mon, Dec 05, 2016 at 02:47:16PM +, Simon Andrews wrote:
> > Hi Andreas,
> >
> > None of the official FastQC releases has ever used htsjdk - we've been
> using the older picard sam.jar API which is substantially different (htsjdk
> is a major rewrite and restructure - it's not just a version update).
> Internally we have tried the new API, and although it works OK it also
> imposes a restriction on the use of java >=8 which wasn't present in the
> old version and which would break a lot of our existing installations.
> We're therefore not keen to make that change yet - especially since the old
> API works just fine for all the types of data we support.
> >
> > If you're packaging this for Debian and wanted to move to htkjdk then
> it's pretty trivial to patch this.  It takes a small boilerplate change to
> the BAM opening and reading code in the BAMFile class, and a change to the
> classpath in the launcher script (which I guess you're already doing).
> We'll probably move to the new API eventually, but at the moment the
> downsides outweigh the benefits for us.
> >
> > Cheers
> >
> > Simon.
> >
> >
> >
> >
> > -Original Message-
> > From: Andreas Tille [mailto:ti...@debian.org]
> > Sent: 05 December 2016 14:34
> > To: Simon Andrews ; 846...@bugs.debian.org
> > Cc: Vincent Danjean ; Olivier Sallou <
> osal...@debian.org>; Charles Plessy 
> > Subject: FastQC should adapt to new htsjdk API which has dropped
> SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version
> 2.7.0 (#767))
> >
> > Hi Simon,
> >
> > after uploading htsjdk 2.7.0 FastQC failed to build from source[1].  I
> relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
> > was removed from htsjdk source and assumed that this was by accident.
> > However, upstream has dropped this interface intentionally as you can
> read below.  In issue #767[2] an htsjdk author gives advise to use the new
> API version.
> >
> > Kind regards
> >
> >Andreas.
> >
> >
> > [1] https://bugs.debian.org/846708
> > [2] https://github.com/samtools/htsjdk/issues/767
> >
> >
> > - Forwarded message from Daniel Gómez-Sánchez <
> notificati...@github.com> -
> >
> > Date: Mon, 05 Dec 2016 06:18:16 -0800
> > From: Daniel Gómez-Sánchez 
> > To: samtools/htsjdk 
> > Cc: Andreas Tille , Author 
> > Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0
> (#767)
> >
> > The file was removed in #699 because it was deprecated. I guess that
> either 1) fastqc/artemis should be updated to use the new API version, or
> 2) the classpath for them in Debian should include an older version.
> >
> > --
> > You are receiving this because you authored the thread.
> > Reply to this email directly or view it on GitHub:
> > https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910
> >
> > - End forwarded message -
> >
> > --
> > http://fam-tille.de
> > The Babraham Institute, Babraham Research Campus, Cambridge CB22 3AT
> Registered Charity No. 1053902.
> > The information transmitted in this email is directed only to the
> addressee. If you received this in error, please contact the sender and
> delete this email from your system. The contents of this e-mail are the
> views of the sender and do not necessarily represent the views of the
> Babraham Institute. Full conditions at: www.babraham.ac.uk<
> http://www.babraham.ac.uk/terms>
> >
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@lists.alioth.debian.org
> >
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> >
>
> --
> http://fam-tille.de
>

Bug#847133: pion FTBFS on arm64: piontests fails

[Adrian Bunk]

Source: pion
Version: 5.0.7+dfsg-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=pion&arch=arm64&ver=5.0.7+dfsg-2&stamp=1480916471

...
make[5]: Entering directory '/«BUILDDIR»/pion-5.0.7+dfsg/tests'
FAIL: piontests
==
   pion 5.0.7: tests/test-suite.log
==

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: piontests
===

global setup for all pion unit tests
Use '-v' to enable logging of errors and warnings from pion.
Running 292 test cases...
unknown location(0): fatal error: in 
"tcp_stream_tests_S/checkTCPConnectToAnotherStream": memory access violation at 
address: 0x: no mapping at fault address
tcp_stream_tests.cpp(67): last checkpoint
global teardown for all pion unit tests
...

Bug#847010: marked as done (zeroc-ice FTBFS: unable to load addon javahelper)

[Debian Bug Tracking System]

Your message dated Mon, 5 Dec 2016 22:19:28 +0100
with message-id 

and subject line Re: Bug#847010: zeroc-ice FTBFS: unable to load addon 
javahelper
has caused the Debian Bug report #847010,
regarding zeroc-ice FTBFS: unable to load addon javahelper
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeroc-ice
Version: 3.6.3-3
Severity: serious

https://buildd.debian.org/status/package.php?p=zeroc-ice

zeroc-ice FTBFS on all architectures:

...
dh clean --parallel --with maven_repo_helper --with systemd --with php --with 
python3 --with javahelper
dh: unable to load addon javahelper: Can't locate 
Debian/Debhelper/Sequence/javahelper.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::javahelper module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 15) line 
2.
BEGIN failed--compilation aborted at (eval 15) line 2.

debian/rules:69: recipe for target 'clean' failed
make: *** [clean] Error 2
--- End Message ---
--- Begin Message ---
Uploade new version 3.6.3-4 with the missing javahelper dependency

On Sun, Dec 4, 2016 at 10:35 PM, Adrian Bunk  wrote:

> Source: zeroc-ice
> Version: 3.6.3-3
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=zeroc-ice
>
> zeroc-ice FTBFS on all architectures:
>
> ...
> dh clean --parallel --with maven_repo_helper --with systemd --with php
> --with python3 --with javahelper
> dh: unable to load addon javahelper: Can't locate
> Debian/Debhelper/Sequence/javahelper.pm in @INC (you may need to install
> the Debian::Debhelper::Sequence::javahelper module) (@INC contains:
> /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1
> /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24
> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval
> 15) line 2.
> BEGIN failed--compilation aborted at (eval 15) line 2.
>
> debian/rules:69: recipe for target 'clean' failed
> make: *** [clean] Error 2
>



-- 
José Gutiérrez de la Concha
ZeroC, Inc.
--- End Message ---

Bug#828564: sx: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-10-09 11:38:37 [+0300], Török Edwin wrote:
> Dear Maintainer,
> 
> Patches to build with both OpenSSL 1.0.x, and 1.1.0 are available in the 
> upstream git repository:
> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=5acd940e97aa1f2bd1b3fdd41f4c98a5783fcb44
> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=0dcacbab63325a83668d000dc8ed7da3bf0e4f7d
> https://gitweb.skylable.com/gitweb/?p=sx.git;a=commitdiff;h=86e06686a5fe10fd823dff805f8439a791290c5b
> 
> They apply on top of SX 2.2.

Okay. What do we do here? Any idea Laszlo?
I could try to cherry-pick the three patches into the currect 2.0 but I
can't look at them because the git server seems to be down at the moment.

Upstream asked about packaging 2.3 which makes sense (I think) but there
is something regarding the update path If I read this correctly. And 2.3
works with openssl 1.1 but needs to go via NEW due to libsxclient4 and I
hope this "transition" is okay because libsxclient3 has no rdeps.

any suggestions?

Sebastian

Bug#811778: marked as done (din: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 21:03:39 +
with message-id 
and subject line Bug#811778: fixed in din 5.2.1-4
has caused the Debian Bug report #811778,
regarding din: FTBFS with GCC 6: narrowing conversion
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
811778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: din
Version: 5.2.1-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DPACKAGE_NAME=\"din\" -DPACKAGE_TARNAME=\"din\" 
> -DPACKAGE_VERSION=\"5.2.1\" -DPACKAGE_STRING=\"din\ 5.2.1\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"din\" 
> -DVERSION=\"5.2.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GL_GL_H=1 
> -DHAVE_TCL8_5_TCL_H=1 -DHAVE_LIBIRCCLIENT_H=1 -I.   -Wdate-time 
> -D_FORTIFY_SOURCE=2-I /usr/include -I /usr/local/include -I /opt/include 
> -I/usr/include/tcl8.5 -I/usr/local/include/tcl8.5 -I /opt/include/tcl8.5 -I 
> ../include  -Wall -O3 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o levels.o levels.cc
> In file included from ../include/color.h:25:0,
>  from curve.cc:24:
> ../include/random.h: In function 'unsigned int get_rand_32()':
> ../include/random.h:57:48: error: narrowing conversion of '-1727483681' from 
> 'int' to 'unsigned int' inside { } [-Wnarrowing]
>  static unsigned int mag01[2]={0x0, MATRIX_A};
> ^
> 
> Makefile:485: recipe for target 'curve.o' failed
> make[3]: *** [curve.o] Error 1
> make[3]: *** Waiting for unfinished jobs
> In file included from ../include/color.h:25:0,
>  from ../include/console.h:31,
>  from help.cc:23:
> ../include/random.h: In function 'unsigned int get_rand_32()':
> ../include/random.h:57:48: error: narrowing conversion of '-1727483681' from 
> 'int' to 'unsigned int' inside { } [-Wnarrowing]
>  static unsigned int mag01[2]={0x0, MATRIX_A};
> ^
> 
> In file included from ../include/color.h:25:0,
>  from ../include/console.h:31,
>  from console.cc:22:
> ../include/random.h: In function 'unsigned int get_rand_32()':
> ../include/random.h:57:48: error: narrowing conversion of '-1727483681' from 
> 'int' to 'unsigned int' inside { } [-Wnarrowing]
>  static unsigned int mag01[2]={0x0, MATRIX_A};
> ^
> 
> In file included from ../include/color.h:25:0,
>  from ../include/range.h:26,
>  from range.cc:21:
> ../include/random.h: In function 'unsigned int get_rand_32()':
> ../include/random.h:57:48: error: narrowing conversion of '-1727483681' from 
> 'int' to 'unsigned int' inside { } [-Wnarrowing]
>  static unsigned int mag01[2]={0x0, MATRIX_A};
> ^
> 
> In file included from ../include/color.h:25:0,
>  from ../include/console.h:31,
>  from viewwin.cc:23:
> ../include/random.h: In function 'unsigned int get_rand_32()':
> ../include/random.h:57:48: error: narrowing conversion of '-1727483681' from 
> 'int' to 'unsigned int' inside { } [-Wnarrowing]
>  static unsigned int mag01[2]={0x0, MATRIX_A};
> ^
> 
> In file included from ../include/color.h:25:0,
>  from ../include/console.h:31,
>  from ../include/console_iterator.h:24,
>  from console_iterator.cc:21:
> ../include/random.h: In function 'unsigned int get_rand_32()':
> ../include/random.h:57:48: error: narrowing conversion of '-1727483681' from 
> 'int' to 'unsigned int' inside { } [-Wnarrowing]
>  static unsigned int mag01[2]={0x0, MATRIX_A};
> ^
> 
> In file included from ../in

Bug#817644: marked as done (python-pqueue: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 21:04:55 +
with message-id 
and subject line Bug#817644: fixed in python-pqueue 0.2-7.3
has caused the Debian Bug report #817644,
regarding python-pqueue: Removal of debhelper compat 4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
817644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pqueue
Severity: important
Usertags: compat-4-removal

Hi,

The package python-pqueue uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: python-pqueue
Source-Version: 0.2-7.3

We believe that the bug you reported is fixed in the latest version of
python-pqueue, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated python-pqueue package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Nov 2016 23:13:27 +0500
Source: python-pqueue
Binary: python-pqueue
Architecture: source
Version: 0.2-7.3
Distribution: unstable
Urgency: medium
Maintainer: Chris Lawrence 
Changed-By: Andrey Rahmatullin 
Description:
 python-pqueue - a priority queue extension for Python
Closes: 817644
Changes:
 python-pqueue (0.2-7.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch to debhelper compat level 10 (Closes: #817644).
   * Add explicit debian/source/format.
Checksums-Sha1:
 c6d4ec240a6b323531aa1f4f3f82dea01ea43037 1707 python-pqueue_0.2-7.3.dsc
 d440e3956234f2544ca0ef5d6d46dcda2e9d0ac3 5456 python-pqueue_0.2-7.3.diff.gz
Checksums-Sha256:
 cb34ea7f1a24c13df70b6fc18479b31eb153bc056ddcced15db974837311f2f5 1707 
python-pqueue_0.2-7.3.dsc
 5d8db2ca9a5c6c212de3ca2d03bfc009ced58de42bfbc1e7d1352a8f354202cd 5456 
python-pqueue_0.2-7.3.diff.gz
Files:
 e585d3440b9b4f253796d3f4ac93d255 1707 python optional python-pqueue_0.2-7.3.dsc
 083cf76fcb96491b9574acb591851260 5456 python optional 
python-pqueue_0.2-7.3.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAlg/GFoACgkQM2L3AxpJ
kuHhnQ//eVtygOsxnZOKsjYcbQk25OGxlL7YRIqyWGNOkOVBrlhHulIukE7Jr8yC
IzHsgOtGfmMjOZNrTY3gpLXN/+O0apU4GDCuK351dzGJbLJj/kUoeaIh1alK7kts
WSPaCfDoQ7wsFsV2rBXhq1l6A6X2+mKrbnyyOV5/0fAhUHLNAHrLZtrT2/XWGqc9
FdsFkLHTknG0jDwhQhBb9ApQGMeiI9ayWB+sCTUHtZ/nu+N623Per+6piLZnz1KH
0bWDHIRQanDeEGbIim3u/JHpCv5Jv+o4k/jpR0PwRNPUBqbkAO2NdedIiJc5tIgI
pva/ee7t0THSBs3Udyg2dCAQLWF1MK2CEZwNgMBQ6TrOM6/FqanwZY7vCOOTiCmJ
nyWmHeCk7OGjqEacaudEw2on4uxoJZapySsuRBApMfTTe/3bXEw+VLy0TeWFgUys
9acIXEscmuk9fyT2ueOaeNyFdhXXGznomXHwT7tHPOzVMobpG5n7I0FjmWUhfpFo
+gVu7ivippyjn7yyjHJSo9amulWndg/AJl2AGxESvs5AilGdYGWwvn9eK5ed/F29
ueErjT4x9d/2EhRCacW6YeumzjC5eIyStc8KnWOeOzjzHPfcBE4EMJPu3BhsZZdm
NT4FodpPZhvPKVhyITn/SvZDzJ6TaZXOtCt+ZRL3Hwlyb/ckty0=
=ZCuu
-END PGP SIGNATURE End Message ---

Processed: Bug#811778 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 811778 pending
Bug #811778 [din] din: FTBFS with GCC 6: narrowing conversion
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
811778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#811778: marked as pending

[James Cowgill]

tag 811778 pending
thanks

Hello,

Bug #811778 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/din.git;a=commitdiff;h=479719e

---
commit 479719e6a061200a1d4ffb27a205a09369d60a02
Author: James Cowgill 
Date:   Mon Dec 5 19:51:28 2016 +

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index 5c2b150..5960975 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,21 @@
-din (5.2.1-4) UNRELEASED; urgency=medium
+din (5.2.1-4) unstable; urgency=medium
 
   * Team upload.
-  *
 
- -- James Cowgill   Mon, 05 Dec 2016 18:20:49 +
+  [ Alessio Treglia ]
+  * Fix bashism in data/m00.
+Thanks to Raphael Geissert for the bug report. (Closes: #772264)
+  * Update debian/copyright.
+
+  [ James Cowgill ]
+  * Fix FTBFS with GCC 6. (Closes: #811778)
+  * Remove generated manpage on clean.
+  * debian/control:
+- Use debhelper compat 10.
+- Use secure Vcs URLs.
+- Bump standards to 3.9.8.
+
+ -- James Cowgill   Mon, 05 Dec 2016 19:47:53 +
 
 din (5.2.1-3) unstable; urgency=medium
 

Bug#847127: Segmentation fault when doing a "Dry run"

[Andreas Moog]

Package: gpointing-device-settings
Version: 1.6.0~git20150314.de7fe9e7-1
Severity: grave

Hi there, Andrew,

when pressing the button "Dry run" I get a segmentation fault:

Thread 1 "gpointing-devic" received signal SIGSEGV, Segmentation fault.
0x77bd4250 in get_int_properties (name=, xinput=0x828880 
[GpdsXInput]) at gpds-xinput.c:765
765 gpds-xinput.c: No such file or directory.
(gdb) q

I attached the output of "thread apply all bt full" to this report. Let me
know if you need any more information.

Thanks!

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gpointing-device-settings depends on:
ii  gconf-service3.2.6-4
ii  gconf2   3.2.6-4
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-7
ii  libcairo21.14.6-1.1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgconf-2-4 3.2.6-4
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.2-2
ii  libgpds0 1.6.0~git20150314.de7fe9e7-1
ii  libgtk2.0-0  2.24.31-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpangoft2-1.0-01.40.3-3
ii  libxi6   2:1.7.6-1.1

gpointing-device-settings recommends no packages.

gpointing-device-settings suggests no packages.

-- no debconf information

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


gdb-backtrace.txt.gz
Description: application/gzip


signature.asc
Description: PGP signature

Processed: notfixed 844917 in 4.12.0-1, fixed 844917 in 4.15.1-1, notfound 842497 in 1.15-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # unconfuse the bts (found and fixed in the same version)
> notfixed 844917 4.12.0-1
Bug #844917 {Done: Jordi Mallach } 
[src:golang-github-tideland-golib] golang-github-tideland-golib: FTBFS: Tests 
failures
No longer marked as fixed in versions 4.12.0-1.
> fixed 844917 4.15.1-1
Bug #844917 {Done: Jordi Mallach } 
[src:golang-github-tideland-golib] golang-github-tideland-golib: FTBFS: Tests 
failures
Marked as fixed in versions golang-github-tideland-golib/4.15.1-1.
> notfound 842497 1.15-1
Bug #842497 {Done: Benjamin Kaduk } [krb5] krb5: [INTL:de] 
German translation is missing
There is no source info for the package 'krb5' at version '1.15-1' with 
architecture ''
Unable to make a source version for version '1.15-1'
No longer marked as found in versions 1.15-1.
> notfixed 723555 0.2.2-1
Bug #723555 {Done: Jaromír Mikeš } [zita-ajbridge] 
zita-ajbridge link with -L/usr/lib
No longer marked as fixed in versions 0.2.2-1.
> notfixed 844596 1.18.15
Bug #844596 {Done: Guillem Jover } [dpkg-dev] 
dpkg-gensymbols doesn't update arch-bits when called with -a
No longer marked as fixed in versions 1.18.15.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
723555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723555
842497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842497
844596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844596
844917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#837861: marked as done (telepathy-logger: FTBFS due to undeclared build dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 19:52:35 +
with message-id 
and subject line Bug#837861: fixed in telepathy-logger 0.8.2-2
has caused the Debian Bug report #837861,
regarding telepathy-logger: FTBFS due to undeclared build dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
837861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-logger
Version: 0.8.2-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk-doc-tools

Hi,

your package telepathy-logger declares a build dependency on gtk-doc-tools.
gtk-doc-tools in turn depends on gnome-common, which in turn pulls in packages
like gettext, intltool or pkg-config.

The dependency on gnome-common was originally added for the GNOME_GTKDOC_CHECK
macro which has been deprecated and replaced by GTK_DOC_CHECK a long time ago.

As gnome-common has been declared deprecated by GNOME upstream [1], we would
like to drop this dependency from gtk-doc-tools.

We did a test of all reverse build dependencies of gtk-doc-tools and 
telepathy-logger
failed to build due to now missing build dependencies which are no longer
pulled in by gtk-doc-tools.

A complete build log is available at
https://people.debian.org/~biebl/gtk-doc-tools/telepathy-logger.log

We have uploaded that gtk-doc-tools package as 1.25-4 to experimental as well,
so you can test your package against this version.

Common build-failures and their fixes:

a/ configure.ac:32: error: possibly undefined macro: AC_PROG_INTLTOOL

   make[1]: intltoolize: Command not found

   → Build-Depends: intltool

b/ ./configure: line 5461: syntax error near unexpected token `yes'
   ./configure: line 5461: `GNOME_COMPILE_WARNINGS(yes)'

   ./configure: line 14801: GNOME_CODE_COVERAGE: command not found

   → Build-Depends: gnome-common (for GNOME_* macros)

c/ ./configure: line 17439: syntax error near unexpected token 
`$WARN_CFLAGS_EXTRA,'
   ./configure: line 17439: `AX_APPEND_COMPILE_FLAGS($WARN_CFLAGS_EXTRA, 
WARN_CFLAGS)'

   ./configure: line 2629: syntax error near unexpected token `git-directory'
   ./configure: line 2629: `AX_IS_RELEASE(git-directory)'

   → Build-Depends: autoconf-archive (for AX_* macros)

d/ ./configure: line 12518: intltool-update: command not found
   checking for intltool >= 0.40.0...  found
   ./configure: error: Your intltool is too old.  You need intltool 0.40.0 or 
later.

   → Build-Depends: intltool

e/ make[1]: intltoolize: Command not found

   → Build-Depends: intltool

f/ ./autogen.sh calls gnome-autogen.sh

   → Build-Depends: gnome-common


Please add the required build-dependencies to your package so once we upload
gtk-doc-tools_1.25-4 to unstable your package doesn't FTBFS.

Regards,
Michael


[1] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Source: telepathy-logger
Source-Version: 0.8.2-2

We believe that the bug you reported is fixed in the latest version of
telepathy-logger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated telepathy-logger 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Dec 2016 20:23:10 +0100
Source: telepathy-logger
Binary: telepathy-logger libtelepathy-logger3 libtelepathy-logger-dev 
libtelepathy-logger-doc gir1.2-telepathylogger-0.2
Architecture: source amd64 all
Version: 0.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Telepathy maintainers 

Changed-By: Laurent Bigonville 
Description:
 gir1.2-telepathylogger-0.2 - Telepathy logger service - introspection
 libtelepathy-logger-dev - Telepathy logger service -- utility library (headers)
 libtelepathy-logger-doc - Telepathy logger service -- documentation
 libtelepathy-logger3 - Telepathy logger service - utility library
 telepathy-logger - Telepathy logger service - Daemon
Closes: 837861
Changes:
 telepathy-logger (0.8.2-2) unstable; urgency=medium
 .
   [ Jonny Lamb ]
   * Remove myself from

Bug#844940: marked as done (telepathy-logger: FTBFS: configure: error: Your intltool is too old. You need intltool 0.35.0 or later.)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 19:52:35 +
with message-id 
and subject line Bug#837861: fixed in telepathy-logger 0.8.2-2
has caused the Debian Bug report #837861,
regarding telepathy-logger: FTBFS: configure: error: Your intltool is too old. 
You need intltool 0.35.0 or later.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
837861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-logger
Version: 0.8.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> checking for GLIB - version >= 2.0.0... yes (version 2.50.2)
> checking for X... no
> checking whether NLS is requested... yes
> ./configure: line 14069: intltool-update: command not found
> checking for intltool >= 0.35.0...  found
> configure: error: Your intltool is too old.  You need intltool 0.35.0 or 
> later.
>   "tail -v -n +0 config.log"

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/telepathy-logger_0.8.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: telepathy-logger
Source-Version: 0.8.2-2

We believe that the bug you reported is fixed in the latest version of
telepathy-logger, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated telepathy-logger 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Dec 2016 20:23:10 +0100
Source: telepathy-logger
Binary: telepathy-logger libtelepathy-logger3 libtelepathy-logger-dev 
libtelepathy-logger-doc gir1.2-telepathylogger-0.2
Architecture: source amd64 all
Version: 0.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Telepathy maintainers 

Changed-By: Laurent Bigonville 
Description:
 gir1.2-telepathylogger-0.2 - Telepathy logger service - introspection
 libtelepathy-logger-dev - Telepathy logger service -- utility library (headers)
 libtelepathy-logger-doc - Telepathy logger service -- documentation
 libtelepathy-logger3 - Telepathy logger service - utility library
 telepathy-logger - Telepathy logger service - Daemon
Closes: 837861
Changes:
 telepathy-logger (0.8.2-2) unstable; urgency=medium
 .
   [ Jonny Lamb ]
   * Remove myself from Uploaders.
 .
   [ Laurent Bigonville ]
   * debian/patches/Add-a-systemd-user-service.patch: Add a systemd user
 .service file
   * debian/control: Add intltool to the build-dependencies, this should fix
 the FTBFS (Closes: #837861)
   * debian/rules: Use gir sequence instead of overriding dh_shlibdeps call
   * debian/control: Bump Standards-Version to 3.9.8 (no further changes)
   * Drop -dbg package and rely on the automatically built dbgsym ones
   * debian/rules: Enable all hardening flags
   * debian/control: Use https and Update the Vcs-* and Homepage fields
Checksums-Sha1:
 91d1f4b3db2ad39c05f16429b8f2786acea8792e 2504 telepathy-logger_0.8.2-2.dsc
 16aa800d7715e94ee9e72c2d655d1d66829d36cd 6892 
telepathy-logger_0.8.2-2.debian.tar.xz
 c16898f4dea9aba170f1884613539913cbdf824b 80728 
gir1.2-telepathylogger-0.2_0.8.2-2_amd64.deb
 335b013c16fa5776d62ceb829cfbb61dbc4ff3fb 158216 
libtelepathy-logger-dev_0.8.2-2_amd64.deb
 471ae3a49c795c29579ee8cb407febf9f40df36a 95522 
libtelepathy-logger-doc_0.8.2-2_all.deb
 7ebbb8f3b9c416d7931d6a8b2482a7d8fa0eaf0b 250546 
libtelepathy-logger3-dbgsym_0.8.2-2_amd64.deb
 43a9b6280b895ef321ccbec4fc24546675e8785c 140552 
libtelepathy-logger3_0.8.2-2_amd64.deb
 5b152ffc1097776fd1e63303a55e1bcfe9f166ae 9278 
telepathy-logger-dbgs

Bug#831965: Status of asciidoc upload?

[Dr. Tobias Quathamer]

Am 05.12.2016 um 07:14 schrieb Alexander Wirt:

On Sun, 04 Dec 2016, Alexander Wirt wrote:

Sorry, I fucked this up. I will get joseph an admin tomorrow.

You two already were admins.

I also fixed the repo permissions (which could have been done by every admin
too).


Hi Alexander,

yes, Joseph and I were given the admin role just a few hours before you 
tried to do this, Fredrik did that.


However, there's a misunderstanding: I don't want to be admin of this 
project, as I don't use and know the package. I'm just in the loop 
because I've asked about bug #831965 -- it's RC and has a trivial fix, 
so I wondered what's the status of a new upload is.


I'd be happy to sponsor Joseph's upload, but there are many changes to 
the package, including a split into more binary packages, so I think it 
might be best if either you or Fredrik could do the upload, because 
you're familiar with the package.


Anyway, thanks for your prompt answer!

Regards,
Tobias




signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#847064: KGPG does not start

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible moreinfo
Bug #847064 [kgpg] KGPG does not start
Added tag(s) moreinfo and unreproducible.
> severity -1 normal
Bug #847064 [kgpg] KGPG does not start
Severity set to 'normal' from 'grave'

-- 
847064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847064: KGPG does not start

[Maximiliano Curia]

Control: tag -1 + unreproducible moreinfo
Control: severity -1 normal

¡Hola Karsten!

About the subject, if your kgpg is already configured kgpg starts as a 
systemtray icon. Please check that.


El 2016-12-05 a las 10:59 +0100, Karsten Malcher escribió:
Package: kgpg 
Version: 4:4.14.2-1 
Justification: renders package unusable 
Severity: grave


As a general rule, do not set a grave severity without checking that the 
issue is only present for you.



When i try to start KGPG i can see the following messages in the console:


$ kgpg 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.


This message isn't important, you can safely ignore it.

Happy hacking,
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are–by
definition–not smart enough to debug it."
-- Brian Kernighan
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: reopening 844141, severity of 844141 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 844141
Bug #844141 {Done: gregor herrmann } 
[src:libsys-cpuaffinity-perl] libsys-cpuaffinity-perl: FTBFS: Failed test 'bind 
to all processors successful 18446744073709551615 == 18446744073709551616-1'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libsys-cpuaffinity-perl/1.11~02-1.
> severity 844141 important
Bug #844141 [src:libsys-cpuaffinity-perl] libsys-cpuaffinity-perl: FTBFS: 
Failed test 'bind to all processors successful 18446744073709551615 == 
18446744073709551616-1'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
844141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#846353: FTBFS: ERROR: Test "ruby2.3" failed. Exiting.

[Sebastiaan Couwenberg]

On 12/05/2016 02:04 PM, Gilles Filippini wrote:
> Sebastiaan Couwenberg a écrit le 03/12/2016 à 19:33 :
>> On 12/03/2016 07:19 PM, Gilles Filippini wrote:
>>> I've filed #846853 against src:hdf-eos5. There are issues in
>>> ruby-hdfeos5 as well. See the attached patch.
>>>
>>> With these fixes the ruby-hdfeos5 testsuite passes on 64 bit and 32 bit
>>> arches.
>>
>> Thanks for the patch! I've applied it in git, and will do a team upload
>> after hdf-eos5 is fixed, unless Youhei beats me to it.
> 
> Fixed hdf-eos5 is now in unstable.

I've uploaded the fixed ruby-hdfeos5 to unstable.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Bug#844141: closed by gregor herrmann (Bug#844141: fixed in libsys-cpuaffinity-perl 1.11~02-1)

[gregor herrmann]

reopen -1
severity -1 important

On Tue, 22 Nov 2016 18:51:08 +, Debian Bug Tracking System wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the src:libsys-cpuaffinity-perl package:
> 
> #844141: libsys-cpuaffinity-perl: FTBFS: Failed test 'bind to all processors 
> successful 18446744073709551615 == 18446744073709551616-1'
> 
> It has been closed by gregor herrmann .

This might have been a bit premature, Lucas can still reproduce the
problem in his setup; cf.
https://rt.cpan.org/Ticket/Display.html?id=118730

So reopening but setting the severity to important as this only
appears in a rare corner case now.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Leonard Cohen: Tower of Song


signature.asc
Description: Digital Signature

Bug#844121: CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are *NOT* valid bug reports [VR-554]

[CERT(R) Coordination Center]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Greetings,

The CERT/CC is tracking this as VR-554, please retain VR-554 in the subject of 
future replies related to this issue.

Considering the issue and CVE IDs are already being publicly discussed, we are 
unlikely to take further action at this time. Any and all CVE disputes should 
be directed to MITRE (c...@mitre.org or their CVE form).

Regards,

Joel Land
Vulnerability Analysis Team
==
CERT Coordination Center
www.cert.org / c...@cert.org 
==



Sam Trenholme  writes:
>CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are *NOT* valid bug reports.
>
>Here’s the deal: The reporter had to patch MaraDNS before he was able
>to crash her.
>
>The patch, however, treats MaraDNS’ special buffer-overflow-resistant
>“js_string” as if it were an ordinary string — but it’s not. Here’s
>the offending code patched in to MaraDNS from the reporter’s “bug
>report”:
>
>sock_num = read(0, incoming, 512);
>
>As per the man page for read:
>
>ssize_t read(int fd, void *buf, size_t count);
>
>DESCRIPTION
>   read()  attempts to read up to count bytes from file descriptor fd into
>   the buffer starting at buf.
>
>However, incoming is not a raw string buffer: It’s a special js_string
>object which MaraDNS uses to be buffer overflow resistant, as can be
>seen here in server/MaraDNS.c:
>
>int main(int argc, char **argv) {
>
>js_string *mararc_loc = 0, *errors = 0,
>  *bind_address = 0, *ipv6_bind_address = 0,
>  *csv2_synthip_address = 0,
>  *ipv4_bind_address = 0, *incoming = 0,
>  *uncomp = 0, *verbstr = 0;
>
>The js_string structure (I guess I would call it an object here in
>2016) is defined in libs/JsStr.h:
>
>typedef struct {
>unsigned char *string;   /* Actual physical string */
>unsigned int unit_size;  /* The size of a single character in the string */
>unsigned int unit_count; /* The length of the string, in units */
>unsigned int max_count;  /* The maximum allowable size of the string,
>   also in units */
>int encoding;   /* The type of language/encoding the string is in */
>int is_good;/* This is checked to make sure the data structure is
>   sane */
>} js_string;
>
>Point being, if we patch MaraDNS to treat this structure as a raw
>buffer instead of a structure, we will be able to crash MaraDNS — but
>that doesn’t mean we have found a UDP packet of death which will crash
>unpatched MaraDNS 2.0.13.
>
>I appreciate that people are performing security research with
>MaraDNS, and the fact that researchers need to resort to patching
>MaraDNS before crashing her indicates that, a decade and a half later
>MaraDNS is still a usable DNS server with a strong security record.


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJYRakeAAoJEOaVDwyMMQJnHSMP/jSEFU9QxktXE+iZR0eaIgBE
/KBiSXAr6MoyIqBhlbaGtg/8aAdrxAP9U6XGvH7ntU/yuy04vOhVbl5rYVsOarg8
1mQWZ48L79ek+P5DBprnbTpoJYoscNIv6FBEH1JM3uXdK80FGajMPf7MOyJsZpPu
/Xcv0cEqrRdJClggQhEoKyz4h8EiT12yl4CvWfVRzX8TFtKGjLh0QIbeLo3OknJZ
dRYylBEf4Z+iD2C3EM8QpjuQfMYGT2YDfc6rjgNuuOl2SBliGMoH6FKXiCNAsn5Q
tfCNFNYP+6On8wfP9hRqPLfQWgxd12bWCWeFEKd0LSsxEvaFpdlwQmLshzxiRDxU
3QYw7azzzFTA6RoBgMOblravwkXY4Gi+vTQqsBqkgCdqNI1i3z6VGGn3xQAfeDFi
lAze+1S7EiEMK96uWygTjCtonoBZdZyuP3J0hQloozxV4+2njSN+H/HosEyirhwe
DVkS2excLG22+K8+PSPkKQZnPMVZQwHH6SkXyGI1uPq9PTLM1cpyqFCT1iI4tRep
3VeMkMwts0NEyRAuvXRhYnKQid71NsWBnNN4OgMtCOxU+JIWHjZzpDOamD99fvZg
/OBdCMvfQcW0YLcMRVV1hznhzfSL9+nL90FpLeeSJ6eszCM5EiAQ+mOGG3/p2t7h
f/0gUgTFaN/A9J+yvUpN
=q4mi
-END PGP SIGNATURE-

Processed: tagging 811793

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 811793 + confirmed
Bug #811793 [packup] packup: FTBFS with GCC 6: error: reference is ambiguous
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
811793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 811793 is forwarded to mikolas DOT janota AT gmail DOT com

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 811793 mikolas DOT janota AT gmail DOT com
Bug #811793 [packup] packup: FTBFS with GCC 6: error: reference is ambiguous
Set Bug forwarded-to-address to 'mikolas DOT janota AT gmail DOT com'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
811793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 811793

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 811793 + upstream
Bug #811793 [packup] packup: FTBFS with GCC 6: error: reference is ambiguous
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
811793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#787956: raising the severity, prevents usage of the multilib packages

[Mark Brown]

On Mon, Dec 05, 2016 at 06:24:46PM +0100, Matthias Klose wrote:
> On 05.12.2016 18:14, Mark Brown wrote:

> > I am suggesting that since nothing except for the multlib D runtime
> > packages needs a multilib zlib and there seems to be a very limited use
> > case for them it seems better to just not ship the multilib runtime for
> > D and instead have people who want to build or run non-native D code use
> > multiarch.  That's where we want to get to anyway.

> >> PS: I pinged about a) moving back zconf.h to /usr/include and b) running
> >> dh_makeshlibs for the 64bit multilib variant. Any update on this?

> > I saw your content free pings.

> If the ping should have been content free, than the content should be in the 
> PS.
>  Or please could you tell me what you are missing?

As we have been discussing it is still not clear to me if I should fix
or remove the multilib packages since it is still not clear to me that
there is a sensible use case for them.  As things stand I'm still not
seeing much of a use case here so it seems like the best thing to do
would be to remove the multilibs.


signature.asc
Description: PGP signature

Bug#846412: marked as done (bsdgames: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 17:48:26 +
with message-id 
and subject line Bug#846412: fixed in bsdgames 2.17-25
has caused the Debian Bug report #846412,
regarding bsdgames: add libfl-dev to Build-Depends
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
846412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bsdgames
Severity: important
User: helm...@debian.org
Usertags: libfldep

bsdgames will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since bsdgames uses parts of libfl-dev (e.g.
libl.a, libfl.a or FlexLexer.h), it should add libfl-dev to its
Build-Depends. This change was previously announced[1] to
debian-devel in accordance with DevRef 7.1.1. Please add the missing
dependency.

Helmut

[1] https://lists.debian.org/debian-devel/2016/03/msg00162.html 
--- End Message ---
--- Begin Message ---
Source: bsdgames
Source-Version: 2.17-25

We believe that the bug you reported is fixed in the latest version of
bsdgames, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 846...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated bsdgames package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 05 Dec 2016 18:27:24 +0100
Source: bsdgames
Binary: bsdgames
Architecture: source
Version: 2.17-25
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Dr. Tobias Quathamer 
Description:
 bsdgames   - collection of classic textual unix games
Closes: 846412
Changes:
 bsdgames (2.17-25) unstable; urgency=medium
 .
   * Add libfl-dev to Build-Depends.
 Thanks to Helmut Grohne  (Closes: #846412)
   * Use debhelper v10
   * Update to Standards-Version 3.9.8, no changes needed
Checksums-Sha1:
 987972a5d262cbd2f4288589829c38c205d5d795 1904 bsdgames_2.17-25.dsc
 4512673116c2ac0185673e9532d1719539025540 6 bsdgames_2.17-25.debian.tar.xz
Checksums-Sha256:
 5889856487411075870a124152f3af3f9f5ac74e3a36fbcd386f3a8b3fe12c0b 1904 
bsdgames_2.17-25.dsc
 f307211c7208ab24896cd239d8dc54f56449b342582a5e27e64c3e145247520f 6 
bsdgames_2.17-25.debian.tar.xz
Files:
 1a3765e9b1a6a8e7be357cd9991c6ddd 1904 games optional bsdgames_2.17-25.dsc
 5c00b1e89cb360007cca7be4b2c09c6a 6 games optional 
bsdgames_2.17-25.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYRaS9AAoJEBMC8fA26+sZ3uIP/1jZoA6Wa6lW9VZutROoPsmx
Xq4i5OLxE1JIdV9qUdg7f30rJy1O10tG/dIwWAK0jfB5FgxN/qGK3neBSZWpcPEd
QWLPsLR0yE5N1DNoYbte1eN/DcIJAM8CYRTZSGK5TZDTVCo0n+l7bV8dgWVFOSRA
FS7iA0oAS0eWp7D+6xfixUJalqc3gRNkLikcKHf1X0R9dJ2aKM1+3IyAOQvVXOzf
N2QmOI+FlduBmXDXMr52vf3H0MD7Ajt0Ag6H3jfWpSUXO4OTsDblF8XqiceDqp5W
gm2e0+iOJt5FBjZIIgoD/NDSMscnCE0HfZK7GRNmQULMImZvPfiVbCT7ws8AuPEX
VyCNeTnnOSbuU1M7Zee2alXiz3VbPMmSFbe7B7V3UVsG6yPDcRNnlQfGu4tpuIse
nOhlLuleJoAMIXnx1zowDzff0f4uB9ymbcQy+TuGDGBEgMW2ilBxZXxnyJY2sxKu
kZRLXB+24vxbh2wH3YEbWn6t87SQ9pd7HX1aGnqp4s0LsNiupsxcRDGjkdPTun03
h42bgoDYKse3bydxjun1pLVa/olzt8x7txBUFyvCTY/9PUX6kZBXQtAwZeOmSq7N
yj/gUfn6aiNLf6gofjBUNKt8FtMaRtFG+U7vWFNTgyXwUeQYSsDqWBjTfAsrnPyB
S9tVtnzlOvYf84Tjn0Z6
=RtbJ
-END PGP SIGNATURE End Message ---

Processed: [bts-link] source package src:lastpass-cli

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:lastpass-cli
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #828371 (http://bugs.debian.org/828371)
> # Bug title: lastpass-cli: FTBFS with openssl 1.1.0
> #  * https://github.com/lastpass/lastpass-cli/pull/215
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 828371 + fixed-upstream
Bug #828371 [src:lastpass-cli] lastpass-cli: FTBFS with openssl 1.1.0
Added tag(s) fixed-upstream.
> usertags 828371 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 828371 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
828371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847055: graphicsmagick: CVE-2016-9830

[Bob Friesenhahn]

On Mon, 5 Dec 2016, Salvatore Bonaccorso wrote:


Hi Chris, hi Bob,

On Mon, Dec 05, 2016 at 05:26:23PM +0100, Chris Lamb wrote:

[Please retain 847...@bugs.debian.org in CC]

Bob Friesenhahn wrote:


Is this CVE fixed upstream?  I am not aware of this number.


I do not know, sorry.


The CVE was assigned in the thread
https://marc.info/?l=oss-security&m=148090788501782&w=2 .


Thanks.  I noticed the posting while catching up with my email.

This morning I updated the GraphicsMagick ChangeLog file to make note 
of the CVE against the fix which was already made in Mercurial.


I have heard that ImageMagick suffers from the same problem.

Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/

Bug#846871: Suggested fix

[Ghislain Vaillant]

On Mon, 05 Dec 2016 11:53:59 +0100 Hilko Bengen  wrote:
> control: tag -1 patch
> 
> Hi,
> 
> I have verified that aff4 builds just fine if the "keepalive=0.5" line
> is removed from the requires.txt, so the extra python-keepalive package
> is not actually needed.
> 
> Please consider adding the patch below. Thanks!
> 
> Cheers,
> -Hilko
> 
> diff --git a/requirements.txt b/requirements.txt
> index cdd0693..55ec214 100644
> --- a/requirements.txt
> +++ b/requirements.txt
> @@ -1,2 +1 @@
>  rdflib>=4.0
> -keepalive>=0.5

I confirm that the dependency on keepalive should not be so strict. A quick
lookup in the upstream VCS showed that it is only used in one method of the
SPARQLWrapper class and its absence only raises a warning.

@maintainers
Please incorporate Hilko's patch to prevent transitive dependencies on keepalive
from leading to FTBFS in packages depending on rdflib. Thanks.

@Hilko
Do you intend to package keepalive? Your first message somewhat hinted this.

Cheers,
Ghis

Processed: Add bug version info

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 846412 2.17-24
Bug #846412 [src:bsdgames] bsdgames: add libfl-dev to Build-Depends
Marked as found in versions bsdgames/2.17-24.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
846412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#787956: raising the severity, prevents usage of the multilib packages

[Matthias Klose]

On 05.12.2016 18:14, Mark Brown wrote:
> On Mon, Dec 05, 2016 at 04:40:29PM +0100, Matthias Klose wrote:
>> On 05.12.2016 11:29, Mark Brown wrote:
>>> On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote:
> 
 it's available in the GCC packages for a while now.
> 
>>> Sure, but there's a bunch more stuff needed.
> 
>> sorry, I don't understand what you mean.
> 
> Getting full x32 support is going to require more than just the
> compiler.

Again, I don't know what this has to do about this issue. I was asking about x32
multilibs in zlib.

>> Well, there are less requirements for the C and C++ runtime libraries 
>> (basically
>> glibc), but the D runtime library requires one more, zlib. I'm not sure what 
>> you
>> are arguing here.
> 
> I am suggesting that since nothing except for the multlib D runtime
> packages needs a multilib zlib and there seems to be a very limited use
> case for them it seems better to just not ship the multilib runtime for
> D and instead have people who want to build or run non-native D code use
> multiarch.  That's where we want to get to anyway.
> 
>> PS: I pinged about a) moving back zconf.h to /usr/include and b) running
>> dh_makeshlibs for the 64bit multilib variant. Any update on this?
> 
> I saw your content free pings.

If the ping should have been content free, than the content should be in the PS.
 Or please could you tell me what you are missing?

Bug#787956: raising the severity, prevents usage of the multilib packages

[Mark Brown]

On Mon, Dec 05, 2016 at 04:40:29PM +0100, Matthias Klose wrote:
> On 05.12.2016 11:29, Mark Brown wrote:
> > On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote:

> >> it's available in the GCC packages for a while now.

> > Sure, but there's a bunch more stuff needed.

> sorry, I don't understand what you mean.

Getting full x32 support is going to require more than just the
compiler.

> Well, there are less requirements for the C and C++ runtime libraries 
> (basically
> glibc), but the D runtime library requires one more, zlib. I'm not sure what 
> you
> are arguing here.

I am suggesting that since nothing except for the multlib D runtime
packages needs a multilib zlib and there seems to be a very limited use
case for them it seems better to just not ship the multilib runtime for
D and instead have people who want to build or run non-native D code use
multiarch.  That's where we want to get to anyway.

> PS: I pinged about a) moving back zconf.h to /usr/include and b) running
> dh_makeshlibs for the 64bit multilib variant. Any update on this?

I saw your content free pings.


signature.asc
Description: PGP signature

Bug#828486: Support for multiple versions of OpenSSL in libp11

[Michał Trojnara]

Hi,

Support for multiple OpenSSL versions was added in libp11 0.4.3:
https://github.com/OpenSC/libp11/releases/tag/libp11-0.4.3

The specific features are:
 - Symbol versioning
 - Soname tied with with the OpenSSL soname

Best regards,
Mike

Bug#846774: openssl/dso.h: No such file or directory

[Michał Trojnara]

> eng_front.c:71:25: fatal error:
> openssl/dso.h: No such file or directory

OpenSSL 1.1.x builds are fixed upstream in libp11 0.4.3.
https://github.com/OpenSC/libp11/releases/tag/libp11-0.4.3

Best regards,
Mike

Processed: forcibly merging 847071 847077

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 847071 847077
Bug #847071 [src:firmware-nonfree] firmware-nonfree has no binaries on any arch
Bug #847077 [src:firmware-nonfree] firmware-nonfree: Sid binary packages gone
Severity set to 'serious' from 'grave'
The source firmware-nonfree and version 20161130-1 do not appear to match any 
binary packages
Marked as found in versions firmware-nonfree/20161130-1.
Merged 847071 847077
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847071
847077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847071: firmware-nonfree has no binaries on any arch

[Laurent Bigonville]

Le 05/12/16 à 17:45, Ben Hutchings a écrit :

On Mon, 2016-12-05 at 11:58 +0100, Laurent Bigonville wrote:

Source: firmware-nonfree
Version: 20161130-1
Severity: serious

Hi,

It seems that the last upload of firmware-nonfree package has no binary
packages and that the buildd are not allowed to build them from the
(non-free) sources.

I guess a new upload should be done.

*sigh* I keep forgetting that non-free is special and this won't be
auto-built.


Maybe you could ask that the package are built even if they are non-free:

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd

Bug#847071: firmware-nonfree has no binaries on any arch

[Ben Hutchings]

On Mon, 2016-12-05 at 11:58 +0100, Laurent Bigonville wrote:
> Source: firmware-nonfree
> Version: 20161130-1
> Severity: serious
> 
> Hi,
> 
> It seems that the last upload of firmware-nonfree package has no binary
> packages and that the buildd are not allowed to build them from the
> (non-free) sources.
> 
> I guess a new upload should be done.

*sigh* I keep forgetting that non-free is special and this won't be
auto-built.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett



signature.asc
Description: This is a digitally signed message part

Bug#847055: graphicsmagick: CVE-2016-9830

[Salvatore Bonaccorso]

Hi Chris, hi Bob,

On Mon, Dec 05, 2016 at 05:26:23PM +0100, Chris Lamb wrote:
> [Please retain 847...@bugs.debian.org in CC]
> 
> Bob Friesenhahn wrote:
> 
> > Is this CVE fixed upstream?  I am not aware of this number.
> 
> I do not know, sorry.

The CVE was assigned in the thread
https://marc.info/?l=oss-security&m=148090788501782&w=2 .

Regards and hope this help,

Salvatore

Bug#847055: graphicsmagick: CVE-2016-9830

[Chris Lamb]

[Please retain 847...@bugs.debian.org in CC]

Bob Friesenhahn wrote:

> Is this CVE fixed upstream?  I am not aware of this number.

I do not know, sorry.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#847083: marked as done (build accesses the network during the build)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 16:06:32 +
with message-id 
and subject line Bug#847083: fixed in rapmap 0.4.0+dfsg-2
has caused the Debian Bug report #847083,
regarding build accesses the network during the build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rapmap
Version: 0.4.0+dfsg-1
Severity: serious
Tags: sid stretch

According to the build log, the package tries to download components during the
build.

https://buildd.debian.org/status/fetch.php?pkg=rapmap&arch=kfreebsd-amd64&ver=0.4.0%2Bdfsg-1&stamp=1476727945

Please allow the package to build on the buildds on amd64 for a proper build.
--- End Message ---
--- Begin Message ---
Source: rapmap
Source-Version: 0.4.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
rapmap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 847...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated rapmap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Dec 2016 16:32:20 +0100
Source: rapmap
Binary: rapmap
Architecture: source
Version: 0.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 rapmap - rapid sensitive and accurate DNA read mapping via quasi-mapping
Closes: 847083 847084
Changes:
 rapmap (0.4.0+dfsg-2) unstable; urgency=medium
 .
   * Set NO_NATIVE_ARCH=true
 Closes: #847084
   * Do not try downloading libjemalloc
 Closes: #847083
   * debhelper 10
   * d/watch: version=4
   * hardening=+all
Checksums-Sha1:
 166cdf0e2bc3d9dd5ebc8200279b4a6b9d594b16 2097 rapmap_0.4.0+dfsg-2.dsc
 9f3bfa1c15de6b57e3556e3b1b11645286bf0614 7560 rapmap_0.4.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 b5002f9914faae198e92a3b3212d2fbb40c20beb6a02878cfb726aab66af4671 2097 
rapmap_0.4.0+dfsg-2.dsc
 6141378e5f86b22e3b8e3c85d98ed37fc2ccec94f74d7b201d961a98efab0ff8 7560 
rapmap_0.4.0+dfsg-2.debian.tar.xz
Files:
 00b971d4bd0c16c54f8bc19932d588f2 2097 science optional rapmap_0.4.0+dfsg-2.dsc
 8bd5dba2899e6c68ff6e5ea8a02c6cb2 7560 science optional 
rapmap_0.4.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYRYw4AAoJEFeKBJTRxkbRTfYP+wUazc0HjxkPrD7+kmREgbLd
ufrL+zK/ZYHvmnGOLAA883MFqxLT1pEJsE6Q0Kr6SVvUrne3173VkH/g35Qm5B7y
u3ndGuKgAEdc7afXkDEdZi1qgsYOw/WLTwqDakCSzHi2lHH7Eq8ZfVrUj0HAOciR
Wu6BrfVDDL71a5N2zCxvaOLULSPV1X5jYWpGmYeq1BG6QsTwEW9uD4u5oOY+TE6U
27AzmV9pVIoNkLwe9xJoTZMYJFh8nRcr/QHNayaQtTkQ2GpQyk1tHpex7eEUXD77
Ir7MgxGor8CQiTs+bsk7X5hYsPDqrzofztorsYGKkP1hr8zWY4vSnzJlD0KmIr8D
NN9Y+Nkb1BaoUhzFsWAWWBlqDkEMtf9Ezy4UKPyLuINQ5rJ5pJthreD/TBuFj4eI
+yczZKgyDYEuVg22Pvvqx74V0HWtiCz9JddUXoFB0qzzLqBc5GRKxjtsh35gKDRE
54pMXi+X8WKOTLzyUykoDuaEBSQJmhxj+JBSXPIJmWKcUoz/XVHzlq4Bd+IQc3tj
q8B5QDDdhCogHwsvuuXc+c5MU6k3u1AWuQRIv5DpYr0iEpfUyJCHdyJnVQ9G6KSa
A3Bo/kZhOjxdVLggUm51MsIs53pxOTY39SDJv/WyBbiPTU/fMeMrU4Ky2hsphqIz
R7fQwZ45WYV8IJ0GLyli
=Fvjz
-END PGP SIGNATURE End Message ---

Bug#847084: marked as done (package builds with -march=native)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 16:06:32 +
with message-id 
and subject line Bug#847084: fixed in rapmap 0.4.0+dfsg-2
has caused the Debian Bug report #847084,
regarding package builds with -march=native
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rapmap
Version: 0.4.0+dfsg-1
Severity: serious
Tags: sid stretch

The package builds with -march=native, not allowed by Debian policy.
--- End Message ---
--- Begin Message ---
Source: rapmap
Source-Version: 0.4.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
rapmap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 847...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated rapmap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Dec 2016 16:32:20 +0100
Source: rapmap
Binary: rapmap
Architecture: source
Version: 0.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 rapmap - rapid sensitive and accurate DNA read mapping via quasi-mapping
Closes: 847083 847084
Changes:
 rapmap (0.4.0+dfsg-2) unstable; urgency=medium
 .
   * Set NO_NATIVE_ARCH=true
 Closes: #847084
   * Do not try downloading libjemalloc
 Closes: #847083
   * debhelper 10
   * d/watch: version=4
   * hardening=+all
Checksums-Sha1:
 166cdf0e2bc3d9dd5ebc8200279b4a6b9d594b16 2097 rapmap_0.4.0+dfsg-2.dsc
 9f3bfa1c15de6b57e3556e3b1b11645286bf0614 7560 rapmap_0.4.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 b5002f9914faae198e92a3b3212d2fbb40c20beb6a02878cfb726aab66af4671 2097 
rapmap_0.4.0+dfsg-2.dsc
 6141378e5f86b22e3b8e3c85d98ed37fc2ccec94f74d7b201d961a98efab0ff8 7560 
rapmap_0.4.0+dfsg-2.debian.tar.xz
Files:
 00b971d4bd0c16c54f8bc19932d588f2 2097 science optional rapmap_0.4.0+dfsg-2.dsc
 8bd5dba2899e6c68ff6e5ea8a02c6cb2 7560 science optional 
rapmap_0.4.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYRYw4AAoJEFeKBJTRxkbRTfYP+wUazc0HjxkPrD7+kmREgbLd
ufrL+zK/ZYHvmnGOLAA883MFqxLT1pEJsE6Q0Kr6SVvUrne3173VkH/g35Qm5B7y
u3ndGuKgAEdc7afXkDEdZi1qgsYOw/WLTwqDakCSzHi2lHH7Eq8ZfVrUj0HAOciR
Wu6BrfVDDL71a5N2zCxvaOLULSPV1X5jYWpGmYeq1BG6QsTwEW9uD4u5oOY+TE6U
27AzmV9pVIoNkLwe9xJoTZMYJFh8nRcr/QHNayaQtTkQ2GpQyk1tHpex7eEUXD77
Ir7MgxGor8CQiTs+bsk7X5hYsPDqrzofztorsYGKkP1hr8zWY4vSnzJlD0KmIr8D
NN9Y+Nkb1BaoUhzFsWAWWBlqDkEMtf9Ezy4UKPyLuINQ5rJ5pJthreD/TBuFj4eI
+yczZKgyDYEuVg22Pvvqx74V0HWtiCz9JddUXoFB0qzzLqBc5GRKxjtsh35gKDRE
54pMXi+X8WKOTLzyUykoDuaEBSQJmhxj+JBSXPIJmWKcUoz/XVHzlq4Bd+IQc3tj
q8B5QDDdhCogHwsvuuXc+c5MU6k3u1AWuQRIv5DpYr0iEpfUyJCHdyJnVQ9G6KSa
A3Bo/kZhOjxdVLggUm51MsIs53pxOTY39SDJv/WyBbiPTU/fMeMrU4Ky2hsphqIz
R7fQwZ45WYV8IJ0GLyli
=Fvjz
-END PGP SIGNATURE End Message ---

Bug#846708: FastQC should adapt to new htsjdk API which has dropped SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))

[Andreas Tille]

Hi folks,

does anybody feel able to rather patch FactQC than reintroducing the
outdated API to htsjdk?  Same is valid for Artemis.  I admit while
reintroducing the old API works I'd consider this only the second best
solution for the problem.

Kind regards

 Andreas.

On Mon, Dec 05, 2016 at 02:47:16PM +, Simon Andrews wrote:
> Hi Andreas,
> 
> None of the official FastQC releases has ever used htsjdk - we've been using 
> the older picard sam.jar API which is substantially different (htsjdk is a 
> major rewrite and restructure - it's not just a version update).  Internally 
> we have tried the new API, and although it works OK it also imposes a 
> restriction on the use of java >=8 which wasn't present in the old version 
> and which would break a lot of our existing installations. We're therefore 
> not keen to make that change yet - especially since the old API works just 
> fine for all the types of data we support.
> 
> If you're packaging this for Debian and wanted to move to htkjdk then it's 
> pretty trivial to patch this.  It takes a small boilerplate change to the BAM 
> opening and reading code in the BAMFile class, and a change to the classpath 
> in the launcher script (which I guess you're already doing).  We'll probably 
> move to the new API eventually, but at the moment the downsides outweigh the 
> benefits for us.
> 
> Cheers
> 
> Simon.
> 
> 
> 
> 
> -Original Message-
> From: Andreas Tille [mailto:ti...@debian.org]
> Sent: 05 December 2016 14:34
> To: Simon Andrews ; 846...@bugs.debian.org
> Cc: Vincent Danjean ; Olivier Sallou 
> ; Charles Plessy 
> Subject: FastQC should adapt to new htsjdk API which has dropped 
> SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 
> (#767))
> 
> Hi Simon,
> 
> after uploading htsjdk 2.7.0 FastQC failed to build from source[1].  I 
> relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
> was removed from htsjdk source and assumed that this was by accident.
> However, upstream has dropped this interface intentionally as you can read 
> below.  In issue #767[2] an htsjdk author gives advise to use the new API 
> version.
> 
> Kind regards
> 
>Andreas.
> 
> 
> [1] https://bugs.debian.org/846708
> [2] https://github.com/samtools/htsjdk/issues/767
> 
> 
> - Forwarded message from Daniel Gómez-Sánchez  
> -
> 
> Date: Mon, 05 Dec 2016 06:18:16 -0800
> From: Daniel Gómez-Sánchez 
> To: samtools/htsjdk 
> Cc: Andreas Tille , Author 
> Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767)
> 
> The file was removed in #699 because it was deprecated. I guess that either 
> 1) fastqc/artemis should be updated to use the new API version, or 2) the 
> classpath for them in Debian should include an older version.
> 
> --
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910
> 
> - End forwarded message -
> 
> --
> http://fam-tille.de
> The Babraham Institute, Babraham Research Campus, Cambridge CB22 3AT 
> Registered Charity No. 1053902.
> The information transmitted in this email is directed only to the addressee. 
> If you received this in error, please contact the sender and delete this 
> email from your system. The contents of this e-mail are the views of the 
> sender and do not necessarily represent the views of the Babraham Institute. 
> Full conditions at: www.babraham.ac.uk
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#847095: marked as done (libmongoclient-dev: Should not conflict with transitional mongodb-dev)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 15:51:30 +
with message-id 
and subject line Bug#847095: fixed in mongo-cxx-driver-legacy 1.1.2-5
has caused the Debian Bug report #847095,
regarding libmongoclient-dev: Should not conflict with transitional mongodb-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmongoclient-dev
Version: 1.1.2-4
Severity: serious
Tags: patch
Justification: piuparts failure

The package does not migrate to testing due to a piuparts failure:
https://piuparts.debian.org/sid/fail/mongodb-dev_2:1.1.2-4.log

Extract:
0m19.6s ERROR: Command failed (status=100): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpRj5FHY', 'apt-get', '-y', 'install', 
'mongodb-dev=2:1.1.2-4']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   mongodb-dev : Depends: libmongoclient-dev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.


The problem is that the new transitional mongodb-dev depends on
libmongoclient-dev which conflicts with mongodb-dev (this would have
been caught by trying to install the uploaded packages).

Please make the conflict versioned or drop it entirely:
--- a/debian/control
+++ b/debian/control
@@ -27,7 +27,7 @@ Section: libdevel
 Architecture: any
 Multi-Arch: same
 Depends: libmongoclient0 (= ${binary:Version}), ${misc:Depends}
-Conflicts: mongodb-dev
+Conflicts: mongodb-dev (<< 2:1.1.2-1~)
 Description: MongoDB C++ Driver (development)
  This package provides C++ development file to interact with MongoDB.
  This is the legacy C++ driver and currently supports MongoDB 2.4, 2.6,

Please upload a fixed package soon and increase priority to high to speed up
testing migration since we already waited multiple rounds for testing migration.

If you can't upload a fixed package soon, let me know and I can upload an
NMU.

Cheers,
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: mongo-cxx-driver-legacy
Source-Version: 1.1.2-5

We believe that the bug you reported is fixed in the latest version of
mongo-cxx-driver-legacy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 847...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated 
mongo-cxx-driver-legacy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Dec 2016 17:21:28 +0200
Source: mongo-cxx-driver-legacy
Binary: libmongoclient-dev libmongoclient0 mongodb-dev
Architecture: source
Version: 1.1.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian MongoDB Maintainers 

Changed-By: Apollon Oikonomopoulos 
Description:
 libmongoclient-dev - MongoDB C++ Driver (development)
 libmongoclient0 - MongoDB C++ Driver (runtime)
 mongodb-dev - MongoDB C++ Driver (transitional package)
Closes: 847095
Changes:
 mongo-cxx-driver-legacy (1.1.2-5) unstable; urgency=medium
 .
   * libmongoclient-dev: Use versioned Breaks/Replaces instead of Conflicts
 with mongodb-dev (Closes: #847095)
Checksums-Sha1:
 b40c9b2114f17e8939b03cff5c75be98ed8902ff 2502 
mongo-cxx-driver-legacy_1.1.2-5.dsc
 1ee98c6c907f4a6cfb8b498d788127b0a2673d5d 19820 
mongo-cxx-driver-legacy_1.1.2-5.debian.tar.xz
Checksums-Sha256:
 77b556271badcdae4a9c1477201738e95d7036c

Bug#846729: marked as done (keystone: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 15:51:23 +
with message-id 
and subject line Bug#846729: fixed in keystone 2:10.0.0-4
has caused the Debian Bug report #846729,
regarding keystone: FTBFS: Tests failures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
846729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: keystone
Version: 2:10.0.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>   File "keystone/identity/backends/sql.py", line 119, in create_user
> user = utils.hash_user_password(user)
>   File "keystone/common/utils.py", line 136, in hash_user_password
> return dict(user, password=hash_password(password))
>   File "keystone/common/utils.py", line 143, in hash_password
> password_utf8, rounds=CONF.crypt_strength)
>   File "/usr/lib/python2.7/dist-packages/passlib/utils/decor.py", line 190, 
> in wrapper
> warn(msg % tmp, DeprecationWarning, stacklevel=2)
> DeprecationWarning: the method 
> passlib.handlers.sha2_crypt.sha512_crypt.encrypt() is deprecated as of 
> Passlib 1.7, and will be removed in Passlib 2.0, use .hash() instead.
> 
> 
> --
> Ran 6957 tests in 49.275s
> 
> FAILED (failures=3459, skipped=1450)
> debian/rules:20: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/keystone_10.0.0-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: keystone
Source-Version: 2:10.0.0-4

We believe that the bug you reported is fixed in the latest version of
keystone, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 846...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated keystone package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Dec 2016 12:33:54 +0100
Source: keystone
Binary: python-keystone keystone keystone-doc
Architecture: source all
Version: 2:10.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 keystone   - OpenStack identity service
 keystone-doc - OpenStack identity service - documentation
 python-keystone - OpenStack identity service - library
Closes: 846729
Changes:
 keystone (2:10.0.0-4) unstable; urgency=medium
 .
   * Fix passlib call of encrypt() which is replaced by hash() upstream
 (Closes: #846729).
Checksums-Sha1:
 14c9f6476e14717621783cc4f23926c5036dcfd0 3721 keystone_10.0.0-4.dsc
 316f5b2ad665b7f18ee615a16ff7bc3f2b993a8a 36444 keystone_10.0.0-4.debian.tar.xz
 73a183c72e852de058900e9585ab7fb21383cc3f 240388 keystone-doc_10.0.0-4_all.deb
 7ffc15348625365c5fa97a3151f6d3ea67449034 71318 keystone_10.0.0-4_all.deb
 44c62706cdda080006a4dd47c841edd3c915c369 13705 
keystone_10.0.0-4_amd64.buildinfo
 00ded8bfe0f90b01f388c88bcd1a653af0f8afca 680708 
python-keystone_10.0.0-4_all.deb
Checksums-Sha256:
 f10d205dd866e42e9c8ec2ce2a999d7b29a0e22cc2bc003f2e401c92f15460a0 3721 
keystone_10.0.0-4.dsc
 f7d73fc671958913c26239176f8349ab9f7fba8f164240f8ba1c4fdf2ae7ac94 36444 
keystone_10.0.0-4.debian.tar.xz
 16065a73bee2817c96226dc688cc7c01e01402791b913a1aae588153d71e1f57 240388 
keystone-doc_10.0.0-4_all.deb
 40029b8d8f295e6f42743516bed108228fe016fcebda9411dab45ea2246911b2 71318 
keystone_10.0.0-4_all.deb
 201cad610e6a5f23e7c7593bf9b8501b444b4e48a1adb85e0d19b83c65d5c4e9 13705 
keystone_10.0.0-4_amd64.buildinfo
 aa148ab4c74a83cc65a58b03c3cfea7457cf1d41597ee1c1217310ef9775367f 680708 
python-keystone_10.

Bug#845793: Bug#787956: raising the severity, prevents usage of the multilib packages

[Matthias Klose]

On 05.12.2016 11:29, Mark Brown wrote:
> On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote:
>> On 30.11.2016 13:45, Mark Brown wrote:
> 
>>> Well, there's a bunch of questions there - people seem generally
>>> negative on x32 and the use cases for multilib with tooling for early
>>> boot and so on don't seem to apply in any case.  I'd really have
>>> expected that it'd just be added as a new architecture at this point.
> 
>> it's available in the GCC packages for a while now.
> 
> Sure, but there's a bunch more stuff needed.

sorry, I don't understand what you mean.

>>> install the multiarch runtime?  The motivation I'm aware of for still
>>> having the multilib packages is to allow other multilib packages to be
>>> built with them but I'm not seeing any packages written in D (and it'd
>>> be pretty surprising TBH given the narrow use case) so I'm not seeing
>>> the use case.
> 
>> If we remove everything where "people seem generally negative on FOO", we'll 
>> end
>> up with a really small distro. We still require the multilibs for 32bit
>> architectures needing to build 64bit kernels, and I'd rather not ask people 
>> to
>> work around issues when they can be fixed.
> 
> These are good reasons for having multilib for C and (to a bit of a
> lesser extent) C++ but this is D which is a different thing - it's a new
> language which is much less widely used.  It is much more difficult to
> see the use case for D, as far as I can tell the applications don't
> really need multilibs.

Well, there are less requirements for the C and C++ runtime libraries (basically
glibc), but the D runtime library requires one more, zlib. I'm not sure what you
are arguing here.

Matthias

PS: I pinged about a) moving back zconf.h to /usr/include and b) running
dh_makeshlibs for the 64bit multilib variant. Any update on this?

Processed: tagging 847095

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 847095 + pending
Bug #847095 [libmongoclient-dev] libmongoclient-dev: Should not conflict with 
transitional mongodb-dev
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847082: marked as done (python-cogent: FTBFS: Fails to build from source with ncbi-data>=6.1.20160908-1)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 15:23:21 +
with message-id 
and subject line Bug#847082: fixed in python-cogent 1.9-7
has caused the Debian Bug report #847082,
regarding python-cogent: FTBFS: Fails to build from source with 
ncbi-data>=6.1.20160908-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cogent
Severity: serious
Tags: patch
Justification: Policy 1.2.3

Hi,

after ncbi-tools6 version 6.1.20160908-1 was in unstable python-cogent
does not build any more since some tests are failing.  In two cases the
build process needed to be interupted and other test cases and up in
failures:

==
FAIL: test_blast_against_new_db (test_app.test_formatdb.FormatDbTests)
Formatdb: blastall against a newly created DB functions as expected
--
Traceback (most recent call last):
  File "/build/python-cogent-1.9/tests/test_app/test_formatdb.py", line 89, in 
test_blast_against_new_db
"Not getting any blast results.")
AssertionError: Not getting any blast results.

==
FAIL: test_build_blast_db_from_fasta_file (test_app.test_formatdb.FormatDbTests)
build_blast_db_from_fasta_file works with open files as input
--
Traceback (most recent call last):
  File "/build/python-cogent-1.9/tests/test_app/test_formatdb.py", line 180, in 
test_build_blast_db_from_fasta_file
len(blastn(self.test_seq,blast_db=blast_db,e_value=0.0)),1)
  File "/build/python-cogent-1.9/cogent/util/unit_test.py", line 316, in 
failUnlessEqual
(msg or 'Got %s, but expected %s' % (`observed`, `expected`))
AssertionError: Got 0, but expected 1

==
FAIL: test_build_blast_db_from_fasta_path (test_app.test_formatdb.FormatDbTests)
build_blast_db_from_fasta_path convenience function works as expected
--
Traceback (most recent call last):
  File "/build/python-cogent-1.9/tests/test_app/test_formatdb.py", line 132, in 
test_build_blast_db_from_fasta_path
len(blastn(self.test_seq,blast_db=blast_db)),1)
  File "/build/python-cogent-1.9/cogent/util/unit_test.py", line 316, in 
failUnlessEqual
(msg or 'Got %s, but expected %s' % (`observed`, `expected`))
AssertionError: Got 0, but expected 1

==
FAIL: test_build_blast_db_from_fasta_path_aln 
(test_app.test_formatdb.FormatDbTests)
build_blast_db_from_fasta_path works with alignment as input
--
Traceback (most recent call last):
  File "/build/python-cogent-1.9/tests/test_app/test_formatdb.py", line 155, in 
test_build_blast_db_from_fasta_path_aln
len(blastn(self.test_seq,blast_db=blast_db,e_value=0.0)),1)
  File "/build/python-cogent-1.9/cogent/util/unit_test.py", line 316, in 
failUnlessEqual
(msg or 'Got %s, but expected %s' % (`observed`, `expected`))
AssertionError: Got 0, but expected 1

==
FAIL: test_build_blast_db_from_seqs (test_app.test_formatdb.FormatDbTests)
build_blast_db_from_seqs convenience function works as expected
--
Traceback (most recent call last):
  File "/build/python-cogent-1.9/tests/test_app/test_formatdb.py", line 107, in 
test_build_blast_db_from_seqs
len(blastn(self.test_seq,blast_db=blast_db)),1)
  File "/build/python-cogent-1.9/cogent/util/unit_test.py", line 316, in 
failUnlessEqual
(msg or 'Got %s, but expected %s' % (`observed`, `expected`))
AssertionError: Got 0, but expected 1

--
Ran 3587 tests in 85.818s


The issue is dealt with in packaging SVN currently but this bug is just
opened to document the issue.

Kind regards

  Andreas.

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/

Bug#844874: marked as done (opensurgsim: googletest related build failure)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 15:22:44 +
with message-id 
and subject line Bug#844874: fixed in opensurgsim 0.7.0-3
has caused the Debian Bug report #844874,
regarding opensurgsim: googletest related build failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
844874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensurgsim
Version: 0.7.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /usr/bin/cc  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -Wall   -Wl,-z,relro 
> -Wl,-z,now  CMakeFiles/cmTC_7d27e.dir/CheckSymbolExists.c.o  -o cmTC_7d27e 
> -rdynamic 
> CMakeFiles/cmTC_7d27e.dir/CheckSymbolExists.c.o: In function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
> reference to `pthread_create'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/opensurgsim_0.7.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: opensurgsim
Source-Version: 0.7.0-3

We believe that the bug you reported is fixed in the latest version of
opensurgsim, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 844...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated opensurgsim 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Dec 2016 08:49:16 +
Source: opensurgsim
Binary: libopensurgsim libopensurgsim-dev opensurgsim-doc
Architecture: source amd64 all
Version: 0.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Ghislain Antony Vaillant 
Description:
 libopensurgsim - Free platform for surgical simulation - runtime
 libopensurgsim-dev - Free platform for surgical simulation - development
 opensurgsim-doc - Free platform for surgical simulation - documentation
Closes: 844874
Changes:
 opensurgsim (0.7.0-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ghislain Antony Vaillant ]
   * Fix FTBFS when building with newest googletest.
 - Build depends on new unified googletest package.
 - Inject path to googlemock via GOOGLEMOCK_DIR.
 - Exclude gtest / gmock artefacts from install.
 Thanks to Lucas Nussbaum for reporting (Closes: #844874)
 .
   [ Andreas Tille ]
   * debhelper 10
   * d/watch: version=4
Checksums-Sha1:
 b92e129334d04c5c567ae2a212ec6278c89b5c53 2329 opensurgsim_0.7.0-3.dsc
 0de54d698c464dac8ac2b25e4b299790c1a12288 9796 opensurgsim_0.7.0-3.debian.tar.xz
 f1e43e3a4ad84cfa408bf72730e534f8e87a51d3 126945628 
libopensurgsim-dbgsym_0.7.0-3_amd64.deb
 3e1dd062e9f44238171e36753cfcb3e825d69ae6 268664 
libopensurgsim-dev_0.7.0-3_amd64.deb
 15329dea4d7482a1d4e32ba188963d01d96764ac 272 
libopensurgsim_0.7.0-3_amd64.deb
 519355ae67f3533f156d36f3a97d6d2b0bcf5fde 3253736 
opensurgsim-doc_0.7.0-3_all.deb
 0f4af8281be7852b675e6665248339ea9ff8be1d 15927 
opensurgsim_0.7.0-3_amd64.buildinfo
Checksums-Sha256:
 435c3a4f0e6069eac28445b38f5fc130376e3f80d74282d473d02901b9bb0656 2329 
opensurgsim_0.7.0-3.dsc
 8615c582c458e224e8230d90e5cc2deecf81e545c07fb83a67d6b5bb7309a2a4 9796 
opensurgsim_0.7.0-3.debian.tar.xz
 078bab750c48b2c5af8e6c4e6228308ba8ebc69f10088c95ce6cb8e7bc749757 126945628 
libopensurgsim-dbgsym_0.7.0-3_amd64.deb
 64f3a5288298d5eaa9901820e1899e1f2b10d7f59cc61a1fcc2327aa99e244b1 268664 
libopensurgsim-dev_0.7.0-3_amd64.deb
 e7f6f00832108e70aef45f595481179eb08012762277f28e67680a9d3c4dc088 272 
lib

Bug#846671: Artemis should adapt to new htsjdk API which has dropped SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))]

[Andrew Page]

Hi Andreas,
Thanks for letting us know.  We are actively trying to hire a Java developer 
who will take over the maintenance and development of Artemis. So unfortunately 
it will be at least a few months before we will have anyone in post to work on 
it.  If you happen to know of anyone looking for a job, please send them our 
way!
Regards,
Andrew



> On 5 Dec 2016, at 14:40, Andreas Tille  wrote:
> 
> Hi,
> 
> after uploading htsjdk 2.7.0 Artemis failed to build from source[1].  I
> relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
> was removed from htsjdk source and assumed that this was by accident.
> However, upstream has dropped this interface intentionally as you can
> read below.  In issue #767[2] an htsjdk author gives advise to use the
> new API version.
> 
> Kind regards
> 
>   Andreas.
> 
> 
> [1] https://bugs.debian.org/846671
> [2] https://github.com/samtools/htsjdk/issues/767
> 
> 
> - Forwarded message from Daniel Gómez-Sánchez  
> -
> 
> Date: Mon, 05 Dec 2016 06:18:16 -0800
> From: Daniel Gómez-Sánchez 
> To: samtools/htsjdk 
> Cc: Andreas Tille , Author 
> Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767)
> 
> The file was removed in #699 because it was deprecated. I guess that either 
> 1) fastqc/artemis should be updated to use the new API version, or 2) the 
> classpath for them in Debian should include an older version.
> 
> -- 
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910
> 
> - End forwarded message -
> 
> -- 
> http://fam-tille.de
> 
> - End forwarded message -
> 
> -- 
> http://fam-tille.de



--
 The Wellcome Trust Sanger Institute is operated by Genome Research
 Limited, a charity registered in England with number 1021457 and a
 company registered in England with number 2742969, whose registered
 office is 215 Euston Road, London, NW1 2BE.

Bug#846816: java.lang.NoSuchFieldError: DLU2

[Eric Peterson]

freeplane/1.5.17 works fine for me

Bug#846708: FastQC should adapt to new htsjdk API which has dropped SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))

[Simon Andrews]

Hi Andreas,

None of the official FastQC releases has ever used htsjdk - we've been using 
the older picard sam.jar API which is substantially different (htsjdk is a 
major rewrite and restructure - it's not just a version update).  Internally we 
have tried the new API, and although it works OK it also imposes a restriction 
on the use of java >=8 which wasn't present in the old version and which would 
break a lot of our existing installations. We're therefore not keen to make 
that change yet - especially since the old API works just fine for all the 
types of data we support.

If you're packaging this for Debian and wanted to move to htkjdk then it's 
pretty trivial to patch this.  It takes a small boilerplate change to the BAM 
opening and reading code in the BAMFile class, and a change to the classpath in 
the launcher script (which I guess you're already doing).  We'll probably move 
to the new API eventually, but at the moment the downsides outweigh the 
benefits for us.

Cheers

Simon.




-Original Message-
From: Andreas Tille [mailto:ti...@debian.org]
Sent: 05 December 2016 14:34
To: Simon Andrews ; 846...@bugs.debian.org
Cc: Vincent Danjean ; Olivier Sallou ; 
Charles Plessy 
Subject: FastQC should adapt to new htsjdk API which has dropped SAMFileReader 
(Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))

Hi Simon,

after uploading htsjdk 2.7.0 FastQC failed to build from source[1].  I relised 
that the file src/main/java/htsjdk/samtools/SAMFileReader.java
was removed from htsjdk source and assumed that this was by accident.
However, upstream has dropped this interface intentionally as you can read 
below.  In issue #767[2] an htsjdk author gives advise to use the new API 
version.

Kind regards

   Andreas.


[1] https://bugs.debian.org/846708
[2] https://github.com/samtools/htsjdk/issues/767


- Forwarded message from Daniel Gómez-Sánchez  
-

Date: Mon, 05 Dec 2016 06:18:16 -0800
From: Daniel Gómez-Sánchez 
To: samtools/htsjdk 
Cc: Andreas Tille , Author 
Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767)

The file was removed in #699 because it was deprecated. I guess that either 1) 
fastqc/artemis should be updated to use the new API version, or 2) the 
classpath for them in Debian should include an older version.

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910

- End forwarded message -

--
http://fam-tille.de
The Babraham Institute, Babraham Research Campus, Cambridge CB22 3AT Registered 
Charity No. 1053902.
The information transmitted in this email is directed only to the addressee. If 
you received this in error, please contact the sender and delete this email 
from your system. The contents of this e-mail are the views of the sender and 
do not necessarily represent the views of the Babraham Institute. Full 
conditions at: www.babraham.ac.uk

Bug#847095: libmongoclient-dev: Should not conflict with transitional mongodb-dev

[Raphaël Hertzog]

Package: libmongoclient-dev
Version: 1.1.2-4
Severity: serious
Tags: patch
Justification: piuparts failure

The package does not migrate to testing due to a piuparts failure:
https://piuparts.debian.org/sid/fail/mongodb-dev_2:1.1.2-4.log

Extract:
0m19.6s ERROR: Command failed (status=100): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpRj5FHY', 'apt-get', '-y', 'install', 
'mongodb-dev=2:1.1.2-4']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   mongodb-dev : Depends: libmongoclient-dev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.


The problem is that the new transitional mongodb-dev depends on
libmongoclient-dev which conflicts with mongodb-dev (this would have
been caught by trying to install the uploaded packages).

Please make the conflict versioned or drop it entirely:
--- a/debian/control
+++ b/debian/control
@@ -27,7 +27,7 @@ Section: libdevel
 Architecture: any
 Multi-Arch: same
 Depends: libmongoclient0 (= ${binary:Version}), ${misc:Depends}
-Conflicts: mongodb-dev
+Conflicts: mongodb-dev (<< 2:1.1.2-1~)
 Description: MongoDB C++ Driver (development)
  This package provides C++ development file to interact with MongoDB.
  This is the legacy C++ driver and currently supports MongoDB 2.4, 2.6,

Please upload a fixed package soon and increase priority to high to speed up
testing migration since we already waited multiple rounds for testing migration.

If you can't upload a fixed package soon, let me know and I can upload an
NMU.

Cheers,
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#846671: Artemis should adapt to new htsjdk API which has dropped SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))]

[Andreas Tille]

Hi,

after uploading htsjdk 2.7.0 Artemis failed to build from source[1].  I
relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
was removed from htsjdk source and assumed that this was by accident.
However, upstream has dropped this interface intentionally as you can
read below.  In issue #767[2] an htsjdk author gives advise to use the
new API version.

Kind regards

   Andreas.


[1] https://bugs.debian.org/846671
[2] https://github.com/samtools/htsjdk/issues/767


- Forwarded message from Daniel Gómez-Sánchez  
-

Date: Mon, 05 Dec 2016 06:18:16 -0800
From: Daniel Gómez-Sánchez 
To: samtools/htsjdk 
Cc: Andreas Tille , Author 
Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767)

The file was removed in #699 because it was deprecated. I guess that either 1) 
fastqc/artemis should be updated to use the new API version, or 2) the 
classpath for them in Debian should include an older version.

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910

- End forwarded message -

-- 
http://fam-tille.de

- End forwarded message -

-- 
http://fam-tille.de

Bug#847074: postfixadmin: Files missing in 3.0.1

[Christoph Martin]

Hi,

thanks for the report. Do you miss anything else that the smarty folder?

Christoph

Am 05.12.2016 um 12:39 schrieb RHaase:
> Package: postfixadmin
> Version: 3.0.1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> after the update from 2.9.3 to 3.0.1 the package was unusable because several
> files are missing like the smarty folder resulting in several reproduceable 
> errors.
> The solution should be to include the missing files from the original source 
> at sourcefourge.
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages postfixadmin depends on:
> ii  apache2 [httpd]2.4.23-8
> ii  dbconfig-common2.0.6
> ii  debconf1.5.59
> ii  mysql-client   5.6.30-1
> ii  php1:7.0+46
> ii  php-imap   1:7.0+46
> ii  php-mbstring   1:7.0+46
> ii  php-mysql  1:7.0+46
> ii  php7.0 [php]   7.0.13-2
> ii  php7.0-cli [php-cli]   7.0.13-2
> ii  php7.0-imap [php-imap] 7.0.13-2
> ii  php7.0-mbstring [php-mbstring] 7.0.13-2
> ii  php7.0-mysql [php-mysqlnd] 7.0.13-2
> ii  postgresql-client  9.6+177
> ii  postgresql-client-9.6 [postgresql-client]  9.6.1-2
> ii  wwwconfig-common   0.3.0
> 
> Versions of packages postfixadmin recommends:
> ii  dovecot-core   1:2.2.26.0-4
> ii  mysql-server   5.6.30-1
> ii  postfix-mysql  3.1.3-4
> ii  zendframework  1.12.20+dfsg-1
> 
> postfixadmin suggests no packages.
> 
> -- Configuration Files:
> /etc/postfixadmin/config.inc.php changed [not included]
> 
> -- debconf information:
>   postfixadmin/app-password-confirm: (password omitted)
>   postfixadmin/password-confirm: (password omitted)
>   postfixadmin/pgsql/admin-pass: (password omitted)
>   postfixadmin/pgsql/app-pass: (password omitted)
>   postfixadmin/mysql/admin-pass: (password omitted)
>   postfixadmin/mysql/app-pass: (password omitted)
> * postfixadmin/mysql/admin-user: debian-sys-maint
>   postfixadmin/internal/skip-preseed: false
>   postfixadmin/passwords-do-not-match:
>   postfixadmin/pgsql/changeconf: false
>   postfixadmin/db/basepath:
>   postfixadmin/missing-db-package-error: abort
>   postfixadmin/dbconfig-upgrade: true
>   postfixadmin/pgsql/admin-user: postgres
>   postfixadmin/remote/newhost:
>   postfixadmin/install-error: abort
>   postfixadmin/mysql/method: Unix socket
>   postfixadmin/upgrade-error: abort
>   postfixadmin/purge: false
> * postfixadmin/dbconfig-install: true
>   postfixadmin/pgsql/manualconf:
>   postfixadmin/remote/port:
>   postfixadmin/upgrade-backup: true
> * postfixadmin/reconfigure-webserver: apache2
> * postfixadmin/dbconfig-remove: true
>   postfixadmin/pgsql/authmethod-user: password
>   postfixadmin/pgsql/no-empty-passwords:
>   postfixadmin/pgsql/authmethod-admin: ident
> * postfixadmin/database-type: mysql
>   postfixadmin/remove-error: abort
>   postfixadmin/db/app-user: postfixadmin@localhost
>   postfixadmin/internal/reconfiguring: false
>   postfixadmin/dbconfig-reinstall: false
>   postfixadmin/remote/host: localhost
>   postfixadmin/db/dbname: postfixadmin
>   postfixadmin/pgsql/method: TCP/IP
> 
<>

signature.asc
Description: OpenPGP digital signature

Bug#846708: FastQC should adapt to new htsjdk API which has dropped SAMFileReader (Was: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767))

[Andreas Tille]

Hi Simon,

after uploading htsjdk 2.7.0 FastQC failed to build from source[1].  I
relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
was removed from htsjdk source and assumed that this was by accident.
However, upstream has dropped this interface intentionally as you can
read below.  In issue #767[2] an htsjdk author gives advise to use the
new API version.

Kind regards

   Andreas.


[1] https://bugs.debian.org/846708
[2] https://github.com/samtools/htsjdk/issues/767


- Forwarded message from Daniel Gómez-Sánchez  
-

Date: Mon, 05 Dec 2016 06:18:16 -0800
From: Daniel Gómez-Sánchez 
To: samtools/htsjdk 
Cc: Andreas Tille , Author 
Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767)

The file was removed in #699 because it was deprecated. I guess that either 1) 
fastqc/artemis should be updated to use the new API version, or 2) the 
classpath for them in Debian should include an older version.

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910

- End forwarded message -

-- 
http://fam-tille.de

Bug#845458: marked as done (python-protobix: FTBFS: error: Could not find suitable distribution for Requirement.parse('simplejson'))

[Debian Bug Tracking System]

Your message dated Mon, 5 Dec 2016 15:06:11 +0100
with message-id <81dced6b-8943-114a-b791-75a0a08b6...@jbfavre.org>
and subject line 
has caused the Debian Bug report #845458,
regarding python-protobix: FTBFS: error: Could not find suitable distribution 
for Requirement.parse('simplejson')
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
845458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-protobix
Version: 1.0.0-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,

python-protobix fails to build from source in unstable/amd64:

  […]

 dh_auto_test -O--buildsystem=pybuild
  dh_auto_test: Compatibility levels before 9 are deprecated (level 8 in use)
  I: pybuild base:184: python2.7 setup.py test 
  running test
  Searching for simplejson
  
  Note: Bypassing https://pypi.python.org/simple/simplejson/ (disallowed host; 
see http://bit.ly/1dg9ijs for details).
  
  Couldn't find index page for 'simplejson' (maybe misspelled?)
  Scanning index of all packages (this may take a while)
  
  Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).
  
  No local packages or working download links found for simplejson
  error: Could not find suitable distribution for 
Requirement.parse('simplejson')
  E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


python-protobix.1.0.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Package: python-protobix
Version: 1.0.0-3

Hello,
Thanks for the bug report.
A new version of the package is available.
Build dependencies have been updated so that package now build succesfully.

Regards,
Jean Baptiste



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 845458 python-protobix/1.0.0-3
Bug #845458 [src:python-protobix] python-protobix: FTBFS: error: Could not find 
suitable distribution for Requirement.parse('simplejson')
Marked as fixed in versions python-protobix/1.0.0-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
845458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#844343: marked as done (golang-github-pierrec-lz4: FTBFS on armhf (TestCopy crashes))

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 13:48:49 +
with message-id 
and subject line Bug#844343: fixed in golang-github-pierrec-lz4 
0.0~git20151216.222ab1f-2
has caused the Debian Bug report #844343,
regarding golang-github-pierrec-lz4: FTBFS on armhf (TestCopy crashes)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
844343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-pierrec-lz4
Version: 0.0~git20151216.222ab1f-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

The build of this package break in the reproducible build environment during the
2nd build on armhf [1]:


=== RUN   TestCopy
SIGQUIT: quit
PC=0x709f8 m=0

goroutine 0 [idle]:
runtime.futex(0x1c48fc, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1dba0, 0x0, 0x0, 0x0, ...)
/usr/lib/go-1.7/src/runtime/sys_linux_arm.s:247 +0x20
runtime.futexsleep(0x1c48fc, 0x0, 0x, 0x)
/usr/lib/go-1.7/src/runtime/os_linux.go:45 +0x68
runtime.notesleep(0x1c48fc)
/usr/lib/go-1.7/src/runtime/lock_futex.go:145 +0xa4
runtime.stopm()
/usr/lib/go-1.7/src/runtime/proc.go:1594 +0x100
runtime.findrunnable(0x1051f400, 0x0)
/usr/lib/go-1.7/src/runtime/proc.go:2021 +0x758
runtime.schedule()
/usr/lib/go-1.7/src/runtime/proc.go:2120 +0x26c
runtime.goexit0(0x117eb770)
/usr/lib/go-1.7/src/runtime/proc.go:2257 +0x1d0
runtime.mcall(0x1c4600)
/usr/lib/go-1.7/src/runtime/asm_arm.s:183 +0x5c

goroutine 1 [chan receive, 3 minutes]:
testing.(*T).Run(0x10588000, 0x14906a, 0x8, 0x15c6f4, 0xa1901)
/usr/lib/go-1.7/src/testing/testing.go:647 +0x324
testing.RunTests.func1(0x10590100)
/usr/lib/go-1.7/src/testing/testing.go:793 +0xb8
testing.tRunner(0x10590100, 0x1053ced4)
/usr/lib/go-1.7/src/testing/testing.go:610 +0xa4
testing.RunTests(0x15c714, 0x1c3120, 0x8, 0x8, 0xa1)
/usr/lib/go-1.7/src/testing/testing.go:799 +0x388
testing.(*M).Run(0x1053cf7c, 0x40)
/usr/lib/go-1.7/src/testing/testing.go:743 +0x8c
main.main()
github.com/pierrec/lz4/_test/_testmain.go:76 +0x118

goroutine 17422 [semacquire]:
sync.runtime_Semacquire(0x10516080)
/usr/lib/go-1.7/src/runtime/sema.go:47 +0x24
sync.(*WaitGroup).Wait(0x10516074)
/usr/lib/go-1.7/src/sync/waitgroup.go:131 +0xc0
github.com/pierrec/lz4.(*Writer).Write(0x10516050, 0x128c, 0x10, 
0x10, 0x0, 0x0, 0x0)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:183
 +0x9b0
github.com/pierrec/lz4.(*Writer).ReadFrom(0x10516050, 0x1b2770, 0x10570128, 
0x20, 0x0, 0x0, 0x0)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:357
 +0x1a0
io.copyBuffer(0x1b2758, 0x10516050, 0x1b2770, 0x10570128, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, ...)
/usr/lib/go-1.7/src/io/io.go:384 +0x124
io.Copy(0x1b2758, 0x10516050, 0x1b2770, 0x10570128, 0x10, 0x148670, 0x0, 0x0)
/usr/lib/go-1.7/src/io/io.go:360 +0x64
github.com/pierrec/lz4_test.TestCopy(0x10588000)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/lz4_test.go:493
 +0x370
testing.tRunner(0x10588000, 0x15c6f4)
/usr/lib/go-1.7/src/testing/testing.go:610 +0xa4
created by testing.(*T).Run
/usr/lib/go-1.7/src/testing/testing.go:646 +0x304

goroutine 25094 [runnable]:
github.com/pierrec/lz4.(*Writer).Write.func1(0x10516050, 0x128c, 0x10, 
0x10)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:120
created by github.com/pierrec/lz4.(*Writer).Write

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:123
 +0xf8

goroutine 25098 [runnable]:
github.com/pierrec/lz4.CompressBlock(0x1298, 0x4, 0x4, 0x112a8000, 
0x4, 0x4, 0x0, 0x4, 0x6fe08, 0x10516074)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/block.go:116
github.com/pierrec/lz4.(*Writer).compressBlock(0x10516050, 0x116ea084)

/build/golang-github-pierrec-lz4-0.0~git20151216.222ab1f/obj-arm-linux-gnueabihf/src/github.com/pierrec/lz4/writer.go:238
 +0x310
created by github.com/pierrec/lz4.(*Writer).Write

Bug#759825: audtty: FTBFS: main.c:20:31: fatal error: audacious/audctrl.h: No such file or directory

[Fernando Seiti Furusato]

Hello, Chris.

Do you still plan to do this upload?
I can send an NMU, but I am not a DD, so the process will be slower.

Thanks!

-- 
Fernando Seiti Furusato
IBM Linux Technology Center





signature.asc
Description: OpenPGP digital signature

Bug#844121: CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are *NOT* valid bug reports

[Ondřej Surý]

Sam and others,

I most deeply apologize, you are right in your assessment.

I somehow missed the extra four additional sanity checks at the
beginning of the getudp() function that seems to catch the error
conditions on those input buffers.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Sat, Dec 3, 2016, at 16:47, Sam Trenholme wrote:
> CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are *NOT* valid bug
> reports.
> 
> Here’s the deal: The reporter had to patch MaraDNS before he was able
> to crash her.
> 
> The patch, however, treats MaraDNS’ special buffer-overflow-resistant
> “js_string” as if it were an ordinary string — but it’s not. Here’s
> the offending code patched in to MaraDNS from the reporter’s “bug
> report”:
> 
> sock_num = read(0, incoming, 512);
> 
> As per the man page for read:
> 
> ssize_t read(int fd, void *buf, size_t count);
> 
> DESCRIPTION
>read()  attempts to read up to count bytes from file descriptor fd
>into
>the buffer starting at buf.
> 
> However, incoming is not a raw string buffer: It’s a special js_string
> object which MaraDNS uses to be buffer overflow resistant, as can be
> seen here in server/MaraDNS.c:
> 
> int main(int argc, char **argv) {
> 
> js_string *mararc_loc = 0, *errors = 0,
>   *bind_address = 0, *ipv6_bind_address = 0,
>   *csv2_synthip_address = 0,
>   *ipv4_bind_address = 0, *incoming = 0,
>   *uncomp = 0, *verbstr = 0;
> 
> The js_string structure (I guess I would call it an object here in
> 2016) is defined in libs/JsStr.h:
> 
> typedef struct {
> unsigned char *string;   /* Actual physical string */
> unsigned int unit_size;  /* The size of a single character in the
> string */
> unsigned int unit_count; /* The length of the string, in units */
> unsigned int max_count;  /* The maximum allowable size of the string,
>also in units */
> int encoding;   /* The type of language/encoding the string is in */
> int is_good;/* This is checked to make sure the data structure is
>sane */
> } js_string;
> 
> Point being, if we patch MaraDNS to treat this structure as a raw
> buffer instead of a structure, we will be able to crash MaraDNS — but
> that doesn’t mean we have found a UDP packet of death which will crash
> unpatched MaraDNS 2.0.13.
> 
> I appreciate that people are performing security research with
> MaraDNS, and the fact that researchers need to resort to patching
> MaraDNS before crashing her indicates that, a decade and a half later
> MaraDNS is still a usable DNS server with a strong security record.

Bug#836770: Bug fix

[Erez]

The parsing of the "mount -l" was wrong.
No break was on finding the proper line.
Only works if the "efivarfs" line was last.

diff -ur efitools-1.4.2/lib/kernel_efivars.c
efitools-1.4.2/lib/kernel_efivars.c---
efitools-1.4.2/lib/kernel_efivars.c+++
efitools-1.4.2/lib/kernel_efivars.c@@ -44,7 +44,6 @@
/* hopefully stderr said what was wrong */
exit(1);
fd = open(fname, O_RDONLY);-   unlink(fname);
if (fd < 0) {
fprintf(stderr, "Failed to open output of %s\n", cmdline);
exit(1);@@ -60,6 +59,7 @@
buf = malloc(st.st_size);
read(fd, buf, st.st_size);
close(fd);+   unlink(fname);

char *ptr = buf;
char path[512], type[512];@@ -68,15 +68,14 @@

sscanf(ptr, "%*s on %s type %s %*s\n%n", path, type, &count);
ptr += count;-   if (strcmp(type, "efivarfs") != 0)-
continue;-   }-   if (strcmp(type, "efivarfs") != 0) {-
fprintf(stderr, "No efivarfs filesystem is mounted\n");-
exit(1);+   if (strcmp(type, "efivarfs") == 0)+   {+
kernel_efi_path = strdup(path);+   return;+   }
}-   kernel_efi_path = malloc(strlen(path) + 1);-
strcpy(kernel_efi_path, path);+   fprintf(stderr, "No efivarfs
filesystem is mounted\n");+   exit(1);
 }

 int

Bug#845638: Compatibility with xserver 1.19 / xorg-video-abi-23

[Luca Boccassi]

On Mon, 2016-12-05 at 09:48 +0100, Emilio Pozuelo Monfort wrote:
> On Fri, 25 Nov 2016 14:30:22 + Luca Boccassi  
> wrote:
> > Control: forcemerge 845638 845000
> > 
> > On Fri, 25 Nov 2016 14:01:20 +0100 Andreas Boll 
> >  wrote:
> > > Source: nvidia-graphics-drivers
> > > Version: 367.57-2
> > > Severity: serious
> > > Control: block 843265 by -1
> > > 
> > > Dear Maintainer,
> > > 
> > > your package is part of the ongoing xserver 1.19 transition #843265.
> > > Please make your xorg driver package compatible with xserver 1.19 (i.e.
> > > supporting xorg-video-abi-23).
> > > 
> > > 
> > > Thanks,
> > > Andreas
> > 
> > Hello,
> > 
> > Version 375.20 supports ABI 23 and it's ready in SVN (branches/375),
> > needs some reviewing and testing.
> > 
> > Andreas, we'd need to push 370 to unstable first to follow the workflow
> > I guess. Do you have time to have a look?
> 
> Why not skip that and just upload 375 from experimental to unstable?
> 
> Emilio

Because 375.20 introduces more changes than the Xorg ABI compatibility,
most importantly the glvnd-rized libEGL, so we need to introduce support
for that and test it.

See existing thread on the ML:

https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-November/013663.html

Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#845366: marked as done (ocaml-schroedinger: removal of libschroedinger)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 13:11:19 +
with message-id 
and subject line Bug#846943: Removed package(s) from unstable
has caused the Debian Bug report #845366,
regarding ocaml-schroedinger: removal of libschroedinger
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
845366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ocaml-schroedinger
Version: 0.1.0-3
Severity: serious
Control: block 845037 by -1

Dear Maintainer,

libschroedinger contains various possibly security relevant bugs and is
no longer maintained upstream. Therefore it has been decided to remove
it from Debian. (see bug #845037)

Before it can be removed, all reverse dependencies have to stop using it.

Since this package is not useful without libschroedinger, the plan is
to remove it along with that library. This is just an advance notice.

Best regards,
Andreas
--- End Message ---
--- Begin Message ---
Version: 0.1.0-3+rm

Dear submitter,

as the package ocaml-schroedinger has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/846943

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#847084: package builds with -march=native

[Matthias Klose]

Package: src:rapmap
Version: 0.4.0+dfsg-1
Severity: serious
Tags: sid stretch

The package builds with -march=native, not allowed by Debian policy.

Bug#846353: FTBFS: ERROR: Test "ruby2.3" failed. Exiting.

[Gilles Filippini]

Sebastiaan Couwenberg a écrit le 03/12/2016 à 19:33 :
> Control: tags -1 pending
> 
> On 12/03/2016 07:19 PM, Gilles Filippini wrote:
>> I've filed #846853 against src:hdf-eos5. There are issues in
>> ruby-hdfeos5 as well. See the attached patch.
>>
>> With these fixes the ruby-hdfeos5 testsuite passes on 64 bit and 32 bit
>> arches.
> 
> Thanks for the patch! I've applied it in git, and will do a team upload
> after hdf-eos5 is fixed, unless Youhei beats me to it.

Fixed hdf-eos5 is now in unstable.

Thanks,

_g.




signature.asc
Description: OpenPGP digital signature

Bug#838944: marked as done (vimhelp-de: depends on vim 7.4 but unstable has vim 8.0)

[Debian Bug Tracking System]

Your message dated Mon, 05 Dec 2016 13:04:10 +
with message-id 
and subject line Bug#846636: Removed package(s) from unstable
has caused the Debian Bug report #838944,
regarding vimhelp-de: depends on vim 7.4 but unstable has vim 8.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
838944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vimhelp-de
Version: 7.4.130818-2
Severity: serious

SSIA

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 7.4.130818-2+rm

Dear submitter,

as the package vimhelp-de has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/846636

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#847083: build accesses the network during the build

[Matthias Klose]

Package: src:rapmap
Version: 0.4.0+dfsg-1
Severity: serious
Tags: sid stretch

According to the build log, the package tries to download components during the
build.

https://buildd.debian.org/status/fetch.php?pkg=rapmap&arch=kfreebsd-amd64&ver=0.4.0%2Bdfsg-1&stamp=1476727945

Please allow the package to build on the buildds on amd64 for a proper build.

Processed: found 847055 in 1.3.16-1.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 847055 1.3.16-1.1
Bug #847055 [src:graphicsmagick] graphicsmagick: CVE-2016-9830
Bug #847072 [src:graphicsmagick] graphicsmagick: CVE-2016-9830
Marked as found in versions graphicsmagick/1.3.16-1.1.
Marked as found in versions graphicsmagick/1.3.16-1.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847055
847072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Merge + reassign

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 846708 htsjdk
Bug #846708 [src:fastqc] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Bug reassigned from package 'src:fastqc' to 'htsjdk'.
No longer marked as found in versions fastqc/0.11.5+dfsg-5.
Ignoring request to alter fixed versions of bug #846708 to the same values 
previously set
> reassign 846671 htsjdk
Bug #846671 [src:artemis] artemis: FTBFS: BamView.java:115: error: cannot find 
symbol
Bug reassigned from package 'src:artemis' to 'htsjdk'.
No longer marked as found in versions artemis/16.0.0+dfsg-5.
Ignoring request to alter fixed versions of bug #846671 to the same values 
previously set
> merge 846708 846671
Bug #846708 [htsjdk] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Bug #846671 [htsjdk] artemis: FTBFS: BamView.java:115: error: cannot find symbol
Merged 846671 846708
> tags 846708 upstream,patch,pending
Bug #846708 [htsjdk] fastqc: FTBFS: [javac] 
/<>/fastqc-0.11.5+dfsg/uk/ac/babraham/FastQC/Sequence/BAMFile.java:30:
 error: cannot find symbol
Bug #846671 [htsjdk] artemis: FTBFS: BamView.java:115: error: cannot find symbol
Added tag(s) pending, upstream, and patch.
Added tag(s) pending, upstream, and patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
846671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846671
846708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems