Bug#800891: Please adjust the licensing of afex

[Andreas Tille]

Hi Henrik,

I'd like to repeat that it would be perfectly simple to just upload the
current version with a fixed license - at least I do not see any reason
why it should be that hard.

Kind regards

   Andreas.

On Sun, Dec 11, 2016 at 10:43:20PM +0100, Henrik Singmann wrote:
> Hi Andreas,
> I am sorry for the delay. I guess you will have to go ahead without it for
> the next version.
> 
> I haven't managed to find the time to work on it yet. I will before the end
> of the year, but don't know when. Sorry.
> 
> Regards,
> Henrik
> 
> 2016-12-11 16:38 GMT+01:00 Andreas Tille :
> 
> > Hi Henrik,
> >
> > any news about a new version with fixed license.  As I said the issue is
> > a bit dense if we want to reach the next Debian stable version.
> >
> > Kind regards
> >
> >  Andreas.
> >
> > On Wed, Nov 16, 2016 at 09:37:57AM +0100, Andreas Tille wrote:
> > > Hi Henrik,
> > >
> > > On Tue, Nov 15, 2016 at 08:57:20PM +0100, Henrik Singmann wrote:
> > > > Hi Andreas, (this time with list in CC)
> > > >
> > > > Thanks for warning me. And no problem. I will change to GPL2 in the
> > next
> > > > release version. Can you give me some time to implement these changes
> > and
> > > > others I have planned for the next release? Let's say 4 weeks?
> > >
> > > As I said 4 weeks is a bit dense.  If you really manage in 4 weeks it
> > > might make it.  However, it is not my power to push any package after
> > > the freeze.
> > >
> > > Kind regards
> > >
> > >  Andreas.
> > >
> > > --
> > > http://fam-tille.de
> >
> > --
> > http://fam-tille.de
> >
> 
> 
> 
> -- 
> Dr. Henrik Singmann
> Postdoc
> Universität Zürich, Schweiz
> http://singmann.org

-- 
http://fam-tille.de

Bug#847831: botch FTBFS

[Johannes Schauer]

Package: botch
Version: 0.20-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

botch currently FTBFS because its tests fail. More precisely, the
"selfcontained" tests fail. This seems to happen because the output of
botch-optuniv changed (opt-packages differs). That in turn then results
in differences in the rest of the test. The only difference in
dependencies seems to be that gringo was upgraded from 4.5.4-4 to
5.1.0-1. Gringo is used by botch-optuniv so this explains the problem.

debci log: https://ci.debian.net/packages/b/botch/unstable/amd64/

Thanks!

cheers, josch

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]

Hi,
I have uploaded biojava, do you still need i have a look? Seems sasha did
the job.. :-)

Olivier

Le lun. 5 déc. 2016 22:24, olivier sallou  a
écrit :

> 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#847747: marked as done (latest version breaks polkitd)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2016 06:33:32 +
with message-id 
and subject line Bug#847747: fixed in mozjs 1.8.5-1.0.0+dfsg-6
has caused the Debian Bug report #847747,
regarding latest version breaks polkitd
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.)


-- 
847747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmozjs185-1.0
Version: 1.8.5-1.0.0+dfsg-5.2
Severity: grave

Version 1.8.5-1.0.0+dfsg-5.2 breaks polkitd:

Dec 10 23:31:07 macarthur kernel: traps: polkitd[577] general protection
ip:7fcce2bcdbd1 sp:7ffe4cf4e220 error:0 in
libmozjs185.so.1.0.0[7fcce2ace000+358000]
Dec 10 23:31:07 macarthur systemd[1]: polkit.service: Main process exited,
code=killed, status=11/SEGV
Dec 10 23:31:07 macarthur systemd[1]: polkit.service: Unit entered failed
state.
Dec 10 23:31:07 macarthur systemd[1]: polkit.service: Failed with result
'signal'.

Symptoms:
- on system startup: a long (minutes) pause between systemd reports
  "Starting User Manager for UID 131" (131 is Debian-gdm) and the
  gdm login screen actually appears
- after login, another long pause before my desktop shows (systemd
  starts another "user" session, this time for my account)
- the top right menu on the Gnome desktop is missing the "shutdown"
  button (though I have the necessary permission)

Downgrading to 1.8.5-1.0.0+dfsg-5 makes the problems go away.


Cheers, Roderich



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

Kernel: Linux 4.8.14 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: mozjs
Source-Version: 1.8.5-1.0.0+dfsg-6

We believe that the bug you reported is fixed in the latest version of
mozjs, 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.
Ben Hutchings  (supplier of updated mozjs 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, 12 Dec 2016 06:01:03 +
Source: mozjs
Binary: libmozjs185-1.0 libmozjs185-dev
Architecture: source
Version: 1.8.5-1.0.0+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Ben Hutchings 
Description:
 libmozjs185-1.0 - SpiderMonkey JavaScript engine
 libmozjs185-dev - SpiderMonkey JavaScript library - development headers
Closes: 847747
Changes:
 mozjs (1.8.5-1.0.0+dfsg-6) unstable; urgency=medium
 .
   * QA upload
   * Remove Modify_tagged_pointer_structure_js1.8.5.patch, which causes an
 ABI change and would therefore require a soname bump (Closes: #847747)
Checksums-Sha1:
 af28434e46d48dfee442d87efceb22f63ecfd4c2 2119 mozjs_1.8.5-1.0.0+dfsg-6.dsc
 73987d942f6fa7bcd5726097bd1072960afa3111 52724 
mozjs_1.8.5-1.0.0+dfsg-6.debian.tar.xz
Checksums-Sha256:
 bbe03c6543cd71c6446024ca85460a4df2b96b8b73522f613a50e93110d89e35 2119 
mozjs_1.8.5-1.0.0+dfsg-6.dsc
 103d1330598cd1b61d29034af5562d4430f98f898b3c4e06692655fd00a4c2cb 52724 
mozjs_1.8.5-1.0.0+dfsg-6.debian.tar.xz
Files:
 334412f63b4e861cce2ae13eaa8dbcaa 2119 libs extra mozjs_1.8.5-1.0.0+dfsg-6.dsc
 ecfac0db2bca0153c3804a885940c36d 52724 libs extra 
mozjs_1.8.5-1.0.0+dfsg-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlhOPtEACgkQ57/I7JWG
EQlIChAAmcL7RRVCxEOubk48p83uw0sihxwGswrDjT2lpBRSsftpfli+yo7inZ+Q
2LE6rlCyYCkqUigOynXoIfUXWvBSsyjCoOJyvH6HkUG5QTj9YSf9Luzq942Ws64m
E5rjwTMshy+z0VlkVbZ8iQpdGpezRPTmz6L0BkhpA4iQ1zXdsHTtPPCRtBOebUbd
lTq3yAgTxL5xxIDKL96npqV67ApBW4y1y0c6DD9qTfInVj255f9dcSjZfpE+AluH
OR6OCH3CCWjccRd3wiSk35SqeW99L7VIyBKGquXR4w0TXumLI5OD+FigSLlDgTP6
WkG1TWJ+Z+YRyV3sD49KZ536Ci6wtcWnmWsN57KkYfR8x8gaLXxYYuDhB3iu9wUq
czD8pRvHZE9mHIgN8BxwSyj9WxSBkOoP1o5TC7nzuS3pbT7jWCbeyqHudo8FOvmL

Processed: reopening 839048

[Debian Bug Tracking System]

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

> reopen 839048
Bug #839048 {Done: John Paul Adrian Glaubitz } 
[libmozjs185-1.0] couchjs crashes on ARM64
'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 mozjs/1.8.5-1.0.0+dfsg-5.1.
> thanks
Stopping processing here.

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

Bug#839048: js24 crashes on ARM64

[Ben Hutchings]

On Mon, 2016-12-12 at 05:59 +, Ben Hutchings wrote:
> On Mon, 2016-12-12 at 13:51 +0800, Zheng Xu wrote:
[...]
> > mozjs1.8.5 -- The patch is different with the upstream one. Because in the
> > old js, there might be objects pass from C allocation, only modify the heap
> > doesn't work. The patch changes the tag bits. And ABI is changed also. So
> > it will require to rebuild all the packages which depends on mozjs1.8.5
> 
> That's not an option as no library ABI changes can go into testing
> before the release.

So I've reverted the change.  It can be fixed after stretch by changing
the tag bits and also bumping the soname at the same time.

Kernel packages for arm64 with 48-bit user virtual addresses will have
an unversioned Breaks relation to libmozjs185-1.0, since the fixed
version must have a new package name.

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.


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

Bug#839048: js24 crashes on ARM64

[Ben Hutchings]

On Mon, 2016-12-12 at 13:51 +0800, Zheng Xu wrote:
> Sorry for making people confused. The patch I uploaded for mozj24 and
> mozjs1.8.5 are different.
> mozjs24 -- The patch is the back port version of the upstream one. It
> doesn't change the ABI.

Unfortunately, the patch that was applied does change the ABI.

> mozjs1.8.5 -- The patch is different with the upstream one. Because in the
> old js, there might be objects pass from C allocation, only modify the heap
> doesn't work. The patch changes the tag bits. And ABI is changed also. So
> it will require to rebuild all the packages which depends on mozjs1.8.5

That's not an option as no library ABI changes can go into testing
before the release.

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.



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

Bug#839048: js24 crashes on ARM64

[Zheng Xu]

Sorry for making people confused. The patch I uploaded for mozj24 and
mozjs1.8.5 are different.
mozjs24 -- The patch is the back port version of the upstream one. It
doesn't change the ABI.
mozjs1.8.5 -- The patch is different with the upstream one. Because in the
old js, there might be objects pass from C allocation, only modify the heap
doesn't work. The patch changes the tag bits. And ABI is changed also. So
it will require to rebuild all the packages which depends on mozjs1.8.5

On 11 December 2016 at 11:08, Ben Hutchings  wrote:

> On Sun, 2016-12-11 at 03:24 +0100, John Paul Adrian Glaubitz wrote:
> > On 12/11/2016 03:13 AM, Ben Hutchings wrote:
> > > Looking at the patch that was added in -4: WTF?  It changes the library
> > > ABI, but you didn't bump the soname.  Of course that breaks clients!
> >
> > That's odd. Why does it break the ABI though? From what I can see, the
> > upstream change just forces the JS memory allocator to avoid certain
> > regions in memory [1].
>
> That's not the one that got backported though.
>
> > > libmozjs185 appears to have been broken in the same way.
> >
> > Is it? As far as I know, the patch was not merged to src:mozjs.
>
> You called the patch Modify_tagged_pointer_structure_js1.8.5.patch
>
> In mozjs24 it's called Manually_mmap_on_arm64.patch but it's not what
> the name says, it's changing the number of tag bits.
>
> Ben.
>
> > > At this point in the release cycle no more library transitions are
> > > allowed, so libmozjs has to be fixed with a kluge like the patch that
> > > Zheng Xu sent, not the upstream change.
> >
> > I agree. But I also think that the ABI break was not intentional.
> >
> > Adrian
> >
> > > [1] https://hg.mozilla.org/mozilla-central/rev/dfaafbaaa291
> --
> Ben Hutchings
> Any sufficiently advanced bug is indistinguishable from a feature.
>

Processed: affects 846961

[Debian Bug Tracking System]

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

> affects 846961 diaspora
Bug #846961 {Done: Pirate Praveen } [ruby-jquery-ui-rails] 
generate app directory using rake task
Added indication that 846961 affects diaspora
> thanks
Stopping processing here.

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

Processed: retitle 845258 to mcabber: CVE-2016-9928: remote attacker can modify the roster and intercept messages via a crafted roster-push IQ stanza

[Debian Bug Tracking System]

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

> retitle 845258 mcabber: CVE-2016-9928: remote attacker can modify the roster 
> and intercept messages via a crafted roster-push IQ stanza
Bug #845258 [src:mcabber] mcabber: remote attacker can modify the roster and 
intercept messages via a crafted roster-push IQ stanza
Changed Bug title to 'mcabber: CVE-2016-9928: remote attacker can modify the 
roster and intercept messages via a crafted roster-push IQ stanza' from 
'mcabber: remote attacker can modify the roster and intercept messages via a 
crafted roster-push IQ stanza'.
> thanks
Stopping processing here.

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

Bug#842145: marked as done (usrmerge: fails on nfsroot systems)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2016 04:49:03 +
with message-id 
and subject line Bug#842145: fixed in usrmerge 13
has caused the Debian Bug report #842145,
regarding usrmerge: fails on nfsroot systems
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.)


-- 
842145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usrmerge
Version: 12
Severity: important

Hi,

Today I upgraded one of my mipsel machines to stretch. The machine is
an Ubiquiti ER8 router and because it doesn't have a hard disk
controller, it's booted using nfsroot.

After upgrading, I tried to install usrmerge which gave:

---
Setting up usrmerge (12) ...

FATAL ERROR:

Can't rename('/sbin/.nfs003efaa00995~~tmp~usrmerge~~', 
'/sbin/.nfs003efaa00995'): Device or resource busy at 
/usr/lib/convert-usrmerge line 98
   
You can try correcting the errors reported and running again
 
/usr/lib/convert-usrmerge until it will complete without errors.  
Do not install or update other Debian packages until the program  
has been run successfully. 

 
dpkg: error processing package usrmerge (--configure):
 subprocess installed post-installation script returned error exit status 1 
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:   
 usrmerge   
E: Sub-process /usr/bin/dpkg returned an error code (1)
---

I then had to convert the machine to usrmerge the painful way. A
warning message for anyone using nfsroot would be nice.

I was thinking that it may be possible to fix this if the machine was
rebooted halfway though (after all the files have been moved, but all
the file symlinks still present), but I don't know if that would work.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: usrmerge
Source-Version: 13

We believe that the bug you reported is fixed in the latest version of
usrmerge, 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 842...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marco d'Itri  (supplier of updated usrmerge 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, 12 Dec 2016 05:23:20 +0100
Source: usrmerge
Binary: usrmerge
Architecture: source all
Version: 13
Distribution: unstable
Urgency: medium
Maintainer: Marco d'Itri 
Changed-By: Marco d'Itri 
Description:
 usrmerge   - Convert the system to the merged /usr directories scheme
Closes: 842145
Changes:
 usrmerge (13) unstable; urgency=medium
 .
   * Do not run convert-usrmerge on NFS systems. (Closes: #842145)
   * Added a version to the conflict with elvis-tiny (see #813857).
   * Added a versioned conflict with libjson-c-dev (see #843145).
Checksums-Sha1:
 1899442f27b35df746507457a9822f5d3bda5399 1338 usrmerge_13.dsc
 8847cc59c865cc237ca57a994ef9130cfce99df5 17668 usrmerge_13.tar.xz
 35ecd8ea4dac44ec8bf522f8f2d33bd7876860b2 12030 usrmerge_13_all.deb
 ef829a29c475230f06dc59c7eaa87da13b9942f1 4282 usrmerge_13_i386.buildinfo
Checksums-Sha256:
 9bfe0c379df5b33d98a6181d8fd61d2de7822685fcd6f4c3a8a304846bea03c2 1338 
usrmerge_13.dsc
 385a60686ad54d97750d1e5b4048d0e9fb2c3fad5780f8acc3d7160c569a9ac4 17668 
usrmerge_13.tar.xz
 80bda966002289593f19bd9123b1c3f87557ca0c5e8022893ae2de5472ff0125 12030 
usrmerge_13_all.deb
 073afc33a2a59bded68751cd31b2149d91f43acbbba63e7619a533997671b4ba 4282 
usrmerge_13_i386.buildinfo
Files:
 

Processed: Proper version tracking

[Debian Bug Tracking System]

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

> fixed 843313 2.7.0-2
Bug #843313 {Done: Hilko Bengen } [ocaml-ipaddr] FTBFS: 
libsexplib-camlp4-dev is no longer available
There is no source info for the package 'ocaml-ipaddr' at version '2.7.0-2' 
with architecture ''
Unable to make a source version for version '2.7.0-2'
Marked as fixed in versions 2.7.0-2.
> thanks
Stopping processing here.

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

Bug#844220: exim4: fails to install: user mail was not found

[Marco d'Itri]

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

On Nov 16, Holger Levsen  wrote:

> sadly I dont have much time atm to try to reproduce manually, so if
> noone else can I would suggest downgrading this bug to normal and
> unreproducible and maybe I'll find the time to properly debug or the bug
> comes back when /usr-merged comes back as a default…
Unreproducible for me too:

# debootstrap --merged-usr --variant=minbase --include=exim4-config stretch 
root http://.../debian/
# ls -l
totale 4
drwxr-xr-x 17 root root 4096 Dec 12 04:48 root/
# chroot root/ /bin/sh -c 'getent passwd mail'
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
#

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Processed: Re: Bug#844220: exim4: fails to install: user mail was not found

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #844220 [usrmerge] exim4: fails to install: user mail was not found
Severity set to 'normal' from 'serious'
> tag -1 unreproducible
Bug #844220 [usrmerge] exim4: fails to install: user mail was not found
Added tag(s) unreproducible.

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

Processed: severity of 810499 is important, tagging 810499

[Debian Bug Tracking System]

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

> severity 810499 important
Bug #810499 [usrmerge] usrmerge: Confuses dpkg-shlibdeps
Severity set to 'important' from 'serious'
> tags 810499 - unreproducible
Bug #810499 [usrmerge] usrmerge: Confuses dpkg-shlibdeps
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#847821: qt3d-opensource-src: FTBFS: tst_QAspectEngine times out (hangs?)

[Aaron M. Ucko]

Source: qt3d-opensource-src
Version: 5.7.1~20161122+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of the latest qt3d-opensource-src release failed on several
architectures with tst_QAspectEngine timeouts, perhaps due to
intermittent hangs.  Specifically, these timeouts affected
shouldNotCrashOnShutdownWhenComponentIsCreatedWithParentBeforeItsEntity
on i386, mips, and the non-release architecture hppa, and
setRootEntity on s390x and the non-release architecture hurd-i386.

Could you please take a look, and ensure that all tests reliably succeed?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#811894: marked as done (tvtime: FTBFS with GCC 6: inconsistent user-defined literal suffixes)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2016 03:06:55 +
with message-id 
and subject line Bug#811894: fixed in tvtime 1.0.2-15
has caused the Debian Bug report #811894,
regarding tvtime: FTBFS with GCC 6: inconsistent user-defined literal suffixes
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.)


-- 
811894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tvtime
Version: 1.0.2-14
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-literal-suffixes

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
...
> if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -MT greedyh.o 
> -MD -MP -MF ".deps/greedyh.Tpo" \
>   -c -o greedyh.o `test -f '../plugins/greedyh.cpp' || echo 
> './'`../plugins/greedyh.cpp; \
> then mv -f ".deps/greedyh.Tpo" ".deps/greedyh.Po"; \
> else rm -f ".deps/greedyh.Tpo"; exit 1; \
> fi
> In file included from ../plugins/greedyh.cpp:35:0:
> ../plugins/greedyh.asm:94:11: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>MOVX" %%"XBX", %[oldbx]\n\t"
>^
> 
> ../plugins/greedyh.asm:96:18: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   MOVX"  %[L1],  %%"XAX"\n\t"
>   ^
> 
> ../plugins/greedyh.asm:97:18: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   LEAX"  8(%%"XAX"), %%"XBX"\n\t"// next qword needed by 
> DJR
>   ^
> 
> ../plugins/greedyh.asm:97:29: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   LEAX"  8(%%"XAX"), %%"XBX"\n\t"// next qword needed by 
> DJR
>  ^
> 
> ../plugins/greedyh.asm:98:18: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   MOVX"  %[L3],  %%"XCX"\n\t"
>   ^
> 
> ../plugins/greedyh.asm:99:18: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   SUBX"  %%"XAX",%%"XCX"\n\t"// carry L3 addr as an 
> offset
>   ^
> 
> ../plugins/greedyh.asm:99:27: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   SUBX"  %%"XAX",%%"XCX"\n\t"// carry L3 addr as an 
> offset
>^
> 
> ../plugins/greedyh.asm:100:18: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   MOVX"  %[L2P], %%"XDX"\n\t"
>   ^
> 
> ../plugins/greedyh.asm:101:18: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   MOVX"  %[L2],  %%"XSI"\n\t"
>   ^
> 
> ../plugins/greedyh.asm:102:18: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   MOVX"  %[Dest],%%"XDI"\n\t"// DL1 if Odd or DL2 if 
> Even
>   ^
> 
> ../plugins/greedyh.asm:107:14: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   "movq  (%%"XSI"),  %%mm0\n\t"  // L2 - the newest weave 
> pixel value
>   ^
> 
> ../plugins/greedyh.asm:108:14: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   "movq  (%%"XAX"),  %%mm1\n\t"  // L1 - the top pixel
>   ^
> 
> ../plugins/greedyh.asm:109:14: warning: invalid suffix on literal; C++11 
> requires a space between literal and string macro [-Wliteral-suffix]
>   "movq  (%%"XDX"),  %%mm2\n\t"  // L2P - 

Bug#828586: marked as done (up-imapproxy: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2016 03:07:05 +
with message-id 
and subject line Bug#828586: fixed in up-imapproxy 1.2.8~svn20161210-1
has caused the Debian Bug report #828586,
regarding up-imapproxy: FTBFS with openssl 1.1.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.)


-- 
828586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: up-imapproxy
Version: 1.2.7-1.1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/up-imapproxy_1.2.7-1.1_amd64-20160529-1547

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: up-imapproxy
Source-Version: 1.2.8~svn20161210-1

We believe that the bug you reported is fixed in the latest version of
up-imapproxy, 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 828...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Richard Laager  (supplier of updated up-imapproxy 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: Sat, 10 Dec 2016 13:52:07 -0600
Source: up-imapproxy
Binary: imapproxy
Architecture: source amd64
Version: 1.2.8~svn20161210-1
Distribution: unstable
Urgency: medium
Maintainer: Jose Luis Tallon 
Changed-By: Richard Laager 
Description:
 imapproxy  - IMAP protocol proxy
Closes: 518928 526673 728557 738882 828586 834591 836122 838071
Changes:
 up-imapproxy (1.2.8~svn20161210-1) unstable; urgency=medium
 .
   [ Peter Eisentraut ]
   * status support (Closes: 526673)
 .
   [ Richard Laager ]
   * New co-maintainer (Closes: 838071)
   * Import packaging into git
   * Update watch file for SquirrelMail adoption
   * Update to debhelper 9
   * Add build-arch and build-indep targets
   * Update Standards-Version to 3.9.8 (no changes)
   * Standardize the name as IMAP Proxy / imapproxy
   * Tweak the package description
   * Import all changes to-date from SVN (Closes: 728557, 834591, 836122)
 (LP: 1614062)
   * Make the pimpstat.8 man page useful (Closes: 518928)
   * Start after IMAP daemons (if installed) (Closes: 738882)
   * Fix many compiler warnings
   * Fix building on OpenSSL 1.1 (Closes: 828586)
   * Remove some useless FAQ items
   * Cleanup the README situation
   * Cleanup comments in imapproxy.conf
   * Fix a spelling error
   * Verify GPG signatures in debian/watch
   * Add tony mancill as an uploader
Checksums-Sha1:
 26d0f70a9f8c59e391c61be3cff548e45bfc60cb 2111 
up-imapproxy_1.2.8~svn20161210-1.dsc
 9c1d72bf919ead75aed658a2649b8cff1f64dbc6 118901 
up-imapproxy_1.2.8~svn20161210.orig.tar.bz2
 53261308b1d33e35e4d6c66d01a9cdd5f7068064 27928 
up-imapproxy_1.2.8~svn20161210-1.debian.tar.xz
 2629dfdd8e192afd087389cc080acf3223fe9628 96126 
imapproxy-dbgsym_1.2.8~svn20161210-1_amd64.deb
 f2f8e5a1a6b314c63456fb3926440f74b0c7e0a0 59258 
imapproxy_1.2.8~svn20161210-1_amd64.deb
 cbd3ee5e2dbe9d530deeba127646d8b0ce18d1ba 4979 
up-imapproxy_1.2.8~svn20161210-1_amd64.buildinfo
Checksums-Sha256:
 7bb6ad915e70220e7be5c83986f098ee61525a425877e9f496e9a7cf533c0499 2111 
up-imapproxy_1.2.8~svn20161210-1.dsc
 e3344da01386e5bd68e6b82a3212545dc9ddbc65c535e4308bd4325581d6fee8 118901 
up-imapproxy_1.2.8~svn20161210.orig.tar.bz2
 4cc609ab0fde2fae9d1e5f77882ec9d22a50871f91c4c1b2e24775951549bf76 27928 
up-imapproxy_1.2.8~svn20161210-1.debian.tar.xz
 84c3b68ae5226fdd1898b1563e04c5453f2b77a35c18d72f0fc506fca530783e 96126 

Bug#836122: marked as done (imapproxy: systemd unit file breaks imapproxy)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2016 03:07:05 +
with message-id 
and subject line Bug#836122: fixed in up-imapproxy 1.2.8~svn20161210-1
has caused the Debian Bug report #836122,
regarding imapproxy: systemd unit file breaks imapproxy
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.)


-- 
836122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imapproxy
Version: 1.2.7-1.1 stretch
Severity: grave
Justification: renders package unusable

The systemd unit file, or something in the patch implemented in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829310 is causing 
imapproxy to randomly timeout and die, see following thread at 
upstream mailing list:

https://sourceforge.net/p/squirrelmail/mailman/squirrelmail-imapproxy/thread/bf5ac0ec-e309-ee5c-70e1-1b2f187249e0%40txbweb.de/#msg35255782

...for them, the solution is to change the following line in the unit file:

Type=fork

to:

Type=simple

I’ll also file a separate bug.
--- End Message ---
--- Begin Message ---
Source: up-imapproxy
Source-Version: 1.2.8~svn20161210-1

We believe that the bug you reported is fixed in the latest version of
up-imapproxy, 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 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Richard Laager  (supplier of updated up-imapproxy 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: Sat, 10 Dec 2016 13:52:07 -0600
Source: up-imapproxy
Binary: imapproxy
Architecture: source amd64
Version: 1.2.8~svn20161210-1
Distribution: unstable
Urgency: medium
Maintainer: Jose Luis Tallon 
Changed-By: Richard Laager 
Description:
 imapproxy  - IMAP protocol proxy
Closes: 518928 526673 728557 738882 828586 834591 836122 838071
Changes:
 up-imapproxy (1.2.8~svn20161210-1) unstable; urgency=medium
 .
   [ Peter Eisentraut ]
   * status support (Closes: 526673)
 .
   [ Richard Laager ]
   * New co-maintainer (Closes: 838071)
   * Import packaging into git
   * Update watch file for SquirrelMail adoption
   * Update to debhelper 9
   * Add build-arch and build-indep targets
   * Update Standards-Version to 3.9.8 (no changes)
   * Standardize the name as IMAP Proxy / imapproxy
   * Tweak the package description
   * Import all changes to-date from SVN (Closes: 728557, 834591, 836122)
 (LP: 1614062)
   * Make the pimpstat.8 man page useful (Closes: 518928)
   * Start after IMAP daemons (if installed) (Closes: 738882)
   * Fix many compiler warnings
   * Fix building on OpenSSL 1.1 (Closes: 828586)
   * Remove some useless FAQ items
   * Cleanup the README situation
   * Cleanup comments in imapproxy.conf
   * Fix a spelling error
   * Verify GPG signatures in debian/watch
   * Add tony mancill as an uploader
Checksums-Sha1:
 26d0f70a9f8c59e391c61be3cff548e45bfc60cb 2111 
up-imapproxy_1.2.8~svn20161210-1.dsc
 9c1d72bf919ead75aed658a2649b8cff1f64dbc6 118901 
up-imapproxy_1.2.8~svn20161210.orig.tar.bz2
 53261308b1d33e35e4d6c66d01a9cdd5f7068064 27928 
up-imapproxy_1.2.8~svn20161210-1.debian.tar.xz
 2629dfdd8e192afd087389cc080acf3223fe9628 96126 
imapproxy-dbgsym_1.2.8~svn20161210-1_amd64.deb
 f2f8e5a1a6b314c63456fb3926440f74b0c7e0a0 59258 
imapproxy_1.2.8~svn20161210-1_amd64.deb
 cbd3ee5e2dbe9d530deeba127646d8b0ce18d1ba 4979 
up-imapproxy_1.2.8~svn20161210-1_amd64.buildinfo
Checksums-Sha256:
 7bb6ad915e70220e7be5c83986f098ee61525a425877e9f496e9a7cf533c0499 2111 
up-imapproxy_1.2.8~svn20161210-1.dsc
 e3344da01386e5bd68e6b82a3212545dc9ddbc65c535e4308bd4325581d6fee8 118901 
up-imapproxy_1.2.8~svn20161210.orig.tar.bz2
 4cc609ab0fde2fae9d1e5f77882ec9d22a50871f91c4c1b2e24775951549bf76 27928 
up-imapproxy_1.2.8~svn20161210-1.debian.tar.xz
 84c3b68ae5226fdd1898b1563e04c5453f2b77a35c18d72f0fc506fca530783e 96126 
imapproxy-dbgsym_1.2.8~svn20161210-1_amd64.deb
 09008d8e0c1ad7b774269f78fe13657bd7e16068ab0e3f87892545e326a7594b 59258 
imapproxy_1.2.8~svn20161210-1_amd64.deb
 d8afd05d3adccdda0ff5ebdf11558857d5c7f4243ab73c5a89e42b3161776deb 4979 

Bug#845865: marked as done (libnss-mysql-bg: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Mon, 12 Dec 2016 03:04:12 +
with message-id 
and subject line Bug#845865: fixed in libnss-mysql-bg 1.5-5
has caused the Debian Bug report #845865,
regarding libnss-mysql-bg: switch to build depend on the metapackage 
default-libmysqlclient-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.)


-- 
845865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnss-mysql-bg
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: libnss-mysql-bg
Source-Version: 1.5-5

We believe that the bug you reported is fixed in the latest version of
libnss-mysql-bg, 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 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated libnss-mysql-bg 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, 12 Dec 2016 02:38:36 +0100
Source: libnss-mysql-bg
Binary: libnss-mysql-bg
Architecture: source
Version: 1.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 libnss-mysql-bg - NSS module for using MySQL as a naming service
Closes: 845865
Changes:
 libnss-mysql-bg (1.5-5) unstable; urgency=medium
 .
   * QA upload.
   * Switch to default-libmysqlclient-dev.  (Closes: #845865)
   * Switch to debhelper compat level 10.
Checksums-Sha1:
 db41e250e447cee5120641896cb941ea32bec2d2 1733 libnss-mysql-bg_1.5-5.dsc
 db7ab4f1806976b7f6566604ca3f3aa721c03e48 4700 
libnss-mysql-bg_1.5-5.debian.tar.xz
Checksums-Sha256:
 c9a490f13d1ebd34abc825021a2a37eb2eb27b04e116cbe5a40db564cec525d9 1733 
libnss-mysql-bg_1.5-5.dsc
 ff77e1350da49ca15fcf8a5cb8d1ed67dba3c640af1749d9b7b66f0a306f7c35 4700 
libnss-mysql-bg_1.5-5.debian.tar.xz
Files:
 8d66411001d6cbcfb19006822acd8810 1733 admin optional libnss-mysql-bg_1.5-5.dsc
 9e286bc9a2861cdab07b08e76587f1a6 4700 admin optional 
libnss-mysql-bg_1.5-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYTghmAAoJEF+zP5NZ6e0Ip3cQAJpXLeNqRW93edqkqV5fEqGk
XvLB0qikyDZT9iRNOUuavr5pRgUBcdGxAZAqivBrlEzGdz8pxMa4GEiWppmoxzJU
MHpe7eD+nwDnnmjyQBYJ0NvXaR+nYW0mi14X+IjHS2K75a4LVU5eLFr3tN324e7X
rnRvQa1J81NBsu9AvL6kQHIMIYR/70WSz1RjuWvAobTh2805KQY31eoWDlJF9HSz
zI/J5O0sTKTpzZ77ubiP13mMtaujMrt2s1izlF3wSOQrbAxRR/KVHYwtnwfEK27M
AIBuGTLYfJTbgzB9TwxI8hxcXZo8lesSlTp05HdN2CP1oqtkYbhaSBafGJqfqrJQ
63yGzZGM3VJmXYtrH0sceeosqrROT6gMvMsRLrGuUbYWGrf5r9uaOlhiYAXdaBg2
Zq/qerVOywVWdbddptuSWtXRcSVQRkfMthSPlK4Pv8UZDwzRar/36P24r5VlWVrx
x1RfWFEgc+eAIpvizDSIylIfufRWFSrFxPJaZDgZ0flddBKrOAYG9KJm7rot9TGe
jPGfDnnJyvJRuWVsv1AN1EqmuUTyRzi3YX9WmHga6t9rpWhbQ0xajAoCv9e5bvBD
vEn5SqXl+JNpzfAqLfY2t0bITZIpxAu4KUS9n4ld6WS/cl0mMBQdg76NRulKfNr+
tFEb2q9k+Dm1xdqBAvMZ
=E77V
-END PGP SIGNATURE End Message ---

Bug#847820: kicad: FTBFS: cannot access .../kicad-common/...

[Aaron M. Ucko]

Source: kicad
Version: 4.0.4+dfsg2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of kicad covering only its architecture-dependent binary
packages (as on the autobuilders, or with -B) have been failing:

  dh_fixperms
  # most of those file are included from somethere and have no shebang
  # like a #! sequence, removing execution rights ...
  chmod -x 
/«BUILDDIR»/kicad-4.0.4+dfsg2/debian/kicad-common/usr/share/kicad/scripting/plugins/*.py
  chmod: cannot access 
'/«BUILDDIR»/kicad-4.0.4+dfsg2/debian/kicad-common/usr/share/kicad/scripting/plugins/*.py':
 No such file or directory
  debian/rules:116: recipe for target 'override_dh_fixperms' failed
  make[1]: *** [override_dh_fixperms] Error 1
  make[1]: Leaving directory '/«BUILDDIR»/kicad-4.0.4+dfsg2'
  debian/rules:66: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

To fix this, I'd recommend splitting override_dh_fixperms up into
-arch and -indep variants, and perhaps transforming the former into
override_dh_strip-arch, which would appear to be a better fit for its
custom command.

Could you please take a look?

Thanks!

BTW, you rarely need to specify $(CURDIR)/ explicitly, though it
doesn't generally hurt, just adds noise.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#784181: razorqt: Razor-Qt dead upstream, superseded by LXDE-Qt

[Jeremy Bicha]

I see that razorqt was removed from testing, but why not remove it
from unstable too now?

Thanks,
Jeremy Bicha

Processed: found 839048 in 1.8.5-1.0.0+dfsg-4.3, tagging 839048, found 839050 in 24.2.0-2, tagging 839050 ...

[Debian Bug Tracking System]

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

> found 839048 1.8.5-1.0.0+dfsg-4.3
Bug #839048 {Done: John Paul Adrian Glaubitz } 
[libmozjs185-1.0] couchjs crashes on ARM64
Marked as found in versions mozjs/1.8.5-1.0.0+dfsg-4.3.
> tags 839048 + jessie sid stretch
Bug #839048 {Done: John Paul Adrian Glaubitz } 
[libmozjs185-1.0] couchjs crashes on ARM64
Added tag(s) stretch, jessie, and sid.
> found 839050 24.2.0-2
Bug #839050 [libmozjs-24-bin] js24 crashes on ARM64
Marked as found in versions mozjs24/24.2.0-2.
> tags 839050 + jessie sid stretch
Bug #839050 [libmozjs-24-bin] js24 crashes on ARM64
Added tag(s) sid, jessie, and stretch.
> found 843842 0.10.9-2
Bug #843842 {Done: Dirk Eddelbuettel } [rmysql] Update build 
dependency to libmariadb-dev in rmysql
There is no source info for the package 'rmysql' at version '0.10.9-2' with 
architecture ''
Unable to make a source version for version '0.10.9-2'
Marked as found in versions 0.10.9-2.
> thanks
Stopping processing here.

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

Bug#844902: marked as done (nuitka: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 23:33:37 +
with message-id 
and subject line Bug#844902: fixed in nuitka 0.5.24.4+ds-1
has caused the Debian Bug report #844902,
regarding nuitka: 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.)


-- 
844902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuitka
Version: 0.5.23+ds-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):
> Run './tests/packages/run_all.py search' in '/<>/nuitka-0.5.23+ds'.
> Using concrete python 2.7.12 on x86_64
> Consider output of recursively compiled program: sub_package
> Comparing output of 'sub_package/kitty' using 'python2.7' with flags silent, 
> expect_success, remove_output, module_mode, two_step_execution, 
> ignore_warnings ...
> Running the optimizations tests with options '--debug' with python2.7:
> Run './tests/optimizations/run_all.py search' in 
> '/<>/nuitka-0.5.23+ds'.
> Warning, no 'lxml' module installed, cannot do XML based tests.
> Running the standalone tests with options '--debug' with python2.7:
> Run './tests/standalone/run_all.py search' in 
> '/<>/nuitka-0.5.23+ds'.
> Using concrete python 2.7.12 on x86_64
> Consider output of recursively compiled program: CtypesUsing.py
> Comparing output of 'CtypesUsing.py' using 'python2.7' with flags silent, 
> expect_success, standalone, remove_output, plugin_disable:pylint-warnings, 
> no_site ...
> Should not access '/lib/x86_64-linux-gnu/libutil.so.1'.
> Should not access '/lib/x86_64-linux-gnu/libz.so.1'.
> Should not access '/usr/lib/x86_64-linux-gnu/libffi.so.6'.
> debian/rules:16: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/nuitka_0.5.23+ds-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: nuitka
Source-Version: 0.5.24.4+ds-1

We believe that the bug you reported is fixed in the latest version of
nuitka, 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.
Kay Hayen  (supplier of updated nuitka 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: Sat, 10 Dec 2016 12:25:35 +0100
Source: nuitka
Binary: nuitka
Architecture: source all
Version: 0.5.24.4+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Kay Hayen 
Changed-By: Kay Hayen 
Description:
 nuitka - Python compiler with full language support and CPython compatibil
Closes: 844902
Changes:
 nuitka (0.5.24.4+ds-1) unstable; urgency=medium
 .
   * New upstream hotfix release.
   * Better detection of acceptable shared library loads from
 system paths for standalone tests (Closes: 844902).
Checksums-Sha1:
 e9c2f77ce730d6843195e47af83484a1df49cd33 2113 nuitka_0.5.24.4+ds-1.dsc
 ea4bb73fd2cec704a6e3022856601c73426e617a 725735 nuitka_0.5.24.4+ds.orig.tar.gz
 f9428e99e7574df9102101a435708b7fcaa18207 10344 
nuitka_0.5.24.4+ds-1.debian.tar.xz
 47e577f9b685779ed7ccc280de6e727847e73a85 639786 nuitka_0.5.24.4+ds-1_all.deb
 6605825f84fdb3ed20f38a5f031d5705e608bf49 6715 
nuitka_0.5.24.4+ds-1_amd64.buildinfo
Checksums-Sha256:
 b94610c8210ae89aca4eb806d9bdf5ed45e027562a54dfb6e7797f7df5e2eade 2113 
nuitka_0.5.24.4+ds-1.dsc
 5452e7c25e4410ffde8b99b12c1b2cdfcbe8e02ae17333585794abe63b9c3035 725735 
nuitka_0.5.24.4+ds.orig.tar.gz
 9828a46f6f07d56c492cc2466beaec30369bc115462bf2300d77732f378ce1df 10344 
nuitka_0.5.24.4+ds-1.debian.tar.xz
 

Bug#847812: pysolfc: crash on startup

[Ben Hildred]

Package: pysolfc
Version: 2.0-4
Severity: grave
Justification: renders package unusable

$  pysolfc
Traceback (most recent call last):
  File "/usr/games/pysolfc", line 32, in 
sys.exit(main(sys.argv))
  File "/usr/share/games/pysolfc/pysollib/main.py", line 359, in main
r = pysol_init(app, args)
  File "/usr/share/games/pysolfc/pysollib/main.py", line 196, in pysol_init
app.loadImages1()
  File "/usr/share/games/pysolfc/pysollib/app.py", line 712, in loadImages1
im = loadImage(fn)
  File "/usr/share/games/pysolfc/pysollib/tile/tkutil.py", line 276, in
makeImage
im = PIL_Image(file)
  File "/usr/share/games/pysolfc/pysollib/tile/tkutil.py", line 254, in
__init__
ImageTk.PhotoImage.__init__(self, image)
  File "/usr/lib/python2.7/dist-packages/PIL/ImageTk.py", line 120, in __init__
self.paste(image)
  File "/usr/lib/python2.7/dist-packages/PIL/ImageTk.py", line 187, in paste
_imagingtk.tkinit(tk.interpaddr(), 1)
OverflowError: Python int too large to convert to C long



-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.7.0-1-686-pae (SMP w/2 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: sysvinit (via /sbin/init)

Versions of packages pysolfc depends on:
ii  python-configobj  5.0.6-2
ii  python-pygame 1.9.1release+dfsg-10+b2
ii  python-tk 2.7.11-2
pn  python:any

Versions of packages pysolfc recommends:
ii  python-pil.imagetk [python-imaging-tk]  3.4.2-1
pn  tk-tile 

Versions of packages pysolfc suggests:
pn  freecell-solver-bin  
ii  pysolfc-cardsets 2.0+dfsg2-2

-- no debconf information

Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Santiago Vila]

severity 825727 important
tags 825727 + patch
thanks

When I have Etc/UTC as the timezone, as autobuilders do,
the failure does not happen. If I use GMT+1, the failure happens.

I guess this makes the bug not to be RC after all, not because
it simply "does not usually happen" in the official autobuilders
(which, for FTBFS that happen randomly may just be a matter of luck),
but because it may *never* happen.

In either case, I believe the following trivial patch should fix the
problem in every case. Could anybody please try it?

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -64,6 +64,6 @@ get-orig-source:
 
 override_dh_auto_test:
 ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
-   LC_ALL=C py.test
-   LC_ALL=C py.test-3
+   LC_ALL=C TZ=Etc/UTC py.test
+   LC_ALL=C TZ=Etc/UTC py.test-3
 endif

Processed: Re: Bug#825727: python-babel: FTBFS: assert 'GMT+00:00' == 'GMT-01:59'

[Debian Bug Tracking System]

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

> severity 825727 important
Bug #825727 [src:python-babel] python-babel: FTBFS: assert 'GMT+00:00' == 
'GMT-01:59'
Severity set to 'important' from 'serious'
> tags 825727 + patch
Bug #825727 [src:python-babel] python-babel: FTBFS: assert 'GMT+00:00' == 
'GMT-01:59'
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#847750: rmysql: FTBFS on mips64el

[Andreas Beckmann]

Hi Otto,

could you take a look at the mariadb-related FTBFS of rmysql on mips64el?


Thanks

Andreas

On 2016-12-11 21:29, Dirk Eddelbuettel wrote:
> 
> On 11 December 2016 at 12:32, Andreas Beckmann wrote:
> | Source: rmysql
> | Version: 0.10.9-3
> | Severity: serious
> | Justification: fails to build from source (but built successfully in the 
> past)
> | 
> | 
> https://buildd.debian.org/status/fetch.php?pkg=rmysql=mips64el=0.10.9-3=1480467978
> | 
> |  fakeroot debian/rules binary-arch
> | CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
> source format 3.0 (quilt) instead
> | test -x debian/rules
> | dh_testroot
> | dh_prep 
> | dh_installdirs -A 
> | dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in 
> use)
> | mkdir -p "."
> | dh_installdirs  usr/lib/R/site-library
> | dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in 
> use)
> | echo "R:Depends=r-base-core (>= 3.3.2-1), r-api-3" >> 
> debian/r-cran-rmysql.substvars
> | if test -f /usr/bin/xvfb-run; then  \
> |  xvfb-run -a\
> | R CMD INSTALL -l 
> /«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library --clean \
> |  .  \
> | "--built-timestamp=\"Thu, 10 Nov 2016 06:12:59 
> -0600\"" \
> | ;   \
> | else\
> |  R CMD INSTALL -l 
> /«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library\
> | --clean  .  \
> | "--built-timestamp=\"Thu, 10 Nov 2016 06:12:59 
> -0600\"" \
> | ;   \
> | fi
> | * installing *source* package 'RMySQL' ...
> | ** package 'RMySQL' successfully unpacked and MD5 sums checked
> | ./configure: line 21: warning: command substitution: ignored null byte in 
> input
> | ./configure: line 22: warning: command substitution: ignored null byte in 
> input
> | Found mysql_config cflags and libs!
> | Using PKG_CFLAGS=-I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 
> -fdebug-prefix-map=/build/mariadb-connector-c-dopxmU/mariadb-connector-c-2.3.1=.
>  -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wunused -Wno-uninitialized
> | -I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 
> -fdebug-prefix-map=/build/mariadb-connector-c-dopxmU/mariadb-connector-c-2.3.1=.
>  -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wunused -Wno-uninitialized
> | Using PKG_LIBS=-L/usr/lib/mips64el-linux-gnuabi64 -lmariadb
> | -L/usr/lib/mips64el-linux-gnuabi64 -lmariadb
> | - ANTICONF ERROR ---
> | Configuration failed because libmysqlclient was not found. Try installing:
> |  * deb: libmariadb-client-lgpl-dev (Debian, Ubuntu 16.04)
> | libmariadbclient-dev (Ubuntu 14.04)
> 
> This is (small shell script 'anticonf') by the upstream author (who is a
> friend) failing.
> 
> Did anything change with respect to mariadb libs on mips64el ?
> 
> We currently use
> 
>Build-Depends: debhelper (>= 7.0.0), cdbs, r-base-dev (>= 3.3.2), 
> libmariadb-dev, r-cran-dbi (>= 0.4)
> 
> and Debian testing resolves libmariadb-dev just fine.  Same on mips64el?
> 
> Dirk
> 
> |  * rpm: mariadb-devel | mysql-devel (Fedora, CentOS, RHEL)
> |  * csw: mysql56_dev (Solaris)
> |  * brew: mariadb-connector-c (OSX)
> | If libmysqlclient is already installed, check that 'pkg-config' is in your
> | PATH and PKG_CONFIG_PATH contains a libmysqlclient.pc file. If pkg-config
> | is unavailable you can set INCLUDE_DIR and LIB_DIR manually via:
> | R CMD INSTALL --configure-vars='INCLUDE_DIR=... LIB_DIR=...'
> | 
> | ERROR: configuration failed for package 'RMySQL'
> | * removing 
> '/«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library/RMySQL'
> | /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
> | make: *** [R_any_arch] Error 1
> | 
> | 
> | Andreas
> 

Bug#847808: ruby-jquery-ui-rails FTBFS

[Johannes Schauer]

Package: ruby-jquery-ui-rails
Version: 6.0.1+dfsg-1
Severity: serious
Justification: fails to build from source

Hi,

the package currently FTBFS. Here are the last lines from the log:

dpkg-buildpackage
-

dpkg-buildpackage: info: source package ruby-jquery-ui-rails
dpkg-buildpackage: info: source version 6.0.1+dfsg-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Pirate Praveen 
 dpkg-source --before-build ruby-jquery-ui-rails-6.0.1+dfsg
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --buildsystem=ruby --with ruby
   dh_testdir -O--buildsystem=ruby
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>/ruby-jquery-ui-rails-6.0.1+dfsg'
rm -f jquery-ui
rm -rf app
make[1]: Leaving directory '/<>/ruby-jquery-ui-rails-6.0.1+dfsg'
   dh_clean -O--buildsystem=ruby
 debian/rules build
dh build --buildsystem=ruby --with ruby
   dh_testdir -O--buildsystem=ruby
   dh_update_autotools_config -O--buildsystem=ruby
   dh_auto_configure -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/ruby-jquery-ui-rails-6.0.1+dfsg'
dh_auto_build
dh_ruby --build
   dh_ruby --build
ln -s /usr/lib/nodejs/jquery-ui .
rake
rake aborted!
LoadError: cannot load such file -- bundler/gem_tasks
/<>/ruby-jquery-ui-rails-6.0.1+dfsg/Rakefile:3:in `'
(See full trace by running task with --trace)
debian/rules:18: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>/ruby-jquery-ui-rails-6.0.1+dfsg'
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2



When running rake with --trace, one gets:


rake aborted!
LoadError: cannot load such file -- bundler/gem_tasks
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/build/ruby-jquery-ui-rails-v29D2i/ruby-jquery-ui-rails-6.0.1+dfsg/Rakefile:3:in
 `'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:28:in `load'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:28:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:689:in `raw_load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:94:in `block in load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:176:in 
`standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:93:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:77:in `block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:176:in 
`standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:75:in `run'
/usr/bin/rake:27:in `'



Thanks!

cheers, josch

Bug#847806: libopenmpi2: broken SONAME links

[Andreas Beckmann]

Package: libopenmpi2
Version: 2.0.1-7
Severity: serious
Tags: patch

Hi,

there is another error in the SONAME links, causing
/usr/lib/libmpi_java.so.20 to be missing after package installation
and creating /usr/lib/libompitrace.so.0 instead of libompitrace.so.20

I'm thinking about a solution how this conditional installation and
linking stuff could be simplified, dh-exec might be a solution. Would
you interested in that?

Is it neccessary to have both the file link (libompifoo.so.20.1.2.3.4.5)
and the soname link (libompifoo.so.20) in /usr/lib? Wouldn't the soname
link be sufficient in /usr/lib? (and then have another soname->file link
in /usr/lib/openmpi/lib instead?)

What are the plans regarding 2.0.2? Do you expect that version to reach
stretch in time? Or will it be be delayed to stretch+1?


Andreas
diff -Nru openmpi-2.0.1/debian/libopenmpi2.links openmpi-2.0.1/debian/libopenmpi2.links
--- openmpi-2.0.1/debian/libopenmpi2.links	2016-10-21 20:01:25.0 +0200
+++ openmpi-2.0.1/debian/libopenmpi2.links	2016-12-11 17:11:33.0 +0100
@@ -16,7 +16,7 @@
 usr/lib/libmpi.so.20.0.1usr/lib/libmpi.so.20
 usr/lib/libmpi_usempif08.so.20.0.0		usr/lib/libmpi_usempif08.so.20
 usr/lib/libmpi_usempi_ignore_tkr.so.20.0.0   	usr/lib/libmpi_usempi_ignore_tkr.so.20
-usr/lib/libompitrace.so.20.0.0   usr/lib/libompitrace.so.0
+usr/lib/libompitrace.so.20.0.0  usr/lib/libompitrace.so.20
 usr/lib/libopen-pal.so.20.1.0   usr/lib/libopen-pal.so.20
 usr/lib/libopen-rte.so.20.0.0   usr/lib/libopen-rte.so.20
 #usr/lib/liboshmem.so.20.0.1		usr/lib/liboshmem.so.20
diff -Nru openmpi-2.0.1/debian/rules openmpi-2.0.1/debian/rules
--- openmpi-2.0.1/debian/rules	2016-10-21 20:01:25.0 +0200
+++ openmpi-2.0.1/debian/rules	2016-12-11 17:28:07.0 +0100
@@ -129,7 +129,7 @@
 		cp -a debian/tmp/usr/lib/openmpi/lib/libmpi_java.so.20.0.1 \
 			debian/libopenmpi2/usr/lib/openmpi/lib/libmpi_java.so.20.0.1 ; \
 		dh_link -p libopenmpi2 usr/lib/libmpi_java.so.20.0.1  usr/lib/libmpi_java.so.20 ; \
-		dh_link -p libopenmpi2 usr/lib/openmpi/lib/libmpi_java.so.20.0.0 usr/lib/libmpi_java.so.20.0.1 ; \
+		dh_link -p libopenmpi2 usr/lib/openmpi/lib/libmpi_java.so.20.0.1 usr/lib/libmpi_java.so.20.0.1 ; \
 		dh_link -p libopenpi-dev usr/lib/libmpi_java.so.20	usr/lib/libmca_common_verbs.so ; \
 	fi
 	if test -f debian/tmp/usr/lib/openmpi/lib/libmca_common_verbs.so.20.0.0 ; then \

Bug#800891: Please adjust the licensing of afex

[Henrik Singmann]

Hi Andreas,
I am sorry for the delay. I guess you will have to go ahead without it for
the next version.

I haven't managed to find the time to work on it yet. I will before the end
of the year, but don't know when. Sorry.

Regards,
Henrik

2016-12-11 16:38 GMT+01:00 Andreas Tille :

> Hi Henrik,
>
> any news about a new version with fixed license.  As I said the issue is
> a bit dense if we want to reach the next Debian stable version.
>
> Kind regards
>
>  Andreas.
>
> On Wed, Nov 16, 2016 at 09:37:57AM +0100, Andreas Tille wrote:
> > Hi Henrik,
> >
> > On Tue, Nov 15, 2016 at 08:57:20PM +0100, Henrik Singmann wrote:
> > > Hi Andreas, (this time with list in CC)
> > >
> > > Thanks for warning me. And no problem. I will change to GPL2 in the
> next
> > > release version. Can you give me some time to implement these changes
> and
> > > others I have planned for the next release? Let's say 4 weeks?
> >
> > As I said 4 weeks is a bit dense.  If you really manage in 4 weeks it
> > might make it.  However, it is not my power to push any package after
> > the freeze.
> >
> > Kind regards
> >
> >  Andreas.
> >
> > --
> > http://fam-tille.de
>
> --
> http://fam-tille.de
>



-- 
Dr. Henrik Singmann
Postdoc
Universität Zürich, Schweiz
http://singmann.org

Bug#846424: marked as done (fim: add libfl-dev to Build-Depends)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 21:34:33 +
with message-id 
and subject line Bug#846424: fixed in fim 0.5~rc2-5
has caused the Debian Bug report #846424,
regarding fim: 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.)


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

fim will soon fail to build from source, beause flex drops its
dependency on libfl-dev. Since fim 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: fim
Source-Version: 0.5~rc2-5

We believe that the bug you reported is fixed in the latest version of
fim, 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.
Rafael Laboissiere  (supplier of updated fim 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:31:53 -0200
Source: fim
Binary: fim
Architecture: source amd64
Version: 0.5~rc2-5
Distribution: unstable
Urgency: medium
Maintainer: Michele Martone 
Changed-By: Rafael Laboissiere 
Description:
 fim- scriptable frame buffer, X.org and ascii art image viewer
Closes: 846424
Changes:
 fim (0.5~rc2-5) unstable; urgency=medium
 .
   [ Michele Martone ]
   * d/control: Added libfl-dev to the Build-Depends list.
 Thanks to Helmut Grohne for notification. (Closes: #846424)
Checksums-Sha1:
 fd081a4604c94104b070747f4114a383a8fd89d3 2028 fim_0.5~rc2-5.dsc
 b0058ecb9110dd31c365decdc2a7c845c2e4a63f 7368 fim_0.5~rc2-5.debian.tar.xz
 b3b307815b1c0c95c0e13aed4441bad51a14c2d5 2786684 fim-dbgsym_0.5~rc2-5_amd64.deb
 9c8fe4ba8c3b9d08c684dd8563923de410bef314 9128 fim_0.5~rc2-5_amd64.buildinfo
 adb1724d1bd3acb54e5a40555bb1e550f4fc335a 395048 fim_0.5~rc2-5_amd64.deb
Checksums-Sha256:
 9c324aa4d54303c9233dce2f98e14d91caf2bb5f08a771e32e517ed7b4cdc463 2028 
fim_0.5~rc2-5.dsc
 2caf6d75215979aea900dee3675fa0f3bf5b37b6c9a39b0416abf3d2ea3133dd 7368 
fim_0.5~rc2-5.debian.tar.xz
 d2a06a26fae70fabb6877324ba71461383f8c5dd388b6b503c5da9382bcea93e 2786684 
fim-dbgsym_0.5~rc2-5_amd64.deb
 6944cd616e42e73ec550691062bc4962382a7a04976f4acd1ce4be488e3b 9128 
fim_0.5~rc2-5_amd64.buildinfo
 16a8648da9695ddb9d4ca72223d588ab900f1acbc598f8d86114678b4edc4a1c 395048 
fim_0.5~rc2-5_amd64.deb
Files:
 3073534ea55de2c2ff6a322b6f04a64a 2028 graphics extra fim_0.5~rc2-5.dsc
 bfb02667fb99681cff9c0f1d6f7c2fd7 7368 graphics extra 
fim_0.5~rc2-5.debian.tar.xz
 1058b055098d2e18a351fd09eccf9051 2786684 debug extra 
fim-dbgsym_0.5~rc2-5_amd64.deb
 09631248fd395b41e5d9ad3267d3223d 9128 graphics extra 
fim_0.5~rc2-5_amd64.buildinfo
 3481ada0779cd79c6f787d052dbfe09f 395048 graphics extra fim_0.5~rc2-5_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYTcGUAAoJECEkqhmDeFyQqCkP/0ueZUm4V8dbCcwnGwT3G1Gy
o/CZ+HwJS02EGnFbHX31Es+eKYKpwDVpO/LEbrHkg3iT3LJ5Zj7ZOWeDieH/4Yr1
ohyAF25KtY4Iu0Imn6X8bEUgXNXm0Vh4cb/TaSGLCTKMlmDSxLGixXBo+4v4ZVB4
aaMML7Yr9sgsFBJIApJj1TrITWtsz01/72JKRum27NgOm5UbwRnUWWhgUPjtWvoc
gViLvpq4lPdSv/d4Px/7f2Li1mf/t+GZ1tHWwEPj7+8ejECwJNp7XtiD96XYLlaQ
lp7WwVtqeXrdcqtf9ayi7c+MkM3QWwwYnYbBAl3W0r00lB4IucxHTpRlu7hgKTAv
fdKsojyOedd6sueQhR8ldprII3li3nWiPF+y0ECEpNnXEkbAdl5w3qcOXUC/sdRg
ljMciSr9dsZNOVoHSH1F8iegXwDw2Uqfk5PEfERUfaWVvTT3SDvURFkEmdmxHpFO
QnnrufrtKlCrUH0dmllQGoITc8ee7xAzOEHpeM7XhX303z73I1inPaRcWUdUn6aL
FEFyz3tJOAlSmyBEQe/Qjd9caLWq0TDFehdUTo+97DOOtyEYP/mh+IQ4gecj+AC4
7MyxzIOCixsFh5GesL8ugqynOkXPeZtEAaYoKMTDKqEWbZG38zh8hn0w941Sl2Gf
fASzN2p6p2LcvmqXcDV8
=DR7c
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 21:18:19 +
with message-id 
and subject line Bug#845909: fixed in soci 3.2.3-2
has caused the Debian Bug report #845909,
regarding soci: switch to build depend on the metapackage 
default-libmysqlclient-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.)


-- 
845909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: soci
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: soci
Source-Version: 3.2.3-2

We believe that the bug you reported is fixed in the latest version of
soci, 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 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
William Blough  (supplier of updated soci 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: Tue, 08 Nov 2016 13:54:34 -0500
Source: soci
Binary: libsoci-core3.2 libsoci-dev libsoci-mysql3.2 libsoci-sqlite3-3.2 
libsoci-postgresql3.2 libsoci-firebird3.2 libsoci-odbc3.2
Architecture: source
Version: 3.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: William Blough 
Changed-By: William Blough 
Description:
 libsoci-core3.2 - C++ Database Access Library
 libsoci-dev - C++ Database Access Library (devel)
 libsoci-firebird3.2 - C++ Database Access Library (Firebird backend)
 libsoci-mysql3.2 - C++ Database Access Library (MySQL backend)
 libsoci-odbc3.2 - C++ Database Access Library (ODBC backend)
 libsoci-postgresql3.2 - C++ Database Access Library (PostgreSQL backend)
 libsoci-sqlite3-3.2 - C++ Database Access Library (SQLite3 backend)
Closes: 845909
Changes:
 soci (3.2.3-2) unstable; urgency=medium
 .
   * Change libmysqlclient-dev to default-libmysqlclient-dev in build-depends
 (Closes: #845909)
   * Remove unneeded dh_clean override
   * Switch to automatic dbgsym package for symbols
   * Update standards version to 3.9.8 (no changes needed)
   * Update copyright
   * Update dh compatibility to 10
   * Linitan overrides for spelling error false positives
   * Force bindnow hardening flag since it's not getting applied automatically
Checksums-Sha1:
 ba910de8e10b8b39b7a54329df374841f3120c7e 2303 soci_3.2.3-2.dsc
 d6a6c2d6d113152dcef16ecbee77b8ad5f2c8ce6 4532 soci_3.2.3-2.debian.tar.xz
Checksums-Sha256:
 d2f9f780506ab50afed87b48ff7839310fe060b8e8deca19a4787268f5f14a4a 2303 
soci_3.2.3-2.dsc
 a85489e166de069ffc77f5dd45f080316bb6f37983cf3acd0a1c181fa7a020d9 4532 
soci_3.2.3-2.debian.tar.xz
Files:
 b7804dad1129ae05d37ee93d96f896d9 2303 libs optional soci_3.2.3-2.dsc
 3a1fe05e08b14dd2c34fcc95f933b6db 4532 libs optional soci_3.2.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlhNvkAACgkQkWT6HRe9
XTbjpxAAiR0iCIXN4uoZolPbRJ65Q2QBs0mZYBRKooBLpTL6wdh1wWRfqmG1ZWwl
6OOmrvmPGme8l4rXrDa0Bpz0VqJht1XValxJedCOb9nBcuNGgBSlZTVYnLh4Xo3L
sk87AekYLe5cQ9z+m6TGt3pSPkA0vM2s/HsnFWMQPriCP1St5eG21XK2iHnc1lK4
jqfEGeWrXugXUJOlRU2nonRwOtc5CTCuDHaSvSP3SajdwkES48c3PDJKuhrDlmSs
jR3hml4PFNOXIlvr2GuKCx/bEyh0fyT88oVwXI5FkMKs0KXm5NDnTMnrgq+xjxR7
a5e7DBaOM0HGYH8jL/VkcZfXQMI1DAPaH4zrLQQslZ3lvQoAiMhqScAOOk/3R95U
HWL6lpwr2LDeuIe2VF0L29gak/2ds5hSfnaJYF8cJH49wkgZfDGXVN6nep7+g4yl
9U2heQWLs4eDB4Q8ZKIP3kknY1eh8zfcuJg9x3vFHDeVSnXxUAbuLRJxhhciA2qR

Bug#847708: marked as done (syslog-ng-mod-json: fails to upgrade from 'testing' - trying to overwrite /usr/share/syslog-ng/include/scl/cim/template.conf)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 21:08:04 +
with message-id 
and subject line Bug#847708: fixed in syslog-ng 3.8.1-8
has caused the Debian Bug report #847708,
regarding syslog-ng-mod-json: fails to upgrade from 'testing' - trying to 
overwrite /usr/share/syslog-ng/include/scl/cim/template.conf
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.)


-- 
847708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: syslog-ng-mod-json
Version: 3.8.1-7
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 syslog-ng-mod-json.
  Preparing to unpack .../2-syslog-ng-mod-json_3.8.1-7_amd64.deb ...
  Unpacking syslog-ng-mod-json (3.8.1-7) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-5g5j8A/2-syslog-ng-mod-json_3.8.1-7_amd64.deb (--unpack):
   trying to overwrite '/usr/share/syslog-ng/include/scl/cim/template.conf', 
which is also in package syslog-ng-core 3.8.1-6
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-5g5j8A/2-syslog-ng-mod-json_3.8.1-7_amd64.deb


cheers,

Andreas


syslog-ng-core=3.8.1-6_syslog-ng-mod-json=3.8.1-7.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: syslog-ng
Source-Version: 3.8.1-8

We believe that the bug you reported is fixed in the latest version of
syslog-ng, 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.
SZALAY Attila  (supplier of updated syslog-ng 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: Sun, 11 Dec 2016 18:32:35 +0100
Source: syslog-ng
Binary: syslog-ng syslog-ng-dbg syslog-ng-dev syslog-ng-core 
syslog-ng-mod-journal syslog-ng-mod-json syslog-ng-mod-mongodb 
syslog-ng-mod-sql syslog-ng-mod-smtp syslog-ng-mod-amqp syslog-ng-mod-geoip 
syslog-ng-mod-redis syslog-ng-mod-stomp syslog-ng-mod-riemann 
syslog-ng-mod-graphite syslog-ng-mod-python syslog-ng-mod-add-contextual-data
Architecture: source amd64 all
Version: 3.8.1-8
Distribution: unstable
Urgency: medium
Maintainer: syslog-ng maintainers 

Changed-By: SZALAY Attila 
Description:
 syslog-ng  - Enhanced system logging daemon (metapackage)
 syslog-ng-core - Enhanced system logging daemon (core)
 syslog-ng-dbg - Enhanced system logging daemon (debug symbols)
 syslog-ng-dev - Enhanced system logging daemon (development files)
 syslog-ng-mod-add-contextual-data - Enhanced system logging daemon 
(add-contextual-data)
 syslog-ng-mod-amqp - Enhanced system logging daemon (AMQP plugin)
 syslog-ng-mod-geoip - Enhanced system logging daemon (GeoIP plugin)
 syslog-ng-mod-graphite - Enhanced system logging daemon (graphite plugin)
 syslog-ng-mod-journal - Enhanced system logging daemon (systemd journal plugin)
 syslog-ng-mod-json - Enhanced system logging daemon (JSON plugin)
 syslog-ng-mod-mongodb - Enhanced system logging daemon (MongoDB plugin)
 syslog-ng-mod-python - Enhanced system logging daemon (Python plugin)
 syslog-ng-mod-redis - Enhanced system logging daemon (Redis plugin)
 syslog-ng-mod-riemann - Enhanced system logging daemon (Riemann destination)
 syslog-ng-mod-smtp - Enhanced system logging daemon (SMTP plugin)
 syslog-ng-mod-sql - Enhanced system logging daemon (SQL plugin)
 syslog-ng-mod-stomp - Enhanced system logging daemon (STOMP plugin)
Closes: 847708
Changes:
 syslog-ng (3.8.1-8) unstable; urgency=medium
 .
   * [ee388fd] Declaring breaks because of file moving (Closes: 847708)
   * [1ebe21f] Switch to unstable repo
   * [18653b3] Added testing upgrade 

Bug#840589: skimage FTBFS on multiple architectures testsuite failures.

[Andreas Tille]

Hi,

I have reported the issue upstream[1] and pointed to Aurelien Jarno's
analysis explicitly.

BTW, I'd consider the packaging fitting into two teams: Either Debian
Science or DPMT.  Having a packaging repository outside of
git.debian.org and noticing it is lagging behind the actual packaging
is not very motivating to contribute.

Kind regards

   Andreas.


[1] https://github.com/scikit-image/scikit-image/issues/2398

-- 
http://fam-tille.de

Bug#847750: rmysql: FTBFS on mips64el

[Dirk Eddelbuettel]

On 11 December 2016 at 12:32, Andreas Beckmann wrote:
| Source: rmysql
| Version: 0.10.9-3
| Severity: serious
| Justification: fails to build from source (but built successfully in the past)
| 
| 
https://buildd.debian.org/status/fetch.php?pkg=rmysql=mips64el=0.10.9-3=1480467978
| 
|  fakeroot debian/rules binary-arch
| CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
| test -x debian/rules
| dh_testroot
| dh_prep 
| dh_installdirs -A 
| dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in use)
| mkdir -p "."
| dh_installdirsusr/lib/R/site-library
| dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in use)
| echo "R:Depends=r-base-core (>= 3.3.2-1), r-api-3" >> 
debian/r-cran-rmysql.substvars
| if test -f /usr/bin/xvfb-run; then\
|xvfb-run -a\
|   R CMD INSTALL -l 
/«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library --clean \
|.  \
|   "--built-timestamp=\"Thu, 10 Nov 2016 06:12:59 
-0600\"" \
|   ;   \
|   else\
|R CMD INSTALL -l 
/«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library\
|   --clean  .  \
|   "--built-timestamp=\"Thu, 10 Nov 2016 06:12:59 
-0600\"" \
|   ;   \
|   fi
| * installing *source* package 'RMySQL' ...
| ** package 'RMySQL' successfully unpacked and MD5 sums checked
| ./configure: line 21: warning: command substitution: ignored null byte in 
input
| ./configure: line 22: warning: command substitution: ignored null byte in 
input
| Found mysql_config cflags and libs!
| Using PKG_CFLAGS=-I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 
-fdebug-prefix-map=/build/mariadb-connector-c-dopxmU/mariadb-connector-c-2.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wunused -Wno-uninitialized
| -I/usr/include/mariadb -I/usr/include/mariadb/mysql -g -O2 
-fdebug-prefix-map=/build/mariadb-connector-c-dopxmU/mariadb-connector-c-2.3.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wunused -Wno-uninitialized
| Using PKG_LIBS=-L/usr/lib/mips64el-linux-gnuabi64 -lmariadb
| -L/usr/lib/mips64el-linux-gnuabi64 -lmariadb
| - ANTICONF ERROR ---
| Configuration failed because libmysqlclient was not found. Try installing:
|  * deb: libmariadb-client-lgpl-dev (Debian, Ubuntu 16.04)
| libmariadbclient-dev (Ubuntu 14.04)

This is (small shell script 'anticonf') by the upstream author (who is a
friend) failing.

Did anything change with respect to mariadb libs on mips64el ?

We currently use

   Build-Depends: debhelper (>= 7.0.0), cdbs, r-base-dev (>= 3.3.2), 
libmariadb-dev, r-cran-dbi (>= 0.4)

and Debian testing resolves libmariadb-dev just fine.  Same on mips64el?

Dirk

|  * rpm: mariadb-devel | mysql-devel (Fedora, CentOS, RHEL)
|  * csw: mysql56_dev (Solaris)
|  * brew: mariadb-connector-c (OSX)
| If libmysqlclient is already installed, check that 'pkg-config' is in your
| PATH and PKG_CONFIG_PATH contains a libmysqlclient.pc file. If pkg-config
| is unavailable you can set INCLUDE_DIR and LIB_DIR manually via:
| R CMD INSTALL --configure-vars='INCLUDE_DIR=... LIB_DIR=...'
| 
| ERROR: configuration failed for package 'RMySQL'
| * removing '/«PKGBUILDDIR»/debian/r-cran-rmysql/usr/lib/R/site-library/RMySQL'
| /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
| make: *** [R_any_arch] Error 1
| 
| 
| Andreas

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#847799: xerces-c: fails to build twice in a row

[Mattia Rizzolo]

Control: severity -1 important

On Sun, Dec 11, 2016 at 08:52:23PM +0100, Mattia Rizzolo wrote:
> source: xerces-c
> version: 3.1.4+debian-1
> severity: serious

$people made me notice how these bug are not RC (even if I thought so).
Sorry for the severity "pike" :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#847799: xerces-c: fails to build twice in a row

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #847799 [src:xerces-c] xerces-c: fails to build twice in a row
Severity set to 'important' from 'serious'

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

Bug#846782: gobject-introspection randomly hangs liferea build

[Paul Gevers]

Hi

On 11-12-16 17:46, Emilio Pozuelo Monfort wrote:
> They should be available in stretch:

I missed the part where it is in a separate archive.

> emilio@tatooine:~$ apt-cache madison libwebkit2gtk-4.0-37-dbgsym 
> libjavascriptcoregtk-4.0-18-dbgsym 
> libwebkit2gtk-4.0-37-dbgsym |   2.14.2-1 | 
> http://debug.mirrors.debian.org/debian-debug testing-debug/main amd64 Packages
> libwebkit2gtk-4.0-37-dbgsym |   2.14.2-1 | 
> http://debug.mirrors.debian.org/debian-debug unstable-debug/main amd64 
> Packages
> libjavascriptcoregtk-4.0-18-dbgsym |   2.14.2-1 | 
> http://debug.mirrors.debian.org/debian-debug testing-debug/main amd64 Packages
> libjavascriptcoregtk-4.0-18-dbgsym |   2.14.2-1 | 
> http://debug.mirrors.debian.org/debian-debug unstable-debug/main amd64 
> Packages

Interestingly, [1] shows it's only available in experimental and sid.

[1] https://packages.debian.org/search?keywords=libwebkit2gtk-4.0-37-dbgsym

> Can you install those and get a new trace, this time running
> 
> (gdb) thread apply all backtrace

Done and attached.

Paul
paul@testavoira ~ $ gdb -p 5674
GNU gdb (Debian 7.11.1-2+b1) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 5674
[New LWP 5675]
[New LWP 5676]
[New LWP 5677]
[New LWP 5678]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f55d97fd18f in pthread_cond_wait@@GLIBC_2.3.2 () from 
/lib/x86_64-linux-gnu/libpthread.so.0
(gdb) thread apply all backtrace

Thread 5 (Thread 0x7f5585ffd700 (LWP 5678)):
#0  0x7f55d953156d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f55d9a579f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f55d9a57d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f55d5d30620 in WTF::RunLoop::run () at 
./Source/WTF/wtf/glib/RunLoopGLib.cpp:94
#4  0x7f55d5d2f292 in WTF::WorkQueue::::operator() 
(__closure=0x7f5585ffcb40)
at ./Source/WTF/wtf/generic/WorkQueueGeneric.cpp:58
#5  std::_Function_handler 
>::_M_invoke(const std::_Any_data &) (__functor=...) at 
/usr/include/c++/6/functional:1740
#6  0x7f55d5d09f85 in std::function::operator()() const 
(this=0x7f5585ffcb40) at /usr/include/c++/6/functional:2136
#7  WTF::threadEntryPoint (contextData=0x7f55c79ec190) at 
./Source/WTF/wtf/Threading.cpp:60
#8  0x7f55d5d2ddba in WTF::wtfThreadEntryPoint (param=0x7f55c79f7070) at 
./Source/WTF/wtf/ThreadingPthreads.cpp:164
#9  0x7f55d97f7464 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7f55d953a9df in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f55867fe700 (LWP 5677)):
#0  0x7f55d953156d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f55d9a579f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f55d9a57d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f55d5d30620 in WTF::RunLoop::run () at 
./Source/WTF/wtf/glib/RunLoopGLib.cpp:94
#4  0x7f55d5d2f292 in WTF::WorkQueue::::operator() 
(__closure=0x7f55867fdb40)
at ./Source/WTF/wtf/generic/WorkQueueGeneric.cpp:58
#5  std::_Function_handler 
>::_M_invoke(const std::_Any_data &) (__functor=...) at 
/usr/include/c++/6/functional:1740
#6  0x7f55d5d09f85 in std::function::operator()() const 
(this=0x7f55867fdb40) at /usr/include/c++/6/functional:2136
#7  WTF::threadEntryPoint (contextData=0x7f55c79ec140) at 
./Source/WTF/wtf/Threading.cpp:60
#8  0x7f55d5d2ddba in WTF::wtfThreadEntryPoint (param=0x7f55c79f7050) at 
./Source/WTF/wtf/ThreadingPthreads.cpp:164
#9  0x7f55d97f7464 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7f55d953a9df in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f5586fff700 (LWP 5676)):
#0  0x7f55d953156d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f55d9a579f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f55d9a57d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f55d5d30620 in WTF::RunLoop::run () at 

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Bill Blough]

> 
> It still fails the very same way.
> Attached the backtrace I get with the way you said above (without
> exporting anything).  It seems to really be full, what Gianfranco posted
> looks more like the non-full/regular bt, dunno why.

Thanks.  Disregard my other email.

GDB didn't find the debug symbols for the other backtrace, but for yours
it did.  This could help.

Thanks,
Bill

Bug#828267: [Pkg-citadel-devel] Bug#828267: reopen, it is still valid

[Michael Meskes]

> > What are you trying to do here? Reopen 828267 and merge with
> > itself?
> > There is no other bug mentioned. What do I miss?
> 
> Yeah. Not very smart. I intended to merge it with 846543.

So there is already 846543 to track this problem. I don't really see
the point in reopening 828267 and then merging it, but ok. 

> > Care to explain? The CFLAG change did make the package compile,
> > install
> > and run, so why reopen the bug?
> 
> The bug was created and it was mentioned that this package needs
> changes in
> order to get it compiled against the new openssl ABI which is in
> experimental.
> Your upload of the "fixed" package was performed on 2016-10-30 and
> was built
> against openssl 1.0.2. So even if you would have done nothing, your 

Sure, because there was no 1.1.0 to build against for unstable.

> package
> would been built successfully *but* against a 1.0.2. The test should
> have been
> done against the version in experimental.

Actually I did, but apparently something went wrong. 

> On 2016-11-01 openssl 1.1.0 was uploaded to unstable. From this point
> in time
> your package would have fail to build. So I *think* the change in the
> CFLAGS
> is a nop.

It definitely is, at the very least because it contains a copy
error, sigh. 

> So the bug was created because the package did not compile against
> openssl
> 1.1.0 and now #846543 was created which mostly a dupe of this one.

Thus it would have worked to use that one.

> That means you have a valid RC bug which should be solved in order to
> get this
> package ready for the release and I mentioned two options people are
> doing.
> Most of what I wrote is from the transition bug #827061. The
> libssl1.0-dev is
> provided by openssl 1.0.2 and is intended to provide the 1.0.2 API
> for package
> which can't be fixed in time for release.

Sorry, wasn't precise enough it seems. I was wondering why you left out
the third possible option, namely the compatibility API in libssl 1.1.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Mattia Rizzolo]

On Sun, Dec 11, 2016 at 01:54:36PM -0500, Bill Blough wrote:
> On Sun, Dec 11, 2016 at 07:43:08PM +0100, Mattia Rizzolo wrote:
> > On Sun, Dec 11, 2016 at 01:34:18PM -0500, Bill Blough wrote:
> > > I just found a reference in the Debian Maintainer's Guide that says the
> > > default build locale is C.  And it looks like the Ubuntu build is
> > > explicitly setting a locale of C.UTF-8.
> > 
> > Where is that?
> 
> I misspoke, it's not the Debian Maintainer's Guide, but the "Guide for
> Debian Maintainers"
> 
> https://www.debian.org/doc/manuals/debmake-doc/ch07.en.html#utf-8-build

Yeah, well, that's not Debian Policy, so it is not so authoritative...

> > Really, in Debian there is no "default build locale", and I've seen RC
> > bugs for packages failing to build in non-C locales.
> > See also the Reproducible Builds project, which is making sure packages
> > built in different locales are always the same.
> 
> The link above says
> 
>   The default locale of the build environment is C
> 
> I certainly agree that we shouldn't be using arbitrary locales, but here
> I'm talking about using C.UTF-8, which the above link says should be
> used when necessary.

Of course.  What I'm saying is that you can't assume that your build is
going to happen in a known locale.  If your build system depends on a
locale you need to assure that's available and set.

> > > Would you be willing to add
> > > 
> > > LC_ALL := C.UTF-8
> > > export LC_ALL
> > > 
> > > to the top of debian/rules and try another build?
> > 
> > running.

It still fails the very same way.
Attached the backtrace I get with the way you said above (without
exporting anything).  It seems to really be full, what Gianfranco posted
looks more like the non-full/regular bt, dunno why.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
(sid_s390x-dchroot)mattia@zelenka ~/xerces/xerces-c-3.1.4+debian % libtool 
--mode=execute gdb --args samples/SAXCount samples/data/personal.xml
GNU gdb (Debian 7.11.1-2+b1) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/home/mattia/xerces/xerces-c-3.1.4+debian/samples/.libs/SAXCount...done.
(gdb) catch throw
Catchpoint 1 (throw)
(gdb) run
Starting program: 
/home/mattia/xerces/xerces-c-3.1.4+debian/samples/.libs/SAXCount 
samples/data/personal.xml
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1".

Catchpoint 1 (exception thrown), 0x03fffbcb49b4 in __cxa_throw () from 
/usr/lib/s390x-linux-gnu/libstdc++.so.6
(gdb) bt full
#0  0x03fffbcb49b4 in __cxa_throw () from 
/usr/lib/s390x-linux-gnu/libstdc++.so.6
No symbol table info available.
#1  0x03fffddb4948 in xercesc_3_1::ReaderMgr::popReader 
(this=0x2b2d838) at xercesc/internal/ReaderMgr.cpp:1083
prevEntity = 0x2b3d488
prevReaderThrowAtEnd = true
readerNum = 3
this = 0x2b2d838
#2  0x03fffddb500c in xercesc_3_1::ReaderMgr::skipPastSpaces 
(this=0x2b2d838) at xercesc/internal/ReaderMgr.cpp:273
tmpFlag = true
#3  0x03fffde59ee8 in xercesc_3_1::DTDScanner::scanExtSubsetDecl 
(this=this@entry=0x3ffe398, inIncludeSect=inIncludeSect@entry=false,
isDTD=isDTD@entry=true) at xercesc/validators/DTD/DTDScanner.cpp:2588
nextCh = 
bDoBreak = false
janContentFlag = {fOldVal = false, fValPtr = 0x3ffe3d0}
bAcceptDecl = false
bbSpace = { = {}, fBuffer = 
, fMgr = 0x2b2d8f0}
orgReader = 3
inMarkup = false
inCharData = false
#4  0x03fffdda1b72 in xercesc_3_1::IGXMLScanner::scanDocTypeDecl 
(this=0x2b2d768) at xercesc/internal/IGXMLScanner.cpp:1544
reader = 0x3fffb1ed018
gDTDStr = {68, 84, 68, 0}
declDTD = 0x2b3d488
janDecl = { = {}, fData = 
0x2b3d488}
srcUsed = 0x2b3da68
janSrc = { = {}, fData = 
0x2b3da68}
skippedSomething = true
bbRootName = { = {}, fBuffer = 
@0x2b38e48, fMgr = }
colonPosition = 1
validName = 

Bug#832307: marked as done (starpy: package has disappeared from unstable)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 20:00:10 +
with message-id 
and subject line Bug#832307: fixed in starpy 1.0.1.0.git.20151124-1.1
has caused the Debian Bug report #832307,
regarding starpy: package has disappeared from unstable
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.)


-- 
832307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starpy
Version: 1.0.1.0.git.20151124-1
Severity: serious

There is something fishy with starpy, it has disappeared from
unstable even though there was an upload 2 weeks ago.

There is a removal record:
https://ftp-master.debian.org/removals.txt

[Date: Fri, 15 Jul 2016 00:44:40 +] [ftpmaster: Scott Kitterman]
Removed the following packages from unstable:

starpy | 1.0.1.0.git.20151124-1 | source

--- Reason ---
[auto-cruft] obsolete source package
--

which probably means it didn't build successfully on the arch:all
autobuilder. Can't check further since the logs are now gone.
Check that it builds with
  dpkg-buildpackage -A


Andreas
--- End Message ---
--- Begin Message ---
Source: starpy
Source-Version: 1.0.1.0.git.20151124-1.1

We believe that the bug you reported is fixed in the latest version of
starpy, 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 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated starpy 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: Sat, 10 Dec 2016 11:12:00 +0100
Source: starpy
Binary: python-starpy
Architecture: source all
Version: 1.0.1.0.git.20151124-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Andreas Beckmann 
Description:
 python-starpy - Asterisk (AMI) protocols for Twisted Python
Closes: 832307
Changes:
 starpy (1.0.1.0.git.20151124-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Re-upload after the package has disappeared from unstable.
 (Closes: #832307)
Checksums-Sha1:
 c4ab158993c2719a288109edda2a33766da7bfea 2088 
starpy_1.0.1.0.git.20151124-1.1.dsc
 af98c71730f603d3f7a6b3b66d75dfe68ede56d5 51886 
starpy_1.0.1.0.git.20151124.orig.tar.gz
 92e893843f2e92248222661d3144afd70b14ae78 4168 
starpy_1.0.1.0.git.20151124-1.1.debian.tar.xz
 68505588411142a8126c6d2c2394c0654001f99b 54174 
python-starpy_1.0.1.0.git.20151124-1.1_all.deb
 f4b40f45c1d10301d2062638ad3098c8bb667dc4 5662 
starpy_1.0.1.0.git.20151124-1.1_amd64.buildinfo
Checksums-Sha256:
 e01ad245b8a9e06669e7e0accf748830c5621d7043d4212003006489023261f9 2088 
starpy_1.0.1.0.git.20151124-1.1.dsc
 e87a6ddc517b4c3ab5c041f1d43592c59fd9065db46371eafc09f183e099f67f 51886 
starpy_1.0.1.0.git.20151124.orig.tar.gz
 409020f1e473b4342a3e19e8a1cdfff76e9923426623679150cd3ef7fabcf62d 4168 
starpy_1.0.1.0.git.20151124-1.1.debian.tar.xz
 61294b36407608c44643a1aa981cbdf095b38a3c7dee22f58412c66d7d6d8be8 54174 
python-starpy_1.0.1.0.git.20151124-1.1_all.deb
 7393fe00eb8ae5bb546cdf89010590c515719585a4ba935299bbca9f47992706 5662 
starpy_1.0.1.0.git.20151124-1.1_amd64.buildinfo
Files:
 caba8903898cb21a34264bfb6c5c4a0c 2088 python optional 
starpy_1.0.1.0.git.20151124-1.1.dsc
 ddd006342c47c2c0ee5ee626d3dd514d 51886 python optional 
starpy_1.0.1.0.git.20151124.orig.tar.gz
 727bbb6c22430dbbb1ab1dfe6589acad 4168 python optional 
starpy_1.0.1.0.git.20151124-1.1.debian.tar.xz
 633e98ecf1882fb5825b7a0d846b41f8 54174 python optional 
python-starpy_1.0.1.0.git.20151124-1.1_all.deb
 68a28ec867e52d7ce7e7356bca32a044 5662 python optional 
starpy_1.0.1.0.git.20151124-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYS9VDAAoJEF+zP5NZ6e0IwJYP/RB3qKjVLFImiIOAUtQInd2U
SS3oDCXyjqk7DQkHW+pfEe9JKYA/HyylVN+u6j27FRo6xiC8CYOPMAT/Rsskd7Kw
w+FlMsMqputAl8ercM+uW0r/7s26woPysqTZKaT3QA/PNgUc/l89s4dOBkTuzkGB
PSpsArz4FfylbPHZyzw9j/Fkgr25YFgK5FY8MiyYRMPutRUvkfajWR4CR9Pm/7Fn

Bug#847799: xerces-c: fails to build twice in a row

[Mattia Rizzolo]

source: xerces-c
version: 3.1.4+debian-1
severity: serious


If I build twice (with a `clean` run in the middle) I get:

   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/home/mattia/xerces/xerces-c-3.1.4+debian'
mkdir doc/html
mkdir: cannot create directory ‘doc/html’: File exists
debian/rules:21: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/home/mattia/xerces/xerces-c-3.1.4+debian'
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2



or, alternatively, a dpkg-source error if I instead run a full build (so
source+binary) instead of a binary-only build (-b) as I did above.


This means that the clean target of your package doesn't properly clean
the source as mandated by Policy 4.9:

| clean (required)
|   This must undo any effects that the build and binary targets may have
|   had, except that it should leave alone any output files created in the
|   parent directory by a run of a binary target.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#828586: Building with OpenSSL 1.0.2 is sufficient for stretch

[Richard Laager]

On 12/11/2016 09:43 AM, Jose Luis Tallon wrote:
> On 12/11/2016 12:58 AM, Adrian Bunk wrote:
>> Not a perfect solution but sufficient for stretch is the patch below to 
>> use OpenSSL 1.0.2
> 
> Thank you for the patch!
> 
> Richard Laager has been preparing a new version, including all pending
> patches. CC'ing him so that we keep synchronized.
> Tony Mancill has agreed to sponsor that upload.

That upload includes a patch I wrote to build imapproxy against OpenSSL
1.1 (while still supporting older OpenSSL). We should be good as soon as
that is uploaded (hopefully today or tomorrow, we have one last thing to
fix).

-- 
Richard

Processed: Bug is also in the version in testing

[Debian Bug Tracking System]

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

> found 845178 1.1.2-1
Bug #845178 [src:python-aiohttp] FTBFS with super-fresh cython -- seems to 
carry pre-cythoned sources which get rebuilt during clean
Bug #846697 [src:python-aiohttp] python-aiohttp: FTBFS: dpkg-buildpackage: 
error: dpkg-source -b python-aiohttp-1.1.5 gave error exit status 2
Marked as found in versions python-aiohttp/1.1.2-1.
Marked as found in versions python-aiohttp/1.1.2-1.
> thanks
Stopping processing here.

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

Bug#847542: #847747

[GCS]

Hi Michael,

2016-12-11 19:29 GMT+01:00 Michael Ott :
> I found it.
> It looks like #847747
 Please test it with downgrading your policykit-1 package as well.

Thanks,
Laszlo/GCS

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 845178 846697
Bug #845178 [src:python-aiohttp] FTBFS with super-fresh cython -- seems to 
carry pre-cythoned sources which get rebuilt during clean
Bug #845178 [src:python-aiohttp] FTBFS with super-fresh cython -- seems to 
carry pre-cythoned sources which get rebuilt during clean
Added tag(s) sid and stretch.
Bug #846697 [src:python-aiohttp] python-aiohttp: FTBFS: dpkg-buildpackage: 
error: dpkg-source -b python-aiohttp-1.1.5 gave error exit status 2
Merged 845178 846697
> thanks
Stopping processing here.

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

Bug#847139: marked as done (tcsh: /usr/bin/tcsh no longer in package)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 19:19:00 +
with message-id 
and subject line Bug#847139: fixed in tcsh 6.20.00-2
has caused the Debian Bug report #847139,
regarding tcsh: /usr/bin/tcsh no longer in package
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.)


-- 
847139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: tcsh
Source-Version: 6.20.00-2

We believe that the bug you reported is fixed in the latest version of
tcsh, 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.
Thomas Lange  (supplier of updated tcsh 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: Sun, 11 Dec 2016 18:51:28 +
Source: tcsh
Binary: tcsh
Architecture: source amd64
Version: 6.20.00-2
Distribution: unstable
Urgency: high
Maintainer: Thomas Lange 
Changed-By: Thomas Lange 
Description:
 tcsh   - TENEX C Shell, an enhanced version of Berkeley csh
Closes: 847139
Changes:
 tcsh (6.20.00-2) unstable; urgency=high
 .
   * rules: put executable into /bin, make new symlink, Closes: #847139
   * variables.at: disable cdtohome test
Checksums-Sha1:
 721df8828ddeb52c8a3ecd2d175f98d0165928cc 1844 tcsh_6.20.00-2.dsc
 1291072f838c964bb6832fd282f2e72bf80d3a47 23091 tcsh_6.20.00-2.diff.gz
 b3f10a3156093025a29406876e12aae3ff20e64b 537988 tcsh-dbgsym_6.20.00-2_amd64.deb
 3e3c161752d850d9cbb20a993acbe95a45dd5217 4964 tcsh_6.20.00-2_amd64.buildinfo
 e3284ab822ca288ba8e2a909f9758e06c24d2747 469640 tcsh_6.20.00-2_amd64.deb
Checksums-Sha256:
 ce5047d16acbb9367e5d69976232d0c10d87078b3207d2fb0a5867023879ce6c 1844 
tcsh_6.20.00-2.dsc
 e58beb3ddad20ffd03fe87adf5a2033ac651eba7df831a127bc3351fb7da9b0d 23091 
tcsh_6.20.00-2.diff.gz
 68a17fb544ee54c0aa5b13956629fc7ccb213df14be1d331705b26312813357e 537988 
tcsh-dbgsym_6.20.00-2_amd64.deb
 e68636de33573a9bfe81b6824113c86646d625f920ec9cc6d158be2869c6faa2 4964 
tcsh_6.20.00-2_amd64.buildinfo
 b534b38f54c9160edbeb0f48cddfe33fd0863e018e63df3cfd0f81d530b8d002 469640 
tcsh_6.20.00-2_amd64.deb
Files:
 3032dfe2ce852ade46adc95cf8080da1 1844 shells optional tcsh_6.20.00-2.dsc
 7111f3438e0114616a110506686620d4 23091 shells optional tcsh_6.20.00-2.diff.gz
 4246738e5ded496994132980ade06b07 537988 debug extra 
tcsh-dbgsym_6.20.00-2_amd64.deb
 b436d9d3176e5e40fbafe13927dabe29 4964 shells optional 
tcsh_6.20.00-2_amd64.buildinfo
 453c2dba9f94995b7ac771248465d4a3 469640 shells optional 
tcsh_6.20.00-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAlhNoJARHGxhbmdlQGRl
Ymlhbi5vcmcACgkQK/jZ/gdLzeSRIw/+Jf3h9FMW5PZFMvfWfsOImB0GlxEBpeTk
G+Mkj90fn1RJI0L3CYpss1BcO0rkG3LRpCG9UZNt9sxqWUgidqJwq3fKsCzTnsCj
VC8G377zG6Te0SKlU7q7KgtnB2LYVwRyjSwz6p4RCPMt6sa4rnB3g/OAcnqNZiYk
p9SPiHR9+bmb1Lx620pGESsRUvA4DxHY9eaz+hxrluly8L9NcZ2XbHAGe95OfPHP
19lsB3HANiU12lkMWOPchdsgnv1WHZBWWycbcy6Cf6nROxD0YYhxbF2R7bRHUR/u
l15o4dZXtD2vt71yCYPtZVwtjMIJ69UZnpcosA+f75lJ5BeQ8mO0PMD02PTAbq41
uCagbZuBVLmh18bR0cLiS/tnXBE0oRI4wXhs+XZWD7pvdRVGd82zZJiblbKtnfmG
D9SCXYc9hW9uak3GWydW6AYYwNZ2b2gfCgkn0/WdQt9EmkyMTGzc4Benc3xn4swt

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Bill Blough]

On Sun, Dec 11, 2016 at 07:43:08PM +0100, Mattia Rizzolo wrote:
> On Sun, Dec 11, 2016 at 01:34:18PM -0500, Bill Blough wrote:
> > I just found a reference in the Debian Maintainer's Guide that says the
> > default build locale is C.  And it looks like the Ubuntu build is
> > explicitly setting a locale of C.UTF-8.
> 
> Where is that?

I misspoke, it's not the Debian Maintainer's Guide, but the "Guide for
Debian Maintainers"

https://www.debian.org/doc/manuals/debmake-doc/ch07.en.html#utf-8-build

> Really, in Debian there is no "default build locale", and I've seen RC
> bugs for packages failing to build in non-C locales.
> See also the Reproducible Builds project, which is making sure packages
> built in different locales are always the same.

The link above says

  The default locale of the build environment is C

I certainly agree that we shouldn't be using arbitrary locales, but here
I'm talking about using C.UTF-8, which the above link says should be
used when necessary.


> 
> > Would you be willing to add
> > 
> > LC_ALL := C.UTF-8
> > export LC_ALL
> > 
> > to the top of debian/rules and try another build?
> 
> running.
> 

Thanks very much.

Bill

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Bill Blough]

On Sun, Dec 11, 2016 at 06:20:13PM +, Mattia Rizzolo wrote:
> anyhow, 1) build should not depend on the locale it runs
I'll admit, I don't know a lot about locales, etc., but some of the
tests use files in UTF-8.  Wouldn't that generally require UTF-8 support
from the locale?

> 2) afaik it isn't any different than other archs
Yes, that's true, but I've seen arch-dependent locale issues in the
past.

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Mattia Rizzolo]

On Sun, Dec 11, 2016 at 01:34:18PM -0500, Bill Blough wrote:
> I just found a reference in the Debian Maintainer's Guide that says the
> default build locale is C.  And it looks like the Ubuntu build is
> explicitly setting a locale of C.UTF-8.

Where is that?
Really, in Debian there is no "default build locale", and I've seen RC
bugs for packages failing to build in non-C locales.
See also the Reproducible Builds project, which is making sure packages
built in different locales are always the same.

> Would you be willing to add
> 
> LC_ALL := C.UTF-8
> export LC_ALL
> 
> to the top of debian/rules and try another build?

running.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Bill Blough]

On Sun, Dec 11, 2016 at 05:57:38PM +, Gianfranco Costamagna wrote:
> Hi,
> 
> >Does anyone know (or can find out) the default locale on the s390
> >systems, and does that differ from the other architectures?
> >
> >env | egrep "(LC|LANG)"
> >
> >should give a list of relevant vars.
> 
> 
> (not sure if it is related to my laptop configuration, I did ssh and 
> copy-pasted)
> 
> locutusofborg@zelenka:~$ uname -a
> Linux zelenka 3.16.0-4-s390x #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) 
> s390x GNU/Linux
> locutusofborg@zelenka:~$ env | egrep "(LC|LANG)"
> LC_PAPER=it_IT.UTF-8
> LC_ADDRESS=it_IT.UTF-8
> LC_MONETARY=it_IT.UTF-8
> LC_NUMERIC=it_IT.UTF-8
> LC_TELEPHONE=it_IT.UTF-8
> LC_IDENTIFICATION=it_IT.UTF-8
> LANG=en_US.UTF-8
> LC_MEASUREMENT=it_IT.UTF-8
> LC_TIME=it_IT.UTF-8
> LC_NAME=it_IT.UTF-8
> 

Hmm... That must be set by ssh based on your local environment.

I just found a reference in the Debian Maintainer's Guide that says the
default build locale is C.  And it looks like the Ubuntu build is
explicitly setting a locale of C.UTF-8.

I've run into locale-related issues that affected one architecture but not
others (though it was i386 vs amd64 in that case), and since we're
dealing with an ICU update, and the runtime exception is dealing with a
bad buffer (which could mean there was a buffer, but it was the
incorrect size), I'm thinking this could be locale related. But
admittedly, it's a shot in the dark.

Would you be willing to add

LC_ALL := C.UTF-8
export LC_ALL

to the top of debian/rules and try another build?  Or I could prepare
another package with the changes if you'd rather not muck with editing
files.

Bug#847789: [node-acorn] node-vinyl-fs tests fail - /usr/lib/nodejs/acorn/tokentype.js:4 SyntaxError: Unexpected token =

[Sruthi]

Package: node-acorn
Version: 4.0.3-1
Severity: grave

--- Please enter the report below this line. ---
Unable to run node-vinyl-fs (repo at 
git+ssh://git.debian.org/git/pkg-javascript/node-vinyl-fs.git)tests
because of the below error in acorn.

$ mocha -R spec
/usr/lib/nodejs/acorn/tokentype.js:4
  constructor(label, conf = {}) {
  ^

SyntaxError: Unexpected token =
  at exports.runInThisContext (vm.js:53:16)
  at Module._compile (module.js:373:25)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load
(/usr/lib/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at Object. (/usr/lib/nodejs/acorn/state.js:2:63)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load
(/usr/lib/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at Object. (/usr/lib/nodejs/acorn/index.js:3:17)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load
(/usr/lib/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at Object. (/usr/lib/nodejs/gulp-sourcemaps/src/init.js:11:11)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load
(/usr/lib/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at Object. (/usr/lib/nodejs/gulp-sourcemaps/index.js:4:9)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load
(/usr/lib/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at Object.
(/home/srud/build/javascript/gulp/vinyl-fs/node-vinyl-fs/lib/src/index.js:8:18)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load
(/usr/lib/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at Object.
(/home/srud/build/javascript/gulp/vinyl-fs/node-vinyl-fs/index.js:4:8)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load
(/usr/lib/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at Object.
(/home/srud/build/javascript/gulp/vinyl-fs/node-vinyl-fs/test/dest.js:9:11)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load
(/usr/lib/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:300:12)
  at Module.require (module.js:353:17)
  at require (internal/module.js:12:17)
  at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
  at Array.forEach (native)
  at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
  at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
  at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
  at Module._compile (module.js:409:26)
  at Object.Module._extensions..js (module.js:416:10)
  at Module.load (module.js:343:32)
  at Function.Module._load (module.js:300:12)
  at Function.Module.runMain (module.js:441:10)
  at startup (node.js:139:18)
  at node.js:974:3


--- System information. ---
Architecture:
Kernel: Linux 4.8.0-1-amd64

Debian Release: stretch/sid
500 unstable debian.sil.at

--- Package information. ---
Depends (Version) | Installed
==-+-===
nodejs | 4.6.1~dfsg-1


Package's Recommends field is empty.

Package's Suggests field is empty.



signature.asc
Description: OpenPGP digital signature

Bug#847542: #847747

[Michael Ott]

Hi Lazlo!

I found it. 
It looks like #847747

CU  
 
  Michael
  
-- 
,''`.   
   : :' :   Michael Ott 
   `. `'e-mail: michael at king-coder dot de
 `-

Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

Bug#845878: marked as done (mysql-ocaml: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 18:21:02 +
with message-id 
and subject line Bug#845878: fixed in mysql-ocaml 1.2.0-3
has caused the Debian Bug report #845878,
regarding mysql-ocaml: switch to build depend on the metapackage 
default-libmysqlclient-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.)


-- 
845878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-ocaml
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: mysql-ocaml
Source-Version: 1.2.0-3

We believe that the bug you reported is fixed in the latest version of
mysql-ocaml, 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 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated mysql-ocaml 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: Sun, 11 Dec 2016 18:52:06 +0100
Source: mysql-ocaml
Binary: libmysql-ocaml libmysql-ocaml-dev
Architecture: source
Version: 1.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Description:
 libmysql-ocaml - OCaml bindings for MySql (runtime package)
 libmysql-ocaml-dev - OCaml bindings for MySql (development package)
Closes: 845878
Changes:
 mysql-ocaml (1.2.0-3) unstable; urgency=medium
 .
   * Team upload
   * Change build-dependency on libmysqlclient-dev to
 default-libmysqlclient-dev, and the same for the dependency of
 libmysql-ocaml-dev  (closes: #845878).
   * Fix spelling in changelog entry 1.2.0-2.
   * Standards-Version 3.9.8 (no change)
   * Vcs-{Git,Browser}: use secure URI
Checksums-Sha1:
 43a880d2107f8b4a597c32e525748b35c886afc5 2181 mysql-ocaml_1.2.0-3.dsc
 70a2326cf3bb7b53a2846fef01533e27944c6ade 3792 mysql-ocaml_1.2.0-3.debian.tar.xz
Checksums-Sha256:
 6a21e1eda8f12b68299ff2dd1687524b68bf32a5397a8bc4069f59a6d3d91a67 2181 
mysql-ocaml_1.2.0-3.dsc
 38a8795be44b4472f8bc6d57c52e62f9ba065cba092b6afc56d0db369c933d7f 3792 
mysql-ocaml_1.2.0-3.debian.tar.xz
Files:
 294e5bf1a7f3f2cecd01fcea5e1f0ed5 2181 ocaml optional mysql-ocaml_1.2.0-3.dsc
 56281d642647d3812f2f309fcd41317a 3792 ocaml optional 
mysql-ocaml_1.2.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAlhNlLcACgkQdFxHZtTK
zf/xcRAAkWIOj0F6f9keFfedtadKyFUmQfR8f3xj4J9xVvP4oeKEM8UuRLTzCjud
NnML1oDnjzazHSqesKkv3qPBTxcrQhfhT9ILvc7ylnRJQcpp4IvKhU8M08L9+glz
aoBBkhNWrELQsqlRGyQOEt1q0vMtAHqBRIRoTzJDVwkuJGsk4BY624c7TeEA0ozP
MPAm1NqRs9h6dxom6TUgyHxyKGL8FhQ9SIeUCZUNXX+LXg9witAjPDdg8v+s2aHu
TF8GDG99lD82yo6NkiBZ8abrA/A5jCErpOL6Hh//FPpFKzyzhfxTIHypUUmEtx7g
Z58ndjBzIKPKKwmUyqeT7alH5+SgUFN1unKdmfjxNlHgY18Cqsjn/UOXtlwQ+nwn
mU/8iGXYVkTo5udRWsKU6/I6dbEOvXLBHM77dBMEaE1WTKzYYRmghu2LqgWfK5HW
jxLZkro1L8r4sHAZZelLzt1wKnVrVpvTordN1ZvlO5iiH4qZekSYC1QOT7s4Bypw
dKwwJ0zYuCBiPc4ZO6tqwEdGml8uOxli62Nx1tyyjHaRzlw9krbVmgUlR85sOT/j
BxAaxGcs+YdIxAbHRXo9DNqsAfkdJPj/qW1Ikl6lYC6cSM7QjoG+0Flh+1RgE/8F
ZcB6+hCgfSENeHsjVLjVCDJC6WGaPU2VAa66/CQfT4CVoEJout8=
=iWev
-END PGP SIGNATURE End Message ---

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Mattia Rizzolo]

On Sun, Dec 11, 2016 at 6:57 PM Gianfranco Costamagna <
costamagnagianfra...@yahoo.it> wrote:

> (not sure if it is related to my laptop configuration, I did ssh and
> copy-pasted)
>

Yep, ssh transfers LC_* variables.

anyhow, 1) build should not depend on the locale it runs 2) afaik it isn't
any different than other archs

Bug#821516: libfpdi-php: diff for NMU version 1.4.1-1

[simon]

Dear maintainer,

I've prepared an NMU for libfpdi-php (versioned as 1.4.1-1) to
PHP 7.0 Transition.

Regards.
Simon

Processed: tagging 821516

[Debian Bug Tracking System]

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

> tags 821516 + patch
Bug #821516 [libfpdi-php] libfpdi-php: PHP 7.0 Transition
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#811588: marked as done (FTBFS with GCC 6: statement indented as if it were guarded by)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 18:03:40 +
with message-id 
and subject line Bug#811588: fixed in grail 3.1.0-2.1
has caused the Debian Bug report #811588,
regarding FTBFS with GCC 6: statement indented as if it were guarded by
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.)


-- 
811588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grail
Version: 3.1.0-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation

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.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> gcc -DHAVE_CONFIG_H -I. -I.. -I../include/ -Wall -Werror -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o grail-test-atomic.o grail-test-atomic.c
> grail-test-atomic.c: In function 'process_frame_events':
> grail-test-atomic.c:151:11: error: statement is indented as if it were 
> guarded by... [-Werror=misleading-indentation]
>subscribe(grail_handle, device, subscribe_window, subscriptions, 3,
>^
> 
> grail-test-atomic.c:148:9: note: ...this 'else' clause, but it is not
>  else
>  ^~~~
> 
> /bin/bash ../libtool  --tag=CC   --mode=link gcc -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -o 
> grail-test-edge grail-test-edge.o device.o servertime.o slice.o 
> ../src/libgrail.la -lframe  -lframe -lX11 -lXext -lXi  -lm 
> cc1: all warnings being treated as errors

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: grail
Source-Version: 3.1.0-2.1

We believe that the bug you reported is fixed in the latest version of
grail, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated grail 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: Sun, 11 Dec 2016 09:45:35 -0700
Source: grail
Binary: libgrail6 libgrail-dev grail-tools
Architecture: source
Version: 3.1.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Stephen M. Webb 
Changed-By: Sean Whitton 
Description:
 grail-tools - Gesture Recognition And Instantiation Library - test tools
 libgrail-dev - Gesture Recognition And Instantiation Library - dev files
 libgrail6  - Gesture Recognition And Instantiation Library
Closes: 811588
Changes:
 grail (3.1.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply upstream revision 257 to fix misleading indentation (Closes: 
#811588).
Checksums-Sha1:
 389f10b079ae8fb86c61ecf6e94afe1faa1c9951 2100 grail_3.1.0-2.1.dsc
 09092390bed8b7623e8af8ce418b2c7cfdcdab17 3396 grail_3.1.0-2.1.debian.tar.xz
Checksums-Sha256:
 89de48d6a00fde249ea827ff502c2d0aa1de00c2b50e6c12b279059e91c55fa3 2100 
grail_3.1.0-2.1.dsc
 81a56b5065874850a24f87bcf49e190d5ada213ea2950f1fdeaa67b13976295b 3396 
grail_3.1.0-2.1.debian.tar.xz
Files:
 16ac1220ddac8bdcc43cbf3763b18e77 2100 libs optional grail_3.1.0-2.1.dsc
 bebda9d477862cce64acdd9427d16a7c 3396 libs optional 
grail_3.1.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYTZLpAAoJEPNPCXROn13ZcygQAM4Ni+MU3eutNsmaHD8MKXQ/
7RymR33LEb1lbBMj9Bfgosf8wrqwZFGUs0BnQZsAJ2lCyb9xfOh0Wfiv0iTUaxPL
6RH25C479uKZM3GufGexNKFst8cC7e1Wx3WEjA1GbxKMNDXTiFo7LVwDnYoUF0EZ
HGgC7fca8kAseBVfUeuOBuHYv/nn4aZyOBIbCt+tlgkep4d1XW+alkmTvAIEwC+l
tPCLDOkh7O67iD9kUw/Zb2onoZRVgwbfu+8bGLeeDINaB7Y/1fpdRHfbUpfu/7V9
AeeWULquO50Axm2B/8S+wA1jwone6g26GtoHFTPglSSQD7LflSzMW7EOURg4em4r

Bug#843313: marked as done (FTBFS: libsexplib-camlp4-dev is no longer available)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 18:59:41 +0100
with message-id <87h96acpo2@msgid.hilluzination.de>
and subject line ocaml-ipaddr/2.7.0-2 builds just fine.
has caused the Debian Bug report #843313,
regarding FTBFS: libsexplib-camlp4-dev is no longer available
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.)


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

Hi,

Your package no longer builds libsexplib-camlp4-dev, and the
new libsexplib-ocaml-dev doesn't provide it. This would be
fine if it weren't for the number of reverse dependencies
that build-depend on it:

* source package sexplib310 version 113.33.03-3 no longer builds
  binary package(s): libsexplib-camlp4-dev
  on 
amd64,arm64,armel,armhf,i386,kfreebsd-amd64,kfreebsd-i386,mips,mips64el,mipsel,powerpc,ppc64el,s390x
  - suggested command:
dak rm -m "[auto-cruft] NBS (no longer built by sexplib310)" -s unstable -a 
amd64,arm64,armel,armhf,i386,kfreebsd-amd64,kfreebsd-i386,mips,mips64el,mipsel,powerpc,ppc64el,s390x
 -p -R -b libsexplib-camlp4-dev
  - broken Depends:
janest-core: libcore-ocaml-dev [amd64 arm64 armel armhf i386 kfreebsd-amd64 
kfreebsd-i386 powerpc]
  - broken Build-Depends:
custom-printf: libsexplib-camlp4-dev
janest-core: libsexplib-camlp4-dev
janest-core-extended: libsexplib-camlp4-dev
janest-core-kernel: libsexplib-camlp4-dev
ocaml-re2: libsexplib-camlp4-dev
ocaml-textutils: libsexplib-camlp4-dev
otags: libsexplib-camlp4-dev
pa-structural-sexp: libsexplib-camlp4-dev
pa-test: libsexplib-camlp4-dev
typerep: libsexplib-camlp4-dev

Please file bugs against those (or fix them directly if you maintain
them) or make libsexplib-ocaml-dev provide libsexplib-camlp4-dev.

Cheers,
Emilio

-- 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 ---
I just verified that ocaml-ipaddr/2.7.0-2 build-depends on
libsexplib-ocaml-dev, not libsexplib-camlp4-dev, and builds just fine in
an current unstable schroot environment.

Cheers,
-Hilko--- End Message ---

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Gianfranco Costamagna]

Hi,

>Does anyone know (or can find out) the default locale on the s390
>systems, and does that differ from the other architectures?
>
>env | egrep "(LC|LANG)"
>
>should give a list of relevant vars.


(not sure if it is related to my laptop configuration, I did ssh and 
copy-pasted)

locutusofborg@zelenka:~$ uname -a
Linux zelenka 3.16.0-4-s390x #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) s390x 
GNU/Linux
locutusofborg@zelenka:~$ env | egrep "(LC|LANG)"
LC_PAPER=it_IT.UTF-8
LC_ADDRESS=it_IT.UTF-8
LC_MONETARY=it_IT.UTF-8
LC_NUMERIC=it_IT.UTF-8
LC_TELEPHONE=it_IT.UTF-8
LC_IDENTIFICATION=it_IT.UTF-8
LANG=en_US.UTF-8
LC_MEASUREMENT=it_IT.UTF-8
LC_TIME=it_IT.UTF-8
LC_NAME=it_IT.UTF-8




G.

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Bill Blough]

Does anyone know (or can find out) the default locale on the s390
systems, and does that differ from the other architectures?

env | egrep "(LC|LANG)"

should give a list of relevant vars.

Thanks,
Bill

Bug#847542: #847542

[GCS]

Control: tags -1 +moreinfo unreproducible

On Sun, Dec 11, 2016 at 4:42 PM, Michael Ott  wrote:
>> > I installed libmozjs-24-0 24.2.0-5 and I have the same as on last
>> > version. I have to downgrade to 24.2.0-3.1 and than it works again
>> What architecture do you use?
> AMD64
 With Intel or AMD CPU?

>> Did you do a full update of your system?
> Yes. I think so.
 May you post the output of:
$ dpkg -l | grep 24.2.0
after installing -5?

> Versions of packages libmozjs-24-0 depends on:
> ii  libc6   2.24-8
> ii  libffi6 3.3~20160224-1
> ii  libgcc1 1:7-20161201-1
> ii  libnspr42:4.13.1-1
> ii  libstdc++6  7-20161201-1
 It seems your system is a mix of Sid and old experimental versions.
For example, libffi6 is 3.2.1-6 in Sid, while 3.3~20160605-1 is in
experimental. You have a rather old one, the 3.3~20160224-1 package
version. The same is with libgcc1 and libstdc++6 packages, Sid has
1:6.2.1-5 and experimental doesn't have it. But your system has GCC 7
(7-20161201-1)! I think these are the main problems, not libmozjs-24-0
this time.
 At least I've tried hard to reproduce your issue on my AMD64 box. Did
a dist-upgrade with Sid, rebooted and my DM started correctly. Then
installed Cinnamon and rebooted again - using it without any problems.
Tried other things as well, everything working as expected.

Please try to update to experimental or downgrade to Sid at least
libffi6 and/or may you try to compile the mozjs24 source package for
your box? There can be an incompatibility with GCC 6 as well and your
GCC 7 compilation would help.

Kind regards,
Laszlo/GCS

Processed: Re: Bug#847542: #847542

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +moreinfo unreproducible
Bug #847542 {Done: Laszlo Boszormenyi (GCS) } [libmozjs-24-0] 
libmozjs-24-0 24.2.0-4 breaks gnome-shell, preventing gdm3 from starting
Bug #847585 {Done: Laszlo Boszormenyi (GCS) } [libmozjs-24-0] 
gnome-shell: Gnome-shell fails to launch
Bug #847590 {Done: Laszlo Boszormenyi (GCS) } [libmozjs-24-0] 
gnome-session crash with latest nvidia driver (375.20)
Added tag(s) moreinfo and unreproducible.
Added tag(s) unreproducible and moreinfo.
Added tag(s) unreproducible and moreinfo.

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

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

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 17:03:23 +
with message-id 
and subject line Bug#821989: fixed in gnokii 0.6.30+dfsg-1.2
has caused the Debian Bug report #821989,
regarding gnokii: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
821989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnokii
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package gnokii builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that gnokii builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to gnokii at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, gnokii will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: gnokii
Source-Version: 0.6.30+dfsg-1.2

We believe that the bug you reported is fixed in the latest version of
gnokii, 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 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated gnokii 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: Fri, 09 Dec 2016 17:39:06 +0100
Source: gnokii
Binary: gnokii gnokii-common gnokii-cli xgnokii gnokii-smsd gnokii-smsd-mysql 
gnokii-smsd-pgsql libgnokii6 libgnokii-dev
Architecture: source
Version: 0.6.30+dfsg-1.2
Distribution: unstable
Urgency: medium
Maintainer: Leo Costela 
Changed-By: Sebastian Ramacher 
Description:
 gnokii - Datasuite for mobile phone management (metapackage)
 gnokii-cli - Datasuite for mobile phone management (console interface)
 gnokii-common - Datasuite for mobile phone management (base files)
 gnokii-smsd - SMS Daemon for mobile phones
 gnokii-smsd-mysql - SMSD plugin for MySQL storage backend
 gnokii-smsd-pgsql - SMSD plugin for PostgreSQL storage backend
 libgnokii-dev - Gnokii mobile phone interface library (development files)
 libgnokii6 - Gnokii mobile phone interface library
 xgnokii- Datasuite for mobile phone management (X interface)
Closes: 821989 845848
Changes:
 gnokii (0.6.30+dfsg-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Santiago Vila ]
   * Add build-arch and build-indep targets. (Closes: #821989)
 .
   [ Sebastian Ramacher ]
   * Switch to default-libmysqlclient-dev. (Closes: #845848)
Checksums-Sha1:
 f2f55759211abb9121dd9e1541a30cef41a72543 2580 gnokii_0.6.30+dfsg-1.2.dsc
 50e75c5ceb31e7f55bf3f844c08a2aaeba46f9ad 16564 
gnokii_0.6.30+dfsg-1.2.debian.tar.xz
Checksums-Sha256:
 cd250863abfc7ee5546f22c36927e933b27407fe194892f80700f3dd6b928d9c 2580 
gnokii_0.6.30+dfsg-1.2.dsc
 1e1acb477cf47f93bc2312d8584cb21ce21776bc2e9923e6187ada7d2eaa876f 16564 
gnokii_0.6.30+dfsg-1.2.debian.tar.xz
Files:
 89391d726b0862e5fce77dd642026ff7 2580 comm optional gnokii_0.6.30+dfsg-1.2.dsc
 0a4655b2c59b78402a2c9ee405e352ba 16564 comm optional 
gnokii_0.6.30+dfsg-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAlhK3zEACgkQafL8UW6n
GZPjGhAAiWnngwMNhEjg7UQIrLKi30mNqIYByUBM9xryde8n/Tm//19k6BNmDO3F
7pkjAA0vDZExMQlxlU7IcGPg/GJfXdSHybU8YfwNHwBxKKQmw3SGC01FFn150xWf
cih5f+DfZWC71SIBFXhMfhU2kDDx4IpulQu0Z0prgvrZ6fip+XOBpgom7VbzJ1a4
eM8LKBT4HTMQx26oNbGpATnS4xpRVPiKxqhoxynmXXrKsavUoS12zDZQgGkEqq8l
XnhzXTsQvsrBR86xKzgpHgXnns45LgmtDmsjUIok32XWfdE6LU01kgeK24g6yVMB
5giFEObhdLZi0BD65q2Th2JJA+AVRVB3UPnYOwt6KBeP/AB6OgrRdir/w8dMi/LH
Nqy9Bq8N2lb8GJYPliaQJ+h1YC5zIL1yju0AZJmrcd6zG+/w68ZEKJ423SN1tUbv

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

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 17:03:23 +
with message-id 
and subject line Bug#845848: fixed in gnokii 0.6.30+dfsg-1.2
has caused the Debian Bug report #845848,
regarding gnokii: switch to build depend on the metapackage 
default-libmysqlclient-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.)


-- 
845848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnokii
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: gnokii
Source-Version: 0.6.30+dfsg-1.2

We believe that the bug you reported is fixed in the latest version of
gnokii, 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 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated gnokii 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: Fri, 09 Dec 2016 17:39:06 +0100
Source: gnokii
Binary: gnokii gnokii-common gnokii-cli xgnokii gnokii-smsd gnokii-smsd-mysql 
gnokii-smsd-pgsql libgnokii6 libgnokii-dev
Architecture: source
Version: 0.6.30+dfsg-1.2
Distribution: unstable
Urgency: medium
Maintainer: Leo Costela 
Changed-By: Sebastian Ramacher 
Description:
 gnokii - Datasuite for mobile phone management (metapackage)
 gnokii-cli - Datasuite for mobile phone management (console interface)
 gnokii-common - Datasuite for mobile phone management (base files)
 gnokii-smsd - SMS Daemon for mobile phones
 gnokii-smsd-mysql - SMSD plugin for MySQL storage backend
 gnokii-smsd-pgsql - SMSD plugin for PostgreSQL storage backend
 libgnokii-dev - Gnokii mobile phone interface library (development files)
 libgnokii6 - Gnokii mobile phone interface library
 xgnokii- Datasuite for mobile phone management (X interface)
Closes: 821989 845848
Changes:
 gnokii (0.6.30+dfsg-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Santiago Vila ]
   * Add build-arch and build-indep targets. (Closes: #821989)
 .
   [ Sebastian Ramacher ]
   * Switch to default-libmysqlclient-dev. (Closes: #845848)
Checksums-Sha1:
 f2f55759211abb9121dd9e1541a30cef41a72543 2580 gnokii_0.6.30+dfsg-1.2.dsc
 50e75c5ceb31e7f55bf3f844c08a2aaeba46f9ad 16564 
gnokii_0.6.30+dfsg-1.2.debian.tar.xz
Checksums-Sha256:
 cd250863abfc7ee5546f22c36927e933b27407fe194892f80700f3dd6b928d9c 2580 
gnokii_0.6.30+dfsg-1.2.dsc
 1e1acb477cf47f93bc2312d8584cb21ce21776bc2e9923e6187ada7d2eaa876f 16564 
gnokii_0.6.30+dfsg-1.2.debian.tar.xz
Files:
 89391d726b0862e5fce77dd642026ff7 2580 comm optional gnokii_0.6.30+dfsg-1.2.dsc
 0a4655b2c59b78402a2c9ee405e352ba 16564 comm optional 
gnokii_0.6.30+dfsg-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAlhK3zEACgkQafL8UW6n
GZPjGhAAiWnngwMNhEjg7UQIrLKi30mNqIYByUBM9xryde8n/Tm//19k6BNmDO3F
7pkjAA0vDZExMQlxlU7IcGPg/GJfXdSHybU8YfwNHwBxKKQmw3SGC01FFn150xWf
cih5f+DfZWC71SIBFXhMfhU2kDDx4IpulQu0Z0prgvrZ6fip+XOBpgom7VbzJ1a4
eM8LKBT4HTMQx26oNbGpATnS4xpRVPiKxqhoxynmXXrKsavUoS12zDZQgGkEqq8l
XnhzXTsQvsrBR86xKzgpHgXnns45LgmtDmsjUIok32XWfdE6LU01kgeK24g6yVMB
5giFEObhdLZi0BD65q2Th2JJA+AVRVB3UPnYOwt6KBeP/AB6OgrRdir/w8dMi/LH
Nqy9Bq8N2lb8GJYPliaQJ+h1YC5zIL1yju0AZJmrcd6zG+/w68ZEKJ423SN1tUbv
Wuh2ArLyFnS0ziGVwtjfouIkodeYwM6N7dj6E2rRDsFhgkyny2zt7n9TC/q1Iuje

Processed: RFS: grail/3.1.0-2.1 [NMU, RC]

[Debian Bug Tracking System]

Processing control commands:

> block 811588 by -1
Bug #811588 [grail] FTBFS with GCC 6: statement indented as if it were guarded 
by
811588 was not blocked by any bugs.
811588 was not blocking any bugs.
Added blocking bug(s) of 811588: 847783

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

Bug#846731: marked as done (libbio-scf-perl: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 17:03:34 +
with message-id 
and subject line Bug#846731: fixed in libbio-scf-perl 1.03-3
has caused the Debian Bug report #846731,
regarding libbio-scf-perl: FTBFS: Test 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.)


-- 
846731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbio-scf-perl
Version: 1.03-2
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):
> # Running under perl version 5.024001 for linux
> # Current time local: Fri Dec  2 19:55:58 2016
> # Current time GMT:   Fri Dec  2 19:55:58 2016
> # Using Test.pm version 1.28_01
> ok 1
> Failed 17/18 subtests 
> 
> Test Summary Report
> ---
> t/scf.t (Wstat: 11 Tests: 1 Failed: 0)
>   Non-zero wait status: 11
>   Parse errors: Bad plan.  You planned 18 tests but ran 1.
> Files=1, Tests=1,  0 wallclock secs ( 0.03 usr  0.00 sys +  0.07 cusr  0.01 
> csys =  0.11 CPU)
> Result: FAIL
> Failed 1/1 test programs. 0/1 subtests failed.
> Makefile:991: recipe for target 'test_dynamic' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/libbio-scf-perl_1.03-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: libbio-scf-perl
Source-Version: 1.03-3

We believe that the bug you reported is fixed in the latest version of
libbio-scf-perl, 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.
gregor herrmann  (supplier of updated libbio-scf-perl 
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: Sun, 11 Dec 2016 17:39:58 +0100
Source: libbio-scf-perl
Binary: libbio-scf-perl
Architecture: source
Version: 1.03-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 775434 846731
Description: 
 libbio-scf-perl - Perl extension for reading and writing SCF sequence files
Changes:
 libbio-scf-perl (1.03-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
 .
   [ gregor herrmann ]
   * Mark package as autopkgtest-able.
   * Slightly reformat debian/copyright.
   * Mention full module name in long description.
   * Rename autopkgtest configuration file(s) as per new pkg-perl-
 autopkgtest schema.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Add patch 0001-Fix-overflowing-casts-from-pointer-to-integer.patch.
 Thanks to Niko Tyni for coming up with the patch.
 (Closes: #846731, #775434)
   * Set bindnow linker flag in debian/rules.
   * Declare compliance with Debian Policy 3.9.8.
Checksums-Sha1: 
 1bee04c89a715b227af804282439f02bc4f80d91 2203 libbio-scf-perl_1.03-3.dsc
 5a8165248492e18800e41ec447b94309580e7014 6924 
libbio-scf-perl_1.03-3.debian.tar.xz
Checksums-Sha256: 
 77110ba659d54bc4556d736989f060b772906aaae3a94422c1e9988c3ed629dd 2203 
libbio-scf-perl_1.03-3.dsc
 ecd1adab02cb40017a09829c7055e1479655366091d295db71cd6209c9cfad41 6924 
libbio-scf-perl_1.03-3.debian.tar.xz
Files: 
 f5fdd455c2ae0e1f14aca5d176f1f4a3 2203 perl optional libbio-scf-perl_1.03-3.dsc
 c9fcb447d95fa968bab2491435a06d75 6924 perl optional 
libbio-scf-perl_1.03-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#846721: marked as done (libaudio-mpd-perl: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 17:03:29 +
with message-id 
and subject line Bug#846721: fixed in libaudio-mpd-perl 2.004-2
has caused the Debian Bug report #846721,
regarding libaudio-mpd-perl: FTBFS: Test 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.)


-- 
846721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaudio-mpd-perl
Version: 2.004-1
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):
> ok 10 - add() songs
> ok 11 - delete() songs
> ok 12 - deleteid() songs
> ok 13 - clear() leaves 0 songs
> ok 14 - clear() changes playlist length
> Failed 10/24 subtests 
> 
> Test Summary Report
> ---
> t/40-playlist.t(Wstat: 0 Tests: 14 Failed: 0)
>   Parse errors: Bad plan.  You planned 24 tests but ran 14.
> Files=12, Tests=201, 31 wallclock secs ( 0.08 usr  0.03 sys +  7.57 cusr  
> 0.75 csys =  8.43 CPU)
> Result: FAIL
> Failed 1/12 test programs. 0/201 subtests failed.
> dh_auto_test: perl Build test --verbose 1 --test_files=t/21-new.t t/24-info.t 
> t/author-pod-coverage.t t/00-compile.t t/author-pod-syntax.t 
> t/30-collection.t t/22-general.t t/25-settings.t t/00-report-prereqs.t 
> t/26-playback.t t/20-connection.t t/40-playlist.t returned exit code 255
> debian/rules:10: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/libaudio-mpd-perl_2.004-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: libaudio-mpd-perl
Source-Version: 2.004-2

We believe that the bug you reported is fixed in the latest version of
libaudio-mpd-perl, 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.
gregor herrmann  (supplier of updated libaudio-mpd-perl 
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: Sun, 11 Dec 2016 17:46:04 +0100
Source: libaudio-mpd-perl
Binary: libaudio-mpd-perl
Architecture: source
Version: 2.004-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 846721
Description: 
 libaudio-mpd-perl - module to communicate with MPD servers
Changes:
 libaudio-mpd-perl (2.004-2) unstable; urgency=medium
 .
   * debian/upstream/metadata: use HTTPS for GitHub URLs.
   * Remove Jonathan Yu from Uploaders. Thanks for your work!
   * Remove Jose Luis Rivas from Uploaders. Thanks for your work!
   * Remove Rene Mayorga from Uploaders. Thanks for your work!
   * Skip t/40-playlist.t during build and autopkgtest. (Closes: #846721)
Checksums-Sha1: 
 ca523784231979e54fb730dd963a0ae422b50e80 2699 libaudio-mpd-perl_2.004-2.dsc
 8ed211c9015d7c3b2c595110a80a978620f6231e 5820 
libaudio-mpd-perl_2.004-2.debian.tar.xz
Checksums-Sha256: 
 480118d08168620af0c5c6a669bac230e022b762f64943c5dd44fe4c746aaab8 2699 
libaudio-mpd-perl_2.004-2.dsc
 0ee79b511d0f3ff5fc5554ac91bb247205c58b2d52d6dec586afa9d88b2149c3 5820 
libaudio-mpd-perl_2.004-2.debian.tar.xz
Files: 
 12a35a4fe0fcba0e06c73a10c1bd8e2b 2699 perl optional 
libaudio-mpd-perl_2.004-2.dsc
 4fe62e916fe57f5e03620166331fdb5f 5820 perl optional 
libaudio-mpd-perl_2.004-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlhNg4VfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ

Bug#811588: grail: diff for NMU version 3.1.0-2.1

[Sean Whitton]

Control: tags 811588 + patch

Dear maintainer,

I've prepared an NMU for grail (versioned as 3.1.0-2.1) and
submitted a request for sponsorship to have it uploaded.

Regards.

-- 
Sean Whitton
diff -Nru grail-3.1.0/debian/changelog grail-3.1.0/debian/changelog
--- grail-3.1.0/debian/changelog	2013-05-27 09:44:36.0 -0700
+++ grail-3.1.0/debian/changelog	2016-12-11 09:45:37.0 -0700
@@ -1,3 +1,10 @@
+grail (3.1.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply upstream revision 257 to fix misleading indentation (Closes: #811588).
+
+ -- Sean Whitton   Sun, 11 Dec 2016 09:45:35 -0700
+
 grail (3.1.0-2) unstable; urgency=low
 
   * change target distribution to unstable
diff -Nru grail-3.1.0/debian/patches/fix-misleading-indentation grail-3.1.0/debian/patches/fix-misleading-indentation
--- grail-3.1.0/debian/patches/fix-misleading-indentation	1969-12-31 17:00:00.0 -0700
+++ grail-3.1.0/debian/patches/fix-misleading-indentation	2016-12-11 09:39:27.0 -0700
@@ -0,0 +1,29 @@
+From: Sean Whitton 
+Date: Sun, 11 Dec 2016 09:39:05 -0700
+X-Dgit-Generated: 3.1.0-2.1 be8ba38d6b13f9811ea9c9ae4be736ae11c2162e
+Subject: fix misleading indentation
+
+
+---
+
+--- grail-3.1.0.orig/tools/grail-test-atomic.c
 grail-3.1.0/tools/grail-test-atomic.c
+@@ -143,15 +143,16 @@ static void process_frame_events(UGHandl
+ print_device_added(frame_handle, event);
+ status = frame_event_get_property(event, UFEventPropertyDevice,
+   );
+-if (status != UFStatusSuccess)
++if (status != UFStatusSuccess) {
+   fprintf(stderr, "Error: failed to get device from event\n");
+-else
++} else {
+   subscribe(grail_handle, device, subscribe_window, subscriptions, 2,
+ 2);
+   subscribe(grail_handle, device, subscribe_window, subscriptions, 3,
+ 1);
+   subscribe(grail_handle, device, subscribe_window, subscriptions, 4,
+ 1);
++}
+ break;
+   }
+ 
diff -Nru grail-3.1.0/debian/patches/series grail-3.1.0/debian/patches/series
--- grail-3.1.0/debian/patches/series	1969-12-31 17:00:00.0 -0700
+++ grail-3.1.0/debian/patches/series	2016-12-11 09:39:27.0 -0700
@@ -0,0 +1 @@
+fix-misleading-indentation


signature.asc
Description: PGP signature

Processed: grail: diff for NMU version 3.1.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 811588 + patch
Bug #811588 [grail] FTBFS with GCC 6: statement indented as if it were guarded 
by
Added tag(s) patch.

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

Bug#846721: Pending fixes for bugs in the libaudio-mpd-perl package

[pkg-perl-maintainers]

tag 846721 + pending
thanks

Some bugs in the libaudio-mpd-perl package are closed in revision
c306ae4beea98d84cb5688cc932d79577d17b4e4 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libaudio-mpd-perl.git/commit/?id=c306ae4

Commit message:

Skip t/40-playlist.t during build and autopkgtest.

Closes: #846721

Bug#847157: marked as done (gitlab: CVE-2016-9469)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 16:48:39 +
with message-id 
and subject line Bug#847157: fixed in gitlab 8.13.6+dfsg2-2
has caused the Debian Bug report #847157,
regarding gitlab: CVE-2016-9469
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.)


-- 
847157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 8.13.6+dfsg2-2

We believe that the bug you reported is fixed in the latest version of
gitlab, 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.
Pirate Praveen  (supplier of updated gitlab 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: Sun, 11 Dec 2016 22:06:59 +0530
Source: gitlab
Binary: gitlab
Architecture: source
Version: 8.13.6+dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code
Closes: 847114 847157 847337 847420
Changes:
 gitlab (8.13.6+dfsg2-2) unstable; urgency=medium
 .
   * Add patch cve-2016-9469.diff (Fixes: CVE-2016-9469) (Closes: #847157)
   * Use ruby-jquery-ui-rails 6 (Closes: #847337)
   * Enable more tests
   * Use -C for specifing sidekiq queues, Thanks to Justin F. Hallett
 (Closes: #847114)
   * Add dpkg trigger to refresh Gemfile.lock if a dependency is changed
 (Closes: #847420)
Checksums-Sha1:
 a1b5f705ca29a95baacef0b6c330fe9aa64b47c8 2492 gitlab_8.13.6+dfsg2-2.dsc
 e2bf3a0b3201918d5b6b9c3191156bea24aaf8c6 45140 
gitlab_8.13.6+dfsg2-2.debian.tar.xz
Checksums-Sha256:
 0c2afd62c76495b2b35d7ae229b11b049246cb1528440d21c5eb3f0f167b7c1c 2492 
gitlab_8.13.6+dfsg2-2.dsc
 6acb1cb34c3c93db5872b42086deb4fa08f0ed319084f2bb509e4a1876e80f9a 45140 
gitlab_8.13.6+dfsg2-2.debian.tar.xz
Files:
 ee22558032bccd6c83ad79468fb3bb93 2492 ruby optional gitlab_8.13.6+dfsg2-2.dsc
 c7446213e1bb822827860ea4d83fbb9d 45140 ruby optional 
gitlab_8.13.6+dfsg2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlhNgOMACgkQzh+cZ0US
wiqi8xAAs4QV4+V5Mjar42iXjY2eqSVTVB2uYmqvgkYYA+mr9ItUV3w/sXbO7+gK
RoMMKydVMO1wP0GIvfQJ30Ue64+ga7+ChCUO8J2fnmOSdd/gVRnyafpWRsLpAvON
J216zP/BDtWS4+0h+X1IqpWP9BGieMV1ngC4FplOtKRnarTm+symB3YP4K322Gny
sjzQASxM02M4hG9iScY/Yn47VwjKifiqPrVi25pYv61WNdIJKHnf597WGrqNSicY
JEPNHdRFLFGlQjEBH26s9H/3VMHKI+YCbp8yccNPa2yfH+bfM9ALp5TkkaEcGIpn
AH5TTX5xslR6hWYlVB8wkEC5Mav1C+c83ZnOeI5v5ZHrLP+JcnnXW+9IRclYTHxc
3lwzbdMGlXaUN9sTFU0J3u9nAdnIahZ6/0Zs5hKnxnuLwgYfmFQRzJyf4VK8YgRh
G0caaOWgUbr5AI6g5CMFer5WoPQoQ8PSh3QOq1c8ZwoKUEOb6sNTDACpsbbwcfKY
57URpBEx2s9qjzSoM71EwcKTTS0ody/DO3DEpt8QiYWG6jmWM9uoWRnxgAh+Ran1
M7awoc95DxRRT8GtmOJ73o7mbaNsWivV2k0FW8i3Mh4NJam5ILd8ARfF2bu/oz5B
NsWzcH7gXRM8qrbCb1qUW6KipnPdkVo38mOVNgFHbVyTKfgK/zE=
=kYhn
-END PGP SIGNATURE End Message ---

Processed: Pending fixes for bugs in the libaudio-mpd-perl package

[Debian Bug Tracking System]

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

> tag 846721 + pending
Bug #846721 [src:libaudio-mpd-perl] libaudio-mpd-perl: FTBFS: Test failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#846782: Re: Bug#846144: gobject-introspection randomly hangs liferea build

[Emilio Pozuelo Monfort]

On 09/12/16 14:51, Paul Gevers wrote:
> Hi,
> 
> On 09-12-16 00:31, Emilio Pozuelo Monfort wrote:
>> Just attach to it with gdb when it is hanged, then get the backtrace.
> 
> I did what you said above. Please find the backtrace attached.
> 
> paul@testavoira ~ $ ps aux | grep 32485
> paul 32485  0.0  0.6 1660456 33340 pts/2   Sl+  14:37   0:00
> /usr/bin/liferea
> --introspect-dump=/tmp/tmp-introspect_2fl6pjm/functions.txt,/tmp/tmp-introspect_2fl6pjm/dump.xml
> 
> I assume this is more interesting with debugging symbols of webkit
> installed as well, right? Unfortunately, it seems they are still not
> available in stretch, and I haven't been successful yet in connecting
> properly with the hanging process my pbuilder environment. So I ran
> g-ir-scanner.sh instead in stretch against a fresh created liferea (in sid).

They should be available in stretch:

emilio@tatooine:~$ apt-cache madison libwebkit2gtk-4.0-37-dbgsym 
libjavascriptcoregtk-4.0-18-dbgsym 
libwebkit2gtk-4.0-37-dbgsym |   2.14.2-1 | 
http://debug.mirrors.debian.org/debian-debug testing-debug/main amd64 Packages
libwebkit2gtk-4.0-37-dbgsym |   2.14.2-1 | 
http://debug.mirrors.debian.org/debian-debug unstable-debug/main amd64 Packages
libjavascriptcoregtk-4.0-18-dbgsym |   2.14.2-1 | 
http://debug.mirrors.debian.org/debian-debug testing-debug/main amd64 Packages
libjavascriptcoregtk-4.0-18-dbgsym |   2.14.2-1 | 
http://debug.mirrors.debian.org/debian-debug unstable-debug/main amd64 Packages

Can you install those and get a new trace, this time running

(gdb) thread apply all backtrace

Thanks,
Emilio

Bug#846961: marked as done (generate app directory using rake task)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 16:50:10 +
with message-id 
and subject line Bug#846961: fixed in ruby-jquery-ui-rails 6.0.1+dfsg-1
has caused the Debian Bug report #846961,
regarding generate app directory using rake task
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.)


-- 
846961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: grave
Justification: renders package unusable

Hi,

this issue happens on a vanilla installation of gitlab on a Debian
Stretch system. Since the problem occurs without any custom
configuration from my side, I deemed this issue to happen for all users
of the gitlab package and thus the severity.

Essentially, the dropdown menus stopped working. This includes:

 - the user menu dropdown on the upper-right
 - the project settings dropdown on the right below
 - the repository clone method dropdown
 - the repository dropdown on the upper-left
 - the download option dropdown
 - the notification dropdown

I judge these elements being dysfunctional to render the package
unusable.

To allow you to investigate the problem, I packed up the rootfs of the
machine I installed this onto. This rootfs is freshly generated and will
not be used in production, so there are no secrets in it.

The only gitlab user is root with the password 12345678.

You can also convince yourself of the problem by looking at this system
running live. For this, just enter the following into your /etc/hosts:

62.75.219.30 gitlab.mister-muffin.de

And then browse to https://gitlab.mister-muffin.de

You can log into the gitlab web interface with the credentials given
above.

For log and configuration files, list of installed packages etc, please
consult the tarball of the whole system here:

https://mister-muffin.de/gitlab_vanilla.tar.xz

To create this setup, I ran in a fresh chroot:

apt-get install --no-install-recommends gitlab msmtp-mta

No further configuration was carried out from my side. I used msmtp-mta
to prevent the bloat of postfix as a provider of mail-transport-agent. I
expect this choice to have no influence on the problem at hand.

I suspected that there might be a problem because I installed with
--no-install-recommends but running the following resulted in the same
behaviour:

apt-get install --install-recommends gitlab msmtp-mta certbot-

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: ruby-jquery-ui-rails
Source-Version: 6.0.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
ruby-jquery-ui-rails, 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.
Pirate Praveen  (supplier of updated ruby-jquery-ui-rails 
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: Sun, 11 Dec 2016 22:01:48 +0530
Source: ruby-jquery-ui-rails
Binary: ruby-jquery-ui-rails
Architecture: source
Version: 6.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-jquery-ui-rails - jQuery UI packaged for the Rails asset pipeline
Closes: 846961
Changes:
 ruby-jquery-ui-rails (6.0.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream release (move to jquery-ui 1.12.1)
   * Generate app directory from node-jquery-ui (Closes: #846961)
Checksums-Sha1:
 0f109bd39fff882d9009452b8ec77879b369d3dc 2223 
ruby-jquery-ui-rails_6.0.1+dfsg-1.dsc
 a64490bea9d296fad567083b3cefb7275140abfd 9276 
ruby-jquery-ui-rails_6.0.1+dfsg.orig.tar.gz
 d5a857a32f240ce677aab51aebcbc7a9185072a0 3500 
ruby-jquery-ui-rails_6.0.1+dfsg-1.debian.tar.xz
Checksums-Sha256:
 b6aaa68a831f4e054e3dd4402ea0cea7281e6d82669bd7656caffad9ee947edd 2223 
ruby-jquery-ui-rails_6.0.1+dfsg-1.dsc
 00ac3776e7c024e6401fea916f4dff0034c5a1aafeff50c3e4fd5668e95b0169 9276 
ruby-jquery-ui-rails_6.0.1+dfsg.orig.tar.gz
 

Bug#846731: Pending fixes for bugs in the libbio-scf-perl package

[pkg-perl-maintainers]

tag 846731 + pending
tag 775434 + pending
thanks

Some bugs in the libbio-scf-perl package are closed in revision
32fefbc45861aaac1f26e7dc2b6b67118e09abb8 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libbio-scf-perl.git/commit/?id=32fefbc

Commit message:

Add patch 0001-Fix-overflowing-casts-from-pointer-to-integer.patch.

Thanks: Niko Tyni for coming up with the patch.
Closes: #846731, #775434

Processed: Pending fixes for bugs in the libbio-scf-perl package

[Debian Bug Tracking System]

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

> tag 846731 + pending
Bug #846731 [src:libbio-scf-perl] libbio-scf-perl: FTBFS: Test failures
Added tag(s) pending.
> tag 775434 + pending
Bug #775434 [src:libbio-scf-perl] libbio-scf-perl: FTBFS on mips64el, ppc64el, 
s390x - tests
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: owner 811588

[Debian Bug Tracking System]

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

> owner 811588 !
Bug #811588 [grail] FTBFS with GCC 6: statement indented as if it were guarded 
by
Owner recorded as Sean Whitton .
> thanks
Stopping processing here.

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

Bug#847741: marked as done (ruby-bunny: FTBFS: Bunny::Session initialized via connection URI handles amqp:// URIs w/o path part)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 16:35:21 +
with message-id 
and subject line Bug#847741: fixed in ruby-bunny 2.6.1-2
has caused the Debian Bug report #847741,
regarding ruby-bunny: FTBFS: Bunny::Session initialized via connection URI 
handles amqp:// URIs w/o path part
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.)


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

ruby-bunny fails to build from source in unstable/amd64:

  […]

  Bunny::Exchange
recovery
  recovers exchange bindings, unless already unbound
  
  Bunny::VersionedDeliveryTag#stale?
when delivery tag version < provided version
  returns true
when delivery tag version = provided version
  returns false
when delivery tag version > provided version
  returns true
  
  Failures:
  
1) Bunny::Session initialized via connection URI handles amqp:// URIs w/o 
path part
   Failure/Error: @origin_thread.raise(e)
  
   Bunny::NotAllowedError:
 Connection-level error: NOT_ALLOWED - access to vhost '/' refused for 
user 'guest'
   # ./lib/bunny/session.rb:1157:in `raise'
   # ./lib/bunny/session.rb:1157:in `open_connection'
   # ./lib/bunny/session.rb:304:in `start'
   # ./spec/higher_level_api/integration/connection_spec.rb:24:in `block (3 
levels) in '
  
2) Bunny::Session initialized with all defaults provides a way to fine tune 
socket options
   Failure/Error: @origin_thread.raise(e)
  
   Bunny::NotAllowedError:
 Connection-level error: NOT_ALLOWED - access to vhost '/' refused for 
user 'guest'
   # ./lib/bunny/session.rb:1157:in `raise'
   # ./lib/bunny/session.rb:1157:in `open_connection'
   # ./lib/bunny/session.rb:304:in `start'
   # ./spec/higher_level_api/integration/connection_spec.rb:54:in `block (3 
levels) in '
  
3) Bunny::Session initialized with all defaults successfully negotiates the 
connection
   Failure/Error: @origin_thread.raise(e)
  
   Bunny::NotAllowedError:
 Connection-level error: NOT_ALLOWED - access to vhost '/' refused for 
user 'guest'
   # ./lib/bunny/session.rb:1157:in `raise'
   # ./lib/bunny/session.rb:1157:in `open_connection'
   # ./lib/bunny/session.rb:304:in `start'
   # ./spec/higher_level_api/integration/connection_spec.rb:62:in `block (3 
levels) in '
  
4) Bunny::Session initialized with TCP connection timeout = 5 successfully 
connects
   Failure/Error: @origin_thread.raise(e)
  
   Bunny::NotAllowedError:
 Connection-level error: NOT_ALLOWED - access to vhost '/' refused for 
user 'guest'
   # ./lib/bunny/session.rb:1157:in `raise'
   # ./lib/bunny/session.rb:1157:in `open_connection'
   # ./lib/bunny/session.rb:304:in `start'
   # ./spec/higher_level_api/integration/connection_spec.rb:82:in `block (3 
levels) in '
  
5) Bunny::Session initialized with :channel_max => 4096 negotiates channel 
max to be 1024
   Failure/Error: @origin_thread.raise(e)
  
   Bunny::NotAllowedError:
 Connection-level error: NOT_ALLOWED - access to vhost '/' refused for 
user 'guest'
   # ./lib/bunny/session.rb:1157:in `raise'
   # ./lib/bunny/session.rb:1157:in `open_connection'
   # ./lib/bunny/session.rb:304:in `start'
   # ./spec/higher_level_api/integration/connection_spec.rb:310:in `block 
(3 levels) in '
  
6) Bunny::Session initialized with a custom logger object uses provided 
logger
   Failure/Error: @origin_thread.raise(e)
  
   Bunny::NotAllowedError:
 Connection-level error: NOT_ALLOWED - access to vhost '/' refused for 
user 'guest'
   # ./lib/bunny/session.rb:1157:in `raise'
   # ./lib/bunny/session.rb:1157:in `open_connection'
   # ./lib/bunny/session.rb:304:in `start'
   # ./spec/higher_level_api/integration/connection_spec.rb:548:in `block 
(3 levels) in '
  
7) A server-named Bunny::Queue can be bound to a pre-declared exchange
   Failure/Error: @origin_thread.raise(e)
  
   Bunny::NotAllowedError:
 Connection-level error: NOT_ALLOWED - access to vhost '/' refused for 
user 'guest'
   # ./lib/bunny/session.rb:1157:in `raise'
   # ./lib/bunny/session.rb:1157:in `open_connection'
   

Bug#847757: testdisk FTBFS on mips: common.h:128:2: error: initializer element is not constant

[Christophe GRENIER]

On Sun, 11 Dec 2016, Adrian Bunk wrote:


Source: testdisk
Version: 7.0-2
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=testdisk=mips

...
In file included from partgpt.c:45:0:
common.h:128:2: error: initializer element is not constant
 
((efi_guid_t){le32(0x516e7cb4),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
 ^
partgpt.c:80:5: note: in expansion of macro 'GPT_ENT_TYPE_FREEBSD'
  { GPT_ENT_TYPE_FREEBSD,  "FreeBSD"  },
^~~~
common.h:128:2: note: (near initialization for 'gpt_sys_types[2].part_type')
 
((efi_guid_t){le32(0x516e7cb4),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
 ^
partgpt.c:80:5: note: in expansion of macro 'GPT_ENT_TYPE_FREEBSD'
  { GPT_ENT_TYPE_FREEBSD,  "FreeBSD"  },
^~~~
...


Is the compilation fixed if "const efi_guid_t" is used ?
See patch in attachment.
Regards,
Christophe
--
   ,-~~-.___. ._.
  / |  ' \| |.   Christophe GRENIER
 (  ) 0   | || gren...@cgsecurity.org
  \_/-, ,'| ||
  !_!-v---v--.
 /  \-'~;  ..   TestDisk & PhotoRec
/  __/~| ._-""|||   Data Recovery
  =(  _|_||||   https://www.cgsecurity.orgdiff -ru testdisk/src/common.h ../testdisk-7.1-WIP/src/common.h
--- testdisk/src/common.h   2016-01-23 09:35:54.053059545 +0100
+++ ../testdisk-7.1-WIP/src/common.h2016-12-11 15:41:40.594247811 +0100
@@ -119,97 +119,97 @@
 #define PXBOX_FATX 1
 
 #defineGPT_ENT_TYPE_UNUSED \
-   
((efi_guid_t){le32(0x),le16(0x),le16(0x),0x00,0x00,{0x00,0x00,0x00,0x00,0x00,0x00}})
+   ((const 
efi_guid_t){le32(0x),le16(0x),le16(0x),0x00,0x00,{0x00,0x00,0x00,0x00,0x00,0x00}})
 #defineGPT_ENT_TYPE_EFI\
-   
((efi_guid_t){le32(0xc12a7328),le16(0xf81f),le16(0x11d2),0xba,0x4b,{0x00,0xa0,0xc9,0x3e,0xc9,0x3b}})
+   ((const 
efi_guid_t){le32(0xc12a7328),le16(0xf81f),le16(0x11d2),0xba,0x4b,{0x00,0xa0,0xc9,0x3e,0xc9,0x3b}})
 #defineGPT_ENT_TYPE_MBR\
-   
((efi_guid_t){le32(0x024dee41),le16(0x33e7),le16(0x11d3),0x9d,0x69,{0x00,0x08,0xc7,0x81,0xf3,0x9f}})
+   ((const 
efi_guid_t){le32(0x024dee41),le16(0x33e7),le16(0x11d3),0x9d,0x69,{0x00,0x08,0xc7,0x81,0xf3,0x9f}})
 #defineGPT_ENT_TYPE_FREEBSD\
-   
((efi_guid_t){le32(0x516e7cb4),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
+   ((const 
efi_guid_t){le32(0x516e7cb4),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
 #defineGPT_ENT_TYPE_FREEBSD_SWAP   \
-   
((efi_guid_t){le32(0x516e7cb5),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
+   ((const 
efi_guid_t){le32(0x516e7cb5),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
 #defineGPT_ENT_TYPE_FREEBSD_UFS\
-   
((efi_guid_t){le32(0x516e7cb6),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
+   ((const 
efi_guid_t){le32(0x516e7cb6),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
 #define GPT_ENT_TYPE_FREEBSD_ZFS   \
-   
((efi_guid_t){le32(0x516e7cb),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
+   ((const 
efi_guid_t){le32(0x516e7cb),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
 /*
  * The following is unused but documented here to avoid reuse.
  *
  * GPT_ENT_TYPE_FREEBSD_UFS2   \
- * 
((efi_guid_t){le32(0x516e7cb7),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
+ * ((const 
efi_guid_t){le32(0x516e7cb7),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
  */
 
 #defineGPT_ENT_TYPE_FREEBSD_VINUM  \
-   
((efi_guid_t){le32(0x516e7cb8),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
+   ((const 
efi_guid_t){le32(0x516e7cb8),le16(0x6ecf),le16(0x11d6),0x8f,0xf8,{0x00,0x02,0x2d,0x09,0x71,0x2b}})
 
 
 #defineGPT_ENT_TYPE_MS_RESERVED\
-   
((efi_guid_t){le32(0xe3c9e316),le16(0x0b5c),le16(0x4db8),0x81,0x7d,{0xf9,0x2d,0xf0,0x02,0x15,0xae}})
+   ((const 
efi_guid_t){le32(0xe3c9e316),le16(0x0b5c),le16(0x4db8),0x81,0x7d,{0xf9,0x2d,0xf0,0x02,0x15,0xae}})
 #defineGPT_ENT_TYPE_MS_BASIC_DATA  \
-   
((efi_guid_t){le32(0xebd0a0a2),le16(0xb9e5),le16(0x4433),0x87,0xc0,{0x68,0xb6,0xb7,0x26,0x99,0xc7}})
+   ((const 
efi_guid_t){le32(0xebd0a0a2),le16(0xb9e5),le16(0x4433),0x87,0xc0,{0x68,0xb6,0xb7,0x26,0x99,0xc7}})
 #defineGPT_ENT_TYPE_MS_LDM_METADATA\
-   
((efi_guid_t){le32(0x5808c8aa),le16(0x7e8f),le16(0x42e0),0x85,0xd2,{0xe1,0xe9,0x04,0x34,0xcf,0xb3}})
+   ((const 
efi_guid_t){le32(0x5808c8aa),le16(0x7e8f),le16(0x42e0),0x85,0xd2,{0xe1,0xe9,0x04,0x34,0xcf,0xb3}})
 #defineGPT_ENT_TYPE_MS_LDM_DATA\
-   

Bug#828608: Building with OpenSSL 1.0.2 is sufficient for stretch

[Ferenc Wágner]

Control: tags -1 + patch

Adrian Bunk  writes:

> On Sun, Dec 11, 2016 at 03:13:58PM +0100, Ferenc Wágner wrote:
>
>> Adrian Bunk  writes:
>> 
>>> Not a perfect solution but sufficient for stretch is the patch below to 
>>> use OpenSSL 1.0.2
>>> [...]
>>>   libcurl4-openssl-dev,
>>>   liblog4shib-dev,
>>> - libssl-dev,
>>> + libssl1.0-dev | libssl-dev (<< 1.1.0~),
>> 
>> As previously established in this bug report, XMLTooling and cURL must
>> use the same OpenSSL version, because they exchange SSL_CTX pointers.
>> I think the only sensible way out would be introducing an OpenSSL 1.0
>> flavour of curl, and build-depending on libcurl4-openssl1.0-dev here.
>> See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844263.
>
> Having two different OpenSSL flavours of curl would open a whole new set 
> of problems, like what happens when a binary ends up linking both.
>
> Also note that due to the freeze deadlines any solution must be
> in a non-RC state in unstable before Christmas, to allow packages
> like moonshot-gss-eap to re-enter testing before January 5th.
>
> The best available solution is to force all r-(b)deps of libcurl4
> to stay at 1.0.2 for stretch:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844018#10
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844018#69

Do you mean that curl itself will stay with OpenSSL 1.0 in stretch?  I
haven't noticed this decision, but I'm certainly happy with it.  Sorry,
your patch is correct then.  Shall I upload ASAP, or wait for the
switchover in curl?
-- 
Feri

Processed: Re: Bug#828608: Building with OpenSSL 1.0.2 is sufficient for stretch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #828608 [src:xmltooling] xmltooling: FTBFS with openssl 1.1.0
Bug #844815 [src:xmltooling] moonshot-gss-eap: FTBFS: build-dependency not 
installable: libshibsp-dev (>= 2.5+dfsg~moonshot5)
Bug #844836 [src:xmltooling] xmltooling: FTBFS: build-dependency not 
installable: libxml-security-c-dev (>= 1.7.3-3)
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.

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

Bug#847353: marked as done (provide node-jquery-ui to build ruby-jquery-ui-rails)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 16:00:13 +
with message-id 
and subject line Bug#847353: fixed in jqueryui 1.12.1+dfsg-3
has caused the Debian Bug report #847353,
regarding provide node-jquery-ui to build ruby-jquery-ui-rails
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.)


-- 
847353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: grave
Justification: renders package unusable

Hi,

this issue happens on a vanilla installation of gitlab on a Debian
Stretch system. Since the problem occurs without any custom
configuration from my side, I deemed this issue to happen for all users
of the gitlab package and thus the severity.

Essentially, the dropdown menus stopped working. This includes:

 - the user menu dropdown on the upper-right
 - the project settings dropdown on the right below
 - the repository clone method dropdown
 - the repository dropdown on the upper-left
 - the download option dropdown
 - the notification dropdown

I judge these elements being dysfunctional to render the package
unusable.

To allow you to investigate the problem, I packed up the rootfs of the
machine I installed this onto. This rootfs is freshly generated and will
not be used in production, so there are no secrets in it.

The only gitlab user is root with the password 12345678.

You can also convince yourself of the problem by looking at this system
running live. For this, just enter the following into your /etc/hosts:

62.75.219.30 gitlab.mister-muffin.de

And then browse to https://gitlab.mister-muffin.de

You can log into the gitlab web interface with the credentials given
above.

For log and configuration files, list of installed packages etc, please
consult the tarball of the whole system here:

https://mister-muffin.de/gitlab_vanilla.tar.xz

To create this setup, I ran in a fresh chroot:

apt-get install --no-install-recommends gitlab msmtp-mta

No further configuration was carried out from my side. I used msmtp-mta
to prevent the bloat of postfix as a provider of mail-transport-agent. I
expect this choice to have no influence on the problem at hand.

I suspected that there might be a problem because I installed with
--no-install-recommends but running the following resulted in the same
behaviour:

apt-get install --install-recommends gitlab msmtp-mta certbot-

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: jqueryui
Source-Version: 1.12.1+dfsg-3

We believe that the bug you reported is fixed in the latest version of
jqueryui, 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.
Pirate Praveen  (supplier of updated jqueryui 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: Thu, 08 Dec 2016 13:29:28 +0530
Source: jqueryui
Binary: libjs-jquery-ui libjs-jquery-ui-docs node-jquery-ui
Architecture: source all
Version: 1.12.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 libjs-jquery-ui - JavaScript UI library for dynamic web applications
 libjs-jquery-ui-docs - Documentation for JQuery-UI
 node-jquery-ui - JavaScript UI library for dynamic web applications (NodeJs)
Closes: 847353
Changes:
 jqueryui (1.12.1+dfsg-3) unstable; urgency=medium
 .
   * Provide node-jquery-ui (Closes: #847353)
   * Add minimum version of node-requirejs as 2.3.2
(r.js is now /usr/lib/nodejs/requirejs/r.js)
   * Add myself to uploaders
Checksums-Sha1:
 3bd536dc3296f2382090c9937f1cdff5809df38e 2261 jqueryui_1.12.1+dfsg-3.dsc
 15dbf4ac5a7ba2f942788e21b9b2281813d08204 124644 
jqueryui_1.12.1+dfsg-3.debian.tar.xz
 c16d64150980de63e76b8dfd618408716f05e49f 8754 
jqueryui_1.12.1+dfsg-3_amd64.buildinfo
 b3c1da06dd6afaff319f976f9b6dbfac094c28a4 339340 
libjs-jquery-ui-docs_1.12.1+dfsg-3_all.deb
 8bdafb7eae87caadbc765320e883ac197674f00c 232132 

Bug#828586: Building with OpenSSL 1.0.2 is sufficient for stretch

[Jose Luis Tallon]

On 12/11/2016 12:58 AM, Adrian Bunk wrote:
> Not a perfect solution but sufficient for stretch is the patch below to 
> use OpenSSL 1.0.2

Thank you for the patch!

Richard Laager has been preparing a new version, including all pending
patches. CC'ing him so that we keep synchronized.
Tony Mancill has agreed to sponsor that upload.

> The "| libssl-dev (<< 1.1.0~)" is added for backports.
>
> --- debian/control.old2016-12-10 23:57:31.0 +
> +++ debian/control2016-12-10 23:57:36.0 +
> @@ -3,7 +3,7 @@
>  Priority: optional
>  Maintainer: Jose Luis Tallon 
>  Build-Depends: autotools-dev, debhelper (>= 5), po-debconf (>= 0.8.2), 
> - libwrap0-dev, libncurses-dev, libssl-dev, dh-systemd
> + libwrap0-dev, libncurses-dev, libssl1.0-dev | libssl-dev (<< 1.1.0~), 
> dh-systemd
>  Homepage: http://www.imapproxy.org
>  Standards-Version: 3.8.4
>  
>
>
> cu
> Adrian
>

Bug#784619: creepy: Qt5 conversion in progress

[Petter Reinholdtsen]

[Ross Gammon]
> I have spent the day doing the Qt4 > Qt5 conversion following the tips
> from Dmitry. See the latest on alioth.

Wow.  I had given up rescuing creepy for stretch, but your email bring
me new hope.

> Unfortunately, I get an import error when running creepy after installation:
> $ creepy -v
> Traceback (most recent call last):
>   File "/usr/bin/creepy", line 14, in 
> from PyQt5.QtCore import QString, QThread, SIGNAL, QUrl, QDateTime, 
> QDate, QRect, Qt
> ImportError: cannot import name QString

I have vague memories of QString moving to somewhere else.  A quick
check indicate that PyQt5 now uses python strings instead.  Perhaps just
dropping QString is the correct approach?

-- 
Happy hacking
Petter Reinholdtsen

Bug#847612: marked as done (monitoring-plugins-basic lost OpenSSL support)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 15:49:32 +
with message-id 
and subject line Bug#847612: fixed in monitoring-plugins 2.2-2
has caused the Debian Bug report #847612,
regarding monitoring-plugins-basic lost OpenSSL support
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.)


-- 
847612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: monitoring-plugins-basic
Version: 2.2-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=monitoring-plugins=amd64=2.2-1=1481212864

...

checking openssl/ssl.h usability... no
checking openssl/ssl.h presence... no
checking for openssl/ssl.h... no
checking openssl/x509.h usability... no
checking openssl/x509.h presence... no
checking for openssl/x509.h... no
checking openssl/rsa.h usability... no
checking openssl/rsa.h presence... no
checking for openssl/rsa.h... no
checking openssl/pem.h usability... no
checking openssl/pem.h presence... no
checking for openssl/pem.h... no
checking openssl/crypto.h usability... no
checking openssl/crypto.h presence... no
checking for openssl/crypto.h... no
checking openssl/err.h usability... no
checking openssl/err.h presence... no
checking for openssl/err.h... no
checking ssl.h usability... no
checking ssl.h presence... no
checking for ssl.h... no
checking x509.h usability... no
checking x509.h presence... no
checking for x509.h... no
checking rsa.h usability... no
checking rsa.h presence... no
checking for rsa.h... no
checking pem.h usability... no
checking pem.h presence... no
checking for pem.h... no
checking crypto.h usability... no
checking crypto.h presence... no
checking for crypto.h... no
checking err.h usability... yes
checking err.h presence... yes
checking for err.h... yes
checking for CRYPTO_new_ex_data in -lcrypto... no
configure: WARNING: OpenSSL or GnuTLS libs could not be found or were disabled
...



The package must again build-depend on either libssl1.0-dev or libssl-dev
for getting OpenSSL support back.
--- End Message ---
--- Begin Message ---
Source: monitoring-plugins
Source-Version: 2.2-2

We believe that the bug you reported is fixed in the latest version of
monitoring-plugins, 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.
Jan Wagner  (supplier of updated monitoring-plugins 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: Sun, 11 Dec 2016 16:17:18 +0100
Source: monitoring-plugins
Binary: monitoring-plugins monitoring-plugins-common monitoring-plugins-basic 
monitoring-plugins-standard nagios-plugins nagios-plugins-common 
nagios-plugins-basic nagios-plugins-standard
Architecture: source i386 all
Version: 2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Jan Wagner 
Description:
 monitoring-plugins - Plugins for nagios compatible monitoring systems 
(metapackage)
 monitoring-plugins-basic - Plugins for nagios compatible monitoring systems 
(basic)
 monitoring-plugins-common - Common files for plugins for nagios compatible 
monitoring
 monitoring-plugins-standard - Plugins for nagios compatible monitoring systems 
(standard)
 nagios-plugins - transitional dummy package (nagios-plugins to 
monitoring-plugins)
 nagios-plugins-basic - transitional dummy package
 nagios-plugins-common - transitional dummy package
 nagios-plugins-standard - transitional dummy package
Closes: 847612
Changes:
 monitoring-plugins (2.2-2) unstable; urgency=medium
 .
   * [627d88a] d/control: Explicit build-dep on libssl-dev or libssl1.0-dev
 (Closes: #847612)
Checksums-Sha1:
 49b42adf278376d547d94d66700c3550469836c2 2812 monitoring-plugins_2.2-2.dsc
 782ee59ed5be6136337cce32f48875fe8efba118 1590008 
monitoring-plugins_2.2.orig.tar.gz
 3a9936f4e5a1f958e4e01ddfbc8f9eb531c31a86 37464 
monitoring-plugins_2.2-2.debian.tar.xz
 ae0467115097b450f9c60c8ab9054ff68248ca41 1367830 
monitoring-plugins-basic-dbgsym_2.2-2_i386.deb
 

Bug#847542: #847542

[Michael Ott]

> > I installed libmozjs-24-0 24.2.0-5 and I have the same as on last
> > version. I have to downgrade to 24.2.0-3.1 and than it works again
> What architecture do you use?
AMD64
> Did you do a full update of your system?
Yes. I think so.

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

Kernel: Linux 4.8.0-2-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)

Versions of packages libmozjs-24-0 depends on:
ii  libc6   2.24-8
ii  libffi6 3.3~20160224-1
ii  libgcc1 1:7-20161201-1
ii  libnspr42:4.13.1-1
ii  libstdc++6  7-20161201-1

libmozjs-24-0 recommends no packages.

libmozjs-24-0 suggests no packages.


> Which application(s) fail and what error message may you get?
Restart the box and GDM does not start.

Dec 11 10:13:10 king-coder13 kernel: [   22.338631] traps: polkitd[1066] 
general protection ip:7fbf71af1bd1 sp:7ffcad43a550 error:0 in 
libmozjs185.so.1.0.0[7fbf719f2000+358000]
Dec 11 10:13:10 king-coder13 rtkit-daemon[1914]: Warning: PolicyKit call 
failed: Message recipient disconnected from message bus without replying
Dec 11 10:13:10 king-coder13 systemd[1]: polkit.service: Main process exited, 
code=killed, status=11/SEGV
Dec 11 10:13:10 king-coder13 systemd[1]: polkit.service: Unit entered failed 
state.
Dec 11 10:13:10 king-coder13 systemd[1]: polkit.service: Failed with result 
'signal'.


> If you use a graphical system, tried logout and login again with -5 installed?
This works when I start with 3.1 and then I upgrade to -5. I restart gdm
and then it works. But not when I restart the box

CU  
 
  Michael
  
-- 
,''`.   
   : :' :   Michael Ott 
   `. `'e-mail: michael at king-coder dot de
 `-

Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

Bug#800891: Please adjust the licensing of afex

[Andreas Tille]

Hi Henrik,

any news about a new version with fixed license.  As I said the issue is
a bit dense if we want to reach the next Debian stable version.

Kind regards

 Andreas.

On Wed, Nov 16, 2016 at 09:37:57AM +0100, Andreas Tille wrote:
> Hi Henrik,
> 
> On Tue, Nov 15, 2016 at 08:57:20PM +0100, Henrik Singmann wrote:
> > Hi Andreas, (this time with list in CC)
> > 
> > Thanks for warning me. And no problem. I will change to GPL2 in the next
> > release version. Can you give me some time to implement these changes and
> > others I have planned for the next release? Let's say 4 weeks?
> 
> As I said 4 weeks is a bit dense.  If you really manage in 4 weeks it
> might make it.  However, it is not my power to push any package after
> the freeze.
>  
> Kind regards
> 
>  Andreas.
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de

Processed: Proper version tracking

[Debian Bug Tracking System]

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

> reassign 839424 libmono-corlib4.5-cil
Bug #839424 {Done: Jo Shields } [src:mono-debugger-libs] 
mono-debugger-libs: FTBFS: System.IO.FileNotFoundException: Could not find file 
"/etc/localtime"
Bug reassigned from package 'src:mono-debugger-libs' to 'libmono-corlib4.5-cil'.
No longer marked as found in versions mono-debugger-libs/0+20131201.3459502-1.
No longer marked as fixed in versions mono/4.6.1.3+dfsg-2.
> fixed 839424 4.6.1.3+dfsg-1
Bug #839424 {Done: Jo Shields } [libmono-corlib4.5-cil] 
mono-debugger-libs: FTBFS: System.IO.FileNotFoundException: Could not find file 
"/etc/localtime"
Marked as fixed in versions mono/4.6.1.3+dfsg-1.
> close 839424
Bug #839424 {Done: Jo Shields } [libmono-corlib4.5-cil] 
mono-debugger-libs: FTBFS: System.IO.FileNotFoundException: Could not find file 
"/etc/localtime"
Bug 839424 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: Also add an affects

[Debian Bug Tracking System]

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

> affects 839424 src:mono-debugger-libs
Bug #839424 {Done: Jo Shields } [libmono-corlib4.5-cil] 
mono-debugger-libs: FTBFS: System.IO.FileNotFoundException: Could not find file 
"/etc/localtime"
Added indication that 839424 affects src:mono-debugger-libs
> thanks
Stopping processing here.

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

Bug#847740: marked as done (jquery: FTBFS: Error: Cannot find module '/usr/lib/nodejs/r.js')

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 15:33:52 +
with message-id 
and subject line Bug#847740: fixed in jquery 3.1.1-2
has caused the Debian Bug report #847740,
regarding jquery: FTBFS: Error: Cannot find module '/usr/lib/nodejs/r.js'
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.)


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

jquery fails to build from source in unstable/amd64:

  […]

 dh_auto_configure
 debian/rules override_dh_auto_build
  make[1]: Entering directory '«BUILDDIR»'
  sed -e '/^\/\*\s*eslint-/d; /^\/\/ @CODE/,$ d' src/wrapper.js > start.js || 
(rm -f start.js; false)
  sed -e '1,/^\/\/ @CODE/ d; /\/\/ build.js inserts compiled jQuery here/d' 
src/wrapper.js > end.js || (rm -f end.js; false)
  cp debian/build.js build.js
  nodejs /usr/lib/nodejs/r.js -o build.js
  module.js:327
  throw err;
  ^
  
  Error: Cannot find module '/usr/lib/nodejs/r.js'
  at Function.Module._resolveFilename (module.js:325:15)
  at Function.Module._load (module.js:276:25)
  at Function.Module.runMain (module.js:441:10)
  at startup (node.js:139:18)
  at node.js:974:3
  debian/rules:14: recipe for target 'dist/jquery.js' failed
  make[1]: *** [dist/jquery.js] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:40: recipe for target 'binary' failed
  make: *** [binary] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2

  […]

The full build log is attached.


Regards,

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


jquery.3.1.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: jquery
Source-Version: 3.1.1-2

We believe that the bug you reported is fixed in the latest version of
jquery, 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.
Antonio Terceiro  (supplier of updated jquery 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: Sun, 11 Dec 2016 13:18:53 -0200
Source: jquery
Binary: libjs-jquery
Architecture: source
Version: 3.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Antonio Terceiro 
Description:
 libjs-jquery - JavaScript library for dynamic web applications
Closes: 847740
Changes:
 jquery (3.1.1-2) unstable; urgency=medium
 .
   * debian/rules: adapt path to r.js after a change in nodejs-requirejs
 (Closes: #847740)
Checksums-Sha1:
 77b10d4514d4d04970686fa87b500f3c7112471f 2111 jquery_3.1.1-2.dsc
 2bcdf6f66df24b716fde06f9a2c052bbb4523fb0 8652 jquery_3.1.1-2.debian.tar.xz
Checksums-Sha256:
 55c20d0637a4d3fd17c5c4b4a47edbda930c06865023277cfad74ab23004dd0d 2111 
jquery_3.1.1-2.dsc
 53ef4bd5f274373099885467fc7aec725acca37eaf898bbf766715a161918cb7 8652 
jquery_3.1.1-2.debian.tar.xz
Files:
 8b812e89d064969e363a693d9fcca921 2111 web optional jquery_3.1.1-2.dsc
 50c34de4078a7534735f2bbc849fd27e 8652 web optional jquery_3.1.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlhNcCYACgkQ/A2xu81G
C94+mA//RrWimoQuBq07YwMuDLkqzWyhZSj2XmgTNjuwGPt0ALllAaAlbe94MI6V
9LNxTtmqaf5XEWs5vkGfa1Ul2zPC+q6aTNXNLCgZi3yXPhTHrCkNuUJFLT2Q1uxT
cOrKvu+ThlzgXXwV5KW2jSKEtMq1YEveI2DNyPk02nHvcFymgAaelEZ4wpT6XITU
yQpdVcAfZLQa8Uvvj4XbQGyGwElNzIqq2NajyAms4BpoIaX44aDqkLkOPDjEXCN/
/ztKxQui8ZDY1Vh2z9QJG9Kj2EryLOWWhoEcQYyufG24o/09LtBuMOVxs4+eAhcJ
BXMTMYyyQKlH846ZDymRJknwYxfz0EFoGf2HP0AyxQlKSpmh/Y/tq/R9i3uddMzE
Y1UllkGnCpNXDblwCy5o2cCOBslm40YJGQPaNjnsy6LIalpXi7im0MKX4UevAb0s
sl7Deh5N2XxCCC8wHKVoA3y2u/rwgTQQrlLUVS18KPG11x0wKNGTjAPZEM9Ic8o7

Bug#847612: [Pkg-nagios-devel] Bug#847612: monitoring-plugins-basic lost OpenSSL support

[Jan Wagner]

Hi Adrian,

Am 09.12.16 um 22:10 schrieb Adrian Bunk:
> configure: WARNING: OpenSSL or GnuTLS libs could not be found or were disabled

thanks for notifying. Seems that there was a change in depencies in
unstable (and testing) for some of the packages we were depending on. A
package with explicit dependency is on it's way.

Thanks, Jan.




signature.asc
Description: OpenPGP digital signature

Processed: block 833252 by 847774

[Debian Bug Tracking System]

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

> block 833252 by 847774
Bug #833252 [src:lbzip2] lbzip2: Uses obsolete compressor for .deb data.tar 
member
833252 was not blocked by any bugs.
833252 was not blocking any bugs.
Added blocking bug(s) of 833252: 847774
>
End of message, stopping processing here.

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

Bug#828608: Building with OpenSSL 1.0.2 is sufficient for stretch

[Adrian Bunk]

On Sun, Dec 11, 2016 at 03:13:58PM +0100, Ferenc Wágner wrote:
> Control: tags -1 - patch
> 
> Adrian Bunk  writes:
> 
> > Not a perfect solution but sufficient for stretch is the patch below to 
> > use OpenSSL 1.0.2
> > [...]
> >   libcurl4-openssl-dev,
> >   liblog4shib-dev,
> > - libssl-dev,
> > + libssl1.0-dev | libssl-dev (<< 1.1.0~),
> 
> As previously established in this bug report, XMLTooling and cURL must
> use the same OpenSSL version, because they exchange SSL_CTX pointers.
> I think the only sensible way out would be introducing an OpenSSL 1.0
> flavour of curl, and build-depending on libcurl4-openssl1.0-dev here.
> See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844263.

Having two different OpenSSL flavours of curl would open a whole new set 
of problems, like what happens when a binary ends up linking both.

Also note that due to the freeze deadlines any solution must be
in a non-RC state in unstable before Christmas, to allow packages
like moonshot-gss-eap to re-enter testing before January 5th.

The best available solution is to force all r-(b)deps of libcurl4
to stay at 1.0.2 for stretch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844018#10
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844018#69

> Regards,
> Feri

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#835746: fixed in odin-2.0.3: FTBFS: seqgradspiral.cpp:30:71: error: no matching function for call to 'max(double, float)'

[Michael Hanke]

Hi Thies,

I had a quick look at upgrading the package to 2.0.3. I am trying to
build against Qt5 (all the bdeps seem to be there), but the AC setup
does not acknowledge the presence of Qt5 in my test system.

Should this be working?

Thanks,

Michael


-- 
Michael Hanke
GPG: 4096R/C073D2287FFB9E9B
http://psychoinformatics.de

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

[Bill Blough]

On Sat, Dec 10, 2016 at 08:56:29AM +, Gianfranco Costamagna wrote:
> 
> >  libtool --mode=execute gdb --args samples/SAXCount 
> > samples/data/personal.xml
> > catch throw
> >
> >  bt full
> >continue
> > quit
> >This will hopefully help me to isolate this issue.
> >
> 
> 
> here we are!
> http://paste.debian.net/901516/

Thanks, looking into it.

Bug#828267: [Pkg-citadel-devel] Bug#828267: reopen, it is still valid

[Sebastian Andrzej Siewior]

control: merge -1 846543
On 2016-12-11 09:54:42 [+0100], Michael Meskes wrote:

> What are you trying to do here? Reopen 828267 and merge with itself?
> There is no other bug mentioned. What do I miss?
Yeah. Not very smart. I intended to merge it with 846543.

> > from the change [0] you use say that a compatible API is used but the
> > CFLAG change makes no sense. This is probably a miss understanding. 
> 
> Care to explain? The CFLAG change did make the package compile, install
> and run, so why reopen the bug?

The bug was created and it was mentioned that this package needs changes in
order to get it compiled against the new openssl ABI which is in experimental.
Your upload of the "fixed" package was performed on 2016-10-30 and was built
against openssl 1.0.2. So even if you would have done nothing, your package
would been built successfully *but* against a 1.0.2. The test should have been
done against the version in experimental.
On 2016-11-01 openssl 1.1.0 was uploaded to unstable. From this point in time
your package would have fail to build. So I *think* the change in the CFLAGS
is a nop.

> > You
> > have two choices:
> > ...
> 
> Says who? Again, without any explanation as to why, I don't see any
> reason to act.

So the bug was created because the package did not compile against openssl
1.1.0 and now #846543 was created which mostly a dupe of this one.

That means you have a valid RC bug which should be solved in order to get this
package ready for the release and I mentioned two options people are doing.
Most of what I wrote is from the transition bug #827061. The libssl1.0-dev is
provided by openssl 1.0.2 and is intended to provide the 1.0.2 API for package
which can't be fixed in time for release.

> Michael

Sebastian

Processed (with 1 error): Re: [Pkg-citadel-devel] Bug#828267: reopen, it is still valid

[Debian Bug Tracking System]

Processing control commands:

> merge -1 846543
Bug #828267 [src:citadel] citadel: FTBFS with openssl 1.1.0
Unable to merge bugs because:
blocks of #846543 is '' not '827061'
Failed to merge 828267: Did not alter merged bugs.


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