Bug#813580: [Pkg-netfilter-devel] Bug#813580: Bug#813580: No Internet Connection with iptables-1.6.0-2

[Arturo Borrero Gonzalez]

Control: tags -1 moreinfo

On 3 February 2016 at 14:09, Tsu Jan  wrote:
> On Wed, 3 Feb 2016 13:00:24 +0100 Arturo Borrero Gonzalez
>  wrote:
>> On 3 February 2016 at 12:13, Tsu Jan  wrote:
>> You were using connman? Or are you using iptables rules directly?
>> Which version of connman are you running?
>> --
>> Arturo Borrero González
>>
>
> Yes, I use connman, which was upgraded alongside iptables from v1.21-1.2+b1
> to v1.21-1.2+b2 (rebuild against libxtables11).
>
> Downgrading connman alone didn't fix the issue, although I had libxtables10
> too.
>


Hi Tsu,

I would need you to provide additional info about this bug:
* connman config
* connman service systemd detailed log
* connman own log? (if exists)
* kernel log (the dmesg one)
* iptables service systemd detailed log (if exists)
* iptables ruleset (from iptables-save)

thanks
-- 
Arturo Borrero González

Bug#813627: mate-terminal.wrapper doesn't run commands with parameters with -e opti, on

[John Paul Adrian Glaubitz]

On 02/04/2016 06:57 AM, Stefano Salvi wrote:
> I found this bug in a FRESH Jessie install, so this is the DISTRIBUTED
> version. This could be a problem...

I could also report a bug against a FRESH install of SuseLinux 5.3
(1998), that it also still DISTRIBUTED on FTP servers. That doesn't
mean, I should.

The fact remains that Debian Jessie (stable) contains an old version
of MATE which no longer receives updates and it's therefore rather
pointless to report bugs against these old versions.

> It would be better if you put the new wrapper version in stable.

That is not possible, at least not as simple as you would think.
To update packages in stable, a package maintainer can't simply create
a new package version and upload it. They have to file a bug report
with the stable release managers and ask for permission to update
the package.

The stable release managers are rather strict and it needs quite some
effort to convince them to allow packages to be updated in a stable
release unless it's a security-relevant or critical update. Thus, most
package maintainers usually don't bother with fixing such bugs in stable
and just focus on improving the packages in unstable and consequently
testing as these can be updated right away and without any buerocracy
unless we're in a freeze just before the release of a new stable
version.

> Thank you

Regards,
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#803542: trnascan-se_1.3.1+dfsg-1_amd64.changes REJECTED

[Andreas Tille]

Hi,

On Wed, Feb 03, 2016 at 09:27:07PM -0800, Afif Elghraoui wrote:
> > there seems to be something wrong with this package.
> > A DFSG package should not be in non-free.
> > 
> 
> This is the package that you rejected last November because of the
> non-free file dbmalloc.h [1]. The package has the +dfsg suffix because I
> excluded the postscript Manual.ps which cannot be built from source.
> It's my understanding that even non-free packages should meet the dfsg
> as far as possible.

Sounds sensible.
 
> Would you prefer I put the Manual.ps back in so that there is no
> repacked tarball? Otherwise, do you have a more appropriate alternative
> to +dfsg for the repack suffix?

I do not think that the tarball name in itself should be a rejection
reason.  I also use this suffix for repackaged tarballs.  Some people
are using +ds but I'd consider this nitpicking.

BTW, did you possibly contact the copyright holders for choosing a
free license?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#809416: Please don't depend on libvirt-bin

[Guido Günther]

Hi,
On Wed, Dec 30, 2015 at 03:06:29PM +0100, Guido Günther wrote:
> Package: virt-goodies
> Version: 1.2.15-1
> Severity: wishlist
> User: a...@sigxcpu.org
> Usertags: drop-libvirt-bin
> 
> Hi,
> libvirt-bin is a transitional package please use either
> 
> libvirt-daemon-system (if you require the privileged daemon)
> 
> or
> 
> libvirt-daemon (if a daemon started for the current user is enough)

I have placed an NMU in delayed/7 with the attached debdiff. Feel free
to cancel it if you think it's not correct.

Cheers,
 -- Guido
diff --git a/debian/changelog b/debian/changelog
index 98fecd2..f8515ac 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+virt-goodies (0.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Depend on libvirt-daemon-system instead of the transitional libvirt-bin
+(Closes: #809416)
+
+ -- Guido Günther   Thu, 04 Feb 2016 08:24:57 +0100
+
 virt-goodies (0.4-2) unstable; urgency=low
 
   * vmware2libvirt: allow for ide0:0.filename (used by easyvmx). Patch
diff --git a/debian/control b/debian/control
index c501a37..bb317ef 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Vcs-Browser: http://codebrowse.launchpad.net/~ubuntu-virt/virt-goodies/trunk
 
 Package: virt-goodies
 Architecture: all
-Depends: ${misc:Depends}, python-libvirt, libvirt-bin, python, uuid-runtime
+Depends: ${misc:Depends}, python-libvirt, libvirt-daemon-system, python, uuid-runtime
 Recommends: munin-node, munin-libvirt-plugins
 Description: A collection of helpful virtualisation related tools
  Included tools are:

Bug#812796: tokyocabinet: testsuite sometimes failes

[Tobias Frost]

Source: tokyocabinet
Followup-For: Bug #812796

I'm be able to reproduce this on a ppc64el porter box.

Could be caused by https://bugzilla.redhat.com/show_bug.cgi?id=572594, though I
did not come along to test this. 

--
tobi

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

Kernel: Linux 4.0.5-revert-done (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#813659: libcrypto++: FTBFS on x32

[GCS]

Hi Adam, Jeffrey,

On Thu, Feb 4, 2016 at 6:37 AM, Adam Borowski  wrote:
> Source: libcrypto++
> Version: 5.6.1-9
> Severity: normal
> Tags: patch
>
> libcrypto++ currently fails to build on x32.  This is caused by attempts to
> use x86 assembly -- the package would build if it used the portable generic
> code instead.
>
> Here's a patch.  It's a hybrid between disabling assembly and making it work
> -- in most places, it works without changes.  In one place, it tried to
> access a 32-bit variable of type size_t as a 64-bit value, so changing the
> type to word64 works.  I did disable the assembly in two places -- whirlpool
> where it doesn't build (insanely macroized code makes it thoroughly
> unobvious) and rijndael which did compile but segfaults in the testsuite.
>
> The patch could be simpler by disabling assembly outright, or more complete
> by fixing pieces I disabled, but it's probably ok for a first stab.
 Thanks for your patch! I do resend it to the actual upstream
maintainer for information. On the other hand, you may check the
v5.6.3 in experimental which builds and according to the self tests
working right on x32.

Thanks,
Laszlo/GCS
--- libcrypto++-5.6.1.orig/cpu.h
+++ libcrypto++-5.6.1/cpu.h
@@ -96,6 +96,8 @@ _mm_aesdeclast_si128 (__m128i a, __m128i
 
 NAMESPACE_BEGIN(CryptoPP)
 
+#define X32 (defined __ILP32__ && defined __x86_64__)
+
 #if CRYPTOPP_BOOL_X86 || CRYPTOPP_BOOL_X64
 
 #define CRYPTOPP_CPUID_AVAILABLE
--- libcrypto++-5.6.1.orig/rijndael.cpp
+++ libcrypto++-5.6.1/rijndael.cpp
@@ -348,7 +348,7 @@ void Rijndael::Base::UncheckedSetKey(con
 
 void Rijndael::Enc::ProcessAndXorBlock(const byte *inBlock, const byte *xorBlock, byte *outBlock) const
 {
-#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE || defined(CRYPTOPP_X64_MASM_AVAILABLE) || CRYPTOPP_BOOL_AESNI_INTRINSICS_AVAILABLE
+#if (CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE || defined(CRYPTOPP_X64_MASM_AVAILABLE) || CRYPTOPP_BOOL_AESNI_INTRINSICS_AVAILABLE) && !X32
 	if (HasSSE2())
 	{
 		Rijndael::Enc::AdvancedProcessBlocks(inBlock, xorBlock, outBlock, 16, 0);
@@ -1179,7 +1179,7 @@ size_t Rijndael::Enc::AdvancedProcessBlo
 		return AESNI_AdvancedProcessBlocks(AESNI_Enc_Block, AESNI_Enc_4_Blocks, (const __m128i *)m_key.begin(), m_rounds, inBlocks, xorBlocks, outBlocks, length, flags);
 #endif
 	
-#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE || defined(CRYPTOPP_X64_MASM_AVAILABLE)
+#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE && !X32 || defined(CRYPTOPP_X64_MASM_AVAILABLE)
 	if (HasSSE2())
 	{
 		if (length < BLOCKSIZE)
--- libcrypto++-5.6.1.orig/vmac.cpp
+++ libcrypto++-5.6.1/vmac.cpp
@@ -735,7 +735,7 @@ size_t VMAC_Base::HashMultipleBlocks(con
 	return remaining;
 }
 
-static word64 L3Hash(const word64 *input, const word64 *l3Key, size_t len)
+static word64 L3Hash(const word64 *input, const word64 *l3Key, word64 len)
 {
 word64 rh, rl, t, z=0;
 	word64 p1 = input[0], p2 = input[1];
--- libcrypto++-5.6.1.orig/whrlpool.cpp
+++ libcrypto++-5.6.1/whrlpool.cpp
@@ -391,7 +391,7 @@ static const word64 Whirlpool_C[4*256+R]
 // Whirlpool basic transformation. Transforms state based on block.
 void Whirlpool::Transform(word64 *digest, const word64 *block)
 {
-#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE
+#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE && !X32
 	if (HasISSE())
 	{
 		// MMX version has the same structure as C version below

Bug#813665: man-db: man -K gives irrelevant results

[B. Ruva]

Package: man-db
Version: 2.7.5-1
Severity: normal

Dear Maintainer,

man -K searches the nroff source, not the formatted manpages. Because of that 
"man -K california" gives a lot of hits (for commands like more, rev, whereis, 
...) whose manpages don't contain the string "california" (it is contained in 
comments in the nroff source). This problematic behavior is not described in 
man(1).


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

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

Versions of packages man-db depends on:
ii  bsdmainutils   9.0.6
ii  debconf [debconf-2.0]  1.5.56
ii  dpkg   1.17.25
ii  groff-base 1.22.2-8
ii  libc6  2.19-18
ii  libgdbm3   1.8.3-13.1
ii  libpipeline1   1.4.0-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

man-db recommends no packages.

Versions of packages man-db suggests:
ii  elinks [www-browser] 0.12~pre6-5+b2
ii  groff1.22.2-8
ii  iceweasel [www-browser]  38.4.0esr-1~deb8u1
ii  less 458-3
ii  lynx-cur [www-browser]   2.8.9dev1-2+deb8u1
ii  w3m [www-browser]0.5.3-19

-- debconf information excluded

Bug#812469: fixed by update

[-]

This bug has disappeared for me after the following update (copy-paste from
Synaptic History):


Removed the following packages:
libgdome2-cpp-smart0c2a

Upgraded the following packages:
adwaita-icon-theme (3.16.2.1-2) to 3.18.0-2
gir1.2-gtk-2.0 (2.24.28-1) to 2.24.29-1
gir1.2-gtk-3.0 (3.16.6-1) to 3.18.6-1
gir1.2-gtk-vnc-2.0 (0.5.3-1.3) to 0.5.3-1.3+b1
gir1.2-gtkclutter-1.0 (1.4.4-3+b1) to 1.6.6-1
gir1.2-gtksource-3.0 (3.10.2-1) to 3.18.2-1
gir1.2-nmgtk-1.0 (0.9.8.8-1) to 1.0.10-1
gir1.2-vte-2.91 (0.40.2-2) to 0.42.1-2+b1
gpicview (0.2.4-1) to 0.2.4-2+b2
gtk-3-examples (3.16.6-1) to 3.18.6-1
gtk2-engines-pixbuf (2.24.28-1) to 2.24.29-1
libappindicator3-1 (0.4.92-3) to 0.4.92-3.1
libcolord-gtk1 (0.1.25-1.1) to 0.1.26-1
libgail18 (2.24.28-1) to 2.24.29-1
libgtk-3-0 (3.16.6-1) to 3.18.6-1
libgtk-3-bin (3.14.5-1) to 3.18.6-1
libgtk-3-common (3.16.6-1) to 3.18.6-1
libgtk-3-dev (3.16.6-1) to 3.18.6-1
libgtk-vnc-2.0-0 (0.5.3-1) to 0.5.3-1.3+b1
libgtk2.0-0 (2.24.28-1) to 2.24.29-1
libgtk2.0-0:i386 (2.24.28-1) to 2.24.29-1
libgtk2.0-bin (2.24.28-1) to 2.24.29-1
libgtk2.0-common (2.24.22-1) to 2.24.29-1
libgtk2.0-dev (2.24.28-1) to 2.24.29-1
libgtkmathview-bin (0.8.0-10) to 0.8.0-13
libgtkmathview0c2a (0.8.0-10) to 0.8.0-13
libgtkmm-3.0-1v5 (3.16.0-2+b1) to 3.18.0-1
libgtksourceview-3.0-1 (3.18.1-1) to 3.18.2-1
libgtksourceview-3.0-common (3.18.1-1) to 3.18.2-1
libgtksourceview-3.0-doc (3.10.2-1) to 3.18.2-1
libgtksourceview2.0-common (2.10.5-1) to 2.10.5-2
libjavascriptcoregtk-3.0-0 (2.4.7-1) to 2.4.9-3
libkeybinder0 (0.3.0-3) to 0.3.1-1
libnm-gtk-common (0.9.10.0-2) to 1.0.10-1
libnm-gtk0 (0.9.10.0-2) to 1.0.10-1
libvte-2.91-0 (0.40.2-2) to 0.42.1-2+b1
libvte-2.91-common (0.40.2-2) to 0.42.1-2
libwebkitgtk-3.0-0 (2.4.7-1) to 2.4.9-3
libwebkitgtk-3.0-common (2.4.7-1) to 2.4.9-3
libxrandr-dev (2:1.4.2-1+b1) to 2:1.5.0-1
libxrandr2 (2:1.4.2-1+b1) to 2:1.5.0-1
libxrandr2:i386 (2:1.4.2-1+b1) to 2:1.5.0-1
python-keybinder (0.3.0-3) to 0.3.1-1
xarchiver (1:0.5.2+20130119+dfsg-3) to 1:0.5.4-2

Installed the following packages:
libgdome2-cpp-smart0v5 (0.2.6-6.2+b1)


I think, that the problem  was in gtk-3.0 libraries.

Bug#808821: asymptote: failing to build on mips

[Norbert Preining]

> Now imported, and building right now. Let us hope that MIPS this
> time works out ;-)

Ok, after adding dh_autoreconf (and dh ... --with autoreconf) to get
a proper configure script, building here in a clean chroot 
succeeded.

Unfortunately with warnings that I graciously ignore:

cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ markers1.asy
failed to create directory /nonexistent/.asy.

Before uploading I am now building the current package on MIPS
(minkus) to see if it really works out.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#813664: New Upstream Version 2.0.3

[Michael D]

Package: anope
Version: 2.0.2-2

New upstream is available for packaging:
https://github.com/anope/anope/releases/tag/2.0.3

Cheers,
Michael

Bug#760029: systemd: doesn't initialise RANDOM_SEED upon installation

[Raphael Geissert]

Hi Michael,

On Feb 4, 2016 3:11 AM, "Michael Biebl"  wrote:
>
> Am 20.06.2015 um 16:43 schrieb Felipe Sateler:
> > Control: tags -1 moreinfo
> >
> > On Sat, 30 Aug 2014 20:56:15 -0700 Raphael Geissert 
wrote:
> >> Source: systemd
> >> Source-Version: 208-8
> >> Tags: security
> >>
> >> Hi,
> >>
> >> At some point between squeeze and wheezy initscript started
initialising the
> >> RANDOM_SEED file in its postinst by basically doing the equivalent of a
> >> "service urandom start". This feature doesn't actually seem to have
been
> >> integrated into the systemd package - which I personally consider it
to be a
> >> regression.
> >>
> >> Could you please then initialise RANDOM_SEED at the package
installation
> >> time?
> >
> > I'm not sure when do you want to run this. Is this for first-time
> > installation of systemd only?
> >
> > When systemd is already installed and running,
> > systemd-random-seed.service should take care of writing the seed file
> > on shutdown.
> >
> > Or do you mean that for some reason, systemd upgrades are a good time
> > to force a seed write?
>
> Raphael, seems you haven't answered Felipe's questions yet.
> Can you elaborate exactly what you have in mind here and why.

Oh, it must have fallen through the cracks.
Anyway, the problem at hand is the lack of entropy during first boot. Think
about a raspberry pi for an example.

By initialising the seed file during the installation of the package,
systemd would be helping the first boot with pseudo random data based on
the entropy of the system running the installer - be it debootstrap or
debian-installer, or any other.

HTH.

Cheers,

Bug#813663: horae: memory leak in Athena when trying to rebin

[Nathaniel Morck Beaver]

Package: horae
Version: 071~svn537-2
Severity: normal
Tags: patch

Hi Carlo,

I've attached a patch for the rebinning memory leak problem in Athena.

For some reason, the $ee variable only gets incremented twice, and so it never 
finishes the while loop. It is beyond my Perl knowledge to ascertain why, but 
the workaround in the patch is only two lines.

Cheers,

Nathaniel

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

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

Versions of packages horae depends on:
ii  ifeffit 2:1.2.11d-10+b1
ii  libarchive-zip-perl 1.56-2
ii  libchemistry-elements-perl  1.07-2
ii  libchemistry-formula-perl   3.0.1-1.2
ii  libconfig-inifiles-perl 2.88-1
ii  libifeffit-perl 2:1.2.11d-10+b1
ii  libmath-combinatorics-perl  0.09-4
ii  libmath-derivative-perl 0.04-2
ii  libmath-round-perl  0.07-1
ii  libmath-spline-perl 0.02-1
ii  libparse-recdescent-perl1.967013+dfsg-1
pn  libpod-escapes-perl 
ii  libspreadsheet-writeexcel-perl  2.40-1
ii  libstatistics-descriptive-perl  3.0612-1
ii  libtext-glob-perl   0.09-2
ii  libtie-ixhash-perl  1.23-2
ii  libtime-stopwatch-perl  1.00-5
ii  libtk-filedialog-perl   1.3-4
ii  libtk-gbarr-perl2.08-2
ii  libtk-histentry-perl0.43-3
ii  libtk-pod-perl  0.9942-1
ii  libtk-splashscreen-perl 1.0-4
ii  libwwwbrowser-perl  2.23-2
ii  libxml-simple-perl  2.22-1
ii  libxray-absorption-perl 3.0.1-3
ii  libxray-scattering-perl 3.0.1-2
ii  perl5.22.1-4
ii  perl-modules-5.22 [libpod-simple-perl]  5.22.1-4
ii  perl-tk 1:804.033-1+b1
ii  perlindex   1.606-1

Versions of packages horae recommends:
ii  horae-doc  072-1

Versions of packages horae suggests:
pn  libstar-parser-perl  

-- no debconf information
--- /usr/bin/athena	2015-01-10 15:00:16.0 -0600
+++ athena	2016-02-04 00:14:54.677112530 -0600
@@ -7086,9 +7086,10 @@
 $ee += $rebin{pre};
   };
   $ee = $rebin{emin}+$e0;
+  my $xanes_step = $rebin{xanes};
   while ($ee < $rebin{emax}+$e0) {
 push @bingrid, $ee;
-$ee += $rebin{xanes};
+$ee += $xanes_step;
   };
   $ee = $rebin{emax}+$e0;
   my $kk = $groups{$group}->e2k($rebin{emax});

Bug#811154: poretools_0.5.1-1_amd64.changes REJECTED

[Afif Elghraoui]

Hello,

على الأربعاء  3 شباط 2016 ‫10:00، كتب Thorsten Alteholz:
> 
> as the authors do not mention the GPL version, it should be GPL-1+.
> 

This is now fixed in git. Could someone upload the corrected package?

git+ssh://git.debian.org/git/debian-med/poretools.git

Many thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#813662: cdimage.debian.org: weekly builds of live images are stale

[Olaf Meeuwissen]

Package: cdimage.debian.org
Severity: normal

Dear Maintainer,

I was looking for a live DVD of testing (stretch) and stumbled upon

  http://cdimage.debian.org/cdimage/weekly-live-builds/

Its parent directory claims that it contains "Regular builds of testing
/ (what will be Stretch)".  Great!  Just what I was looking for.

Or so I thought.  The time stamps for the images are three and a half
month old (as of writing) and the images have an 8.2.1 version number.
Slightly alarmed, I checked the packages file for one of the images.
Turns out that these images really are Debian 8.2 (aka Jessie).

Bummer for me, but please either update the live images for stretch
weekly as documented or just remove them completely.  There are live
images for the latest stable Debian release and those are at 8.3
already.

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

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

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- EPSON AVASYS CORPORATION
   Free Software Foundation Associate Member since 2004-01-27
Support Free Software  https://my.fsf.org/donate
Join the Free Software Foundationhttps://my.fsf.org/join

Bug#808821: asymptote: failing to build on mips

[Norbert Preining]

> I just checked, not released by now, but as soon as it is I will update
> the Debian repository.

Now imported, and building right now. Let us hope that MIPS this
time works out ;-)

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#813627: mate-terminal.wrapper doesn't run commands with parameters with -e opti, on

[Stefano Salvi]

Il 03/02/2016 21:16, John Paul Adrian Glaubitz ha scritto:

In the system only Mate dektop is installed.
>Geany invokes x-terminal-emulator -e "/bin/sh ./geany_run_script.sh"
>x-terminal-emulator is linked to mate-terminal.wrapper
>Mate-terminal.wrapper translates "-e" parameter in the unknown parameter
>"-x".

You are reporting a bug against a very old version of mate-terminal. The
wrapper script has been re-written for newer versions of mate-terminal,
you may want to update to a newer version of mate-terminal (and
therefore MATE) first before reporting a bug here. We're not going to
fix bugs in older versions.

I found this bug in a FRESH Jessie install, so this is the DISTRIBUTED 
version. This could be a problem...


It would be better if you put the new wrapper version in stable.

Thank you

Bug#813660: reportbug: very unobvious that a report was NOT sent

[Adam Borowski]

Package: reportbug
Version: 6.6.6
Severity: normal


Today I filed a bug report, running reportbug from a recently installed
chroot.  The reporting process looked like always, the last messages being:

=
File /tmp/reportbug-libcrypto++-20160204-30442-_ABUoJ saved
Report will be sent to "Debian Bug Tracking System" 
Submit this report on libcrypto++ (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? a
Choose a file to attach: debian/patches/x32.patch
Report will be sent to "Debian Bug Tracking System" 
Attachments:
 debian/patches/x32.patch
Submit this report on libcrypto++ (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? 
Saving a backup of the report at 
/tmp/reportbug-libcrypto++-backup-20160204-30442-0H7d7t
Bug report written as /var/tmp/libcrypto++.bug

If you want to provide additional information, please wait to receive the bug 
tracking number via email;
you may then send any extra information to n...@bugs.debian.org (e.g. 
999...@bugs.debian.org), where n is
the bug number. Normally you will receive an acknowledgement via email 
including the bug report number
within an hour; if you haven't received a confirmation, then the bug reporting 
process failed at some
point (reportbug or MTA failure, BTS maintenance, etc.).
=

The message clearly says I'll get the confirmation soon, etc.  Except for
one small detail... reportbug did nothing.  The direct reason being that
there was no MTA in the chroot (nothing depends on it).  I was presented
with no error message.

Thus, in such a case please add a message that the bug was NOT sent.
The paragraph about additional information, in particular, needs to be
suppressed, as what is says is untrue.



-- Package-specific info:
** Environment settings:
EDITOR="jstar"
EMAIL="kilob...@angband.pl"
INTERFACE="text"

** /home/kilobyte/.reportbugrc:
reportbug_version "3.17"
mode advanced
ui text

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

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

Versions of packages reportbug depends on:
ii  apt   1.2.1
ii  python-reportbug  6.6.6
pn  python:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs23-bin-common | emacs24-bin-common
ii  exim4  4.86-7
ii  exim4-daemon-light [mail-transport-agent]  4.86-7+b2
ii  file   1:5.25-2
ii  gnupg  1.4.20-1
ii  python-gtk22.24.0-4
pn  python-gtkspellcheck   
pn  python-urwid   
pn  python-vte 
ii  xdg-utils  1.1.1-1

Versions of packages python-reportbug depends on:
ii  apt   1.2.1
ii  file  1:5.25-2
ii  python-debian 0.1.27
ii  python-debianbts  2.6.0
pn  python:any

python-reportbug suggests no packages.

-- no debconf information

Bug#813659: libcrypto++: FTBFS on x32

[Adam Borowski]

Source: libcrypto++
Version: 5.6.1-9
Severity: normal
Tags: patch

Hi!

libcrypto++ currently fails to build on x32.  This is caused by attempts to
use x86 assembly -- the package would build if it used the portable generic
code instead.

Here's a patch.  It's a hybrid between disabling assembly and making it work
-- in most places, it works without changes.  In one place, it tried to
access a 32-bit variable of type size_t as a 64-bit value, so changing the
type to word64 works.  I did disable the assembly in two places -- whirlpool
where it doesn't build (insanely macroized code makes it thoroughly
unobvious) and rijndael which did compile but segfaults in the testsuite.

The patch could be simpler by disabling assembly outright, or more complete
by fixing pieces I disabled, but it's probably ok for a first stab.



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

Kernel: Linux 4.4.0-x32 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- libcrypto++-5.6.1.orig/cpu.h
+++ libcrypto++-5.6.1/cpu.h
@@ -96,6 +96,8 @@ _mm_aesdeclast_si128 (__m128i a, __m128i
 
 NAMESPACE_BEGIN(CryptoPP)
 
+#define X32 (defined __ILP32__ && defined __x86_64__)
+
 #if CRYPTOPP_BOOL_X86 || CRYPTOPP_BOOL_X64
 
 #define CRYPTOPP_CPUID_AVAILABLE
--- libcrypto++-5.6.1.orig/rijndael.cpp
+++ libcrypto++-5.6.1/rijndael.cpp
@@ -348,7 +348,7 @@ void Rijndael::Base::UncheckedSetKey(con
 
 void Rijndael::Enc::ProcessAndXorBlock(const byte *inBlock, const byte *xorBlock, byte *outBlock) const
 {
-#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE || defined(CRYPTOPP_X64_MASM_AVAILABLE) || CRYPTOPP_BOOL_AESNI_INTRINSICS_AVAILABLE
+#if (CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE || defined(CRYPTOPP_X64_MASM_AVAILABLE) || CRYPTOPP_BOOL_AESNI_INTRINSICS_AVAILABLE) && !X32
 	if (HasSSE2())
 	{
 		Rijndael::Enc::AdvancedProcessBlocks(inBlock, xorBlock, outBlock, 16, 0);
@@ -1179,7 +1179,7 @@ size_t Rijndael::Enc::AdvancedProcessBlo
 		return AESNI_AdvancedProcessBlocks(AESNI_Enc_Block, AESNI_Enc_4_Blocks, (const __m128i *)m_key.begin(), m_rounds, inBlocks, xorBlocks, outBlocks, length, flags);
 #endif
 	
-#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE || defined(CRYPTOPP_X64_MASM_AVAILABLE)
+#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE && !X32 || defined(CRYPTOPP_X64_MASM_AVAILABLE)
 	if (HasSSE2())
 	{
 		if (length < BLOCKSIZE)
--- libcrypto++-5.6.1.orig/vmac.cpp
+++ libcrypto++-5.6.1/vmac.cpp
@@ -735,7 +735,7 @@ size_t VMAC_Base::HashMultipleBlocks(con
 	return remaining;
 }
 
-static word64 L3Hash(const word64 *input, const word64 *l3Key, size_t len)
+static word64 L3Hash(const word64 *input, const word64 *l3Key, word64 len)
 {
 word64 rh, rl, t, z=0;
 	word64 p1 = input[0], p2 = input[1];
--- libcrypto++-5.6.1.orig/whrlpool.cpp
+++ libcrypto++-5.6.1/whrlpool.cpp
@@ -391,7 +391,7 @@ static const word64 Whirlpool_C[4*256+R]
 // Whirlpool basic transformation. Transforms state based on block.
 void Whirlpool::Transform(word64 *digest, const word64 *block)
 {
-#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE
+#if CRYPTOPP_BOOL_SSE2_ASM_AVAILABLE && !X32
 	if (HasISSE())
 	{
 		// MMX version has the same structure as C version below

Bug#743227: Reproduced today on Debian 7.9

[Mike Hommey]

On Wed, Feb 03, 2016 at 11:23:21AM +0100, Stéphane Gourichon wrote:
> Reproduced today on Debian 7.9 Amd64, git 1:1.9.1-1~bpo70+2,
> which means that the repository was not fixed in between.

Why would it have been "fixed", when that means changing the tree sha1,
and the commit sha1 of the first commit containing this tree, and all
the child commits?

> LC_ALL=C git -c transfer.fsckobjects=true clone
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware
> 
> Cloning into 'linux-firmware'...
> remote: Counting objects: 3966, done.
> remote: Total 3966 (delta 0), reused 0 (delta 0)
> error: object 087fbb748f50af6eac2248a445d25d666cc92c78:contains zero-padded
> file modes
> fatal: Error in object
> fatal: index-pack failed

Note that what this error means is that that tree contains modes like
04 instead of 4. In practice, it doesn't matter, and the tree
was likely generated with some tool using a dulwich version that left
zero-padding on modes or something like that. Git itself, afaict from
a quick glance at the history of cache-tree.c never created such objects
(it's always used %o for the mode) ; and in fact, it looks like it can't
be dulwich either, which always used %04o (which doesn't pad for 4).
So it must be some other tool.

Mike

Bug#803542: trnascan-se_1.3.1+dfsg-1_amd64.changes REJECTED

[Afif Elghraoui]

Hi, Thorsten,

على الثلاثاء  2 شباط 2016 ‫04:00، كتب Thorsten Alteholz:
> 
> there seems to be something wrong with this package.
> A DFSG package should not be in non-free.
> 

This is the package that you rejected last November because of the
non-free file dbmalloc.h [1]. The package has the +dfsg suffix because I
excluded the postscript Manual.ps which cannot be built from source.
It's my understanding that even non-free packages should meet the dfsg
as far as possible.

Would you prefer I put the Manual.ps back in so that there is no
repacked tarball? Otherwise, do you have a more appropriate alternative
to +dfsg for the repack suffix?

Thanks and regards
Afif


1.
https://lists.alioth.debian.org/pipermail/debian-med-packaging/2015-November/036574.html

--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#813297: gdm3: gdm is crashing and does not auto-start on system boot

[Rigved Rakshit]

Hello,

On Sun, 31 Jan 2016 at 19:13 Michael Biebl wrote:

> Do you have xserver-xorg-legacy installed?
> Please attach /var/log/Xorg.0.log from a failed start attempt.
>

No, that package was not installed as a dependency of the "gnome" package.
I have installed it now and everything is working fine. If you still need
the xorg logs, let me know.

Also, should I file a separate bug report for the xserver-xorg-legacy
dependency which was not installed?
-- 

Best Regards,
Rigved

Bug#813157: git: please default fsckobjects to true in transfer, fetch, and receive

[Mike Hommey]

On Fri, Jan 29, 2016 at 06:40:57PM -0500, Daniel Kahn Gillmor wrote:
> Package: git
> Tags: security
> 
> Currently by default, git does not verify the integrity of objects it
> requests by digest over the network.
> 
> This suggests that momentary control over a malicious repository or (for
> unencrypted transports) momentary control over the network is sufficient
> to produce a modified working copy with at worst a non-fatal warning.
> 
> I think these failures can be avoided by setting the following config
> options to "true" by default:
> 
>  transfer.fsckobjects
>  fetch.fsckobjects
>  receive.fsckobjects
> 
> Many users of git rely on commit IDs for integrity proof that they're
> working from the same point in the repository held by other developers
> (i've certainly told people that they can do this) without knowing that
> one pull from a malicious repo could tamper with the contents of a
> freshly-received object without noticing.
> 
> git should default to safe usage, and people with an argument for unsafe
> usage should change their own defaults manually.

Git is, in fact, safe by default. See
https://news.ycombinator.com/item?id=11032094

Mike

Bug#813658: Please enable virgl support

[Martin Michlmayr]

Package: qemu
Version: 1:2.5+dfsg-5
Severity: wishlist

It would be nice to have Virgil 3d support in QEMU
(--enable-virglrenderer).

Note that this requires virglrenderer to be packages in Debian.
I submitted an RFP (#813657).

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#813657: RFP: virglrenderer -- Virgl Rendering library

[Martin Michlmayr]

Package: wnpp
Severity: wishlist

* Package name: virglrenderer
  Version : 0.2.0
  Upstream Author : Dave Airlie 
* URL : http://cgit.freedesktop.org/~airlied/virglrenderer
* License : MIT
  Programming Lang: C
  Description : Virgl Rendering library

The virgil3d rendering library is a library used by qemu to implement
3D GPU support for the virtio GPU.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#813656: photutils: FTBFS due to test suite errors

[Aaron M. Ucko]

Source: photutils
Version: 0.1-1
Severity: important
Justification: fails to build from source

Builds of photutils for most platforms (all but amd64 and x32) failed
with test suite errors, as detailed at

https://buildd.debian.org/status/logs.php?pkg=photutils&ver=0.1-1

Could you please take a look?

Thanks!

Bug#813655: kicad: Python extension missing from package

[Daniel Gröber]

Package: kicad
Version: 4.0.1+dfsg1-1
Severity: normal

Dear Maintainer,

Looking at the debian/changelog it seems like Python scripting support
is supposed to work with the latest version of kicad, however the
Python extension needed for that isn't being installed into the kicad
package at build time.

The build system spits out the appropriate files in
./debian/tmp/usr/lib/python2.7/dist-packages/ and copying the .py and
.so files there into the right place in /usr/local seems to work so
it's probably just a matter of adding those to kicad.install.

Though maybe it would be better to provide a separate python-kicad
package, I checked the Python policy and it seems while that's not
mandatory for packages providing public extensions it is encouraged.
Either way I'm thinking that maybe that also makes dh pick up the
extension automatically or something. 

Looking at the output of ldd for the _pcbnew.so it looks like it's
statically linked against the rest of pcbnew so it could be provided
as a seperate package but I'm not sure how the kiface stuff works so
maybe that's a red herring.

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

Kernel: Linux 4.3.0-1-amd64 (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)

Versions of packages kicad depends on:
ii  kicad-common4.0.1+dfsg1-1
ii  libboost-context1.58.0  1.58.0+dfsg-4.1
ii  libboost-date-time1.58.01.58.0+dfsg-4.1
ii  libboost-filesystem1.58.0   1.58.0+dfsg-4.1
ii  libboost-iostreams1.58.01.58.0+dfsg-4.1
ii  libboost-locale1.58.0   1.58.0+dfsg-4.1
ii  libboost-program-options1.58.0  1.58.0+dfsg-4.1
ii  libboost-regex1.58.01.58.0+dfsg-4.1
ii  libboost-system1.58.0   1.58.0+dfsg-4.1
ii  libboost-thread1.58.0   1.58.0+dfsg-4.1
ii  libc6   2.21-6
ii  libgcc1 1:5.3.1-6
ii  libgl1-mesa-glx [libgl1]11.1.1-2
ii  libglew1.10 1.10.0-3
ii  libglew1.13 1.13.0-2
ii  libglu1-mesa [libglu1]  9.0.0-2.1
ii  libgomp15.3.1-6
ii  libstdc++6  5.3.1-6
ii  libwxbase3.0-0v53.0.2+dfsg-1.2
ii  libwxgtk3.0-0v5 3.0.2+dfsg-1.2

kicad recommends no packages.

Versions of packages kicad suggests:
ii  extra-xdg-menus  1.0-4
ii  kicad-doc-en 4.0.0~rc1a-3

-- no debconf information

Bug#760029: systemd: doesn't initialise RANDOM_SEED upon installation

[Michael Biebl]

Am 20.06.2015 um 16:43 schrieb Felipe Sateler:
> Control: tags -1 moreinfo
> 
> On Sat, 30 Aug 2014 20:56:15 -0700 Raphael Geissert  
> wrote:
>> Source: systemd
>> Source-Version: 208-8
>> Tags: security
>>
>> Hi,
>>
>> At some point between squeeze and wheezy initscript started initialising the
>> RANDOM_SEED file in its postinst by basically doing the equivalent of a
>> "service urandom start". This feature doesn't actually seem to have been
>> integrated into the systemd package - which I personally consider it to be a
>> regression.
>>
>> Could you please then initialise RANDOM_SEED at the package installation
>> time?
> 
> I'm not sure when do you want to run this. Is this for first-time
> installation of systemd only?
> 
> When systemd is already installed and running,
> systemd-random-seed.service should take care of writing the seed file
> on shutdown.
> 
> Or do you mean that for some reason, systemd upgrades are a good time
> to force a seed write?

Raphael, seems you haven't answered Felipe's questions yet.
Can you elaborate exactly what you have in mind here and why.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#813599: systemd - systemd-random-seed.service fails to start in clean install

[Michael Biebl]

Control: tags -1 + unreproducible

Am 03.02.2016 um 17:40 schrieb Michael Biebl:
> Am 03.02.2016 um 16:00 schrieb Bastian Blank:
>> systemd-random-seed.service fails to start after a clean install.  It
>> tries to read /var/lib/systemd/random-seed, which is not generated
>> during installation.

..

>> | Feb 03 14:53:49 localhost systemd[1]: Starting Load/Save Random Seed...
>> | Feb 03 14:53:49 localhost systemd-random-seed[258]: Failed to open 
>> /var/lib/systemd/random-seed: No such file or directory

..

>  systemd-random-seed.service is not started as part of the installation
> process. So I assume this happened after the first boot only and goes
> away after a second reboot?

I looked into this a bit. The systemd-random-seed code will generate a
/var/lib/systemd/random-seed file if not existent [1].
This works fine here. If I delete /var/lib/systemd/random-seed and run
systemctl start systemd-random-seed.service, the file is created.

For some reasons, this fails on your system. Any idea why? When exactly
did you get this error?
Can you run "strace /lib/systemd/systemd-random-seed load" and attach
the trace.

Marking as unreproducible, as I can't reproduce the issue.

Michael



[1]
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/src/random-seed/random-seed.c#n89


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#813654: ITP: golang-github-go-ini-ini -- Go package for control of INI file

[Nobuhiro Iwamatsu]

Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu 

* Package name: golang-github-go-ini-ini
  Version : 1.8.6
  Upstream Author : Unknwon 
* URL : https://github.com/go-ini/ini
* License : Apache-2.0
  Programming Lang: go
  Description : Go package for control of INI file

 Package ini provides INI file read and write functionality.
 This library privides functions following:
  - Load multiple data sources(`[]byte` or file) with overwrites.
  - Read with recursion values.
  - Read with parent-child sections.
  - Read with auto-increment key names.
  - Read with multiple-line values.
  - Read with tons of helper methods.
  - Read and convert values to Go types.
  - Read and **WRITE** comments of sections and keys.
  - Manipulate sections, keys and comments with ease.
  - Keep sections and keys in order as you parse and save.


-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#813164: alias ls='ls -N' is not a solution

[Pádraig Brady]

On 03/02/16 06:05, Adam Borowski wrote:
> Also, the proposed workaround, "alias ls='ls -N'" doesn't act reasonably.
> It disables _all_ quoting, including nasty unprintable characters.  When the
> output goes to the terminal, it is meant to be read by a human.  Humans can
> read spaces and apostrophes just fine, they can't read \1 or broken UTF-8.

`ls -N` does revert to the previous behaviour.
I.E. weird chars are replaced with ?

Bug#813653: jessie-pu: package symfony/2.3.21+dfsg-4+deb8u3

[David Prévot]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hi,

As agreed with the security team, we’d like to fix CVE-2016-1902 via
p-u. The patch is “a bit” bigger than usual (homemade implementation
replaced by a proper embedded one), sorry about that. Thanks in advance
for considering it.

symfony (2.3.21+dfsg-4+deb8u3) jessie; urgency=medium

  [ Daniel Beyer ]
  * Backport a security fix from 2.3.37
- SecureRandom's fallback not secure when OpenSSL fails [CVE-2016-1902]

  [ David Prévot ]
  * Add copyright entry for embeded paragonie/random_compat

Please note that the only component touch by this fix
(php-symfony-security) has no (external) reverse dependencies in Jessie.

Regards

David
diff --git a/debian/changelog b/debian/changelog
index f5a2743..5092e50 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+symfony (2.3.21+dfsg-4+deb8u3) jessie; urgency=medium
+
+  [ Daniel Beyer ]
+  * Backport a security fix from 2.3.37
+- SecureRandom's fallback not secure when OpenSSL fails [CVE-2016-1902]
+
+  [ David Prévot ]
+  * Add copyright entry for embeded paragonie/random_compat
+
+ -- David Prévot   Wed, 03 Feb 2016 19:44:47 -0400
+
 symfony (2.3.21+dfsg-4+deb8u2) jessie-security; urgency=high
 
   * Backport security fixes from 2.3.35
diff --git a/debian/copyright b/debian/copyright
index 1bc9817..e71be14 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -6,6 +6,7 @@ Files-Excluded: src/Symfony/Component/Console/Resources/bin/hiddeninput.exe
 
 Files: *
 Copyright: 2004-2014 Fabien Potencier
+   2015 Paragon Initiative Enterprises
 License: Expat
 
 Files: debian/licensing/bin/*
diff --git a/debian/patches/0012-Fix-possibly-weak-random-number-generator.patch b/debian/patches/0012-Fix-possibly-weak-random-number-generator.patch
new file mode 100644
index 000..6943d76
--- /dev/null
+++ b/debian/patches/0012-Fix-possibly-weak-random-number-generator.patch
@@ -0,0 +1,1379 @@
+From: Daniel Beyer 
+Date: Thu, 14 Jan 2016 18:11:12 +0100
+Subject: Fix possibly weak random number generator
+
+Bug: https://github.com/symfony/symfony/issues/17359
+Origin: https://github.com/symfony/symfony/commit/fcd3160a0f77931b1b2fd066bbb0bb0907d80fee
+
+This embeds paragonie/random_compat into the security component, since
+upstream's patch requires it.
+
+paragonie/random_compat is licensed under the MIT License (MIT) and
+copyright (c) 2015 Paragon Initiative Enterprises
+---
+ .../Component/Security/Core/Util/SecureRandom.php  |  86 +-
+ .../vendor/paragonie/random_compat/LICENSE |  22 +++
+ .../random_compat/lib/byte_safe_strings.php| 160 ++
+ .../paragonie/random_compat/lib/cast_to_int.php|  64 +++
+ .../paragonie/random_compat/lib/error_polyfill.php |  42 +
+ .../vendor/paragonie/random_compat/lib/random.php  | 149 +
+ .../random_compat/lib/random_bytes_com_dotnet.php  |  77 +
+ .../random_compat/lib/random_bytes_dev_urandom.php | 142 
+ .../random_compat/lib/random_bytes_libsodium.php   |  84 ++
+ .../lib/random_bytes_libsodium_legacy.php  |  84 ++
+ .../random_compat/lib/random_bytes_mcrypt.php  |  72 
+ .../random_compat/lib/random_bytes_openssl.php |  76 +
+ .../paragonie/random_compat/lib/random_int.php | 185 +
+ 13 files changed, 1159 insertions(+), 84 deletions(-)
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/LICENSE
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/byte_safe_strings.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/cast_to_int.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/error_polyfill.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/random.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/random_bytes_com_dotnet.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/random_bytes_dev_urandom.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/random_bytes_libsodium.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/random_bytes_libsodium_legacy.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/random_bytes_mcrypt.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/random_bytes_openssl.php
+ create mode 100644 src/Symfony/Component/Security/vendor/paragonie/random_compat/lib/random_int.php
+
+diff --git a/src/Symfony/Component/Security/Core/Util/SecureRandom.php b/src/Symfony/Component/Security/Core/Util/SecureRandom.php
+index 841b9af..baaae82 100644
+--- a/src/Symfony/Component/Security/Core/Util/Se

Bug#813652: ITP: golang-github-tarm-serial -- Go package for serial port communucation

[Nobuhiro Iwamatsu]

Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu 

* Package name: golang-github-tarm-serial
  Version : 0.0+git20151113
  Upstream Author : tarm 
* URL : https://github.com/tarm/serial
* License : BSD-3-clause
  Programming Lang: go
  Description : Go package for serial port communucation
 
  Go package to allow user to read and write from the
  serial port as a stream of bytes.

Bug#812444: Info received (aptitude: REQUEST: operator to version order test in "aptitude search" query syntax.)

[Oleksandr Gavenko]

I make script that scans for Kali packages that have version newer that in
Debian:

  import apt_pkg

  def main():
  apt_pkg.init()
  cache = apt_pkg.Cache()
  for pkg in cache.packages:
  vkali = []
  vdeb = []
  for ver in pkg.version_list:
  for fl, _ in ver.file_list:
  if fl.origin == 'Kali':
  vkali.append(ver.ver_str)
  elif fl.origin == 'Debian':
  vdeb.append(ver.ver_str)
  if len(vdeb) == 0:
  continue
  diff = set(vkali) - set(vdeb)
  if len(diff) == 0:
  continue
  ver0 = vkali[0]
  if all(apt_pkg.version_compare(x, ver0) < 0 for x in vdeb):
  print pkg.name, vkali, vdeb

  if __name__ == '__main__':
  main()

-- 
http://defun.work/

Bug#138409: [Reproducible-builds] Bug#138409: dpkg-dev: please add support for .buildinfo files

[Guillem Jover]

Hi!

On Tue, 2016-02-02 at 16:34:40 +0100, Jérémy Bobbio wrote:
> We were discussions the restrictions on buildinfo identifiers:
> 
> fweb_1.62-12+b2_brahms-20120530T114812Z.buildinfo
> ^^^
>   this part
> 
> The proposal was “the string should consist only of alphanumeric
> characters and hyphens”. Guillem made the following comment while
> reviewing the patches for dpkg:
> 
> Guillem Jover:
> > Can we just simply use the package name rules instead? It also avoids
> > potential problems with case and similar. (There's a
> > pkg_name_is_illegal function in Dpkg::Package already.)
> 
> After reaching out to Ansgar with a patch for dak to implement the
> above, he replied:
> 
> Ansgar Burchardt:
> > The allowed sets for package names and the suffix of buildinfo
> > filenames won't be the same even with that change.  However currently
> > the suffix of buildinfo filenames matches what is allowed for .changes
> > files.

Ah ok matching what is allowed in «.changes» with what is allowed in
«.buildinfo» makes sense. But…

> > I'm not sure why allowing capital letters used in the suffix of
> > buildinfo files should be an issue? After all we allow capital letters
> > for both version numbers (part of the filename) and in names of changes
> > files.

…are uppercase letters allowed for the third (arch) component in
.changes files? No architecture should be uppercase anyway.

I'd just like to avoid allowing things that then becomes very
difficult to ban after the fact.

> > (In the other direction not everything allowed as a package name can be
> > used as the suffix of .changes and .buildinfo files either.)

True, which would introduce more undesired things.

> Guillem, any further comments? Do you have any strong opposition to the
> initial proposal?

Actually after consideration, I don't think I have, more so if it
makes representing dates in an incorrect way (the ‘Z’).

Thanks,
Guillem

Bug#808775: CKeditor: outstanding issues and maintenance; build system

[Dmitry Smirnov]

On Wed, 3 Feb 2016 09:55:55 PM roucaries bastien wrote:
> How do you achieve to clean ckbuilder from source is missing and
> license problem ?

Through meticulous review and exclusion by Files-Excluded...
I've also added lintian-overrides for false positives.

> 
> Last time I give up...

I've seen much more difficult cases than CKeditor... ;)


> Layout is gitpkg. I have added debian directory above all. I use
> debian/version branch for upstream+patches+debian directory
> upstream/version for upstream and debian-patches/version for upstream+patch

I am not familiar with gitpkg and I found such repository layout confusing 
and difficult to contribute... :(  Do you know of any Debian team using 
gitpkg?


> > Bastien, would you be interested to help or would you rather leave
> > CKeditor maintenance with me (at least for some time)?
> 
> I cannot work on it now. I need to care about my new born baby.

Wow, congratulations. :)  Happy time and all the best.

I'll take care of next upload and add myself as Maintainer or Uploaders until 
you'll be able to work on this package again.

For now I'll work inside master branch (which is required for successful 
checkout) so later you can merge changes or drop it entirely as you wish...

Thank you.

-- 
Best wishes,
 Dmitry Smirnov.

---

There are two different types of people in the world, those who want to
know, and those who want to believe.
-- Friedrich Nietzsche


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

Bug#812149: retext: program crash

[Erik Haller]

​- Does this error happen every time you start ReText? Or only for some

*Yes. Happens everytime. No special documents.*

  special documents? (If the latter, can you attach one of them?)

- Did you configure ReText for custom language for spell checking?


*I did not configure any language setting. I enabled spell checking. ​I
​just discovered that it only crashes when spell checking is enabled.*

*​script output:*

*​Script started on Wed 03 Feb 2016 03:57:29 PM PST*
*erik@incense:~$ python3*
*Python 3.5.1+ (default, Jan 13 2016, 15:09:18) *
*[GCC 5.3.1 20160101] on linux*
*Type "help", "copyright", "credits" or "license" for more information.*
*>>> import enchant*
*>>> enchant.Dict('en_US')._Dict__describe()*
*('en_US', 'myspell', 'Myspell Provider',
'/usr/lib/i386-linux-gnu/enchant/libenchant_myspell.so')*
*>>> *
*erik@incense:~$ exit*

*Script done on Wed 03 Feb 2016 03:57:59 PM PST*


*​*
*LANG=en_US.utf8 is set in my shell.*

On Sat, Jan 30, 2016 at 2:27 AM, Dmitry Shachnev  wrote:

> Control: tags -1 +moreinfo
>
> Hi Erik,
>
> On Wed, Jan 20, 2016 at 05:32:44PM -0800, Erik wrote:
> > Ran: retext docs/api.md and received the below output:
> >
> > Traceback (most recent call last):
> >   File "/usr/share/retext/ReText/highlighter.py", line 129, in
> highlightBlock
> > if not self.dictionary.check(match.group(0)):
> >   File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 634,
> in check
> > self._check_this()
> >   File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 606,
> in _check_this
> > _EnchantObject._check_this(self,msg)
> >   File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 176,
> in _check_this
> > raise Error(msg)
> > enchant.errors.Error: Dict unusable: the underlying C-library object has
> been freed.
>
> I cannot reproduce this error.
> Can you please provide me the following details:
>
> - Does this error happen every time you start ReText? Or only for some
>   special documents? (If the latter, can you attach one of them?)
>
> - Did you configure ReText for custom language for spell checking?
>
> - Can you please run python3 console and check what is the enchant provider
>   there? For example:
>
>   >>> import enchant
>   >>> enchant.Dict('en_US')._Dict__describe()
>   ('en_US', 'aspell', 'Aspell Provider',
> '/usr/lib/x86_64-linux-gnu/enchant/libenchant_aspell.so')
>
>   ... and paste all the output here.
>   If you are using a different language, replace en_US with code of that
> language.
>
> Thanks in advance,
>
> --
> Dmitry Shachnev
>

Bug#812994: apt 1.2.1 fails to configure packages

[Guillem Jover]

Hi!

On Wed, 2016-02-03 at 09:22:51 -0500, James McCoy wrote:
> Package: apt
> Version: 1.2.1
> Followup-For: Bug #812994
> 
> I just noticed some interesting behavior related to this bug.  Looking
> back at Rohan's initial term.log, we see this:
> 
> Log started: 2016-01-28  12:13:31
> ...
> Selecting previously unselected package 
> libglobus-xio-gridftp-driver-dev:amd64.
> Preparing to unpack .../libpipeline1_1.4.1-2_amd64.deb ... 
> Unpacking libglobus-xio-gridftp-driver-dev:amd64 (2.11-1) ... 
> ...
> dpkg: error processing package libpipeline1 (--configure):
>  no package named 'libpipeline1' is installed, cannot configure
> 
> Now, the "Selecting previously unselected", "Preparing to unpack", etc.
> lines come from dpkg.  From what I can tell, those 3 lines should all
> refer to the same archive, and they do for the rest of the log.

Yeah, we also noticed this today on #debian-dpkg.

> I had a similar problem today.

> ...
> Selecting previously unselected package libn32atomic1-mips64el-cross.
> Preparing to unpack .../libjpeg62-turbo_1%3a1.4.2-2_amd64.deb ...
> Unpacking libn32atomic1-mips64el-cross (5.3.1-7cross1) ...
> ...
> dpkg: error processing package libjpeg62-turbo:amd64 (--configure):
>  package libjpeg62-turbo:amd64 is already installed and configured
> ...

The first and third lines come supposedly from the .deb control file,
the second from the filename.

If this is just a problem with wrong strings, then libjpeg62-turbo:amd64
in theory would not be already configured, just unpacked (but I might be
missing context here).

> $ dpkg-query -l libjpeg62-turbo
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ NameVersion  Architecture 
> Description
> +++-===---===
> ii  libjpeg62-turbo:amd64   1:1.4.1-2amd64
> libjpeg-turbo JPEG runtime library

> Even though there was no reason for libn32atomic1-mips64el-cross to be
> installed, apt didn't download the archive, and I don't have the .deb
> for it in /var/cache/apt/archives, dpkg thought it was unpacked instead
> of libjpeg62-turbo.

Weird.

> >From /var/log/dpkg.log:
> 
> 2016-02-03 08:53:33 startup archives unpack
> ...
> 2016-02-03 08:53:40 install libn32atomic1-mips64el-cross:all  
> 5.3.1-7cross1
> 2016-02-03 08:53:40 status half-installed libn32atomic1-mips64el-cross:all 
> 5.3.1-7cross1
> 2016-02-03 08:53:40 status unpacked libn32atomic1-mips64el-cross:all 
> 5.3.1-7cross1
> 2016-02-03 08:53:40 status unpacked libn32atomic1-mips64el-cross:all 
> 5.3.1-7cross1

Just to make sure, if you have the libjpeg62-turbo_1%3a1.4.2-2_amd64.deb
around could you check that it really contains the libjpec62-turbo
package inside with say dpkg-deb, or manually with ar+tar?

If you have the previous status file in /var/backups, and you could
try to reproduce this that would be great, otherwise, sending it here
or to me and the apt maintainers in case of privacy concerns might help
too.

> I'm not sure if this is something to do with how apt is driving dpkg or
> dpkg itself is getting confused, but hopefully this helps.

(It could well be dak being confused perhaps? But… :)

Thanks,
Guillem

Bug#806161: Implementing #741573 in policy via NMU

[Don Armstrong]

On February 3, 2016 5:38:31 PM CST, Bill Allombert  wrote:
>I understand you expected more of it but I had to release Policy
>3.9.7.0
>out of schedule to fix a RC bug #812663.
>
>Please let it propagate to testing.


My plan is to upload to delayed, so that should be no problem.
-- 
This is not a signature.

Bug#813520: ITP: cloudflare -- CloudFlare® command line tool and Go client

[Zlatan Todoric]

On Tue, 2 Feb 2016 17:13:15 +0100 Zlatan Todoric  wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Zlatan Todoric 
> 
> * Package name: cloudflare
>   Version : 0.0~git20151227.0.d872e84-1
>   Upstream Author : Łukasz Kurowski
> * URL : https://github.com/crackcomm/cloudflare
> * License : Apache-2.0
>   Programming Lang: Go
>   Description : CloudFlare® command line tool and Go client
> 
>   Simple and easy to use Golang API Client for CloudFlare® API v4.
>   It manages zones and zones records.
> 
> This package is dependency of caddy.
> 
>

Making it an actual ITP! :)

Bug#813602: monkeysign: QRCode is no longer shown on stretch (traceback on stderr)

[Antoine Beaupré]

Control: reassign 813602 1.01-5
Control: affects 813602 monkeysign
Control: forwarded 813602 https://github.com/Arachnid/pyqrencode/issues/7

This actually seems to be a bug with the qrencode package, from looking
at the traceback, reassigning (which is not to say it shouldn't be
somehow solved in monkeysign too!)

It seems the bug is also upstream:

https://github.com/Arachnid/pyqrencode/blob/master/qrencode/__init__.py#L51

So I have opened a bug report there:

https://github.com/Arachnid/pyqrencode/issues/7

It's somewhat a concern that there hasn't been a release there in
years... :/

https://github.com/Arachnid/pyqrencode/issues/5

.. but we'll see how it goes.

thanks for the bug report!

a.

On 2016-02-03 10:08:48, Elena Grandi wrote:
> Package: monkeysign
> Version: 2.0.2
> Severity: important
>
> Dear Maintainer,
>
> When running monkeyscan under a recently updated stretch system no
> QR-Code is shown on the right panel, and the following traceback is
> shown on stderr:
>
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/monkeysign/gtkui.py", line 306, in 
> expose_event
> self.draw_qrcode()
>   File "/usr/lib/python2.7/dist-packages/monkeysign/gtkui.py", line 317, in 
> draw_qrcode
> self.pixbuf = self.image_to_pixbuf(self.make_qrcode(self.active_key.fpr))
>   File "/usr/lib/python2.7/dist-packages/monkeysign/gtkui.py", line 342, in 
> make_qrcode
> version, width, image = 
> _qrencode_scaled('OPENPGP4FPR:'+fingerprint,size,0,1,2,True)
>   File "/usr/lib/python2.7/dist-packages/qrencode/__init__.py", line 69, in 
> encode_scaled
> version, src_size, im = encode(data, version, level, hint, case_sensitive)
>   File "/usr/lib/python2.7/dist-packages/qrencode/__init__.py", line 47, in 
> encode
> im = Image.fromstring('L', (size, size), data)
>   File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 2063, in 
> fromstring
> "Please call frombytes() instead.")
> Exception: fromstring() has been removed. Please call frombytes() instead.
>
> The same traceback happens when trying to save the QRCode (File -> Save QR 
> Code as...)
>
> The version of PIL I have installed is:
>
> ii  python-pil:amd 3.1.0-1  amd64Python Imaging Library (Pillow fo
>
> Thanks for your work developing and maitaing this package
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.3.0-1-amd64 (SMP w/2 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)
>
> Versions of packages monkeysign depends on:
> ii  gnupg 1.4.20-1
> ii  gnupg-agent   2.1.9-1
> ii  python2.7.11-1
> ii  python-pkg-resources  18.8-1
>
> Versions of packages monkeysign recommends:
> ii  python-gtk2   2.24.0-4
> ii  python-qrencode   1.01-5
> ii  python-zbar   0.10+doc-10+b1
> ii  python-zbarpygtk  0.10+doc-10+b1
>
> monkeysign suggests no packages.
>
> -- no debconf information

-- 
Freedom is being able to make decisions that affect mainly you. Power
is being able to make decisions that affect others more than you. If
we confuse power with freedom, we will fail to uphold real freedom.
- Richard Stallman

Bug#806161: Implementing #741573 in policy via NMU

[Bill Allombert]

On Mon, Feb 01, 2016 at 08:30:03PM -0800, Don Armstrong wrote:
> Attached, please find a diff for the NMU which I will upload to resolve
> #806161 and implement #741573 in policy in the next few days.

Hello Don,

I understand you expected more of it but I had to release Policy 3.9.7.0
out of schedule to fix a RC bug #812663.

Please let it propagate to testing.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#812444: aptitude: REQUEST: operator to version order test in "aptitude search" query syntax.

[Oleksandr Gavenko]

On 2016-02-03, Manuel A. Fernandez Montecelo wrote:

> I think that indeed the way to get this list of newer packages Kali than
> in Debian is using ?upgradable, if pinning of the repositories (man
> apt_preferences) is done correctly and if Kali's versions indeed show
> higher numbers than Debian.  Is this not working properly?
>
I know about pinning solution. Just keep text short.

This require modifying system files in order to make desired query.

Doing so in chroot environments after debootstrap also looks complicated.

> Another way to get such a list would be to produce a list of packages
> and versions of both Kali an Debian, and post-process it using "dpkg
> --compare-versions".
>
I think that "python-apt" is better way to do such task because parsing output
from:

  $ aptitude versions '...'
  $ apt-cache policy '...'
  ...

isn't pleasure. But I haven't worked with "python-apt".

> In general, I don't know if the requested operator is very useful,
> because aptitude and apt have different concept of how the system should
> work, based on apt pinning.  Packages in Debian experimental or unstable
> might have bigger version numbers than the ones in testing or stable,
> but still the ones in testing and stable used by default, because the
> user prefers to maintain most packages in the stable or testing version.
>
One important question when you work with mixed sources - what is the
difference.

With "?narrow(X,Y)" you get it.

But you don't know how they are different. List of newer/older packages gives
better picture.

But anyway I don't know easy way to display and process list of packages with
versions. "apt-cache policy" output is not in machine readable format.

"aptitude" formatting is not so rich to show several versions for single
package:

  https://www.debian.org/doc/manuals/aptitude/ch02s05s01.en.html

I was not aware about formatting issue. I don't need list of packages without
origin/version association.

I think that request should be closed. Any advanced querying should be done
with "python-apt" or other programming interfaces.

-- 
http://defun.work/

Bug#541538: pulseaudio: disable flat volumes

[Thomas van der Berg]

I've recently installed Debian Testing and have been disturbed by
flat-volumes being on by default. It's completely unintuitive when
raising my VLC volume suddenly raises the volume of other programs on my
OS! The whole reason I'm raising a program's volume is because I want it
to be louder than the rest. The "flat-volumes = yes" default just causes
mysterious audio behaviour that I've never experienced on Ubuntu,
Windows or OSX. In fact I thought my VLC was bugged until I went to
investigate the issue.

In fact, both Ubuntu and Arch[1] already explicitly disable the
"flat-volumes" setting because it causes unintuitive and problematic
behaviour. Here's just a few of the many reports people made about
problems with flat-volumes I've found: [2][3][4]. And you can find many
more just by searching "PulseAudio flat volumes" on any internet search
engine.

"flat volumes" supporters justify their decision with a Microsoft
research paper from 2004 [5], however, it seems that even Windows 7 was
no longer following the idea presented in this paper [6], and one can
say that PulseAudio's implementation(allowing each application to set
the master volume higher) doesn't even match the paper's idea(allowing
each application to set its own relative volume, and having the system
adjust each application's volume levels in the background to match the
master volume).

Supporters also claim that the flat volumes system is more intuitive or
easier for non-experts to understand, but I think just the large
volume(no pun intended) of reported issues with this easily disproves
that idea.

I hope Debian follows suit and finally turns the setting explicitly off
by default like Ubuntu and Arch have already (very sanely) done.

[1] https://wiki.archlinux.org/index.php/PulseAudio#daemon.conf

[2]
https://www.reddit.com/r/linux/comments/2rjiaa/horrible_decisions_flat_volumes_in_pulseaudio_a/
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1265267
[4] https://features.opensuse.org/310668

[5]
http://www.patrickbaudisch.com/publications/2004-Baudisch-CHI04-FlatVolumeControl.pdf
[6] http://permalink.gmane.org/gmane.comp.audio.pulseaudio.general/17426

Bug#813648: [linux-image] WARNING: at /build/linux-38KGl9/linux-3.2.73/drivers/gpu/drm/i915/intel_display.c:967 assert_pipe+0x62/0x69 [i915]()

[Mattia Rizzolo]

control: reassign -1 src:linux 3.2.73-2+deb7u2

On Wed, Feb 03, 2016 at 10:40:33PM +, Pedro Mariano wrote:
> Package: linux-image
> Version: 3.2.0-4-686-pae

these data seem to be wrong, as I can't find a package named such and a
package with such version.  I reassign to linux to the version currently
in oldstable-security.

> Severity: normal
> 
> --- Please enter the report below this line. ---
> 
> When I turn on the laptop after hibernation, I get the following message
> during boot.  Sometimes the system freezes and I have to reset the laptop.
> 
> 
> [ 3710.876233] [ cut here ]
> [ 3710.876300] WARNING: at
> /build/linux-38KGl9/linux-3.2.73/drivers/gpu/drm/i915/intel_display.c:967 
> assert_pipe+0x62/0x69
> [i915]()
> [ 3710.876303] Hardware name: Satellite U300
> [ 3710.876305] pipe A assertion failure (expected off, current on)
> [ 3710.876325] Modules linked in: snd_hrtimer parport_pc ppdev lp
> parport bnep rfcomm bluetooth crc16 binfmt_misc fuse firewire_sbp2 loop
> uvcvideo videodev media snd_hda_codec_realtek arc4 i915 snd_hda_intel
> snd_hda_codec snd_hwdep snd_pcm snd_page_alloc drm_kms_helper snd_seq
> joydev snd_seq_device iwl4965 snd_timer drm r852 sm_common iwl_legacy
> nand snd nand_ecc r592 iTCO_wdt psmouse acpi_cpufreq memstick evdev
> i2c_algo_bit mac80211 nand_ids pcspkr coretemp mtd cfg80211
> iTCO_vendor_support toshiba_acpi serio_raw mperf i2c_i801 ac battery
> power_supply sparse_keymap button processor video wmi toshiba_bluetooth
> soundcore rfkill i2c_core ext3 mbcache jbd sg usbhid sr_mod hid sd_mod
> cdrom crc_t10dif ata_generic ata_piix ahci libahci libata sdhci_pci
> sdhci firewire_ohci mmc_core thermal thermal_sys firewire_core crc_itu_t
> scsi_mod uhci_hcd ehci_hcd r8169 usbcore mii usb_common [last unloaded:
> scsi_wait_scan]
> [ 3710.876461] Pid: 17737, comm: kworker/u:7 Not tainted 3.2.0-4-686-pae
> #1 Debian 3.2.73-2+deb7u2
> [ 3710.876463] Call Trace:
> [ 3710.876488]  [] ? warn_slowpath_common+0x68/0x79
> [ 3710.876518]  [] ? assert_pipe+0x62/0x69 [i915]
> [ 3710.876522]  [] ? warn_slowpath_fmt+0x29/0x2d
> [ 3710.876552]  [] ? assert_pipe+0x62/0x69 [i915]
> [ 3710.876582]  [] ? intel_crtc_disable+0x39/0x60 [i915]
> [ 3710.876588]  [] ?
> drm_helper_disable_unused_functions+0xb0/0xd3 [drm_kms_helper]
> [ 3710.876592]  [] ? drm_helper_resume_force_mode+0xd5/0xdf
> [drm_kms_helper]
> [ 3710.876619]  [] ? i915_drm_thaw+0xb8/0xf7 [i915]
> [ 3710.876645]  [] ? i915_resume+0x35/0x47 [i915]
> [ 3710.876652]  [] ? pci_pm_restore+0x6b/0x7a
> [ 3710.876656]  [] ? pm_op+0xe4/0x108
> [ 3710.876677]  [] ? device_resume+0x78/0xc1
> [ 3710.876680]  [] ? async_resume+0x13/0x33
> [ 3710.876684]  [] ? async_run_entry_fn+0x8d/0x125
> [ 3710.876688]  [] ? process_one_work+0x12a/0x209
> [ 3710.876709]  [] ? worker_thread+0xa9/0x122
> [ 3710.876712]  [] ? manage_workers.isra.25+0x13d/0x13d
> [ 3710.876715]  [] ? kthread+0x63/0x68
> [ 3710.876718]  [] ? kthread_worker_fn+0x101/0x101
> [ 3710.876740]  [] ? kernel_thread_helper+0x6/0x10
> [ 3710.876742] ---[ end trace 2dbcb745adc19e8a ]---
> 
> 
> [ 3719.059423] [ cut here ]
> [ 3719.059479] WARNING: at
> /build/linux-38KGl9/linux-3.2.73/drivers/gpu/drm/i915/intel_display.c:967 
> assert_pipe+0x62/0x69
> [i915]()
> [ 3719.059482] Hardware name: Satellite U300
> [ 3719.059485] pipe A assertion failure (expected off, current on)
> [ 3719.059486] Modules linked in: snd_hrtimer parport_pc ppdev lp
> parport bnep rfcomm bluetooth crc16 binfmt_misc fuse firewire_sbp2 loop
> uvcvideo videodev media snd_hda_codec_realtek arc4 i915 snd_hda_intel
> snd_hda_codec snd_hwdep snd_pcm snd_page_alloc drm_kms_helper snd_seq
> joydev snd_seq_device iwl4965 snd_timer drm r852 sm_common iwl_legacy
> nand snd nand_ecc r592 iTCO_wdt psmouse acpi_cpufreq memstick evdev
> i2c_algo_bit mac80211 nand_ids pcspkr coretemp mtd cfg80211
> iTCO_vendor_support toshiba_acpi serio_raw mperf i2c_i801 ac battery
> power_supply sparse_keymap button processor video wmi toshiba_bluetooth
> soundcore rfkill i2c_core ext3 mbcache jbd sg usbhid sr_mod hid sd_mod
> cdrom crc_t10dif ata_generic ata_piix ahci libahci libata sdhci_pci
> sdhci firewire_ohci mmc_core thermal thermal_sys firewire_core crc_itu_t
> scsi_mod uhci_hcd ehci_hcd r8169 usbcore mii usb_common [last unloaded:
> scsi_wait_scan]
> [ 3719.059615] Pid: 14649, comm: Xorg Tainted: GW
> 3.2.0-4-686-pae #1 Debian 3.2.73-2+deb7u2
> [ 3719.059617] Call Trace:
> [ 3719.059642]  [] ? warn_slowpath_common+0x68/0x79
> [ 3719.059672]  [] ? assert_pipe+0x62/0x69 [i915]
> [ 3719.059676]  [] ? warn_slowpath_fmt+0x29/0x2d
> [ 3719.059705]  [] ? assert_pipe+0x62/0x69 [i915]
> [ 3719.059735]  [] ? intel_crtc_disable+0x39/0x60 [i915]
> [ 3719.059740]  [] ?
> drm_helper_disable_unused_functions+0xb0/0xd3 [drm_kms_helper]
> [ 3719.059744]  [] ? drm_crtc_helper_set_config+0x137/0x7e3
> [drm_kms_helper]
> [ 3719.059767]  [] ? hrtimer_forward+0x135/0x14d
> [ 3719.059772]  [] ? shou

Bug#782143: pu: package stunnel4/3:5.06-2+deb8u1

[Ana Guerrero Lopez]

On Sun, Apr 26, 2015 at 01:45:11AM +0300, Peter Pentchev wrote:
> Control: retitle -1 pu: package stunnel4/3:5.06-2+deb8u1
> 
> On Thu, Apr 23, 2015 at 10:35:28PM +0100, Jonathan Wiltshire wrote:
> > Control: retitle -1 pu: package stunnel4/3:5.06-3
> > Control: tag -1 jessie
> > 
> > On Wed, Apr 08, 2015 at 02:32:49PM +0300, Peter Pentchev wrote:
> > > This is a pre-approval request for unblocking a RC bugfix upload of
> > > stunnel4 that will fix two RC bugs:
> > > - #771421 - makes stunnel unusable for some users in certain
> > >   configurations; not for everyone, but still, it happens too often to
> > >   be ignored
> > > - #782030 - makes stunnel start and stop properly, checking whether
> > >   the action has actually succeeded
> > 
> > Deferring to a point release; SRM will confirm after release.
> 
> OK, here's an updated debdiff that retargets the upload towards
> stable-proposed-updates; the only change is the header and the footer
> of the changelog entry itself.
> 

Ping!
Are you still interested in this update? It only needs to be rebased
on top of 3:5.06-2+deb8u1.

Ana

Bug#813614: upstream request?

[Stéphane Blondon]

I would have sent this wish to the upstream maintainer but I don't know
if upstream still exists.
If it's the case, I can contact him/her directly if you prefer.


-- 
Stéphane



signature.asc
Description: OpenPGP digital signature

Bug#813649: emoslib; FTBFS on sparc64, needs different -mcmodel option

[John Paul Adrian Glaubitz]

On 02/03/2016 11:59 PM, Patrick Baggett wrote:
> On Wed, Feb 3, 2016 at 4:55 PM, John Paul Adrian Glaubitz
>  wrote:
>> On 02/03/2016 11:48 PM, John Paul Adrian Glaubitz wrote:
>>> cd /«PKGBUILDDIR»/obj-sparc64-linux-gnu/libemos-dp && /usr/bin/cc  
>>> -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 
>>> -DINTEGER_IS_INT -DINTERPOL_TABLES_PATH=\"/usr/share/emos\" -DLITTLE_ENDIAN 
>>> -DPOINTER_64 -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -D_FILE_OFFSET_BITS=64 
>>> -D_LARGEFILE64_SOURCE -Dgfortran -Dlinux -I/«PKGBUILDDIR» 
>>> -I/«PKGBUILDDIR»/obj-sparc64-linux-gnu -I/«PKGBUILDDIR»/interpolation 
>>> -I/«PKGBUILDDIR»/bufrdc_wmo -I/usr/lib/include  -g -O2 
>>> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
>>> -D_FORTIFY_SOURCE=2  -pipe -O3 -DNDEBUG -fPIC   -fpic-o 
>>> CMakeFiles/emos.dir/__/pbio/readany.c.o   -c /«PKGBUILDDIR»/pbio/readany.c
> 
> Somewhat off-topic: It's weird that -DLITTLE_ENDIAN is defined for
> this build... that seems like it could cause problems.

True, this should probably be -DBIG_ENDIAN :).

-- 
 .''`.  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#807969: jessie-pu: package clamav/0.99+dfsg-0+deb8u1

[Adam D. Barratt]

On Wed, 2016-02-03 at 23:55 +0100, Sebastian Andrzej Siewior wrote:
> On 2016-02-02 20:31:23 [+], Adam D. Barratt wrote:
[...]
> > > havp seems to work (installed old, dpkg -i new package, loaded a page
> > > and the eicar test signature which got blocked as expected). dansguardian
> > > (just installed the new package, used behind havp) seems to serve content,
> > > too.
> > > I did no test the other packages (but this can change on your request).
> > 
> > Any testing we could get before looking at releasing the packages to the
> > masses via -updates would be appreciated.
> 
> Okay. Uploaded the current package which hits first s-p-u. I hope to be
> able to test the remaining two packages this weekend.

Thanks. It should end up in NEW, as libclamav7 doesn't exist in stable.
Once it does, we can ask the ftp-team to have a look.

> Regading the binNMU: please note that (almost) all packages have the
> same source version in stable as in unstable/testing and their binary
> version (in testing) is +b1. So maybe +0+b1 would be better to ensure an
> update path from s -> s-u and then s -> testing.

We can only schedule binNMUs as +bX, so in those cases we'll likely have
to do something like schedule +b(>=3) for unstable and, assuming those
succeed, then schedule +b2s for p-u.

Regards,

Adam

Bug#813641: multcomp: FTBFS: Error : package 'MASS' required by 'TH.data' could not be found

[Dirk Eddelbuettel]

On 3 February 2016 at 23:31, Chris Lamb wrote:
| Source: multcomp
| Version: 1.4-2-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,
| 
| multcomp fails to build from source in unstable/amd64:
| 
|   [..]
| 
|   * installing *source* package 'multcomp' ...
|   ** package 'multcomp' successfully unpacked and MD5 sums checked
|   ** R
|   ** data
|   *** moving datasets to lazyload DB
|   ** demo
|   ** inst
|   ** preparing package for lazy loading
|   Error : package 'MASS' required by 'TH.data' could not be found
|   ERROR: lazy loading failed for package 'multcomp'
|   * removing 
'/home/lamby/temp/cdt.20160203230629.amdKvAuzFF/multcomp-1.4-2/debian/r-cran-multcomp/usr/lib/R/site-library/multcomp'
|   /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
|   make: *** [R_any_arch] Error 1

Thanks. It is actually a bug in TH.data (aka r-cran-th.data) which should
pull MASS (aka r-cran-mass) in.  Rebuilding that one now; will rebuild this
one in a day or so.

Dirk
 
|   [..]
| 
| The full build log is attached.
| 
| 
| Regards,
| 
| -- 
|   ,''`.
|  : :'  : Chris Lamb
|  `. `'`  la...@debian.org / chris-lamb.co.uk
|`-
| [DELETED ATTACHMENT multcomp.1.4-2-1.unstable.amd64.log.txt.gz, Untyped 
binary data]

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

Bug#813649: emoslib; FTBFS on sparc64, needs different -mcmodel option

[Patrick Baggett]

On Wed, Feb 3, 2016 at 4:55 PM, John Paul Adrian Glaubitz
 wrote:
> On 02/03/2016 11:48 PM, John Paul Adrian Glaubitz wrote:
>> cd /«PKGBUILDDIR»/obj-sparc64-linux-gnu/libemos-dp && /usr/bin/cc  
>> -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 -DINTEGER_IS_INT 
>> -DINTERPOL_TABLES_PATH=\"/usr/share/emos\" -DLITTLE_ENDIAN -DPOINTER_64 
>> -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -D_FILE_OFFSET_BITS=64 
>> -D_LARGEFILE64_SOURCE -Dgfortran -Dlinux -I/«PKGBUILDDIR» 
>> -I/«PKGBUILDDIR»/obj-sparc64-linux-gnu -I/«PKGBUILDDIR»/interpolation 
>> -I/«PKGBUILDDIR»/bufrdc_wmo -I/usr/lib/include  -g -O2 
>> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
>> -D_FORTIFY_SOURCE=2  -pipe -O3 -DNDEBUG -fPIC   -fpic-o 
>> CMakeFiles/emos.dir/__/pbio/readany.c.o   -c /«PKGBUILDDIR»/pbio/readany.c

Somewhat off-topic: It's weird that -DLITTLE_ENDIAN is defined for
this build... that seems like it could cause problems.

Bug#813649: emoslib; FTBFS on sparc64, needs different -mcmodel option

[John Paul Adrian Glaubitz]

On 02/03/2016 11:48 PM, John Paul Adrian Glaubitz wrote:
> cd /«PKGBUILDDIR»/obj-sparc64-linux-gnu/libemos-dp && /usr/bin/cc  
> -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 -DINTEGER_IS_INT 
> -DINTERPOL_TABLES_PATH=\"/usr/share/emos\" -DLITTLE_ENDIAN -DPOINTER_64 
> -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE64_SOURCE -Dgfortran -Dlinux -I/«PKGBUILDDIR» 
> -I/«PKGBUILDDIR»/obj-sparc64-linux-gnu -I/«PKGBUILDDIR»/interpolation 
> -I/«PKGBUILDDIR»/bufrdc_wmo -I/usr/lib/include  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -pipe -O3 -DNDEBUG -fPIC   -fpic-o 
> CMakeFiles/emos.dir/__/pbio/readany.c.o   -c /«PKGBUILDDIR»/pbio/readany.c
> [ 19%] Building C object libemos-dp/CMakeFiles/emos.dir/__/pbio/readbufr.c.o

I somehow managed to miss the actual error message during copy/paste:

[ 19%] Linking C executable ../usr/bin/emos_tool
cd /«PKGBUILDDIR»/obj-sparc64-linux-gnu/sandbox && /usr/bin/cmake -E
remove /«PKGBUILDDIR»/obj-sparc64-linux-gnu/usr/bin/emos_tool
cd /«PKGBUILDDIR»/obj-sparc64-linux-gnu/sandbox && /usr/bin/cmake -E
cmake_link_script CMakeFiles/emos_tool.dir/link.txt --verbose=1
/usr/bin/cc  -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -pipe -O3
-DNDEBUG   -Wl,-z,defs -Wl,--as-needed -Wl,-z,relro
-Wl,--disable-new-dtags CMakeFiles/emos_tool.dir/emos_tool.c.o  -o
../usr/bin/emos_tool -rdynamic ../usr/lib/sparc64-linux-gnu/libemosR64.a
/usr/lib/libgrib_api_f77.so.0 /usr/lib/libgrib_api_f90.so.0
/usr/lib/libgrib_api.so.0 -lpthread -laec -lpng -lz -ljasper -ljpeg -lm
-lgfortran -lm -lm -Wl,-rpath,"\$ORIGIN/../lib"
../usr/lib/sparc64-linux-gnu/libemosR64.a(hirlam.F.o): In function
`hirlam_':
/«PKGBUILDDIR»/interpolation/hirlam.F:254:(.text+0x98): relocation
truncated to fit: R_SPARC_GOT13 against symbol `jdcflags_' defined in
COMMON section in ../usr/lib/sparc64-linux-gnu/libemosR64.a(hirlam.F.o)
(...)

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#813647: Further information.

[C. Morgan Hamill]

This thread upstream might be relevant:
http://permalink.gmane.org/gmane.comp.handhelds.openembedded.core/75201
--
Morgan Hamill

Bug#807969: jessie-pu: package clamav/0.99+dfsg-0+deb8u1

[Sebastian Andrzej Siewior]

On 2016-02-02 20:31:23 [+], Adam D. Barratt wrote:
> Okay, thanks. Let's get this rolling; apologies for the delay in getting
> back to you.

No problem. It is better that way than just rubber-stamp it.

> > havp seems to work (installed old, dpkg -i new package, loaded a page
> > and the eicar test signature which got blocked as expected). dansguardian
> > (just installed the new package, used behind havp) seems to serve content,
> > too.
> > I did no test the other packages (but this can change on your request).
> 
> Any testing we could get before looking at releasing the packages to the
> masses via -updates would be appreciated.

Okay. Uploaded the current package which hits first s-p-u. I hope to be
able to test the remaining two packages this weekend.

Regading the binNMU: please note that (almost) all packages have the
same source version in stable as in unstable/testing and their binary
version (in testing) is +b1. So maybe +0+b1 would be better to ensure an
update path from s -> s-u and then s -> testing.

> Regards,
> 
> Adam

Sebastian

Bug#479998: spamassassin: SPF doesn't work with sendmail

[Elrond]

package spamassassin
tags 479998 +moreinfo
thanks

Hi,

On Wed, May 07, 2008 at 14:48:57 +0200, Gabor wrote:
> Package: spamassassin
> Version: 3.1.7-2
> Severity: normal
[...]

I am happily running 3.4.0-* from jessie on a box with
sendmail and spf works nicely. would you mind rechecking on
a more current version?

Thanks

Bug#813651: libucommon-dev: New version available upstream: 7.0.0

[Ohm Base]

Package: libucommon-dev
Version: 6.4.4-2
Severity: wishlist

Dear Maintainer,

As per

https://www.fsf.org/blogs/community/gnu-spotlight-december-2015

a new version of GNU uCommon (7.0.0) is available.  It can be found on the GNU
project's FTP site.

ftp://ftp.gnu.org/pub/gnu/commonc++/



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

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

Versions of packages libucommon-dev depends on:
ii  libgnutls28-dev  3.4.8-3
ii  libucommon7v56.4.4-2

Versions of packages libucommon-dev recommends:
ii  pkg-config  0.29-3

Versions of packages libucommon-dev suggests:
pn  ucommon-doc  

-- no debconf information

Bug#813649: emoslib; FTBFS on sparc64, needs different -mcmodel option

[John Paul Adrian Glaubitz]

Source: emoslib
Version: 2:4.3.3-4
Severity: normal
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hi!

On sparc64, emoslib fails to build from source with:

cd /«PKGBUILDDIR»/obj-sparc64-linux-gnu/libemos-dp && /usr/bin/cc  
-DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" -DFOPEN64 -DINTEGER_IS_INT 
-DINTERPOL_TABLES_PATH=\"/usr/share/emos\" -DLITTLE_ENDIAN -DPOINTER_64 
-DREAL_8 -DREAL_BIGGER_THAN_INTEGER -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE64_SOURCE -Dgfortran -Dlinux -I/«PKGBUILDDIR» 
-I/«PKGBUILDDIR»/obj-sparc64-linux-gnu -I/«PKGBUILDDIR»/interpolation 
-I/«PKGBUILDDIR»/bufrdc_wmo -I/usr/lib/include  -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -pipe -O3 
-DNDEBUG -fPIC   -fpic-o CMakeFiles/emos.dir/__/pbio/readany.c.o   -c 
/«PKGBUILDDIR»/pbio/readany.c
[ 19%] Building C object libemos-dp/CMakeFiles/emos.dir/__/pbio/readbufr.c.o

This is basically the same issue as in #790078 [1], so building with 
-mcmodel=large
on sparc64 should be enough to fix the issue.

Thanks,
Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790078


-- 
 .''`.  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#813650: liferea: Liferea close with database error during launch

[Sami RHATAY]

Package: liferea
Version: 1.10.17-1
Severity: important
Tags: newcomer

During launch, Liferea close with the following messages :

"Unexpected status on SQL execution: 11 (database disk image is malformed)"

and

"ERROR:db.c:729:db_init: assertion failed: (sqlite3_get_autocommit (db))" .

The problem persist even after deleting all (including database) files in
~/.liferea/

There is references about this bug on other bugtrackers but seems like to be
old bugs (2010) here :

https://bugs.archlinux.org/task/21331
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/674746



-- 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.3.0-1-amd64 (SMP w/2 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 liferea depends on:
ii  dbus-x11 1.10.6-1
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gir1.2-gtk-3.0   3.18.6-1
ii  gir1.2-peas-1.0  1.16.0-1+b1
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-7
ii  libcairo21.14.6-1
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libgirepository-1.0-11.46.0-3
ii  libglib2.0-0 2.46.2-3
ii  libgtk-3-0   3.18.6-1
ii  libindicate5 0.6.92-2
ii  libjson-glib-1.0-0   1.0.4-2
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.38.1-1
ii  libpeas-1.0-01.16.0-1+b1
ii  libsoup2.4-1 2.52.2-1
ii  libsqlite3-0 3.10.2-1
ii  libwebkitgtk-3.0-0   2.4.9-3
ii  libxml2  2.9.3+dfsg1-1
ii  libxslt1.1   1.1.28-2.1
ii  liferea-data 1.10.17-1
ii  python-gi3.18.2-2
pn  python:any   

Versions of packages liferea recommends:
ii  gir1.2-gnomekeyring-1.0  3.12.0-1+b1
ii  gnome-icon-theme 3.12.0-1
ii  gnome-keyring3.18.3-1

Versions of packages liferea suggests:
pn  kget 
ii  network-manager  1.0.10-2+b1

-- no debconf information

Bug#813648: [linux-image] WARNING: at /build/linux-38KGl9/linux-3.2.73/drivers/gpu/drm/i915/intel_display.c:967 assert_pipe+0x62/0x69 [i915]()

[Pedro Mariano]

Package: linux-image
Version: 3.2.0-4-686-pae
Severity: normal

--- Please enter the report below this line. ---

When I turn on the laptop after hibernation, I get the following message
during boot.  Sometimes the system freezes and I have to reset the laptop.


[ 3710.876233] [ cut here ]
[ 3710.876300] WARNING: at
/build/linux-38KGl9/linux-3.2.73/drivers/gpu/drm/i915/intel_display.c:967 
assert_pipe+0x62/0x69
[i915]()
[ 3710.876303] Hardware name: Satellite U300
[ 3710.876305] pipe A assertion failure (expected off, current on)
[ 3710.876325] Modules linked in: snd_hrtimer parport_pc ppdev lp
parport bnep rfcomm bluetooth crc16 binfmt_misc fuse firewire_sbp2 loop
uvcvideo videodev media snd_hda_codec_realtek arc4 i915 snd_hda_intel
snd_hda_codec snd_hwdep snd_pcm snd_page_alloc drm_kms_helper snd_seq
joydev snd_seq_device iwl4965 snd_timer drm r852 sm_common iwl_legacy
nand snd nand_ecc r592 iTCO_wdt psmouse acpi_cpufreq memstick evdev
i2c_algo_bit mac80211 nand_ids pcspkr coretemp mtd cfg80211
iTCO_vendor_support toshiba_acpi serio_raw mperf i2c_i801 ac battery
power_supply sparse_keymap button processor video wmi toshiba_bluetooth
soundcore rfkill i2c_core ext3 mbcache jbd sg usbhid sr_mod hid sd_mod
cdrom crc_t10dif ata_generic ata_piix ahci libahci libata sdhci_pci
sdhci firewire_ohci mmc_core thermal thermal_sys firewire_core crc_itu_t
scsi_mod uhci_hcd ehci_hcd r8169 usbcore mii usb_common [last unloaded:
scsi_wait_scan]
[ 3710.876461] Pid: 17737, comm: kworker/u:7 Not tainted 3.2.0-4-686-pae
#1 Debian 3.2.73-2+deb7u2
[ 3710.876463] Call Trace:
[ 3710.876488]  [] ? warn_slowpath_common+0x68/0x79
[ 3710.876518]  [] ? assert_pipe+0x62/0x69 [i915]
[ 3710.876522]  [] ? warn_slowpath_fmt+0x29/0x2d
[ 3710.876552]  [] ? assert_pipe+0x62/0x69 [i915]
[ 3710.876582]  [] ? intel_crtc_disable+0x39/0x60 [i915]
[ 3710.876588]  [] ?
drm_helper_disable_unused_functions+0xb0/0xd3 [drm_kms_helper]
[ 3710.876592]  [] ? drm_helper_resume_force_mode+0xd5/0xdf
[drm_kms_helper]
[ 3710.876619]  [] ? i915_drm_thaw+0xb8/0xf7 [i915]
[ 3710.876645]  [] ? i915_resume+0x35/0x47 [i915]
[ 3710.876652]  [] ? pci_pm_restore+0x6b/0x7a
[ 3710.876656]  [] ? pm_op+0xe4/0x108
[ 3710.876677]  [] ? device_resume+0x78/0xc1
[ 3710.876680]  [] ? async_resume+0x13/0x33
[ 3710.876684]  [] ? async_run_entry_fn+0x8d/0x125
[ 3710.876688]  [] ? process_one_work+0x12a/0x209
[ 3710.876709]  [] ? worker_thread+0xa9/0x122
[ 3710.876712]  [] ? manage_workers.isra.25+0x13d/0x13d
[ 3710.876715]  [] ? kthread+0x63/0x68
[ 3710.876718]  [] ? kthread_worker_fn+0x101/0x101
[ 3710.876740]  [] ? kernel_thread_helper+0x6/0x10
[ 3710.876742] ---[ end trace 2dbcb745adc19e8a ]---


[ 3719.059423] [ cut here ]
[ 3719.059479] WARNING: at
/build/linux-38KGl9/linux-3.2.73/drivers/gpu/drm/i915/intel_display.c:967 
assert_pipe+0x62/0x69
[i915]()
[ 3719.059482] Hardware name: Satellite U300
[ 3719.059485] pipe A assertion failure (expected off, current on)
[ 3719.059486] Modules linked in: snd_hrtimer parport_pc ppdev lp
parport bnep rfcomm bluetooth crc16 binfmt_misc fuse firewire_sbp2 loop
uvcvideo videodev media snd_hda_codec_realtek arc4 i915 snd_hda_intel
snd_hda_codec snd_hwdep snd_pcm snd_page_alloc drm_kms_helper snd_seq
joydev snd_seq_device iwl4965 snd_timer drm r852 sm_common iwl_legacy
nand snd nand_ecc r592 iTCO_wdt psmouse acpi_cpufreq memstick evdev
i2c_algo_bit mac80211 nand_ids pcspkr coretemp mtd cfg80211
iTCO_vendor_support toshiba_acpi serio_raw mperf i2c_i801 ac battery
power_supply sparse_keymap button processor video wmi toshiba_bluetooth
soundcore rfkill i2c_core ext3 mbcache jbd sg usbhid sr_mod hid sd_mod
cdrom crc_t10dif ata_generic ata_piix ahci libahci libata sdhci_pci
sdhci firewire_ohci mmc_core thermal thermal_sys firewire_core crc_itu_t
scsi_mod uhci_hcd ehci_hcd r8169 usbcore mii usb_common [last unloaded:
scsi_wait_scan]
[ 3719.059615] Pid: 14649, comm: Xorg Tainted: GW
3.2.0-4-686-pae #1 Debian 3.2.73-2+deb7u2
[ 3719.059617] Call Trace:
[ 3719.059642]  [] ? warn_slowpath_common+0x68/0x79
[ 3719.059672]  [] ? assert_pipe+0x62/0x69 [i915]
[ 3719.059676]  [] ? warn_slowpath_fmt+0x29/0x2d
[ 3719.059705]  [] ? assert_pipe+0x62/0x69 [i915]
[ 3719.059735]  [] ? intel_crtc_disable+0x39/0x60 [i915]
[ 3719.059740]  [] ?
drm_helper_disable_unused_functions+0xb0/0xd3 [drm_kms_helper]
[ 3719.059744]  [] ? drm_crtc_helper_set_config+0x137/0x7e3
[drm_kms_helper]
[ 3719.059767]  [] ? hrtimer_forward+0x135/0x14d
[ 3719.059772]  [] ? should_resched+0x5/0x1e
[ 3719.059776]  [] ? drm_fb_helper_set_par+0x51/0x87
[drm_kms_helper]
[ 3719.059798]  [] ? fb_set_var+0x1dd/0x2ba
[ 3719.059805]  [] ? bit_putcs+0x2fe/0x35d
[ 3719.059808]  [] ? fbcon_blank+0x65/0x1ad
[ 3719.059830]  [] ? mod_timer+0x64/0x69
[ 3719.059834]  [] ? do_unblank_screen+0xd8/0x127
[ 3719.059838]  [] ? complete_change_console+0x4a/0xb0
[ 3719.059841]  [] ? vt_ioctl+0x11d1/0x18f0
[ 3719.059867]  [] ? drm_master_put+0xf/0x17 [drm]
[ 3719.

Bug#813647: connman: daemon no longer starts after upgrade

[C. Morgan Hamill]

Package: connman
Version: 1.21-1.2+b2
Severity: grave
Justification: renders package unusable

Connman fails to start. See the attached 'connmand.out' for the segfault
which is printed on running `connmand -n --debug`.

Thanks for your help.
--
Morgan Hamill

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

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

Versions of packages connman depends on:
ii  dbus 1.10.6-1
ii  init-system-helpers  1.24
ii  libc62.21-7
ii  libdbus-1-3  1.10.6-1
ii  libglib2.0-0 2.46.2-3
ii  libgnutls30  3.4.8-2
ii  libreadline6 6.3-8+b4
ii  libxtables11 1.6.0-2
ii  lsb-base 9.20160110

Versions of packages connman recommends:
ii  bluez  5.36-1
pn  ofono  
ii  wpasupplicant  2.3-2.3

Versions of packages connman suggests:
pn  indicator-network  

-- no debconf information
connmand[5781]: Connection Manager version 1.21
connmand[5781]: src/dbus.c:__connman_dbus_init() 
connmand[5781]: src/main.c:parse_config() parsing main.conf
connmand[5781]: src/inotify.c:__connman_inotify_init() 
connmand[5781]: src/technology.c:__connman_technology_init() 
connmand[5781]: src/storage.c:storage_load() Loading /var/lib/connman/settings
connmand[5781]: src/storage.c:storage_load() Loading /var/lib/connman/settings
connmand[5781]: src/notifier.c:__connman_notifier_init() 
connmand[5781]: src/agent.c:__connman_agent_init() 
connmand[5781]: src/service.c:__connman_service_init() 
connmand[5781]: src/agent.c:connman_agent_driver_register() Registering driver 
0x6be180 name service
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_d637d70df97b_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_546f6d4e546f6d735f58656e2077696669_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fec4bf467024_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_616e7369626c65_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_9af97dbef0dd_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_494e46494e4954554d6b677a7a_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_4c41504c2d5075626c6963_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_476f6f676c6520537461726275636b73_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fe5400fc3e5f_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_44415649442031_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_aed21fe1c27c_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_73756265746861_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_42444c7075626c6963_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_feb7764a17b1_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_537461706c6573486f7473706f74_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fe2ae7117c92_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_776972656c657373_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_56696c6c6167652043616665204775657374204e6574776f726b_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_434f4646454520484f555345_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_416d7472616b436f6e6e656374_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_61747477696669_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_da67ab1d3186_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_4c61204d6f6e617263612042616b657279_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fe0095c5787b_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_

Bug#813646: sipwitch: New version available upstream: 1.9.15

[Ohm Base]

Package: sipwitch
Version: 1.6.1-2+b2
Severity: wishlist

Dear Maintainer,

As per

https://www.fsf.org/blogs/community/gnu-spotlight-december-2015

A new version of sipwitch is available on the GNU Project's FTP site:

ftp://ftp.gnu.org/pub/gnu/sipwitch/




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

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

Versions of packages sipwitch depends on:
ii  adduser   3.113+nmu3
ii  libavahi-client3  0.6.32~rc+dfsg-1
ii  libavahi-common3  0.6.32~rc+dfsg-1
ii  libc6 2.21-7
ii  libexosip2-11 4.1.0-2+b1
ii  libgcc1   1:5.3.1-7
ii  libgnutls30   3.4.8-3
ii  libosip2-11   4.1.0-2
ii  libsipwitch1  1.6.1-2+b2
ii  libstdc++65.3.1-7
ii  libucommon7v5 6.4.4-2

Versions of packages sipwitch recommends:
ii  cron   3.0pl1-128
ii  logrotate  3.8.7-2

Versions of packages sipwitch suggests:
pn  sipwitch-cgi  

-- no debconf information

Bug#813645: jessie-pu: package libclamunrar/0.99-0+deb8u1

[Sebastian Andrzej Siewior]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: jessie
Severity: normal

The upgrade of clamav in Jessie (#807969) requires a source upload of
libclamunrar building libclamunrar7 instead of libclamunrar6.

Please find attached a complete diff against current stable release.
Most of it just noise. This package is what we have in unstable
currently. The important part is probably m4/reorganization/version.m4
next to the debian/ folder

The library was tested on i386 against
/usr/share/clamav-testfiles/*.rar.

Sebastian
diff --git a/Makefile.in b/Makefile.in
index a7cac882adca..074e9f267d6a 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -1,7 +1,7 @@
-# Makefile.in generated by automake 1.14.1 from Makefile.am.
+# Makefile.in generated by automake 1.15 from Makefile.am.
 # @configure_input@
 
-# Copyright (C) 1994-2013 Free Software Foundation, Inc.
+# Copyright (C) 1994-2014 Free Software Foundation, Inc.
 
 # This Makefile.in is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -14,7 +14,17 @@
 
 @SET_MAKE@
 VPATH = @srcdir@
-am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)'
+am__is_gnu_make = { \
+  if test -z '$(MAKELEVEL)'; then \
+false; \
+  elif test -n '$(MAKE_HOST)'; then \
+true; \
+  elif test -n '$(MAKE_VERSION)' && test -n '$(CURDIR)'; then \
+true; \
+  else \
+false; \
+  fi; \
+}
 am__make_running_with_option = \
   case $${target_option-} in \
   ?) ;; \
@@ -79,17 +89,6 @@ build_triplet = @build@
 host_triplet = @host@
 target_triplet = @target@
 subdir = .
-DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \
-	$(top_srcdir)/configure $(am__configure_deps) \
-	$(srcdir)/clamav-config.h.in $(srcdir)/platform.h.in COPYING \
-	config/compile config/config.guess config/config.rpath \
-	config/config.sub config/depcomp config/install-sh \
-	config/missing config/ltmain.sh $(top_srcdir)/config/compile \
-	$(top_srcdir)/config/config.guess \
-	$(top_srcdir)/config/config.rpath \
-	$(top_srcdir)/config/config.sub \
-	$(top_srcdir)/config/install-sh $(top_srcdir)/config/ltmain.sh \
-	$(top_srcdir)/config/missing
 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
 am__aclocal_m4_deps = $(top_srcdir)/m4/acinclude.m4 \
 	$(top_srcdir)/m4/ax_check_uname_syscall.m4 \
@@ -112,6 +111,7 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/acinclude.m4 \
 	$(top_srcdir)/m4/reorganization/libs/xml.m4 \
 	$(top_srcdir)/m4/reorganization/libs/openssl.m4 \
 	$(top_srcdir)/m4/reorganization/libs/json.m4 \
+	$(top_srcdir)/m4/reorganization/libs/pcre.m4 \
 	$(top_srcdir)/m4/reorganization/libs/libz.m4 \
 	$(top_srcdir)/m4/reorganization/libs/bzip.m4 \
 	$(top_srcdir)/m4/reorganization/libs/unrar.m4 \
@@ -151,12 +151,15 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/acinclude.m4 \
 	$(top_srcdir)/m4/reorganization/distcheck.m4 \
 	$(top_srcdir)/m4/reorganization/llvm.m4 \
 	$(top_srcdir)/m4/reorganization/sha_collect.m4 \
+	$(top_srcdir)/m4/reorganization/yara.m4 \
 	$(top_srcdir)/m4/reorganization/bsd.m4 \
 	$(top_srcdir)/m4/reorganization/libs/curl.m4 \
 	$(top_srcdir)/m4/reorganization/substitutions.m4 \
 	$(top_srcdir)/configure.ac
 am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
 	$(ACLOCAL_M4)
+DIST_COMMON = $(srcdir)/Makefile.am $(top_srcdir)/configure \
+	$(am__configure_deps) $(am__DIST_COMMON)
 am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
  configure.lineno config.status.lineno
 mkinstalldirs = $(install_sh) -d
@@ -220,6 +223,16 @@ ETAGS = etags
 CTAGS = ctags
 CSCOPE = cscope
 DIST_SUBDIRS = $(SUBDIRS)
+am__DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/clamav-config.h.in \
+	$(srcdir)/platform.h.in $(top_srcdir)/config/compile \
+	$(top_srcdir)/config/config.guess \
+	$(top_srcdir)/config/config.rpath \
+	$(top_srcdir)/config/config.sub \
+	$(top_srcdir)/config/install-sh $(top_srcdir)/config/ltmain.sh \
+	$(top_srcdir)/config/missing COPYING config/compile \
+	config/config.guess config/config.rpath config/config.sub \
+	config/depcomp config/install-sh config/ltmain.sh \
+	config/missing config/ylwrap
 DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
 distdir = $(PACKAGE)-$(VERSION)
 top_distdir = $(distdir)
@@ -275,6 +288,7 @@ CC = @CC@
 CCDEPMODE = @CCDEPMODE@
 CFGDIR = @CFGDIR@
 CFLAGS = @CFLAGS@
+CHECK_CFLAGS = @CHECK_CFLAGS@
 CHECK_CPPFLAGS = @CHECK_CPPFLAGS@
 CHECK_LIBS = @CHECK_LIBS@
 CLAMAVGROUP = @CLAMAVGROUP@
@@ -321,6 +335,7 @@ GENHTML = @GENHTML@
 GETENT = @GETENT@
 GPERF = @GPERF@
 GREP = @GREP@
+HAVE_YARA = @HAVE_YARA@
 INSTALL = @INSTALL@
 INSTALL_DATA = @INSTALL_DATA@
 INSTALL_PROGRAM = @INSTALL_PROGRAM@
@@ -332,6 +347,9 @@ JSON_LIBS = @JSON_LIBS@
 LCOV = @LCOV@
 LD = @LD@
 LDFLAGS = @LDFLAGS@
+LEX = @LEX@
+LEXLIB = @LEXLIB@
+LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@
 LIBBZ2 = @LIBBZ2@
 LIBBZ2_PREFIX = @LIBBZ2_PREFIX@
 LIBCLAMAV_CPPFLAGS = @LIBCLAMAV_CPPFLAGS@
@@ -364,6 +382,11 @@ PACKAGE_TARNAME = @PACKAGE_TA

Bug#813644: ruby-albino: FTBFS: assert_match %(# é), code

[Chris Lamb]

Source: ruby-albino
Version: 1.3.3-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,

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

  [..]

  
RUBYLIB=/home/lamby/temp/cdt.20160203231145.5acNUVZ0Oi/ruby-albino-1.3.3/debian/ruby-albino/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-albino/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.2 -I"lib"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/*_test.rb" 
  Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
  Started
  .F
  
===
  Failure:
\#\ \u00E9<\/span>/> expected to be =~
<"# 
\u00E9\n\n\n">.
  test_works_with_utf8_strings(AlbinoTest)
  
/home/lamby/temp/cdt.20160203231145.5acNUVZ0Oi/ruby-albino-1.3.3/test/albino_test.rb:42:in
 `test_works_with_utf8_strings'
   39:   def test_works_with_utf8_strings
   40: code = Albino.new("# é", :bash).colorize
   41: assert_match %r(highlight), code
=> 42: assert_match %(# é), code
   43:   end
   44: 
   45:   def test_works_with_files
  
===
  
  
  Finished in 2.846354828 seconds.
  --
  22 tests, 30 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
  95.4545% passed
  --
  7.73 tests/s, 10.54 assertions/s
  rake aborted!
  Command failed with status (1): [ruby -I"lib"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/*_test.rb" ]
  
  Tasks: TOP => default => test
  (See full trace by running task with --trace)
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160203231145.5acNUVZ0Oi/ruby-albino-1.3.3/debian/ruby-albino
 returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

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


ruby-albino.1.3.3-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#813643: numexpr: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Chris Lamb]

Source: numexpr
Version: 2.4.3-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,

numexpr fails to build from source in unstable/amd64:

  [..]
  
  ==
  ERROR: test_reductions (__main__.test_numexpr)
  --
  Traceback (most recent call last):
File "numexpr/tests/test_numexpr.py", line 95, in test_reductions
  x = zeros(1e5) + .01  # checks issue #41
  TypeError: 'float' object cannot be interpreted as an index
  
  ==
  ERROR: test_reductions (__main__.test_numexpr2)
  --
  Traceback (most recent call last):
File "numexpr/tests/test_numexpr.py", line 95, in test_reductions
  x = zeros(1e5) + .01  # checks issue #41
  TypeError: 'float' object cannot be interpreted as an index
  
  --
  Ran 5434 tests in 5.111s
  
  FAILED (errors=2)
  debian/rules:59: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160203230943.1VeeSgqY1a/numexpr-2.4.3'
  debian/rules:18: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


numexpr.2.4.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#287789: IT Service Desk

[Salma Farah]

We detected a suspicious login to your email account (Sep 23, 2015, 1:47 PM).
Note: This location is based on information from your ISP or wireless provider.

Was this you? If so, you can disregard this alert message.

If this wasn't you, please follow the links below to protect your email account 
information from future account hijacking: - >Click 
Here:


Yours sincerely,
IT Service Desk


The information in this e-mail is intended solely for the addressee(s) named, 
and is confidential. Any other distribution, disclosure or copying is strictly 
prohibited. If you have received this communication in error, please reply by 
e-mail to the sender and delete or destroy all copies of this message.
Les renseignements contenus dans le présent message électronique sont 
confidentiels et concernent exclusivement le(s) destinataire(s) désigné(s). Il 
est strictement interdit de distribuer ou de copier ce message. Si vous avez 
reçu ce message par erreur, veuillez répondre par courriel à l'expéditeur et 
effacer ou détruire toutes les copies du présent message.

Bug#813641: multcomp: FTBFS: Error : package 'MASS' required by 'TH.data' could not be found

[Chris Lamb]

Source: multcomp
Version: 1.4-2-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,

multcomp fails to build from source in unstable/amd64:

  [..]

  * installing *source* package 'multcomp' ...
  ** package 'multcomp' successfully unpacked and MD5 sums checked
  ** R
  ** data
  *** moving datasets to lazyload DB
  ** demo
  ** inst
  ** preparing package for lazy loading
  Error : package 'MASS' required by 'TH.data' could not be found
  ERROR: lazy loading failed for package 'multcomp'
  * removing 
'/home/lamby/temp/cdt.20160203230629.amdKvAuzFF/multcomp-1.4-2/debian/r-cran-multcomp/usr/lib/R/site-library/multcomp'
  /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
   `-


multcomp.1.4-2-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#813642: netty-3.9: FTBFS: mv: cannot stat 'debian/libnetty-3.9-java/usr/share/java/netty.jar': No such file or directory

[Chris Lamb]

Source: netty-3.9
Version: 3.9.0.Final-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,

netty-3.9 fails to build from source in unstable/amd64:

  [..]

  Install jar for netty into /usr/share/java
  [INFO] 

  [INFO] BUILD SUCCESS
  [INFO] 

  [INFO] Total time: 1.300 s
  [INFO] Finished at: 2016-02-03T23:09:38+01:00
  [INFO] Final Memory: 11M/298M
  [INFO] 

mh_resolve_dependencies --non-interactive --offline -plibnetty-3.9-java 
--base-directory=/home/lamby/temp/cdt.20160203230716.t87RFxqiA4/netty-3.9-3.9.0.Final
 --non-explore
  Analysing pom.xml...
  mv debian/libnetty-3.9-java/usr/share/java/netty.jar \
 debian/libnetty-3.9-java/usr/share/java/netty-3.9.0.Final.jar
  mv: cannot stat 'debian/libnetty-3.9-java/usr/share/java/netty.jar': No such 
file or directory
  debian/rules:7: recipe for target 'override_dh_auto_install' failed
  make[1]: *** [override_dh_auto_install] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160203230716.t87RFxqiA4/netty-3.9-3.9.0.Final'
  debian/rules:4: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


netty-3.9.3.9.0.Final-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#813639: parallel: new version available upstream: 20151222

[Ohm Base]

Package: parallel
Version: 20141022+ds1-1
Severity: wishlist

Dear Maintainer,

As per

https://www.gnu.org/software/parallel/

a new version of GNU parallel (20151222) is available on the GNU project's
FTP
site at

http://ftp.gnu.org/gnu/parallel/




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

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

Versions of packages parallel depends on:
ii  perl  5.22.1-5
ii  perl-modules-5.22 [perl-modules]  5.22.1-5
ii  sysstat   11.2.0-1

parallel recommends no packages.

parallel suggests no packages.

-- no debconf information

Bug#813640: Enable VMX crypto extensions module

[Timothy Pearson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA224

Package: linux-image-4.3.0-1-powerpc64
Version: 4.3.3-7
Severity: normal

The POWER8 processors use VMX to accelerate cryptographic functions.  
Linux supports the use of VMX for cryptographic acceleration, however
Debian does not build this module, leaving users of some systems (e.g.
OpenPOWER) unable to reach rated bandwidths e.g. in OpenSSL.

Please enable the VMX cryptographic extensions module with
CONFIG_CRYPTO_DEV_VMX=m in the kernel configuration.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iFYEARELAAYFAlayfr0ACgkQLaxZSoRZrGG7jgDeJP6HVdTmuRbnBrMdM9JKxLFS
V0e4BLuRB2qp8gDdHQ2pcqsHPF1uxHHMag5N7c8GZgGv0N0a5vEgYQ==
=epAE
-END PGP SIGNATURE-

Bug#813638: wishlist: add --dicomdir commandline option

[Karsten Hilbert]

Package: aeskulap
Version: 0.2.2b1-13+b2
Severity: wishlist
Tags: upstream

Dear Maintainer,

Aeskulap has functionality to read studies from disk by way of a DICOMDIR
file which can be selected via a menu item.

It would be really helpful for using Aeskulap in daily medical practice
if the application was enhanced to offer the same functionality via a
commandline option, like so:

$> aeskulap --dicomdir=/path/to/a/DICOMDIR

or even

$> aeskulap /path/to/a/DICOMDIR

In the latter case, however, the code processing "path/to/a/DICOMDIR"
would need to distinguish DICOMDIR files from DICOM image files because

$> aeskulap /path/to/an/DICOM/imagefile.dcm

already works.

Thanks for considering,
Karsten

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

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

Versions of packages aeskulap depends on:
ii  dcmtk3.6.1~20131114-4
ii  gconf-service3.2.6-3
ii  gconf2   3.2.6-3
ii  libatk1.0-0  2.18.0-1
ii  libatkmm-1.6-1   2.22.7-2.1
ii  libc62.19-22
ii  libcairo21.14.6-1
ii  libcairomm-1.0-1 1.10.0-1.1
ii  libdcmtk23.6.0-15+b1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6.1-0.1
ii  libgcc1  1:5.1.1-14
ii  libgconf-2-4 3.2.6-3
ii  libgconfmm-2.6-1c2   2.28.0-1.1
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libglade2-0  1:2.6.4-2
ii  libglademm-2.4-1c2a  2.6.7-4
ii  libglib2.0-0 2.46.2-3
ii  libglibmm-2.4-1c2a   2.44.0-1
ii  libgtk2.0-0  2.24.29-1
ii  libgtkmm-2.4-1c2a1:2.24.4-1.1
ii  libjpeg62-turbo  1:1.4.1-2
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpangoft2-1.0-01.38.1-1
ii  libpangomm-1.4-1 2.36.0-1
ii  libpng12-0   1.2.54-1
ii  libsigc++-2.0-0c2a   2.4.1-1
ii  libstdc++6   5.1.1-14
ii  libtiff5 4.0.6-1
ii  libwrap0 7.6.q-25
ii  libxml2  2.9.1+dfsg1-5

aeskulap recommends no packages.

aeskulap suggests no packages.

-- no debconf information

Bug#813232: The right place to call setup_devices in debootstrap (?)

[jhcha54008]

Hi,

It seems that setup_devices() was called previously from the end
of first_stage(). It was moved then to the beginning of second_stage()
to solve #498731 and #531316 
(see commit d3518b9c7e4f693562d99ec4c15bb009b456603b of debootstrap 
version 1.0.34)
As far as I understand, the aim was to cross-debootstrap kfreebsd/Hurd
(ie first_stage runs in linux, second_stage runs in kfreebsd/Hurd)

What is the right place of setup_device to permit all use cases ?

I hope it will help !

Regards,
JH Chatenet

Bug#813637: mdadm: raid-1 assembly faild due to removed disk

[Anders Boström]

Package: mdadm
Version: 3.3.2-5+deb8u1
Severity: important

Hi!

The following sequence of operations made my system end up in booting
to emergency mode due to failure to assembly 2 of my raid-1 arrays,
md5 and md6.

1. Working system with 3 raid 1 arrays.
2. One disk start to report SMART errors.
3. Install new replacement disk.
4. Partition replacement disk and add to the raid 1 arrays.
5. Grow the raids to 3 devices.
6. Wait until the sync is done.
7. Fail (mdadm /dev/md5 --fail /dev/sdh2) the disk reporting SMART errors.
8. Remove (mdadm /dev/md5 --remove /dev/sdh2) the disk reporting SMART
   errors.
9. "Grow" the raids to 2 devices again.
10. Reboot.

After the reboot, in emergency mode, 'mdadm -A --scan' failed to
assembly any array and reported problems with the disk I had failed
and removed!

''mdadm -A md5' reported failure to find any partitions with the right
UUID. But when checking mdadm.conf and comparing to
'mdadm -E /dev/sdf3', the UUID match.

'mdadm -A md5 /dev/sdf3 /dev/sdi3' and
'mdadm -A md6 /dev/sdf4 /dev/sdi4' worked fine.

/ Anders

-- Package-specific info:
--- mdadm.conf
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST 
MAILADDR and...@bostrom.dyndns.org
ARRAY /dev/md0 UUID=4093a038:462303e2:d516da34:f28a82cb
ARRAY /dev/md5 UUID=3f343f37:8c2bea5b:99538d3a:74394982
ARRAY /dev/md6 UUID=45f90cc6:2f9efbe1:7ed54299:8e77c287

--- /etc/default/mdadm
INITRDSTART='/dev/md0'
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid1] 
md6 : active raid1 sdf4[0] sdi4[1]
  931834176 blocks [2/2] [UU]
  
md5 : active (auto-read-only) raid1 sdf3[0] sdi3[1]
  1951808 blocks [2/2] [UU]
  
md0 : active raid1 sdg1[0] sdi2[2](W)(S) sdf1[1](W)
  39079872 blocks [2/2] [UU]
  
unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   8   80  976762584 sdf
   8   81   42973843 sdf1
   8   831951897 sdf3
   8   84  931834260 sdf4
   8   96   39080664 sdg
   8   97   39079936 sdg1
   8  112  976762584 sdh
   8  113   39086113 sdh1
   8  1141951897 sdh2
   8  116  931834260 sdh4
   8  128 3907018584 sdi
   8  129   1007 sdi1
   8  130   39079936 sdi2
   8  1311952768 sdi3
   8  132  931836928 sdi4
   8  133 2934147911 sdi5
  1101048575 sr0
   90   39079872 md0
   951951808 md5
   96  931834176 md6

--- LVM physical volumes:
LVM does not seem to be used.
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=505091,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=811652k,mode=755)
/dev/md0 on / type ext4 
(rw,relatime,discard,errors=remount-ro,stripe=128,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/md0 on /nfs4/root type ext4 
(rw,relatime,discard,errors=remount-ro,stripe=128,data=ordered)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/md6 on /srv type ext4 (rw,relatime,data=ordered)
/dev/md6 on /nfs4/root/srv type ext4 (rw,relatime,data=ordered)
/dev/md6 on /nfs4/srv type ext4 (rw,relatime,data=ordered)
/dev/md6 on /nfs4/root/nfs4/srv type ext4 (rw,relatime,data=ordered)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
/etc/a

Bug#813636: libmicrohttpd10: new version available upstream: 0.9.48

[Ohm Base]

Package: libmicrohttpd10
Version: 0.9.44+dfsg-1+b2
Severity: wishlist

Dear Maintainer,

As per

https://www.gnu.org/software/libmicrohttpd/

a new version ( 0.9.48 ) has been released on the GNU project's FTP server:

ftp://ftp.gnu.org/gnu/libmicrohttpd






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

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

Versions of packages libmicrohttpd10 depends on:
ii  libc62.21-7
ii  libgcrypt20  1.6.4-5
ii  libgnutls30  3.4.8-3

libmicrohttpd10 recommends no packages.

libmicrohttpd10 suggests no packages.

-- no debconf information

Bug#805498: systemd: Systemd errors in syslog: Failed to set cpu.cfs_{period, quota}_us

[Ralf Jung]

Hi,

> It's not really a bug in the logging. The log messages seem correct to me.

Then I don't understand... how can it be, just because docker needs some
cgroups (or whatever) for its operation that have not been enabled, that
systemd suddenly tries (and fails) to use those cgroups on completely
unrelated units? Like this:

> Jan 19 19:25:02 core.hacksaar.de systemd[1]: Failed to set cpu.cfs_quota_us 
> on /system.slice/apache2.service: Permission denied

> Which docker version is that btw?

This is Docker 1.9.1.

Kind regards,
Ralf

Bug#805498: systemd: Systemd errors in syslog: Failed to set cpu.cfs_{period, quota}_us

[Michael Biebl]

Am 03.02.2016 um 22:24 schrieb Ralf Jung:
> Hi,
> 
>> Afaics, docker is using one of CPU* resource control features. This
>> requires a kernel that supports it.
>> You can either try to convince the kernel maintainers to enable that
>> support, compile a kernel on your own, or fix docker, to not make use of
>> that feature in jessie. I don't think there is a lot we can do in
>> systemd about this.
> 
> I agree. The units that show this error are entirely independent from
> Docker, so I still do not understand how installing Docker can trigger
> this - but that's at best a minor bug in the logging.

It's not really a bug in the logging. The log messages seem correct to me.
Which docker version is that btw?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#798023: cssutils: diff for NMU version 1.0-4.1

[gregor herrmann]

Control: tags 798023 + pending

Dear maintainer,

Chris Knadle has prepared an NMU for cssutils (versioned as 1.0-4.1)
and I've uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  Homepage https://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: Cranberries: Dreams
diff -Nru cssutils-1.0/debian/changelog cssutils-1.0/debian/changelog
--- cssutils-1.0/debian/changelog	2015-11-30 00:31:12.0 +0100
+++ cssutils-1.0/debian/changelog	2016-02-03 22:40:28.0 +0100
@@ -1,3 +1,12 @@
+cssutils (1.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches:
+- Add 02_fix_octal_escape.patch to fix FTBFS bug with Python 3.5
+  (Closes: #798023).
+
+ -- Christopher Knadle   Thu, 21 Jan 2016 05:21:33 -0500
+
 cssutils (1.0-4) unstable; urgency=high
 
   * Upload to unstable (Closes: #802063).
diff -Nru cssutils-1.0/debian/patches/02_fix_octal_escape.patch cssutils-1.0/debian/patches/02_fix_octal_escape.patch
--- cssutils-1.0/debian/patches/02_fix_octal_escape.patch	1970-01-01 01:00:00.0 +0100
+++ cssutils-1.0/debian/patches/02_fix_octal_escape.patch	2016-02-03 22:43:41.0 +0100
@@ -0,0 +1,18 @@
+Description: Fix octal escape on Python 3.5
+Origin: https://bitbucket.org/cthedot/cssutils/commits/866a29f7e03447199ba22fb114d42a7aab027db9/raw/
+Author: Daniel 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798023
+Bug-Upstream: https://bugs.python.org/issue22362
+Last-Updated: 2016-01-21
+
+--- a/src/cssutils/profiles.py
 b/src/cssutils/profiles.py
+@@ -102,7 +102,7 @@
+ 'nmstart': r'[_a-z]|{nonascii}|{escape}',
+ 'nonascii': r'[^\0-\177]',
+ 'unicode': r'\\[0-9a-f]{1,6}(\r\n|[ \n\r\t\f])?',
+-'escape': r'{unicode}|\\[ -~\200-\777]',
++'escape': r'{unicode}|\\[ -~\u0080-\u01ff]',
+ #   'escape': r'{unicode}|\\[ -~\200-\417]',
+ 'int': r'[-]?\d+',
+ 'nmchar': r'[\w-]|{nonascii}|{escape}',
diff -Nru cssutils-1.0/debian/patches/series cssutils-1.0/debian/patches/series
--- cssutils-1.0/debian/patches/series	2015-11-29 23:20:19.0 +0100
+++ cssutils-1.0/debian/patches/series	2016-02-03 22:40:28.0 +0100
@@ -1 +1,2 @@
 01_setup_fix.patch
+02_fix_octal_escape.patch


signature.asc
Description: Digital Signature

Bug#813635: freeipmi: New version available upstream: 1.5.1

[Ohm Base]

Package: freeipmi
Version: 1.4.11-1
Severity: wishlist

Dear Maintainer,

As per

http://lists.gnu.org/archive/html/freeipmi-announce/2015-12/msg0.html

A new version of FreeIPMI has been released (1.5.1) and is available on the
GNU
project's FTP site.

http://ftp.gnu.org/gnu/freeipmi/freeipmi-1.5.1.tar.gz




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

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

Versions of packages freeipmi depends on:
ii  freeipmi-bmc-watchdog  1.4.11-1
ii  freeipmi-common1.4.11-1
ii  freeipmi-ipmidetect1.4.11-1
ii  freeipmi-tools 1.4.11-1

freeipmi recommends no packages.

freeipmi suggests no packages.

-- no debconf information

Bug#813374: general: Menus and window popup does not work after recent upgrade

[Vincent Danjean]

Le 03/02/2016 12:31, Thomas Goirand a écrit :
> Vincent,
> 
> This sounds like issues with your window manager, since you mostly
> complain about issues with window placements and dispositions. Just to
> be sure, you're using XFCE, right?

Yes.
But is the WM involved in (the placement of) application menus ?
If yes, xfce seems indeed a good target.

  Regards,
Vincent

> Cheers,
> 
> Thomas Goirand (zigo)
> 


-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Bug#805498: systemd: Systemd errors in syslog: Failed to set cpu.cfs_{period, quota}_us

[Ralf Jung]

Hi,

> Afaics, docker is using one of CPU* resource control features. This
> requires a kernel that supports it.
> You can either try to convince the kernel maintainers to enable that
> support, compile a kernel on your own, or fix docker, to not make use of
> that feature in jessie. I don't think there is a lot we can do in
> systemd about this.

I agree. The units that show this error are entirely independent from
Docker, so I still do not understand how installing Docker can trigger
this - but that's at best a minor bug in the logging.

Kind regards,
Ralf

Bug#813631: Pending fixes for bugs in the libdatetime-timezone-perl package

[pkg-perl-maintainers]

tag 813631 + pending
thanks

Some bugs in the libdatetime-timezone-perl package are closed in
revision aa8ee0c81ddd01abc7583abe6d906643c1288de0 in branch 'master'
by gregor herrmann

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

Commit message:

Fix spelling of Chita in the previous changelog entry.

Thanks: Stepan Golosunov for the bug report.
Closes: #813631

Bug#813631: libdatetime-timezone-perl: Chita is misspelled in the changelog

[gregor herrmann]

Control: found -1 1:1.75-2+2016a

On Thu, 04 Feb 2016 00:43:08 +0400, Stepan Golosunov wrote:

> Package: libdatetime-timezone-perl
> Version: 1:1.95-1+2016a
> Severity: minor
> 
> Chita is misspelled in the changelog:
> 
> >* Import upstream version 1.95.
> >  Based on version 2016a of the Olson database. This release includes
> >  contemporary changes for the Cayman Islands, Iran, and Chrita, Russia.

Thanks for the bug report, and sorry for the mistake, I copied this
from the upstream Changes file.
 
> (Looks like 1:1.75-2+2016a is affected too.)

Right. Both fixed in git, will be in the next upload.

Cheers,
gregor

-- 
 .''`.  Homepage https://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: John Zorn: Ravayah (Sparks)


signature.asc
Description: Digital Signature

Bug#813406: [Pkg-samba-maint] Bug#813406: ctdb, raw sockets and CVE-2015-8543

[Adi Kriegisch]

Hi!

> There are two set of patches:
> - yours that basically keep the same behavior as pre-CVE-2015-8543 (proto=0)
I just desperately tried to get my cluster going again... ;-)

> - Amitay's that restore the intented behavior (proto=255)
[...] 
> I think I'll got for Amitay's patch which probably fixes a lot of
> weird behaviors I've seen pre-CVE-2015-8543 (i.e TCP connections not
> reset, Ip not properly relocated).
This is -- of course -- the way better approach!

> I plan to fix this for wheezy and jessie. stretch will come with next
> upstream release.
> 
> Givent the importance of the bug, I think it can go thru -security.
I think so too -- especially as it is some kind of regression.

Thank you very much for taking care of this!

-- Adi


signature.asc
Description: Digital signature

Bug#813631: Pending fixes for bugs in the libdatetime-timezone-perl package

[pkg-perl-maintainers]

tag 813631 + pending
thanks

Some bugs in the libdatetime-timezone-perl package are closed in
revision 94c5152ef4dc5b4d3ea0c7d1a3ae32fc8ad4b380 in branch ' 
jessie' by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdatetime-timezone-perl.git/commit/?id=94c5152

Commit message:

Fix spelling of Chita in the previous changelog entry.

Thanks: Stepan Golosunov for the bug report.
Closes: #813631

Bug#813634: RFP: erlang-sd-notify -- Erlang bindings for systemd-notify subsystem

[Heather Ellsworth]

Package: wnpp
Severity: wishlist

* Package name: erlang-sd-notify
  Version : 0.9-1
  Upstream Author : Peter Lemenkov 
* URL : https://github.com/lemenkov/erlang-sd_notify.git
* License : MIT
  Programming Lang: Erlang
  Description : Erlang bindings for systemd-notify subsystem

With erlang-sd-notify installed, then packages like rabbitmq-server have access 
to using the type notify. Since some services like rabbitmq take a while to 
completely stop, using type notify becomes relevent to prevent issues when 
stopping and starting rabbimq in a short period of time. Without type notify, 
rabbit can incorrectly report it's status to systemd which can cause problems 
if stopped/started frequesntly. 

I don't believe there is an equivalent package that allows the use of similar 
notifications already in debian.

Note that the original author is Peter Lemenkov. However his branch was forked 
to create https://github.com/Gsantomaggio/erlang-sd_notify.git. Gsantomaggio's 
was forked to create Jan's https://github.com/jan-grant/erlang-sd_notify.git. 
Jan's version has an option to make deb packages.

Thank you for considering this package,
Heather Ellsworth

Bug#813632: digikam crashes when tagging a photo

[G. Milde]

Package: digikam
Version: 4:4.14.0-3
Severity: important

Dear Maintainer,


* What led up to the situation?

adding/removing a tag to a photo.
   
* What exactly did you do (or not do) that was effective (or
  ineffective)?

Updating digikam to 4.14.0, updating Debian to "stretch".

1. Open digikam (with a large collection that used to work before the update)
2. Open an album
3. Select a photography
4. Open the labels/tags sidebar
5. Add a tag or remove a tag
6. Press "Apply" or move selection to the next photography.
 
* What was the outcome of this action?

digikam crashed with

digikam: tiffcomposite.cpp:749: virtual Exiv2::Internal::TiffComponent* 
Exiv2::Internal::TiffMnEntry::doAddPath(uint16_t, Exiv2::Internal::TiffPath&, 
Exiv2::Internal::TiffComponent*, Exiv2::Internal::TiffComponent::AutoPtr): 
Zusicherung »mn_« nicht erfüllt.
digikam: Fatal IO error: client killed

(After re-opening digikam, the tag was set/removed.)

* What outcome did you expect instead?

No crash, just setting/removing the tag.



The issue also manifested when editing an image, i.e. replacing
4 to 6 above with

4. open the image in the editor (F4)
5. some edit
6. save new version

crash.




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

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

Versions of packages digikam depends on:
ii  digikam-data4:4.14.0-3
ii  digikam-private-libs4:4.14.0-3
ii  kde-runtime 4:15.08.3-1
ii  libc6   2.21-7
ii  libgcc1 1:5.3.1-7
ii  libgphoto2-62.5.9-3
ii  libgphoto2-port12   2.5.9-3
ii  libkdcraw23 4:15.08.0-1+b1
ii  libkdecore5 4:4.14.14-1+b1
ii  libkdeui5   4:4.14.14-1+b1
ii  libkexiv2-114:15.04.3-1
ii  libkhtml5   4:4.14.14-1+b1
ii  libkio5 4:4.14.14-1+b1
ii  libkipi11   4:15.08.3-1
ii  libknotifyconfig4   4:4.14.14-1+b1
ii  libkparts4  4:4.14.14-1+b1
ii  libopencv-core2.4v5 2.4.9.1+dfsg-1.2
ii  libopencv-imgproc2.4v5  2.4.9.1+dfsg-1.2
ii  libphonon4  4:4.8.3-2
ii  libqt4-dbus 4:4.8.7+dfsg-5
ii  libqt4-sql  4:4.8.7+dfsg-5
ii  libqt4-sql-sqlite   4:4.8.7+dfsg-5
ii  libqt4-xml  4:4.8.7+dfsg-5
ii  libqtcore4  4:4.8.7+dfsg-5
ii  libqtgui4   4:4.8.7+dfsg-5
ii  libsolid4   4:4.14.14-1+b1
ii  libstdc++6  5.3.1-7
ii  libthreadweaver44:4.14.14-1+b1
ii  perl5.22.1-4
ii  phonon  4:4.8.3-2

Versions of packages digikam recommends:
ii  chromium [www-browser]   47.0.2526.80-1~deb8u1
ii  dillo [www-browser]  3.0.5-1+b1
ii  elinks [www-browser] 0.12~pre6-11+b2
ii  iceweasel [www-browser]  43.0.4-1
ii  kipi-plugins 4:4.14.0-3
ii  midori [www-browser] 0.5.11-ds1-2
ii  mplayerthumbs4:15.08.3-1

Versions of packages digikam suggests:
ii  digikam-doc 4:4.4.0-1.1
ii  systemsettings  4:5.4.3-1

-- no debconf information

Bug#813633: botan1.10: FTBFS with nocheck in DEB_BUILD_OPTIONS

[Thorsten Glaser]

Source: botan1.10
Version: 1.10.12-1
Severity: serious
Justification: Policy §4.9.1
X-Debbugs-Cc: debian-...@lists.debian.org

Your package FTBFS with nocheck in DEB_BUILD_OPTIONS:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dh_auto_test -- check
LD_LIBRARY_PATH="/usr/lib/libeatmydata:/<>" ./check --validate
/bin/sh: 1: ./check: not found
debian/rules:34: recipe for target 'override_dh_auto_test' failed

Bug#813406: [Pkg-samba-maint] Bug#813406: ctdb, raw sockets and CVE-2015-8543

[Mathieu Parent]

2016-02-01 17:29 GMT+01:00 Adi Kriegisch :
> Package: ctdb
> Severity: grave
> Tags: patch,upstream
>
> Hi!
>
> The kernel upgrade for CVE-2015-8543 showed a bug in CTDB that leads to a
> broken cluster:
>   | s = socket(AF_INET, SOCK_RAW, htons(IPPROTO_RAW));
> htons(IPPROTO_RAW) leads to 0xff00 which causes "-1 EINVAL (Invalid
> argument)" because of CVE-2015-8543.
> The fix for the issue is quite simple: remove IPPROTO_RAW; to make the fix
> more consistent with what was used before, use IPPROTO_IP (which is 0).
>
> Error messages related to this bug are:
>   | We are still serving a public IP 'x.x.x.x' that we should not be serving. 
> Removing it
>   | common/system_common.c:89 failed to open raw socket (Invalid argument)
>   | Could not find which interface the ip address is hosted on. can not 
> release it
> and
>   | common/system_linux.c:344 failed to open raw socket (Invalid argument)
> As a result, IP addresses cannot be released and multiple nodes in the
> cluster serve the same address, which obviously does not work.

Thank you so much for finding this bug! I was wondering why my
clusters were crazy, blaming the network itself.

> Upstream bug: https://bugzilla.samba.org/show_bug.cgi?id=11705 and mailing
> list conversation: 
> https://lists.samba.org/archive/samba/2016-January/197389.html

There are two set of patches:
- yours that basically keep the same behavior as pre-CVE-2015-8543 (proto=0)
- Amitay's that restore the intented behavior (proto=255)

Also you patch only fixes 2 functions.

Amitay's patch also fixes references to ETHERTYPE_ARP (0x0806) and
ETH_P_ALL (0x0003)

I think I'll got for Amitay's patch which probably fixes a lot of
weird behaviors I've seen pre-CVE-2015-8543 (i.e TCP connections not
reset, Ip not properly relocated).

I plan to fix this for wheezy and jessie. stretch will come with next
upstream release.

Givent the importance of the bug, I think it can go thru -security.

Regards
-- 
Mathieu

Bug#813631: libdatetime-timezone-perl: Chita is misspelled in the changelog

[Stepan Golosunov]

Package: libdatetime-timezone-perl
Version: 1:1.95-1+2016a
Severity: minor

Chita is misspelled in the changelog:

>* Import upstream version 1.95.
>  Based on version 2016a of the Olson database. This release includes
>  contemporary changes for the Cayman Islands, Iran, and Chrita, Russia.

(Looks like 1:1.75-2+2016a is affected too.)

Bug#808775: CKeditor: outstanding issues and maintenance; build system

[roucaries bastien]

On Wed, Feb 3, 2016 at 4:02 PM, Dmitry Smirnov  wrote:
> Guys, we have a problem with CKeditor.
> As I've recently realised, in its current source form CKeditor can't be
> loaded dynamically which breaks one of my packages after update. Therefore
> CKeditor badly needs maintenance.
>
> I took some time to learn how to build CKeditor from source. Current way is
> not safe and not compatible with official release. The best way to build
> CKeditor is to use CKbuilder that I've just packaged (#813577). As soon as it
> will be accepted I'd like to update CKeditor ASAP so I'm offering myself as
> (co-)maintainer.


Thanks help welcome.

How do you achieve to clean ckbuilder from source is missing and
license problem ?

Last time I give up...
> Knowing that package is in poor shape and not updated for a while I took
> liberty to introduce some improvements into "master" branch that I created in
> the package repository:
>
> https://anonscm.debian.org/cgit/collab-maint/ckeditor.git
Done pushed
>
> I did that because I found repository in bad shape -- one tag incorrectly
> applied (mismatch with uploaded package), two tags missing which comes down
> to three last uploads not committed. :(
>
> In master branch I was working only within "debian" directory and I did not
> touch upstream files as I'm not too sure about repository layout and I wanted
> to avoid introducing too many layout-related changes.

Layout is gitpkg. I have added debian directory above all. I use
debian/version branch for upstream+patches+debian directory
upstream/version for upstream and debian-patches/version for upstream+patch

> Bastien, would you be interested to help or would you rather leave CKeditor
> maintenance with me (at least for some time)?

I cannot work on it now. I need to care about my new born baby.

> Frank, are you still interested in maintaining CKeditor?
>
> Thanks.
>
> --
> Best wishes,
>  Dmitry Smirnov.
>
> ---
>
> There is not enough love and goodness in the world to permit giving any of
> it away to imaginary beings.
> -- Friedrich Nietzsche

Bug#813630: [libphonenumber6-dev] Missing 'template_util.h' from "base/memory/scoped_ptr.h"

[Leonhard Weber]

Package: libphonenumber6-dev
Version: 6.3~svn698-3+b1
Severity: normal

Hi,

when attempting to compile against libphonenumber6-dev headers it fails:

In file included from /usr/include/phonenumbers/asyoutypeformatter.h:40:
/usr/include/phonenumbers/base/memory/scoped_ptr.h:25:10: fatal error:
'phonenumbers/base/template_util.h' file not found
#include "phonenumbers/base/template_util.h"
 ^
1 error generated.

Looks like it is missing from the contents of libphonenumber6-dev:
$> dpkg -L libphonenumber6-dev
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libgeocoding.a
/usr/lib/x86_64-linux-gnu/libphonenumber.a
/usr/include
/usr/include/phonenumbers
/usr/include/phonenumbers/asyoutypeformatter.h
/usr/include/phonenumbers/base
/usr/include/phonenumbers/base/synchronization
/usr/include/phonenumbers/base/synchronization/lock.h
/usr/include/phonenumbers/base/memory
/usr/include/phonenumbers/base/memory/singleton.h
/usr/include/phonenumbers/base/memory/scoped_ptr.h
/usr/include/phonenumbers/base/basictypes.h
/usr/include/phonenumbers/geocoding
/usr/include/phonenumbers/geocoding/phonenumber_offline_geocoder.h
/usr/include/phonenumbers/phonenumbermatcher.h
/usr/include/phonenumbers/phonenumbermatch.h
/usr/include/phonenumbers/utf
/usr/include/phonenumbers/utf/unicodetext.h
/usr/include/phonenumbers/unicodestring.h
/usr/include/phonenumbers/shortnumberutil.h
/usr/include/phonenumbers/shortnumberinfo.h
/usr/include/phonenumbers/regexp_cache.h
/usr/include/phonenumbers/regexp_adapter.h
/usr/include/phonenumbers/phonenumberutil.h
/usr/include/phonenumbers/phonemetadata.pb.h
/usr/include/phonenumbers/phonenumber.pb.h
/usr/include/phonenumbers/logger.h
/usr/include/phonenumbers/callback.h
/usr/share
/usr/share/doc
/usr/share/doc/libphonenumber6-dev
/usr/share/doc/libphonenumber6-dev/changelog.Debian.gz
/usr/share/doc/libphonenumber6-dev/changelog.Debian.amd64.gz
/usr/share/doc/libphonenumber6-dev/copyright
/usr/share/doc/libphonenumber6-dev/CONTRIBUTORS
/usr/share/doc/libphonenumber6-dev/AUTHORS
/usr/lib/x86_64-linux-gnu/libphonenumber.so
/usr/lib/x86_64-linux-gnu/libgeocoding.so

There is no telling if there are more missing, this is maybe the first
of missing headers, could be more, did not probe further.

At the state of affairs, libphonenumber7(-dev) breaks a debian stable +
bpo's installation because of the dependency on newer libc(++?). So no
temporary workaround there. Did not try backports either because of the
huge pull on the Java realm.

Thank you very much for the packaging of this library in the first place.
I'd very much appreciate any help that can be provided.

Its my first bugreport, so please go easy on me ;). Maybe I'm just
overlooking something?.

Best Regards,
Leonhard Weber

--- System information. ---
Architecture: amd64
Kernel: Linux 4.3.0-0.bpo.1-amd64
Debian Release: 8.3




signature.asc
Description: OpenPGP digital signature

Bug#813629: libccaudio2-dev: new version available upstream: 2.2.0

[Ohm Base]

Package: libccaudio2-dev
Version: 2.1.3-1.1+b2
Severity: wishlist

Dear Maintainer,

There is a new version of ccaudio2 available upstream (2.2.0) at the GNU
project.

https://www.gnu.org/software/ccaudio/
ftp://ftp.gnu.org/pub/gnu/ccaudio/





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

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

Versions of packages libccaudio2-dev depends on:
ii  libc6   2.21-7
ii  libccaudio2-2   2.1.3-1.1+b2
ii  libgcc1 1:5.3.1-7
ii  libgnutls30 3.4.8-3
ii  libgsm1 1.0.13-4
ii  libspeex1   1.2~rc1.2-1
ii  libstdc++6  5.3.1-7
ii  libucommon-dev  6.4.4-2
ii  libucommon7v5   6.4.4-2
ii  pkg-config  0.29-3

libccaudio2-dev recommends no packages.

libccaudio2-dev suggests no packages.

-- no debconf information

Bug#813301: Related bugs

[Geoffrey Merck]

After resuming from suspend the scrren rotates just fine. 

Some related issues : 

[](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813301)[https://bugzilla.kernel.org/show_bug.cgi?id=109501](https://bugzilla.kernel.org/show_bug.cgi?id=109501)

[https://bugzilla.kernel.org/show_bug.cgi?id=111321](https://bugzilla.kernel.org/show_bug.cgi?id=111321)

[https://github.com/hadess/iio-sensor-proxy/issues/66](https://github.com/hadess/iio-sensor-proxy/issues/66)

  

Bug#813619: closed by Michael Biebl (Re: Bug#813619: libgdata: aptitude build-dep libgdata19 fails to install libuhttpmock-dev)

[Karl O. Pinc]

On Wed, 03 Feb 2016 19:54:05 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> It has been closed by Michael Biebl .

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


Karl 
Free Software:  "You don't pay back, you pay forward."
 -- Robert A. Heinlein

Bug#802331: jessie-pu: package cyrus-imapd-2.4/2.4.17+nocaldav-1

[Adam D. Barratt]

Hi,

On Mon, 2016-02-01 at 17:19 +0100, Ondřej Surý wrote:
> Control: retitle -1 jessie-pu: package
> cyrus-imapd-2.4/2.4.17+nocaldav-0~deb8u1
> 
> So, it looks like the security queue is quite stalled, so I will use
> your offer to p-u.
> 
> Just changed s/jessie-security/jessie/ and preparing the rebuild.
> debdiff should be same as already attached except this change.

I have to admit that I'm slightly confused by the uploaded diff:

- is it intentional that doc/man/*.html disappear?
- what are the changes to e.g. imap/{annotate,arbitron,backend}.c about?

Regards,

Adam

Bug#813628: Fix debian/watch for rabbitmq

[Nicholas Luedtke]

Package: rabbitmq-server
Version: 3.5.7-1
Tags: patch

The watch file is broken.  Attached below is a patch to reflect the
current layout.

-- 
Nicholas Luedtke
Linux for HP Helion OpenStack, Hewlett-Packard Enterprise
diff -Nru rabbitmq-server-3.5.7/debian/watch rabbitmq-server-3.5.7/debian/watch
--- rabbitmq-server-3.5.7/debian/watch	2016-02-03 13:21:41.365715596 -0700
+++ rabbitmq-server-3.5.7/debian/watch	2016-02-03 13:24:22.665714406 -0700
@@ -1,2 +1,2 @@
 version=3
-http://www.rabbitmq.com/releases/rabbitmq-server/v(.*)/rabbitmq-server-(\d.*)\.tar\.gz
+http://www.rabbitmq.com/releases/rabbitmq-server/v(.*)/rabbitmq-server_(\d.*)\.orig\.tar\.xz


signature.asc
Description: OpenPGP digital signature

Bug#813627: mate-terminal.wrapper doesn't run commands with parameters with -e opti, on

[John Paul Adrian Glaubitz]

On 02/03/2016 08:59 PM, Stefano Salvi wrote:
> I tred to execute the result of a compilation within Geany (a GTK simpe
> editor/ide).
> The terminal opens but it contains the following message:
> 
>  Errore nel creare il processo figlio per questo terminale
> 
> Esecuzione del processo figlio "/bin/sh ./geany_run_script.sh" non riuscita
> (File o directory non esistente)

Please run the application you try to debug with "LC_ALL=C", this way
you don't have to translate error messages which is also a very bad
idea since your translation most likely deviates from the
original English error message which means it's very hard to find
bug reports like these when googling the original English error message.

> In the system only Mate dektop is installed.
> Geany invokes x-terminal-emulator -e "/bin/sh ./geany_run_script.sh"
> x-terminal-emulator is linked to mate-terminal.wrapper
> Mate-terminal.wrapper translates "-e" parameter in the unknown parameter
> "-x".

You are reporting a bug against a very old version of mate-terminal. The
wrapper script has been re-written for newer versions of mate-terminal,
you may want to update to a newer version of mate-terminal (and
therefore MATE) first before reporting a bug here. We're not going to
fix bugs in older versions.

> I preapred a patch to solve the proble. Double check it as it modifies the
> wrapper in /usr/bin and I'm not shure I prepared it correctly

That's not a proper patch. Use "diff -u" to create a proper patch.

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#813565: 358.16 is far more recent than the 355.11 witch is 7 month old. SO why was it uploaded to experimental?

[Eric Valette]

looking at nvidia driver page I really wonder why someone decided to 
upload this old, not ABI 20 compatible driver to experimental!


-- eric

Bug#813627: mate-terminal.wrapper doesn't run commands with parameters with -e opti,on

[Stefano Salvi]

Package: mate-terminal
Version: 1.8.1+dfsg1-4
Severity: normal
Tags: patch

Dear Maintainer,

I tred to execute the result of a compilation within Geany (a GTK simpe
editor/ide).
The terminal opens but it contains the following message:

 Errore nel creare il processo figlio per questo terminale

Esecuzione del processo figlio "/bin/sh ./geany_run_script.sh" non riuscita
(File o directory non esistente)

that translates to:

Error in creating child process
Execution of child process "/bin/sh ./geany_run_script.sh" failed (file or
directory missing)

The correct result would be the execution of the compiled program, it's 
output.


In the system only Mate dektop is installed.
Geany invokes x-terminal-emulator -e "/bin/sh ./geany_run_script.sh"
x-terminal-emulator is linked to mate-terminal.wrapper
Mate-terminal.wrapper translates "-e" parameter in the unknown parameter 
"-x".


I preapred a patch to solve the proble. Double check it as it modifies the
wrapper in /usr/bin and I'm not shure I prepared it correctly



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

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

Versions of packages mate-terminal depends on:
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u2
ii  libcairo2 1.14.0-2.1
ii  libdconf1 0.22.0-1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u4
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-3
ii  libice6   2:1.0.9-1+b1
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libsm62:1.2.2-1+b1
ii  libvte9   1:0.28.2-5
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  mate-desktop-common   1.8.1+dfsg1-3+deb8u1
ii  mate-terminal-common  1.8.1+dfsg1-4
pn  python:any

mate-terminal recommends no packages.

mate-terminal suggests no packages.

-- no debconf information

*** usr/bin/mate-terminal.wrapper	2016-02-03 20:03:08.156040385 +0100
--- usr.new/bin/mate-terminal.wrapper	2016-02-03 20:12:32.318236873 +0100
***
*** 35,41 
  elif arg == '-h' or arg == '--help':
  newargs.append('--help')
  elif arg == '-e':
! newargs.append('-x')
  newargs += oldargs
  break
  except IndexError:
--- 35,41 
  elif arg == '-h' or arg == '--help':
  newargs.append('--help')
  elif arg == '-e':
! newargs.append('-e')
  newargs += oldargs
  break
  except IndexError:

Bug#813623: wheezy-pu: package libdatetime-timezone-perl/1:1.58-1+2016a

[gregor herrmann]

On Wed, 03 Feb 2016 19:35:25 +, Adam D. Barratt wrote:

> On Wed, 2016-02-03 at 19:40 +0100, gregor herrmann wrote:
> > I've prepared an update for libdatetime-timezone-perl for wheezy,
> > incorporating the changes of the 2016a tzdata release [0].
> Please go ahead.

Thanks! Uploaded.

Cheers,
gregor

-- 
 .''`.  Homepage https://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: Wir sind Helden: (Ode) An die Arbeit


signature.asc
Description: Digital Signature

Bug#750498: IdleExitTimeout is the silver bullet

[Dominique Brazziel]

Just specifying 'IdleExitTimeout 0' keeps the CUPS daemon
from exiting on idle activity.  'SystemdIdleTimeout' does not
work and throws an error in cupsd.conf.

Bug#813622: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016a

[gregor herrmann]

On Wed, 03 Feb 2016 19:35:53 +, Adam D. Barratt wrote:

> On Wed, 2016-02-03 at 19:40 +0100, gregor herrmann wrote:
> > I've prepared an update for libdatetime-timezone-perl for jessie,
> > incorporating the changes of the 2016a tzdata release [0].
> Please go ahead.

Thanks! Uploaded.

Cheers,
gregor

-- 
 .''`.  Homepage https://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: Wir sind Helden: (Ode) An die Arbeit


signature.asc
Description: Digital Signature