Bug#847428: Package the Entire "eclipse.jdt.core"

[殷啟聰]

Source: ecj
Version: 3.11.0-7
Severity: wishlist
Control: block 847427 by -1

Dear maintainers,

android-toolchain-jack requires both the existing libecj-java and the
"org.eclipse.jdt.compiler.apt" module in "eclipse.jdt.core". As the
upstream of src:ecj is exactly "eclipse.jdt.core", so I wish that the
entire "eclipse.jdt.core" is packaged in Debian as several non-GUI
Java libraries.

I noticed that "org.eclipse.jdt.compiler.apt" is provided by
eclipse-jdt, which is a GUI application component (a plugin of Eclipse
IDE). There's no need for a command line program to depend on a
graphical package which will then pulls the entire Eclipse Platform.

Bug#847044: allow gitlab 8.13.6+dfsg2-1 to migrate testing

[Pirate Praveen]

On ബുധന്‍ 07 ഡിസംബര്‍ 2016 12:32 വൈകു, Niels Thykier wrote:
> I have added a hint to ignore the piuparts issues.

But gitlab is still not migrated after 7 days.



signature.asc
Description: OpenPGP digital signature

Bug#734218: spice: Please support powerpcspe (and maybe other architectures)

[Riku Voipio]

severity 734218 important
user debian-...@lists.debian.org
usertags 734218 arm64
thanks

Wookeys patch looks good to me. Liang,  Michael, can you upload or are you ok
with an NMU?

Riku

Bug#847427: ITP: android-toolchain-jack -Java Android Compiler Kit

[殷啟聰]

Package: wnpp
Severity: wishlist

* Package Name: android-toolchain-jack
* Version : 1.3~b8
* Upstream Author : The Android Open Source Project
* License : Apache-2.0
* Programming Lang: Java
* Description : Java Android Compiler Kit
* URL : https://android.googlesource.com/toolchain/jack
* Repo: https://gitlab.com/seamlik/debianpkg_android-toolchain-jack

Jack is the experimental Java compiler for building Android applications. It is
included in the Android SDK but needs to be enabled explicitly.

This package builds the following binary packages:

  * jack-compiler: Java Android Compiler Kit
  * jill-linker: Jack Intermediate Library Linker

For more information please visit [1] [2].

[1]: https://source.android.com/source/jack.html
[2]: https://sites.google.com/a/android.com/tools/tech-docs/jackandjill

Bug#847426: RFS: fortune-zh/2.0

[lumin]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: a...@debian.org, as...@debian.org, 073p...@gmail.com

Dear mentors,

  I am looking for a sponsor for my package "fortune-zh"

 * Package name: fortune-zh
   Version : 2.0
   Upstream Author : myself
 * URL : http://anonscm.debian.org/cgit/chinese/fortune-zh.git
 * License : GPL-3+
   Section : games

  It builds those binary packages:

fortune-zh - Chinese Data files for fortune

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/fortune-zh


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/f/fortune-zh/fortune-zh_2.0.dsc

  More information about hello can be obtained from

http://debomatic-amd64.debian.net/distribution#unstable/fortune-zh/2.0/buildlog

  Changes since the last upload:

fortune-zh (2.0) unstable; urgency=medium

  * New 2.X release.
  * Bump standards version to 3.9.8 . (requires no change)
  * Use https link in both Vcs-Git and Vcs-Browser section.
  * Fix invalid encodings in tang300 (LP: #499664)
  * Add new Chinese cookie under chinese.d/ .
  * Rewrite d/copyright in dep8 machine-readable style.
  * Update package description.
  * Update manpage man/fortune-zh.6 .
  * Simplify Makefile, removing redundant lines.
  * Remove .u8 symlinks. Use fortune-zh.links to create symlinks instead.
  * Override false positive lintian: capitalization-error-in-description .
  * Add autopkgtest support -- test fortune-zh script and cookie files.
  * Update fortune-zh script.

  [ Boyuan Yang ]
  * Add a Simplified Chinese manpage.

Bug#839961: libjs-d3: please package new upstream release

[Petter Reinholdtsen]

Note, I am told by its authors that coz depend on libjs-d3 too, but do not
work with version 4 as it has a different API.
-- 
Happy hacking
Petter Reinholdtsen

Bug#847353: [Pkg-javascript-devel] help with node-grunt-contrib-requirejs

[Pirate Praveen]

[adding debian-ruby and #847353]

On വ്യാഴം 08 ഡിസംബര്‍ 2016 10:34 രാവിലെ, Pirate Praveen wrote:
> I think you are only checking for jquery-ui.js and not all the other files 
> like jquery-ui/widgets/datepicker.js
> 
> I did not see any error in gitlab when using the embedded copy of jquery-ui 
> in ruby-jquery-ui-rails (removed .links and installed app directory). So it 
> has to be a bug in the build system.

I just found the root cause, ruby-jquery-ui-rails adds dependency
mapping at the top in addition to embedding the corresponding jquery-ui
files. There is a rake task to generate these files if we symlink
pkg-javascript/jqueryui directory to ruby-jquery-ui-rails/jquery-ui. I
think if we create node-jquery-ui package and add it as a build
dependency of ruby-jquery-ui-rails and symlink /usr/lib/nodejs/jquery-ui
to ruby-jquery-ui-rails/jquery-ui this will solve the problem.

ruby-jquery-ui-rails$ diff -u
app/assets/javascripts/jquery-ui/widgets/draggable.js
/usr/share/javascript/jquery-ui/ui/widgets/draggable.js
--- app/assets/javascripts/jquery-ui/widgets/draggable.js   2016-12-07
11:27:13.193475539 +0530
+++ /usr/share/javascript/jquery-ui/ui/widgets/draggable.js 2016-09-14
22:01:37.0 +0530
@@ -1,12 +1,3 @@
-//= require jquery-ui/widgets/mouse
-//= require jquery-ui/data
-//= require jquery-ui/plugin
-//= require jquery-ui/safe-active-element
-//= require jquery-ui/safe-blur
-//= require jquery-ui/scroll-parent
-//= require jquery-ui/version
-//= require jquery-ui/widget
-
 /*!
  * jQuery UI Draggable 1.12.1
  * http://jqueryui.com





signature.asc
Description: OpenPGP digital signature

Bug#794438: [Pkg-kde-extras] Bug#794438: Partition manager does not launch

[Scott Kitterman]

On Thursday, December 08, 2016 11:18:35 AM Boyuan Yang wrote:
> Hello,
> 
> Ping everyone,
> 
> Partition Manager will miss Stretch if we do not solve this problem
> (#794438), which would be a great pity.
> 
> Anyone would like to work on this issue and solve the problem? Maybe we can
> port the new version from Ubuntu to greatly reduce the efforts.

I'm willing to sponsor partition manager if someone has a well put together, 
tested package.

Scott K

Bug#847325: Unable to copy symlinks with copy_file

[Vincent Bernat]

 ❦  8 décembre 2016 02:08 GMT, Ben Hutchings  :

> (Annoyingly, I couldn't reproduce this at first because I tried just
> adding nouveau to /etc/initramfs-tools/modules.  Since mkinitramfs does
> *not* use 'set -e' (unlike most hooks), the 'failure' of copy_file was
> not fatal.)

I should have said that I got the error through plymouth hook.
-- 
Civilization is the limitless multiplication of unnecessary necessities.
-- Mark Twain


signature.asc
Description: PGP signature

Bug#847425: linux-image-4.8.0-1-amd64: Oops on boot with unable to handle kernel paging request after software IO TLB mapping

[clemens . schwaighofer]

Package: src:linux
Version: 4.8.7-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Booting Linux 4.8.0-1-amd64 kernel in a VMware ESX 6

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Tried to boot with various boot options (eg nomodeset), but oops always
appeared

   * What was the outcome of this action?

Kernel hangs during boot.

Output is only visible if all framebuffer settings are turned off.
Bug output was catched via COM port

Note:
I have another VMware with the same settings (memory 8GB, two cores) that also 
does not boot.
But I have three other VMwares with only 4GB of memory, two cores that boot.

DMESG output:

[0.00] Linux version 4.8.0-1-amd64 (debian-ker...@lists.debian.org) 
(gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 
(2016-11-13)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-1-amd64 
root=/dev/mapper/vg-root ro nomodeset console=tty0 console=ttyS0,19200n8
[0.00] Disabled fast string operations
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable
[0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xbfee] usable
[0.00] BIOS-e820: [mem 0xbfef-0xbfefefff] ACPI data
[0.00] BIOS-e820: [mem 0xbfeff000-0xbfef] ACPI NVS
[0.00] BIOS-e820: [mem 0xbff0-0xbfff] usable
[0.00] BIOS-e820: [mem 0xf000-0xf7ff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec0] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xfffe-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00023fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.4 present.
[0.00] Hypervisor detected: VMware
[0.00] e820: last_pfn = 0x24 max_arch_pfn = 0x4
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: last_pfn = 0xc max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000f6b30-0x000f6b3f] mapped at 
[a03d400f6b30]
[0.00] RAMDISK: [mem 0x35cbd000-0x36e55fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F6AC0 24 (v02 PTLTD )
[0.00] ACPI: XSDT 0xBFEF109B 5C (v01 INTEL  440BX
0604 VMW  01324272)
[0.00] ACPI: FACP 0xBFEFEE73 F4 (v04 INTEL  440BX
0604 PTL  000F4240)
[0.00] ACPI: DSDT 0xBFEF1349 00DB2A (v01 PTLTD  Custom   
0604 MSFT 0301)
[0.00] ACPI: FACS 0xBFEFFFC0 40
[0.00] ACPI: FACS 0xBFEFFFC0 40
[0.00] ACPI: BOOT 0xBFEF1321 28 (v01 PTLTD  $SBFTBL$ 
0604  LTP 0001)
[0.00] ACPI: APIC 0xBFEF12C3 5E (v01 PTLTD  ? APIC   
0604  LTP )
[0.00] ACPI: MCFG 0xBFEF1287 3C (v01 PTLTD  $PCITBL$ 
0604  LTP 0001)
[0.00] ACPI: SRAT 0xBFEF1197 F0 (v02 VMWARE MEMPLUG  
0604 VMW  0001)
[0.00] ACPI: HPET 0xBFEF115F 38 (v01 VMWARE VMW HPET 
0604 VMW  0001)
[0.00] ACPI: WAET 0xBFEF1137 28 (v01 VMWARE VMW WAET 
0604 VMW  0001)
[0.00] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[0.00] SRAT: PXM 0 -> APIC 0x01 -> Node 0
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x-0x0009]
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x0010-0x0fff]
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x1000-0xbfff]
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x1-0x23fff]
[0.00] NUMA: Node 0 [mem 0x-0x0009] + [mem 
0x0010-0x0fff] -> [mem 0x-0x0fff]
[0.00] NUMA: Node 0 [mem 0x-0x0fff] + [mem 
0x1000-0xbfff] -> [mem 0x-0xbfff]
[0.00] NUMA: Node 0 [mem 0x-0xbfff] + [mem 
0x1-0x23fff] -> [mem 0x-0x23fff]
[0.00] NODE_DATA(0) allocated [mem 0x23fff8000-0x23fffcfff]
[

Bug#847369: Error: Cannot find module 'requirejs' (missing package.json)

[Pirate Praveen]

On വ്യാഴം 08 ഡിസംബര്‍ 2016 01:18 രാവിലെ, László Böszörményi (GCS) wrote:
>  Package is upadted and this is fixed.

Thanks for the quick update. Can you check the test failure of
grunt-contrib-requirejs? (same git repo, you need to run quilt push
before running grunt) Full error message here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847367#14

>> Also consider using pkg-javascript alioth repo for this package (there
>> is a repo there, but it is outdated), so we can fix these kind of issues
>> faster.
>  Thanks, will consider it. I try to act fast, package is going to be
> uploaded soon.

It helps when you are away or busy as other team members can take care
of the package. But its your choice, just mentioned it.



signature.asc
Description: OpenPGP digital signature

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

[olivier sallou]

Le jeu. 8 déc. 2016 01:04, Sascha Steinbiss  a
écrit :

> Hi Andreas and Andrew,
>
> to address this problem I have taken a shot at patching Debian’s Artemis
> to use the new htsjdk API, avoiding SAMFileReader and using the
> SamReaderFactory instead. This fixed the FTBFS for me.
> I tested BAM file reading by opening MAL1.embl.gz from the test/data
> directory and adding MAL1_8h.bam via ‘File->Read BAM/VCF...'. One of the
> genes has some mapped reads that are indeed shown. Comparing the displayed
> pile of mapped reads to the one shown by the recent Artemis version I have
> on Mac OS X, the result seems to be correct, but given my lack of practical
> experience with the BAM/VCF/‘anything-to-do-with-reads' components of
> Artemis I can’t say if I caught everything.
>
If you compile and can view the bam, i would consider the api call is
correct and so your patch

Olivier




> I also updated the Debian version to 16.0.17, the latest release from
> Sanger. This allowed me to drop a couple of patches that I already merged
> earlier with my part-time-upstream hat on.
> For now I have pushed my work into the ’6_0_17’ branch in git and I would
> like to kindly ask for some more testing. I don’t have suitable test data
> here and don’t really feel like an expert to test the right usage patterns.
>
> Cheers
> Sascha
>
> > On 5 Dec 2016, at 15:56, Andrew Page  wrote:
> >
> > Hi Andreas,
> > Thanks for letting us know.  We are actively trying to hire a Java
> developer who will take over the maintenance and development of Artemis. So
> unfortunately it will be at least a few months before we will have anyone
> in post to work on it.  If you happen to know of anyone looking for a job,
> please send them our way!
> > Regards,
> > Andrew
> >
> >
> >
> >> On 5 Dec 2016, at 14:40, Andreas Tille  wrote:
> >>
> >> Hi,
> >>
> >> after uploading htsjdk 2.7.0 Artemis failed to build from source[1].  I
> >> relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
> >> was removed from htsjdk source and assumed that this was by accident.
> >> However, upstream has dropped this interface intentionally as you can
> >> read below.  In issue #767[2] an htsjdk author gives advise to use the
> >> new API version.
> >>
> >> Kind regards
> >>
> >>  Andreas.
> >>
> >>
> >> [1] https://bugs.debian.org/846671
> >> [2] https://github.com/samtools/htsjdk/issues/767
> >>
> >>
> >> - Forwarded message from Daniel Gómez-Sánchez <
> notificati...@github.com> -
> >>
> >> Date: Mon, 05 Dec 2016 06:18:16 -0800
> >> From: Daniel Gómez-Sánchez 
> >> To: samtools/htsjdk 
> >> Cc: Andreas Tille , Author  >
> >> Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0
> (#767)
> >>
> >> The file was removed in #699 because it was deprecated. I guess that
> either 1) fastqc/artemis should be updated to use the new API version, or
> 2) the classpath for them in Debian should include an older version.
> >>
> >> --
> >> You are receiving this because you authored the thread.
> >> Reply to this email directly or view it on GitHub:
> >> https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910
> >>
> >> - End forwarded message -
> >>
> >> --
> >> http://fam-tille.de
> >>
> >> - End forwarded message -
> >>
> >> --
> >> http://fam-tille.de
> >
> >
> >
> > --
> > The Wellcome Trust Sanger Institute is operated by Genome Research
> > Limited, a charity registered in England with number 1021457 and a
> > company registered in England with number 2742969, whose registered
> > office is 215 Euston Road, London, NW1 2BE.
> >
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@lists.alioth.debian.org
> >
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>
>

Bug#844486: [Freewx-maint] Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Adrian Bunk]

Control: unmerge 846019
Control: severity 844486 minor
Control: affects 846019 =
Control: reassign 846019 pgadmin3 1.22.2-1

On Wed, Dec 07, 2016 at 07:36:42PM -0500, Scott Talbert wrote:
> On Thu, 8 Dec 2016, Olly Betts wrote:
> 
> > #846019 looks to be something different - it's giving a *FATAL* error there
> > (it's not obvious to me how or why since the two strings seem to match aside
> > from the ABI and I've not had time to try to reproduce yet), but that means 
> > it
> > would not be helped by the proposed patch, since it's not invoking the 
> > warning
> > case but dropping through to the fatal error code below.
> 
> I haven't been able to reproduce the fatal error either.  I wonder if
> perhaps it has some dependency on the user's language settings, as the
> original reporter has LANG=sv_SE.UTF-8.  I tried setting my LANG to
> sv_SE.UTF-8 but still wasn't able to repro, but maybe I didn't do it
> correctly.

After trying to run pgadmin3, I can also not reproduce it.

It is even possible that the crash is completely unrelated to the 
warning message.

I am moving #846019 back to pgadmin3.

> Scott

cu
Adrian

-- 

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

Bug#847367: ITP: node-grunt-contrib-requirejs -- Optimize RequireJS projects using r.js

[Pirate Praveen]

Control: tags -1 help

tests are failing.

$ grunt
Running "clean:test" (clean) task
>> 0 paths cleaned.

Running "requirejs:compile" (requirejs) task

Running "requirejs:template" (requirejs) task

Running "requirejs:onOptimize" (requirejs) task

Running "nodeunit:tests" (nodeunit) task
Testing requirejs_test.jsFF.
>> requirejs - main
>> Message: should optimize javascript modules with requireJS
>> Error:
'define("hello",[],function(){return"hello"}),define("world",[],function(){return"world"}),require(["hello","world"],function(e,t){console.log(e,t)}),define("project",function(){});'
==
'define("hello",[],function(){return"hello"}),define("world",[],function(){return"world"}),require(["hello","world"],function(e,n){console.log(e,n)}),define("project",function(){});'
>>   at Object.equal (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
>>   at Object.exports.requirejs.main (test/requirejs_test.js:13:10)
>>   at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
>>   at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
>>   at /usr/lib/nodejs/nodeunit/lib/core.js:236:16
>>   at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9)
>>   at /usr/lib/nodejs/nodeunit/lib/core.js:118:25
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:513:13
>>   at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13)
>>   at async.forEachSeries (/usr/lib/nodejs/nodeunit/deps/async.js:139:9)
>>   at _concat (/usr/lib/nodejs/nodeunit/deps/async.js:512:9)
>>   at Object.concatSeries (/usr/lib/nodejs/nodeunit/deps/async.js:152:23)
>>   at Object.exports.runSuite (/usr/lib/nodejs/nodeunit/lib/core.js:96:11)
>>   at /usr/lib/nodejs/nodeunit/lib/core.js:125:21
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:513:13
>>   at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13)
>>   at async.forEachSeries (/usr/lib/nodejs/nodeunit/deps/async.js:139:9)
>>   at _concat (/usr/lib/nodejs/nodeunit/deps/async.js:512:9)
>>   at Object.concatSeries (/usr/lib/nodejs/nodeunit/deps/async.js:152:23)
>>   at Object.exports.runSuite (/usr/lib/nodejs/nodeunit/lib/core.js:96:11)
>>   at Object.exports.runModule
(/usr/lib/nodejs/nodeunit/lib/core.js:158:13)
>>   at /usr/lib/nodejs/nodeunit/lib/nodeunit.js:75:21
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:513:13
>>   at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13)
>>   at async.forEachSeries (/usr/lib/nodejs/nodeunit/deps/async.js:139:9)
>>   at _concat (/usr/lib/nodejs/nodeunit/deps/async.js:512:9)
>>   at Object.concatSeries (/usr/lib/nodejs/nodeunit/deps/async.js:152:23)
>>   at /usr/lib/nodejs/nodeunit/lib/nodeunit.js:73:15
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:518:13
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:131:25
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:515:17
>>   at /usr/lib/nodejs/nodeunit/lib/utils.js:67:24
>>   at FSReqWrap.oncomplete (fs.js:82:15)

>> requirejs - template
>> Message: should process options with template variables.
>> Error:
'define("hello",[],function(){return"hello"}),define("world",[],function(){return"world"}),require(["hello","world"],function(e,t){console.log(e,t)}),define("project",function(){});'
==
'define("hello",[],function(){return"hello"}),define("world",[],function(){return"world"}),require(["hello","world"],function(e,n){console.log(e,n)}),define("project",function(){});'
>>   at Object.equal (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
>>   at Object.exports.requirejs.template (test/requirejs_test.js:25:10)
>>   at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
>>   at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
>>   at /usr/lib/nodejs/nodeunit/lib/core.js:236:16
>>   at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9)
>>   at /usr/lib/nodejs/nodeunit/lib/core.js:118:25
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:513:13
>>   at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13)
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:134:25
>>   at /usr/lib/nodejs/nodeunit/deps/async.js:515:17
>>   at Immediate._onImmediate
(/usr/lib/nodejs/nodeunit/lib/types.js:146:17)
>>   at processImmediate [as _immediateCallback] (timers.js:383:17)

Warning: 2/3 assertions failed (16ms) Use --force to continue.




signature.asc
Description: OpenPGP digital signature

Bug#846464: apt: Please drop B-D on googletest on unsupported architectures

[Steve M. Robbins]

Hi,

Executive summary: the build failures are mostly solved -- save for one test 
failure on m68k.

On Thursday, December 1, 2016 1:16:43 PM CST David Kalnischkies wrote:

> So @googletest maintainers, please state what you can/want to do about
> it or not.  Being a build-dependency of apt provides some benefits, 

... such as ?  :-)


> also carries a cost in that there basically is no distinction between
> release, non-release and unofficial port architectures.  If you
> can't/won't pay that price that is fine, we (as in deity@l.d.o) just
> need to know and we will figure something out – I just want to ask first
> before we rush into evaluating and moving to other testing frameworks,
> which is time better spent on other bugs if we can help it…

OK, so the root cause of the issues was that one of the tests in googletest's 
own test suite was failing when I first built it.  The failure went away if I 
built without optimization, so that is what I did for the first 3 uploads (the 
build is ONLY used for the test suite, so I figured lack of optimization is 
acceptable).  I don't know whether this failure (gtest_catch_exceptions_test) 
is a bug in GoogleTest or in Debian's toolchain as no-one else seems to be 
reporting it.  

Anyway, for some reason, building with no optimization caused failures in many 
architectures -- typically overflowing a symbol table; c.f. #845274.   It was 
surprising to me that optimiziation would affect the number of symbols 
produced.  In any case, rev 3 fixed that issue but inadvertently caused a 
different set of problems because setting CXXFLAGS disables the dpkg hardening 
flags.  Rev 4 fixes that, re-enables optimization, but drops the failing test.  
There are two architectures left to hear from, but -- apart from m68k -- all 
others have successfully built now.

I do intend to look into the m68k failure, but would really appreciate some 
help with it.  And with the failure of gtest_catch_exceptions_test -- which 
I'd prefer to reinstate once fixed.

I'm not certain what the original question was, but maybe the above helps.  If 
not, please elaborate.

Best,
-Steve


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

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

[Salvatore Bonaccorso]

tags 844121 + wontfix
notfound 844121 2.0.13-1.2
thanks

Hi all

In meanwhile the CVEs were properly rejected by MITRE. I'm closing
this bugreport now.

Regards,
Salvatore

Bug#846918: interface opens, but no menus and no action on button clicks

[tony mancill]

On Wed, Dec 07, 2016 at 10:55:38AM +0100, gregor herrmann wrote:
> On Wed, 07 Dec 2016 09:49:32 +0100, Martin Lutz wrote:
> 
> > Package: jabref
> > Version: 2.10+ds-7
> > Followup-For: Bug #846918
> > 
> > Dear Maintainer,
> > 
> > after an update yesterday, jabref fails to start.
> > ERROR while starting or running JabRef: java.lang.NoSuchFieldError: DIALOG
> > 
> > Searching through the debian bug list, I find bug 846503 with a similar 
> > problem.
> 
> Yup, there seem to be some runtime incompatibilitites with the new
> libjgoodies-*, which were not caught at buildtime. Cf. also the
> thread starting at
> https://lists.debian.org/debian-java/2016/12/msg00010.html
> 
> Probably we'll try with rebuilding the affected packages; for JabRef
> the good news is that we're working on updating to 3.6 which doesn't
> have these problems (but needs some wrinkles ironed out before we can
> upload it).

I attempted a binary rebuild of 2.10+ds using the libraries found in sid
and it didn't change the behavior.  It appears that it might be an issue
with the version of jgoodies-looks (2.7.0) available in Debian.  I will
dig into this more, since it could be affecting other users of
jgoodies-looks similarly, but at the moment, I'm trying to get an
updated JabRef version into the archive before stretch freezes.

Currently we're working on JabRef 3.6, but due to some excellent
assistance from upstream (thanks Oliver!), it could also be 3.7.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

[Pirate Praveen]

Control: severity -1 normal

On 2016, ഡിസംബർ 8 8:42:57 AM IST, Johannes Schauer  wrote:
>
>When I now enter my gitlab instance I only get a 502 error with the
>message "Whoops, GitLab is taking too much time to respond".
>
>Since the last time I changed the version of a ruby package you told me
>to run assets:precompile, I ran the following command:
>
>runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat
>/etc/gitlab/gitlab-debian.conf) && rake assets:precompile
>RAILS_ENV=production'
>Could not find grape-entity-0.5.1 in any of the sources
>Run `bundle install` to install missing gems.
>
>Given the error above, I suspect that the new ruby-grape-entity version
>is the culprit here.

I think its just the old Gemfile.lock expecting the older version. We should 
truncate Gemfile.lock in postinst.

>Thanks!
>
>cheers, josch

Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

[Pirate Praveen]

On 2016, ഡിസംബർ 8 8:53:16 AM IST, Johannes Schauer  wrote:
>Hi,
>
>On Thu, 08 Dec 2016 04:12:57 +0100 Johannes Schauer 
>wrote:
>> When I now enter my gitlab instance I only get a 502 error with the
>message
>> "Whoops, GitLab is taking too much time to respond".
>> 
>> Since the last time I changed the version of a ruby package you told
>me
>> to run assets:precompile, I ran the following command:
>> 
>> runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat
>/etc/gitlab/gitlab-debian.conf) && rake assets:precompile
>RAILS_ENV=production'
>> Could not find grape-entity-0.5.1 in any of the sources
>> Run `bundle install` to install missing gems.
>> 
>> Given the error above, I suspect that the new ruby-grape-entity
>version
>> is the culprit here.
>
>in the hopes that the gitlab postinst maintainer script would contain
>something
>that fixes this problem, I ran "apt-get install --reinstall gitlab"
>with the
>following result:
>
>Verifying we have all required libraries...
>Could not find gem 'grape-entity (~> 0.5.0)' in any of the gem sources
>listed in
>your Gemfile or available on this machine.
>dpkg: error processing package gitlab (--configure):
>subprocess installed post-installation script returned error exit
>status 7
>Processing triggers for systemd (232-7) ...
>Errors were encountered while processing:
> gitlab
>E: Sub-process /usr/bin/dpkg returned an error code (1)

This is fixed in git, you need to update ruby-grape-entity.

>
>
>Thanks!
>
>cheers, josch

Bug#847422: lintian: Syntax error in spelling/corrections

[Francois Gouget]

Package: lintian
Version: 2.5.49
Severity: normal

Dear Maintainer,

Line 544 of /usr/share/lintian/data/spelling/corrections is incorrect:

calulations|calculations

should be (notice the missing pipe)

calulations||calculations

Given that this is a really trivial fix I'm not including a patch.

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

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

Versions of packages lintian depends on:
ii  binutils  2.27.51.20161108-1
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.29-1
ii  gettext   0.19.8.1-1
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.30
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b1
ii  libdigest-sha-perl5.96-1+b1
ii  libdpkg-perl  1.18.15
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libparse-debianchangelog-perl 1.2.0-11
ii  libperl5.22 [libdigest-sha-perl]  5.22.2-5
ii  libperl5.24 [libdigest-sha-perl]  5.24.1~rc3-3
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.63-1+b1
ii  man-db2.7.5-1
ii  patchutils0.3.4-2
ii  perl  5.24.1~rc3-3
ii  t1utils   1.39-2
ii  xz-utils  5.2.2-1.2

Versions of packages lintian recommends:
ii  dpkg 1.18.15
ii  libautodie-perl  2.29-2
ii  libperlio-gzip-perl  0.19-1+b2
ii  perl 5.24.1~rc3-3
ii  perl-modules-5.22 [libautodie-perl]  5.22.2-5
ii  perl-modules-5.24 [libautodie-perl]  5.24.1~rc3-3

Versions of packages lintian suggests:
ii  binutils-multiarch 2.27.51.20161108-1
ii  dpkg-dev   1.18.15
ii  libhtml-parser-perl3.72-2+b1
pn  libtext-template-perl  

-- no debconf information

Bug#842520: RFS: glances/2.7.1.1-1

[Daniel Echeverry]

Hi Gianfranco!

2016-10-31 11:56 GMT-05:00 Gianfranco Costamagna
:
> control: owner -1 !
> control: tags -1 moreinfo
>
> Hi,
>
>>I am looking for a sponsor for my package "glances"
>
>
> missing licenses and copyrights:
> e.g.
>
> +++ glances-2.7.1.1/.ci/appveyor/install.ps12016-09-18 21:06:28.0 
> +0200
> @@ -0,0 +1,85 @@
> +# Sample script to install Python and pip under Windows
> +# Authors: Olivier Grisel and Kyle Kastner
> +# License: CC0 1.0 Universal: 
> http://creativecommons.org/publicdomain/zero/1.0/
>
>

Fixed!

> + * @license AngularJS v1.5.8
> + * (c) 2010-2016 Google, Inc. http://angularjs.org
> + * License: MIT
> + */
>
>
> + * @license
> + * lodash 
> + * Copyright jQuery Foundation and other contributors 
> + * Released under MIT license 
> + * Based on Underscore.js 1.8.3 
> + * Copyright Jeremy Ashkenas, DocumentCloud and Investigative Reporters & 
> Editors
>
>
> seems that they haven't been removed, but became embedded code copies,
> so your debian/*.link removals is probably wrong
>
>

Fixed!

> 2) outdated copyright years
>
> - * Copyright 2012-2015 The Dojo Foundation 
> - * Copyright 2009-2015 Jeremy Ashkenas, DocumentCloud and Investigative 
> Reporters & Editors
> + * Copyright 2011-2015 Twitter, Inc.
> + * Copyright 2011-2015 Twitter, Inc.
> + * Copyright jQuery Foundation and other contributors 
> + * Copyright Jeremy Ashkenas, DocumentCloud and Investigative Reporters & 
> Editors
>
> +# Copyright (C) 2015 Angelo Poerio 
>
> Copyright: 2011-2015 Twitter, Inc
>
>
>
> and so on
>
> G.

Fixed!

Could you check it out again?
https://anonscm.debian.org/cgit/collab-maint/glances.git

Really, thank you very much!

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
http://rinconinformatico.net
Linux user: #477840
Debian user

Bug#846977: [Pkg-xfce-devel] Bug#846977: thunar: thumbnail for rotated jpeg appears as unrotated

[Mike Kupfer]

Yves-Alexis Perez wrote:

> So you have a jpeg file /path/to/file.jpg, you open /path/to with Thunar and
> the thumbnail is generated. Then you open the file in Shotwell, rotate it,
> then save the rotated file in /path/to/other/file.jpg. Then when you open
> /path/to/other in Thunar the thumbnail is already there and is not rotated.

No, the image was imported directly from the camera to Shotwell on a
Jessie system.  I'm afraid I don't remember how I got the image out of
Shotwell.

Hmm.  If I look at the directory in Shotwell's storage area using any of
Thunar, Nautilus, or Caja, the file appears unrotated (landscape
orientation).  It has an md5sum of

  306c0a274435016922cea2f3c1898819

and jpegexiforient says it has an Exif Orientation Tag of 1.

Maybe I rotated the file outside Shotwell (e.g., using Eye of GNOME or
Eye of MATE).  But I think that trying to figure out how I produced the
image is a distraction.

I have a copy of the sample file (message #10 of the bug report) in a
separate folder, on both the Jessie system and the Stretch VM that I
submitted the bug from.  The md5sum for this file is

  5445cbb90960a93259db3b7045cdaf77

and jpegexiforient says it has an orientation of 8.

On Jessie:

If I open that folder using Caja or Nautilus, the sample file appears
rotated.  If I open the same folder using Thunar, it appears unrotated.
(I can have both Caja and Thunar open at the same time; Caja shows the
image rotated, Thunar shows it unrotated.)

If I open the sample file using GIMP, I get a popup saying that the exif
data says the image should be rotated and do I want to do that.  If I
click on Rotate, I get the rotated image.  If I dismiss the popup, I get
the unrotated image.  So perhaps with Thunar the exif data is getting
ignored when the thumbnail is generated.

On Stretch:

It depends on which program I run first.  If I delete the cached
thumbnails and then view the folder using Caja, both Caja and Thunar
show the image as rotated.  If I clear the thumbnail cache again and
then view the folder using Thunar, both Caja and Thunar show the image
as unrotated.  (I guess with Stretch they share the same thumbnail
cache?)

I hope this gives you the information you were looking for.  If not, let
me know what I missed and I'll try again.

cheers,
mike

Bug#826910: libpam-modules: pam_open_session() causes libasan to report a memory leak

[Nye Liu]

Now that I am using systemd, it moved to pam_systemd

If I preload pam_systemd.so it goes away:

LD_PRELOAD=libasan.so.3:/lib/x86_64-linux-gnu/security/pam_systemd.so ./pamtest


With it:

...
7f6c521a5000-7f6c521a6000 ---p 0004 00:14 102797 
/lib/x86_64-linux-gnu/security/pam_systemd.so
7f6c521a6000-7f6c521a9000 r--p 0004 00:14 102797 
/lib/x86_64-linux-gnu/security/pam_systemd.so
7f6c521a9000-7f6c521aa000 rw-p 00043000 00:14 102797 
/lib/x86_64-linux-gnu/security/pam_systemd.so
...

=
==26908==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 4096 byte(s) in 1 object(s) allocated from:
#0 0x7f6c51104d28 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28)
#1 0x7f6c52178b21  ()


Note that 0x7f6c52178b21 is now in pam_systemd.so

Bug#847313: network-manager-openconnect: nmcli connect doesn't work with --ask but works with nm-applet running

[Mike Miller]

On Wed, Dec 07, 2016 at 10:54:10 +0200, Matti Koskimies wrote:
> I have a OpenConnect VPN connection and I like to use nmcli to connect to it.
> But I can't do that unless nm-applet is running. When I use the --ask option I
> get a connection to the authentication, but it fails every time. After I start
> nm-applet I get a GUI asking for credentials, and the connection is
> established.

I can't reproduce this, but that doesn't mean it's not a bug in some
component. I would suspect this is network-manager itself rather than
the nm-openconnect component. Can you test with another VPN type?

> $ nmcli --ask connection up HaVaVPN
> POST https://*hostname removed*/restricted
> Connected to *IP removed*:443
> SSL negotiation with *hostname removed*
> Connected to HTTPS on *hostname removed*
> XML POST enabled
> Please enter your username and password.
> Username:*username removed*
> Password:
> POST https://*hostname removed*/
> Error: Connection activation failed: unknown reason.

What is the timing in this example? A couple seconds? Is it just a
simple user + password login?

Does connecting with openconnect directly work?

Here's what I see in a completely headless environment:

  $ nmcli --ask con up test
  POST https://example.com/
  Connected to [...]:443
  SSL negotiation with example.com
  Server certificate verify failed: signer not found

  Certificate from VPN server "example.com" failed verification.
  Reason: signer not found
  Enter 'yes' to accept, 'no' to abort; anything else to view: yes
  Connected to HTTPS on example.com
  XML POST enabled
  Please enter your username.
  Username:user
  POST https://example.com/auth
  Please enter your password.
  Password:
  POST https://example.com/auth
  VPN connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/33)

-- 
mike

Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

[Johannes Schauer]

Hi,

On Thu, 08 Dec 2016 04:12:57 +0100 Johannes Schauer  wrote:
> When I now enter my gitlab instance I only get a 502 error with the message
> "Whoops, GitLab is taking too much time to respond".
> 
> Since the last time I changed the version of a ruby package you told me
> to run assets:precompile, I ran the following command:
> 
> runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat 
> /etc/gitlab/gitlab-debian.conf) && rake assets:precompile 
> RAILS_ENV=production'
> Could not find grape-entity-0.5.1 in any of the sources
> Run `bundle install` to install missing gems.
> 
> Given the error above, I suspect that the new ruby-grape-entity version
> is the culprit here.

in the hopes that the gitlab postinst maintainer script would contain something
that fixes this problem, I ran "apt-get install --reinstall gitlab" with the
following result:

Verifying we have all required libraries...
Could not find gem 'grape-entity (~> 0.5.0)' in any of the gem sources listed in
your Gemfile or available on this machine.
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 7
Processing triggers for systemd (232-7) ...
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)



Thanks!

cheers, josch


signature.asc
Description: signature

Bug#847421: gitlab should precompile assets itself if relevant dependencies change

[Johannes Schauer]

Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: important

Hi,

in #846916 you advised me to run "rake assets:precompile" after I
upgraded my version of ruby-jquery-rails. This really should not be
necessary and the gitlab package should do this itself if any relevant
package versions get upgraded/changed. I could for example imagine that
you could use dpkg triggers to run the required gitlab tasks.

Thanks!

cheers, josch

Bug#794438: Partition manager does not launch

[Boyuan Yang]

Hello,

Ping everyone,

Partition Manager will miss Stretch if we do not solve this problem (#794438), 
which would be a great pity.

Anyone would like to work on this issue and solve the problem? Maybe we can 
port the new version from Ubuntu to greatly reduce the efforts.

--
Sincerely,
Boyuan Yang

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

Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

[Johannes Schauer]

Package: gitlab
Version: 8.13.3+dfsg1-2
Severity: grave
Justification: renders package unusable

Hi,

sorry for reporting another RC bug.

Because you were so quick in fixing #846916, I just upgraded my gitlab
chroot. Here are the relevant lines from my "apt-get upgrade" run
(showing all the package versions):

The following packages will be upgraded:
  bundler libjs-jquery-ui libruby2.3 libsqlite3-0 libsystemd0 libudev1 
libustr-1.0-1 msmtp msmtp-mta ruby-bundler ruby-grape-entity ruby-molinillo 
ruby-rubypants ruby-temple ruby-thor ruby2.3 systemd systemd-sysv
18 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 7535 kB of archives.
After this operation, 169 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 systemd amd64 
232-7 [2452 kB]
Get:2 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libsystemd0 
amd64 232-7 [273 kB]
Get:3 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 systemd-sysv 
amd64 232-7 [74.6 kB]
Get:4 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libudev1 amd64 
232-7 [118 kB]
Get:5 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libustr-1.0-1 
amd64 1.0.4-6 [76.3 kB]
Get:6 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libsqlite3-0 
amd64 3.15.2-1 [568 kB]
Get:7 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-molinillo 
all 0.5.0-2 [15.1 kB]
Get:8 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-thor all 
0.19.1-3 [46.5 kB]
Get:9 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 bundler all 
1.12.5-4 [35.5 kB]
Get:10 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-bundler 
all 1.12.5-4 [160 kB]
Get:11 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 
libjs-jquery-ui all 1.12.1+dfsg-2 [227 kB]
Get:12 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 
ruby-grape-entity all 0.6.0-1 [24.5 kB]
Get:13 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 
ruby-rubypants all 0.6.0-1 [9232 B]
Get:14 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby-temple 
all 0.7.7-1 [29.7 kB]
Get:15 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 libruby2.3 
amd64 2.3.3-1 [3104 kB]
Get:16 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 msmtp amd64 
1.6.6-1 [120 kB]
Get:17 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 msmtp-mta all 
1.6.6-1 [15.2 kB]
Get:18 http://ftp.iut-bm.univ-fcomte.fr/debian stretch/main amd64 ruby2.3 amd64 
2.3.3-1 [186 kB]


When I now enter my gitlab instance I only get a 502 error with the
message "Whoops, GitLab is taking too much time to respond".

Since the last time I changed the version of a ruby package you told me
to run assets:precompile, I ran the following command:

runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat 
/etc/gitlab/gitlab-debian.conf) && rake assets:precompile RAILS_ENV=production'
Could not find grape-entity-0.5.1 in any of the sources
Run `bundle install` to install missing gems.

Given the error above, I suspect that the new ruby-grape-entity version
is the culprit here.

Thanks!

cheers, josch

Bug#823547: clearlooks-phenix-theme: The mecurial vcs listed in the package is not up to date with the latest debian-sources

[Daniel Reurich]

It looks like it may be coming from ubuntu:
https://launchpad.net/ubuntu/+source/clearlooks-phenix-theme/6.0.3-1



On Thu, 05 May 2016 20:48:09 + Daniel Reurich 
 wrote:

Package: clearlooks-phenix-theme
Version: 6.0.3-1
Severity: normal



-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 1.0 (jessie)
Release:1.0
Codename:   jessie
Architecture: i686

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)




--
Daniel Reurich
Centurion Computer Technology (2005) Ltd.
021 797 722

Bug#847419: apt-listchanges: crashes with AttributeError: 'str' object has no attribute 'decode'

[David Starner]

Package: apt-listchanges
Version: 3.6
Severity: important

Dear Maintainer,

Apt upgrade leads to

Traceback (most recent call last):
  File "/usr/bin/apt-listchanges", line 243, in 
main(config)
  File "/usr/bin/apt-listchanges", line 141, in main
(news, changelog, binnmu) = pkg.extract_changes(config.which, fromversion, 
config.reverse)
  File "/usr/share/apt-listchanges/DebianFiles.py", line 246, in extract_changes
changelog  = reduce(find_first, changelog_filenames + 
changelog_filenames_native, None)
  File "/usr/share/apt-listchanges/DebianFiles.py", line 243, in 
find_first = lambda acc, fname: acc or 
self._read_changelog(os.path.join(tempdir, fname), since_version, reverse)
  File "/usr/share/apt-listchanges/DebianFiles.py", line 295, in _read_changelog
entries, urgency = ChangelogParser().parse(fd, since_version)
  File "/usr/share/apt-listchanges/DebianFiles.py", line 160, in parse
line = line.decode('utf-8', 'replace')
AttributeError: 'str' object has no attribute 'decode'
apt-listchanges: Do you want to continue? [Y/n] n

There doesn't seem to be any way around this.

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

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

Versions of packages apt-listchanges depends on:
ii  apt1.4~beta1
ii  debconf [debconf-2.0]  1.5.59
ii  debianutils4.8.1
ii  python3-apt1.1.0~beta5
pn  python3:any
ii  ucf3.0036

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chromium [www-browser] 55.0.2883.75-1
ii  exim4-daemon-light [mail-transport-agent]  4.88~RC5-1
ii  firefox-esr [www-browser]  45.5.1esr-1
ii  konqueror [www-browser]4:16.08.3-1
ii  konsole [x-terminal-emulator]  4:16.08.3-1
ii  kterm [x-terminal-emulator]6.2.0-46.2
ii  lxterminal [x-terminal-emulator]   0.2.0-1
ii  lynx [www-browser] 2.8.9dev11-1
ii  python3-gi 3.22.0-1
ii  w3m [www-browser]  0.5.3-33
ii  xterm [x-terminal-emulator]327-1

-- debconf information:
* apt-listchanges/confirm: true
* apt-listchanges/frontend: pager
* apt-listchanges/save-seen: true
* apt-listchanges/email-address: root
* apt-listchanges/which: both

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Hutchings]

On Thu, 2016-12-08 at 15:34 +1300, Ben Caradoc-Davies wrote:
> On 08/12/16 15:21, Ben Hutchings wrote:
> > Doesn't apt-listbugs see bugs that 'affect' a package?
> 
> I do not know. Does "affects" provide the version information that 
> apt-listbugs needs to filter bugs?

I don't think there's any way to specify which versions of the affected
package are affected.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



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

Bug#840424: RFS: verilog-mode

[Kiwamu Okabe]

Hi Gianfranco,

On Thu, Dec 8, 2016 at 11:10 AM, Sean Whitton  wrote:
> You don't need to: just provide Gianfranco with a tarball to upload, or
> tell him how to produce it from your git repository.

Thanks for your advice.
Could you upload my package with following? > Gianfranco

https://mentors.debian.net/package/verilog-mode

Best regards,
-- 
Kiwamu Okabe at METASEPI DESIGN

Bug#846382: display artifacts in Blender

[ian_bruce]

I confirm this bug. It's extremely easy to reproduce; simply moving the
mouse pointer across any of the controls is sufficient to trigger
flickering and display corruption. This program is currently unusable.

I, too, have Mesa v13 installed. Whatever the cause of the problem is,
it's of very recent origin. However, it has been the case for a long
time that using the "Toggle Window Fullscreen" option from the "Window"
menu (as opposed to the window manager "maximize" button) causes similar
problems.

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Caradoc-Davies]

On 08/12/16 15:21, Ben Hutchings wrote:

Doesn't apt-listbugs see bugs that 'affect' a package?


I do not know. Does "affects" provide the version information that 
apt-listbugs needs to filter bugs?



(2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
0.125)" which it will need even after #847340 is fixed.

I won't add that Breaks line because:
- Only the combination of the new firmware-misc-nonfree *and* plymouth
  breaks with the unfixed initramfs-tools
- jessie and jessie-backports will never have a version of initramfs-
  tools that satisfies that
- jessie can get a fix for this in a stable update


Yes, that sounds fine to me. The Breaks: I wrote is too broad and this 
will all come out in the wash on unstable.



I agree we need to stop this version of firmware-nonfree going into
testing before initramfs-tools is fixed, so I'm assigning this bug
back.


Thanks very much.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Olly Betts]

On Thu, Dec 08, 2016 at 02:59:54AM +0100, Vincent Lefevre wrote:
> On 2016-12-08 00:22:51 +, Olly Betts wrote:
> > As for the proposed patch, I'm not wild about just removing this warning - 
> > the
> > current patch we're applying downgrades the fatal error to a warning so that
> > there's a hint as to what's going on if there are problems caused by the
> > compler ABI change.  Remove that will make it much harder to debug any
> > such cases, and risks annoying wx upstream with bug reports.  If people
> > are finding the current wording too scary, we could reword it.
> 
> The terminal is not there to output debug messages (unless explicitly
> requested by the user). Such messages are distracting the user.

It's not a debug message, it's a warning message.

> In any case, if you fear that the ABI change may break something,
> you should rebuild the packages.

I don't fear it will break something, but I worry that if it did break
something it would be much harder for people to work out what's going on.

A binNMU for wxwidgets3.0 is OK by me - the point I was trying to make in
#844526 is that it's not helpful to just binNMU wxwidgets3.0 - you also
need to binNMU any rdeps which haven't yet been rebuilt with the newer
compiler ABI - otherwise you're just moving the warnings to different
packages.

Cheers,
Olly

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Hutchings]

Control: unmerge -1
Control: reassign -1 firmware-misc-nonfree 20161130-1

On Thu, 2016-12-08 at 14:33 +1300, Ben Caradoc-Davies wrote:
> Ben,
> 
> you reassigned this bug to initramfs-tools and removed the version. As 
> detailed in #847343, I wanted to keep this bug on firmware-misc-nonfree 
> because:
> 
> (1) it protects apt-listbugs users from upgrading firmware-misc-nonfree 
> and being hit by #847340, and

Doesn't apt-listbugs see bugs that 'affect' a package?

> (2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
> 0.125)" which it will need even after #847340 is fixed.

I won't add that Breaks line because:
- Only the combination of the new firmware-misc-nonfree *and* plymouth
  breaks with the unfixed initramfs-tools
- jessie and jessie-backports will never have a version of initramfs-
  tools that satisfies that
- jessie can get a fix for this in a stable update

> If you are sure that you want this bug on initramfs-tools, I will defer 
> to your expertise, but I do not see how this addresses my points above.

I agree we need to stop this version of firmware-nonfree going into
testing before initramfs-tools is fixed, so I'm assigning this bug
back.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


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

Bug#844184: RFS: muse-el/3.20+dfsg-1 [ITA]

[Nicholas D Steeves]

Dear Sean,

Thank you once again for holding me to high standards and for taking
the time to point out what needs work!

1-to-5, and 8: done
>
> 6. In d/NEWS,
> 
> > Unfortunately, it is not possible to distribute this manual with the
> > muse-el Debian package because the Debian project has chosen to remove
> > most GFDL'd documentation.
> 
> Wouldn't you say the unfortunate thing is that the manual has not been
> relicensed under a DFSG-compatible license? ;)

Yes, I agree :-) however, I didn't write that part of d/NEWS and only
made in-line updates to paths.  Originally I had added a message at
the top which essentially said "in your head, do s/this/that/ -e s/and
this/with this/ -e s/and don't forget/this either/".  It seemed
clumsy, so I decided to merge it and put the originally author's name
unambiguously right at the top.

> 7. I'm pretty sure you shouldn't compress
> /usr/share/doc/elpa-muse/QuickStart.pdf.  It might break doc-base
> clients, and in any case, I doubt that gzip compression is very good for
> PDFs.

That you for reminding me to fix this; my mental TODO list dropped
this item!  On that topic, should examples/* be ready to copy into
place and use, or is ok to let dh_examples compress those? (related to
the answer to 10.)

> 9. There is still a lot of Lintian output.  Please make the package
> Lintian clean.  Please ensure you turn on experimental and informational
> tags:
> 
> I: muse-el source: binary-control-field-duplicates-source field 
> "priority" in package muse-el
> E: muse-el source: license-problem-gfdl-invariants README invariant part 
> is: with no invariant sections, and with the front-cover texts and back-cover 
> texts as specified in the manual
> I: muse-el source: debian-watch-file-is-missing
> I: elpa-muse: debian-news-entry-uses-asterisk
> X: elpa-muse: privacy-breach-generic 
> usr/share/doc/elpa-muse/examples/mwolson/templates/generic-header.html 
> (http://www.mwolson.org/web/aboutme.html)
> X: elpa-muse: privacy-breach-generic 
> usr/share/doc/elpa-muse/examples/mwolson/templates/header.html 
> (http://blog.mwolson.org/index.rss)
> X: elpa-muse: privacy-breach-generic 
> usr/share/doc/elpa-muse/examples/mwolson/templates/header.html 
> (http://mwolson.org/web/aboutme.html)
> X: elpa-muse: privacy-breach-generic ... use --no-tag-display-limit to 
> see all (or pipe to a file/program)
> I: muse-el: debian-news-entry-uses-asterisk
> I: muse-el: description-synopsis-might-not-be-phrased-properly

E: muse-el source: license-problem-gfdl-invariants README is, to the
best of my knowledge bogus, because that documentation is stripped
from our orig.tarball.  I believe it's ok to leave the README
unpatched, but I might be wrong about this.

I've contacted Michael Olson about the possibility of providing an
examples/mwolson tarball on his website, because as I see it the
external links are an integral part of the Muse-managed website
example.  Specifically, I believe the intent of the example is to
provide a copy of a website that is browsable online so that the user
can explore both the source layout of a Muse-managed project and
browse the result.  In the meantime, I've added an override; if that
override is unacceptable, please let me know.  If we can keep the
override, I'd be happy to notify users--with NEWS--of the potential
privacy breach.

> 10. How are the *.py files meant to be used?  Are they supposed to be
> copied into a pyblosxom installation, or run directly from where they
> are installed?  If the latter, they should be bytecompiled and installed
> into /usr/share/elpa-muse/contrib.  If the former, they are fine as they are.

By reading the following from getstamps.py:

Run 'python getstamps.py' from the directory that contains your
unpublished blog entries.

You may need to make some modification for your situation. This
assumes your blog entries use a .txt extension and that you generate
them from "source" files in a different directory (with an optional
.muse extension).

It would seem that these are intended to be used in the following
manner: user reads the headers of these contributed python programs,
then adapts them to his/her needs, then copies them to the blog
project dir (eg: ~/my_blog).  Previous versions of src:muse-el
installed these contributed programs to
/usr/share/doc/muse-el/contrib.  According to this precedent and the
intended usage described in the programs header, I believe that the
current location is correct.  Alternatively, these files might exist
primarily as examples of how to configure upstream pyblosxom for use
with Muse; if this is the case, then they belong in /usr/share/doc.

> 11. I've now reviewed d/copyright.  Unfortunately, you can't claim that
> the debian/ directory is GPL-3+ without contacting each of the authors
> you name and confirming they are happy to release their contributors
> under that license, since it was not explicitly stated.  What happens 

Bug#847418: depends on gstreamer-plugins-bad, which is an ongoing source of security holes

[Joey Hess]

Package: libfarstream-0.2-5
Version: 0.2.8-1
Severity: normal

gstreamer-plugins-bad has been in the news at least twice recently for
security holes.

http://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-compromising-linux-desktop.html
https://scarybeastsecurity.blogspot.dk/2016/11/0day-poc-risky-design-decisions-in.html

It seems likely that it will continue to be a source of such security
holes.

I wanted to remove gstreamer-plugins-bad from my system, but this would
remove libfarstream-0.2-5, which would remove pidgin.

I doubt that pidgin needs a ton of insecurely implemented codecs for
playing Nintendo games etc in order to do video/audio chat. Could this
dependency please be lessened to a Suggests? Or even better, don't
depend on codecs from a library package; let the packages for programs
that actually need to codecs depend on the codec packages.

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

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

Versions of packages libfarstream-0.2-5 depends on:
ii  gstreamer1.0-nice   0.1.13-2
ii  gstreamer1.0-plugins-bad1.10.0-1
ii  gstreamer1.0-plugins-base   1.10.0-1
ii  gstreamer1.0-plugins-good   1.10.0-1
ii  libc6   2.24-5
ii  libglib2.0-02.50.2-1
ii  libgstreamer-plugins-base1.0-0  1.10.0-1
ii  libgstreamer1.0-0   1.10.0-2
ii  libgupnp-1.0-4  1.0.1-1
ii  libgupnp-igd-1.0-4  0.2.4-1
ii  libnice10   0.1.13-2

libfarstream-0.2-5 recommends no packages.

libfarstream-0.2-5 suggests no packages.

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#847325: Unable to copy symlinks with copy_file

[Ben Hutchings]

On Wed, 2016-12-07 at 11:46 +0100, Vincent Bernat wrote:
[...]
> I have this error on update-initramfs -u -vv:
> 
> Adding firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin
> Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin
> Adding firmware /usr/lib/firmware/nvidia/gm200/gr/gpccs_inst.bin
> Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
> Removing /boot/initrd.img-4.8.0-2-amd64.dpkg-bak
> update-initramfs: failed for /boot/initrd.img-4.8.0-2-amd64 with 1.
> 
> I have traced to this:
> 
> + copy_file firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + local type src target link_target
> + type=firmware
> + src=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + target=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + [ -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
> + [ -d /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin 
> ]
> + [ -e /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin 
> ]
> + mkdir -p /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr
> + [ -h /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
> + readlink -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + link_target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
> + [ /usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin != 
> /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
> + [ y = y ]
> + echo Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + ln -rs 
> /var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin 
> /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + src=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
> + target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
> + [ -e 
> /var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin ]
> + return 1
> 
> Maybe the check should also use cmp.

It should not.  copy_file is documented to return 1 in case the target
already exists, and some of its callers rely on that to skip looking at
the file's dependencies.

If copy_file copies a symlink, it then moves on to copying the link-
target.  It also returns 1 if that already exists in the initramfs, but
this is not obvious from the documentation.  It seems to make more
sense to return 0 in this case and reserve 1 for the case that nothing 
at all was copied.

(Annoyingly, I couldn't reproduce this at first because I tried just
adding nouveau to /etc/initramfs-tools/modules.  Since mkinitramfs does
*not* use 'set -e' (unlike most hooks), the 'failure' of copy_file was
not fatal.)

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



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

Bug#840424: RFS: verilog-mode

[Sean Whitton]

Dear Kiwamu,

On Thu, Dec 08, 2016 at 10:22:00AM +0900, Kiwamu Okabe wrote:
> Could you advice me how to use the command in this situation?

You don't need to: just provide Gianfranco with a tarball to upload, or
tell him how to produce it from your git repository.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#847417: depends on gstreamer-plugins-bad, which is an ongoing source of security holes

[Joey Hess]

Package: gnome-video-effects
Version: 0.4.1-3
Severity: normal

gstreamer-plugins-bad has been in the news at least twice recently for
security holes. 

http://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-compromising-linux-desktop.html
https://scarybeastsecurity.blogspot.dk/2016/11/0day-poc-risky-design-decisions-in.html

It seems likely that it will continue to be a source of such security
holes.

I wanted to remove gstreamer-plugins-bad from my system, but this would
remove gnome-video-effects, which would remove cheese. I don't know why
cheese needs a ton of insecurely implemented codecs for playing Nintendo
games etc in order to take snapshots and record videos. Probably it doesn't?

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

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

Versions of packages gnome-video-effects depends on:
ii  gstreamer1.0-plugins-bad   1.10.0-1
ii  gstreamer1.0-plugins-good  1.10.0-1

gnome-video-effects recommends no packages.

Versions of packages gnome-video-effects suggests:
pn  gnome-video-effects-frei0r  

-- no debconf information

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Vincent Lefevre]

On 2016-12-08 00:22:51 +, Olly Betts wrote:
> As for the proposed patch, I'm not wild about just removing this warning - the
> current patch we're applying downgrades the fatal error to a warning so that
> there's a hint as to what's going on if there are problems caused by the
> compler ABI change.  Remove that will make it much harder to debug any
> such cases, and risks annoying wx upstream with bug reports.  If people
> are finding the current wording too scary, we could reword it.

The terminal is not there to output debug messages (unless explicitly
requested by the user). Such messages are distracting the user.

In any case, if you fear that the ABI change may break something,
you should rebuild the packages.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#832074: networking.service: Start operation timed out

[Brian Embry]

I believe I have reproduced this bug on my system (system would hang
for 5 mins waiting for DHCP address).  If I manually ran dhclient
after the system cam up it would work fine.

I first saw this issue after upgrading systemd to 230-7~bpo8+2,
ifupdown to 0.8.13~bpo8+1 and udev  230-7~bpo8+2f rom
jessie-backports.

My topology is dhcp on a bridge with eth0, and tap0, and a network
namespace interface. The system would boot fine if I didn't rely on
DHCP for addressing of br0.

$ journalctl -u networking
Dec 01 19:46:26 server dhclient[3951]: Listening on LPF/br0/00:1d:7d:02:3c:4d
Dec 01 19:46:26 server ifup[3779]: Listening on LPF/br0/00:1d:7d:02:3c:4d
Dec 01 19:46:26 server ifup[3779]: Sending on   LPF/br0/00:1d:7d:02:3c:4d
Dec 01 19:46:26 server ifup[3779]: Sending on   Socket/fallback
Dec 01 19:46:26 server ifup[3779]: DHCPREQUEST on br0 to 255.255.255.255 port 67
Dec 01 19:46:26 server dhclient[3951]: Sending on   LPF/br0/00:1d:7d:02:3c:4d
Dec 01 19:46:26 server dhclient[3951]: Sending on   Socket/fallback
Dec 01 19:46:26 server dhclient[3951]: DHCPREQUEST on br0 to
255.255.255.255 port 67
Dec 01 19:46:26 server dhclient[3951]: DHCPACK from 192.168.0.1
Dec 01 19:46:26 server ifup[3779]: DHCPACK from 192.168.0.1
Dec 01 19:51:26 server systemd[1]: networking.service: Start operation
timed out. Terminating.
Dec 01 19:51:26 server systemd[1]: Failed to start Raise network interfaces.
Dec 01 19:51:26 server systemd[1]: networking.service: Unit entered
failed state.
Dec 01 19:51:26 server systemd[1]: networking.service: Failed with
result 'timeout'.

I was able to fix it by downgrading udev, systemd and ifupdown to jessie.

--Brian

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Caradoc-Davies]

Ben,

you reassigned this bug to initramfs-tools and removed the version. As 
detailed in #847343, I wanted to keep this bug on firmware-misc-nonfree 
because:


(1) it protects apt-listbugs users from upgrading firmware-misc-nonfree 
and being hit by #847340, and


(2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
0.125)" which it will need even after #847340 is fixed.

If you are sure that you want this bug on initramfs-tools, I will defer 
to your expertise, but I do not see how this addresses my points above.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#840424: RFS: verilog-mode

[Kiwamu Okabe]

Hi all,

On Thu, Dec 8, 2016 at 9:07 AM, Sean Whitton  wrote:
>> verilog-mode (master) $ gbp buildpackage -S -d
>> gbp:warning: Pristine-tar branch "pristine-tar" not found
>> gbp:error: Pristine-tar couldn't checkout 
>> "verilog-mode_20161124.fd230e6.orig.tar.gz": pristine-tar: no pristine-tar 
>> branch found, use "pristine-tar commit" first
>
> For my review, I generated one using git-archive(1).  There is no
> upstream tarball release aside from the tarballs github generates.
> Kiwamu: what would you prefer?

Sorry, I do not understand pristine-tar command. And I'm afraid of
breaking my git repo with the command...

Could you advice me how to use the command in this situation? > Gianfranco

Best regards,
-- 
Kiwamu Okabe at METASEPI DESIGN

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Caradoc-Davies]

Grave severity is not justified because this package works fine if 
plymouth is not installed. I have set the severity to serious because 
firmware-misc-nonfree does not declare Breaks: initramfs-tools (<= 
0.125). I expect that adding this relationship is the cleanest way to 
ensure working upgrades.


Serious severity still meets my goal of warning apt-listbugs users, 
because RC bugs are reported by default.


I do not know if it is possible to include a conditional in a Breaks: 
(something like "and plymouth installed"). In any case, this is now a 
bona fide firmware-misc-nonfree bug.  :-)


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#847416: Updating the fishpoll Uploaders list

[Mattia Rizzolo]

Source: fishpoll
Version: 0.1.7-1
Severity: minor
X-Debbugs-Cc: Andrea Veri 

Andrea Veri  has retired, so can't work on
the fishpoll package anymore (at least with this address).

I would like to ask you to remove them from the Uploaders list of the
package.

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#827976: closed by Mike Gabriel <sunwea...@debian.org> (Bug#827976: fixed in bamf 0.5.3-1~exp1)

[Mattia Rizzolo]

Control: reopen -1

Hi,

reopening this since you actually removed the wrong person :)
see your changelog:

On Mon, Oct 10, 2016 at 10:03:15AM +, Debian Bug Tracking System wrote:
> #827976: Please remove me from Uploaders
> 
> It has been closed by Mike Gabriel .
> 
>* debian/control:
>  + Remove from Uploaders: field: Didier Roche on self-request. (Closes:
>#827976).

But the original bug was from another person:

> Date: Thu, 23 Jun 2016 13:36:39 +0200
> From: Andrea Veri 
> To: sub...@bugs.debian.org
> Subject: Please remove me from Uploaders
> Message-ID: <20160623113639.gl7...@debian.org>
> User-Agent: Mutt/1.5.21 (2010-09-15)
> 
> Package: bamf
> Severity: normal
> 
> Hi,
> 
> I'm currently not interested in being an Uploader for the
> bamf package anymore. Please remove me.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#844486: [Freewx-maint] Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Scott Talbert]

On Thu, 8 Dec 2016, Olly Betts wrote:


#846019 looks to be something different - it's giving a *FATAL* error there
(it's not obvious to me how or why since the two strings seem to match aside
from the ABI and I've not had time to try to reproduce yet), but that means it
would not be helped by the proposed patch, since it's not invoking the warning
case but dropping through to the fatal error code below.


I haven't been able to reproduce the fatal error either.  I wonder if 
perhaps it has some dependency on the user's language settings, as the 
original reporter has LANG=sv_SE.UTF-8.  I tried setting my LANG to 
sv_SE.UTF-8 but still wasn't able to repro, but maybe I didn't do it 
correctly.


Scott

Bug#844486: [Freewx-maint] Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Olly Betts]

On Wed, Dec 07, 2016 at 07:36:42PM -0500, Scott Talbert wrote:
> On Thu, 8 Dec 2016, Olly Betts wrote:
> >#846019 looks to be something different - it's giving a *FATAL* error there
> >(it's not obvious to me how or why since the two strings seem to match aside
> >from the ABI and I've not had time to try to reproduce yet), but that means 
> >it
> >would not be helped by the proposed patch, since it's not invoking the 
> >warning
> >case but dropping through to the fatal error code below.
> 
> I haven't been able to reproduce the fatal error either.  I wonder if
> perhaps it has some dependency on the user's language settings, as the
> original reporter has LANG=sv_SE.UTF-8.  I tried setting my LANG to
> sv_SE.UTF-8 but still wasn't able to repro, but maybe I didn't do it
> correctly.

Hmm, I wonder if the reporter has a non-packaged build of wxWidgets 3.0
installed and that's getting used instead of the Debian package - if
they're running the unpatched upstream code that would explain the fatal
error.

Cheers,
Olly

Bug#846399: RFS: rush/1.8+dfsg-1 -- New upstream's release.

[Mats Erik Andersson]

Onsdag den 7:e december 2016, klockan 23:38, skrev Gianfranco Costamagna detta:
> 
> >> please use a text-version of the signing-key and avoid the 
> >> include-binaries file?
> >
> >Then I need education on the procedure to create a keyring file on the go,
> >since gpgv only handles keyrings, not armoured keyfiles.
> 
> https://wiki.debian.org/debian/watch#Cryptographic_signature_verification
> gpg --keyserver keys.gnupg.net --recv-keys 3602B07F55D0C732
> gpg --armor --export-options export-minimal --export '3602B07F55D0C732' >> 
> debian/upstream/signing-key.asc
> 
> does this work?

There is no problem to fetch the key. The problem is to use it. My present
use case is this

   gpgv --homedir debian/upstream --keyring debian/upstream/signing-key.pgp \
archive.sig archive

You are requesting me to use 'debian/upstream/signing-key.asc', an armoured key
which gpgv is not able to handle to my knowledge. Observe that upstream's source
archive must be repackaged to fulfill DFSG, so the above use of gpgv is located
in the target 'get-orig-source' for verification of the original archive
before proceeding to eliminate the texinfo source, which violates DFSG.

Best regards,
  Mats E Andersson

Bug#846657: [reportbug/master] add python3-requests to python3-reportbug Depends; Closes: #846657

[Sandro Tosi]

tag 846657 pending
tag 846657 pending
thanks

Date:   Wed Dec 7 18:43:15 2016 -0500
Author: Sandro Tosi 
Commit ID: 146e5d1049b714f4439150b0aa307c121336a29f
Commit URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=146e5d1049b714f4439150b0aa307c121336a29f
Patch URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=146e5d1049b714f4439150b0aa307c121336a29f

add python3-requests to python3-reportbug Depends; Closes: #846657

  

Bug#846778: [reportbug/master] dont remove the first character from the filename when calling an external MUA; Closes: #846778

[Sandro Tosi]

tag 846778 pending
tag 846778 pending
thanks

Date:   Wed Dec 7 18:50:49 2016 -0500
Author: Sandro Tosi 
Commit ID: 70c147fb43948a8caaf6853db085b1dbfc2f006e
Commit URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=70c147fb43948a8caaf6853db085b1dbfc2f006e
Patch URL: 
http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=70c147fb43948a8caaf6853db085b1dbfc2f006e

dont remove the first character from the filename when calling an external 
MUA; Closes: #846778

  

Bug#847413: gprolog: Debian changelog uncompressed

[Salvador Abreu]

Hi; I'll take care of it in the next version (which is needed
for other reasons as well...)

thanks for noting,
-s

> On 07 Dec 2016, at 23h26, Aaron M. Ucko  wrote:
> 
> Package: gprolog
> Version: 1.4.5-1
> Severity: serious
> Justification: Policy 12.7
> 
> gprolog now ships its Debian changelog in uncompressed form, a policy
> violation that turns out to reveal a latent bug in apt-listchanges
> (which I'll report in a moment, so I can't cite a number yet).
> 
> Could you please fix that?
> 
> Thanks!
> 
> -- System Information:
> Debian Release: stretch/sid
>  APT prefers testing
>  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, x32
> 
> Kernel: Linux 4.8.0-2-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 gprolog depends on:
> ii  libc6  2.24-7
> 
> gprolog recommends no packages.
> 
> gprolog suggests no packages.
> 
> -- no debconf information



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Olly Betts]

Control: severity -1 minor

On Tue, Dec 06, 2016 at 07:26:17PM +0200, Adrian Bunk wrote:
> Control: reassign 846019 src:wxwidgets3.0
> Control: forcemerge -1 846019
> Control: severity -1 serious
> Control: affects -1 pgadmin3
> 
> After looking at #846019 this appears to be pretty RC.

#846019 looks to be something different - it's giving a *FATAL* error there
(it's not obvious to me how or why since the two strings seem to match aside
from the ABI and I've not had time to try to reproduce yet), but that means it
would not be helped by the proposed patch, since it's not invoking the warning
case but dropping through to the fatal error code below.

I also don't have the time right now to work out how to undo the unhelpful
forcemerge you've just done, so for now I'm just setting the severity back to
the appropriate one for #844486.  If you know how to cleanly revert a
forcemerge, please do.

As for the proposed patch, I'm not wild about just removing this warning - the
current patch we're applying downgrades the fatal error to a warning so that
there's a hint as to what's going on if there are problems caused by the
compler ABI change.  Remove that will make it much harder to debug any
such cases, and risks annoying wx upstream with bug reports.  If people
are finding the current wording too scary, we could reword it.

Cheers,
Olly

Bug#845425: DataSource no longer accessible since jessie security update

[Emmanuel Bourg]

Le 7/12/2016 à 20:16, Arne Nordmark a écrit :

> OK. I first built 7.0.56-3+deb8u5 as distributed, installed, and
> verified that your example works but not my webapp. Then I added the
> loop to validateGlobalResourceAccess() (patch attached), reinstalled
> libtomcat7-java, restarted tomcat7, and verified that both webapps now work.
> 
> Thanks for your patience,

Thanks a lot for the tests Arne. We are basically missing the commit
1763236 [1]  that added the recursion through the classloader hierarchy.
This commit wasn't documented as related to CVE-2016-6797. I'll add it
in the next update. The tomcat8 package is also affected.

Emmanuel Bourg

[1] https://svn.apache.org/r1763236

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

[Guillem Jover]

Hi!

On Wed, 2016-11-30 at 22:00:12 +0100, Kurt Roeckx wrote:
> On Wed, Nov 30, 2016 at 07:55:55PM +, Thorsten Glaser wrote:
> > Kurt Roeckx dixit:
> > >> Unfortunately, I have no idea; 1.1 builds, 1.0 doesn’t.
> > >
> > >But both are actually in installed state now?

> > Yes because I built it in a chroot in which I downgraded dpkg
> > to .10, which led to a completely fine build of openssl1.0
> > with testsuite enabled even.
> > 
> > >And if only 1.0 is affected, I'm not sure why it's assigned to the
> > >openssl source package.
> > 
> > I’m not sure why Guillem reassigned the bug either, considering
> > I cloned it in the first place to have one part in openssl1.0
> > and one in dpkg (or, more likely, gcc-6)…
> 
> So I'm rather confused. I at least see some mention of a log with
> -fPIC before the -specs, and then failing to link because it's not
> build using -fPIC but the specs override that to use -fPIE. So I
> would need to find a way to move the -fPIC after the flags set by
> dpkg.  But I don't actually find any log on buildd.debian.org that
> shows that problem.
> 
> In any case, 1.1 seems to place the -fPIC after the CFLAGS from
> dpkg, so I guess moving it around will fix things.

When using the specs files the order is irrelevant, at least relative
to options vs specs. So moving the flags after the specs should not
change anything, see this example session on amd64:

  ,---
  $ gcc -pie -fPIE -specs=/usr/share/dpkg/no-pie-compile.specs \
-specs=/usr/share/dpkg/no-pie-link.specs -o test test.c
  $ readelf -h test|grep Type
  Type:  DYN (Shared object file)
  $ gcc -specs=/usr/share/dpkg/no-pie-compile.specs \
-specs=/usr/share/dpkg/no-pie-link.specs -pie -fPIE -o test test.c
  $ readelf -h test|grep Type
  Type:  DYN (Shared object file)
  $ gcc -specs=/usr/share/dpkg/no-pie-compile.specs \
-specs=/usr/share/dpkg/no-pie-link.specs  -o test test.c
  $ readelf -h test|grep Type
  Type:  EXEC (Executable file)
  $ gcc -specs=/usr/share/dpkg/no-pie-compile.specs \
-specs=/usr/share/dpkg/no-pie-link.specs \
-specs=/usr/share/dpkg/pie-compile.specs \
-specs=/usr/share/dpkg/pie-link.specs  -o test test.c
  $ readelf -h test|grep Type
  Type:  DYN (Shared object file)
  `---

The actual problem here, is that for whatever reason on x32 and only
x32, the build system is (as I noted in #845193#10) calling link_a.gnu
instead of the link_o.gnu target, which tries to link a static library
composed of PIE objects into a shared library, which makes it fail.

Thanks,
Guillem

Bug#833193: closed by Sean Whitton <spwhit...@spwhitton.name> (Closing inactive ITP RFSs)

[Sean Whitton]

control: reopen -1
control: noowner -1
control: tag -1 -moreinfo

Dear Ben,

Thank you for your renewed interest in this ITP.

The deadline for getting new packages into stretch is fast approaching,
and I won't be able to throughly examine your work until late next week
at the earliest.  For this reason, I'm dropping my ownership of the RFS
bug so that others are not discouraged from getting involved.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#845193: [Pkg-openssl-devel] Bug#845193: dpkg: recent -specs PIE changes break openssl

[Guillem Jover]

On Wed, 2016-11-30 at 19:55:55 +, Thorsten Glaser wrote:
> Kurt Roeckx dixit:
> >And if only 1.0 is affected, I'm not sure why it's assigned to the
> >openssl source package.

It's not.

> I’m not sure why Guillem reassigned the bug either, considering
> I cloned it in the first place to have one part in openssl1.0
> and one in dpkg (or, more likely, gcc-6)…

Yes, and that's why I reassigned one part precisely to openssl1.0 and
not openssl. :)

Thanks,
Guillem

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

[Sascha Steinbiss]

Hi Andreas and Andrew,

to address this problem I have taken a shot at patching Debian’s Artemis to use 
the new htsjdk API, avoiding SAMFileReader and using the SamReaderFactory 
instead. This fixed the FTBFS for me.
I tested BAM file reading by opening MAL1.embl.gz from the test/data directory 
and adding MAL1_8h.bam via ‘File->Read BAM/VCF...'. One of the genes has some 
mapped reads that are indeed shown. Comparing the displayed pile of mapped 
reads to the one shown by the recent Artemis version I have on Mac OS X, the 
result seems to be correct, but given my lack of practical experience with the 
BAM/VCF/‘anything-to-do-with-reads' components of Artemis I can’t say if I 
caught everything.

I also updated the Debian version to 16.0.17, the latest release from Sanger. 
This allowed me to drop a couple of patches that I already merged earlier with 
my part-time-upstream hat on.
For now I have pushed my work into the ’6_0_17’ branch in git and I would like 
to kindly ask for some more testing. I don’t have suitable test data here and 
don’t really feel like an expert to test the right usage patterns. 

Cheers
Sascha

> On 5 Dec 2016, at 15:56, Andrew Page  wrote:
> 
> Hi Andreas,
> Thanks for letting us know.  We are actively trying to hire a Java developer 
> who will take over the maintenance and development of Artemis. So 
> unfortunately it will be at least a few months before we will have anyone in 
> post to work on it.  If you happen to know of anyone looking for a job, 
> please send them our way!
> Regards,
> Andrew
> 
> 
> 
>> On 5 Dec 2016, at 14:40, Andreas Tille  wrote:
>> 
>> Hi,
>> 
>> after uploading htsjdk 2.7.0 Artemis failed to build from source[1].  I
>> relised that the file src/main/java/htsjdk/samtools/SAMFileReader.java
>> was removed from htsjdk source and assumed that this was by accident.
>> However, upstream has dropped this interface intentionally as you can
>> read below.  In issue #767[2] an htsjdk author gives advise to use the
>> new API version.
>> 
>> Kind regards
>> 
>>  Andreas.
>> 
>> 
>> [1] https://bugs.debian.org/846671
>> [2] https://github.com/samtools/htsjdk/issues/767
>> 
>> 
>> - Forwarded message from Daniel Gómez-Sánchez  
>> -
>> 
>> Date: Mon, 05 Dec 2016 06:18:16 -0800
>> From: Daniel Gómez-Sánchez 
>> To: samtools/htsjdk 
>> Cc: Andreas Tille , Author 
>> Subject: Re: [samtools/htsjdk] SAMFileReader vanished in Version 2.7.0 (#767)
>> 
>> The file was removed in #699 because it was deprecated. I guess that either 
>> 1) fastqc/artemis should be updated to use the new API version, or 2) the 
>> classpath for them in Debian should include an older version.
>> 
>> -- 
>> You are receiving this because you authored the thread.
>> Reply to this email directly or view it on GitHub:
>> https://github.com/samtools/htsjdk/issues/767#issuecomment-264864910
>> 
>> - End forwarded message -
>> 
>> -- 
>> http://fam-tille.de
>> 
>> - End forwarded message -
>> 
>> -- 
>> http://fam-tille.de
> 
> 
> 
> -- 
> The Wellcome Trust Sanger Institute is operated by Genome Research 
> Limited, a charity registered in England with number 1021457 and a 
> company registered in England with number 2742969, whose registered 
> office is 215 Euston Road, London, NW1 2BE. 
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging

Bug#840424: RFS: verilog-mode

[Sean Whitton]

Hello,

On Wed, Dec 07, 2016 at 11:46:19PM +, Gianfranco Costamagna wrote:
> verilog-mode (master) $ gbp buildpackage -S -d
> gbp:warning: Pristine-tar branch "pristine-tar" not found
> gbp:error: Pristine-tar couldn't checkout 
> "verilog-mode_20161124.fd230e6.orig.tar.gz": pristine-tar: no pristine-tar 
> branch found, use "pristine-tar commit" first

For my review, I generated one using git-archive(1).  There is no
upstream tarball release aside from the tarballs github generates.
Kiwamu: what would you prefer?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#846711: git-build-recipe: FTBFS: Tests failures

[Guillem Jover]

Hi!

On Wed, 2016-12-07 at 09:14:36 +, Colin Watson wrote:
> On Tue, Dec 06, 2016 at 10:54:21PM -0500, James McCoy wrote:
> > On Tue, Dec 06, 2016 at 10:39:44AM +, Colin Watson wrote:
> > > git-build-recipe doesn't do anything particular to ask debuild to run
> > > lintian here, and it doesn't expect or require a lintian check.  It used
> > > to be that debuild would check whether lintian was in fact installed,
> > > and not run it if it wasn't; indeed, its documentation still says "then
> > > runs lintian on the .changes file created (assuming that lintian is
> > > installed)", thereby claiming that that's still what it does.  But this
> > > was broken in devscripts 58eb4a4a5e006bf9a2589da0ef2f36aa0d81ed8c when
> > > changing debuild to use dpkg-buildpackage --check-command.
> > 
> > Indeed.  In order to fix this, I either need to move running lintian
> > back into debuild or dpkg needs to not error when the check command
> > isn't present.
> 
> I don't understand why.  Wouldn't something like this (untested) be
> sufficient?
> 
> diff --git a/scripts/debuild.pl b/scripts/debuild.pl
> index 639bbac..afbd1dc 100755
> --- a/scripts/debuild.pl
> +++ b/scripts/debuild.pl
> @@ -988,7 +988,7 @@ else {
>  open STDOUT, ">" or fatal "can't reopen stdout: $!";
>  open STDERR, ">" or fatal "can't reopen stderr: $!";
>  
> -if ($run_lintian) {
> +if ($run_lintian and system("command -v lintian >/dev/null 2>&1") == 0) {
>   push(@dpkg_opts, '--check-command=lintian',
>   map { "--check-option=$_" } @lintian_opts);
>  }

Yes, please. I'da rather not change the current behavior in
dpkg-buildpackage, because I think that if the user explicitly asked
to run a command that that does not exist, the correct thing to do is
to fail stating so. :)

Thanks,
Guillem

Bug#847415: easy-rsa fails if its path contains spaces

[Nemo Inis]

Package: easy-rsa
Version: 2.2.2-2
Severity: important

Dear Maintainer,

easy-rsa fails if the path to it (when copied to a user directory as
recommended, or the path created by make-cadir) contains a space.
At the very least, the following scripts aren't space-safe: vars,
whichopensslcnf, build-dh



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

Kernel: Linux 4.7.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 easy-rsa depends on:
ii  openssl  1.1.0c-2

Versions of packages easy-rsa recommends:
pn  opensc  

easy-rsa suggests no packages.

-- no debconf information

Bug#847413: gprolog: Debian changelog uncompressed

[Aaron M. Ucko]

"Aaron M. Ucko"  writes:

> (which I'll report in a moment, so I can't cite a number yet).

FTR, the apt-listchanges bug is #847414.

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

Bug#847414: apt-listchanges: AttributeError on uncompressed changelog

[Aaron M. Ucko]

"Aaron M. Ucko"  writes:

> problem just now with gprolog 1.4.5-1 (bug number pending).

FTR, the gprolog bug wound up with #847413.

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

Bug#840424: RFS: verilog-mode

[Gianfranco Costamagna]

control: owner -1 !
control: tags -1 moreinfo

Hi

>I consider git revision 4ba937fbc958fb5037e65fe351d18f2da8e0b988 ready
>for upload.
>
>Thank you for your patience, Kiwamu.


tarball?
verilog-mode (master) $ gbp buildpackage -S -d
gbp:warning: Pristine-tar branch "pristine-tar" not found
gbp:error: Pristine-tar couldn't checkout 
"verilog-mode_20161124.fd230e6.orig.tar.gz": pristine-tar: no pristine-tar 
branch found, use "pristine-tar commit" first

G.

Bug#846399: RFS: rush/1.8+dfsg-1 -- New upstream's release.

[Gianfranco Costamagna]

Hi


>> please use a text-version of the signing-key and avoid the include-binaries 
>> file?
>
>
>Then I need education on the procedure to create a keyring file on the go,
>since gpgv only handles keyrings, not armoured keyfiles.



https://wiki.debian.org/debian/watch#Cryptographic_signature_verification
gpg --keyserver keys.gnupg.net --recv-keys 3602B07F55D0C732
gpg --armor --export-options export-minimal --export '3602B07F55D0C732' >> 
debian/upstream/signing-key.asc



does this work?
G.

Bug#847414: apt-listchanges: AttributeError on uncompressed changelog

[Aaron M. Ucko]

Package: apt-listchanges
Version: 3.6
Severity: normal

When apt-listchanges encounters a package with an uncompressed Debian
changelog, it proceeds to open the changelog in default (text) mode,
resulting in an AttributeError per the below stack trace.  Such
packages are of course in violation of policy (specifically, section
12.7), but still sometimes appear in practice, and should be easy
enough to accommodate by explicitly specifying binary mode in
DebianFiles._open_changelog_file.  In particular, I encountered this
problem just now with gprolog 1.4.5-1 (bug number pending).

Could you please take a look?

Thanks!

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

Kernel: Linux 4.8.0-2-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 apt-listchanges depends on:
ii  apt 1.4~beta1
ii  cdebconf [debconf-2.0]  0.218
ii  debconf [debconf-2.0]   1.5.59
ii  debianutils 4.8.1
ii  python3-apt 1.1.0~beta5
pn  python3:any 
ii  ucf 3.0036

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chimera2 [www-browser] 2.0a19-8+b3
ii  chromium [www-browser] 53.0.2785.143-1
ii  conkeror [www-browser] 1.0.3-1
ii  dillo [www-browser]3.0.5-3
ii  dwb [www-browser]  20150419git-2+b1
ii  edbrowse [www-browser] 3.6.1-1+b1
ii  elinks [www-browser]   0.12~pre6-12
ii  elvis [www-browser]2.2.0-12
ii  epiphany-browser [www-browser] 3.22.3-1
ii  eterm [x-terminal-emulator]0.9.6-4
ii  evilvte [x-terminal-emulator]  0.5.1-1
ii  exim4-daemon-heavy [mail-transport-agent]  4.88~RC5-1
ii  firefox [www-browser]  50.0.2-1
ii  firefox-esr [www-browser]  45.5.1esr-1
ii  gnome-terminal [x-terminal-emulator]   3.22.1-1
ii  hv3 [www-browser]  3.0~fossil20110109-6
ii  konqueror [www-browser]4:16.08.3-1
ii  konsole [x-terminal-emulator]  4:16.08.2-2
ii  kterm [x-terminal-emulator]6.2.0-46.2
ii  lilyterm [x-terminal-emulator] 0.9.9.4+git20150208.f600c0-4
ii  links [www-browser]2.13-1
ii  links2 [www-browser]   2.13-1
ii  lxterminal [x-terminal-emulator]   0.2.0-1
ii  lynx [www-browser] 2.8.9dev11-1
ii  mate-terminal [x-terminal-emulator]1.16.1-1
ii  midori [www-browser]   0.5.11-ds1-4
ii  mlterm [x-terminal-emulator]   3.5.0-1+b1
ii  mrxvt [x-terminal-emulator]0.5.4-2
ii  netrik [www-browser]   1.16.1-2
ii  netsurf-gtk [www-browser]  3.6-3
ii  pterm [x-terminal-emulator]0.67-2
ii  python3-gi 3.22.0-1
ii  qterminal [x-terminal-emulator]0.7.0-2
ii  qupzilla [www-browser] 1.8.9~dfsg1-3
ii  rekonq [www-browser]   0.9.2-1
ii  roxterm [x-terminal-emulator]  3.3.2-1
ii  rxvt [x-terminal-emulator] 1:2.7.10-7
ii  rxvt-unicode [x-terminal-emulator] 9.22-1+b1
ii  sakura [x-terminal-emulator]   3.3.4-2
ii  stterm [x-terminal-emulator]   0.6-1
ii  surf [www-browser] 0.7-2
ii  terminal.app [x-terminal-emulator] 0.9.8-1+nmu1+b2
ii  terminator [x-terminal-emulator]   1.90-1
ii  termit [x-terminal-emulator]   3.0-1
ii  uzbl [www-browser] 0.0.0~git.20120514-1.2
ii  w3m [www-browser]  0.5.3-33
ii  xemacs21-mule [www-browser]21.4.24-4
ii  xemacs21-nomule [www-browser]  21.4.24-4
ii  xfce4-terminal [x-terminal-emulator]   0.8.1-1
ii  xterm [x-terminal-emulator]327-1
ii  xvt [x-terminal-emulator]  2.1-20.2

-- debconf information excluded

Bug#847412: pyca should not ship files in /var/log

[Lars Bahner]

Duly noted.

8. des. 2016 12.27 a.m. skrev "Stuart Prescott" :

> Package: pyca
> Version: 20031119-0
> Severity: important
>
> Dear Maintainer,
>
> pyca currently ships /var/log/pyca/{ca-certreq-mail.out,httpd_error_log}
> files. The consequence of this is that any time the package is upgraded,
> the logs are lost, which is unacceptable. Note that if pyca is to stop
> shipping these files, it should include a suitable maintainer script
> that ensures that the files are saved prior to the upgrade otherwise
> dpkg will remove them during the upgrade process.
>
> regards
> Stuart
>

Bug#847413: gprolog: Debian changelog uncompressed

[Aaron M. Ucko]

Package: gprolog
Version: 1.4.5-1
Severity: serious
Justification: Policy 12.7

gprolog now ships its Debian changelog in uncompressed form, a policy
violation that turns out to reveal a latent bug in apt-listchanges
(which I'll report in a moment, so I can't cite a number yet).

Could you please fix that?

Thanks!

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

Kernel: Linux 4.8.0-2-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 gprolog depends on:
ii  libc6  2.24-7

gprolog recommends no packages.

gprolog suggests no packages.

-- no debconf information

Bug#847412: pyca should not ship files in /var/log

[Stuart Prescott]

Package: pyca
Version: 20031119-0
Severity: important

Dear Maintainer,

pyca currently ships /var/log/pyca/{ca-certreq-mail.out,httpd_error_log}
files. The consequence of this is that any time the package is upgraded,
the logs are lost, which is unacceptable. Note that if pyca is to stop
shipping these files, it should include a suitable maintainer script
that ensures that the files are saved prior to the upgrade otherwise
dpkg will remove them during the upgrade process.

regards
Stuart

Bug#845750: postfix: Cleanup does not see the postfix-pcre.so.1.0.1 file (and probably others libraries)

[Bartosz Rudnicki]

On 03.12.2016 15:10, Bartosz Rudnicki wrote:

On 30.11.2016 19:30, Bartosz Rudnicki wrote:

On 2016-11-30 01:18, LaMont Jones wrote:

On Sat, Nov 26, 2016 at 01:06:26PM -0500, Scott Kitterman wrote:

On Saturday, November 26, 2016 06:42:13 PM Bartosz Rudnicki wrote:

Yes, there is a tab character after pcre.

I set "chroot" option to "n" for all services in the master.cf and
restarted postfix.

Now, during sending a message, the following messages filling up 
the log

file:

Nov 26 18:11:45 Sirius postfix/cleanup[1723]: error: open
/etc/postfix/pcre/auth_policies: Permission denied

What are the permissions on /etc/postfix/pcre?  That almost looks like
the postfix user is unable to access the directory.

Nov 26 18:11:45 Sirius postfix/cleanup[1723]: warning:
pcre:/etc/postfix/pcre/auth_policies is unavailable. open
/etc/postfix/pcre/auth_policies: Permission denied
Nov 26 18:11:45 Sirius postfix/cleanup[1723]: warning: 42B227212B6:
milter_header_checks map lookup problem -- message not accepted, try
again later

Although I set recursively 777 permissions for /etc/postfix/pcre/
directory, postfix can not reach my pcre map file.

Try 755 -- postfix is picky about world writable directories, iirc.


Did you use postmap [1] to update the map?

pcre maps do not need postmap compilation (nor does postmap accept such
requests.)

The next thing to do would be to add some -v options (3 or 4 of 
them) to
the cleanup line in master.cf and see what it has to spew into the 
logs.


FWIW, pcre maps seem to work just fine for me in 3.1.3-4.

lamont


First of all - I noticed that pcre complications appears only when 
using "milter_header_checks"; After removing this option and 
replacing it with "header_checks" and "mime_header_checks" - 
everything seems to work properly.


So in order to reproduce the situation in another environment, the 
milter application is needed, which has to append additional header 
to the message.


I set the /etc/postfix/pcre directory permissions to 755 and repeated 
attempts both for default master.cf file (default chroot settings) 
and for modified master.cf file, where all commands have "chroot" 
option set to NO.


Results are the same as before:

1) for default master.cf:

http://pastebin.com/raw/ukfF5Zui

2) for modified master.cf (no-chroot):

http://pastebin.com/raw/5CJZU8Ki



I've just figured out that postfix directory had not a execute 
permission for others (711), so cleanup could not read the pcre map 
file. Sorry for my oversight. Now, everything seems to work fine but 
obviously only for the non-chrooted cleanup instance.


Interestingly the "header_checks" and "mime_header_checks" do not need 
"x" permission on /etc/postfix/ directory when cleanup works without 
chroot.




Due to inaccurate description of the reported issue which caused 
misunderstanding, I intend to describe mentioned behaviors once again, 
keeping in mind the specific conditions which MUST be satisfied in order 
to recreate this bug.


By default, the cleanup process works chrooted inside postfix queue 
directory. Maintaining this option untouched, I am able to set 
additional "header_checks" or "mime_header_checks" functionality, by 
adding corresponding options in the main.cf file. For this example I 
used the pcre map type which requires additional package be installed 
(postfix-pcre). After installation required package and indicate testing 
pcre map file (which rejects every input string) in the "header_checks" 
and "mime_header_checks" options, postfix reload is needed. In this case 
everything works properly - received message via smtpd is catched by 
cleanup process and respectively rejected.


The undesirable behavior appears ONLY, when the "milter_header_checks" 
option is used. But for this, a milter application is needed which will 
append additional header. I use OpenDKIM milter which inserts DKIM 
signature to the message. After assign testing pcre map to the 
"milter_header_checks" option and reload postfix, the following entries 
fills up the mail log file causing tempfail in the SMTP conversation:


Dec  7 23:13:32 Sirius postfix/cleanup[2738]: warning: unsupported 
dictionary type: pcre (/usr/lib/postfix/postfix-pcre.so.1.0.1: No such 
file or directory)
Dec  7 23:13:32 Sirius postfix/cleanup[2738]: error: unsupported 
dictionary type: pcre


I stress once again - this error *occurs ONLY* when 
"milter_header_checks" option is used. This behavior*does not appear* 
with the generic (mime_)header_checks!


A temporary solution is to set the cleanup process to work in the 
non-chrooted mode. Aditionaly, but after that new obstacle has appeared 
- Postfix comes with "o=" /etc/postfix/ directory permission, whereby 
cleanup cannot reach the map file. "chmod o+x /etc/postfix/" should 
cause to this workaround works properly.


Below, I put a step by step how to reproduce this bug:

*Postfix 3.1.3 from debian repository is needed.

*Any milter application which will write header to the 

Bug#842753: closed by gregor herrmann <gre...@debian.org> (Bug#842753: fixed in libnet-sip-perl 0.807-1)

[gregor herrmann]

Control: reopen -1

On Wed, 07 Dec 2016 17:42:13 +, Debian Bug Tracking System wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the libnet-sip-perl package:
> 
> #842753: FTBFS: test failures
> 
> It has been closed by gregor herrmann .

That was too fast :/

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/libnet-sip-perl.html
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/libnet-sip-perl_0.807-1.rbuild.log


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#844048: mysql-common: Fails to install when conffile /etc/mysql/my.cnf.fallback is removed

[Andreas Beckmann]

Control: tag -1 pending

On Fri, 11 Nov 2016 21:59:38 -0300 Felipe Sateler 
wrote:
> As subject says. Error is:
> 
> update-alternatives: error: alternative path /etc/mysql/my.cnf.fallback 
> doesn't exist

It's a strange use case ... but mysql-common shouldn't fail to install
in that case.

> Perhaps preinst should recreate it before running update-alternatives?
> If not desired, maybe it can suggest how to fix the issue (dpkg
> --force-confask)

Since packages are supposed to respect local modifications to conffiles
(including deletion), I'm not trying to restore that file.

We will just skip setting up an alternative pointing to the missing file
(leaving the system with possibly no my.cnf or a dangling symlink,
unless there is another provider of that alternative installed).


Andreas

Bug#841636: [debian-mysql] Processed: Merge duplicates

[Otto Kekäläinen]

Have you tried building with MariaDB Connector C/C++ (package
libmariadb-dev) instead of the MySQL Connector C++?

841636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841636
844275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844275
844302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844302
844304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844304
844401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844401
844492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844492
844550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844550
844824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844824
844850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844850
844851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844851
844852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844852
844863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844863
844868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844868
844875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844875
844876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844876
844894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844894
844895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844895
844899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844899
844935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844935
844941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844941
844957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844957
844981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844981
846746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846746

Bug#846399: RFS: rush/1.8+dfsg-1 -- New upstream's release.

[Mats Erik Andersson]

Hello there!

Onsdag den 7:e december 2016, klockan 15:56, skrev Gianfranco Costamagna detta:
> >
> >+ debian/upstream/signing-key.pgp: New file.
> >+ debian/source/include-binaries: New file.
> 
> please use a text-version of the signing-key and avoid the include-binaries 
> file?

Then I need education on the procedure to create a keyring file on the go,
since gpgv only handles keyrings, not armoured keyfiles.

Best regards,
 Mats E Andersson

Bug#846956: details

[Tadsel]

Possible lead : python[-x.y] and python-qt[-z.za] are notoriously out of sync. 
Dependency mismatch? 

Bug#834093: guile-2.0: leaves alternatives after purge: /usr/bin/guile, /usr/share/man/man1/guile.1.gz

[Rob Browning]

Andreas Beckmann  writes:

> I'd like to see this fixed in stretch.

Hopefully -3 did it.  If not, please shout.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#847343: firmware-misc-nonfree: breaks update-initramfs if plymouth installed

[Ben Caradoc-Davies]

On Wed, 7 Dec 2016 11:57:54 -0500 Zack Weinberg  wrote:

FYI, on a system without plymouth, the package installs without any
complaint, and the computer boots successfully using the new
initramfs.


Thanks, Zack. I have updated the title to indicate that this bug only 
affects systems with plymouth installed.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#840424: RFS: verilog-mode

[Sean Whitton]

control: tag -1 -moreinfo +confirmed
control: noowner -1

I consider git revision 4ba937fbc958fb5037e65fe351d18f2da8e0b988 ready
for upload.

Thank you for your patience, Kiwamu.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#847340: initramfs-tools: fails to copy DRM modules with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8

[Ben Caradoc-Davies]

Also reported as grave bug #847343 against firmware-nonfree/20161130-1 
to warn apt-listbugs users against upgrading:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#847343: firmware-misc-nonfree: breaks update-initramfs

[Ben Caradoc-Davies]

This is the same bug reported in #847340 against initramfs-tools:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847340

The problem is in initramfs-tools; firmware-misc-nonfree is just the 
trigger. Rather than merging, I would like to leave this bug against 
firmware-misc-nonfree to protect apt-listbugs users from the breakage 
upgrading firmware-misc-nonfree triggers.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#847411: O: gnome-btdownload, GNOME interface for 'executing' BitTorrent files

[Andrea Veri]

Package: wnpp
Severity: normal

Package description:

A simple GNOME interface designed as a mime-sink for BitTorrent files.

Not a front-end, more-or-less just a session dialog. Check the BitTorrent
package for more details.

-- 

Cheers,

Andrea

Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin Team Coordinator,
GNOME Foundation Membership & Elections Committee Chairman

Homepage: http://www.gnome.org/~av


signature.asc
Description: Digital signature

Bug#847410: O: fische, stand-alone sound visualisation for Linux

[Andrea Veri]

Package: wnpp
Severity: normal

Package description:

This application based on libsdl and on the alsa audio 
driver provides visualisation to the sound reproduced 
by a sound device creating waves and particular effects.

-- 

Cheers,

Andrea

Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin Team Coordinator,
GNOME Foundation Membership & Elections Committee Chairman

Homepage: http://www.gnome.org/~av


signature.asc
Description: Digital signature

Bug#847397: libimager-perl FTBFS on mips/mipsel: Failed 10/66 test programs

[Tony Cook]

On Wed, Dec 07, 2016 at 10:27:33PM +0200, Adrian Bunk wrote:
> Source: libimager-perl
> Version: 1.005+dfsg-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=libimager-perl=sid
> 
> ...
> Test Summary Report
> ---
> t/150-type/030-double.t   (Wstat: 10 Tests: 16 Failed: 0)
>   Non-zero wait status: 10
>   Parse errors: Bad plan.  You planned 136 tests but ran 16.

This looks like an unaligned access from the tests that failed,
probably in imgdouble.c.

Would it be possible to get access to this (or similar) hardware to
debug on?

Otherwise a backtrace for a -g build from the crash would be handy:

  perl Makefile.PL OPTIMIZE=-g
  make
  gdb --args perl -Mblib t/150-type/030-double.t
  r
  
  bt

Thanks,
Tony

Bug#847409: O: bitstormlite, BitTorrent Client based on C++/Gtk+2.0

[Andrea Veri]

Package: wnpp
Severity: normal

Package description:

This application based on the C++ language integrated
with a Gtk+2.0 user-friendly gui has a great feature, 
which is the possibility to download a huge amount of 
data from any .torrent file taken from trackers around
the web.

-- 

Cheers,

Andrea

Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin Team Coordinator,
GNOME Foundation Membership & Elections Committee Chairman

Homepage: http://www.gnome.org/~av


signature.asc
Description: Digital signature

Bug#828262: cfengine2: FTBFS with openssl 1.1.0

[Petter Reinholdtsen]

Given that cfengine2 no longer get any upstream development, as far as I know,
I guess the easiest and most sensible way to fix this is to build with
libssl1.0-dev for now.  If cfengine2 is still needed in Stretch+1 someone should
consider to port the code to openssl 1.1.

Debian Edu still uses cfengine2, and would very much like to see it still
available in Stretch.

If this patch is applied, this BTS report should have its severity lowered to
important or normal.

diff -ur cfengine2-2.2.10/debian/control cfengine2-2.2.10-pere/debian/control
--- cfengine2-2.2.10/debian/control 2016-08-21 08:24:15.0 +
+++ cfengine2-2.2.10-pere/debian/control2016-12-07 22:14:28.911881217 
+
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Antonio Radici 
 Build-Depends: debhelper (>= 7.0.50), autoconf, automake, autotools-dev,
- bison, dh-autoreconf, flex, libdb-dev, libssl-dev, libtool, perl (>= 5),
+ bison, dh-autoreconf, flex, libdb-dev, libssl1.0-dev, libtool, perl (>= 5),
  po-debconf, texinfo, quilt, libselinux1-dev [linux-any]
 Standards-Version: 3.9.8
 Homepage: http://www.cfengine.org/

-- 
Happy hacking
Petter Reinholdtsen

Bug#847408: openorienteering-mapper: New upstream release

[Kjetil Kjernsmo]

Package: openorienteering-mapper
Version: 0.6.5-14.1
Severity: wishlist

Dear Maintainer,

I just wanted to give a heads-up: There's a new upstream release. 

Seems like the watch-script has failed to detect it.

KUTGW!

Cheers,

Kjetil


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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 openorienteering-mapper depends on:
ii  dpkg 1.17.27
ii  libc62.19-18+deb8u6
ii  libgcc1  1:4.9.2-10
ii  libpolyclipping166.1.3a-2
ii  libproj0 4.8.0-5
ii  libqt5core5a [qtbase-abi-5-3-2]  5.3.2+dfsg-4+deb8u1
ii  libqt5gui5   5.3.2+dfsg-4+deb8u1
ii  libqt5network5   5.3.2+dfsg-4+deb8u1
ii  libqt5printsupport5  5.3.2+dfsg-4+deb8u1
ii  libqt5widgets5   5.3.2+dfsg-4+deb8u1
ii  libqt5xml5   5.3.2+dfsg-4+deb8u1
ii  libstdc++6   4.9.2-10
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages openorienteering-mapper recommends:
ii  qt5-image-formats-plugins  5.3.2-2
ii  qttools5-dev-tools 5.3.2-3
ii  qttranslations5-l10n   5.3.2-2

openorienteering-mapper suggests no packages.

-- no debconf information

Bug#847407: pius: Signing keys doesn't work due to KEY_CONSIDERED gpg response

[Ingo Bauersachs]

Package: pius
Version: 2.2.2-2
Severity: important
Tags: upstream

Dear Maintainer,

The upstream package v2.2.2 cannot deal with gpg's KEY_CONSIDERED responses.
This prevents key signing commands such as 'pius -s  '
from working and reporting 'ERROR: GnuPG reported an unknown error'.

Upstream has this bug fixed in Github pull request #44. Please consider
applying this patch (maybe even package the latest state from master).



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

Kernel: Linux 4.8.0-1-amd64 (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 pius depends on:
ii  gnupg   2.1.16-3
ii  gnupg2  2.1.16-3
ii  python  2.7.11-2
pn  python:any  

pius recommends no packages.

pius suggests no packages.

-- no debconf information

Bug#847405: modemmanager: USSD does not work (mmcli, D-link DWM-157)

[Wlodek Drabent]

Package: modemmanager
Version: 1.4.0-1
Severity: normal

Dear Maintainer,

sudo mmcli -m 51 --3gpp-ussd-initiate='*101#'
results in
error: couldn't initiate USSD session: 'Timeout was reached'
(instead of making the modem to send the USSD message).
This functionality works when the modem is connected to Windows.

Othewise the modem seems to work correctly, including surviving suspend/resume.
Some info about the modem included at the end.

Sincerely
--W.D.


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

Kernel: Linux 3.16.0-4-686-pae (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 modemmanager depends on:
ii  init-system-helpers1.22
ii  libc6  2.19-18+deb8u6
ii  libglib2.0-0   2.42.1-1+b1
ii  libgudev-1.0-0 215-17+deb8u5
ii  libmbim-glib4  1.10.0-2.1
ii  libmbim-proxy  1.10.0-2.1
ii  libmm-glib01.4.0-1
ii  libpolkit-gobject-1-0  0.105-15~deb8u2
ii  libqmi-glib1   1.10.2-2
ii  libqmi-proxy   1.10.2-2

Versions of packages modemmanager recommends:
ii  usb-modeswitch  2.2.0+repack0-2

modemmanager suggests no packages.

-- no debconf information
.

The modem is:  D-link DWM-157, USB.  lsusb says:   ID 2001:7d02 D-Link Corp. 


mmcli -m 59  (the number keeps changing) produces this

/org/freedesktop/ModemManager1/Modem/59 (device id '***removed***')
  -
  Hardware |   manufacturer: 'Generic'
   |  model: 'MBIM [2001:7D02]'
   |   revision: 'MOLY.WR8.W1231.DC.WG.MP.V3'
   |  supported: 'gsm-umts'
   |current: 'gsm-umts'
   |   equipment id: '355620057029171'
  -
  System   | device: '/sys/devices/pci:00/:00:1a.7/usb6/6-3'
   |drivers: 'cdc_mbim, option1'
   | plugin: 'Generic'
   |   primary port: 'cdc-wdm0'
   |  ports: 'cdc-wdm0 (mbim), wwan0 (net), ttyUSB136 (at), 
ttyUSB137 (at)'
  -
  Numbers  |   own : '48***removed***'
  -
  Status   |   lock: 'none'
   | unlock retries: 'unknown (0)'
   |  state: 'connected'
   |power state: 'on'
   |access tech: 'hsdpa, hsupa'
   | signal quality: '0' (cached)
  -
  Modes|  supported: 'allowed: 2g, 3g; preferred: none'
   |current: 'allowed: 2g, 3g; preferred: none'
  -
  Bands|  supported: 'unknown'
   |current: 'unknown'
  -
  IP   |  supported: 'ipv4, ipv6, ipv4v6'
  -
  3GPP |   imei: '355620057029171'
   |  enabled locks: 'net-pers, net-sub-pers, provider-pers, corp-pers'
   |operator id: '26002'
   |  operator name: '26002'
   |   subscription: 'unknown'
   |   registration: 'home'
  -
  SIM  |   path: '/org/freedesktop/ModemManager1/SIM/59'

  -
  Bearers  |  paths: '/org/freedesktop/ModemManager1/Bearer/59'

.

 mmcli --messaging-status -m 59produces:

/org/freedesktop/ModemManager1/Modem/59
  
  Messaging | supported storages: 'mt'
|default storage: 'unknown'

Bug#847406: O: ctorrent - BitTorrent Client written in C++

[Andrea Veri]

Package: wnpp
Severity: normal

Package description:

This application is written in the C++ language and doesn't require any 
graphical component, such as an X server. Original ctorrent's upstream has 
stopped its development and now it's kept updated with new releases/bug fixes 
by a new developer. It's built as a console program and it can be even used 
remotely in a machine that provides outside ssh access. Other main features are:

 * Support for large files (>2GB) and large torrents (>255 files).
 * Strategic selection of pieces to request for download.
 * Continuous queueing of download requests, tuned based on
   latency and throughput for each peer.
 * Improved download performance, including parallel requests
   in initial and endgame modes.
 * Improved bandwidth regulation.
 * Improved compatibility with other peers.
 * Performance optimization and bug fixes.
 * An interface for monitoring and managing multiple clients.
 * Dynamic cache allocation and management, including prefetch.

More information about the original but discontinued ctorrent's project can be 
found by browsing the following website: http://ctorrent.sourceforge.net

-- 

Cheers,

Andrea

Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin Team Coordinator,
GNOME Foundation Membership & Elections Committee Chairman

Homepage: http://www.gnome.org/~av


signature.asc
Description: Digital signature

Bug#808784: Refresh the xserver-xorg-video-openchrome package

[Dylan]

Hi Andreas,

2016-12-05 14:31 GMT+01:00 Andreas Boll :
> I have some comments for further improvements:
>
> Please use `wrap-and-sort -a -s` to be more consistent with the
> previous style and other xsf packages.
>
> With the debhelper compat change you can also remove the build-dep on
> dh-autoreconf since debhelper >= 10 depends on dh-autoreconf itself.
> Furthermore you can remove autoreconf from the dh line in debian/rules
> since debhelper compat level 10 enables it by default. See also [1].
>
> Other than that your changes look good to me.
>

Thanks for your review. I pushed your suggestions and some other changes.

What do you prefer for the next steps (push on Alioth and the sponsorship)?
Should I join the team to push myself these changes on the repository?
Should I push the package on mentors.debian.net?

Thanks

Best regards,
Dylan

Bug#847404: ITP: golang-github-geertjohan-go.incremental -- package incremental provides concurency-safe incremental numbers

[liang yan]

Package: wnpp
Severity: wishlist
Owner: Liang Yan 

* Package name: golang-github-geertjohan-go.incremental
  Version : 0.0~git20140220.0.92fd0ce-1
  Upstream Author : Geert-Johan Riemer
* URL : https://github.com/geertjohan/go.incremental
* License : BSD-2-clause
  Programming Lang: Go
  Description :Go package incremental provides concurency-safe
incremental numbers.

 Go package incremental provides typed incremental counters that are
type-safe,
 it has example that located in example subdirectory.





signature.asc
Description: OpenPGP digital signature

Bug#847338: flight-of-the-amazon-queen: non-free restrictions in license conditions

[Ben Finney]

On 07-Dec-2016, Ben Finney wrote:

> The license conditions from the copyright holders restrict
> distributing the work for a fee:
> 
> 2) You may charge a reasonable copying fee for this archive […]
> 
> It is unclear what the copyright holders would consider a “reasonable
> fee”; regardless what that limit would be, it is a restriction on the
> fee that may be charged for redistribution.
> 
> 3) You may not charge a fee for the game itself. This includes
> reselling the game as an individual item.

As has been pointed out to me (thanks, Ansgar Burchardt) the existing
Artistic License terms contain effectively the same restrictions, in §5:

5. You may charge a reasonable copying fee for any distribution of
this Package. […] You may not charge a fee for this Package itself.



That demonstrates that these restrictions are deemed DFSG-free by
Debian's FTP Masters in works prior and subsequent to this one.


Thank you, maintainers, for responding promptly to bug reports :-)

-- 
 \ “If I had known what it would be like to have it all... I might |
  `\ have been willing to settle for less.” —Jane Wagner, via Lily |
_o__)   Tomlin |
Ben Finney 


signature.asc
Description: PGP signature

Bug#840424: RFS: verilog-mode

[Kiwamu Okabe]

Dear Sean,

On Thu, Dec 8, 2016 at 12:42 AM, Sean Whitton  wrote:
>> I think "Forwarded: no" is valid, because
>> http://dep.debian.net/deps/dep3/ say following:
>
> Right, but the convention is that "no" means "I should forward this but
> I haven't forwarded it yet" and "not-needed" means "this shouldn't be
> forwarded."

Thanks. I didn't understand it. It's fixed.

Best regards,
-- 
Kiwamu Okabe at METASEPI DESIGN

Bug#847403: RFS: nlohmann-json/2.0.6-1

[Muri Nicanor]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "nlohmann-json"

* Package name: nlohmann-json
  Version : 2.0.6-1
  Upstream Author : Niels Lohmann
* Url : https://nlohmann.github.io/json/
* Licenses: Apache-2.0,BSL-1.0,MIT
  Section : libs

It builds those binary packages:

  * nlohmann-json-dev

To access further information about this package, visit the following URL:

https://mentors.debian.net/package/nlohmann-json

Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/n/nlohmann-json/nlohmann-json_2.0.6-1.dsc


More information about nlohmann-json can be obtained from
https://nlohmann.github.io/json/

Changes since last upload:

  * New upstream version 2.0.5
  * New upstream version 2.0.6

cheers,
-- 
muri



signature.asc
Description: OpenPGP digital signature

Bug#845335: bzr issue

[Jelmer Vernooij]

On Wed, Dec 07, 2016 at 05:47:52PM +, Ben Dooks wrote:
> The "bzr: ERROR: exceptions.TypeError: first argument must be string or
> compiled pattern" is still there after updating.
> 
> bzr is already the newest version (2.7.0+bzr6619-1).
This has been fixed. The latest version of bzr (currently in unstable, doesn't
seem to have made it to testing) is 2.7.0+bzr6619-3.

Bug#847322: flight-of-the-amazon-queen: source package should include complete source

[Ben Finney]

On 07-Dec-2016, Markus Koschany wrote:
> On 07.12.2016 11:24, Ben Finney wrote:

> > The source was presumably available to upstream when making this
> > package, see  for
> > example.

I have now responded to ask about the source that message describes
.

> Please read README.Debian. This game is fully DFSG compliant and every
> piece of source, in this case game assets and media files are included
> in this package.

It is because the copyright holder described having the source (which
I take to mean, the source used to generate the binary blob) at the
time of making what became the Debian package, that I am seeking that
source for the Debian source package.

-- 
 \“If one tells the truth, one is sure, sooner or later, to be |
  `\   found out.” —Oscar Wilde, _Phrases and Philosophies for the Use |
_o__)  of the Young_, 1894 |
Ben Finney 


signature.asc
Description: PGP signature

Bug#847402: RM: gitit [arm64] -- ICE; FTBFS on arm64 due to binutils regression #830540

[Adrian Bunk]

Package: ftp.debian.org
Severity: normal

See #830540 for details.

Bug#834989: Using the Apache authenticator

[Peter Eckersley]

Hi Andrey,

If you have Apache listening on :80 and :443, you probably actually want to
use the Apache *authenticator* to obtain all your certs (you don't have to
install them in your Apache config). If you run certbot with "certonly
--apache" what that will do is either use your default :443 vhost if you have
one, or spin up a transient Apache vhost to prove control of the domain by
TLS-SNI-01, obtain the cert, then remove the vhost again.

In all cases, using Apache for authentication but not installation should
leave your Apache configuration in its original state after Certbot is run.

You could edit the renewal conf file to make that happen, or just run:

certbot certonly -n --force-renewal -a apache -i none -d $EMAIL_DOMAINS

to update that certificiate lineage to use the apache authenticator.

Then in the future, use:

certbot certonly -n --apache -d $NEW_EMAIL_DOMAINS

to get certs for things like mail domains that you don't want Apache to
actually respond to.

(I'm including the -n non-interactive flag because it works around this UI
issue: https://github.com/certbot/certbot/issues/3869 )

-- 
Peter Eckersleyp...@eff.org
Chief Computer Scientist  Tel  +1 415 436 9333 x131
Electronic Frontier FoundationFax  +1 415 436 9993