Bug#659630: tardy: problems with files >2GB

[Jari Aalto]

forwarded 659630  Peter Miller , 

thanks

There is persistent problem packaging 1.28.D001 which would
fix this bug. The tests do not succeed: hangs at
t0072a

$ PATH="$(pwd)/bin:$PATH" /bin/sh -x test/00/t0072a.sh
+ TEST_SUBJECT=dot.xz input
+ . test_prelude
+ [ dot.xz input = fill me in -o dot.xz input =  ]
+ pwd
+ here=/srv/deb/debian/tardy/tardy.git
+ test 0 -eq 0
+ arch=.
+ bindir=/srv/deb/debian/tardy/tardy.git/./bin
+ testdir=/tmp/icomp-14224
+ mkdir /tmp/icomp-14224
+ test 0 -eq 0
+ cd /tmp/icomp-14224
+ test 0 -eq 0
+ diff --strip-trailing-cr /dev/null /dev/null
+ which diff
+ diffpath=/usr/bin/diff
+ LINES=24
+ export LINES
+ COLS=80
+ export COLS
+ cat
+ test 0 -ne 0
+ date
+ test 0 -ne 0
+ tar cJf test.tar.xz test.in
+ test 0 -ne 0
+ tardy -auto-test test.tar.xz test.tar.gz

Bug#842431: iptraf-ng: maintainer's address doesn't accept mail from the BTS

[Adam Borowski]

Package: iptraf-ng
Version: 1.1.4-3
Severity: serious
Justification: Policy 3.3

Hi!
I'm afraid that the maintainer's address for this package is set to "Ubuntu
Developers ", which doesn't accept
mail from the BTS, as required by the Policy.

This also seems to be a medium-traffic general list for a derived
distribution whose packaging policies differ from those of Debian, thus
mails related to non-Ubuntu packaging of a specific package are probably out
of place.


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

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

Versions of packages iptraf-ng depends on:
ii  libc6 2.24-5
ii  libncursesw5  6.0+20160917-1
ii  libtinfo5 6.0+20160917-1

iptraf-ng recommends no packages.

iptraf-ng suggests no packages.

-- no debconf information

Bug#741582: closed by Ron <r...@debian.org> (Stylus can lock up left mouse button with no debug trail)

[Borden Rhodes]

It's perfectly fair to assume that my Bluetooth mouse + Wacom tablet
has created a corner case creating the sorts of lock-ups I describe.
Whilst I agree that the developers should improve the software as a
whole instead of chase one-off corner cases, the software neither
crashes loudly nor even whispers to ~/.xsession-errors that this, what
I hope you'll agree is, undesirable behaviour occurred and the
component that broke. Can this silence alone be considered a problem
with the software that is worth addressing?


On 28 October 2016 at 04:21, Debian Bug Tracking System
 wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the xserver-xorg-input-wacom package:
>
> #741582: wacom: Stylus can lock up left mouse button with no debug trail
>
> It has been closed by Ron .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ron  by
> replying to this email.
>
>
> --
> 741582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741582
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Ron 
> To: 741582-d...@bugs.debian.org
> Cc:
> Date: Fri, 28 Oct 2016 18:39:19 +1030
> Subject: Stylus can lock up left mouse button with no debug trail
>
> Hi,
>
> I'm going to tentatively close this bug here now, since there's a pretty
> good chance that it falls into the "new device, not yet properly supported"
> category, and so there's a reasonably good chance that things have
> improved on that front since it was reported.
>
> If you've got 'mouse buttons' locking up, that sounds like something
> more fundamental is wrong than just a glitch with the part of it in
> this package.
>
> If you're still seeing this with the kernel and drivers in unstable,
> then more information might be useful - but it's the kind of bug that
> is hard for anyone without the device in question to do much about.
>
>   Ron
>
> -- Forwarded message --
> From: Borden Rhodes 
> To: Debian Bug Tracking System 
> Cc:
> Date: Fri, 14 Mar 2014 01:48:28 -0400
> Subject: wacom: Stylus can lock up left mouse button with no debug trail
> Package: xserver-xorg-input-wacom
> Version: 0.23.0+20131011-1+b1
> Severity: important
> File: wacom
>
> Good evening,
>
> I use a Fujitsu Lifebook T4410, which comes with a built-in touchpad and Wacom
> touch + stylus screen. In addition, I use a generic bluetooth mouse (typically
> in lieu of the touchpad when I'm using it in laptop mode).
>
> The stylus has these features:
> 1) tapping the pointy end normally acts like a normal left mouse button click
> (LMB);
> 2) pressing the bottom end of the stylus button and then tapping acts like a
> right mouse button (RMB);
> 3) pressing the top end of the stylus button and then tapping acts like a
> middle mouse button (MMB); and
> 4) the eraser bit at the other end of the stylus appears to act like a left
> mouse button click (Eraser).
>
> I was using the stylus in Xournal when I noticed that the left regular LMB was
> no longer working. I was still able to draw in Xournal, but tapping outside 
> the
> drawing area had no effect at all. The MMB and RMB continued to work normally,
> except that I couldn't activate anything because the LMB wasn't working. This
> behaviour affected the whole desktop, which is why I'm not filing a bug with
> Xournal.
>
> The same behaviour extended to the laptop's touchpad and my Bluetooth mouse:
> right clicks, middle clicks and movement continued to work normally, but left
> clicks had no response.
>
> Using keyboard commands, I opened a terminal and tailed every log in 
> /var/log/,
> including dmesg, syslog, Xorg.0.log, messages, kdm.log, kern.log, debug and
> daemon.log. I also tailed ~/.xsession-errors for good measure. None of these
> logs had any mention whatsoever of the Wacom drivers during the time period
> when the stylus/mouse started acting up. The only message relevant to human
> input devices were dmesg entries announcing that my Bluetooth mouse had woken
> up and been assigned correctly.
>
> Accordingly, other than my epic on how my mouse got to this situation, I have
> no other debugging information to offer.
>
> I went back into Xournal and mashed the RMB and MMB a couple of times and the
> LMB started working again (as did the left mouse button on my Bluetooth mouse
> and touchpad). For all intents and purposes, my computer is working normally
> again.
>
> I should add that this is not the first time the LMB has locked up like this.
> Sometimes, the LMB will lock in 'pressed' mode, leading to a persistent drag-
> and-drop state. However, I wasn't paying close enough attention the times it
> locked up before to give any useful information. I 

Bug#842426: onedrive: systemd user unit shipped is incorrect

[Norbert Preining]

Hi Alam,

> onedrive.service been shipped to installed to /lib/systemd/user/
> But it should be in /usr/lib/systemd/user/ to be listed and start by a user's 
> systemd

Interesting, I did not install anything by myself, that was all
done by debhelper .. dh $@, so either it is a bug there or I need
to do something else.

I will look into it.

> ExecStart=/usr/local/bin/onedrive -m

Thanks, fixed in git.

All the best

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#683493: moot now that iptraf is gone

[Adam Borowski]

> Long description mentions that iptraf-ng is a fork of iptraf, but such
> historical info is less useful for people looking at packages to install. 
> Much better would be describing *how* iptraf-ng compares to iptraf.

Now that iptraf is gone, I think such a comparison is no longer needed
(nothing to compare *to*), and this bug can be closed.


Meow!
-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Bug#842430: /var/cache/apt/archives/\*

[積丹尼 Dan Jacobson]

Package: aptitude
Version: 0.8.3-1+b1
Severity: wishlist

I notice file '/var/cache/apt/archives/*' on all my machine.
$ stat /var/cache/apt/archives/\*
  File: '/var/cache/apt/archives/*'
  Size: 0   Blocks: 0  IO Block: 4096   regular empty file
Device: 812h/2066d  Inode: 14  Links: 1
Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (0/root)
Access: 2016-01-30 10:51:21.047306840 +0800
Modify: 2016-01-30 10:51:21.171306834 +0800
Change: 2016-10-29 12:44:46.880101991 +0800
 Birth: -

Not sure how it got there.
OK I'll remove it.

Bug#842429: RFS: mlocate/0.26-1.1 [NMU]

[Dan Mick]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "mlocate"

* Package name: mlocate
 Version : 0.26-1.1
 Upstream Author : Miloslav Trmac 
* URL : https://fedorahosted.org/mlocate/
* License : GPLv2
 Section : utils

It builds those binary packages:

  mlocate- quickly find files on the filesystem based on their
name

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

https://mentors.debian.net/package/mlocate


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

  dget -x
https://mentors.debian.net/debian/pool/main/m/mlocate/mlocate_0.26-1.1.dsc

More information about hello can be obtained from
https://www.example.com.

Changes since the last upload:

mlocate (0.26-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Add cephfs to PRUNEFS and /var/lib/ceph to PRUNEPATHS
Closes: #786433

 -- Dan Mick   Fri, 28 Oct 2016 18:41:42 -0700


Regards,
Dan Mick

Bug#842428: debsecan: error 403 forbidden since 10/27/2016

[Paul Wise]

Control: fixed -1 0.4.17
Control: tags -1 + fixed-upstream
Control: forwarded -1 
https://gitorious.org/debsecan/debsecan.git/?p=debsecan:debsecan.git;a=commit;h=0fca4c0af14fdd2fab74982985dd2387df3af26c

On Sat, 29 Oct 2016 05:00:40 +0200 jeromecc wrote:

> I get these error reports in my incoming email:
> error: while downloading 
> http://secure-testing.debian.net/debian-secure-testing/project/debsecan/release/1/wheezy:
> HTTP Error 403: Forbidden

This bug was fixed in Debian jessie, see the URL above.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#840540: dianara: Please update to v1.3.5 to allow switching qoauth to qt5

[Lisandro Damián Nicanor Pérez Meyer]

¡Hola Mónica!

On jueves, 20 de octubre de 2016 3:22:06 P. M. ART Mònica Ramírez Arceda 
wrote:
[snip] 
> Perfect :)
> Waiting for your news!

I have just pushed qoauth2 to experimental. I'm afraid it took me too much 
time to push it and we are near the freeze deadeline, but we might be able to 
get it done in time :-/

It has go to trough NEW first, but if you want to have it sooner I can send 
you the link of my personal repo.

Cheers!

-- 
~/ sweet ~/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#842428: debsecan: error 403 forbidden since 10/27/2016

[jeromecc]

Package: debsecan
Version: 0.4.16+nmu1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I get these error reports in my incoming email:
error: while downloading 
http://secure-testing.debian.net/debian-secure-testing/project/debsecan/release/1/wheezy:
HTTP Error 403: Forbidden

several times a day since 10/27/2016.

I don't get any security reports anymore.

Thanks for maintaining this useful package.

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

Kernel: Linux 3.18.43-guest-7-e34a08f-x86_64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debsecan depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  python 2.7.3-4+deb7u1
ii  python-apt 0.8.8.2

Versions of packages debsecan recommends:
ii  cron3.0pl1-124
ii  postfix [mail-transport-agent]  2.9.6-2

debsecan suggests no packages.

-- debconf information:
  debsecan/source:
  debsecan/mailto: root
  debsecan/report: true
  debsecan/suite: GENERIC

Bug#842427: php7.0-common: Timezone is set incorrectly

[Russell Stuart]

Package: php7.0-common
Version: 7.0.12-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

README.Debian.gz says:

  "Debian PHP has been patched to use the system wide timezone database
  from the tzdata package, making sure any updates there are
  automatically used by PHP as well."

Looking at php7.0/ext/date/lib/parse_date.re it doesn't do that.  What
is does do doesn't work when Daylight saving is in effect, to wit:

  - My timezone is Australia/Brisbane.  This is accurately reflected
in /etc/localtime and /etc/timezone.

  - Australia/Brisbane is the same timezone as Australia/Melbourne,
but with one difference: Australia/Brisbane does not implement
Daylight savings, whereas Australia/Melbourne does.

  - Daylight savings is currently in effect in Australia/Melbourne.

  - abbr_search() in parse_date.re checks for a matching gmtoffset,
only.  This is the timezone offset before Daylight savings is
applied.  This is the same for both Australia/Brisbane and
Australia/Melbourne.  It happens to find Australia/Melbourne
first.

  - So PHP's timezone is set to Australia/Melbourne.  Which means
localtime is 1 hour ahead of where it should be.

If I find the time, I will submit a patch for this.  The patch will:

  - First look at /etc/timezone.  If it accurately reflects what
/etc/localtime says, it will be used.

  - Otherwise the attempt fails, and so PHP will continue to look
for other options.  As it stands I don't believe there are any
so "UTC" will be the time zone.



- -- Package-specific info:
 Additional PHP 7.0 information 

 PHP @PHP_VERSION SAPI (php7.0query -S): 

 PHP 7.0 Extensions (php7.0query -M -v): 

 Configuration files: 
 /etc/php/7.0/mods-available/calendar.ini 
extension=calendar.so

 /etc/php/7.0/mods-available/ctype.ini 
extension=ctype.so

 /etc/php/7.0/mods-available/exif.ini 
extension=exif.so

 /etc/php/7.0/mods-available/fileinfo.ini 
extension=fileinfo.so

 /etc/php/7.0/mods-available/ftp.ini 
extension=ftp.so

 /etc/php/7.0/mods-available/gettext.ini 
extension=gettext.so

 /etc/php/7.0/mods-available/iconv.ini 
extension=iconv.so

 /etc/php/7.0/mods-available/pdo.ini 
extension=pdo.so

 /etc/php/7.0/mods-available/phar.ini 
extension=phar.so

 /etc/php/7.0/mods-available/posix.ini 
extension=posix.so

 /etc/php/7.0/mods-available/shmop.ini 
extension=shmop.so

 /etc/php/7.0/mods-available/sockets.ini 
extension=sockets.so

 /etc/php/7.0/mods-available/sysvmsg.ini 
extension=sysvmsg.so

 /etc/php/7.0/mods-available/sysvsem.ini 
extension=sysvsem.so

 /etc/php/7.0/mods-available/sysvshm.ini 
extension=sysvshm.so

 /etc/php/7.0/mods-available/tokenizer.ini 
extension=tokenizer.so


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

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

Versions of packages php7.0-common depends on:
ii  libc62.24-5
ii  libssl1.0.2  1.0.2j-1
ii  php-common   1:45
ii  ucf  3.0036

php7.0-common recommends no packages.

php7.0-common suggests no packages.

Versions of packages php7.0-cli depends on:
ii  libc62.24-5
ii  libedit2 3.1-20150325-1+b1
ii  libmagic11:5.28-4
ii  libpcre3 2:8.39-2
ii  libssl1.0.2  1.0.2j-1
ii  libxml2  2.9.4+dfsg1-2
ii  mime-support 3.60
ii  php7.0-json  7.0.12-1
ii  php7.0-opcache   7.0.12-1
ii  php7.0-readline  7.0.12-1
ii  tzdata   2016h-1
ii  ucf  3.0036
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages php7.0-cli suggests:
pn  php-pear  

Versions of packages libapache2-mod-php7.0 depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.23-5
ii  libc6   2.24-5
ii  libmagic1   1:5.28-4
ii  libpcre32:8.39-2
ii  libssl1.0.2 1.0.2j-1
ii  libxml2 2.9.4+dfsg1-2
ii  mime-support3.60
ii  php7.0-cli  7.0.12-1
ii  php7.0-json 7.0.12-1
ii  php7.0-opcache  7.0.12-1
ii  tzdata  2016h-1
ii  ucf 3.0036
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages libapache2-mod-php7.0 recommends:
ii  apache2  2.4.23-5

Versions of packages libapache2-mod-php7.0 suggests:
pn  php-pear  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYFAiBAAoJEKzUn4heVFJuMTgP/R4vrKiQI0rdjt8GKAGgpNNP

Bug#842426: onedrive: systemd user unit shipped is incorrect

[Alam Arias]

Package: onedrive
Version: 1.1.20161012-1
Severity: normal

Dear Maintainer,

onedrive.service been shipped to installed to /lib/systemd/user/
But it should be in /usr/lib/systemd/user/ to be listed and start by a user's 
systemd

Also, the systemd unit's ExecStart is incorrect 
it have
ExecStart=/usr/local/bin/onedrive -m
When it should be
ExecStart=/usr/bin/onedrive -m

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 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 onedrive depends on:
ii  libc6 2.24-5
ii  libcurl3-gnutls   7.50.1-1
ii  libphobos2-ldc71  1:1.1.0+b3-1
ii  libsqlite3-0  3.14.2-1+b1

onedrive recommends no packages.

onedrive suggests no packages.

-- no debconf information

Bug#842423: gnome-terminal: Regression? gnome-terminal copies text to the wrong X display, but pastes from the correct one

[Robert Ou]

On Fri, Oct 28, 2016 at 6:35 PM, Michael Biebl  wrote:
>
> Am 29.10.2016 um 01:29 schrieb Robert Ou:
> > Package: gnome-terminal
> > Version: 3.22.0-3
> > Severity: important
> >
> > Dear Maintainer,
> >
> > After updating packages, I discovered that I was unable to copy/paste
> > properly in gnome-terminal. After experimenting, I discovered that this
> > was related to how my system has two X displays (e.g. :0 and :1) at the
> > same time. If gnome-terminal is launched on display :1, it somehow
> > manages to copy text onto the clipboard of display :0. However, pasting
> > text will paste the text from the clipboard of display :1. This makes it
> > impossible to use copy/paste in gnome-terminal in any sane way because
> > copied text can no longer be pasted in the same window where the text was
> > originally copied from. A gnome-terminal launched on display :0 copy/pastes
> > correctly (from and to the clipboard of display :0).
>
> Running multiple X/GNOME sessions for the same user is something which
> is not supported by GNOME.
>

I am not understanding what this problem has to do with sessions. My
system currently isn't running gnome-session at all, and this issue is
not affected by the presence or absence of gnome-settings-daemon.
Other GNOME applications like gedit can copy/paste correctly.

Bug#842423: gnome-terminal: Regression? gnome-terminal copies text to the wrong X display, but pastes from the correct one

[Michael Biebl]

Am 29.10.2016 um 01:29 schrieb Robert Ou:
> Package: gnome-terminal
> Version: 3.22.0-3
> Severity: important
> 
> Dear Maintainer,
> 
> After updating packages, I discovered that I was unable to copy/paste
> properly in gnome-terminal. After experimenting, I discovered that this
> was related to how my system has two X displays (e.g. :0 and :1) at the
> same time. If gnome-terminal is launched on display :1, it somehow
> manages to copy text onto the clipboard of display :0. However, pasting
> text will paste the text from the clipboard of display :1. This makes it
> impossible to use copy/paste in gnome-terminal in any sane way because
> copied text can no longer be pasted in the same window where the text was
> originally copied from. A gnome-terminal launched on display :0 copy/pastes
> correctly (from and to the clipboard of display :0).

Running multiple X/GNOME sessions for the same user is something which
is not supported by GNOME.



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



signature.asc
Description: OpenPGP digital signature

Bug#842425: RFP: meteor - Meteor, the JavaScript App Platform

[Jeffrey Cliff]

Package: wnpp
Severity: wishlist

Meteor is an ultra-simple environment for building modern web applications.

With Meteor you write apps:

   - in pure JavaScript
   - that send data over the wire, rather than HTML
   - using your choice of popular open-source libraries

Website: https://github.com/meteor/meteor


   - License permissive/MIT :
   https://github.com/meteor/meteor/blob/devel/LICENSE.txt

Bug#842117: file: detect MacWrite II documents

[Paul Wise]

On Fri, 2016-10-28 at 22:43 +0200, Christoph Biedl wrote:

> Some research reveals this is actually Word for Mac versions 4 or 5.

I see, sorry for the mis-diagnosis, I was mislead by this site:

http://mark0.net/onlinetrid.aspx

> The libreoffice suite can open this file, although the rendering looks
> a bit weird. I however failed to derive the file format from the
> code in sw/source/filter/ww8/ww8scan.cxx.

The WW8Fib::GetFIBVersion function looks interesting and matches the
first two bytes of the file. 

https://sources.debian.net/src/libreoffice/1:5.2.3~rc1-4/sw/source/filter/ww8/ww8scan.cxx/#L5414

Interestingly, the file referenced by that function *is* detected by
`file` as a 'Microsoft Office Document':

http://cmsdoc.cern.ch/documents/docformat/CMS_CERN_LetterHead.word

The WW8Fib::WW8Fib function looks to be the place where the header is
read out of the file:

https://sources.debian.net/src/libreoffice/1:5.2.3~rc1-4/sw/source/filter/ww8/ww8scan.cxx/#L5459

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#827061: transition: openssl

[Kurt Roeckx]

On Wed, Oct 26, 2016 at 10:55:19AM +0200, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> 
> On 25/10/16 20:09, Moritz Muehlenhoff wrote:
> > On Wed, Oct 19, 2016 at 10:44:08PM +0200, Kurt Roeckx wrote:
> >> On Mon, Oct 17, 2016 at 08:52:31PM +0200, Emilio Pozuelo Monfort wrote:
> >>>
> >>> I'm sorry but I'm going to have to nack this for Stretch, as much as I 
> >>> like to
> >>> approve transitions and get new stuff in. I have looked at the opened 
> >>> bugs and
> >>> I'm afraid this still is too disruptive. I have noticed that you have 
> >>> forwarded
> >>> some of them and sent patches, and I appreciate that. We can do this 
> >>> early in
> >>> the Buster cycle, so let's look at the status of this and prepare for the
> >>> transition when Stretch gets released.
> >>
> >> Is having 2 version of OpenSSL in Stretch an option?
> > 
> > We've discussed this within the security team and we'd be fine with
> > a one-time exception to have two openssl releases in stretch; the API
> > changes are clearly too invasive to cover the entire Debian archive,
> > but 1.1 also carries sufficiently important new features (like support
> > for chacha20/poly1305) to warrant the extra complexity.
> > 
> > (It's the release team's call of course).
> 
> 19:46 <  nthykier> pochu: seen jmm_ reply to the libssl thread?
> 19:46 <  jcristau> adsb: yay for binary debdiffs in q-v!  thanks a bunch.
> 19:46 < pochu> yep
> 19:47 < pochu> nthykier: so my concern was there was a big risk that we
> wouldn't finish the transition intime, delaying the release. but if the 
> security
> team is fine with (potentially, as I'll try not to) shipping both, then we
> should be fine, and I think I'll ack it
> 19:48 < pochu> of course we'll still try to get rid of the old one
> 19:48 <  nthykier> ack, I think that just made me pro on doing that as well
> 19:48 < pochu> cool, good to see we're on the same page
> 
> So let's do this. Let's try to get it finished and only ship openssl 1.1. We
> still have three months until the full freeze, and depending on how many
> packages (and which ones, for risk management etc) are left to be fixed after
> that, I may be happy to grant exceptions. But worst case we just ship both.
> 
> But please, wait a little bit so that we can sort out the PIE fallout. You can
> start preparing the updates and upload to experimental to clear NEW if you 
> want.
> We'll let you know once it's ok to upload to sid.

So it has been suggested that we keep the libssl-dev package at
the 1.0.2 package and create a new -dev package for the 1.1
version. We could then lower the severity of the bugs to important
again, and only the packages wanting to make use of 1.1 could
switch then.

I think the most important new security feature in the 1.1.0
version is the extended master secret support. There are also a
bunch of others like the chacha20-poly1305 and x25519, but they're
less important. All TLS using applications really should start
ussing the EMS, not just a few that want to switch to 1.1.


Kurt

Bug#762715: updates to dch --lts

[Holger Levsen]

Hi,

On Wed, Oct 26, 2016 at 01:23:56PM -0400, Antoine Beaupré wrote:
> I believe a few parameters here are incorrect as they have changed since
> this bug was reported.
> 
> * release should be: "wheezy-security"
> * the first log entry should be: "Non-maintainer upload by the Wheezy
>   LTS Team."
> * increment the version like this:
>   * if a package already e.g. had a +wheezy1 update, use +wheezy2 for the
> next update,
>   * if a package hasn't seen an update, use +deb7u1 for the next update.
> 
> Basically, the change is "s/squeeze/wheezy/" and "wheezy-security works
> now".

I happily stand corrected on all these details. Thanks!
 
> Since this may change again in the future before this issue is resolved,
> maybe it's better to just refer to the LTS notes here:
> https://wiki.debian.org/LTS/Development#Build_the_update

no. "dch --lts" should do the right thing - and just like "dch --bpo" it
will be outdated & in need of an update once in a while - each time we
release… \o/ yay! :)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#842424: rawtherapee: UI is too big. Tone curves are totally unusable.

[bernie]

Package: rawtherapee
Version: 4.2.1241-2
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



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

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

Versions of packages rawtherapee depends on:
ii  libatkmm-1.6-1v52.24.2-2
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.24-5
ii  libcairomm-1.0-1v5  1.12.0-1+b1
ii  libcanberra-gtk3-0  0.30-3
ii  libcanberra00.30-3
ii  libexpat1   2.2.0-1
ii  libfftw3-single33.3.5-1
ii  libgcc1 1:6.2.0-10
ii  libglib2.0-02.50.1-1
ii  libglibmm-2.4-1v5   2.50.0-1
ii  libgomp16.2.0-10
ii  libgtk-3-0  3.22.2-1
ii  libgtkmm-3.0-1v53.22.0-1
ii  libiptcdata01.0.4-6
ii  libjpeg62-turbo 1:1.5.1-2
ii  liblcms2-2  2.7-1
ii  libpangomm-1.4-1v5  2.40.1-3
ii  libpng16-16 1.6.26-1
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libstdc++6  6.2.0-10
ii  libtiff54.0.6-2
ii  rawtherapee-data4.2.1241-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

rawtherapee recommends no packages.

rawtherapee suggests no packages.

-- no debconf information

Bug#839843: /usr/bin/lxc-create: Ran rm -rf on an entire filesystem after failing to create a container

[Christian Brauner]

On Sat, Oct 29, 2016 at 12:38:40AM +0200, Christian Brauner wrote:
> On Wed, 05 Oct 2016 13:25:18 -0400 Matthew Gabeler-Lee
>  wrote:
> > Package: lxc
> > Version: 1:2.0.4-1
> > Severity: normal
> > File: /usr/bin/lxc-create
> >
> > I ran lxc-create to setup an image, and realized I had given it the wrong
> > arguments (wrong distro version, nothing dramatic), so I stopped it with
> > Ctrl-C and cleaned up the partial directory it left behind.
> >
> > Some time later, while in the process of setting up the container created
> > from using the correct arguments, I noticed many many things going wrong.
> > As I started to go WTF, this pops out on the console used for the original
> > incorrect lxc-create:
> >
> > lxc-destroy: utils.c: _recursive_rmdir: 170 _recursive_rmdir: failed to 
> > delete /scratch
> > lxc-destroy: lxccontainer.c: container_destroy: 2384 Error destroying 
> > rootfs for centos7-32bit-lxc
> > Container is not defined
> > exiting...
> >
> > It ran rm -rf on the ENTIRE FILESYSTEM CONTAINING ALL OF MY LXC IMAGES.
> >
> > Instead of doing an rm -rf on the container, it tried to do an rm -rf of the
> > directory in which the container was created, and since it had to be run as
> > root to create the container, it was pretty $#!%$ successful.
> >
> > reportbug wants me to quote chapter and verse from the policy manual to mark
> > this as a serious bug, but "don't rm -rf the entire OS" is so blatantly
> > obvious that there is no specific policy entry to reference.
> >
> >
> > -- System Information:
> > Debian Release: stretch/sid
> >   APT prefers testing
> >   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 4.7.0-1-amd64 (SMP w/8 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 lxc depends on:
> > ii  init-system-helpers  1.45
> > ii  libapparmor1 2.10.95-4+b1
> > ii  libc62.24-3
> > ii  libcap2  1:2.25-1
> > ii  liblxc1  1:2.0.4-1
> > ii  libseccomp2  2.3.1-2
> > ii  libselinux1  2.5-3
> > ii  python3  3.5.1-4
> > pn  python3:any  
> >
> > Versions of packages lxc recommends:
> > ii  bridge-utils  1.5-9
> > pn  cgmanager 
> > pn  debootstrap   
> > ii  dirmngr   2.1.15-3
> > ii  dnsmasq-base  2.76-4
> > ii  gnupg 2.1.15-3
> 
> Hi,
> 
> Can you please specify the exact commands you used to create the container,
> and the commands you used to clean up the partial directory. The
> partial directory
> should usually be cleaned up by LXC itself. So I'm wondering if this
> has anything
> to do with it. If it's not too much trouble, could you also file a bug against
> https://github.com/lxc/lxc and link in this one here?
> 
> Christian

On second look, there is something that confuses me about this bug report:
You said that you ran lxc-create and then Ctrl+Ced it and then:

> > As I started to go WTF, this pops out on the console used for the original
> > incorrect lxc-create:
> >
> > lxc-destroy: utils.c: _recursive_rmdir: 170 _recursive_rmdir: failed to 
> > delete /scratch
> > lxc-destroy: lxccontainer.c: container_destroy: 2384 Error destroying 
> > rootfs for centos7-32bit-lxc
> > Container is not defined
> > exiting...

This confuses me as the output can only come from running lxc-destroy. So you
must have called the lxc-destroy command. lxc-create would not cause this error
message to be printed. Again, to have any idea of what could possibly cause this
we need to know the exact commands you used.

Christian

Bug#842423: gnome-terminal: Regression? gnome-terminal copies text to the wrong X display, but pastes from the correct one

[Robert Ou]

Package: gnome-terminal
Version: 3.22.0-3
Severity: important

Dear Maintainer,

After updating packages, I discovered that I was unable to copy/paste
properly in gnome-terminal. After experimenting, I discovered that this
was related to how my system has two X displays (e.g. :0 and :1) at the
same time. If gnome-terminal is launched on display :1, it somehow
manages to copy text onto the clipboard of display :0. However, pasting
text will paste the text from the clipboard of display :1. This makes it
impossible to use copy/paste in gnome-terminal in any sane way because
copied text can no longer be pasted in the same window where the text was
originally copied from. A gnome-terminal launched on display :0 copy/pastes
correctly (from and to the clipboard of display :0).

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/20 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 gnome-terminal depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  gconf-service3.2.6-4
ii  gnome-terminal-data  3.22.0-3
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-5
ii  libdconf10.26.0-2
ii  libgconf-2-4 3.2.6-4
ii  libglib2.0-0 2.50.1-1
ii  libgtk-3-0   3.22.2-1
ii  libnautilus-extension1a  3.22.1-2
ii  libpango-1.0-0   1.40.3-3
ii  libuuid1 2.28.2-1
ii  libvte-2.91-00.46.0-1
ii  libx11-6 2:1.6.3-1

Versions of packages gnome-terminal recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.10.12-1
ii  dbus-x11 [dbus-session-bus]   1.10.12-1
ii  gvfs  1.30.1.1-1
ii  yelp  3.22.0-1

gnome-terminal suggests no packages.

-- no debconf information

Bug#842422: network-manager: NetworkManager fails to authenticate with old 802.11bg USB devices

[Vladimir Kudrya]

Package: network-manager
Version: 1.4.2-2
Severity: normal

Dear Maintainer, NetworkManager fails to connect to wireless network using 
802.11bg dongles.
The bug appeared somewhere around september upgrades on stretch (unfortunately, 
I can not pinpoint).

I am able to connect using wpa_supplicant directly:

# wpa_supplicant -i wlx  -c /tmp/wpapp 
Successfully initialized wpa_supplicant
wlx: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX 
(SSID='wlanssid' freq=2437 MHz)
wlx: Trying to associate with XX:XX:XX:XX:XX:XX 
(SSID='wlanssid' freq=2437 MHz)
wlx: Associated with XX:XX:XX:XX:XX:XX
wlx: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY 
alpha2=RU
wlx: WPA: Key negotiation completed with XX:XX:XX:XX:XX:XX 
[PTK=CCMP GTK=CCMP]
wlx: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:XX:XX 
completed [id=0 id_str=]
wlx: WPA: Group rekeying completed with XX:XX:XX:XX:XX:XX 
[GTK=CCMP]
wlx: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX:XX:XX 
reason=2 locally_generated=1
wlx: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlx: SME: Trying to authenticate with XX:XX:XX:XX:XX:XX 
(SSID='wlanssid' freq=2437 MHz)
wlx: Trying to associate with XX:XX:XX:XX:XX:XX 
(SSID='wlanssid' freq=2437 MHz)
wlx: Associated with XX:XX:XX:XX:XX:XX
wlx: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY 
alpha2=RU
wlx: WPA: Key negotiation completed with XX:XX:XX:XX:XX:XX 
[PTK=CCMP GTK=CCMP]
wlx: CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:XX:XX:XX 
completed [id=0 id_str=]
wlx: WPA: Group rekeying completed with XX:XX:XX:XX:XX:XX 
[GTK=CCMP]
^Cwlx: CTRL-EVENT-DISCONNECTED bssid=XX:XX:XX:XX:XX:XX 
reason=3 locally_generated=1
nl80211: deinit ifname=wlx disabled_11b_rates=0
wlx: CTRL-EVENT-TERMINATING

But when using NetworkManager, authentication fails:

Oct 29 02:09:02 hostname wpa_supplicant[22933]: wlx: SME: 
Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
Oct 29 02:09:02 hostname kernel: wlx: authenticate with 
XX:XX:XX:XX:XX:XX
Oct 29 02:09:02 hostname NetworkManager[8518]:   
[1477696142.2096] device (wlx): supplicant interface state: 
inactive -> authenticating
Oct 29 02:09:02 hostname kernel: wlx: send auth to 
XX:XX:XX:XX:XX:XX (try 1/3)
Oct 29 02:09:02 hostname kernel: wlx: authenticated
Oct 29 02:09:07 hostname kernel: wlx: aborting 
authentication with XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 29 02:09:07 hostname NetworkManager[8518]:   
[1477696147.2352] device (wlx): supplicant interface state: 
authenticating -> disconnected
Oct 29 02:09:07 hostname NetworkManager[8518]:   
[1477696147.3382] device (wlx): supplicant interface state: 
disconnected -> scanning
Oct 29 02:09:08 hostname wpa_supplicant[22933]: wlx: SME: 
Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
Oct 29 02:09:08 hostname kernel: wlx: authenticate with 
XX:XX:XX:XX:XX:XX
Oct 29 02:09:08 hostname kernel: wlx: send auth to 
XX:XX:XX:XX:XX:XX (try 1/3)
Oct 29 02:09:08 hostname NetworkManager[8518]:   
[1477696148.4705] device (wlx): supplicant interface state: 
scanning -> authenticating
Oct 29 02:09:08 hostname kernel: wlx: authenticated
Oct 29 02:09:13 hostname kernel: wlx: aborting 
authentication with XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 29 02:09:13 hostname NetworkManager[8518]:   
[1477696153.4989] device (wlx): supplicant interface state: 
authenticating -> disconnected
Oct 29 02:09:14 hostname NetworkManager[8518]:   
[1477696154.0034] device (wlx): supplicant interface state: 
disconnected -> scanning
Oct 29 02:09:15 hostname wpa_supplicant[22933]: wlx: SME: 
Trying to authenticate with XX:XX:XX:XX:XX:XX (SSID='wlanssid' freq=2437 MHz)
Oct 29 02:09:15 hostname kernel: wlx: authenticate with 
XX:XX:XX:XX:XX:XX
Oct 29 02:09:15 hostname NetworkManager[8518]:   
[1477696155.1391] device (wlx): supplicant interface state: 
scanning -> authenticating
Oct 29 02:09:15 hostname kernel: wlx: send auth to 
XX:XX:XX:XX:XX:XX (try 1/3)
Oct 29 02:09:15 hostname kernel: wlx: authenticated
Oct 29 02:09:20 hostname wpa_supplicant[22933]: wlx: SME: 
Deauth request to the driver failed
Oct 29 02:09:20 

Bug#842421: gnome-screensaver: Regression? Refusing to launch on a different X display

[Robert Ou]

Package: gnome-screensaver
Version: 3.6.1-7+b1
Severity: important

Dear Maintainer,

After updating packages, I discovered that gnome-screensaver is now
refusing to launch a second copy of itself on a different X display from
an existing copy. Before, this would Just Work, but now
gnome-screensaver explicitly complains "screensaver already running in
this session."

The particular way I have my system set up requires me to use
two separate X displays (e.g. :0 and :1). Before, I was able to lock
either display by running two copies of gnome-screensaver and running
"gnome-screensaver-command -l" with the appropriate DISPLAY setting.
Now, I am only able to ever lock one of the X displays because
gnome-screensaver won't launch a second copy and
gnome-screensaver-command communicates with the first copy regardless of
DISPLAY.

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/20 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 gnome-screensaver depends on:
ii  dbus-x11   1.10.12-1
ii  gnome-icon-theme   3.12.0-2
ii  gnome-session-bin  3.22.1-1
ii  gsettings-desktop-schemas  3.22.0-1
ii  libc6  2.24-5
ii  libcairo2  1.14.6-1+b1
ii  libdbus-1-31.10.12-1
ii  libdbus-glib-1-2   0.108-1
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libglib2.0-0   2.50.1-1
ii  libgnome-desktop-3-12  3.22.1-1
ii  libgnomekbd8   3.22.0.1-1
ii  libgtk-3-0 3.22.2-1
ii  libpam0g   1.1.8-3.3
ii  libsystemd0231-10
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxklavier16  5.4-2
ii  libxxf86vm11:1.1.4-1

Versions of packages gnome-screensaver recommends:
ii  gnome-power-manager   3.22.1-1
ii  libpam-gnome-keyring  3.20.0-3

gnome-screensaver suggests no packages.

-- no debconf information

Bug#842419: gnome-screensaver: Regression? Password prompt often will appear in the bottom right corner of the screen

[Robert Ou]

Package: gnome-screensaver
Version: 3.6.1-7+b1
Severity: important

Dear Maintainer,

After updating packages some time ago, I noticed that the
gnome-screensaver password prompt will now appear only in the bottom
right corner of the screen most of the time. See this link for
clarification: https://goo.gl/photos/pKiCeJU1j3vwv6f2A . This makes it
impossible to click any of the buttons, but you can still type a
password and press enter to unlock the screen.

I have not figured out what causes the password prompt to appear in the
corner, but it seems to happen 100% of the time on my laptop and has
happened once so far on my desktop. I expected the password prompt to
appear in the center of the screen every time.

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/20 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 gnome-screensaver depends on:
ii  dbus-x11   1.10.12-1
ii  gnome-icon-theme   3.12.0-2
ii  gnome-session-bin  3.22.1-1
ii  gsettings-desktop-schemas  3.22.0-1
ii  libc6  2.24-5
ii  libcairo2  1.14.6-1+b1
ii  libdbus-1-31.10.12-1
ii  libdbus-glib-1-2   0.108-1
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libglib2.0-0   2.50.1-1
ii  libgnome-desktop-3-12  3.22.1-1
ii  libgnomekbd8   3.22.0.1-1
ii  libgtk-3-0 3.22.2-1
ii  libpam0g   1.1.8-3.3
ii  libsystemd0231-10
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxklavier16  5.4-2
ii  libxxf86vm11:1.1.4-1

Versions of packages gnome-screensaver recommends:
ii  gnome-power-manager   3.22.1-1
ii  libpam-gnome-keyring  3.20.0-3

gnome-screensaver suggests no packages.

-- no debconf information

Bug#842420: RFP: electron -- Build cross platform desktop apps with JavaScript, HTML, and CSS

[Jeffrey Cliff]

Package: wnpp
Severity: wishlist

The Electron framework lets you write cross-platform desktop applications
using JavaScript, HTML and CSS. It is based on Node.js 
and Chromium  and is used by the Atom editor
 and many other apps
.

Website: https://github.com/electron/electron

License: MIT https://github.com/electron/electron/blob/master/LICENSE

Bug#842418: nvidia-driver fails to install

[Nigel Horne]

Package: nvidia-driver
Severity: normal

My nvidia card has stopped working in anything other than 1024x768 mode
since Linux 4.5.  Seeing as this makes my desktop unusuable I thought I'd
ditch the nouveau driver and try the nvidia driver.

However that won't install

apt-get install  nvidia-driver 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-driver : PreDepends: nvidia-installer-cleanup but it is not installable
 PreDepends: nvidia-legacy-check (>= 343) but it is not going 
to be installed
 Depends: nvidia-driver-libs (= 367.44-3) but it is not going 
to be installed
 Depends: nvidia-driver-bin (= 367.44-3) but it is not going to 
be installed
 Depends: xserver-xorg-video-nvidia (= 367.44-3) but it is not 
going to be installed
 Depends: nvidia-vdpau-driver (= 367.44-3) but it is not going 
to be installed
 Depends: nvidia-alternative (= 367.44-3) but it is not going 
to be installed
 Depends: nvidia-kernel-dkms (= 367.44-3) but it is not going 
to be installed or
  nvidia-kernel-367.44
 Depends: nvidia-support but it is not installable
 Recommends: nvidia-settings (>= 367) but it is not installable
 Recommends: nvidia-persistenced but it is not installable
E: Unable to correct problems, you have held broken packages.


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

Kernel: Linux 4.7.0-1-amd64 (SMP w/20 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)

Bug#840145: ejabberd: mod_irc fails to handle server configuration

[Dominik George]

Hi,

> I am unable to reproduce your problem,
> please upgrade to ejabberd 16.09-2 and try again.

No change, as expected.

> 
> If the problem persists, I need your full ejabberd.yml (you can send it
> privately to me).

Find it attached (stripped of passwords).

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Contributor

LPIC-3 Linux Enterprise Professional (Security)
###
###'  ejabberd configuration file
###
###

### The parameters used in this configuration file are explained in more detail
### in the ejabberd Installation and Operation Guide.
### Please consult the Guide in case of doubts, it is included with
### your copy of ejabberd, and is also available online at
### http://www.process-one.net/en/ejabberd/docs/

### The configuration file is written in YAML.
### Refer to http://en.wikipedia.org/wiki/YAML for the brief description.
### However, ejabberd treats different literals as different types:
###
### - unquoted or single-quoted strings. They are called "atoms".
###   Example: dog, 'Jupiter', '3.14159', YELLOW
###
### - numeric literals. Example: 3, -45.0, .0
###
### - quoted or folded strings.
###   Examples of quoted string: "Lizzard", "orange".
###   Example of folded string:
###   > Art thou not Romeo,
### and a Montague?

###.  ===
###'  LOGGING

##
## loglevel: Verbosity of log files generated by ejabberd.
## 0: No ejabberd log at all (not recommended)
## 1: Critical
## 2: Error
## 3: Warning
## 4: Info
## 5: Debug
##
loglevel: 4

##
## rotation: Disable ejabberd's internal log rotation, as the Debian package
## uses logrotate(8).
log_rotate_size: 0
log_rotate_date: ""

##
## overload protection: If you want to limit the number of messages per second
## allowed from error_logger, which is a good idea if you want to avoid a flood
## of messages when system is overloaded, you can set a limit.
## 100 is ejabberd's default.
log_rate_limit: 100

##
## watchdog_admins: Only useful for developers: if an ejabberd process
## consumes a lot of memory, send live notifications to these XMPP
## accounts.
##
## watchdog_admins:
##   - "b...@example.com"

###.  ===
###'  NODE PARAMETERS

##
## net_ticktime: Specifies net_kernel tick time in seconds. This options must 
have
## identical value on all nodes, and in most cases shouldn't be changed at all 
from
## default value.
##
## net_ticktime: 60

###.  
###'  SERVED HOSTNAMES

##
## hosts: Domains served by ejabberd.
## You can define one or several, for example:
## hosts: 
##   - "example.net"
##   - "example.com"
##   - "example.org"
##
hosts:
  - "naturalnet.de"

##
## route_subdomains: Delegate subdomains to other XMPP servers.
## For example, if this ejabberd serves example.org and you want
## to allow communication with an XMPP server called im.example.org.
##
## route_subdomains: s2s

###.  ===
###'  LISTENING PORTS

##
## listen: The ports ejabberd will listen on, which service each is handled
## by and what options to start it with.
##
listen: 
  - 
port: 5222
ip: "::"
module: ejabberd_c2s
##
## If TLS is compiled in and you installed a SSL
## certificate, specify the full path to the
## file and uncomment these lines:
##
certfile: "/etc/letsencrypt/live/shore.naturalnet.de/all.pem"
## starttls: true
##
## To enforce TLS encryption for client connections,
## use this instead of the "starttls" option:
##
starttls_required: true
##
## Custom OpenSSL options
##
protocol_options:
  - "no_sslv3"
##   - "no_tlsv1"
max_stanza_size: 65536
shaper: c2s_shaper
access: c2s
zlib: true
resend_on_timeout: if_offline
  - 
port: 5223
ip: "::"
module: ejabberd_c2s
certfile: "/etc/letsencrypt/live/shore.naturalnet.de/all.pem"
tls: true
##
## Custom OpenSSL options
##
protocol_options:
  - "no_sslv3"
##   - "no_tlsv1"
max_stanza_size: 65536
shaper: c2s_shaper
access: c2s
zlib: true
resend_on_timeout: if_offline
  - 
port: 5269
ip: "::"
module: ejabberd_s2s_in
  ##
  ## ejabberd_service: Interact with external components (transports, ...)
  ##
#  - 
#port: 5347
#module: ejabberd_service
#access: all
#shaper_rule: fast
#ip: "127.0.0.1"

  ##
  ## ejabberd_stun: Handles STUN Binding requests
  ##
  - 
port: 3478
transport: udp
module: ejabberd_stun
use_turn: true
auth_type: anonymous
turn_ip: "217.144.132.152"
turn_min_port: 49152
turn_max_port: 50152
  - 
port: 3478
module: ejabberd_stun
use_turn: true
auth_type: anonymous
turn_ip: "217.144.132.152"
turn_min_port: 49152
turn_max_port: 50152
  - 
  

Bug#830961: jessie-backports upload ?

[Mattia Rizzolo]

On Wed, Jul 13, 2016 at 12:22:51PM +0200, Didier 'OdyX' Raboud wrote:
> I'd be interested in a taskd package installable on jessie; would you be
> interested in uploading it to jessie-backports?
> 
> I've tried to build taskd on jessie-backports and it is straightforward; and
> I'd be willing to upload it. Do you want to do it yourself or should I 
> proceed?

I'm interested too, and I'd be equally happy to take care of backporting
it myself.

Would you mind? :)

-- 
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#839843: /usr/bin/lxc-create: Ran rm -rf on an entire filesystem after failing to create a container

[Christian Brauner]

On Wed, 05 Oct 2016 13:25:18 -0400 Matthew Gabeler-Lee
 wrote:
> Package: lxc
> Version: 1:2.0.4-1
> Severity: normal
> File: /usr/bin/lxc-create
>
> I ran lxc-create to setup an image, and realized I had given it the wrong
> arguments (wrong distro version, nothing dramatic), so I stopped it with
> Ctrl-C and cleaned up the partial directory it left behind.
>
> Some time later, while in the process of setting up the container created
> from using the correct arguments, I noticed many many things going wrong.
> As I started to go WTF, this pops out on the console used for the original
> incorrect lxc-create:
>
> lxc-destroy: utils.c: _recursive_rmdir: 170 _recursive_rmdir: failed to 
> delete /scratch
> lxc-destroy: lxccontainer.c: container_destroy: 2384 Error destroying rootfs 
> for centos7-32bit-lxc
> Container is not defined
> exiting...
>
> It ran rm -rf on the ENTIRE FILESYSTEM CONTAINING ALL OF MY LXC IMAGES.
>
> Instead of doing an rm -rf on the container, it tried to do an rm -rf of the
> directory in which the container was created, and since it had to be run as
> root to create the container, it was pretty $#!%$ successful.
>
> reportbug wants me to quote chapter and verse from the policy manual to mark
> this as a serious bug, but "don't rm -rf the entire OS" is so blatantly
> obvious that there is no specific policy entry to reference.
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.7.0-1-amd64 (SMP w/8 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 lxc depends on:
> ii  init-system-helpers  1.45
> ii  libapparmor1 2.10.95-4+b1
> ii  libc62.24-3
> ii  libcap2  1:2.25-1
> ii  liblxc1  1:2.0.4-1
> ii  libseccomp2  2.3.1-2
> ii  libselinux1  2.5-3
> ii  python3  3.5.1-4
> pn  python3:any  
>
> Versions of packages lxc recommends:
> ii  bridge-utils  1.5-9
> pn  cgmanager 
> pn  debootstrap   
> ii  dirmngr   2.1.15-3
> ii  dnsmasq-base  2.76-4
> ii  gnupg 2.1.15-3

Hi,

Can you please specify the exact commands you used to create the container,
and the commands you used to clean up the partial directory. The
partial directory
should usually be cleaned up by LXC itself. So I'm wondering if this
has anything
to do with it. If it's not too much trouble, could you also file a bug against
https://github.com/lxc/lxc and link in this one here?

Christian

Bug#832247: closed by Antonio Terceiro <terce...@debian.org> (Bug#832247: fixed in origami-pdf 2.0.0-1)

[Ben Finney]

On 28-Oct-2016, Debian Bug Tracking System wrote:

>* Change Section: to `utils` (Closes: #832247)

Thank you for fixing the source package. Which is the bug report for
fixing the archive?

As described in the original message:

> Since the package is already in Debian with a different section, you
> will also need to submit a request to override the existing section
> .
> 
> Then mark this bug report as blocked by that new one, and be sure not
> to close this one until that new one is completed.

-- 
 \   “Too many Indians spoil the golden egg.” —Sir Joh |
  `\   Bjelke-Petersen |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#832203: closed by Timo Aaltonen <tjaal...@debian.org> (Bug#832203: fixed in custodia 0.1.0-6)

[Ben Finney]

On 27-Oct-2016, Debian Bug Tracking System wrote:

>* control: Fix section. (Closes: #832203)

Thank you for fixing the source package. Which is the bug report for
fixing the archive?

As described in the original message:

> Since the package is already in Debian with a different section, you
> will also need to submit a request to override the existing section
> .
> 
> Then mark this bug report as blocked by that new one, and be sure not
> to close this one until that new one is completed.

-- 
 \   “If you do not trust the source do not use this program.” |
  `\—Microsoft Vista security dialogue |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#842417: TAG: Nightingale -- media player and library

[David HILL]

Package: wnpp
Severity: RFP


Some information about the package


https://getnightingale.com/

https://getnightingale.com/all-versions.php

https://github.com/nightingale-media-player

http://wiki.getnightingale.com/doku.php?id=licensing


GNU General Public License version 2.0 
(GPLv2), Mozilla Public License 
1.1 (MPL 1.1)

Bug#842416: Some Breaks and Replaces are missed for Qt4 and Qt5 version

[Alf Gaida]

Package: libqt5keychain1
Version: 0.7.0-2.1
Severity: serious
Tags: patch

Hi,
the package lacks some breaks and replaces:
dpkg: error processing archive 
/var/cache/apt/archives/libqt5keychain1_0.7.0-2_amd64.deb (--unpack):
 trying to overwrite '/usr/share/qt5/translations/qtkeychain_de.qm', which is 
also in package libqt5keychain0:amd64 0.5.0-1

Patch attached

Cheers Alf


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

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

Versions of packages libqt5keychain1 depends on:
ii  libc6 2.24-5
ii  libgcc1   1:6.2.0-10
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5dbus5   5.6.1+dfsg-3+b1
ii  libstdc++66.2.0-10

Versions of packages libqt5keychain1 recommends:
ii  gnome-keyring  3.20.0-3

libqt5keychain1 suggests no packages.

-- no debconf information
diff --git a/debian/control b/debian/control
index add7a8c..b83862d 100644
--- a/debian/control
+++ b/debian/control
@@ -20,6 +20,8 @@ Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Pre-Depends: ${misc:Pre-Depends}
 Recommends: gnome-keyring | kde-runtime
+Breaks: libqtkeychain0
+Replaces: libqtkeychain0
 Description: Qt API to store passwords
  It can use KWallet or GNOME Keyring, if one of them is available.
  If none of them is available, qtkeychain will report an error or writes
@@ -43,6 +45,8 @@ Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Pre-Depends: ${misc:Pre-Depends}
 Recommends: gnome-keyring | kwalletmanager
+Breaks: libqt5keychain0
+Replaces: libqt5keychain0
 Description: Qt API to store passwords (QT5 version)
  It can use KWallet or GNOME Keyring, if one of them is available.
  If none of them is available, qtkeychain will report an error or writes

Bug#842315: Misdetects systemd with merged-usr

[Felipe Sateler]

Package: grub-common
Version: 2.02~beta3-1
Followup-For: Bug #842315
Control: tags -1 patch

Hi,

This patch fixes the issue. It is as simple as resolving the
symlinks for the known names as well:

--- /etc/grub.d/10_linux2016-10-28 19:02:21.057213089 -0300
+++ 10_linux2016-10-28 19:02:43.841806736 -0300
@@ -349,7 +349,7 @@
   "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_LINUX_DEFAULT}"
   for supported_init in ${SUPPORTED_INITS}; do
 init_path="${supported_init#*:}"
-if [ -x "${init_path}" ] && [ "$(readlink -f /sbin/init)" != 
"${init_path}" ]; then
+if [ -x "${init_path}" ] && [ "$(readlink -f /sbin/init)" != "$(readlink 
-f ${init_path})" ]; then
   linux_entry "${OS}" "${version}" "init-${supported_init%%:*}" \
  "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_LINUX_DEFAULT} 
init=${init_path}"
 fi


Saludos

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

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

Versions of packages grub-common depends on:
ii  gettext-base0.19.8.1-1
ii  libc6   2.24-5
ii  libdevmapper1.02.1  2:1.02.133-1
ii  libfreetype62.6.3-3+b1
ii  libfuse22.9.7-1
ii  liblzma55.2.2-1.2

Versions of packages grub-common recommends:
ii  os-prober  1.71

Versions of packages grub-common suggests:
pn  console-setup  
ii  desktop-base   8.0.2
pn  grub-emu   
pn  multiboot-doc  
pn  xorriso

-- Configuration Files:
/etc/grub.d/10_linux changed [not included]

-- no debconf information

Bug#842415: TAG: fre:ac-- free audio converter and CD ripper

[David HILL]

Package: wnpp
Severity: RFP


Some information about the package


https://www.freac.org/


https://sourceforge.net/projects/bonkenc/



GNU General Public License version 2.0 
(GPLv2)

Bug#842414: linux-image-4.7.0-1-686-pae fails to boot, stops right after GRUB

[Vladimir Kudrya]

Package: src:linux
Version: 4.7.8-1
Severity: normal

Dear Maintainer, after recent kernel upgrade my old laptop fails to boot. All 
visible activity is stopped
right after GRUB, no logs being written.

I've found similar reports (for newer kernel) with a possible lead to a fix:
https://bugs.archlinux.org/task/51506
http://www.gossamer-threads.com/lists/linux/kernel/2551992
https://github.com/torvalds/linux/commit/ff8560512b8d4b7ca3ef4fd69166634ac30b2525

Also relevant Debian mailing list:
https://lists.debian.org/debian-user/2016/10/msg00753.html

-- Package-specific info:
** Kernel log: No log is produced, kernel is not loaded.

** CPU: Intel(R) Celeron(R) M processor 1500MHz

** Model information

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O 
Controller [8086:3340] (rev 21)
Subsystem: LG Electronics, Inc. 82855PM Processor to I/O Controller 
[1854:0003]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: agpgart-intel

00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP 
Controller [8086:3341] (rev 21) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Kernel modules: shpchp

00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 03) (prog-if 00 
[UHCI])
Subsystem: LG Electronics, Inc. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller [1854:0003]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
[8086:2448] (rev 83) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Kernel modules: shpchp

00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface 
Bridge [8086:24cc] (rev 03)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: snd_intel8x0
Kernel modules: snd_intel8x0

00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
AC'97 Modem Controller [8086:24c6] (rev 03) (prog-if 00 [Generic])
Subsystem: LG Electronics, Inc. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
AC'97 Modem Controller [1854:0003]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: snd_intel8x0m
Kernel modules: snd_intel8x0m

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RV280/M9+ [Mobility Radeon 9200 AGP] [1002:5c63] (rev 01) (prog-if 00 
[VGA controller])
Subsystem: LG Electronics, Inc. RV280/M9+ [Mobility Radeon 9200 AGP] 
[1854:0003]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B+ DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: radeon
Kernel modules: radeonfb, radeon

02:00.0 CardBus bridge [0607]: Texas Instruments PCI7420 CardBus Controller 
[104c:ac8e]
Subsystem: LG Electronics, Inc. PCI7420 CardBus Controller [1854:0003]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
Capabilities: 
Kernel driver in use: yenta_cardbus
Kernel modules: yenta_socket

02:00.2 FireWire (IEEE 1394) [0c00]: Texas 

Bug#842413: TAG: Quick Hash GUI -- Hashing GUI Tool

[David HILL]

Package: wnpp
Severity: RFP


Some information about the package


https://sourceforge.net/projects/quickhash/


https://github.com/tedsmith/quickhash/releases


GNU General Public License version 2.0 
(GPLv2)

Bug#810146:

[salsaman]

This bug can be closed with the release of LiVES 2.8.1

Bug#756565:

[salsaman]

This bug can be closed with the release of LiVES 2.8.1

Bug#798043:

[salsaman]

This bug can be closed with the release of LiVES 2.8.1

Bug#842412: TAG: Money Manager Ex -- Is an easy to use, money management application

[David HILL]

Package: wnpp
Severity: RFP



Some information about the package


https://github.com/moneymanagerex/moneymanagerex/releases


https://github.com/moneymanagerex


https://sourceforge.net/projects/moneymanagerex/



http://www.moneymanagerex.org/




http://www.moneymanagerex.org/about/license

Bug#842348: Patch: Let linspace accept input that has an array_interface...

[Sandro Tosi]

that patch is not even merged upstream in any branch, so pursue that
first than having the debian package be patched.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#842411: iptraf-ng should offer iptraf command and transitional package

[Adrian Bunk]

Package: iptraf-ng
Version: 1.1.4-3
Severity: normal

After the removal of iptraf from unstable (see #842355),
iptraf-ng should provide an iptraf command and an iptraf
transitional package to ease the iptraf -> iptraf-ng
migration for people upgrading from jessie to stretch.

Bug#798212: node-indent-string ITPs with different owners

[Adrian Bunk]

Control: forcemerge -1 842321

Hi Bastien, hi Sarath,

you both submitted ITPs for node-indent-string.

Please coordinate and agree who will package node-indent-string.

Thanks
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#798278: node-tape ITPs with different owners

[Adrian Bunk]

Control: forcemerge -1 842327

Hi Ross, hi Lucas,

you both submitted ITPs for node-tape.

Please coordinate and agree who will package node-tape.

Thanks
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#842410: ableton-link: FTBFS: -m64 considered harmful

[Aaron M. Ucko]

Source: ableton-link
Version: 1.0.0+dfsg-1
Severity: important
Justification: fails to build from source

Builds of ableton-link for most architectures failed due to its
explicit use of -m64.  This option is appropriate for Debian package
builds only in very specialized circumstances, since the compiler
already targets the system's native architecture by default; please
fix the build system not to supply -m64 at all.

Thanks!

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

Bug#842409: Subject: debian-installer: Partitioner alters current swap UUID's

[DAVID]

Subject: debian-installer: Partitioner alters current swap UUID's
Package: debian-installer
Severity: minor

Dear Maintainer,

Installing Debian 8.6.0, at the completion of partitioning, the installer finds
all the swap partitions on other installations on other drives and will not 
proceed
until I confirm. Then it reformats all those swap partitions, changing their 
UUID's.
Then when trying to boot one of those other Debian operating systems, systemd 
will
not recognise the swap from fstab, timing out or sometimes entering recovery 
mode
until I alter fstab to its new swap UUID.

I work round this by deleting all swap partitions and commenting out the 
references in
fstabs before an installation.

I would like the installer to give me an option to create swaps or bypass.

dsd

-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (750, 'stable'), (500, 'testing'), (250, 'unstable')
Architecture: amd64 (x86_64)

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

Bug#828521: Severity shouldn't be serious

[Thomas Goirand]

Hi,

Until OpenSSL 1.1.0 is in Sid, there's no reason to have the bug
severity raised to serious. Currently, it's only in Experimental.

Cheers,

Thomas Goirand (zigo)

Bug#797530: 32bit pie memory layout leaves only ~100MB between heap and stack

[Florian Weimer]

* Christoph Berg:

> More details:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518483

Why do you consider this a security issue?  Do you consider it an
availability issue?

I'm a bit confused why this shows up as a userspace allocation
failure.  glibc should switch to mmap (creating another arena) if sbrk
fails.  I thought we had logic for that in malloc, but the whole code
is kind of convoluted, so it is difficult to be sure.

Bug#842408: Acknowledgement (qt4-designer: SIGSEGV with designer-qt4)

[Antti Järvinen]

Please find full GDB log attached to this message.

--
Antti


designer-qt4.out
Description: debugger output

Bug#842117: file: detect MacWrite II documents

[Christoph Biedl]

Christoph Biedl wrote...

> Um, I can certainly prepare something for upstream to include, however
> the sample you provided does not match the description:
> 
>   fe 37 00 1c 00 00 00 00  00 00 28 00 00 19 00 00  |.7(.|
> 0010  00 00 00 00 00 00 01 00  00 00 75 35 00 01 0b 3f  |..u5...?|
> (...)

Some research reveals this is actually Word for Mac versions 4 or 5.
The libreoffice suite can open this file, although the rendering looks
a bit weird. I however failed to derive the file format from the
code in sw/source/filter/ww8/ww8scan.cxx.

Christoph



signature.asc
Description: Digital signature

Bug#842408: qt4-designer: SIGSEGV with designer-qt4

[Antti Järvinen]

Package: qt4-designer
Version: 4:4.8.7+dfsg-9
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I suspect this bug is due to malfunction inside libkio5 but I'm 
reporting it against qt4-designer because that is the way I can produce 
the bug every time. 

Initial setup is this:
 - debian testing up to date.
 - $HOME is mounted via nfs. This may have something to do with 
   the issue because previously I've had sometimes issues with
   KDE-related parts while having $HOME as network file system. 
   While having problems there, the error situation always is
   "too many open files" e.g. it seems like something in KDE is
   leaking file descriptors while $HOME is mounted via nfs.
 - run "gdb designer-qt4" or just plain "designer-qt4" is less details
   about crash are wanted.
 - select "open" from "file" menu

->
BFD: reopening /lib/x86_64-linux-gnu/libdbus-1.so.3: Too many open files in 
system

Can't read data for section '.eh_frame' in file 
'/lib/x86_64-linux-gnu/libdbus-1.so.3'
warning: unable to open /proc file '/proc/3344/status'

Thread 1 received signal SIGSEGV, Segmentation fault.
0x7fffeae16c39 in KFileDialog::KFileDialog (this=0x7fffd450, 
startDir=..., filter=..., parent=, 
customWidget=) at ./kio/kfile/kfiledialog.cpp:266


I'll follow-up to this post and attach the full gdb log of the process 
crashing if that helps at all.

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

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

Versions of packages qt4-designer depends on:
ii  libc62.24-5
ii  libgcc1  1:6.2.0-9
ii  libqt4-designer  4:4.8.7+dfsg-9
ii  libqt4-network   4:4.8.7+dfsg-9
ii  libqt4-xml   4:4.8.7+dfsg-9
ii  libqtcore4   4:4.8.7+dfsg-9
ii  libqtgui44:4.8.7+dfsg-9
ii  libstdc++6   6.2.0-9
ii  qtchooser58-gfab25f1-1

Versions of packages qt4-designer recommends:
ii  libqt4-dev  4:4.8.7+dfsg-9

qt4-designer suggests no packages.

-- no debconf information

Bug#838517: lxc-alpine template broken

[Evgeni Golov]

control: tags -1 + patch

Hi Alexander,

On Wed, Sep 21, 2016 at 10:11:16PM +0200, Alexander Schier wrote:
> the alpine template for lxc seem to be broken:
> 
> $ LANG=C lxc-create -n mycontainer -t alpine
> Verification Failure

Thanks for the report!
This is fixed upstream in https://github.com/lxc/lxc/issues/609 and available 
in Debian since LXC 2.0.

If you do not want to upgrade to LXC 2.0 yet, the patch is trivial:
 https://github.com/lxc/lxc/commit/e00f9e4e7ab5a76cfd4068e09579f9f471666a90

We might include it in a stable update, but won't promise it :)

Greets
Evgeni

Bug#842372: [SOLVED] Re: Bug#842372: Acknowledgement (kernel-package: Not compile new kernel.)

[Santiago José López Borrazás]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

El 28/10/16 a las 16:54, Debian Bug Tracking System escribió:

Solved. I installed packages on the GCC 6, and not compatibility.

Is compatible on the GCC 5. Is solved and marked.

I do not know why, if having the updated bundles that he me would have
already to be settled to be able to compile the kernel's in the GCC 6, but
I see that not, I have to resort to the GCC 5. But it is already.

In this moment is compile kernel 4.8.5, not fail and working compilation.

Thanks.

- -- 
Saludos de Santiago José López Borrazás.
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYE7XRAAoJEIFZAuZYtJmMUmoP/i6GIizv8p2+ZydTKuhHaN53
I0T+KM2CmOvxHo6LCi6EtvUXi4fBMUTAxi+STOJPJg60Dy8qt8Lg8J0xomKz17WM
8Ff2TQgWn9HWfEZdGeU+rTTf+jdx+5QYfgNLzUAqlX+5Tw65F55ujuZxQHIEBpx6
34C9PN0J/9Fb9WfLkX8rEU7/N+uvT0c7n6AxS4UexmGK+IrWFwpXhZRq6IixNYMB
iFj8u/Sabo4uaj6rFMM9PNMrqK7EnO4B9869FyQgsHuuGlInzpelIQO0+9CKvep0
Aaeyv2zOwMhHWFnekV0SJX2FXec4LfEgYWrJVC+jAXQ9KgWr8u72HD0kvtYzGrrd
3pS1jO0DY9znDkLKtyp1UCCzAfkszwZs4qae5f55/u25DmpBg8T40GSMhx3tA98P
x0w/XDZoO/U1/HzCbBaJ6rVuAMCmCjIrqfmEFtzJmgDTCjoldvxnN6hGYv11pxBw
b+xiV7N4c6tp9yhoEJLQW5tZxNQR9GgmAB5s5jpX77K3gGSy2z43Yg3OvZ3mU9JN
uHXiALqWR6355vutdFvf3RVC+Bsd+fs0WJTyu7gH7khBy7/d6B0cfmvjUBjncdZw
xTIY+rQvQT+awRaGRD0+H2UV70RFYGApErGvyCO9sHW7exx8YyDi7t7xFdxMqoWQ
RkVOsJqa71O5vUvKILIr
=RrVz
-END PGP SIGNATURE-

Bug#840674: (no subject)

[ZenWalker]

currently, amule works misteriously

this bug was solved, I don't know why

can someone confirm?

Bug#842407: gcj-6-jre-headless: adequate reports numerous broken symlinks for manpages

[shirish शिरीष]

Package: gcj-6-jre-headless
Version: 6.2.0-9
Severity: normal
User: debian...@lists.debian.org
Usertags: broken-symlink adequate

Dear Maintainer,
Adequate reports various broken symlinks for gcj-6-jre-headless.
Please fix them.

[$] adequate gcj-6-jre-headless

gcj-6-jre-headless: broken-symlink /usr/share/man/man1/gkeytool-6.1.gz
-> x86_64-linux-gnu-gnat-6.1.gz
gcj-6-jre-headless: broken-symlink /usr/share/man/man1/gorbd-6.1.gz ->
x86_64-linux-gnu-gnat-6.1.gz
gcj-6-jre-headless: broken-symlink /usr/share/man/man1/grmid-6.1.gz ->
x86_64-linux-gnu-gnat-6.1.gz
gcj-6-jre-headless: broken-symlink
/usr/share/man/man1/grmiregistry-6.1.gz ->
x86_64-linux-gnu-gnat-6.1.gz
gcj-6-jre-headless: broken-symlink
/usr/share/man/man1/gtnameserv-6.1.gz -> x86_64-linux-gnu-gnat-6.1.gz

And this is easily proved by for e.g. -

[$] man gtnameserv-6.1.gz

No manual entry for gtnameserv-6.1.gz


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

Kernel: Linux 4.7.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 gcj-6-jre-headless depends on:
ii  gcc-6-base 6.2.0-9
ii  gcj-6-jre-lib  6.2.0-9
ii  libc6  2.24-5
ii  libgcc11:6.2.0-9
ii  libgcj17   6.2.0-9
ii  zlib1g 1:1.2.8.dfsg-2+b1

gcj-6-jre-headless recommends no packages.

Versions of packages gcj-6-jre-headless suggests:
ii  fastjar   2:0.98-6
pn  gcj-6-jdk 
ii  libgcj17-awt  6.2.0-9

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#839104: (no subject)

[ZenWalker]

I can confirm

extremetuxracer works

# aptitude safe-upgrade libsfml-window2.4 -t experimental

thanks :)

Bug#840193: (no subject) [liferea: missing depends for plugins]

[Paul Gevers]

Hi ZenWalker,

On 28-10-16 00:24, ZenWalker wrote:
> Paul Gevers, I don't understand why you changed the title.
> 
> The new title has nothing to do with the original bug.

Please see my comments in message #47:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840193#47

What isn't clear there?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#842406: RFS: sysbench/1.0~20161026git0.7085367-1 [ITA] [RC]

[JCF Ploemen]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for "sysbench":

  Package name: sysbench
  Version : 1.0~20161026git0.7085367-1
  Upstream Author : Alexey Kopytov
  URL : https://github.com/akopytov/sysbench
  License : GPL-2
  Section : misc

It builds a single binary package:
  sysbench - multi-threaded benchmark tool for database systems

Mentors URL:
  https://mentors.debian.net/package/sysbench

Download with dget:
  dget -x 
https://mentors.debian.net/debian/pool/main/s/sysbench/sysbench_1.0~20161026git0.7085367-1.dsc

Changes since last upload:
  * New upstream version:
+ no longer links against libmysqlclient_r. (Closes: #825083)
  * New maintainer. (Closes: #841528)
  * Remove d/dirs: not needed just to create /usr/bin.
  * Docs:
+ stop installing upstream TODO (empty file).
+ replace README with README.md (renamed upstream).
+ include doc-base entry for html manual.
  * Add get-orig-source target to compensate for upstream not tagging
releases, with a combination of git branch, commit date and hash
used for versioning. Also strips a convenience copy of lua 5.1
from upstream sources.
  * Rules:
+ switch to dh sequencer with autoreconf; also avoids issues with
  autotools version changes. (Closes: #797260)
+ override dh_auto_configure to enable pgsql database driver.
+ enable all hardening.
  * Control:
+ remove build-depends on cdbs, autoconf, automake, and libtool
  (switch to dh with autoreconf).
+ replace build-depends on obsolete libmysqlclient-dev and its
  alternative libmysqlclient15-dev by default-libmysqlclient-dev.
  (Closes: #790475)
+ add build-depends on libaio-dev (asynchronous I/O mode support)
  (LP: #1009126), libpq-dev (for the postgresql database driver),
  python-cram (to run tests at build time), txt2man (to generate
  manpage during build), git (required by d/get-orig-source.sh)
  and liblua5.1-0-dev (see get-orig-source and/or patch 01).
+ set upstream homepage to their github page.
+ enhance short description to include mention of focus on database
  systems.
+ fix typo in long description.
+ update VCS links.
+ bump Standards-Version to 3.9.8 (from 3.9.5).
  * Patches:
+ drop old patch in order to re-enable building html manual.
+ add 01_use_system_lua: make buildsys use system lua headers)
+ add 02_fix_typo: self-explanatory.
+ add 03_dont_install_tests: already run at build time.
+ add 04_force_build_of_html_manual: bypass broken check for
  xsltproc to prevent inclusion of an empty html manual.
  (Closes: #695377)
  * Watch: limit to just comments documenting the lack of releases.
  * Remove d/TODO, all done now that postgresql support is builtin.
  * Manpage:
+ dump outdated debian/sysbench.xml and recreate based on help
  output, eliminating some typos in the process. (Closes: #793428)
+ remove incorrect examples. (Closes: #692822)
+ include options of various test modes. (LP: #1309532)
  * Copyright:
+ correct Format URI for machine-readable copyright spec.
+ update all upstream copyright and contact info.
+ add myself as a copyright holder for the packaging.


Regards.


pgpetxG2todUs.pgp
Description: OpenPGP digital signature

Bug#842405: paraview: can't load hdf5 file: vtkSISourceProxy: Failed to create vtkXdmfReader

[Drew Parsons]

Package: paraview
Version: 5.1.2+dfsg1-1+b1
Severity: normal

I'm trying to load a 1D HDF5 dataset (attached) into paraview, but it's crashing
with 

ERROR: In 
/build/paraview-MvSREd/paraview-5.1.2+dfsg1/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx,
 line 310
vtkSISourceProxy (0x333fce0): Failed to create vtkXdmfReader. Aborting for 
debugging purposes.

Is this normal?

Reports on the web suggest this might happen when there is something
wrong with the build,
cf. http://public.kitware.com/pipermail/paraview/2016-March/036420.html



The backtrace is
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#1  0x7401740a in __GI_abort () at abort.c:89
#2  0x72a2c35e in 
vtkSIProxy::CreateVTKObjects(paraview_protobuf::Message*) () from 
/usr/lib/paraview/libvtkPVServerImplementationCore.so.1
#3  0x72a41eb8 in 
vtkSISourceProxy::CreateVTKObjects(paraview_protobuf::Message*) () from 
/usr/lib/paraview/libvtkPVServerImplementationCore.so.1
#4  0x72a276ed in vtkSIProxy::Push(paraview_protobuf::Message*) () from 
/usr/lib/paraview/libvtkPVServerImplementationCore.so.1
#5  0x729ffe1a in 
vtkPVSessionCore::PushStateInternal(paraview_protobuf::Message*) () from 
/usr/lib/paraview/libvtkPVServerImplementationCore.so.1
#6  0x729fcd3f in 
vtkPVSessionCore::PushState(paraview_protobuf::Message*) () from 
/usr/lib/paraview/libvtkPVServerImplementationCore.so.1
#7  0x729fb655 in 
vtkPVSessionBase::PushState(paraview_protobuf::Message*) () from 
/usr/lib/paraview/libvtkPVServerImplementationCore.so.1
#8  0x766a0b96 in vtkSMProxy::CreateVTKObjects() () from 
/usr/lib/paraview/libvtkPVServerManagerCore.so.1
#9  0x766f3739 in vtkSMSourceProxy::CreateVTKObjects() () from 
/usr/lib/paraview/libvtkPVServerManagerCore.so.1
#10 0x766a0aef in vtkSMProxy::CreateVTKObjects() () from 
/usr/lib/paraview/libvtkPVServerManagerCore.so.1
#11 0x766f3739 in vtkSMSourceProxy::CreateVTKObjects() () from 
/usr/lib/paraview/libvtkPVServerManagerCore.so.1
#12 0x766a0460 in vtkSMProxy::UpdateVTKObjects() () from 
/usr/lib/paraview/libvtkPVServerManagerCore.so.1
#13 0x766be015 in vtkSMReaderFactory::CanReadFile(char const*, 
vtkSMProxy*) () from /usr/lib/paraview/libvtkPVServerManagerCore.so.1
#14 0x766bec91 in 
vtkSMReaderFactory::vtkInternals::vtkValue::CanReadFile(char const*, 
std::vector, std::allocator > > const&, vtkSMSession*, bool) 
() from /usr/lib/paraview/libvtkPVServerManagerCore.so.1
#15 0x766bf0fc in vtkSMReaderFactory::GetPossibleReaders(char const*, 
vtkSMSession*) () from /usr/lib/paraview/libvtkPVServerManagerCore.so.1
#16 0x773e067f in pqSelectReaderDialog::pqSelectReaderDialog(QString 
const&, pqServer*, vtkSMReaderFactory*, QWidget*) () from 
/usr/lib/paraview/libvtkpqComponents.so.1
#17 0x77ab2d5d in pqLoadDataReaction::DetermineFileReader(QString 
const&, pqServer*, vtkSMReaderFactory*, QPair&) () from 
/usr/lib/paraview/libvtkpqApplicationComponents.so.1
#18 0x77ab3bd5 in pqLoadDataReaction::loadData(QList 
const&) () from /usr/lib/paraview/libvtkpqApplicationComponents.so.1
#19 0x77ab48bf in pqLoadDataReaction::loadData(QStringList const&) () 
from /usr/lib/paraview/libvtkpqApplicationComponents.so.1
#20 0x77a82c3d in 
pqCommandLineOptionsBehavior::processCommandLineOptions() () from 
/usr/lib/paraview/libvtkpqApplicationComponents.so.1
#21 0x752246a0 in QMetaObject::activate(QObject*, QMetaObject const*, 
int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x7522eefa in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x7522a293 in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x7573c54c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x7574352c in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#26 0x7520ff5d in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x75242d20 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x7523ff21 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#29 0x7fffe9bd37d7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7fffe9bd3a40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7fffe9bd3aec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x75240894 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x757e65d6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#34 0x7520e82f in 

Bug#842404: tomcat7-user fails to install on stretch

[Brent S. Elmer]

Package: tomcat7-user
Version: 7.0.72-1
Severity: normal

 systemctl status tomcat7.service
● tomcat7.service - LSB: Start Tomcat.
   Loaded: loaded (/etc/init.d/tomcat7; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2016-10-28 14:52:15 CDT; 11s
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 6964 ExecStart=/etc/init.d/tomcat7 start (code=exited,
status=1/FAILURE)

Oct 28 14:52:15 brente systemd[1]: Starting LSB: Start Tomcat
Oct 28 14:52:15 brente tomcat7[6964]: invalid CATALINA_BASE: /var/lib/tomcat7
... failed!
Oct 28 14:52:15 brente systemd[1]: tomcat7.service: Control process exited,
code=exited status=1
Oct 28 14:52:15 brente systemd[1]: Failed to start LSB: Start Tomcat..
Oct 28 14:52:15 brente systemd[1]: tomcat7.service: Unit entered failed state.
Oct 28 14:52:15 brente systemd[1]: tomcat7.service: Failed with result 'exit-
code'.



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

Kernel: Linux 4.7.5.161003 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages tomcat7-user depends on:
ii  netcat-openbsd [netcat]  1.105-7
ii  netcat-traditional [netcat]  1.10-41
ii  tomcat7-common   7.0.72-1

tomcat7-user recommends no packages.

Versions of packages tomcat7-user suggests:
ic  tomcat7   7.0.72-1
pn  tomcat7-admin 
pn  tomcat7-docs  
pn  tomcat7-examples  

-- no debconf information

Bug#842013: jessie-pu: package potrace/1.12-1+deb8u1

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2016-10-25 at 18:49 +0200, Andrew Shadura wrote:
> On 25/10/16 18:26, Adam D. Barratt wrote:
> > On 2016-10-25 14:32, Andrew Shadura wrote:
> >> On 25/10/16 15:31, Adam D. Barratt wrote:
> >>> Control: tags -1 + confirmed
> >>>
> >>> On 2016-10-25 10:10, Andrew Shadura wrote:
>  I have prepared an upload fixing CVE-2016-8694, CVE-2016-8695,
>  CVE-2016-8696, CVE-2016-8697, CVE-2016-8698, CVE-2016-8699,
>  CVE-2016-8700,
>  CVE-2016-8701, CVE-2016-8702, CVE-2016-8703.
[...]
> Indeed, I uploaded a wrong .changes. Sorry for the noise, will re-upload
> shortly.

I've flagged that re-upload for acceptance; thanks.

Regards,

Adam

Bug#842280: kdevelop: memory leak when open js-file

[Sergey Stremidlo]

Sorry, problem still here.









 On Fri, 28 Oct 2016 21:52:28 +0300Sergey Stremidlo 
ser...@stremidlo.name wrote 






After upgrade problem disappeared.



Start-Date: 2016-10-28  20:08:30 
Commandline: apt upgrade 
Requested-By: sergey (1000) 
Upgrade: libmpx2:amd64 (6.2.0-6, 6.2.0-9), libgcj17:amd64 (6.2.0-6, 6.2.0-9), 
libobjc-6-dev:amd64 (6.2.0-6, 6.2.0-9), 
lib32stdc++6:amd64 (6.2.0-6, 6.2.0-9), libobjc4:amd64 (6.2.0-6, 6.2.0-9), 
cpp-6:amd64 (6.2.0-6, 6.2.0-9), lp-solve:amd
64 (5.5.0.15-4, 5.5.0.15-4+b1), libitm1:amd64 (6.2.0-6, 6.2.0-9), 
libcilkrts5:amd64 (6.2.0-6, 6.2.0-9), libasan3:amd64
 (6.2.0-6, 6.2.0-9), libquadmath0:amd64 (6.2.0-6, 6.2.0-9), gcc-6-base:amd64 
(6.2.0-6, 6.2.0-9), gcc-6-base:i386 (6.2.
0-6, 6.2.0-9), libgcc1:amd64 (1:6.2.0-6, 1:6.2.0-9), libgcc1:i386 (1:6.2.0-6, 
1:6.2.0-9), lib32gcc1:amd64 (1:6.2.0-6, 
1:6.2.0-9), libtsan0:amd64 (6.2.0-6, 6.2.0-9), libgcc-6-dev:amd64 (6.2.0-6, 
6.2.0-9), libubsan0:amd64 (6.2.0-6, 6.2.0-
9), g++-6:amd64 (6.2.0-6, 6.2.0-9), libgfortran3:amd64 (6.2.0-6, 6.2.0-9), 
gcc-6:amd64 (6.2.0-6, 6.2.0-9), gcj-6-jre-l
ib:amd64 (6.2.0-6, 6.2.0-9), liblsan0:amd64 (6.2.0-6, 6.2.0-9), libgomp1:amd64 
(6.2.0-6, 6.2.0-9), libgomp1:i386 (6.2.
0-6, 6.2.0-9), libatomic1:amd64 (6.2.0-6, 6.2.0-9), libcc1-0:amd64 (6.2.0-6, 
6.2.0-9), libstdc++6:amd64 (6.2.0-6, 6.2.
0-9), libstdc++6:i386 (6.2.0-6, 6.2.0-9), libstdc++-6-dev:amd64 (6.2.0-6, 
6.2.0-9) 
End-Date: 2016-10-28  20:09:16
 

Bug#842403: jetty8 install fails on stretch

[Brent S. Elmer]

Package: jetty8
Version: 8.2.0-2
Severity: normal

Preparing to unpack .../jetty8_8.2.0-2_all.deb ...
Unpacking jetty8 (8.2.0-2) ...
Processing triggers for systemd (231-9) ...
Setting up jetty8 (8.2.0-2) ...
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides
insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides
Job for jetty8.service failed because the control process exited with error
code.
See "systemctl status jetty8.service" and "journalctl -xe" for details.
invoke-rc.d: initscript jetty8, action "start" failed.
● jetty8.service - LSB: Start Jetty
   Loaded: loaded (/etc/init.d/jetty8; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2016-10-28 14:37:22 CDT; 6ms
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 23368 ExecStart=/etc/init.d/jetty8 start (code=exited,
status=1/FAILURE)

Oct 28 14:37:17 brente systemd[1]: Starting LSB: Start Jetty...
Oct 28 14:37:17 brente jetty8[23368]: Starting Jetty 8 Servlet Engine:
jett...).
Oct 28 14:37:22 brente jetty8[23368]:  failed!
Oct 28 14:37:22 brente systemd[1]: jetty8.service: Control process exited,
...=1
Oct 28 14:37:22 brente systemd[1]: Failed to start LSB: Start Jetty.
Oct 28 14:37:22 brente systemd[1]: jetty8.service: Unit entered failed state.
Oct 28 14:37:22 brente systemd[1]: jetty8.service: Failed with result
'exit...'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package jetty8 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 jetty8
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

Kernel: Linux 4.7.5.161003 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages jetty8 depends on:
ii  adduser  3.115
ii  apache2-utils2.4.23-5
ii  default-jre-headless [java7-runtime-headless]2:1.8-57
ii  ibm-j2re1.6 [default-jre-headless]   1.6.0.16.26-0
ii  libjetty8-extra-java 8.2.0-2
ii  libjetty8-java   8.2.0-2
ii  openjdk-8-jre-headless [java7-runtime-headless]  8u111-b14-2

Versions of packages jetty8 recommends:
ii  authbind  2.1.1+nmu1

Versions of packages jetty8 suggests:
pn  libjetty8-java-doc  

-- no debconf information

Bug#840169: Seems to be upstream issue

[shanavas]

The package has an invalid npm config file `package.json`.
The repository declaration in pacakge.json is not in format specified by 
https://docs.npmjs.com/files/package.json#repository 
(https://docs.npmjs.com/files/package.json#repository)

Bug#842288: transition: gdal

[Sebastiaan Couwenberg]

On 10/28/2016 01:39 AM, Sebastiaan Couwenberg wrote:
> On 10/27/2016 11:58 PM, Emilio Pozuelo Monfort wrote:
>> On 27/10/16 20:10, Bas Couwenberg wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian@packages.debian.org
>>> Usertags: transition
>>>
>>> Dear Release Team,
>>>
>>> For the Debian GIS team I'd like to transition to GDAL 2.1.2.
>>>
>>> Like the previous transition to GDAL 2.1.1 (#830966), there is no SONAME
>>> bump, only the virtual ABI package changed to account for the C++ symbol
>>> changes.
>>>
>>> All reverse dependencies rebuilt successfully with GDAL 2.1.2 from
>>> experimental as summarized below, except mysql-workbench whose build
>>> dependencies are not installable (#840786), but it's not in testing due
>>> to (#839356).
>>>
>>> libgdal-grass doesn't need a binNMU as the 2.1.2 version will be
>>> uploaded to unstable instead. liblas likewise doesn't need a binNMU,
>>> the version is experimental will be moved to unstable instead.
>>>
>>> Please also binNMU osgearth in experimental as part of the transition.
>>
>> Sounds good. Go ahead.
> 
> Thanks for the super quick feedback again!
> 
> gdal (2.1.2+dfsg-1), liblas (1.8.1-3) & libgdal-grass (2.1.2-1) have
> been uploaded to unstable, and gdal was just accepted. Sometime tomorrow
> the buildds should have installed the packages.

The mips64el buildd just installed gdal (2.1.2+dfsg-1), it's now
available on all release architectures and all ports where the build
dependencies are installable.

Looks like we're ready for the binNMUs.

Kind Regards,

Bas

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

Bug#842389: systemd-coredump: useful stacktraces in systemd-coredump

[Felipe Sateler]

Control: tags -1 moreinfo

On 28 October 2016 at 14:49, Ritesh Raj Sarraf  wrote:
> Package: systemd-coredump
> Version: 231-10
> Severity: wishlist
>
> I just started using systemd-coredump and was wondering if it has
> capability to generate a full stack trace ?
>
> A standard installation wouldn't really have all the debug symbol
> packages installed. On Ubuntu (and also an outdated version in Debian
> Experimental), with apport, the user has the capability to (re)generate
> useful and complete stacktraces, by installing the debug packages on the fly.
>
> I am wondering if the same is doable with systemd-coredump ?

I'm not sure what your precise question is, but if you install the
debug packages, then you can generate a full backtrace.

If you mean that systemd-coredump should automatically install the
packages, then it can't do that.


-- 

Saludos,
Felipe Sateler

Bug#840754: Memory leak in libmagic and failure in magic_load

[Christoph Biedl]

Arnaud Quette wrote...

> looking closer at the patch I pointed, it's very probably not suitable.

Now I see a patch. I'll take a close look tomorrow

> IMHO, it's Debian related, though I've not tested on Redhat nor others.

As far as I understand it the leak is caused by the fact Debian uses
a different compile-time option for MAGIC: Two items, separated by ':';
and the code that splits this has the leak.

If this is true, it's technically upstream although it does not
manifest there. But is should happen in Redhat, too.

> again, the simple solution, while waiting for fixing the code, may be
> to export MAGIC=/usr/share/misc/magic

Yes, but that's just a workaround. I want to identify the underlying
issue, and fix it.

Christoph


signature.asc
Description: Digital signature

Bug#842402: error installing

[Brent S. Elmer]

Package: solr-tomcat
Version: 3.6.2+dfsg-8
Severity: normal

When I try to install solr-tomcat on stretch.  I get the following error:

Setting up solr-tomcat (3.6.2+dfsg-8) ...
chown: invalid user: ‘tomcat7:tomcat7’
dpkg: error processing package solr-tomcat (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up libcommons-digester-java (1.8.1-4) ...
Errors were encountered while processing:
 solr-tomcat



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

Kernel: Linux 4.7.5.161003 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages solr-tomcat depends on:
ii  solr-common   3.6.2+dfsg-8
ii  tomcat7-user  7.0.72-1

solr-tomcat recommends no packages.

solr-tomcat suggests no packages.

-- no debconf information

Bug#842401: ITP: pd-upp -- Universal Polyphonic Player for Pure Data

[IOhannes m zmoelnig]

Package: wnpp
Severity: wishlist
Owner: IOhannes m zmoelnig 

* Package name: pd-upp
  Version : 0.1
  Upstream Author : Thomas Grill 
* URL : http://g.org/research/software/upp/
* License : CC-BY-SA
  Programming Lang: Pd
  Description : Universal Polyphonic Player for Pure Data

 The Universal Polyphonic Player (short UPP) is an infrastructure for all kinds
 of polyphonic events – be it note-like events, other generated sounds or short
 grains in granular synthesis. The strengths of the system are a modular, easily
 extendible design, almost unlimited polyphony, ease of control, DSP load
 scaling and sample-accurate timing.

I intend to maintain this package under the pkg-multimedia-maintainers umbrella
as part of the pd-externals packaging effort.

Bug#842334: [pkg-gnupg-maint] Bug#842334: Needs an X display to run?

[Daniel Kahn Gillmor]

Control: tags 842334 - moreinfo unreproducible
Control: clone 842334 -1
Control: reassign -1 lxdm 0.5.3-1
Control: retitle -1 lxdm allows user to retain control over X11 session after 
logout
Control: tags -1 + security
Control: forcemerge 841909 842334

Thanks for your quick response, Julien.

On Fri 2016-10-28 13:39:26 -0400, Julien Puydt wrote:
> On 28/10/2016 18:55, Daniel Kahn Gillmor wrote:
> I'm using mosh to connect to a tmux session. In that tmux session, there 
> is a window with a "TMUX= ssh-agent tmux", where my ~/.ssh/debian key is 
> ssh-add-ed.

I don't see how the ssh-agent stuff is relevant to this discussion, so
i'm going to ignore it for now.

> This is the terminal I use to work on Debian packaging, and in
> particular, to run "gbp buildpackage -S -kdebian", which until
> recently showed me a curses window.

ok, makes sense.

>> In particular answers to any or all of the questions below would help me
>> understand your use case:
>>
>>  * what versions of pinentry do you have installed?
>
> pinentry-gnome3, 0.9.7-6
>
>>  * do you have dbus-user-session installed?
>
> Yes, version 1.10.12-1.
>
>>  * which version of pinentry is the default pinentry?
>
> It's pinentry-gnome3, from src:pinentry version 0.9.7-6, as above : I 
> don't think I have another one.

Thanks, this is useful details.

>>  * is there a concurrent graphical (X11) session running for the user
>>account that you're using?
>
> When there is or has been such a session, then I get an X window (even
> in lxdm's login screen after logout : that point is a security
> issue!).

This is definitely a bug, and a security one at that.  I'm assuming
you're running lxdm 0.5.3-1, and i've cloned and assigned this bug to
that package.  Please adjust the cloned bug in case any of those details
are wrong.  I don't have anything running lxdm at the moment to test
with.

> If not I get an error trying to sign, but no curses window.
 [...]
> If I kill dbus instances running as my user, then I get an error, so 
> indeed it's the fact that there's a still-running dbus that makes it 
> possible to display an X window . And that is already wrong, because I'm 
> not supposed to access the lxdm session screen as a user.
>
> I took your 0011 patch and added it to the package, then installed it : 
> I now get the curses window...

ok, that's a win, thanks!

> even when I run a gpg command inside an xterm within a lxsession, in
> which case I would have expected an X11 window.

hm, this doesn't make sense to me.  Was this after you killed your dbus
session?  If so, that would certainly explain the fallback.  But if your
dbus session was live and your lxsession was running and you have gcr
installed, i would have expected any gpg command inside an xterm within
an lxsession to trigger the gcr graphical prompt instead of a curses
prompt.

Can you confirm the situation here?

--dkg


signature.asc
Description: PGP signature

Bug#842399: ITP: pd-autopreset -- simple state saving for Pure Data

[IOhannes m zmoelnig]

Package: wnpp
Severity: wishlist
Owner: IOhannes m zmoelnig 

* Package name: pd-autopreset
  Version : 0.9
  Upstream Author : Antoine Rousseau
* URL : https://github.com/MetaluNet/AutoPreset
* License : GPL
  Programming Lang: Pd
  Description : simple state saving for Pure Data

 AutoPreset is a simple state saving system (like rradical/ssad, among other
 ones). It aims to be simple and yet powerful.
 .
 One particularity of this system is to be able to interpolate float parameters
 between different settings (parameter morphing).


I intend to maintain this package under the pkg-multimedia-maintainers umbrella
as part of the pd-externals packaging effort.

Bug#842117: file: detect MacWrite II documents

[Christoph Biedl]

tags 842117 confirmed upstream moreinfo
thanks

Paul Wise wrote...

> Please detect MacWrite II documents:
> 
> Name: MacWrite II document
> Sample: https://www.w3.org/History/1989/proposal
> Info: http://fileformats.archiveteam.org/wiki/MacWrite

Um, I can certainly prepare something for upstream to include, however
the sample you provided does not match the description:

  fe 37 00 1c 00 00 00 00  00 00 28 00 00 19 00 00  |.7(.|
0010  00 00 00 00 00 00 01 00  00 00 75 35 00 01 0b 3f  |..u5...?|
(...)

does not match the documents that state the first two octets should be
00 03. Can you shed some light on this?

Christoph


signature.asc
Description: Digital signature

Bug#842398: ITP: pd-bandlimited -- bandlimited (non-aliasing) waveform generators for Pure Data

[IOhannes m zmoelnig]

Package: wnpp
Severity: wishlist
Owner: IOhannes m zmoelnig 

* Package name: pd-bandlimited
  Version : 1.0.0
  Upstream Author : Paulo Casaes
* URL : https://github.com/pcasaes/bandlimited
* License : Apache
  Programming Lang: C, Pd
  Description : bandlimited (non-aliasing) waveform generators for Pure Data

 A computational expensive Pure Data (Pd) external that generates signal (saw,
 triangle, square, and variable duty cycle pulse wave) band limited to the
 sampling rate.


I intend to maintain this package under the pkg-multimedia-maintainers umbrella
as part of the pd-externals packaging effort.

Bug#842397: ITP: pd-ableton-link -- integration of Ableton Link into Pure Data

[IOhannes m zmoelnig]

Package: wnpp
Severity: wishlist
Owner: IOhannes m zmoelnig 

* Package name: pd-ableton-link
  Version : 0.2
  Upstream Author : Google Inc.
* URL : 
https://github.com/libpd/pd-for-ios/tree/master/abl_link/external
* License : GPL-2+
  Programming Lang: C++, Pd
  Description : integration of Ableton Link into Pure Data

 [abl_link~] is a Pd object that integrates Ableton Link into Pd. It has four
 outlets, which emit the index of the current step (at the beginning of each
 step), the current phase and beat time on each DSP tick, as well as the tempo
 on tempo changes. Phase and beat time are Link concepts. The purpose of the
 step feature is to generate events in Pd at a given rate (measured in steps per
 beat).

I intend to maintain this package under the pkg-multimedia-maintainers umbrella
as part of the pd-externals packaging effort.

Bug#842280: kdevelop: memory leak when open js-file

[Sergey Stremidlo]

After upgrade problem disappeared.


Start-Date: 2016-10-28  20:08:30 
Commandline: apt upgrade 
Requested-By: sergey (1000) 
Upgrade: libmpx2:amd64 (6.2.0-6, 6.2.0-9), libgcj17:amd64 (6.2.0-6, 6.2.0-9), 
libobjc-6-dev:amd64 (6.2.0-6, 6.2.0-9), 
lib32stdc++6:amd64 (6.2.0-6, 6.2.0-9), libobjc4:amd64 (6.2.0-6, 6.2.0-9), 
cpp-6:amd64 (6.2.0-6, 6.2.0-9), lp-solve:amd
64 (5.5.0.15-4, 5.5.0.15-4+b1), libitm1:amd64 (6.2.0-6, 6.2.0-9), 
libcilkrts5:amd64 (6.2.0-6, 6.2.0-9), libasan3:amd64
 (6.2.0-6, 6.2.0-9), libquadmath0:amd64 (6.2.0-6, 6.2.0-9), gcc-6-base:amd64 
(6.2.0-6, 6.2.0-9), gcc-6-base:i386 (6.2.
0-6, 6.2.0-9), libgcc1:amd64 (1:6.2.0-6, 1:6.2.0-9), libgcc1:i386 (1:6.2.0-6, 
1:6.2.0-9), lib32gcc1:amd64 (1:6.2.0-6, 
1:6.2.0-9), libtsan0:amd64 (6.2.0-6, 6.2.0-9), libgcc-6-dev:amd64 (6.2.0-6, 
6.2.0-9), libubsan0:amd64 (6.2.0-6, 6.2.0-
9), g++-6:amd64 (6.2.0-6, 6.2.0-9), libgfortran3:amd64 (6.2.0-6, 6.2.0-9), 
gcc-6:amd64 (6.2.0-6, 6.2.0-9), gcj-6-jre-l
ib:amd64 (6.2.0-6, 6.2.0-9), liblsan0:amd64 (6.2.0-6, 6.2.0-9), libgomp1:amd64 
(6.2.0-6, 6.2.0-9), libgomp1:i386 (6.2.
0-6, 6.2.0-9), libatomic1:amd64 (6.2.0-6, 6.2.0-9), libcc1-0:amd64 (6.2.0-6, 
6.2.0-9), libstdc++6:amd64 (6.2.0-6, 6.2.
0-9), libstdc++6:i386 (6.2.0-6, 6.2.0-9), libstdc++-6-dev:amd64 (6.2.0-6, 
6.2.0-9) 
End-Date: 2016-10-28  20:09:16
 

Bug#842396: Lynx browser: Can't set margins

[David Lawyer]

Package:lynx-cur
Version: 2.8.9dev6-4

I have a wide monitor and need wide margins in order to easily move my
eyes down to the next line when reading.  I've noticed that most websites use 
wide
margins (and sometimes put ads in them) to make it easier to read an
article.  But I can't find any way to set margins in the Lynx
documentation.  I did set NO_MARGINS: FALSE and that creates a narrow
margin but I want margins (left and right) of about 30 characters each.  I
tried setting SCREEN_SIZE but it doesn't work and I want the full screen
size for tables and data in multiple columns.

The documentation implies that margins are set the the style-sheet but I
can't find any such sheet (although there is one restricted only to
setting colors).  If lynx doesn't suppor margins, it is a very serious
defficiency and should be noted in the documentation.

David Lawyer

Bug#842395: libghc-fail-dev: this version should not be released with stretch

[Clint Adams]

Package: libghc-fail-dev
Version: 4.9.0.0-1
Severity: serious

fail 4.9.0.0 should not be released with ghc 8.0 in stretch

Bug#842394: haskell-cabal: this version should not be released with stretch

[Clint Adams]

Source: haskell-cabal
Version: 1.22.8.0-1
Severity: serious

stretch should be released either without the haskell-cabal package
or with a newer version than is shipped with ghc

Bug#841427: unifdef: FTBFS under some locales (eg. fr_CH.UTF-8)

[Bob Proulx]

severity 841427 important
tags 841427 + pending
thanks

Changing severity level to prevent removal from Testing.  This is a
build time issue not a run time issue.  I don't think this is a severe
enough problem to warrant removing the working package from Testing.

Bob

Bug#842393: thefuck: Missing dependency on python-pkg-resources

[Robbie Harwood]

Package: thefuck
Version: 3.11-2
Severity: important

Dear Maintainer,

When run on a system without python-pkg-resources, running
`eval "$(thefuck --alias)` produces the following traceback:

> Traceback (most recent call last):
>   File "/usr/bin/thefuck", line 6, in 
> from pkg_resources import load_entry_point
> ImportError: No module named pkg_resources

which goes away (and the package works as expected) once python-pkg-resources
is installed.

Thanks!


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

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

Versions of packages thefuck depends on:
ii  python-colorama   0.3.7-1
ii  python-decorator  4.0.6-1
ii  python-pathlib2   2.1.0-1
ii  python-psutil 4.3.1-1
ii  python-six1.10.0-3
ii  python2.7 2.7.12-3+b1
pn  python:any

thefuck recommends no packages.

thefuck suggests no packages.

-- no debconf information

Bug#842392: libmailtools-perl: Please package new upstream version (2.18)

[Salvatore Bonaccorso]

Package: libmailtools-perl
Version: 2.13-1
Severity: wishlist

Hi Anibal,

There is a new upstream version for libmailtools-perl, 2.18. Could you
please package it? I need it at least 2.17 to be able to update a
package maintained in the pkg-perl group.

Btw, I would like to take to opportunity: Have you considered to move
the package unter the pkg-perl umbrella and maintain it within the
Debian Perl Group maintenance team? If you are interested here is an
introductory page:

https://wiki.debian.org/Teams/DebianPerlGroup/Welcome

Regards,
Salvatore

Bug#842356: bio-eagle: please make the build reproducible

[Chris Lamb]

Hi,

> Patch attached

Do note that his slightly changes the directory structure of the
.tar.xz. If you care (enough!), you can probably use tar -C instead;
what I was trying to avoid was an ugly:

  cd examples && find -type f | LC_ALL=C sort | tar … -T -

.. call :) Will leave it up to your judgement as maintaner.


Regards,

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

Bug#842391: libconfig-model-dpkg-perl: cme edit dpkg-patches should handle patch written like git commits

[Dominique Dumont]

Package: libconfig-model-dpkg-perl
Version: 2.085
Severity: normal

Dear Maintainer,

cme chokes on patches created with git show:

$ cme dump dpkg-patch use-ffi_arg-type 
cme: using Dpkg::Patch model  
File debian/patches/use-ffi_arg-type line 5 has a syntax error:
Did not find a keyword before: '   use ffi_arg type for libffi 
nativecall return types''

The patch is:
$ quilt header use-ffi_arg-type
commit 45d5c13ecbeeb085ddaaabec8150b6051b90f023
Author: Tobias Leich 
Date:   Thu Oct 27 17:55:36 2016 +0200

use ffi_arg type for libffi nativecall return types

This fixes issues on big endian machines, and is according to
https://github.com/libffi/libffi/issues/286 the right way to handle
it anyway.


using -force option is useless as the patch is dropped.

With (or without?) -force, cme should store information lines in
the dep-3 Description field. (with the commit line ?)



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

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

Versions of packages libconfig-model-dpkg-perl depends on:
ii  libapt-pkg-perl  0.1.30
ii  libarray-intspan-perl2.003-1
ii  libconfig-model-perl 2.092-1
ii  libexporter-lite-perl0.08-1
ii  liblog-log4perl-perl 1.47-2
ii  libmodule-corelist-perl  5.20161020-1
ii  libmouse-perl2.4.5-2+b1
ii  libparse-recdescent-perl 1.967013+dfsg-1
ii  libsoftware-license-perl 0.103012-1
ii  libtext-autoformat-perl  1.74-2
ii  libtext-levenshtein-damerau-perl 0.41-1
ii  liburi-perl  1.71-1
ii  libwww-perl  6.15-1
ii  libyaml-perl 1.18-1
ii  licensecheck 3.0.24-1
ii  lintian  2.5.49
ii  perl 5.24.1~rc3-3
ii  perl-modules-5.24 [libmodule-corelist-perl]  5.24.1~rc3-3

Versions of packages libconfig-model-dpkg-perl recommends:
ii  libconfig-model-tkui-perl  1.357-1

libconfig-model-dpkg-perl suggests no packages.

-- no debconf information

Bug#842390: jmeter: BeanShell PreProcessor fails: Cannot find BeanShell

[Dominique Dumont]

Package: jmeter
Version: 2.13-1
Severity: normal

Dear Maintainer,

jmeter fails all tests that use BeanShell PreProcessor:

2016/10/28 16:47:07 INFO  - jmeter.threads.ThreadGroup: Starting thread group 
number 1 threads 10 ramp-up 0 perThread 0.0 delayedStart=false 
2016/10/28 16:47:07 ERROR - jmeter.util.BeanShellTestElement: Cannot find 
BeanShell: java.lang.ClassNotFoundException: bsh.Interpreter 
2016/10/28 16:47:07 ERROR - jmeter.util.BeanShellTestElement: Cannot find 
BeanShell: java.lang.ClassNotFoundException: bsh.Interpreter 
2016/10/28 16:47:07 INFO  - jmeter.threads.JMeterThread: Thread started: User 
Group 1-1 
2016/10/28 16:47:07 ERROR - jmeter.util.BeanShellTestElement: Cannot find 
BeanShell: java.lang.ClassNotFoundException: bsh.Interpreter 
2016/10/28 16:47:07 ERROR - jmeter.util.BeanShellTestElement: Cannot find 
BeanShell: java.lang.ClassNotFoundException: bsh.Interpreter 
2016/10/28 16:47:07 ERROR - jmeter.threads.JMeterThread: Error while processing 
sampler 'Post - Create tenant' : java.lang.NullPointerException
at 
org.apache.jmeter.util.BeanShellTestElement.getBeanShellInterpreter(BeanShellTestElement.java:89)
at 
org.apache.jmeter.modifiers.BeanShellPreProcessor.process(BeanShellPreProcessor.java:49)
at 
org.apache.jmeter.threads.JMeterThread.runPreProcessors(JMeterThread.java:762)
at 
org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:419)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:261)
at java.lang.Thread.run(Thread.java:745)

Is a dependency missing ?

All the best

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

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

Versions of packages jmeter depends on:
ii  default-jre [java2-runtime]   2:1.8-57
ii  java-wrappers 0.1.28
ii  libavalon-framework-java  4.2.0-9
ii  libbcmail-java1.55-1
ii  libbcprov-java1.55-1
ii  libbsf-java   1:2.4.0-5
ii  libcommons-collections3-java  3.2.2-1
ii  libcommons-httpclient-java3.1-12
ii  libcommons-io-java2.5-1
ii  libcommons-jexl-java  1.1-3
ii  libcommons-jexl2-java 2.1.1-3
ii  libcommons-lang3-java 3.5-1
ii  libcommons-math3-java 3.6.1-1
ii  libcommons-pool2-java 2.4.2-2
ii  libexcalibur-logger-java  2.1-6
ii  libexcalibur-logkit-java  2.0-11
ii  libjcharts-java   0.7.5-4
ii  libjdom1-java 1.1.3-1
ii  libjtidy-java 7+svn20110807-4
ii  libmail-java  1.5.6-1
ii  liboro-java   2.0.8a-12
ii  librhino-java 1.7R4-3
ii  librsyntaxtextarea-java   2.5.0-1
ii  libxalan2-java2.7.1-9
ii  libxmlgraphics-commons-java   2.1-2
ii  libxstream-java   1.4.9-1
ii  openjdk-8-jre [java2-runtime] 8u111-b14-2
ii  oracle-java8-jdk [java2-runtime]  8u66

Versions of packages jmeter recommends:
ii  jmeter-help  2.13-1
ii  jmeter-http  2.13-1

jmeter suggests no packages.

-- no debconf information

Bug#842389: systemd-coredump: useful stacktraces in systemd-coredump

[Ritesh Raj Sarraf]

Package: systemd-coredump
Version: 231-10
Severity: wishlist

I just started using systemd-coredump and was wondering if it has
capability to generate a full stack trace ?

A standard installation wouldn't really have all the debug symbol
packages installed. On Ubuntu (and also an outdated version in Debian
Experimental), with apport, the user has the capability to (re)generate
useful and complete stacktraces, by installing the debug packages on the fly.

I am wondering if the same is doable with systemd-coredump ?

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

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

Versions of packages systemd-coredump depends on:
ii  adduser  3.115
ii  libacl1  2.2.52-3
ii  libc62.24-5
ii  libdw1   0.166-2.2
ii  libelf1  0.166-2.2
ii  systemd  231-10

systemd-coredump recommends no packages.

systemd-coredump suggests no packages.

-- no debconf information

Bug#838640: [/master] New upstream release (Closes: #838640).

[Andrew Starr-Bochicchio]

tag 838640 pending
thanks

Date: Thu Oct 27 18:53:09 2016 -0400
Author: Andrew Starr-Bochicchio 
Commit ID: 5014455d5cd5385efff3fc05bbedb7ca8a9b55e4
Commit URL: 
https://anonscm.debian.org/cgit/collab-maint/deluge.git;a=commitdiff;h=5014455d5cd5385efff3fc05bbedb7ca8a9b55e4
Patch URL: 
https://anonscm.debian.org/cgit/collab-maint/deluge.git;a=commitdiff_plain;h=5014455d5cd5385efff3fc05bbedb7ca8a9b55e4

New upstream release (Closes: #838640).

  

Bug#842334: [pkg-gnupg-maint] Bug#842334: Needs an X display to run?

[Julien Puydt]

Hi,

On 28/10/2016 18:55, Daniel Kahn Gillmor wrote:

Control: tags 842334 + moreinfo unreproducible

Hi Julien--

On Fri 2016-10-28 03:47:24 -0400, Julien Puydt wrote:

I hadn't signed a Debian package since a few days, and it's now failing
because I do remote work on a host without X access. The last time I
worked on Debian packaging there was a curses window showing up asking
for the password to the key.


That should still be the case.  Can you describe the situation you're in
in more detail?  I can make a signature using a curses window for
passphrase prompting.


I'm using mosh to connect to a tmux session. In that tmux session, there 
is a window with a "TMUX= ssh-agent tmux", where my ~/.ssh/debian key is 
ssh-add-ed. This is the terminal I use to work on Debian packaging, and 
in particular, to run "gbp buildpackage -S -kdebian", which until 
recently showed me a curses window.



In particular answers to any or all of the questions below would help me
understand your use case:

 * what versions of pinentry do you have installed?


pinentry-gnome3, 0.9.7-6


 * do you have dbus-user-session installed?


Yes, version 1.10.12-1.


 * which version of pinentry is the default pinentry?


It's pinentry-gnome3, from src:pinentry version 0.9.7-6, as above : I 
don't think I have another one.



 * is there a concurrent graphical (X11) session running for the user
   account that you're using?


When there is or has been such a session, then I get an X window (even 
in lxdm's login screen after logout : that point is a security issue!). 
If not I get an error trying to sign, but no curses window.



 * how are you connecting to the remote host?


See above : mosh. But I tried with slogin and obtained the same results.


 * what session management governs your non-X session on the remote host?


See above : tmux or direct slogin give me the same behaviour.


If you've got a running dbus session (whether you have dbus-user-session
or not), and you're using pinentry-gnome3, can you try rebuilding it
with the patch i mentioned in  https://bugs.debian.org/841909  and let
me know how that works?


If I kill dbus instances running as my user, then I get an error, so 
indeed it's the fact that there's a still-running dbus that makes it 
possible to display an X window . And that is already wrong, because I'm 
not supposed to access the lxdm session screen as a user.


I took your 0011 patch and added it to the package, then installed it : 
I now get the curses window... even when I run a gpg command inside an 
xterm within a lxsession, in which case I would have expected an X11 window.


I hope that helps,

Snark on #debian-science

Bug#841910: uscan behaviour on multiple signatures

[Bernhard Schmidt]

On Wed, Oct 26, 2016 at 06:08:28PM -0400, James McCoy wrote:

Hi,

> > IMHO this behaviour does not make any sense. You need to check the
> > authenticity of any additional key upstream might use before adding it
> > to the repo,
> 
> Of course you do.  Why wouldn't you verify the authenticity of a key
> before adding it to signing-key.asc?  Adding the key is indicating that
> you trust it's a valid key to be used to sign the archive you're going
> to use to create a new version of the Debian package.

Indeed. So I have to check every key very carefully, because
> 
> > you cannot just use one known-good key and ignore the rest.
> > This even makes an attack a bit more likely, since control over just one
> > key in the set is enough to build and sign an accepted tarball.
> How so?  Every signature on the archive needs to be verified for gpgv to
> return success.  gpgv is already return a failing exit code in your
> scenario because you have weren't able to verify one of the 4 signatures
> on the archive.  uscan just needs to propagate gpgv failure to its own
> exit code.

as soon as I add it to the keyring every single key in there is
sufficient to properly (in the eyes of uscan/gpgv) sign a new release
alone.

See my answer to Osamu as well.

Say a hypothetical upstream allows everyone to publish additional
signatures for a release (i.e. every developer in the project or even
everyone in the world, because additional signatures don't hurt). I'd
have to check everyone, add everyone to the keyring and every single key
in there would be sufficient to sign a new release.

But this part of the report is rather theoretical, my main issue was
that uscan stops processing the tarball (no repack etc) without a clear
error message.

uscan warn: OpenPGP signature did not verify.

as last message on the console does not really tell me that the
processing has bailed out at this point. I had not used the dfsg
repacking feature of uscan before and was scratching my head quite a bit
until I realized that the warning and the missing dfsg tarball were
related.

Bernhard


signature.asc
Description: Digital signature

Bug#842388: RFP: zcash -- an implementation of the "Zerocash" protocol

[Jeffrey Cliff]

Package: wnpp
Severity: wishlist

Zcash is an implementation of the "Zerocash" protocol. Based on Bitcoin's
code, it intends to offer a far higher standard of privacy and anonymity
through a sophisticated zero-knowledge proving scheme that preserves
confidentiality of transaction metadata.

This software is the Zcash client. It downloads and stores the entire
history of Zcash transactions; depending on the speed of your computer and
network connection, the synchronization process could take a day or more
once the block chain has reached a significant size.

License: permissive "MIT" :
https://github.com/zcash/zcash/blob/master/COPYING

Source Code: https://github.com/zcash/zcash/

Bug#842160: RFS: python-memory-profiler/0.40-1 [RC]

[Mattia Rizzolo]

Control: tag -1 moreinfo
Control: owner -1 !

On Wed, Oct 26, 2016 at 10:41:36PM +0900, Changwoo Ryu wrote:
> I am looking for a sponsor for my package "python-memory-profiler":

sure thing!

> Or you can use the alioth git:
> 
> https://anonscm.debian.org/git/users/cwryu/python-memory-profiler.git

let's use git indeed.

> 
>   * New upstream release
>   * debian/*: Clean up the pybuild build (Closes: #804442)
>   * debian/*: lintian fixes
> - Standard-Version: 3.9.8
> - Add missing source format
> - Use new https addresses for Vcs-* fields

This is broken:

mattia@chase /tmp % git clone 
https://anonscm.debian.org/users/cwryu/python-memory-profiler.git
Cloning into 'python-memory-profiler'...
fatal: repository 
'https://anonscm.debian.org/users/cwryu/python-memory-profiler.git/' not found
128 mattia@chase /tmp % 

 :(

Furthermore be aware that you can use
https://anonscm.debian.org/git/users/cwryu/python-memory-profiler.git/
for both of Vcs-Git and Vcs-Browser.

Also, upstream has released 0.41, why not packaging that?  (annoying the
fact that seems there are no recent tags in github).

> My new gpg key is not in the keyring yet since the weak key 
> removal so I can't upload this update myself. RFS.

No problem, we're here :)

-- 
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#818537: RC bug on maildrop [was Re: freeradius]

[Josip Rodin]

On Sat, Oct 22, 2016 at 03:41:46PM +0200, Tobias Frost wrote:
> However may I ask you to take a look at the RC bugs in your DDPO? [2]
> ;-)

Intriguing, I completely missed that maildrop bug, I think my spam filters
somehow ate it. I'll try to figure out both issues, thanks for the hint.

-- 
 2. That which causes joy or happiness.

Bug#841313: latex-cjk-japanese-wadalab: FTBFS: Create .afm and .pfa fonts from dg. \n Segmentation fault (core dumped)

[韓達耐]

Hi all

I'm back from holiday and have been able to compile wftodm
successfully under a two-weeks-old Debian/unstable amd64 system, and
been able to reproduce the bug in a Debian/unstable amd64 system from
yesterday.

Hi Adrian

Thanks a lot for finding the bug.  I will report it upstream.

Hi Norbert

Thanks a bunch for uploading a new package and including the pending changes.


Cheers


-- 
Danai

On 27 October 2016 at 09:17, Norbert Preining  wrote:
>> Thanks a lot, I will upload a fixed package soon. If Danai wants to
>
> Uploaded, svn updated.
>
> Danai, that also shipped out all the changes that were in the repo
> since long ...
>
> All the best
>
> Norbert
>
> --
> PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
> GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#842387: zeroc-icee: FTBFS in amd64 clean jail

[Joao Eriberto Mota Filho]

Source: zeroc-icee
Version: 1.2.0-6.2
Severity: grave
Justification: renders package unusable

The package FTBFS in a chroot jail and in cowbuilder. The error message is:

dh_install -plibicee-dev --sourcedir=debian/tmp
dh_install: Cannot find (any matches for) "usr/lib/*.a" (tried in "debian/tmp" 
and "debian/tmp")
dh_install: libicee-dev missing files: usr/lib/*.a
dh_install: missing files, aborting
/usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 
'binary-install/libicee-dev' failed
make: *** [binary-install/libicee-dev] Error 255

Regards,

Eriberto

Bug#829623: libcoap: FTBFS on non-Linux: unsupported operating system

[Carsten Schoenert]

Hello Aaron,

On Tue, Jul 05, 2016 at 08:14:11PM -0400, Aaron M. Ucko wrote:
> That's fair.  I tried your suggested patch on the porterbox
> falla.debian.org, but found that the build still failed because
> src/coap_io.c relies on IP_PKTINFO, which isn't available on kFreeBSD
> (or the Hurd, for that matter).  As such, it looks like specifying
> Architecture: linux-any is the way to go after all.

a small update on that issue.
Olaf and myself got the FreeBSD platform implemented into the supported
build environment. But the issue later while building is still alive.

Olaf is willing to take a look at this build issue later once we have
finished the FreeBSD platform support. I can't help much on that, my
experience with C on that low level stuff is rather small. But it should
be solvable as the problem isn't now and already fixed in other
packages. Unless this issue isn't really fixed I will left this report
open and tagged with help needed.

Regards
Carsten

Bug#801406: /usr/bin/uvcdynctrl-0.2.4: Re: uvcdynctrl: crash during system startup

[Ritesh Raj Sarraf]

Package: uvcdynctrl
Version: 0.2.4-1.1
Severity: important
Followup-For: Bug #801406

With systemd-coredump now available, here's what it reports.


rrs@learner:~$ coredumpctl info 
   PID: 594 (uvcdynctrl)
   UID: 0 (root)
   GID: 0 (root)
Signal: 11 (SEGV)
 Timestamp: Fri 2016-10-28 22:37:54 IST (3min 3s ago)
  Command Line: uvcdynctrl -d /dev/video0 --addctrl=04f2:b40f
Executable: /usr/bin/uvcdynctrl-0.2.4
 Control Group: /system.slice/systemd-udevd.service
  Unit: systemd-udevd.service
 Slice: system.slice
   Boot ID: 124bf2a00eb1476589a050f7b4bf54a0
Machine ID: e8814e2f596247dca3634da367a0ba04
  Hostname: learner
  Coredump: 
/var/lib/systemd/coredump/core.uvcdynctrl.0.124bf2a00eb1476589a050f7b4bf54a0.59
   Message: Process 594 (uvcdynctrl) of user 0 dumped core.

Stack trace of thread 594:
#0  0x7f1096e71892 readdir (libc.so.6)
#1  0x00402032 main (uvcdynctrl-0.2.4)
#2  0x7f1096dde2b1 __libc_start_main (libc.so.6)
#3  0x004033d1 _start (uvcdynctrl-0.2.4)

BTW, I never heard any feedback on this bug report. Should I raise the
severity? Because this bug, IMO, makes this package unusable.
-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (500, 
'unstable-debug'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages uvcdynctrl depends on:
ii  libc62.24-5
ii  libwebcam0   0.2.4-1.1
ii  libxml2  2.9.4+dfsg1-2
ii  uvcdynctrl-data  0.2.4-1.1

uvcdynctrl recommends no packages.

uvcdynctrl suggests no packages.

-- no debconf information

Bug#842386: dgit clone no longer seems to reuse existing origs

[Ian Jackson]

Package: dgit
Version: 2.8

$ ls -al libvirt_2.3.0.orig.tar.xz 
-rw-r--r-- 1 ian ian 13224384 Oct  8 08:38 libvirt_2.3.0.orig.tar.xz
$ sha256sum libvirt_2.3.0.orig.tar.xz 
e430e69b27d3f6c97255e638617b59b179618d531d81ac7dfe0783a1c1eeafd1  
libvirt_2.3.0.orig.tar.xz
$ dgit clone libvirt
canonical suite name for unstable is sid
starting new git history
downloading 
http://ftp.debian.org/debian//pool/main/libv/libvirt/libvirt_2.3.0-3.dsc...
last upload to archive has NO git hash
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 12.6M0  119k0 0  23466  0  0:09:23  0:00:05  0:09:18 24573



-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#746005: Current status of lilypond in experimental

[Dr. Tobias Quathamer]

Hi,

unfortunately, there's no real news on lilypond. I've just tried to 
build the current upstream (2.19.49) in experimental, because there's a 
new guile-2.0 version available in unstable (2.0.13) since a few days.


I had hoped that some of the bugs concerning lilypond had been fixed in 
the new guile version, but the build still fails at the same stage with 
the same error (#Measure_counter_engraver).


Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#842334: [pkg-gnupg-maint] Bug#842334: Needs an X display to run?

[Daniel Kahn Gillmor]

Control: tags 842334 + moreinfo unreproducible

Hi Julien--

On Fri 2016-10-28 03:47:24 -0400, Julien Puydt wrote:
> I hadn't signed a Debian package since a few days, and it's now failing 
> because I do remote work on a host without X access. The last time I 
> worked on Debian packaging there was a curses window showing up asking 
> for the password to the key.

That should still be the case.  Can you describe the situation you're in
in more detail?  I can make a signature using a curses window for
passphrase prompting.

In particular answers to any or all of the questions below would help me
understand your use case:

 * what versions of pinentry do you have installed?
 * do you have dbus-user-session installed?
 * which version of pinentry is the default pinentry?
 * is there a concurrent graphical (X11) session running for the user
   account that you're using?
 * how are you connecting to the remote host?
 * what session management governs your non-X session on the remote host?

If you've got a running dbus session (whether you have dbus-user-session
or not), and you're using pinentry-gnome3, can you try rebuilding it
with the patch i mentioned in  https://bugs.debian.org/841909  and let
me know how that works?

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#793116: systemd-journald exiting with SIGUSR1

[Daniel Povey]

To follow up: this did not fix the problem.

On Fri, Oct 21, 2016 at 2:45 PM, Daniel Povey  wrote:

> I just want to follow up on this that I believe I have found the reason
> for this bug and I have a solution which I am testing out.
>
> In the output of `systemctl status systemd-journald` it says:
>Active: failed (Result: start-limit)
> and this is related to the systemd mechanism to stop cycles where services
> keep restarting.  It's related to the configs
> StartLimitIntervalSec=   [defaults to DefaultStartLimitIntervalSec=10 sec
> by default]
> StartLimitBurst=  [defaults to DefaultStartLimitBurst=5 by default]
>
> so that if a service is restarted 5 times within 10 seconds, it's not
> restarted any more to avoid wasting resources.
> What seems to happen is that if systemd-journal-flush.service sends the
> signal SIGUSR1 to systemd-journald and systemd-journald wasn't ready to
> handle it for some reason (e.g. had just been started, or there was some
> hangup), then systemd-journald is restarted, and
> systemd-journal-flush.service immediately restarts also.  Again
> systemd-journald won't be ready to handle the signal as it hasn't had time
> to run the signal handler, and the cycle repeats 5 times until the
> systemd-journald service hits the StartLimitBurst and dies.  I verified
> using `lastcomm` (we have process accounting enabled) that this did in fact
> happen.
>
> The way I am trying to fix it is to introduce a restart delay of 10
> seconds into the systemd-journal-flush service.  See the config file below;
> the only new line that differs from the defaults in
>  /lib/systemd/system/systemd-journal-flush.service is the line
> RestartSec=10.
>
> Dan
>
>
>
> ==
> cat /etc/systemd/system/systemd-journal-flush.service
> #  This file is part of systemd.
> #
> #  systemd is free software; you can redistribute it and/or modify it
> #  under the terms of the GNU Lesser General Public License as published by
> #  the Free Software Foundation; either version 2.1 of the License, or
> #  (at your option) any later version.
>
> [Unit]
> Description=Trigger Flushing of Journal to Persistent Storage
> Documentation=man:systemd-journald.service(8) man:journald.conf(5)
> DefaultDependencies=no
> Requires=systemd-journald.service
> After=systemd-journald.service local-fs.target remote-fs.target
> Before=systemd-user-sessions.service
> # Don't re-start this service too often, or we can get into a cycle where
> # if this service was run just after systemd-journald was started, it
> # fails to handle the signal, causing that service to be restarted
> # and this servie to be immediately restarted also, until we hit
> # the limit of StartLimitBurst=5 restarts and systemd-journald
> # dies.
> RestartSec=10
>
> [Service]
> ExecStart=/bin/systemctl kill --kill-who=main --signal=SIGUSR1
> systemd-journald.service
> Type=oneshot
>
>
> On Sat, Oct 15, 2016 at 9:48 PM, Daniel Povey  wrote:
>
>> Another observation about this bug, which might be helpful.
>>
>> If the signal is sent to systemd-journald via
>> /bin/systemctl kill --kill-who=main --signal=SIGUSR1
>> systemd-journald.service
>> then messages like the following show up in the kernel messages from
>> `dmesg -T`, like:
>>
>> [Sat Oct 15 21:02:35 2016] systemd-journald[26517]: Received request to
>> flush runtime journal from PID 1
>>
>> but they don't show up in the output of 'journalctl -r'.
>> In  /etc/systemd/journald.conf, it says:
>>
>> #MaxLevelStore=debug
>> #MaxLevelSyslog=debug
>>
>> so I would have thought the same messages would go to both places.
>> I don't know if I'm misunderstanding something here..
>>
>> Dan
>>
>>
>>
>>
>>
>> On Sat, Oct 15, 2016 at 9:07 PM, Daniel Povey  wrote:
>>
>>> BTW, I attach the output from `systemd-analyze dump`, as dump.txt.
>>> It would be great if the debian people could help us look into this.
>>> Lennart has a policy that his team will only look into bug reports in
>>> the latest two versions of systemd, and obviously we are well behind that.
>>>
>>> Dan
>>>
>>>
>>> On Sat, Oct 15, 2016 at 8:53 PM, Daniel Povey  wrote:
>>>

 I just want to report that we are suffering from this bug, and it is
 quite frequent.
 This is with version  215-17+deb8u5 .

 root@a12:~# systemctl status systemd-journald

 *** systemd-journald.service - Journal Service

Loaded: loaded (/lib/systemd/system/systemd-journald.service;
 static)

Active: *failed* (Result: start-limit) since Sat 2016-10-15
 12:01:57 EDT; 8h ago

  Docs: man:systemd-journald.service(8)

man:journald.conf(5)

   Process: 51561 ExecStart=/lib/systemd/systemd-journald *(code=killed,
 signal=USR1)*

  Main PID: 51561 (code=killed, signal=USR1)



>>>
>>
>