Bug#804240: libsane: scanning does not work with HPLIP backend

[Raphael Hertzog]

Hi,

On Sat, 07 Nov 2015, Jörg Frings-Fürst wrote:
> So I found one wrongly removed patch. A version with the re-enabled
> patch was uploaded to mentors[1]. Can you build and test this version?

Yes, it works!

Thank you.
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#802400: marked as done (erlang: FTBFS: FOP - Exception

[Debian Bug Tracking System]

Your message dated Sat, 7 Nov 2015 09:56:57 +0300
with message-id 

and subject line Re: [Pkg-erlang-devel] Bug#802400: Bug#802400: Bug#802400: 
erlang: FTBFS: FOP - Exception http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang
Version: 1:18.0-dfsg-2
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

[INFO] FOUserAgent - Rendered page #284.
[ERROR] FOP - Exception org.apache.fop.apps.FOPException
java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.NullPointerException
at 
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405)
at 
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at 
org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)

...

/erlang-18.0-dfsg/make/x86_64-pc-linux-gnu/otp.mk:326: recipe for target 
'../pdf/stdlib-2.5.pdf' failed
make[4]: *** [../pdf/stdlib-2.5.pdf] Error 1
make[4]: Leaving directory '/erlang-18.0-dfsg/lib/stdlib/doc/src'
/erlang-18.0-dfsg/make/otp_subdir.mk:29: recipe for target 'docs' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/erlang.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
On Fri, Nov 6, 2015 at 2:13 PM, Sergei Golovan  wrote:
> block 802400 by 799662
> thanks
>
> On Tue, Oct 20, 2015 at 7:43 AM, Sergei Golovan  wrote:
>>
>> I'd say that It's not a bug in Erlang but a bug in fop. Likely, it's
>> bug #799662. I haven't had time to confirm yet whether it's really
>> #799662 and whether the patch to #799662 fixes it. I'll do that in a
>> few days.
>
> I confirm that after applying the patch from #799662 to fop Erlang build
> is fixed. So, I'll bump the severity of #799662 at the moment.

Since fop 1:2.0+dfsg-4 is accepted to unstable this bug is gone, so
I'm closing the bugreport.

Cheers!
-- 
Sergei Golovan--- End Message ---

Bug#804240: libsane: scanning does not work with HPLIP backend

[Jörg Frings-Fürst]

Hello Raphaël,
hello James,

I have check the difference between the 1.0.25-1 and
1.0.25+git20150927-1.

So I found one wrongly removed patch. A version with the re-enabled
patch was uploaded to mentors[1]. Can you build and test this version?

If you need I can build the package for Jessie, Stretch or Sid [amd64,
i386]. 


Thanks 

CU
Jörg


[1] 
http://mentors.debian.net/debian/pool/main/s/sane-backends/sane-backends_1.0.25-2.dsc

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54526 Niederkail

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.





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

Bug#802917: do not migrate denyhosts to testing: who will do security support?

[Salvatore Bonaccorso]

Hi Jan-Pascal and Helmut,

On Mon, Oct 26, 2015 at 09:23:19PM +0100, Jan-Pascal van Best wrote:
> Hi Helmut,
> 
> Thanks for showing some care for this package. The main reason for me to
> want to support denyhosts was the possibility of the synchronisation
> server. I have since written a (AGPL licensed) replacement for the
> original, closed source, server, starting from Anne Bezemer's suggestion
> in Debian bug#622697.
> 
> I may consider offering to do the security support for denyhosts for at
> least the stretch support period, but I'm not sure what that would mean
> exactly. Is the main work in following CNEs for the package and fixing
> them for Debian (and preferably upstream as well)?
> 
> Another possibility might be to work with fail2ban upstream to also
> support my, or another, synchronisation server, but I'm not sure if they
> would be willing to accept patches to that effect.
> 
> >  * Your upload reintroduces security bug #692229.
> You're right. I checked whether all Debian patches had been implemented
> upstream, must have missed this one.
> 
> >  * Due to the removal of denyhosts from Debian, the following bugs were
> >closed by the ftp masters:
> >
> >#395565 #436417 #497485 #514024 #529089 #546772 #597956 #567209 #611756
> >#622697 #643031 #720130 #729322 #731963
> >
> >Please evaluate which of them need to be reopened or failing that
> >reopen all of them.
> Of course, I was planning to do that.

From security team point of view: If all the previously open security
bugs get's fixed, and both maintainer (hey! ;-)) and upstream remain
active and on track when issues appear I guess we will be fine to have
as well denyhosts in stretch.

OTOH, there is fail2ban which is actively developped as well, and so I
guess much widely used, so it would be possibly better to concentrate
the work effort on fail2ban. Helmut is right here, that it's hard to
get all the bits right already, so if we can avoid in the end having
to maintain both denyhosts and fail2ban that might be preferable.

have you spoken/contacted fail2ban upstream to bring your ideas about
the synchronisation server?

Please only close this bug in case we would be sure that denyhosts
should go in stretch and all the items raised by Helmut are addressed.

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#804183: dbus fails to start, circular inclusion of *.dpkg-bak

[Holger Schramm]

Hi,

I cannot reproduce the bug. After making the update I had no *.bak files
and no problems.

Perhaps there were problems during the update with aptitude o. sth?

-- 
Holger

Processed: graphviz: dot on mipsel fails with emit.c:3873: bezier_bb: Assertion `bz.size > 0' failed

[Debian Bug Tracking System]

Processing control commands:

> block 804296 by -1
Bug #804296 [src:botch] botch: dot assertion failed when building docs on mipsel
804296 was not blocked by any bugs.
804296 was not blocking any bugs.
Added blocking bug(s) of 804296: 804297

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

Bug#804296: botch: dot assertion failed when building docs on mipsel

[Johannes Schauer]

Source: botch
Version: 0.17-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

on mipsel the following error happens:

dot -T png buildgraph1.dot > buildgraph1.png
dot: emit.c:3873: bezier_bb: Assertion `bz.size > 0' failed.
Aborted
Makefile:14: recipe for target 'buildgraph1.png' failed
make[2]: *** [buildgraph1.png] Error 134
make[2]: Leaving directory '/«PKGBUILDDIR»/doc/wiki'
Makefile:89: recipe for target 'doc' failed
make[1]: *** [doc] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

full log:

https://buildd.debian.org/status/fetch.php?pkg=botch&arch=mipsel&ver=0.17-2&stamp=1446862050

Bug#804240: similar issue

[James Healy]

Hi,

I'm experiencing the same issue.

With both 1.0.25-1 (sid) and 1.0.25+git20150927-1 (experimental), the
output of sane-find-scanner detects my scanner:

# sane-find-scanner
found USB scanner (vendor=0x05ac [Apple Inc.], product=0x828f
[Bluetooth USB Host Controller]) at libusb:001:006
found USB scanner (vendor=0x03f0 [HP], product=0x7111 [Photosmart
C5300 series]) at libusb:001:010

However, with 1.0.25-1 the output of scanimage -L is blank, and with
1.0.25+git20150927-1 the output of scanimage -L is:

scanimage -L
device `hpaio:/usb/Photosmart_C5300_series?serial=MY89Q5702P054V'
is a Hewlett-Packard Photosmart_C5300_series all-in-one

Let me know if there's further debugging info I can provide.

James

Bug#803757: marked as done (csoundqt: FTBFS: src/configlists.h:55:2: error: 'QHash' does not name a type)

[Debian Bug Tracking System]

Your message dated Sat, 07 Nov 2015 00:49:22 +
with message-id 
and subject line Bug#803757: fixed in csoundqt 0.9.1-1
has caused the Debian Bug report #803757,
regarding csoundqt: FTBFS: src/configlists.h:55:2: error: 'QHash' does not name 
a type
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.)


-- 
803757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: csoundqt
Version: 0.9.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

csoundqt fails to build from source in unstable/amd64:

  [..]

  In file included from src/csoundoptions.cpp:24:0:
  src/configlists.h:55:2: error: 'QHash' does not name a type
QHash getMidiInputDevices(QString module);

  [..]

   ^
  src/csoundengine.cpp:339:42: warning: unused parameter 'csound'
  [-Wunused-parameter]
   int CsoundEngine::midiOutCloseCb(CSOUND *csound, void *ud)
^
  src/csoundengine.cpp:339:56: warning: unused parameter 'ud'
  [-Wunused-parameter]
   int CsoundEngine::midiOutCloseCb(CSOUND *csound, void *ud)
  ^
  src/csoundengine.cpp:364:56: warning: unused parameter 'message'
  [-Wunused-parameter]
   void CsoundEngine::sendMidiOut(QVector &message)
  ^
  src/csoundengine.cpp:746:54: warning: unused parameter 'delay'
  [-Wunused-parameter]
   void CsoundEngine::queueEvent(QString eventLine, int delay)
^
  src/csoundengine.cpp:1203:47: warning: unused parameter 'csound'
  [-Wunused-parameter]
   void CsoundEngine::breakpointCallback(CSOUND *csound,
   debug_bkpt_info_t *bkpt_info, void *udata)
 ^
  src/documentview.cpp: At global scope:
  src/documentview.cpp:1847:48: warning: unused parameter 'ev'
  [-Wunused-parameter]
   void HoverWidget::mousePressEvent(QMouseEvent *ev)
  ^
  src/documentpage.cpp: In member function 'virtual int
  DocumentPage::setTextString(QString&)':
  src/documentpage.cpp:192:7: warning: unused variable 'visibleEnabled'
  [-Wunused-variable]
 int visibleEnabled = panelElement.attribute("visible","true") ==
 "true";
 ^
  src/documentpage.cpp: At global scope:
  src/documentpage.cpp:558:44: warning: unused parameter 'sheetName'
  [-Wunused-parameter]
   EventSheet* DocumentPage::getSheet(QString sheetName)
  ^
  src/documentpage.cpp:1102:38: warning: unused parameter 'index'
  [-Wunused-parameter]
   void DocumentPage::stopPanelSlot(int index)
^
  src/documentpage.cpp:1119:41: warning: unused parameter 'index'
  [-Wunused-parameter]
   void DocumentPage::setPanelSyncSlot(int index, int mode)
   ^
  src/documentpage.cpp:1119:52: warning: unused parameter 'mode'
  [-Wunused-parameter]
   void DocumentPage::setPanelSyncSlot(int index, int mode)
  ^
  src/documentpage.cpp:1263:30: warning: unused parameter 'format'
  [-Wunused-parameter]
   int DocumentPage::record(int format)
^
  src/documentpage.cpp:1356:53: warning: unused parameter 'widget'
  [-Wunused-parameter]
   void DocumentPage::passUnselectedWidget(QuteWidget *widget)
   ^
  make[1]: Leaving directory '/build/csoundqt-0.9.0'
  /usr/share/cdbs/1/class/makefile.mk:47: recipe for target
  'debian/stamp-makefile-build' failed
  make: *** [debian/stamp-makefile-build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or (an alternate build) can be viewed
here:


https://reproducible.debian.net/logs/unstable/amd64/csoundqt_0.9.0-1.build1.log.gz


Regards,

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


csoundqt.0.9.0-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: csoundqt
Source-Version: 0.9.1-1

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

A summary of the changes between this version and th

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

[gregor herrmann]

On Fri, 06 Nov 2015 22:07:25 +0100, Kurt Roeckx wrote:

> On Fri, Nov 06, 2015 at 09:22:04PM +0200, Niko Tyni wrote:
> > As discussed on IRC, it looks to me like there's no code support for
> > HTTPS_VERSION in 0.73_04 anymore. It seems to be just a leftover in
> > the docs.
> > 
> > The upstream code in 0.73_04 now uses SSLv23_client_method() with
> >  SSL_OP_ALL | SSL_OP_NO_SSLv2 | SSL_OP_NO_SSLv3
> > by default, and with
> >  SSL_OP_ALL | SSL_OP_NO_SSLv2
> > if the (currently undocumented) environment variable
> > CRYPT_SSLEAY_ALLOW_SSLv3 is set.
> > 
> > This seems to be pretty much we want, so I think uploading 0.73_04 is
> > the way to fix this bug. The docs could be improved a bit of course.
> 
> Yes, that looks good to me.

Thanks everybody; uploaded.


Cheers,
gregor

PS: Bug filed about the doc inconsistencies:
https://rt.cpan.org/Ticket/Display.html?id=108520

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Janis Joplin: Maybe


signature.asc
Description: Digital Signature

Bug#803975: marked as done (libcrypt-ssleay-perl: Uses SSLv3_client_method())

[Debian Bug Tracking System]

Your message dated Sat, 07 Nov 2015 00:06:17 +
with message-id 
and subject line Bug#803975: fixed in libcrypt-ssleay-perl 0.73.04-1
has caused the Debian Bug report #803975,
regarding libcrypt-ssleay-perl: Uses SSLv3_client_method()
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.)


-- 
803975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcrypt-ssleay-perl
Version: 0.58-1
Severity: serious

Hi,

Your package has code in SSLeay.xs that does:
if(ssl_version == 23) {
ctx = SSL_CTX_new(SSLv23_client_method());
}
else if(ssl_version == 3) {
ctx = SSL_CTX_new(SSLv3_client_method());
}
else {
#ifndef OPENSSL_NO_SSL2
/* v2 is the default */
ctx = SSL_CTX_new(SSLv2_client_method());
#else
/* v3 is the default */
ctx = SSL_CTX_new(SSLv3_client_method());
#endif
}


You really only ever want to use SSLv23_client_method() since that
is the only one that supports multiple versions.  I suggest you
modify your nossl2.patch to just replace all of the above by:
ctx = SSL_CTX_new(SSLv23_client_method());

ssl_version would then become an unused variable.

Just like SSLv2 has already been removed, SSLv3 is now also
removed because it's insecure.


Kurt
--- End Message ---
--- Begin Message ---
Source: libcrypt-ssleay-perl
Source-Version: 0.73.04-1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libcrypt-ssleay-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: Sat, 07 Nov 2015 00:53:32 +0100
Source: libcrypt-ssleay-perl
Binary: libcrypt-ssleay-perl
Architecture: source
Version: 0.73.04-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 803975
Description: 
 libcrypt-ssleay-perl - OpenSSL support for LWP
Changes:
 libcrypt-ssleay-perl (0.73.04-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Harlan Lieberman-Berg ]
   * New upstream release.
   * Remove patch accepted upstream.
   * Rework d/copyright to conform with final spec.
   * Bump s-v to 3.9.5, compat to 9, d-h to >= 9.20120312
   * Add dependency for libtry-tiny-perl
   * Add deprecation warning.
   * Update d/control, d/copyright with new dependencies and files.
 .
   [ Salvatore Bonaccorso ]
   * Change Vcs-Git to canonical URI (git://anonscm.debian.org)
   * Change search.cpan.org based URIs to metacpan.org based URIs
 .
   [ gregor herrmann ]
   * Strip trailing slash from metacpan URLs.
 .
   [ Axel Beckert ]
   * Fix Vcs-* headers (Thanks DUCK!)
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
 .
   [ gregor herrmann ]
   * Update years of upstream and packaging copyright.
   * Update upstream license.
   * Add versions to new build dependencies.
   * Add libdevel-checklib-perl to Build-Depends.
   * Add debian/upstream/metadata.
   * debian/watch: temporarily allow devel releases.
 .
   * Import upstream development version 0.73_04.
 Fixes "Uses SSLv3_client_method()".
 (Closes: #803975)
   * Add IO::Socket::IP to Recommends and Build-Depends.
   * Add (build) dependency on libbytes-random-secure-perl.
   * Mark package as autopkgtest-able.
   * Declare compliance with Debian Policy 3.9.6.
Checksums-Sha1: 
 377d48759dbbb6c8357bc8c64bb2bcaffd92375f 2469 
libcrypt-ssleay-perl_0.73.04-1.dsc
 17722f5343e8474cb7098691b63ef5b27fbfe82d 129261 
libcrypt-ssleay-perl_0.73.04.orig.tar.gz
 31c1e837038f139eb4714c5fec79f758a07c2163 7568 
libcrypt-ssleay-perl_0.73.04-1.debian.tar.xz
Checksums-Sha256: 
 489583669b3113047eed64b2e894a93877a3987101a6b6ff2501278196a90ead 2469 
libcrypt-ssleay-perl_0.73.04-1.dsc
 b7098d14d3db4a089eee765440b27c2838e204b61297c062c4feb50eb75aee10 129261 
libcrypt-ssleay-perl_0.73.04.orig.tar.gz
 16e24712a7f93b3ebd1af168ec3c113ad6a39f188a89c10c3d17bd7dec22

Bug#804289: libcacard-dev: Please add libglib2.0-dev to the dependencies

[Laurent Bigonville]

Package: libcacard-dev
Version: 1:2.5.0-1a
Severity: serious

Hi,

The libcacard.pc file requires glib2.0 but the package is not declaring
any dependencies against libglib2.0-dev.

Please add it to the dependencies

Cheers,

Laurent Bigonville

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

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

Versions of packages libcacard-dev depends on:
ii  libcacard0   1:2.5.0-1a
ii  libnss3-dev  2:3.20.1-1

libcacard-dev recommends no packages.

libcacard-dev suggests no packages.

-- no debconf information

Bug#803567: marked as done (r-bioc-cummerbund: FTBFS: objects 'FilterRules', 'seqsplit', 'FilterMatrix', 'subsetByFilter' are not exported by 'namespace:IRanges')

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 23:21:40 +
with message-id 
and subject line Bug#803567: fixed in r-bioc-cummerbund 2.12.0-1
has caused the Debian Bug report #803567,
regarding r-bioc-cummerbund: FTBFS: objects 'FilterRules', 'seqsplit', 
'FilterMatrix', 'subsetByFilter' are not exported by 'namespace:IRanges'
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.)


-- 
803567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-cummerbund
Version: 2.10.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

r-bioc-cummerbund fails to build from source in unstable/amd64:

  [..]

  * installing *source* package 'cummeRbund' ...
  ** R
  ** data
  ** inst
  ** preparing package for lazy loading
  Warning: replacing previous import by 'IRanges::FilterRules' when
  loading 'VariantAnnotation'
  Warning: replacing previous import by 'IRanges::FilterMatrix' when
  loading 'VariantAnnotation'
  Error : objects 'FilterRules', 'seqsplit', 'FilterMatrix',
  'subsetByFilter' are not exported by 'namespace:IRanges'
  Error : package 'Gviz' could not be loaded
  ERROR: lazy loading failed for package 'cummeRbund'
  * removing
  
'/home/lamby/temp/cdt.20151031125953.K7Z1F3IZ2W/r-bioc-cummerbund-2.10.0/debian/r-bioc-cummerbund/usr/lib/R/site-library/cummeRbund'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch'
  failed
  make: *** [R_any_arch] Error 1

  [..]

The full build log is attached.


Regards,

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


r-bioc-cummerbund.2.10.0-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: r-bioc-cummerbund
Source-Version: 2.12.0-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-cummerbund 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, 06 Nov 2015 15:20:28 +0100
Source: r-bioc-cummerbund
Binary: r-bioc-cummerbund
Architecture: source all
Version: 2.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 r-bioc-cummerbund - tool for analysis of Cufflinks RNA-Seq output
Closes: 803567
Changes:
 r-bioc-cummerbund (2.12.0-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #803567
Checksums-Sha1:
 f5f7fe656132e7031ddf43e3a8f8327c7619d926 2156 r-bioc-cummerbund_2.12.0-1.dsc
 1870a35b275ea6ebb7d253deb726a8ff01b7386e 2299346 
r-bioc-cummerbund_2.12.0.orig.tar.gz
 c4b2ff00e3fb97af27bdf6876ef85f8688b64dc5 4264 
r-bioc-cummerbund_2.12.0-1.debian.tar.xz
 d488cede141da68305eb20a5e4ffd04ecc9c1483 2089956 
r-bioc-cummerbund_2.12.0-1_all.deb
Checksums-Sha256:
 3668284bda4eda045d4bd7ac2081e3c488026d6b5e4cc1e45e231e4982297ae8 2156 
r-bioc-cummerbund_2.12.0-1.dsc
 da1cfed216831868f9514c30f27f36112998fac753bedfc5c68c57d4fef19ca6 2299346 
r-bioc-cummerbund_2.12.0.orig.tar.gz
 0214afeaf1bf3fd2187c13d16df63e74d429587edd07de8fd26e87cc22656835 4264 
r-bioc-cummerbund_2.12.0-1.debian.tar.xz
 4e8d3fb8734004a1d6ea243a68c94293cd4ebf5ad5225e184c0bbc860df02b76 2089956 
r-bioc-cummerbund_2.12.0-1_all.deb
Files:
 eb91993b2d1f15cb0bcd7fd66c340335 2156 gnu-r optional 
r-bioc-cummerbund_2.12.0-1.dsc
 4fa63efce8d85ea6b48afca6a454ce87 2299346 gnu-r optional 
r-bioc-cummerbund_2.12.0.orig.tar.gz
 0b46ac1f4299e7f28cb4d7ad0d10ad91 4264 gnu-r optional 
r-bioc-cummerbund_2.12.0-1.debian.tar.xz
 d56af12c0b94430a8fbd705d26c167b2 2089956 gnu-r optional 
r-bioc-cummerbund_2.12.0-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWPTOVAAoJEFeKBJTRxkbRjKEP/2mdcZHJ+O8+XOnRrdsFgdG8
xT5oBrOWP7Zp07e+sileyJg8ZDjilg7TAC4qv7lhBPue7KilZtcBzkrRpwGDIcsJ
Lz0OnV7EsTADCGmRvOlV+ja4Gdl5oZI

Processed: tagging 803972

[Debian Bug Tracking System]

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

> tags 803972 + pending
Bug #803972 [src:attic] attic: Fixed depedency on libssl1.0.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: bug 802619 is forwarded to https://github.com/jborg/attic/issues/356

[Debian Bug Tracking System]

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

> forwarded 802619 https://github.com/jborg/attic/issues/356
Bug #802619 [attic] attic: Unrecoverable data integrity error after running out 
of disk space
Set Bug forwarded-to-address to 'https://github.com/jborg/attic/issues/356'.
> thanks
Stopping processing here.

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

Bug#799662: marked as done (Null pointer exception at org.apache.fop.cli.InputHandler.transformTo)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 21:38:03 +
with message-id 
and subject line Bug#799662: fixed in fop 1:2.0+dfsg-4
has caused the Debian Bug report #799662,
regarding Null pointer exception at org.apache.fop.cli.InputHandler.transformTo
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.)


-- 
799662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fop
Version: 1:2.0+dfsg-3
Severity: important

Dear maintainer,

Currently fop fails to build our internal training slides likes this:

[INFO] FOUserAgent - Rendered page #321.
[ERROR] FOP - Exception org.apache.fop.apps.FOPException
java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.NullPointerException
at 
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405)
at 
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at 
org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at 
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252)
at 
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158)
at 
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384)
at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
at 
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138)
at 
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)
at 
org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130)
at 
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360)
at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190)
at 
org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1102)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown 
Source)
at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

Bug#804279: fwupd: FTBFS in sid/amd64: dh_install: fwupd missing files (lib/udev/rules.d/*), aborting

[Mario Limonciello]

I'm unsure how that would have happened, all the builds have been done
from source.

We just uploaded 0.5.3-1 today, which I did a test build from source in
a newly built debian unstable chroot.  All I did was debootstrap and
then install build-deps mentioned in debian/control.

# dpkg-buildpackage
.
.
.
make[5]: Leaving directory '/fwupd-0.5.3/src'
make[4]: Leaving directory '/fwupd-0.5.3/src'
make[3]: Leaving directory '/fwupd-0.5.3/src'
make[2]: Leaving directory '/fwupd-0.5.3/src'
make[2]: Entering directory '/fwupd-0.5.3'
make[3]: Entering directory '/fwupd-0.5.3'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/fwupd-0.5.3'
make[2]: Leaving directory '/fwupd-0.5.3'
make[1]: Leaving directory '/fwupd-0.5.3'
   dh_install
   dh_installdocs
.
.
.

# ls debian/tmp/lib/udev/rules.d/
90-fwupd-devices.rules

Can you please check if this issue persists with the 0.5.3-1 upload?  If
it was caused by a missed transition in NEW, I believe that it should be
resolved with the fresh build.  If it does persist, can you please
recommend to me how I can reproduce the problem or review a full log of
the autobuilder (since I already tried with a local amd64 debian
unstable chroot).

On 11/06/2015 02:37 PM, Andreas Beckmann wrote:
> Package: fwupd
> Version: 0.1.5-1
> Severity: serious
> Justification: fails to build from source
>
> While checking for a solution of the uninstallability in sid/amd64 (the
> package probably missed some transitions while in NEW), I noticed that
> it FTBFS:
>
> [...]
> ving directory '/tmp/buildd/fwupd-0.1.5/src'
> make[4]: Leaving directory '/tmp/buildd/fwupd-0.1.5/src'
> make[3]: Leaving directory '/tmp/buildd/fwupd-0.1.5/src'
> make[2]: Leaving directory '/tmp/buildd/fwupd-0.1.5/src'
> make[2]: Entering directory '/tmp/buildd/fwupd-0.1.5'
> make[3]: Entering directory '/tmp/buildd/fwupd-0.1.5'
> make[3]: Nothing to be done for 'install-exec-am'.
> make[3]: Nothing to be done for 'install-data-am'.
> make[3]: Leaving directory '/tmp/buildd/fwupd-0.1.5'
> make[2]: Leaving directory '/tmp/buildd/fwupd-0.1.5'
> make[1]: Leaving directory '/tmp/buildd/fwupd-0.1.5'
>dh_install
> dh_install: fwupd missing files (lib/udev/rules.d/*), aborting
> debian/rules:8: recipe for target 'binary' failed
> make: *** [binary] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
> E: Failed autobuilding of package
>
>
> Andreas
>

-- 
*Mario Limonciello*
*Dell*| Client Software Group
*office*+1 512 723 0582

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

[Kurt Roeckx]

On Fri, Nov 06, 2015 at 09:22:04PM +0200, Niko Tyni wrote:
> On Fri, Nov 06, 2015 at 05:48:32PM +0100, gregor herrmann wrote:
> 
> > I have to admit that I'm still not completely sure if/how this
> > affects us packaging-wise. My current understanding is, that the
> > library would allow to set SSLv3 via HTTPS_VERSION which will fail
> > now on Debian but that it should just work fine with the default
> > values. Is this correct?
> 
> As discussed on IRC, it looks to me like there's no code support for
> HTTPS_VERSION in 0.73_04 anymore. It seems to be just a leftover in
> the docs.
> 
> The upstream code in 0.73_04 now uses SSLv23_client_method() with
>  SSL_OP_ALL | SSL_OP_NO_SSLv2 | SSL_OP_NO_SSLv3
> by default, and with
>  SSL_OP_ALL | SSL_OP_NO_SSLv2
> if the (currently undocumented) environment variable
> CRYPT_SSLEAY_ALLOW_SSLv3 is set.
> 
> This seems to be pretty much we want, so I think uploading 0.73_04 is
> the way to fix this bug. The docs could be improved a bit of course.

Yes, that looks good to me.


Kurt

Processed: found 804149 in 1.8.5p2-1

[Debian Bug Tracking System]

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

> found 804149 1.8.5p2-1
Bug #804149 [sudo] CVE-2015-5602: Unauthorized privilege escalation in sudoedit
Marked as found in versions sudo/1.8.5p2-1.
> thanks
Stopping processing here.

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

Bug#804279: fwupd: FTBFS in sid/amd64: dh_install: fwupd missing files (lib/udev/rules.d/*), aborting

[Andreas Beckmann]

Package: fwupd
Version: 0.1.5-1
Severity: serious
Justification: fails to build from source

While checking for a solution of the uninstallability in sid/amd64 (the
package probably missed some transitions while in NEW), I noticed that
it FTBFS:

[...]
ving directory '/tmp/buildd/fwupd-0.1.5/src'
make[4]: Leaving directory '/tmp/buildd/fwupd-0.1.5/src'
make[3]: Leaving directory '/tmp/buildd/fwupd-0.1.5/src'
make[2]: Leaving directory '/tmp/buildd/fwupd-0.1.5/src'
make[2]: Entering directory '/tmp/buildd/fwupd-0.1.5'
make[3]: Entering directory '/tmp/buildd/fwupd-0.1.5'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/tmp/buildd/fwupd-0.1.5'
make[2]: Leaving directory '/tmp/buildd/fwupd-0.1.5'
make[1]: Leaving directory '/tmp/buildd/fwupd-0.1.5'
   dh_install
dh_install: fwupd missing files (lib/udev/rules.d/*), aborting
debian/rules:8: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Failed autobuilding of package


Andreas

Bug#804259: mercurial-git: TypeError: exchangepush() got an unexpected keyword argument 'opargs'

[Javi Merino]

On Fri, Nov 06, 2015 at 06:50:01PM +0100, Jakub Wilk wrote:
> Package: mercurial-git
> Version: 0.8.2-1
> Severity: grave
> 
> I can't push to git repos:
> 
> $ git init gitrepo
> Initialized empty Git repository in /home/jwilk/gitrepo/.git/
> 
> $ hg clone gitrepo hgrepo
> updating to branch default
> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
> 
> $ cd hgrepo
> $ hg push
> pushing to /home/jwilk/gitrepo
> ** Unknown exception encountered with possibly-broken third-party extension 
> git
> ** which supports versions 3.4 of Mercurial.
> ** Please disable git and try your action again.
> ** If that fixes the bug please report it to 
> https://bitbucket.org/durin42/hg-git/issues
> ** Python 2.7.10+ (default, Oct 10 2015, 09:11:24) [GCC 5.2.1 20151028]
> ** Mercurial Distributed SCM (version 3.6)
> ** Extensions loaded: color, convert, gpg, graphlog, strip, mq, pager, 
> progress, purge, rebase, record, shelve, git
> Traceback (most recent call last):
>  File "/usr/bin/hg", line 43, in 
>mercurial.dispatch.run()
>  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 54, in 
> run
>sys.exit((dispatch(request(sys.argv[1:])) or 0) & 255)
>  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 116, in 
> dispatch
>ret = _runcatch(req)
>  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 187, in 
> _runcatch
>return _dispatch(req)
>  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 920, in 
> _dispatch
>cmdpats, cmdoptions)
>  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 679, in 
> runcommand
>ret = _runcommand(ui, options, cmd, d)
>  File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 183, 
> in closure
>return func(*(args + a), **kw)
>  File "/usr/lib/python2.7/dist-packages/hgext/pager.py", line 139, in pagecmd
>return orig(ui, options, cmd, cmdfunc)
>  File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 183, 
> in closure
>return func(*(args + a), **kw)
>  File "/usr/lib/python2.7/dist-packages/hgext/color.py", line 525, in colorcmd
>return orig(ui_, opts, cmd, cmdfunc)
>  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 1051, in 
> _runcommand
>return checkargs()
>  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 1011, in 
> checkargs
>return cmdfunc()
>  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 917, in 
> 
>d = lambda: util.checksignature(func)(ui, *args, **cmdoptions)
>  File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 803, in check
>return func(*args, **kwargs)
>  File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 183, 
> in closure
>return func(*(args + a), **kw)
>  File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 803, in check
>return func(*args, **kwargs)
>  File "/usr/lib/python2.7/dist-packages/hgext/mq.py", line 3525, in mqcommand
>return orig(ui, repo, *args, **kwargs)
>  File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 803, in check
>return func(*args, **kwargs)
>  File "/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 5426, in 
> push
>opargs=opts.get('opargs'))
>  File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 183, 
> in closure
>return func(*(args + a), **kw)
>  File "/usr/lib/python2.7/dist-packages/hgext/git/util.py", line 48, in inner
>return f(*args, **kwargs)
> TypeError: exchangepush() got an unexpected keyword argument 'opargs'

Gah, sorry for that, it's due to mercurial 3.6.  I did a very brief
test of mercurial-git but I didn't test pushing to git repositories so
I missed it.

There isn't a new version of mercurial-git yet, so for the time being
downgrade to mercurial 3.5.2-2 as workaround.

Cheers,
Javi


signature.asc
Description: PGP signature

Bug#783503: mediawiki: not suitable for Stretch

[Salvatore Bonaccorso]

Hi,

On Mon, Apr 27, 2015 at 04:00:10PM +0100, Jonathan Wiltshire wrote:
> Package: mediawiki
> Version: 1:1.19.20+dfsg-2.3
> Severity: serious
> Tags: stretch sid
> 
> Mediawiki as it currently stands is not suitable for a stable release.
> This blocker bug is to ensure it does not migrate to testing.

Give the current status for mediawiki in unstable (version 1.19.x)
should maybe mediawiki be dropped as well from unstable?

Regards,
Salvatore

Bug#804240: libsane: scanning does not work with HPLIP backend

[Raphael Hertzog]

Hi Jörg,

On Fri, 06 Nov 2015, Jörg Frings-Fürst wrote:
> first thanks for your bug report.
> 
> Do you have some more informations as error messages or so?

Nothing on the terminal. In the logs I see this:
nov. 06 14:40:48 x230-buxy simple-scan[7392]: sane_hpaio_cancel: already 
cancelled!

But I'm not sure if it happens right at the start of scan try or only after
the error message has been displayed/validated. I get a an error message but it 
was
in french and I don't remember it offhand.

I can check later but not this evening (remind me if I forget).

If there's a way to enable more extensive debug information, let me know
and I can try. That said since the git snapshot in experimental seems to
work, I wonder if it's worth investing lots of time on this issue.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#804274: Torbrowser update 5.5a4-hardened breaks launcher

[Julien Aubin]

Package: torbrowser-launcher
Version: 0.2.0-1~bpo8+1
Severity: grave
Justification: renders package unusable

Hello,

Release 5.5a4 of TorBrowser is now out. The problem is that they changed the
archive layout, which actually breaks the Tor browser package.

When trying to launch it here's what I get :

julien@pccorei7-4770:~$ torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.0
https://github.com/micahflee/torbrowser-launcher
Updating over Tor
Checked for update within 24 hours, skipping
TBB is out of date, attempting to upgrade to 5.5a4-hardened
Downloading
https://dist.torproject.org/torbrowser/5.5a4-hardened/sha256sums.txt
Downloading
https://dist.torproject.org/torbrowser/5.5a4-hardened/sha256sums.txt.asc
Downloading
https://dist.torproject.org/torbrowser/5.5a4-hardened/tor-browser-
linux64-5.5a4-hardened_fr.tar.xz
Download error: Download Error: 404 Not Found 


Actually release 5.5a4 (not hardened) contains all the languages, but not
the
hardened flavour, which only contains a _ALL archive.

Could you please fix it ?



-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages torbrowser-launcher depends on:
ii  gnupg1.4.18-7
ii  python   2.7.9-1
ii  python-gtk2  2.24.0-4
ii  python-lzma  0.5.3-2+b1
ii  python-parsley   1.2-1
ii  python-psutil2.1.1-1+b1
ii  python-twisted   14.0.2-3
ii  python-txsocksx  1.13.0.3-1
ii  tor  0.2.5.12-1
ii  wmctrl   1.07-7

torbrowser-launcher recommends no packages.

Versions of packages torbrowser-launcher suggests:
ii  apparmor   2.9.0-3
pn  python-pygame  

-- no debconf information

Bug#804272: fails to synchronize caldav to OpenXChange without notice

[Thomas Koch]

Package: akonadi-server
Version: 1.13.0-2+deb8u1
Severity: serious
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I've started to use the Calendar and Contacts features of Kontact together
with mailbox.org seriously. mailbox.org uses OpenXChange and I connect to it
via DAV groupware resources.

After entering many contacts, I noticed that they were not synchronized
anymore to mailbox.org. I solved this by copying all contacts in an vCard
folder resource, setting up a new DAV groupware resource and copying the
contacts back.

Today I noticed that calendar events were not synchronized from the
mailbox.org server to my laptop.

Since there are many search hits for this kind of error with different CalDav
server, I believe that this is a bug in Akonadi.

Maybe it would be possible to backport a newer version of Akonadi and Kontact
for Jessie that might have fewer bugs? That would also be a good preparation
to maybe get a working Kontakt for Stretch?

This bug is serious because it causes important personal data loss.

Thank you, Thomas Koch

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

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

Versions of packages akonadi-server depends on:
ii  akonadi-backend-postgresql  1.13.0-2+deb8u1
ii  libakonadiprotocolinternals11.13.0-2+deb8u1
ii  libboost-program-options1.55.0  1.55.0+dfsg-3
ii  libc6   2.19-18+deb8u1
ii  libgcc1 1:4.9.2-10
ii  libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-network  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-sql  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-xml  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtcore4  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libstdc++6  4.9.2-10

akonadi-server recommends no packages.

Versions of packages akonadi-server suggests:
pn  akonadi-backend-mysql   
ii  akonadi-backend-postgresql  1.13.0-2+deb8u1
pn  akonadi-backend-sqlite  

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWPQMNAAoJEAf8SJEEK6ZabjEP+wT+7IOVCXHiNJgNHIEuXW34
SFptaUTo/E58mT0Vu7QO07cyEe+t0BuvrFI3FW7LmWGUTFQnKISW/pVMCWNPt/gZ
zuWJ2EQN3ZXgsoMKWwil3yBGSbMTxZ8At9htG5N8u/F5OPGcGZ3sp7ZUVXjg1Azx
iQroxFxqs1c81fwsOil5UqSDDvfdM9+OWq9xAjWvietvz2DdS/SEKHhM9kaquxJx
Q6wTm2LXul5bltQuGiaMqADvNy1aLdM3tWbbFPVeREQI5ImjyiiITgBQtT/eEOQK
SRG6dyARHyTbxLFkycMpcU4U1j8vcX/MATS2OkipVXiApxUE7zj2yM6+YsYYmpf1
dOUDYxRBFCyE92dNUXM5GiYM1rAZMipsBP6LZbNcuAKAI4JwLIzUjk6pMTi3lbVp
Rcd8YPqqLDELc7siEjnrfuY/e2lTy7DJi44FdRmRrjUIVL8+5bRwKVrGhH6QHUOy
VKY4zWnElClh2o4oqSqlJRT+Gna+xj7q5204gffxLIg9iB7Yymwa3FVuZIjxChMV
YVR7nF1NllotnL1qt+YTQCJe/neXGJrT0p+t3mkIiGIYzSKDm9aAbmCXq6T1XPvb
14IXDrt/pTZt/3kULj2+P1gm2TKO0T16XmN6yRJLvUj5Cr4CrxqJSf2m10/xUJaD
DYK0iHacBL5Xz1Gn3M/Z
=RWEM
-END PGP SIGNATURE-

Processed: patch

[Debian Bug Tracking System]

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

> tags 777861 + patch
Bug #777861 [src:gauche-c-wrapper] gauche-c-wrapper: ftbfs with GCC-5
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: bug 804259 is forwarded to https://bitbucket.org/durin42/hg-git/issues/169/hg-push-to-github-fails

[Debian Bug Tracking System]

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

> forwarded 804259 
> https://bitbucket.org/durin42/hg-git/issues/169/hg-push-to-github-fails
Bug #804259 [mercurial-git] mercurial-git: TypeError: exchangepush() got an 
unexpected keyword argument 'opargs'
Set Bug forwarded-to-address to 
'https://bitbucket.org/durin42/hg-git/issues/169/hg-push-to-github-fails'.
> thanks
Stopping processing here.

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

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

[Niko Tyni]

On Fri, Nov 06, 2015 at 05:48:32PM +0100, gregor herrmann wrote:

> I have to admit that I'm still not completely sure if/how this
> affects us packaging-wise. My current understanding is, that the
> library would allow to set SSLv3 via HTTPS_VERSION which will fail
> now on Debian but that it should just work fine with the default
> values. Is this correct?

As discussed on IRC, it looks to me like there's no code support for
HTTPS_VERSION in 0.73_04 anymore. It seems to be just a leftover in
the docs.

The upstream code in 0.73_04 now uses SSLv23_client_method() with
 SSL_OP_ALL | SSL_OP_NO_SSLv2 | SSL_OP_NO_SSLv3
by default, and with
 SSL_OP_ALL | SSL_OP_NO_SSLv2
if the (currently undocumented) environment variable
CRYPT_SSLEAY_ALLOW_SSLv3 is set.

This seems to be pretty much we want, so I think uploading 0.73_04 is
the way to fix this bug. The docs could be improved a bit of course.
-- 
Niko Tyni   nt...@debian.org

Processed: your mail

[Debian Bug Tracking System]

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

> tags 799662 pending
Bug #799662 [fop] Null pointer exception at 
org.apache.fop.cli.InputHandler.transformTo
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: Re: Bug#802912: nmu: openmw_0.36.1-1

[Debian Bug Tracking System]

Processing control commands:

> reassign 801914 src:bullet
Bug #801914 [openmw] Game crashes when quitting imperial ship
Bug reassigned from package 'openmw' to 'src:bullet'.
No longer marked as found in versions openmw/0.36.1-1.
Ignoring request to alter fixed versions of bug #801914 to the same values 
previously set
> affects 801914 openmw
Bug #801914 [src:bullet] Game crashes when quitting imperial ship
Added indication that 801914 affects openmw
> retitle 801914 bullet: broke ABI without a library transition
Bug #801914 [src:bullet] Game crashes when quitting imperial ship
Changed Bug title to 'bullet: broke ABI without a library transition' from 
'Game crashes when quitting imperial ship'

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

Bug#801914: Bug#802912: nmu: openmw_0.36.1-1

[Emilio Pozuelo Monfort]

Control: reassign 801914 src:bullet
Control: affects 801914 openmw
Control: retitle 801914 bullet: broke ABI without a library transition

On 06/11/15 11:22, bret curtis wrote:
> On Mon, Oct 26, 2015 at 8:10 PM, Emilio Pozuelo Monfort 
> wrote:
> 
>> On 26/10/15 18:30, Scott Howard wrote:
>>> On Mon, Oct 26, 2015 at 5:12 AM, Emilio Pozuelo Monfort
>>>  wrote:
 On 25/10/15 02:27, Scott Howard wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
>
> nmu openmw_0.36.1-1 . ANY . unstable . -m "rebuild against new
>> libbullet"
>
> The maintainer (Bret Curtis) is busy but asked me to request this
>> binNMU
>
> Game crashes because it was compiled against an old libbullet. More
>> info:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801914
> https://forum.openmw.org/viewtopic.php?f=2&t=3053

 Sounds like you need a library transition.

 Emilio
>>>
>>> Yes, but the discussion on the libbullet transition went another way:
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790988#35
>>
>> As you can see in that bug report, there already was a bullet transition
>> for the
>> GCC 5 / libstdc++6 breaks.
>>
>> The problem is that openmw 0.36.1-1+b2 was built against bullet
>> 2.83.5+dfsg-2,
>> but upgrading bullet to 2.83.6+dfsg-1 breaks openmw. That means bullet
>> broke the
>> ABI and needs a transition.
>>
>> Cheers,
>> Emilio
>>
> 
> As of today:
>openmw: flagged for removal in 7.6 days
> 
> is there any way to prevent it's removal and having to go through the whole
> ITP again?

That will only remove it from testing, not unstable. So you won't have to go
through the whole process. You'll just need to fix the RC bugs for the package
to get back into testing.

> Is there anything being done about bullet?

Let's close this binNMU request and reassign #801914 to bullet. Bullet will need
a library transition to fix this properly.

Cheers,
Emilio

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

[Kurt Roeckx]

On Fri, Nov 06, 2015 at 05:48:32PM +0100, gregor herrmann wrote:
> On Tue, 03 Nov 2015 22:35:10 +0100, Kurt Roeckx wrote:
> 
> > On Tue, Nov 03, 2015 at 10:33:21PM +0100, Kurt Roeckx wrote:
> > > On Tue, Nov 03, 2015 at 09:56:36PM +0100, gregor herrmann wrote:
> 
> > > > At a quick glance this looks good, since there's only
> > > > SSLv23_client_method() left. What confuses me a bit is
> > > > - in the .xs file the allow_sslv3 variable
> > > > - in the .pm file the HTTPS_VERSION environmen variable.
> > > 
> > > Since jessie SSLv23_client_method() doesn't support SSLv3 anymore,
> > > SSLv2 was removed before.  So "allow_sslv3" doesn't make sense, at
> > > least in Debian.  If you really wanted to allow SSLv3 the proper
> > > way to do that was by default set the option SSL_OP_NO_SSLv3 (and
> > > SSL_OP_NO_SSLv2) and then don't set SSL_OP_NO_SSLv3 when it's
> > > allowed.  That would be with the SSL_{CTX_}set_options function.
> > > 
> > > The code still seems to have a reference to the library when it
> > > was called ssleay and when TLS didn't exist, at least the version
> > > I looked at, and so seems to pick between SSLv2 and SSLv3.
> > > 
> > > HTTPS_VERSION seems really weird.  There is also a
> > > $DEFAULT_VERSION set to 23 which then makes it use SSLv3, and
> > > setting it to 3 makes it use SSLv2?
> > 
> > There is this text:
> > SSL versions
> > "Crypt::SSLeay" tries very hard to connect to *any* SSL web server
> > accomodating servers that are buggy, old or simply not
> > standards-compliant. To this effect, this module will try SSL
> > connections in this order:
> > 
> > SSL v23
> > should allow v2 and v3 servers to pick their best type
> > 
> > SSL v3
> > best connection type
> > 
> > SSL v2
> > old connection type
> > 
> > Unfortunately, some servers seem not to handle a reconnect to SSL v3
> > after a failed connect of SSL v23 is tried, so you may set before using
> > LWP or Net::SSL:
> > 
> > $ENV{HTTPS_VERSION} = 3;
> > 
> > to force a version 3 SSL connection first. At this time only a version 2
> > SSL connection will be tried after this, as the connection attempt order
> > remains unchanged by this setting.
> 
> Thanks for taking the time to look into this.
> 
> I have to admit that I'm still not completely sure if/how this
> affects us packaging-wise. My current understanding is, that the
> library would allow to set SSLv3 via HTTPS_VERSION which will fail
> now on Debian but that it should just work fine with the default
> values. Is this correct?
> 
> If yes I guess we can just take 0.73_04 as is and everything should
> work. (Or maybe we want to patch the documentation to say that SSLv3
> won't work anymore on Debian.)
> 
> In any case I've imported 0.73_04 as 0.73.04-1 and pushed it to
> Alioth.

I'm not sure I understand the question.  So let me try to explain
it from the OpenSSL side.

There are functions like SSLv2_client_method(), SSLv1_client_method(),
TLSv1_client_method().  Those are version specific method that
will only talk that protocol.

Then there is SSLv23_client_method(), which supports multiple
protocol versions.  Behind the scenes ones a protocol version is
selected it will switch the method to one of those others.

The SSLv2_* functions have been removed in Debian in 1.0.0c-2, it
they were never in any 1.* version in unstable.  At that time the
SSLv23_* method also stopped supporting SSLv2.  So that's the case
in wheezy en jessie, but squeeze still has it.

Before the jessie release SSLv3 also got disabled, but only in the
SSLv23_* methods.  That is, the SSLv3_* methods still exists and
you can still create SSLv3 connections with it, but you can't
anymore using the SSLv23_* methods.

Now those SSLv3_* methods have also been removed, completly
removing any SSLv3 (and SSLv2) support.

People should in general stop using the version specific methods
and instead use the SSLv23_* methods.  (It was renamed to
TLS_*_method in openssl's master branch, to avoid confusion.)

There might have been problems a long time ago where talking to a
v2 server didn't work when using a v3 client hello.  This is why
at least in 0.9.8 the client hello that was send with a "SSLv2
compatible" client hello.  It indicated support for SSLv3 but an
SSLv2 *should* be able to understand it.

But there have been many cases of "version intolerance" where
indicating support for a higher version than the server supports
resulted in an error.  I'm guessing that's why perl has this version
rollback mechanism.  But you really shouldn't be doing that, it
can be used in a "version rollback attack" where the attacker can
force you to use a lower version even tough both sides support a
newer version.  If you really want to do that, you should tell
OpenSSL that you're actually doing that using: SSL_set_mode(s,
SSL_MODE_SEND_FALLBACK_SCSV).  It's not perfect, but it's better
than nothing.  You also might want to look at CVE-2

Bug#804259: mercurial-git: TypeError: exchangepush() got an unexpected keyword argument 'opargs'

[Jakub Wilk]

Package: mercurial-git
Version: 0.8.2-1
Severity: grave

I can't push to git repos:

$ git init gitrepo
Initialized empty Git repository in /home/jwilk/gitrepo/.git/

$ hg clone gitrepo hgrepo
updating to branch default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved

$ cd hgrepo
$ hg push
pushing to /home/jwilk/gitrepo
** Unknown exception encountered with possibly-broken third-party extension git
** which supports versions 3.4 of Mercurial.
** Please disable git and try your action again.
** If that fixes the bug please report it to 
https://bitbucket.org/durin42/hg-git/issues
** Python 2.7.10+ (default, Oct 10 2015, 09:11:24) [GCC 5.2.1 20151028]
** Mercurial Distributed SCM (version 3.6)
** Extensions loaded: color, convert, gpg, graphlog, strip, mq, pager, 
progress, purge, rebase, record, shelve, git
Traceback (most recent call last):
 File "/usr/bin/hg", line 43, in 
   mercurial.dispatch.run()
 File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 54, in run
   sys.exit((dispatch(request(sys.argv[1:])) or 0) & 255)
 File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 116, in 
dispatch
   ret = _runcatch(req)
 File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 187, in 
_runcatch
   return _dispatch(req)
 File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 920, in 
_dispatch
   cmdpats, cmdoptions)
 File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 679, in 
runcommand
   ret = _runcommand(ui, options, cmd, d)
 File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 183, in 
closure
   return func(*(args + a), **kw)
 File "/usr/lib/python2.7/dist-packages/hgext/pager.py", line 139, in pagecmd
   return orig(ui, options, cmd, cmdfunc)
 File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 183, in 
closure
   return func(*(args + a), **kw)
 File "/usr/lib/python2.7/dist-packages/hgext/color.py", line 525, in colorcmd
   return orig(ui_, opts, cmd, cmdfunc)
 File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 1051, in 
_runcommand
   return checkargs()
 File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 1011, in 
checkargs
   return cmdfunc()
 File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 917, in 

   d = lambda: util.checksignature(func)(ui, *args, **cmdoptions)
 File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 803, in check
   return func(*args, **kwargs)
 File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 183, in 
closure
   return func(*(args + a), **kw)
 File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 803, in check
   return func(*args, **kwargs)
 File "/usr/lib/python2.7/dist-packages/hgext/mq.py", line 3525, in mqcommand
   return orig(ui, repo, *args, **kwargs)
 File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 803, in check
   return func(*args, **kwargs)
 File "/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 5426, in 
push
   opargs=opts.get('opargs'))
 File "/usr/lib/python2.7/dist-packages/mercurial/extensions.py", line 183, in 
closure
   return func(*(args + a), **kw)
 File "/usr/lib/python2.7/dist-packages/hgext/git/util.py", line 48, in inner
   return f(*args, **kwargs)
TypeError: exchangepush() got an unexpected keyword argument 'opargs'


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

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mercurial-git depends on:
ii  mercurial   3.6-1
ii  python-dulwich  0.11.2-1+b1
pn  python:any  

--
Jakub Wilk

Bug#798355: marked as done (colord-sensor-argyll: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/colord-sensors/libcolord_sensor_argyll.so)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 17:20:17 +
with message-id 
and subject line Bug#798355: fixed in colord 1.2.12-1
has caused the Debian Bug report #798355,
regarding colord-sensor-argyll: fails to upgrade from 'jessie' - trying to 
overwrite /usr/lib/x86_64-linux-gnu/colord-sensors/libcolord_sensor_argyll.so
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.)


-- 
798355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: colord-sensor-argyll
Version: 1.2.11-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' 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 colord-sensor-argyll.
  Preparing to unpack .../colord-sensor-argyll_1.2.11-1_amd64.deb ...
  Unpacking colord-sensor-argyll (1.2.11-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/colord-sensor-argyll_1.2.11-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/colord-sensors/libcolord_sensor_argyll.so', which is 
also in package colord 1.2.1-1+b2


cheers,

Andreas


colord=1.2.1-1+b2_colord-sensor-argyll=1.2.11-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: colord
Source-Version: 1.2.12-1

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

Debian distribution maintenance software
pp.
Christopher James Halse Rogers  (supplier of updated colord 
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, 06 Nov 2015 10:51:38 -0600
Source: colord
Binary: libcolord-dev libcolord2 colord colord-sensor-argyll colord-data 
gir1.2-colord-1.0 libcolorhug-dev libcolorhug2 gir1.2-colorhug-1.0
Architecture: source all amd64
Version: 1.2.12-1
Distribution: unstable
Urgency: medium
Maintainer: Christopher James Halse Rogers 
Changed-By: Christopher James Halse Rogers 
Description:
 colord - system service to manage device colour profiles -- system daemon
 colord-data - system service to manage device colour profiles -- data files
 colord-sensor-argyll - system service to manage device colour profiles -- 
argyll sensor
 gir1.2-colord-1.0 - GObject introspection data for the colord library
 gir1.2-colorhug-1.0 - GObject introspection data for the colorhug library
 libcolord-dev - system service to manage device colour profiles -- development 
fi
 libcolord2 - system service to manage device colour profiles -- runtime
 libcolorhug-dev - library to access the ColorHug colourimeter -- development 
files
 libcolorhug2 - library to access the ColorHug colourimeter -- runtime
Closes: 751212 795536 798355
Changes:
 colord (1.2.12-1) unstable; urgency=medium
 .
   * Bump standards-version; no changes required
   * Use canonical Vcs-Git URL
   * Fix Files: glob in debian/copyright to actually match
   * Drop obsolete XS-Testsuite stanza; dpkg handles this now
   * Move hardening-check lintian override to correct package
   * Fix FTBFS on !Linux architectures.
 Argyll is now linux-only, so guard all the features that rely on it
 behind linux-any.
 Thanks to Pino Toscano  (Closes: 795536)
   * Update libcolorhug symbols for 1.2.12 release
   * Really, truly, remove obsolete colord.conf. (Closes: 751212)
   * colord-plugin-argyll: fix upgrade from Jessie.
 This package was split out of colord as argyll has become Linux-only, so 
we need
 to do the Breaks/Replaces dance. (Closes: 798355)
Checksums-Sha1:
 330cc769127e37e0476d6b8492f0d5fcbcf884a1 2887 colord_1.2.12-1.dsc
 46c6fda75928b118a8c5d152bba6234a9ffca0a4 1214992 colord_1.2.12.orig.tar.xz
 ebfcf7acf8767ce2cca1827742e06063275df7c4 20936 colord_1.2.12-1.debian.tar.xz
 3

Bug#797961: ecryptfs-utils: encrypted swap fails

[GCS]

On Fri, Sep 4, 2015 at 1:24 AM, Richard Jasmin  wrote:
> one has to rely on ecryptfs.
>
> sudo ecryptfs-setup-swap
>
> to get encrypted swap in the first place.
 Does it work now on your machine?

> When using it we are presented with another problem.
>
> On boot swap fails to properly encrypt.You get a nice "system service
> cryptswapper" is busy (time remaining) notice, which does nothing but timeout.
 What does '/sbin/cryptdisks_start cryptswap1' outputs on your system
when swap doesn't work?

> Swap either never gets its random key, never gets written to disk, or never
> bothers to properly mount itself.
 Can you check it's not active at all, 'free -m' shows it's not available?

> Unfortunately I cannot tell you which happens as all I can tell is that swap
> never gets mounted.There are no /dev/mapper entries for swap, even though 
> there
> SHOULD BE.
 Can you do 'blkid /dev/[your swap partition' and its output matches
the one set in '/etc/crypttab'?

> I do not know yet how repeatable this issue is.This is the first occurrence
> since swap has been encrypted.
 Do you have experience if it works sometimes when you reboot or
constantly fails?

Thanks,
Laszlo/GCS

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

[gregor herrmann]

On Tue, 03 Nov 2015 22:35:10 +0100, Kurt Roeckx wrote:

> On Tue, Nov 03, 2015 at 10:33:21PM +0100, Kurt Roeckx wrote:
> > On Tue, Nov 03, 2015 at 09:56:36PM +0100, gregor herrmann wrote:

> > > At a quick glance this looks good, since there's only
> > > SSLv23_client_method() left. What confuses me a bit is
> > > - in the .xs file the allow_sslv3 variable
> > > - in the .pm file the HTTPS_VERSION environmen variable.
> > 
> > Since jessie SSLv23_client_method() doesn't support SSLv3 anymore,
> > SSLv2 was removed before.  So "allow_sslv3" doesn't make sense, at
> > least in Debian.  If you really wanted to allow SSLv3 the proper
> > way to do that was by default set the option SSL_OP_NO_SSLv3 (and
> > SSL_OP_NO_SSLv2) and then don't set SSL_OP_NO_SSLv3 when it's
> > allowed.  That would be with the SSL_{CTX_}set_options function.
> > 
> > The code still seems to have a reference to the library when it
> > was called ssleay and when TLS didn't exist, at least the version
> > I looked at, and so seems to pick between SSLv2 and SSLv3.
> > 
> > HTTPS_VERSION seems really weird.  There is also a
> > $DEFAULT_VERSION set to 23 which then makes it use SSLv3, and
> > setting it to 3 makes it use SSLv2?
> 
> There is this text:
> SSL versions
> "Crypt::SSLeay" tries very hard to connect to *any* SSL web server
> accomodating servers that are buggy, old or simply not
> standards-compliant. To this effect, this module will try SSL
> connections in this order:
> 
> SSL v23
> should allow v2 and v3 servers to pick their best type
> 
> SSL v3
> best connection type
> 
> SSL v2
> old connection type
> 
> Unfortunately, some servers seem not to handle a reconnect to SSL v3
> after a failed connect of SSL v23 is tried, so you may set before using
> LWP or Net::SSL:
> 
> $ENV{HTTPS_VERSION} = 3;
> 
> to force a version 3 SSL connection first. At this time only a version 2
> SSL connection will be tried after this, as the connection attempt order
> remains unchanged by this setting.

Thanks for taking the time to look into this.

I have to admit that I'm still not completely sure if/how this
affects us packaging-wise. My current understanding is, that the
library would allow to set SSLv3 via HTTPS_VERSION which will fail
now on Debian but that it should just work fine with the default
values. Is this correct?

If yes I guess we can just take 0.73_04 as is and everything should
work. (Or maybe we want to patch the documentation to say that SSLv3
won't work anymore on Debian.)

In any case I've imported 0.73_04 as 0.73.04-1 and pushed it to
Alioth.


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Ludwig Hirsch: Nicht küssen


signature.asc
Description: Digital Signature

Processed: Re: Bug#804222: harvid: FTBFS: *** No rule to make target '../libharvid/libharvid.a', needed by 'harvid'. Stop.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #804222 [src:harvid] harvid: FTBFS: *** No rule to make target 
'../libharvid/libharvid.a', needed by 'harvid'.  Stop.
Added tag(s) patch.

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

Bug#804222: harvid: FTBFS: *** No rule to make target '../libharvid/libharvid.a', needed by 'harvid'. Stop.

[Andreas Cadhalpun]

Control: tags -1 patch

Hi Chris,

On 06.11.2015 12:37, Chris Lamb wrote:
> harvid fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   cc -c -o timecode.o -g -O2 -fstack-protector-strong -Wformat
>   -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2`pkg-config
>   --cflags libavcodec libavformat libavutil libswscale` timecode.c
>   export PKG_CONFIG_PATH=;\
>   cc -c -o vinfo.o -g -O2 -fstack-protector-strong -Wformat
>   -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2`pkg-config
>   --cflags libavcodec libavformat libavutil libswscale` vinfo.c
>   make[3]: *** No rule to make target '../libharvid/libharvid.a', needed
>   by 'harvid'.  Stop.

The problem is that upstream's Makefile is not compatible with parallel
building. Attached patch fixes this.

Best regards,
Andreas

Description: Fix parallel build
 libharvid is required to build the harvid binary in the src directory.
 Declaring this dependency is only possible, when changing the $(SUBDIRS)
 target from double-colon to single-colon, since double-colon implies
 independence.
 But then it has to be marked .PHONY as well, or nothing will be built.

Author: Andreas Cadhalpun 
Last-Update: <2015-11-06>

--- harvid-0.8.0.orig/Makefile
+++ harvid-0.8.0/Makefile
@@ -3,7 +3,9 @@ SUBDIRS = libharvid src doc
 
 default: all
 
-$(SUBDIRS)::
+src: libharvid
+
+$(SUBDIRS):
 	$(MAKE) -C $@ $(MAKECMDGOALS)
 
 all clean man install uninstall install-bin install-man uninstall-bin uninstall-man install-lib uninstall-lib: $(SUBDIRS)
@@ -11,4 +13,4 @@ all clean man install uninstall install-bin install-man uninstall-bin uninstall-
 dist:
 	git archive --format=tar --prefix=harvid-$(VERSION)/ HEAD | gzip -9 > harvid-$(VERSION).tar.gz
 
-.PHONY: clean all subdirs install uninstall dist install-bin install-man uninstall-bin uninstall-man install-lib uninstall-lib
+.PHONY: clean all subdirs install uninstall dist install-bin install-man uninstall-bin uninstall-man install-lib uninstall-lib $(SUBDIRS)

Processed: Debian bug #804240

[Debian Bug Tracking System]

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

> tags 804240 + moreinfo
Bug #804240 [libsane] libsane: scanning does not work with HPLIP backend
Added tag(s) moreinfo.
> --
Stopping processing here.

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

Bug#803974: marked as done (libnet-tclink-perl: FTBFS: Uses SSLv3_client_method)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 16:24:29 +
with message-id 
and subject line Bug#803974: fixed in libnet-tclink-perl 3.4.0-8
has caused the Debian Bug report #803974,
regarding libnet-tclink-perl: FTBFS: Uses SSLv3_client_method
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.)


-- 
803974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnet-tclink-perl
Version: 3.4.0-7
Severity: serious

Hi,

Your package does this in tclink.c:
c->meth = SSLv3_client_method();

Please call SSLv23_client_method() instead. The SSLv3_* methods
only supports SSLv3 while the SSLv23_* is the only that supports
multiple versions.

The SSLv3_* methods have now been removed in unstable.

SSLv3 is no longer considered secure and you should stop using it.
SSLv3 support has been disabled in jessie when using the SSLv23_*
methods but you could still use it using the SSLv3_* methods.

I suggest you fix this in all releaes.


Kurt
--- End Message ---
--- Begin Message ---
Source: libnet-tclink-perl
Source-Version: 3.4.0-8

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libnet-tclink-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: Fri, 06 Nov 2015 16:39:49 +0100
Source: libnet-tclink-perl
Binary: libnet-tclink-perl
Architecture: source
Version: 3.4.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 803974
Description: 
 libnet-tclink-perl - Perl interface to the TrustCommerce payment gateway
Changes:
 libnet-tclink-perl (3.4.0-8) unstable; urgency=medium
 .
   * Team upload.
   * Rename autopkgtest configuration file(s) as per new pkg-perl-
 autopkgtest schema.
   * Add patch no-SSLv3.patch to use SSLv23_client_method() instead of the
 insecure and removed SSLv3_client_method().
 Thanks to Kurt Roeckx for the bug report. (Closes: #803974)
Checksums-Sha1: 
 149b20c97b5afe6f9ae0a9fa4d2574d984298643 2245 libnet-tclink-perl_3.4.0-8.dsc
 8d9c58918d8844421900681e8f8911c66711aed8 4000 
libnet-tclink-perl_3.4.0-8.debian.tar.xz
Checksums-Sha256: 
 7c4ec6a08a356a3e4c44caaeaf6b249d5864fcff4d37f3f6d9d903ee682e5cbd 2245 
libnet-tclink-perl_3.4.0-8.dsc
 b2acd02eae169f253c5a1b224c6723c64722591906b3d767e1de8354b71a15b0 4000 
libnet-tclink-perl_3.4.0-8.debian.tar.xz
Files: 
 109351e8b5d54d67b11057fd6807418f 2245 perl optional 
libnet-tclink-perl_3.4.0-8.dsc
 e7f6ffe3d647a3bf854dc64524678c91 4000 perl optional 
libnet-tclink-perl_3.4.0-8.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWPMouXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGLtEQAMKDBlbT3bQIj1SI4atTDAdH
fDQ3mB77VwYUiTNf0kNDTW5lZRPzlGTwYqhq3KzcWUYxMmqtOr6MntN5itIF4rU0
S3cI3ijP5zm6aAocieMl5ZIP1BZldOyFpdpe1VBzZQgRMnJRov2tyAiIBTaT1w+r
pJVWjfXDxRh7FG+dwN7fqNes8AXPH/JgpWx8bU/E2BKjge74kSRmkJwF/tbsfc0/
6dfpBNkzUIJrlLhUWBoqyKkmcCTNwvsfeOKP8z0Qmo474HJwjfgrQMKCDy9J26wV
GafKeLLEff/K79vsBwNZEuuB19srGwXgWRvA2pomlvdpa/W4IuAS+1OUeAfdJkxA
g4BwqqPZODJzkGXgCODcg0z+ipejz2v9gucDqdFeVOuyZ422Jfus2xdH8TVZqqyE
QkbYGnO5Nt1m+YaV5ip49g3V3CUDuHRfhzZ1o/mWjuqqL+L1rBxpzTPQzeXeaUsB
A+Veteoow8Ya0sf/uOOkCbXYvrI+wAgZ2gsjpsYmVUVzng3vQhhBdXpNJQB4Xf/l
9n+3/1/Ap3eq2FV+HgtBkXra+t6Mj+hqM52+eYgunBP7wdgaRUcHkmLCc/2vEIP6
oYNeI2P2zFvGAAx6XR37zLKpryaMxz3wFg2GTPzjoh0jn/CuOzWp0KEkPA6JcbbW
lxuldLYcFR3Nw7woFxTI
=byK7
-END PGP SIGNATURE End Message ---

Bug#804166: marked as done (nm.debian.org: link to resend challenge email is public)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 15:40:07 +
with message-id <8235c0bc97ac4ddd1f1ecdfbed2e3...@hogwarts.powdarrmonkey.net>
and subject line Re: Bug#804166: nm.debian.org: link to resend challenge email 
is  public
has caused the Debian Bug report #804166,
regarding nm.debian.org: link to resend challenge email is public
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.)


-- 
804166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nm.debian.org
Severity: serious
Justification: I said so

We do not require authentication before displaying the "Resend email challenge"
link on a person's profile, nor when resending the challenge. Comedy ensues
when we get crawled.


-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.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)
--- End Message ---
--- Begin Message ---

On 2015-11-05 16:25, Jonathan Wiltshire wrote:
We do not require authentication before displaying the "Resend email 
challenge"
link on a person's profile, nor when resending the challenge. Comedy 
ensues

when we get crawled.


I have resolved this by raising a 403 error if the requester is not 
logged in, which is better than nothing.



--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits--- End Message ---

Bug#804240: libsane: scanning does not work with HPLIP backend

[Jörg Frings-Fürst]

Hello Raphaël,

first thanks for your bug report.

Do you have some more informations as error messages or so?

Thanks

CU
Jörg


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54526 Niederkail

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.





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

Bug#804167: fails to upgrade

[Peter Palfrader]

On Fri, 06 Nov 2015, Andreas Henriksson wrote:

> Hi again.
> 
> On Fri, Nov 06, 2015 at 03:01:08PM +0100, Peter Palfrader wrote:
> [...]
> > But it should work.
> > 
> > An "exit 0" at the end, or a "if [ -d ... ]; then rmdir .. ; fi" would
> > also work instead and might be preferable.
> 
> Please stop suggesting exit 0. It does not work. Hopefully the attached
> minimal testcase will convince you of this. The final "exit 0" will
> simply never be reached. run: ./foo.sh && echo $?

It will.  This is why I suggest it.

| weasel@defiant:~$ cat ./tst.sh
| #!/bin/sh
| set -xe
| false && true
| exit 0
| weasel@defiant:~$ ./tst.sh 
| + false
| + exit 0
| weasel@defiant:~$


> (Try also replace 'false' with 'false && true' to more exactly simulate
> your particular bug case.)

Yeah.  Maybe you should try it.

> (... and even if it was reached, that would certainly throw away
> any exit code - not just the rmdir one.)

No it wouldn't.

| weasel@defiant:~$ cat ./tst2.sh
| #!/bin/sh
| set -xe
| true && false
| exit 0
| weasel@defiant:~$ ./tst2.sh
| + true
| + false
| e1:weasel@defiant:~$ 


-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#742347: Fwd: Re: [Pkg-javascript-devel] Bug#742347: Bug#742347: tilemill vs mapbox studio?

[Sebastiaan Couwenberg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06-11-15 16:16, Ross Gammon wrote:
> Also not sure if Bas is still reading Javascript list (so cc'd).

I am, so need to CC.

Kind Regards,

Bas

- -- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWPMaeAAoJEGdQ8QrojUrxfX8P/0KzMJ+/5Km0ElKoDE89sJOn
RdTGsxqhJDwHAdL2c7qZgW21ijpgbYAm5AzpgIt2x5sfXusc+DDMkTBiqHjYu783
T+5+GU5ePq1wru6z1RGgMIkGkLoAyzERJxGoApE5q4ZXxJ9QEiiW/jCSsWTqQDuD
dbU9xvm24eesRMjznGMrzzGoij+FjDD2WQfXG8pMJWVplgY5S95FV5quNLmcEuQw
dkKBMcg7xubpGQb+pKVaq8qQ7SqtdNhdJ12wMxDqJeMW9dL5ctSHhtXZBYTY17iO
W7lxiU7kweCikI7y0P0IIVaL/0WRmbvPbNaSDvi05zXq52vdtakY5CilGpT1sEQ4
lqmMo/12KDRuT/5zaFfk2rmbbMI2JBTZ8RTwszTYFHE0Rk8qGTNUwyD0HXBFTxQz
eskvKTY+QZOuzEEHYBa7N+NDNRx+8xrfHSj8Ah0GmuH7iabzLhOIBUd+aQaPq4QF
FKop9hD7X0VMh6GZ8vH3DCZpDG+XAo6TMcN2kRI3cqohlk+mYmip1y4YbTcpDpit
Fhjg8htfMcVIwYF2Kd+94IkrbdWP7qmDbMRa9kAGBkNAuUO01+8SKDBHHrCPAsf9
B3HqUgSuoAbrLqjxyff/yDv1IV2JITV8lE5pu+MWvSPejeM/D+VZDeH1gQmZVZue
pbQPQmwI8WmiivDPjcHa
=jE74
-END PGP SIGNATURE-

Bug#804167: fails to upgrade

[Andreas Henriksson]

Hi again.

On Fri, Nov 06, 2015 at 03:01:08PM +0100, Peter Palfrader wrote:
[...]
> But it should work.
> 
> An "exit 0" at the end, or a "if [ -d ... ]; then rmdir .. ; fi" would
> also work instead and might be preferable.

Please stop suggesting exit 0. It does not work. Hopefully the attached
minimal testcase will convince you of this. The final "exit 0" will
simply never be reached. run: ./foo.sh && echo $?
(Try also replace 'false' with 'false && true' to more exactly simulate
your particular bug case.)

(... and even if it was reached, that would certainly throw away
any exit code - not just the rmdir one.)

rmdir failing is not the end of the world anyway, it's just a
"lets be nice and clean up if we can" kind of thing.

In your very obscure case that noone else triggered so far there
is no directory to clean up anyway, so don't worry! :P

Regards,
Andreas Henriksson


foo.sh
Description: Bourne shell script

Bug#742347: Fwd: Re: [Pkg-javascript-devel] Bug#742347: Bug#742347: tilemill vs mapbox studio?

[Ross Gammon]

Sorry - dropping the bug and Antoine was unintentional, so forwarding my
reply to javascript list. Also not sure if Bas is still readiing
Javascript list (so cc'd).


 Forwarded Message 
Subject: Re: [Pkg-javascript-devel] Bug#742347: Bug#742347: tilemill vs
mapbox studio?
Date: Fri, 6 Nov 2015 15:57:58 +0100
From: Ross Gammon 
To: pkg-javascript-de...@lists.alioth.debian.org

On 11/05/2015 05:11 PM, Jérémy Lal wrote:
> 
> 
> 2015-11-05 17:04 GMT+01:00 Bas Couwenberg  >:
> 
> On 2015-11-05 16:59, Antoine Beaupré wrote:
> 
> On 2015-11-05 09:52:19, Bas Couwenberg wrote:
> 
> The openstreetmap-carto developers have mostly switched to
> kosmtic:
> 
> https://github.com/kosmtik/kosmtik
> 
> 
> is that a fork of tilemill? how does it differ?
> 
> 
> It's not a fork. It's not a Mapbox project.
> 
> maybe a new ITP should be opened for this then?
> 
> 
> It's still alpha, but shows much more promise than mapbox-studio as
> an alternative to tilemill.
> 
> If you want to spend time packaging an alternative for tilemill, I
> think kosmtik is your best option.
> 
> 
> Indeed it looks like an alternative to tilemill.
> Mapbox studio classic is not really as good, and to be released mapbox
> studio (but i don't know when)
> is very promising.

Every now and then I try running tilemill from the github source tree to
see if it is close to something that could be packaged. But I didn't
have success the last couple of times. There is certainly no sniff of a
coming release. It is a shame considering all of the hard work Dave put
in to package all the dependencies.

Not knowing about kosmtk, I started working on mapbox (the one released
in npm):
https://wiki.debian.org/Javascript/Nodejs/Tasks/mapbox-studio
Feel free to grab one of the dependencies to package if you are looking
for work.

But kosmtik certainly looks like it would be a much quicker win, and a
better place to start:
$ npm2deb depends kosmtik
Dependencies:
NPM   Debian
kosmtik (0.0.12)  None
├─ carto (^0.15.2)node-carto (0.9.5-2)
├─ generic-pool (^2.2.0)  node-generic-pool
(2.0.3-1)
├─ js-yaml (^3.4.2)   None
├─ json-localizer (0.0.3) None
├─ leaflet (^0.7.3)   None
├─ leaflet-formbuilder (^0.2.0)   None
├─ leaflet-hash (^0.2.1)  None
├─ mapnik (^3.4.7)node-mapnik
(1.2.3-1build1)
├─ nomnom (^1.8.1)None
├─ npm (^3.3.5)   None
├─ request (^2.64.0)  node-request
(2.26.1-1)
└─ semver (^5.0.3)node-semver (2.1.0-2)

Build dependencies:
NPM   Debian
mocha (^2.2.5)node-mocha (1.20.1-1)

I will do an ITP & create a task page over the weekend. But please jump
in when/if any of you like. My current work rate is not very high (one
package every other day).

Cheers,

Ross




___
Pkg-javascript-devel mailing list
pkg-javascript-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel


signature.asc
Description: OpenPGP digital signature

Bug#777861: gauche-c-wrapper: ftbfs with GCC-5

[Jens Thiele]

maybe at least play a bit safer:

Index: gauche-c-wrapper-0.6.1/src/c-parser.c
===
--- gauche-c-wrapper-0.6.1.orig/src/c-parser.c
+++ gauche-c-wrapper-0.6.1/src/c-parser.c
@@ -1668,6 +1668,8 @@ ScmObj Scm_ParseMacroCode(ScmObj in, Scm
 {
 static ScmObj trigger_line = SCM_FALSE;
 ScmObj line_str;
+ScmObj next_line_str; /* one line look-ahead */
+ScmObj skip_regex;
 
 /* skip the first line '# 1 ""' */
 Scm_ReadLineUnsafe(SCM_PORT(in));
@@ -1682,17 +1684,40 @@ ScmObj Scm_ParseMacroCode(ScmObj in, Scm
 }
 }
 
-while (!SCM_EOFP(line_str = Scm_ReadLineUnsafe(SCM_PORT(in {
+skip_regex = Scm_RegComp(SCM_STRING(SCM_MAKE_STR_IMMUTABLE("^# [0-9]+ 
\"\"")), 0);
+line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
+next_line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
+while (!SCM_EOFP(line_str)) {
+/* skip lines starting with "# " and matching regexp and join with 
following line */
+Scm_Printf(SCM_CURERR, "line_str = %S\n", line_str);
+if (!SCM_EOFP(next_line_str))
+Scm_Printf(SCM_CURERR, "next_line_str = %S\n", next_line_str);
+while (!SCM_EOFP(next_line_str)
+   && (SCM_STRING_LENGTH(next_line_str) > 2)
+   && (Scm_StringRef(SCM_STRING(next_line_str), 0, 0) == 35)
+   && (Scm_StringRef(SCM_STRING(next_line_str), 1, 0) == 32)
+   && SCM_REGMATCHP(Scm_RegExec(SCM_REGEXP(skip_regex), 
SCM_STRING(next_line_str {
+next_line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
+if (!SCM_EOFP(next_line_str)) {
+line_str = Scm_StringAppend2(SCM_STRING(line_str), 
SCM_STRING(next_line_str));
+next_line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
+}
+}
 if (SCM_NULLP(macro_list)) {
-Scm_Error("[bug] lost macro body");
+Scm_Error("[bug] more cpp output than expected");
 } else {
 ScmObj pos_name_args = SCM_CDAR(macro_list);
 macro_list = SCM_CDR(macro_list);
 Scm_FilenameSet(SCM_CAAR(pos_name_args));
 Scm_LineNumberSet(SCM_INT_VALUE(SCM_CDAR(pos_name_args)));
 parse_macro_body(SCM_CADR(pos_name_args), SCM_CDDR(pos_name_args), 
line_str);
+line_str = next_line_str;
+next_line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
 }
 }
+if (!(SCM_NULLP(macro_list))) {
+Scm_Error("[bug] less cpp output than expected");
+}
 
 SCM_RETURN(SCM_UNDEFINED);
 }

Bug#804167: fails to upgrade

[Peter Palfrader]

On Fri, 06 Nov 2015, Andreas Henriksson wrote:

> > libuuid1 fails to upgrade cleanly in sid under certain circumstances:
> [...]
> 
> While the upgrade code is no longer needed (given that the migration
> should already have happened during Wheezy->Jessie upgrade) it
> might be useful to keep it around as noted in the commit message of:
> https://anonscm.debian.org/cgit/collab-maint/pkg-util-linux.git/commit/?id=8f35d7f7f1a309239b08eaa0a821d962478f5037
> 
> This commit should fix the problem, verification would be welcome.

It is a roundabout way of fixing this issue.  In particular, it ignores
any errors that rmdir might spew and it makes it less obvious that the
exit code from the [ -d ] is the thing that makes the shell end with a
non-zero exit code.

But it should work.

An "exit 0" at the end, or a "if [ -d ... ]; then rmdir .. ; fi" would
also work instead and might be preferable.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Processed: libsane: scanning does not work with HPLIP backend

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.0.25+git20150927-1
Bug #804240 [libsane] libsane: scanning does not work with HPLIP backend
Marked as fixed in versions sane-backends/1.0.25+git20150927-1.

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

Bug#804240: libsane: scanning does not work with HPLIP backend

[Raphaël Hertzog]

Package: libsane
Version: 1.0.25-1
Severity: serious
Control: fixed -1 1.0.25+git20150927-1

With libsane 1.0.25-1 available in sid, I can't scan with my HP printer.

I use this to start the scanning process:
simple-scan hpaio:/net/HP_Color_LaserJet_2840?ip=192.168.1.10

With libsane 1.0.24-14 in testing, it works.
With libsane 1.0.25+git20150927-1 in experimental, it works.

So I'm filing this serious bug to avoid this regression in testing
and to keep a working package around for unstable users that can quickly
downgrade to the testing version.

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

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

Versions of packages libsane depends on:
ii  acl2.2.52-2
ii  adduser3.113+nmu3
ii  libavahi-client3   0.6.32~rc+dfsg-1
ii  libavahi-common3   0.6.32~rc+dfsg-1
ii  libc6  2.19-22
ii  libexif12  0.6.21-2
ii  libgphoto2-6   2.5.8-3
ii  libgphoto2-port12  2.5.8-3
ii  libieee1284-3  0.2.11-12
ii  libjpeg62-turbo1:1.4.1-2
ii  libsane-common 1.0.25+git20150927-1
ii  libtiff5   4.0.5-1
ii  libusb-1.0-0   2:1.0.20-1
ii  udev   227-2

Versions of packages libsane recommends:
ii  libsane-extras  1.0.22.3
ii  sane-utils  1.0.25+git20150927-1

Versions of packages libsane suggests:
ii  avahi-daemon  0.6.32~rc+dfsg-1
ii  hplip 3.14.6-1+b3

-- no debconf information

Bug#801928: marked as done (python-django-uuidfield: Fails to build from source with Django 1.8)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 13:35:10 +
with message-id 
and subject line Bug#804020: Removed package(s) from unstable
has caused the Debian Bug report #801928,
regarding python-django-uuidfield: Fails to build from source with Django 1.8
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.)


-- 
801928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-uuidfield
Version: 0.5.0-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django18 django18-ftbfs

Hello,

while preparing to upload Django 1.8 to unstable, I rebuilt all reverse
build-dependencies of python-django. Among those I noticed that
python-django-uuidfield fails to build.

Please update your package to work with Django 1.8 as I will upload
it to unstable at the start of November 2015 (and the same time raise
the severity of this bug to serious). Django 1.8.5 is available
in experimental so that you can easily try it out.

The failing build log of your package is available here:
https://people.debian.org/~hertzog/django18-rebuild/python-django-uuidfield_0.5.0-2

Thank you in advance!
--- End Message ---
--- Begin Message ---
Version: 0.5.0-2+rm

Dear submitter,

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

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

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

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

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

Processed: Re: Bug#804167: fails to upgrade

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #804167 [libuuid1] fails to upgrade
Added tag(s) pending.

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

Bug#804167: fails to upgrade

[Andreas Henriksson]

Control: tags -1 + pending

Hello Peter Palfrader.

Thanks for your bug report.

On Thu, Nov 05, 2015 at 05:27:38PM +0100, Peter Palfrader wrote:
> Package: libuuid1
> Version: 2.27.1-1
> Severity: serious
> 
> Hi,
> 
> libuuid1 fails to upgrade cleanly in sid under certain circumstances:
[...]

While the upgrade code is no longer needed (given that the migration
should already have happened during Wheezy->Jessie upgrade) it
might be useful to keep it around as noted in the commit message of:
https://anonscm.debian.org/cgit/collab-maint/pkg-util-linux.git/commit/?id=8f35d7f7f1a309239b08eaa0a821d962478f5037

This commit should fix the problem, verification would be welcome.

Regards,
Andreas Henriksson

Bug#804223: marked as done (r-bioc-variantannotation: FTBFS: Error : objects 'FilterRules', 'seqsplit', 'FilterMatrix', 'subsetByFilter' are not exported by 'namespace:IRanges')

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 13:26:46 +
with message-id 
and subject line Bug#804223: fixed in r-bioc-variantannotation 1.16.3-1
has caused the Debian Bug report #804223,
regarding r-bioc-variantannotation: FTBFS: Error : objects 'FilterRules', 
'seqsplit', 'FilterMatrix', 'subsetByFilter' are not exported by 
'namespace:IRanges'
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.)


-- 
804223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-variantannotation
Version: 1.14.13-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

r-bioc-variantannotation fails to build from source in unstable/amd64:

  [..]

  ** R
  ** inst
  ** preparing package for lazy loading
  Warning: replacing previous import by 'IRanges::FilterRules' when
  loading 'VariantAnnotation'
  Warning: replacing previous import by 'IRanges::FilterMatrix' when
  loading 'VariantAnnotation'
  Error : objects 'FilterRules', 'seqsplit', 'FilterMatrix',
  'subsetByFilter' are not exported by 'namespace:IRanges'
  ERROR: lazy loading failed for package 'VariantAnnotation'
  * removing
  
'/build/r-bioc-variantannotation-1.14.13/debian/r-bioc-variantannotation/usr/lib/R/site-library/VariantAnnotation'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch'
  failed
  make: *** [R_any_arch] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/r-bioc-variantannotation_1.14.13-1.build1.log.gz


Regards,

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


r-bioc-variantannotation.1.14.13-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: r-bioc-variantannotation
Source-Version: 1.16.3-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-variantannotation 
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, 06 Nov 2015 13:08:13 +0100
Source: r-bioc-variantannotation
Binary: r-bioc-variantannotation
Architecture: source amd64
Version: 1.16.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 r-bioc-variantannotation - BioConductor annotation of genetic variants
Closes: 804223
Changes:
 r-bioc-variantannotation (1.16.3-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #804223
Checksums-Sha1:
 dca8c2a11de8da15faaade2e952ca84dbb2d3612 2275 
r-bioc-variantannotation_1.16.3-1.dsc
 415837d0b05c5b1b20471aad6e3b0d2390f28e3f 1311936 
r-bioc-variantannotation_1.16.3.orig.tar.gz
 4b04233b2baa7229b5e5bd48e3db10bed6d1ac42 7148 
r-bioc-variantannotation_1.16.3-1.debian.tar.xz
 465c2e854edcefaaf614345d58b0eaa15538dab3 1863508 
r-bioc-variantannotation_1.16.3-1_amd64.deb
Checksums-Sha256:
 635f2bf0e7783f5380872e2b16d121cf0fb7bf3c1b834caffcbc7ae590cdf4bc 2275 
r-bioc-variantannotation_1.16.3-1.dsc
 2625dd1a9afa55dd888b761f09476d39abfecfbdc553894329e71695e15d8f42 1311936 
r-bioc-variantannotation_1.16.3.orig.tar.gz
 56f030ae17d94eb321b246924294600502c45961fdcdc35612ad6ce4065e54d4 7148 
r-bioc-variantannotation_1.16.3-1.debian.tar.xz
 d8c054b01f9d6c5b41f269f4dba6562d07ca090e013135bb0cd662b9e89047ee 1863508 
r-bioc-variantannotation_1.16.3-1_amd64.deb
Files:
 bc6f7dcf591ef4b19afddd8becd29aa0 2275 gnu-r optional 
r-bioc-variantannotation_1.16.3-1.dsc
 cef655eec3d3653207588f053bdb2257 1311936 gnu-r optional 
r-bioc-variantannotation_1.16.3.orig.tar.gz
 2d67a777fb698f2dadfd7ffb90b80bb9 7148 gnu-r optional 
r-bioc-variantannotation_1.16.3-1.debian.tar.xz
 16b55ba50c64af1b9717a79e35

Bug#802863: marked as done (mondrian: FTBFS: error: is not abstract and does not override)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 13:24:11 +
with message-id 
and subject line Bug#802863: fixed in mondrian 1:3.11.0.1-1
has caused the Debian Bug report #802863,
regarding mondrian: FTBFS: error:  is not abstract and does not 
override
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.)


-- 
802863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mondrian
Version: 1:3.4.1-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

compileJdk15:
 [exec] Using JAVA_HOME: /usr/lib/jvm/default-java
 [exec] Using Ant arguments: -Drequested.java.version=jdk1.5 
-Dskip.download=true compile.java
 [exec] Buildfile: /mondrian-3.4.1/build.xml
 [exec] 
 [exec] compile.java:
 [exec]  [echo] Compiling on JVM Version: 1.7.0_85-b01
 [exec] [javac] Compiling 677 source files to /mondrian-3.4.1/classes
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jConnection.java:604: 
error:  is not abstract 
and does not override abstract method getName(Object) in NamedList
 [exec] [javac] return new 
AbstractNamedList() {
 [exec] [javac] 
 ^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jMember.java:72: error: 
 is not abstract and does not 
override abstract method getName(Object) in NamedList
 [exec] [javac] return new 
AbstractNamedList() {
 [exec] [javac] 
 ^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jLevel.java:139: error: 
 is not abstract and does not 
override abstract method getName(Object) in NamedList
 [exec] [javac] final NamedList list = new 
ArrayNamedListImpl() {
 [exec] [javac] 
^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jHierarchy.java:91: 
error:  is not abstract 
and does not override abstract method getName(Object) in NamedList
 [exec] [javac] return new AbstractNamedList() {
 [exec] [javac]^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jCellSetMetaData.java:34: 
error:  is not 
abstract and does not override abstract method getName(Object) in NamedList
 [exec] [javac] new ArrayNamedListImpl() {
 [exec] [javac]   ^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jCellSetMetaData.java:62: 
error:  is not 
abstract and does not override abstract method getName(Object) in NamedList
 [exec] [javac] new ArrayNamedListImpl() {
 [exec] [javac]^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/xmla/RowsetDefinition.java:6519: error: 
 is not 
abstract and does not override abstract method getName(Object) in NamedList
 [exec] [javac] new ArrayNamedListImpl() {
 [exec] [javac] ^
 [exec] [javac] Note: Some input files use or override a deprecated API.
 [exec] [javac] Note: Recompile with -Xlint:deprecation for details.
 [exec] [javac] Note: Some input files use unchecked or unsafe 
operations.
 [exec] [javac] Note: Recompile with -Xlint:unchecked for details.
 [exec] [javac] 7 errors
 [exec] 
 [exec] BUILD FAILED
 [exec] /mondrian-3.4.1/build.xml:553: Compile failed; see the compiler 
error output for details.
 [exec] 
 [exec] Total time: 12 seconds


Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/mondrian.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: mondrian
Source-Version: 1:3.11.0.1-1

We believe that the bug you reported is fixed in the latest version of
mondrian, 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

Processed: Re: Bug#804234: fs-uae: No source for AROS boot ROM

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #804234 [src:fs-uae] fs-uae: No source for AROS boot ROM
Severity set to 'normal' from 'serious'

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

Bug#804234: fs-uae: No source for AROS boot ROM

[John Paul Adrian Glaubitz]

Control: severity -1 normal

On 11/06/2015 02:04 PM, G. Prentice wrote:
> There are two files in the source package which are distributed without source
> and violate directive 2 of the DFSG:

Well, the FTP team was fine with the ROMs being shipped when
I first uploaded the emulator. AROS is fully open source, so
I don't see where your problem is.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#804234: fs-uae: No source for AROS boot ROM

[G. Prentice]

Source: fs-uae
Version: 2.6.2+dfsg-3
Severity: serious
Tags: upstream
Justification: Policy 2.1

Dear Maintainer,

There are two files in the source package which are distributed without source
and violate directive 2 of the DFSG:
/share/fs-uae/aros-amiga-m68k-ext.bin
/share/fs-uae/aros-amiga-m68k-rom.bin
ROM source code is available on the AROS web site, although compiling the ROMs
from source is another issue.
Removing the ROMs will result in the package being unusable since it depends
on either the free AROS ROMs or the non-free Kickstart ROMs to operate and
run software.

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

Kernel: Linux 4.3.0-gnu (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#804220: marked as done (libmath-bigint-gmp-perl: FTBFS: t/bigintpm.t (Wstat: 256 Tests: 3707 Failed: 1))

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 12:35:53 +
with message-id 
and subject line Bug#804220: fixed in libmath-bigint-gmp-perl 1.44-1
has caused the Debian Bug report #804220,
regarding libmath-bigint-gmp-perl: FTBFS: t/bigintpm.t (Wstat: 256 Tests: 3707 
Failed: 1)
to be marked as done.

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

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


-- 
804220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmath-bigint-gmp-perl
Version: 1.43-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libmath-bigint-gmp-perl fails to build from source in unstable/amd64:

  [..]

  Test Summary Report
  ---
  t/bigintpm.t (Wstat: 256 Tests: 3707 Failed: 1)
Failed test:  791
Non-zero exit status: 1
  Files=11, Tests=6535,  5 wallclock secs ( 0.82 usr  0.05 sys +  4.06
  cusr  0.22 csys =  5.15 CPU)
  Result: FAIL
  Failed 1/11 test programs. 1/6535 subtests failed.
  Makefile:984: recipe for target 'test_dynamic' failed
  make[1]: *** [test_dynamic] Error 255
  make[1]: Leaving directory '/build/libmath-bigint-gmp-perl-1.43'
  dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
  debian/rules:4: 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 or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/libmath-bigint-gmp-perl_1.43-1.build1.log.gz


Regards,

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


libmath-bigint-gmp-perl.1.43-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libmath-bigint-gmp-perl
Source-Version: 1.44-1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libmath-bigint-gmp-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: Fri, 06 Nov 2015 13:19:17 +0100
Source: libmath-bigint-gmp-perl
Binary: libmath-bigint-gmp-perl
Architecture: source
Version: 1.44-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 804220
Description: 
 libmath-bigint-gmp-perl - module for arbitrary precision arithmetic using GMP
Changes:
 libmath-bigint-gmp-perl (1.44-1) unstable; urgency=medium
 .
   * New upstream release.
 Requires Math::BigInt 1.999706. (Closes: #804220)
   * Refresh fix-checklib-fail.patch (offset).
   * Add new upstream copyright holder.
Checksums-Sha1: 
 c6963177fa2cc9098f5105050c8b28a7d83c77ff 2467 
libmath-bigint-gmp-perl_1.44-1.dsc
 34c45bee0c9540da6e846b678ed7edca5f867960 57287 
libmath-bigint-gmp-perl_1.44.orig.tar.gz
 addf9027ea5d1ae15a7a95076f128508d5f5f6b1 3712 
libmath-bigint-gmp-perl_1.44-1.debian.tar.xz
Checksums-Sha256: 
 c0fb139061d3ecfbb91a220e0ad6de07cc14d1bdb5aa6673a91d8af1a4589069 2467 
libmath-bigint-gmp-perl_1.44-1.dsc
 aa4673b5faeed24a8d9b51baca59521c6963ad9258dd33821afa5ec8a6c16d0d 57287 
libmath-bigint-gmp-perl_1.44.orig.tar.gz
 a0f9b6c64dab38fe71a2f8c8f7a0d53bc508abfbf3a33bc7a4bdbfd65982960d 3712 
libmath-bigint-gmp-perl_1.44-1.debian.tar.xz
Files: 
 be4b476c304c97e243a2ffe30ac5b6ee 2467 perl optional 
libmath-bigint-gmp-perl_1.44-1.dsc
 a78336ce940689afe8539ce84e90495d 57287 perl optional 
libmath-bigint-gmp-perl_1.44.orig.tar.gz
 ef5d4acd81b583fd015537b2c9f8027b 3712 perl optional 
libmath-bigint-gmp-perl_1.44-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWPJsaXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG6k0P/jho3fFs5kmhJnhzaTakUl7b
kOFCD9bCvVGPdDsdrxomMDT0/HzTS3ByeZpPEeRyfmek91zE4mzSEfUOpCZQ

Processed: tagging 804184

[Debian Bug Tracking System]

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

> tags 804184 + fixed-upstream
Bug #804184 [torbrowser-launcher] torbrowser-launcher: Download error: Download 
Error: 404 Not Found
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 799717 1.0.4-1
Bug #799717 [stress] stress: ships /usr/share/info/dir.gz on arm64
Marked as fixed in versions stress/1.0.4-1.
>
End of message, stopping processing here.

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

Bug#804222: harvid: FTBFS: *** No rule to make target '../libharvid/libharvid.a', needed by 'harvid'. Stop.

[Chris Lamb]

Source: harvid
Version: 0.8.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

harvid fails to build from source in unstable/amd64:

  [..]

  cc -c -o timecode.o -g -O2 -fstack-protector-strong -Wformat
  -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2`pkg-config
  --cflags libavcodec libavformat libavutil libswscale` timecode.c
  export PKG_CONFIG_PATH=;\
  cc -c -o vinfo.o -g -O2 -fstack-protector-strong -Wformat
  -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2`pkg-config
  --cflags libavcodec libavformat libavutil libswscale` vinfo.c
  make[3]: *** No rule to make target '../libharvid/libharvid.a', needed
  by 'harvid'.  Stop.
  make[3]: Leaving directory '/build/harvid-0.8.0/src'
  Makefile:7: recipe for target 'src' failed
  make[2]: *** [src] Error 2
  make[2]: *** Waiting for unfinished jobs
  ar cru libharvid.a decoder_ctrl.o ffdecoder.o frame_cache.o
  image_cache.o timecode.o vinfo.o
  ar: `u' modifier ignored since `D' is the default (see `U')
  ranlib libharvid.a
  make[3]: Leaving directory '/build/harvid-0.8.0/libharvid'
  make[2]: Leaving directory '/build/harvid-0.8.0'
  dh_auto_build: make -j17 CFLAGS=-g -O2 -fstack-protector-strong
  -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
  LDFLAGS=-Wl,-z,relro -Wl,--as-needed VERSION=0.8.0 returned exit code
  2
  debian/rules:9: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/build/harvid-0.8.0'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/harvid_0.8.0-3.build1.log.gz


Regards,

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


harvid.0.8.0-3.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#804223: r-bioc-variantannotation: FTBFS: Error : objects 'FilterRules', 'seqsplit', 'FilterMatrix', 'subsetByFilter' are not exported by 'namespace:IRanges'

[Chris Lamb]

Source: r-bioc-variantannotation
Version: 1.14.13-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

r-bioc-variantannotation fails to build from source in unstable/amd64:

  [..]

  ** R
  ** inst
  ** preparing package for lazy loading
  Warning: replacing previous import by 'IRanges::FilterRules' when
  loading 'VariantAnnotation'
  Warning: replacing previous import by 'IRanges::FilterMatrix' when
  loading 'VariantAnnotation'
  Error : objects 'FilterRules', 'seqsplit', 'FilterMatrix',
  'subsetByFilter' are not exported by 'namespace:IRanges'
  ERROR: lazy loading failed for package 'VariantAnnotation'
  * removing
  
'/build/r-bioc-variantannotation-1.14.13/debian/r-bioc-variantannotation/usr/lib/R/site-library/VariantAnnotation'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch'
  failed
  make: *** [R_any_arch] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/r-bioc-variantannotation_1.14.13-1.build1.log.gz


Regards,

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


r-bioc-variantannotation.1.14.13-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#804224: ruby-virtus: FTBFS: each_spec.rb:58 # Virtus::AttributeSet#each with a block when the parent has attributes that are duplicates yields the expected attributes

[Chris Lamb]

Source: ruby-virtus
Version: 1.0.5-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  [..]
  
  Finished in 1.23 seconds (files took 0.73448 seconds to load)
  459 examples, 16 failures, 2 pending
  
  Failed examples:
  
  rspec ./spec/unit/virtus/attribute_set/each_spec.rb:58 #
  Virtus::AttributeSet#each with a block when the parent has attributes
  that are duplicates yields the expected attributes
  rspec ./spec/unit/virtus/attribute_set/each_spec.rb:30 #
  Virtus::AttributeSet#each with a block when the parent has no
  attributes yields the expected attributes
  rspec ./spec/unit/virtus/attribute_set/merge_spec.rb:28 #
  Virtus::AttributeSet#merge with a duplicate attribute replaces the
  original attribute
  rspec ./spec/unit/virtus/attribute_set/merge_spec.rb:17 #
  Virtus::AttributeSet#merge with a new attribute adds an attribute
  rspec ./spec/unit/virtus/attribute_set/element_set_spec.rb:16 #
  Virtus::AttributeSet#[]= with a new attribute adds an attribute
  rspec ./spec/unit/virtus/attribute_set/element_set_spec.rb:28 #
  Virtus::AttributeSet#[]= with a new attribute allows #reset to track
  overridden attributes
  rspec ./spec/unit/virtus/attribute_set/element_set_spec.rb:20 #
  Virtus::AttributeSet#[]= with a new attribute allows #[] to access the
  attribute with a symbol
  rspec ./spec/unit/virtus/attribute_set/element_set_spec.rb:24 #
  Virtus::AttributeSet#[]= with a new attribute allows #[] to access the
  attribute with a string
  rspec ./spec/unit/virtus/attribute_set/element_set_spec.rb:44 #
  Virtus::AttributeSet#[]= with a duplicate attribute allows #[] to
  access the attribute with a symbol
  rspec ./spec/unit/virtus/attribute_set/element_set_spec.rb:40 #
  Virtus::AttributeSet#[]= with a duplicate attribute replaces the
  original attribute
  rspec ./spec/unit/virtus/attribute_set/element_set_spec.rb:48 #
  Virtus::AttributeSet#[]= with a duplicate attribute allows #[] to
  access the attribute with a string
  rspec ./spec/unit/virtus/attribute_set/element_set_spec.rb:52 #
  Virtus::AttributeSet#[]= with a duplicate attribute allows #reset to
  track overridden attributes
  rspec ./spec/unit/virtus/attribute_set/append_spec.rb:22 #
  Virtus::AttributeSet#<< with a new attribute indexes the new attribute
  under its #name property
  rspec ./spec/unit/virtus/attribute_set/append_spec.rb:28 #
  Virtus::AttributeSet#<< with a new attribute indexes the new attribute
  under the string version of its #name property
  rspec ./spec/unit/virtus/attribute_set/append_spec.rb:16 #
  Virtus::AttributeSet#<< with a new attribute adds an attribute
  rspec ./spec/unit/virtus/attribute_set/append_spec.rb:41 #
  Virtus::AttributeSet#<< with a duplicate attribute replaces the
  original attribute
  
  Randomized with seed 2982
  
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  --format documentation failed
  ERROR: Test "ruby2.1" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /build/ruby-virtus-1.0.5/debian/ruby-virtus returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ruby-virtus_1.0.5-1.build1.log.gz


Regards,

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


ruby-virtus.1.0.5-1.unstable.amd64.log.txt.gz
Description: application/gzip

Processed: Erlang FTBFS because of #799662

[Debian Bug Tracking System]

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

> severity 799662 serious
Bug #799662 [fop] Null pointer exception at 
org.apache.fop.cli.InputHandler.transformTo
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: [Pkg-erlang-devel] Bug#802400: Bug#802400: erlang: FTBFS: FOP - Exception

[Debian Bug Tracking System]

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

> block 802400 by 799662
Bug #802400 [src:erlang] erlang: FTBFS: FOP - Exception 
 thanks
Stopping processing here.

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

Bug#804184:

[Nicolas Vigier]

Hi,

On Fri, 06 Nov 2015, intrigeri wrote:

> 
> > It looks like it should 
> > download 
> > https://dist.torproject.org/torbrowser/5.5a4-hardened/tor-browser-linux64-5.5a4-hardened_ALL.tar.xz
> >  
> > instead
> 
> No, it should download 5.0.4.

This patch should make it download 5.0.4:
https://github.com/micahflee/torbrowser-launcher/commit/e07beac325b7bd716b7a053dcd5664c113e67458.patch

Nicolas



pgpZtWeSRFZ2G.pgp
Description: PGP signature

Bug#802400: [Pkg-erlang-devel] Bug#802400: Bug#802400: erlang: FTBFS: FOP - Exception

[Sergei Golovan]

block 802400 by 799662
thanks

On Tue, Oct 20, 2015 at 7:43 AM, Sergei Golovan  wrote:
>
> I'd say that It's not a bug in Erlang but a bug in fop. Likely, it's
> bug #799662. I haven't had time to confirm yet whether it's really
> #799662 and whether the patch to #799662 fixes it. I'll do that in a
> few days.

I confirm that after applying the patch from #799662 to fop Erlang build
is fixed. So, I'll bump the severity of #799662 at the moment.

Cheers!
-- 
Sergei Golovan

Bug#751005: new hg doesn't seem to be enough to build clisp for arm*

[Peter Michael Green]

Note that the experimental package is failing with a different error:

gcc -I/«BUILDDIR»/clisp-2.49+hg.2015.05.31/src 
-I/«BUILDDIR»/clisp-2.49+hg.2015.05.31/debian/build/gllib 
-I/«BUILDDIR»/clisp-2.49+hg.2015.05.31/src/gllib -falign-functions=4 -W 
-Wswitch -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations 
-Wimplicit -O2 -DENABLE_UNICODE -DDYNAMIC_FFI -DDYNAMIC_MODULES -c lisparit.c
In file included from /«BUILDDIR»/clisp-2.49+hg.2015.05.31/src/lisparit.d:28:0:
/«BUILDDIR»/clisp-2.49+hg.2015.05.31/src/arilev1.d:270:26: fatal error: 
ariarm.c: No such file or directory
compilation terminated.
Makefile:1299: recipe for target 'lisparit.o' failed
make[1]: *** [lisparit.o] Error 1

Bug#802821: marked as done (openstack-dashboard: postinst error "No module named oslo.config")

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 11:47:16 +0100
with message-id <563c8534.1070...@debian.org>
and subject line Re: openstack-dashboard: postinst error "No module named 
oslo.config"
has caused the Debian Bug report #802821,
regarding openstack-dashboard: postinst error "No module named oslo.config"
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.)


-- 
802821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-dashboard
Version: 2015.1.1-1
Severity: normal


Setting up openstack-dashboard (2015.1.1-1) ...
Traceback (most recent call last):
  File "/usr/share/openstack-dashboard/manage.py", line 25, in 
execute_from_command_line(sys.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 385, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 345, in execute
settings.INSTALLED_APPS
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 46, in 
__getattr__
self._setup(name)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 42, in 
_setup
self._wrapped = Settings(settings_module)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 98, in 
__init__
% (self.SETTINGS_MODULE, e)
ImportError: Could not import settings 'openstack_dashboard.settings' (Is it on 
sys.path? Is there an import error in the settings file?): No module named 
oslo.config
dpkg: error processing package openstack-dashboard (--configure):
 subprocess installed post-installation script returned error exit status 1


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

Debian Release: stretch/sid
  500 testing-updates httpredir.debian.org 
  500 testing security.debian.org 
  500 testing httpredir.debian.org 
  333 unstablehttpredir.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Hi Dmitry,

You're seeing this issue because testing contains a newer
python-oslo.config module, while it still contains Horizon 2015.1.1
instead of version 8.0.0. So in fact, testing contains currently a mix
of the Kilo release and the Liberty release of OpenStack. This is a
consequence of the way Debian repositories are built, and could hardly
be addressed.

Please just wait for all of Liberty to migrate to testing, or use
snapshot.debian.org to use the Kilo release in testing for a while so
that you can use the Kilo OpenStack release before all of Liberty gets
migrated.

Thanks for your understanding,

Thomas Goirand (zigo)

P.S: I'm of course closing this bug.--- End Message ---

Bug#804220: libmath-bigint-gmp-perl: FTBFS: t/bigintpm.t (Wstat: 256 Tests: 3707 Failed: 1)

[Chris Lamb]

Source: libmath-bigint-gmp-perl
Version: 1.43-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libmath-bigint-gmp-perl fails to build from source in unstable/amd64:

  [..]

  Test Summary Report
  ---
  t/bigintpm.t (Wstat: 256 Tests: 3707 Failed: 1)
Failed test:  791
Non-zero exit status: 1
  Files=11, Tests=6535,  5 wallclock secs ( 0.82 usr  0.05 sys +  4.06
  cusr  0.22 csys =  5.15 CPU)
  Result: FAIL
  Failed 1/11 test programs. 1/6535 subtests failed.
  Makefile:984: recipe for target 'test_dynamic' failed
  make[1]: *** [test_dynamic] Error 255
  make[1]: Leaving directory '/build/libmath-bigint-gmp-perl-1.43'
  dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
  debian/rules:4: 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 or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/libmath-bigint-gmp-perl_1.43-1.build1.log.gz


Regards,

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


libmath-bigint-gmp-perl.1.43-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#804219: apt-listdifferences: FTBFS: 1 out of 4 hunks FAILED -- saving rejects to file colordiff-git.rej

[Chris Lamb]

Source: apt-listdifferences
Version: 1.20141011
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

apt-listdifferences fails to build from source in unstable/amd64:

  [..]

 debian/rules override_dh_auto_build
  make[1]: Entering directory '/build/apt-listdifferences-1.20141011'
  patch /usr/bin/colordiff colordiff-git.patch -o colordiff-git   
  File /usr/bin/colordiff is read-only; trying to patch anyway
  patching file colordiff-git (read from /usr/bin/colordiff)
  Hunk #1 succeeded at 7 with fuzz 2.
  Hunk #2 succeeded at 56 (offset -1 lines).
  Hunk #3 FAILED at 165.
  Hunk #4 succeeded at 508 (offset 68 lines).
  1 out of 4 hunks FAILED -- saving rejects to file colordiff-git.rej
  debian/rules:9: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 1
  make[1]: Leaving directory '/build/apt-listdifferences-1.20141011'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/apt-listdifferences_1.20141011.build1.log.gz


Regards,

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


apt-listdifferences.1.20141011.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#777861: gauche-c-wrapper: ftbfs with GCC-5

[Jens Thiele]

Matthias Klose  writes:

> you could use -P, or fix the parsing.

a first minimal hackish patch (not using -P)
likely this is not really good enough yet (but yes it compiles and
passes the tests)

Maybe a version using -P just using the last n lines of the cpp output
would be better?

Index: gauche-c-wrapper-0.6.1/src/c-parser.c
===
--- gauche-c-wrapper-0.6.1.orig/src/c-parser.c
+++ gauche-c-wrapper-0.6.1/src/c-parser.c
@@ -1668,6 +1668,7 @@ ScmObj Scm_ParseMacroCode(ScmObj in, Scm
 {
 static ScmObj trigger_line = SCM_FALSE;
 ScmObj line_str;
+ScmObj next_line_str; /* one line look-ahead */
 
 /* skip the first line '# 1 ""' */
 Scm_ReadLineUnsafe(SCM_PORT(in));
@@ -1682,7 +1683,20 @@ ScmObj Scm_ParseMacroCode(ScmObj in, Scm
 }
 }
 
-while (!SCM_EOFP(line_str = Scm_ReadLineUnsafe(SCM_PORT(in {
+line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
+next_line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
+while (!SCM_EOFP(line_str)) {
+/* skip lines starting with "# " and join with following line */
+while (!SCM_EOFP(next_line_str)
+   && (SCM_STRING_LENGTH(next_line_str)>2)
+   && (Scm_StringRef(SCM_STRING(next_line_str),0,0)==35)
+   && (Scm_StringRef(SCM_STRING(next_line_str),1,0)==32)) {
+next_line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
+if (!SCM_EOFP(next_line_str)) {
+line_str = Scm_StringAppend2(SCM_STRING(line_str), 
SCM_STRING(next_line_str));
+next_line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
+}
+}
 if (SCM_NULLP(macro_list)) {
 Scm_Error("[bug] lost macro body");
 } else {
@@ -1691,6 +1705,8 @@ ScmObj Scm_ParseMacroCode(ScmObj in, Scm
 Scm_FilenameSet(SCM_CAAR(pos_name_args));
 Scm_LineNumberSet(SCM_INT_VALUE(SCM_CDAR(pos_name_args)));
 parse_macro_body(SCM_CADR(pos_name_args), SCM_CDDR(pos_name_args), 
line_str);
+line_str = next_line_str;
+next_line_str = Scm_ReadLineUnsafe(SCM_PORT(in));
 }
 }
 

Bug#804107: marked as done (magnum-common: missing Depends: dbconfig-common)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 10:19:56 +
with message-id 
and subject line Bug#804107: fixed in magnum 1.0.0~b1-4
has caused the Debian Bug report #804107,
regarding magnum-common: missing Depends: dbconfig-common
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.)


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

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package magnum-common.
  (Reading database ... 
(Reading database ... 16671 files and directories currently installed.)
  Preparing to unpack .../magnum-common_1.0.0~b1-3_all.deb ...
  Unpacking magnum-common (1.0.0~b1-3) ...
  Setting up magnum-common (1.0.0~b1-3) ...
  /var/lib/dpkg/info/magnum-common.postinst: 702: .: Can't open 
/usr/share/dbconfig-common/dpkg/postinst
  dpkg: error processing package magnum-common (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   magnum-common


cheers,

Andreas


magnum-common_1.0.0~b1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: magnum
Source-Version: 1.0.0~b1-4

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated magnum 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, 06 Nov 2015 11:03:26 +0100
Source: magnum
Binary: python-magnum magnum-common magnum-api magnum-conductor
Architecture: source all
Version: 1.0.0~b1-4
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 magnum-api - OpenStack containers as a service
 magnum-common - OpenStack containers as a service - API server
 magnum-conductor - OpenStack containers as a service - conductor
 python-magnum - OpenStack containers as a service - Python library
Closes: 804107
Changes:
 magnum (1.0.0~b1-4) unstable; urgency=medium
 .
   * Added missing magnum-common dbconfig-common dependency (Closes: #804107).
   * Added python-openstackclient depends in magnum-api.
Checksums-Sha1:
 53dc090e10d0d4f3c371577a02d0dbbf8951a7a3 3668 magnum_1.0.0~b1-4.dsc
 3353df39c4a8d66a5a466bbc72d9b7c861593108 6648 magnum_1.0.0~b1-4.debian.tar.xz
 ad858583889af8f19f4b458c288a1f723525ed4e 12836 magnum-api_1.0.0~b1-4_all.deb
 b95e06de8926642bca169101fd5e811fc2c4021d 18382 magnum-common_1.0.0~b1-4_all.deb
 4a5cba6a11fc2d89dc4413f9b787a82b549053cc 4822 
magnum-conductor_1.0.0~b1-4_all.deb
 b5971ae5eb8d1822c0199b456c02185763c665c0 238488 
python-magnum_1.0.0~b1-4_all.deb
Checksums-Sha256:
 58047b87242249d2d38163b60a3849559a83338447712055f582752adcfd3561 3668 
magnum_1.0.0~b1-4.dsc
 7059d4cd40318f81a2d4269aeaf6d274e425c1a6cdfdc9135c7a606274153580 6648 
magnum_1.0.0~b1-4.debian.tar.xz
 82c97b9184d7c3853f03c851750d75cb55c606ab957dc610e5886549e8e90411 12836 
magnum-api_1.0.0~b1-4_all.deb
 3061705e74fd3405c762acf224add110051428ef56ec1d931f77b1f175256389 18382 
magnum-common_1.0.0~b1-4_all.deb
 079d07762dc4f83eee96e981d6d1322d3e851af0ad9580fbae84fc2eda64d362 4822 
magnum-conductor_1.0.0~b1-4_all.deb
 6fa2e04b69f36c07f9983dd7d71c10ad24a72e36790ba0f55e5d7c72b55d400c 238488 
python-magnum_1.0.0~b1-4_all.deb
Files:
 f00075d5a8069949fbf86aaef0bfce5f 3668 net extra magnum_1.0.0~b1-4.dsc
 be4d71a784b740df75ea558a84c4c676 6648 net extra magnum_1.0.0~b1-4.debian.tar.xz
 d0a99cad8d80ceb86576a173e2034af8 12836 net extra magnum-api_1.0.0~b1-4_all.deb
 81ed7c2324ac448941498bf886c83577 18382 net extra 
magnum-common_1.0.0~b1-4_all.deb
 f0a226ad38637ce4624051812f1d2af7 4822 net extra 
magnum-conductor_1.0.0~b1-4_all.deb
 7a7d047aa1b4a82dedea54679b

Bug#804184:

[intrigeri]

Jason Hernandez wrote (06 Nov 2015 04:32:48 GMT) :
> Hello -It looks like the name of the binaries has changed as a result of 
> including all supported languages in the same 
> build.https://blog.torproject.org/blog/tor-browser-55a4-hardened-released
> torbrowser-launcher tries to download this URL (on a machine with en_US 
> default).https://dist.torproject.org/torbrowser/5.5a4-hardened/tor-browser-linux64-5.5a4-hardened_en-US.tar.xz

Yes, this will become a problem once 5.5 is stable, but in the meantime:

> It looks like it should 
> download 
> https://dist.torproject.org/torbrowser/5.5a4-hardened/tor-browser-linux64-5.5a4-hardened_ALL.tar.xz
>  
> instead

No, it should download 5.0.4.

Cheers,
-- 
intrigeri

Bug#801933: python-django-guardian

[Brian May]

Brian May  writes:

> and filled a bug report upstream about tests failing (under Django 1.8
> no tests run for Python 2.7 and Python 3.4 or the tests fail for Python
> 3.5):

I made a pull request to fix the non-execution of the tests, which has
been merged upstream:

https://github.com/django-guardian/django-guardian/pull/357

I have another pull request pending that will fix the tests under Django
1.8:

https://github.com/django-guardian/django-guardian/pull/359
-- 
Brian May 

Bug#804149: squeeze update of sudo?

[Raphael Hertzog]

Hello Bdale,

the Debian LTS team would like to fix the security issues which are
currently open in the Squeeze version of sudo:
https://security-tracker.debian.org/tracker/CVE-2015-5602

Would you like to take care of this yourself (once a proper
fix is available upstream)?

If yes, please follow the workflow we have defined here:
http://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

Thank you very much.

Raphaël Hertzog,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Processed: Re: Bug#804149: CVE-2015-5602: Unauthorized privilege escalation in sudoedit

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 http://bugzilla.sudo.ws/show_bug.cgi?id=707
Bug #804149 [sudo] CVE-2015-5602: Unauthorized privilege escalation in sudoedit
Set Bug forwarded-to-address to 'http://bugzilla.sudo.ws/show_bug.cgi?id=707'.

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

Bug#804149: CVE-2015-5602: Unauthorized privilege escalation in sudoedit

[Raphael Hertzog]

Control: forwarded -1 http://bugzilla.sudo.ws/show_bug.cgi?id=707

On Thu, 05 Nov 2015, Laurent Bigonville wrote:
> Apparently a security has been disclosed (CVE-2015-5602) allowing users
> to open files with sudoedit that is not supposed to using a symlinks,
> see: https://www.exploit-db.com/exploits/37710/
> 
> Upstream has released a new fixed version by no following the symlinks
> by default.
> 
> But according to this comment[0], this is not fixing the issue
> completely.

It's really a combination of a specific sudoers configuration
(allowing the edition via root of files possibly under the user's
control) and a lack of checks for this specific case in sudoedit.

I doubt that many systems have such a setup but sudo is not really
helping the administrator to notice their mistake. And depending
on what files the configuration allows to edit, even the patched
1.8.15 does not help...

I left a comment on the upstream ticket:
http://bugzilla.sudo.ws/show_bug.cgi?id=707

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#804171: marked as done (phpmyadmin: does not install)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 09:37:22 +
with message-id 
and subject line Bug#804213: fixed in phpmyadmin 4:4.5.1-3
has caused the Debian Bug report #804213,
regarding phpmyadmin: does not install
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.)


-- 
804213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpmyadmin
Version: 4:4.5.1-2
Severity: normal

près cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] 
Paramétrage de phpmyadmin (4:4.5.1-2) ...
dbconfig-common: writing config to /etc/dbconfig-common/phpmyadmin.conf
dbconfig-common: flushing administrative password
You must invoke apache2-maintscript-helper with an unmodified environment when 
sourcing it
dpkg: erreur de traitement du paquet phpmyadmin (--configure) :
 le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
Des erreurs ont été rencontrées pendant l'exécution :
 phpmyadmin


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

Kernel: Linux 4.1.12 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages phpmyadmin depends on:
ii  dbconfig-common1.8.55
ii  debconf [debconf-2.0]  1.5.57
ii  libapache2-mod-php55.6.14+dfsg-1
ii  libjs-sphinxdoc1.3.1-7
ii  perl   5.20.2-6
ii  php-gettext1.0.11-1
ii  php-seclib 2.0.0-1
ii  php5   5.6.14+dfsg-1
ii  php5-cgi   5.6.14+dfsg-1
ii  php5-json  1.3.7-1
ii  php5-mcrypt5.6.14+dfsg-1
ii  php5-mysql 5.6.14+dfsg-1
ii  ucf3.0030

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd]  2.4.17-2
ii  mysql-client 5.6.25-4
ii  mysql-client-5.6 [virtual-mysql-client]  5.6.25-4
ii  php-tcpdf6.0.093+dfsg-1
ii  php5-gd  5.6.14+dfsg-1

Versions of packages phpmyadmin suggests:
ii  google-chrome-stable [www-browser]   46.0.2490.80-1
ii  iceweasel [www-browser]  42.0-1
ii  konqueror [www-browser]  4:15.08.2-1
ii  links2 [www-browser] 2.12-1+b1
ii  lynx-cur [www-browser]   2.8.9dev6-4
ii  mysql-server 5.6.25-4
ii  mysql-server-5.6 [virtual-mysql-server]  5.6.25-4
ii  opera [www-browser]  12.16.1860
ii  w3m [www-browser]0.5.3-25+b1

-- debconf information:
  phpmyadmin/purge: false
  phpmyadmin/db/app-user: phpmyadmin
  phpmyadmin/remove-error: abort
  phpmyadmin/mysql/method: Unix socket
  phpmyadmin/remote/newhost:
  phpmyadmin/dbconfig-upgrade: true
* phpmyadmin/reconfigure-webserver: apache2
  phpmyadmin/upgrade-backup: true
  phpmyadmin/dbconfig-remove:
  phpmyadmin/upgrade-error: abort
  phpmyadmin/internal/skip-preseed: false
  phpmyadmin/passwords-do-not-match:
  phpmyadmin/db/dbname: phpmyadmin
  phpmyadmin/mysql/admin-user: root
  phpmyadmin/database-type: mysql
  phpmyadmin/missing-db-package-error: abort
* phpmyadmin/dbconfig-install: true
  phpmyadmin/remote/host:
  phpmyadmin/internal/reconfiguring: false
  phpmyadmin/dbconfig-reinstall: false
  phpmyadmin/install-error: ignore
  phpmyadmin/setup-username: admin
  phpmyadmin/remote/port:
--- End Message ---
--- Begin Message ---
Source: phpmyadmin
Source-Version: 4:4.5.1-3

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

Debian distribution maintenance software
pp.
Michal Čihař  (supplier of updated phpmyadmin 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, 06 Nov 2015 10:30:52 +0100
Source: phpmyadmin
Binary: phpmyadmin
Architecture: source all
Ve

Bug#804213: marked as done (phpmyadmin: You must invoke apache2-maintscript-helper with an unmodified environment when sourcing it)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 09:37:22 +
with message-id 
and subject line Bug#804213: fixed in phpmyadmin 4:4.5.1-3
has caused the Debian Bug report #804213,
regarding phpmyadmin: You must invoke apache2-maintscript-helper with an 
unmodified environment when sourcing it
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.)


-- 
804213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpmyadmin
Version: 4:4.5.1-2
Severity: grave
Justification: renders package unusable

There is a bug that occured today while upgrading phpmyadmin (and apache2, so I
can't really say it's not apache bug).

It is now unpossible to install nor upgrade phpmyadmin. It occured to me on
daily upgrade.

apt-get log:

dbconfig-common: flushing administrative password
You must invoke apache2-maintscript-helper with an unmodified environment when
sourcing it
dpkg: błąd przetwarzania pakietu phpmyadmin (--configure):
 podproces zainstalowany skrypt post-installation zwrócił kod błędu 1
Wystąpiły błędy podczas przetwarzania:
 javascript-common
 phpmyadmin
E: Sub-process /usr/bin/dpkg returned an error code (1)




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

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

Versions of packages phpmyadmin depends on:
ii  dbconfig-common1.8.55
ii  debconf [debconf-2.0]  1.5.57
ii  libapache2-mod-php55.6.14+dfsg-1
ii  libjs-sphinxdoc1.3.1-7
ii  perl   5.20.2-6
ii  php-gettext1.0.11-1
ii  php-seclib 1.0.0-2
ii  php5   5.6.14+dfsg-1
ii  php5-json  1.3.7-1
ii  php5-mcrypt5.6.14+dfsg-1
ii  php5-mysql 5.6.14+dfsg-1
ii  ucf3.0030

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd]  2.4.17-2+b1
ii  mysql-client 5.6.25-4
ii  mysql-client-5.6 [virtual-mysql-client]  5.6.25-4
ii  php-tcpdf6.0.093+dfsg-1
ii  php5-gd  5.6.14+dfsg-1

Versions of packages phpmyadmin suggests:
ii  firefox [www-browser]42.0~linuxmint1+betsy
ii  google-chrome-beta [www-browser] 47.0.2526.49-1
ii  links [www-browser]  2.12-1+b1
ii  mysql-server 5.6.25-4
ii  mysql-server-5.6 [virtual-mysql-server]  5.6.25-4
ii  w3m [www-browser]0.5.3-25+b1

-- debconf information:
  phpmyadmin/dbconfig-upgrade: true
  phpmyadmin/dbconfig-install: true
  phpmyadmin/internal/skip-preseed: false
  phpmyadmin/database-type: mysql
* phpmyadmin/reconfigure-webserver: apache2
  phpmyadmin/upgrade-backup: true
  phpmyadmin/mysql/method: Unix socket
  phpmyadmin/db/app-user: phpmyadmin
  phpmyadmin/db/dbname: phpmyadmin
  phpmyadmin/mysql/admin-user: root
  phpmyadmin/missing-db-package-error: abort
  phpmyadmin/install-error: retry
  phpmyadmin/setup-username: admin
  phpmyadmin/internal/reconfiguring: false
  phpmyadmin/purge: false
  phpmyadmin/remote/host:
* phpmyadmin/dbconfig-reinstall: true
  phpmyadmin/upgrade-error: abort
  phpmyadmin/remote/port:
* phpmyadmin/dbconfig-remove: true
  phpmyadmin/remove-error: retry
  phpmyadmin/remote/newhost:
  phpmyadmin/passwords-do-not-match:
--- End Message ---
--- Begin Message ---
Source: phpmyadmin
Source-Version: 4:4.5.1-3

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

Debian distribution maintenance software
pp.
Michal Čihař  (supplier of updated phpmyadmin 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, 06 Nov 2015 10:30:52 +0100
Source: phpmyadmin
Binary: phpmyadmin
Architecture: source all
Version: 4:4.5.1-3
Dis

Bug#797165: marked as done (CVE-2015-0852: integer overflow in PluginPCX.cpp)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 09:32:56 +
with message-id 
and subject line Bug#797165: fixed in freeimage 3.15.1-1.1
has caused the Debian Bug report #797165,
regarding CVE-2015-0852: integer overflow in PluginPCX.cpp
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.)


-- 
797165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeimage
Version: 3.10.0-4
Severity: serious
Tags: security upstream fixed-upstream

Hi,

the following vulnerability was published for freeimage.

CVE-2015-0852[0]:
Integer overflow in PluginPCX.cpp

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-2015-0852
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0852
https://marc.info/?l=oss-security&m=144073280200732&w=2
Please adjust the affected versions in the BTS as needed.

BTW upstream patches are available but they are not minimal patches:
http://freeimage.cvs.sourceforge.net/viewvc/freeimage/FreeImage/Source/FreeImage/PluginPCX.cpp?r1=1.17&r2=1.18&pathrev=MAIN
http://freeimage.cvs.sourceforge.net/viewvc/freeimage/FreeImage/Source/FreeImage/PluginPCX.cpp?r1=1.18&r2=1.19&pathrev=MAIN

Hopefully one the of the people who will discover this RC bug (because
their package depends on freeimage or whatever) can be convinced to take
over this package... it has been orphaned for way too long.

Note that the package has another pending security issue (#786790).

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--- End Message ---
--- Begin Message ---
Source: freeimage
Source-Version: 3.15.1-1.1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated freeimage 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: SHA1

Format: 1.8
Date: Thu, 29 Oct 2015 22:33:32 +0100
Source: freeimage
Binary: libfreeimage-dev libfreeimage3 libfreeimage3-dbg
Architecture: source amd64
Version: 3.15.1-1.1
Distribution: wheezy-security
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Anton Gladky 
Description: 
 libfreeimage-dev - Support library for graphics image formats (development 
files)
 libfreeimage3 - Support library for graphics image formats (library)
 libfreeimage3-dbg - Support library for graphics image formats (debugging 
symbols)
Closes: 797165
Changes: 
 freeimage (3.15.1-1.1) wheezy-security; urgency=high
 .
   * Non-maintainer upload.
   * Fix integer overflow CVE-2015-0852. (Closes: #797165)
Checksums-Sha1: 
 a9c206f0eb2dd894c34fc537a2f6ca23c3dad4e5 2135 freeimage_3.15.1-1.1.dsc
 5a56c590c433ff2573320e7288b194ee617f1de9 5242162 freeimage_3.15.1.orig.tar.gz
 c528ca5f5314214142b46bb7ded8734366cf749e 17812 
freeimage_3.15.1-1.1.debian.tar.gz
 d1c619e5bdb529bc0332fd4f4e7ceb81ef236dc8 2015470 
libfreeimage-dev_3.15.1-1.1_amd64.deb
 547a244e643667a9be3b7d725876ddcb8361773c 837078 
libfreeimage3_3.15.1-1.1_amd64.deb
 4a85b0c7454433c049b4f080aa69b6a81ce3a69b 2939862 
libfreeimage3-dbg_3.15.1-1.1_amd64.deb
Checksums-Sha256: 
 450fd366dad5bd3170fdb2ffa9c779a7a9e39d65dca89c3c8d3ca1a8da242f67 2135 
freeimage_3.15.1-1.1.dsc
 023b242dfe19d1fce328165b78a7fada6ed29718feba38b26760d21f36c79408 5242162 
freeimage_3.15.1.orig.tar.gz
 05fdcd5577bb30487ad7b5e38e24b1e87fb2e8a5db8f8088c7c93543cf92e36a 17812 
freeimage_3.15.1-1.1.debian.tar.gz
 eadc4c6df17d1a24946787dc84d17d0fc354b4a2159300699f68bea83b336969 2015470 
libfreeimage-dev_3.15.1-1.1_amd64.deb
 1c821aad7a9f58002daefcd4b9386f8a8f1bf027e97fb3ab902ce87d5eeabba4 837078 
libfreeimage3_3.15.1-1.1_amd64.deb
 a4af9b3b23bb34edae9474de284156b912a159c355b908769c77f4bb61798ae4 2939862 
libfreeimage3-dbg_3.15.1-1.1_amd64.deb
Files: 
 b8cbe939e31479ca5af0e065414cb24c 2135 libs optional freeima

Bug#803926: marked as done (Should depend on libssl-dev)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 09:22:35 +
with message-id 
and subject line Bug#803926: fixed in spice 0.12.6-4
has caused the Debian Bug report #803926,
regarding Should depend on libssl-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.)


-- 
803926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libspice-server-dev
Version: 0.12.6-3
Severity: serious

libspice-server-dev should depend on the libssl-dev package. Without it
an attempt to compile software with it fails:

$ pkg-config --cflags 'spice-server >= 0.12.0' ; echo $?
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'spice-server', not found


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

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

Versions of packages libspice-server-dev depends on:
ii  libcacard-dev  1:2.4+dfsg-4
ii  libspice-protocol-dev  0.12.10-1
ii  libspice-server1   0.12.6-3

libspice-server-dev recommends no packages.

Versions of packages libspice-server-dev suggests:
ii  pkg-config  0.28-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: spice
Source-Version: 0.12.6-4

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated spice 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: SHA1

Format: 1.8
Date: Fri, 06 Nov 2015 10:43:55 +0300
Source: spice
Binary: libspice-server1 libspice-server1-dbg libspice-server-dev
Architecture: source amd64
Version: 0.12.6-4
Distribution: unstable
Urgency: medium
Maintainer: Liang Guo 
Changed-By: Michael Tokarev 
Description:
 libspice-server-dev - Header files and development documentation for 
spice-server
 libspice-server1 - Implements the server side of the SPICE protocol
 libspice-server1-dbg - Debugging symbols for libspice-server1
Closes: 803926
Changes:
 spice (0.12.6-4) unstable; urgency=medium
 .
   * stop depending libspice-server-dev on libcacard-dev (#802413).
 Instead, remove mention of libcacard from the .pc file, as it
 is not actually used when building with libspice-server.
   * remove Requires.private defs from .pc file -- we're not building static
 libs, but if Requires.private is present, pkg-config requires the other
 .pc files to be present too, which is wrong (Closes: #803926)
Checksums-Sha1:
 11be6bcf3e6307d1e106f9f7e45e06c1cfd14f0e 1936 spice_0.12.6-4.dsc
 ac36c3155a9d6ef901ef805e4d22cecdcc0e8f9c 9096 spice_0.12.6-4.debian.tar.xz
 098c52e7d80fa86078b1b85f4a50c10b3b63b643 530126 
libspice-server-dev_0.12.6-4_amd64.deb
 7d875370ca94f4ceb2cd7b0b897d40d35c2a4cd1 1295542 
libspice-server1-dbg_0.12.6-4_amd64.deb
 8d1fb674c56a13f3bcdbe41a901a5c0cfa0111b3 496538 
libspice-server1_0.12.6-4_amd64.deb
Checksums-Sha256:
 1e5d840fabc70d788f5e167c9e95c732ce7bf884dc5129c222b6339bc64ac76a 1936 
spice_0.12.6-4.dsc
 6f955dafc73e5f4ee80a22e80add2a492020592462337a6d976bbfeb068b66e9 9096 
spice_0.12.6-4.debian.tar.xz
 6f9152e165876e7c3190ac3ddd88ed108ca28bbb963c960a9d1dff7fd6403098 530126 
libspice-server-dev_0.12.6-4_amd64.deb
 330f9e312f91f67480b04f69553d4d01272a921f7302dd9e5b42ce9a6e196fa8 1295542 
libspice-server1-dbg_0.12.6-4_amd64.deb
 f8182c63141ff7e39ab76f7bf286f3eaa6b822e504205f668467b802783605ac 496538 
libspice-server1_0.12.6-4_amd64.deb
Files:
 db7cbb063def75d9f33677b8b90272f6 1936 misc optional spice_0.12.6-4.dsc
 7537bd27af2cbc0669b6267b6dd464ed 9096 misc optional 
spice_0.12.6-4.debian.tar.xz
 c156e1feeb77c95816ee80c0550141a6 530126 libdevel optional 
libspice-server-dev_0.12.6-4_amd6

Bug#803479: marked as done (r-bioc-genomicalignments: FTBFS: cigar_utils.c:179:33: error: request for member 'elts' in something not a structure or union)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 09:22:21 +
with message-id 
and subject line Bug#803479: fixed in r-bioc-genomicalignments 1.6.1-1
has caused the Debian Bug report #803479,
regarding r-bioc-genomicalignments: FTBFS: cigar_utils.c:179:33: error: request 
for member 'elts' in something not a structure or union
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.)


-- 
803479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-genomicalignments
Version: 1.4.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

r-bioc-genomicalignments fails to build from source in unstable/amd64:

  [..]

  cigar_utils.c: In function 'drop_or_append_or_merge_range':
  cigar_utils.c:179:33: error: request for member 'elts' in something
  not a structure or union
 prev_end_plus_1 = range_buf->a.elts[buf_nelt_minus_1] +
   ^
  cigar_utils.c:180:19: error: request for member 'elts' in something
  not a structure or union
 range_buf->b.elts[buf_nelt_minus_1];
 ^
  cigar_utils.c:183:16: error: request for member 'elts' in something
  not a structure or union
  range_buf->b.elts[buf_nelt_minus_1] += width;
  ^
  cigar_utils.c:185:21: warning: assignment from incompatible pointer
  type [-Wincompatible-pointer-types]
   OP_buf_prev_elt = OP_buf->elts +
   ^
  cigar_utils.c:196:18: error: incompatible types when assigning to type
  'CharAE {aka struct char_ae}' from type 'CharAE * {aka struct char_ae
  *}'
 OP_buf_new_elt = new_CharAE(1);
^
  cigar_utils.c: In function 'explode_cigar_ops':
  cigar_utils.c:361:8: error: incompatible types when assigning to type
  'CharAE {aka struct char_ae}' from type 'CharAE * {aka struct char_ae
  *}'
OPbuf = new_CharAE(0);
  ^
  cigar_utils.c: In function 'explode_cigar_op_lengths':
  cigar_utils.c:403:9: error: incompatible types when assigning to type
  'IntAE {aka struct int_ae}' from type 'IntAE * {aka struct int_ae *}'
OPLbuf = new_IntAE(0, 0, 0);
   ^
  cigar_utils.c: In function 'cigar_ranges':
  cigar_utils.c:607:14: error: incompatible types when assigning to type
  'IntPairAE {aka struct intpair_ae}' from type 'IntPairAE * {aka struct
  intpair_ae *}'
 range_buf1 = new_IntPairAE(ans_len, 0);
^
  cigar_utils.c:614:14: error: incompatible types when assigning to type
  'IntPairAEAE {aka struct intpair_aeae}' from type 'IntPairAEAE * {aka
  struct intpair_aeae *}'
 range_buf2 = new_IntPairAEAE(ans_len, ans_len);
^
  cigar_utils.c:621:10: error: incompatible types when assigning to type
  'CharAEAE {aka struct char_aeae}' from type 'CharAEAE * {aka struct
  char_aeae *}'
 OP_buf = new_CharAEAE(cigar_len, 0);
^
  cigar_utils.c:660:16: warning: assignment from incompatible pointer
  type [-Wincompatible-pointer-types]
  range_buf_p = range_buf2.elts + *f_elt - 1;
  ^
  /usr/lib/R/etc/Makeconf:134: recipe for target 'cigar_utils.o' failed
  make[1]: *** [cigar_utils.o] Error 1
  make[1]: Leaving directory '/build/r-bioc-genomicalignments-1.4.1/src'
  make[1]: Entering directory
  '/build/r-bioc-genomicalignments-1.4.1/src'
  make[1]: Leaving directory '/build/r-bioc-genomicalignments-1.4.1/src'
  ERROR: compilation failed for package 'GenomicAlignments'
  * removing
  
'/build/r-bioc-genomicalignments-1.4.1/debian/r-bioc-genomicalignments/usr/lib/R/site-library/GenomicAlignments'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch'
  failed
  make: *** [R_any_arch] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

The full build log is attached or (an alternate build) can be viewed
here:


https://reproducible.debian.net/logs/unstable/amd64/r-bioc-genomicalignments_1.4.1-1.build1.log.gz


Regards,

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


r-bioc-genomicalignments.1.4.1-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: r-bioc-genomicalignments
Source-Version: 1.6.1-1

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

A summary of the change

Processed: forcibly merging 804213 804171

[Debian Bug Tracking System]

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

> forcemerge 804213 804171
Bug #804213 [phpmyadmin] phpmyadmin: You must invoke apache2-maintscript-helper 
with an unmodified environment when sourcing it
Bug #804171 [phpmyadmin] phpmyadmin: does not install
Severity set to 'grave' from 'normal'
Merged 804171 804213
> thanks
Stopping processing here.

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

Bug#804213: phpmyadmin: You must invoke apache2-maintscript-helper with an unmodified environment when sourcing it

[Igor Kowasz]

Package: phpmyadmin
Version: 4:4.5.1-2
Severity: grave
Justification: renders package unusable

There is a bug that occured today while upgrading phpmyadmin (and apache2, so I
can't really say it's not apache bug).

It is now unpossible to install nor upgrade phpmyadmin. It occured to me on
daily upgrade.

apt-get log:

dbconfig-common: flushing administrative password
You must invoke apache2-maintscript-helper with an unmodified environment when
sourcing it
dpkg: błąd przetwarzania pakietu phpmyadmin (--configure):
 podproces zainstalowany skrypt post-installation zwrócił kod błędu 1
Wystąpiły błędy podczas przetwarzania:
 javascript-common
 phpmyadmin
E: Sub-process /usr/bin/dpkg returned an error code (1)




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

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

Versions of packages phpmyadmin depends on:
ii  dbconfig-common1.8.55
ii  debconf [debconf-2.0]  1.5.57
ii  libapache2-mod-php55.6.14+dfsg-1
ii  libjs-sphinxdoc1.3.1-7
ii  perl   5.20.2-6
ii  php-gettext1.0.11-1
ii  php-seclib 1.0.0-2
ii  php5   5.6.14+dfsg-1
ii  php5-json  1.3.7-1
ii  php5-mcrypt5.6.14+dfsg-1
ii  php5-mysql 5.6.14+dfsg-1
ii  ucf3.0030

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd]  2.4.17-2+b1
ii  mysql-client 5.6.25-4
ii  mysql-client-5.6 [virtual-mysql-client]  5.6.25-4
ii  php-tcpdf6.0.093+dfsg-1
ii  php5-gd  5.6.14+dfsg-1

Versions of packages phpmyadmin suggests:
ii  firefox [www-browser]42.0~linuxmint1+betsy
ii  google-chrome-beta [www-browser] 47.0.2526.49-1
ii  links [www-browser]  2.12-1+b1
ii  mysql-server 5.6.25-4
ii  mysql-server-5.6 [virtual-mysql-server]  5.6.25-4
ii  w3m [www-browser]0.5.3-25+b1

-- debconf information:
  phpmyadmin/dbconfig-upgrade: true
  phpmyadmin/dbconfig-install: true
  phpmyadmin/internal/skip-preseed: false
  phpmyadmin/database-type: mysql
* phpmyadmin/reconfigure-webserver: apache2
  phpmyadmin/upgrade-backup: true
  phpmyadmin/mysql/method: Unix socket
  phpmyadmin/db/app-user: phpmyadmin
  phpmyadmin/db/dbname: phpmyadmin
  phpmyadmin/mysql/admin-user: root
  phpmyadmin/missing-db-package-error: abort
  phpmyadmin/install-error: retry
  phpmyadmin/setup-username: admin
  phpmyadmin/internal/reconfiguring: false
  phpmyadmin/purge: false
  phpmyadmin/remote/host:
* phpmyadmin/dbconfig-reinstall: true
  phpmyadmin/upgrade-error: abort
  phpmyadmin/remote/port:
* phpmyadmin/dbconfig-remove: true
  phpmyadmin/remove-error: retry
  phpmyadmin/remote/newhost:
  phpmyadmin/passwords-do-not-match:

Bug#784070: mdadm: diff for NMU version 3.3.2-5.1

[Yann Soubeyrand]

On Thu, 5 Nov 2015 14:17:11 -0600 Bryan Christ  wrote:
> I'll be glad to test this if someone will provide me instructions on how to
> apply the fixes.  I've downloaded all the files from here:
> 
> http://mentors.debian.net/debian/pool/main/m/mdadm/
> 
> I have also extracted mdadm_3.3.2-5.1.dsc with this:
> 
> dpkg-source -x mdadm_3.3.2-5.1.dsc
> 
> It's pretty unclear what to do next.  A few steps of instructions would be
> helpful.

Make sure to install the build-essential package plus all the build
dependencies listed in the .dsc file (Build-Depends: debhelper (>=
6.0.7~), po-debconf, groff-base), then execute the command
dpkg-buildpackage -us -uc inside the source tree you extracted earlier
using dpkg-source -x.

If you want to learn more about package building you can refer to
https://www.debian.org/doc/manuals/maint-guide/build.en.html.

Cheers

Yann