Bug#775090: logcheck-database: Should filter shh preauth disconnect ok messages

[Adrian Heine]

Package: logcheck-database
Version: 1.3.17
Severity: normal
Tags: patch

I get tons of messages for sshd like these:

  Received disconnect from [IP]: 11: ok [preauth]

`Bye Bye [preauth]` is already filtered out.

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From fc9a190720510e14039505229c9e6c0803ebde3f Mon Sep 17 00:00:00 2001
From: Adrian Heine 
Date: Sun, 11 Jan 2015 08:34:07 +0100
Subject: [PATCH] server/ssh: Better match for preauth disconnect

---
 rulefiles/linux/ignore.d.server/ssh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rulefiles/linux/ignore.d.server/ssh b/rulefiles/linux/ignore.d.server/ssh
index 890d20a..9c6ec96 100644
--- a/rulefiles/linux/ignore.d.server/ssh
+++ b/rulefiles/linux/ignore.d.server/ssh
@@ -14,7 +14,7 @@
 ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Postponed keyboard-interactive(/pam)? for (invalid user )?[^[:space:]]+ from [^[:space:]]+ port [[:digit:]]+( (ssh|ssh2)( \[preauth\])?)?$
 ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Received disconnect from [:.[:xdigit:]]+: [12]: Timeout, server not responding\.$
 ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Received disconnect from [:.[:xdigit:]]+: 11: (disconnected by user|Closed due to user request\.)$
-^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Received disconnect from [:.[:xdigit:]]+: 11: Bye Bye \[preauth\]$
+^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Received disconnect from [:.[:xdigit:]]+: 11: (Bye Bye|ok) \[preauth\]$
 ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Received disconnect from [:[:xdigit:].]+: [[:digit:]]+: Client disconnect$
 ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Received disconnect from [:[:xdigit:].]+: [[:digit:]]+: Disconnect requested by Windows SSH Client\.$
 ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: Connection closed by [:.[:xdigit:]]+ \[preauth\]$
-- 
2.1.4

Bug#775066: zeromq: New Upstream releases

[GCS]

On Sat, Jan 10, 2015 at 11:44 PM, Josue Ortega
 wrote:
> Package: libzmq1
> Version: 2.2.0+dfsg-6
>
> I've found this package is 2 versions behind of the latesst upstream version.
> Is there any reason to keep the version 2.2.0 in the archive?
 As I know there's no lagging behind upstream, it's the latest v2
release[1]. Please tell me if you know otherwise.
Yes, it's needed as amavisd-new depends on libzeromq-perl which in
turns depends on libzmq1 .

> Also I've found the watch file has the version 2 hardcoded. I am attaching a
> patch to fix the watch file.
 It hardcodes 2 as it's the v2 release. Your patch just create confusion.

Regards,
Laszlo/GCS
[1] https://github.com/zeromq/zeromq2-x/releases


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#731709: Updated EFI patch

[Raphael Hertzog]

Hi,

On Sat, 10 Jan 2015, jnqnfe wrote:
> "After includes/hooks because it copies in efi.img files that can be
> overriden by binary_includes and modified by binary_hooks"
> 
> Do you have examples of existing hooks/includes which actually clash
> with the new files?

In Kali we use both of those features to modify the syslinux
configuration & related data (background image). If binary_efi copies the
syslinux configuration & data before those scripts have run, the EFI boot
menu doesn't have the correct content/look.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774348: RFS: hebrew-cal/1.0 [ ITP]

[Avi Software]

I have fixed all of those. i will be happy to get sponsor for this.

2015-01-01 22:45 GMT+02:00 Riley Baird wrote:

> Hi, I'm not a DD, so I can't sponsor your package, but I've had a look
> and here are some things I've noticed:
>
> * Your package should be a non-native package, because it isn't
> exclusive to Debian.
>
> fix.


> * You need to update the standards version in d/control to 3.9.6
>
> fix.

> * You say that hebrew-cal is based on libhdate and zmanim-java-API.
> Debian policy forbids convenience copies, so would it be possible to
> simply depend on the libhdate packages? You might also have to package
> kosherjava to meet this policy, but maybe someone else on the list can
> confirm this.
>
> i changed this, and it is now depend on libhdate.
about  zmanim-java-API: I took from him a very small piece of code, I fork
it, and if it will be a problem, I will cut it...


> * You need to make a manpage for hebrew-cal.
>
> fix

> * You should have a watch file.
>
> fix

> * In data/hebrew-cal.desktop, you do not need to specify the encoding.
>
> fix.

> * In data/hebrew-cal.desktop, add a "Keywords" field. See
> https://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html
> 
> for more information.
>
> fix.

> * Your short description would ideally give more information than
> "Hebrew Calendar". How about "a beautiful, Qt-based Hebrew calendar"
>
> * Your long description doesn't sound natural. How about:
>  hebrew-cal is a beautifully designed Hebrew calendar
>  which is very easy to use and customize.
>  The calendar includes Hebrew dates, holidays,
>  times, Parshiot Hashavua, Daf Yomi, and more.
>  .
>  The appearance can be changed, the colors are editable
>  and calendars can be printed.
>  .
>  It is written in C++ using the Qt libraries, and is
>  based on the libhdate code and zmanim-java-API.
>
> fix.

> Good luck getting your package into Debian!
>
> Riley Baird
>

here is my changlog:
hebrew-cal (1.1-1) unstable; urgency=low
 * update control file
 * add man file
 * add watch file
 * depend on hdate
 * change to quilt
-- Avi Software  Wed, 07 Jan 2015 12:55:27 +0200

thank you everybody.
Avi Software.

Bug#774134: Info received (Bug#774134: pre-approval: unblock: wader/0.5.12-1.1)

[Graham Inggs]

Is any further information needed from me?

Wader has since been orphaned (#774577) and I will close that bug in
the changelog.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775050: FTCBFS for arm64: failure to determine stack direction

[Helmut Grohne]

On Sat, Jan 10, 2015 at 11:37:09PM +, peter green wrote:
> Can you confirm that FTCBFS stands for "fails to cross build from source"?

I do.

> However I would expect that either way the release team will consider this
> something that should be dealt with post-jessie.

I did not mean to imply anything to the contrary. Accordingly, this bug
is filed at non-rc severity. I did not expect an upload fixing this
before jessie. Yet, I did not see a reason to withhold this patch.

Helmut


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775089: linkchecker-web: lc.wsgi script unable to run in web interface

[Riley]

Package: linkchecker-web
Version: 9.3-1
Severity: important

Dear Maintainer,

My webserver is lighttpd. I have successfully configured it to run python
scripts in a cgi-bin directory with .wsgi extensions.

However, despite this, the provided lc.wsgi script does not produce any output
when run. When a URL is entered, the only output is "500 - Internal Server
Error". If 'print "Content-Type: text/html\n\n"' is added to lc.wsgi, this
error disappears and a blank page remains.

When the below command is run from the command line, there is no output:
$ python lc.wsgi

Yours thankfully,

Riley Baird



-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

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

Versions of packages linkchecker-web depends on:
ii  libapache2-mod-wsgi [httpd-wsgi]  4.3.0-1
ii  lighttpd [httpd]  1.4.35-4
ii  linkchecker   9.3-1
ii  python2.7.8-2

linkchecker-web recommends no packages.

linkchecker-web suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#760911: gcc-arm-none-eabi: Version 4.8.3-9+11 breaks Linux kernel build

[Agustin Henze]

First of all thank you for you bug report and sorry for the long delay I will 
fix this next week. Help is always welcomed :) and if you send me a patch much 
better. On the other hand today I have uploaded to experimental a gcc 4.9 based 
with this patch applied.

Cheers,
--
TiN

Bug#775088: linkchecker-web: Add information from cgi-bin/README into debian/README.Debian.web

[Riley]

Package: linkchecker-web
Version: 9.3-1
Severity: wishlist

Dear Maintainer,

It is at first difficult to realise that .en (or .de) needs to be stripped from
the files without mod_negotiation enabled. If the information in cgi-bin/README
were incorporated into debian/README.Debian.web, it would make this easier to
figure out.

Yours sincerely,

Riley Baird



-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

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

Versions of packages linkchecker-web depends on:
ii  libapache2-mod-wsgi [httpd-wsgi]  4.3.0-1
ii  lighttpd [httpd]  1.4.35-4
ii  linkchecker   9.3-1
ii  python2.7.8-2

linkchecker-web recommends no packages.

linkchecker-web suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775065: dpkg --configure -a results in "Hangup" after first package

[Guillem Jover]

Hi!

On Sat, 2015-01-10 at 22:42:56 +, Chris Carr wrote:
> Package: dpkg
> Version: 1.17.23

> I have been away from Debian development for over a year due to some RL
> issues. I booted my Sid box and did apt-get update and then upgrade, and
> everything went wrong. Full story (badly told) is at
> 
> http://forums.debian.net/viewtopic.php?f=5&t=119834

To be honest, I've just skimmed over that URL, because the issue here
seems quite confused, with many broken parts. But this does not seem
to me to be a problem in dpkg itself.

> The issue I have now is that whenever I try to use apt-get I am told  "dpkg
> was interrupted, you must manually run 'dpkg --configure -a' to correct the
> problem". Running this as root results in
> 
> Setting up cups-daemon (1.7.5-10) ...
> Hangup
> 
> ... without that package being configured, nor any others.

Please run «dpkg -D7 --configure -a 2>&1 | tee dpkg.log», and
attach the output. We can check from there

> If this is not a bug in dpkg, please could someone tell me how to go about
> diagnosing and correcting it? I need to be able to finish installing and
> configuring the ~55 half-done packages so that I can get my system working
> again. At the moment it doesn't boot properly and drops me into emergency
> mode. I cannot run openssh-server or reportbug.

Hmm, if you are on an emergency shell, I guess the system is not
properly booted, are all partitions mounted? Otherwise there's no
wonder things are not being configured correctly.

If that's the case, then this is probably a problem with your init
system or thereabouts.

Thanks,
Guillem


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#757298: Please add fallback boot entry for sysvinit when systemd is the active init

[I. Schrey]

Am 10.01.2015 um 19:19 schrieb Colin Watson:

> Oh, right, there's absolutely no guarantee that menu entry numbers won't
> change.
> This is exactly why the ability to set the default to a name
> was introduced; you need to use that if you want predictable behaviour
> across upgrades.
>
> (In this case, of course, you'd need to use two names separated by ">"
> to account for the submenu.)
>

I was afraid you were gonna say that. ;)
Yeah, maybe I should try getting used to using names instead
of numbers. Although,

grub-reboot 
(frequent use) is easier for me to remember than
grub-reboot 

...but hey, grub-reboot seems to have tab completion!
*makes mental note*


Anyway, case closed I guess, thank you for the reminder,
pardon me for wasting our time.


Regards
Ingmar


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775084: devscripts: [rmadison] No/wrong support for "-b TYPE"

[Cyril Brulebois]

James McCoy  (2015-01-10):
> On Sun, Jan 11, 2015 at 03:19:00AM +0100, Cyril Brulebois wrote:
> > man rmadison and a quick glance at the script suggest that support is
> > supposed to be there, so it might just be some bug on the UDD side;
> 
> Indeed, it is.  UDD doesn't gather the Package-Type information.  I had
> been considering switching the default URL to
> https://api.ftp-master.debian.org/madison and this looks like another
> reason to do that.
> 
> In the interim you can use either “rmadison -u
> https://api.ftp-master.debian.org/madison …” or add
> 
>   RMADISON_URL_MAP_DEBIAN=https://api.ftp-master.debian.org/madison
> 
> to ~/.devscripts.

Thanks for the confirmation and the workaround; that'll probably be
useful to people who don't have this:
  alias rmadison='ssh release.debian.org dak ls'

;)

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#775087: linkchecker-web.postinst requires apache to be installed, despite it not being a dependency

[Riley]

Package: linkchecker-web
Version: 9.3-1
Severity: normal

Dear Maintainer,

I do not have apache2 installed on my system, but I do have lighttpd. When I
"apt-get install linkchecker-web", I get the following error. It seems that the
postinst script requires apache2 to run.

/var/lib/dpkg/info/linkchecker-web.postinst: 29: /var/lib/dpkg/info
/linkchecker-web.postinst: a2enmod: not found
dpkg: error processing package linkchecker-web (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 linkchecker-web
E: Sub-process /usr/bin/dpkg returned an error code (1)

Yours sincerely,

Riley Baird



-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

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

Versions of packages linkchecker-web depends on:
ii  libapache2-mod-wsgi [httpd-wsgi]  4.3.0-1
ii  lighttpd [httpd]  1.4.35-4
ii  linkchecker   9.3-1
ii  python2.7.8-2

linkchecker-web recommends no packages.

linkchecker-web suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775084: devscripts: [rmadison] No/wrong support for "-b TYPE"

[James McCoy]

On Sun, Jan 11, 2015 at 03:19:00AM +0100, Cyril Brulebois wrote:
> rmadison is supposed to be a remote madison aka. dak ls, but here's
> another example of incorrect output:
> | kibi@franck:~$ dak ls -b deb -s testing bash 
> | bash   | 4.3-11+b1 | testing| amd64, arm64, armel, armhf, i386, 
> kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
> 
> but the source is included nonetheless:
> | kibi@arya:~$ \rmadison -b deb -s testing bash 
> |  bash | 4.3-11| jessie | source
> |  bash | 4.3-11+b1 | jessie | amd64, arm64, armel, armhf, i386, 
> kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
> 
> man rmadison and a quick glance at the script suggest that support is
> supposed to be there, so it might just be some bug on the UDD side;

Indeed, it is.  UDD doesn't gather the Package-Type information.  I had
been considering switching the default URL to
https://api.ftp-master.debian.org/madison and this looks like another
reason to do that.

In the interim you can use either “rmadison -u
https://api.ftp-master.debian.org/madison …” or add

  RMADISON_URL_MAP_DEBIAN=https://api.ftp-master.debian.org/madison

to ~/.devscripts.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 


signature.asc
Description: Digital signature

Bug#687904: interchange-ui: cannot install this package

[Riley]

Package: interchange
Version: 5.7.7-2
Followup-For: Bug #687904

Will this bug be able to be fixed before jessie is released? Otherwise, I would
recommend that you file an RM bug against release.debian.org, since the package
is non-functional as it currently stands.



-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

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

Versions of packages interchange depends on:
ii  adduser  3.113+nmu3
ii  debconf [debconf-2.0]1.5.55
ii  libc62.19-13
pn  libdigest-md5-perl   
pn  libdigest-sha-perl   
ii  libhtml-parser-perl  3.71-1+b3
pn  libmime-base64-perl  
ii  libsafe-hole-perl0.13-1+b3
ii  libset-crontab-perl  1.02-1
ii  libtie-shadowhash-perl   1.00-1
ii  liburi-perl  1.64-1
ii  libwww-perl  6.08-1
ii  logrotate3.8.7-1+b1
ii  perl [libstorable-perl]  5.20.1-4

Versions of packages interchange recommends:
ii  interchange-ui  5.7.7-2

interchange suggests no packages.

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774838: weboob: insecure keyring handling

[Cyril Brulebois]

Hi,

and sorry for the lag, been busy with some offline things.

Romain Bignon  (2015-01-08):
> On 08/Jan - 11:11, Cyril Brulebois wrote:
> > I would expect the Debian packages to contain some kind of trust chain
> > to bootstrap the keyring handling, and weboob to abort instead of
> > “blindly accepting” in other cases.
> 
> You're right we should have the official keyring distributed in the
> Debian package, but in case the user adds a new repository, we
> shouldn't reject it but ask him to accept (like ssh)?

yes, that looks like a sane thing to do (possibly pointing to some
instructions on how to check the trust chain).

> I'm going to send a patch on the package this week.

Great, thanks.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#773245: git-p4 package in contrib, how to proceed?

[Vincent Cheng]

On Sat, Jan 10, 2015 at 10:12 AM, Luke Diamand  wrote:
> Hi!
>
> I'm trying to create a package  for 'git-p4', a python script which mirrors
> between git and Perforce (the latter is a proprietary version control
> system). I'm looking for advice on the best way to do this.
>
> The source code lives in the upstream git repository, but isn't packaged
> with the regular 'git' package because of the proprietary nature of
> Perforce. I thought I'd try to create a separate package that could go into
> contrib instead.
>
> I've created a bug report with a patch for the git package to implement this
> (773245) which Jonathan Nieder was kind enough to look at, but I'm
> struggling to understand what I should do next!
>
> Is it going to be possible to get the regular git package to generate a
> secondary package in contrib? Or would I be better off with a new standalone
> package?

Yes, source packages in main can generate binary packages in contrib;
Policy does not prevent this from happening, and there are existing
source packages in main, in the archive, which generate binary
packages in contrib. See e.g. src:nvidia-settings (and #747837 which
was what prompted one of the binary packages built from it to be moved
from contrib to main).

Regards,
Vincent


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775086: xfburn fails on a Mac Mini and a Macbook Pro

[Jim Ham]

Package: xfburn
Version: 0.5.2-1
Severity: important

Dear Maintainer,

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


  * What led up to the situation?
  Burn fails on both the Mini and the Macbook Pro. OS-X works, K3b 
works. Both Mini and Macbook are early Intel machines with CoreDuo 
processors.

  * What exactly did you do (or not do) that was effective (or
ineffective)?
xfburn continues inop.
  * What was the outcome of this action?
  Had to install the K libraries :-(
  * What outcome did you expect instead?

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

Here's the results of starting xfburn from the command line:

jeh@Mini:~$ xfburn
** Message: Using UDEV
** Message: Using gstreamer transcoder.

** (xfburn:3769): WARNING **: Read-only profile 0x8!

** (xfburn:3769): WARNING **: [FATAL] 131357: SCSI error on 
write(32,16): [5 24 00] Illegal request. Invalid field in cdb. (0)


** (xfburn:3769): WARNING **: [FATAL] 131339: Burn run failed (0)
^C
jeh@Mini:~$

xfburn writes the lead-in but fails to write any data.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 xfburn depends on:
ii  libburn4 1.3.2-1.1
ii  libc62.19-13
ii  libexo-1-0   0.10.2-4
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgstreamer-plugins-base0.10-0  0.10.36-2
ii  libgstreamer0.10-0   0.10.36-1.5
ii  libgtk2.0-0  2.24.25-1
ii  libgudev-1.0-0   215-8
ii  libisofs61.3.2-1.1
ii  libxfce4ui-1-0   4.10.0-6
ii  libxfce4util64.10.1-2

xfburn recommends no packages.

xfburn suggests no packages.

-- no debconf information


Porcine Associates +1.650.326.2669 www.porcine.com


-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5645 / Virus Database: 4257/8906 - Release Date: 01/10/15


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775085: (no subject)

[Jim Ham]

Package: xfburn

Version: 0.5.2-1

Severity: important



Dear Maintainer,



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



  * What led up to the situation?

  Burn fails on both the Mini and the Macbook Pro. OS-X works, K3b works. Both 
Mini and Macbook are early Intel machines with CoreDuo processors.

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

ineffective)?

xfburn continues inop.

  * What was the outcome of this action?

  Had to install the K libraries :-(

  * What outcome did you expect instead?



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



Here's the results of starting xfburn from the command line:



jeh@Mini:~$ xfburn

** Message: Using UDEV

** Message: Using gstreamer transcoder.



** (xfburn:3769): WARNING **: Read-only profile 0x8!



** (xfburn:3769): WARNING **: [FATAL] 131357: SCSI error on write(32,16): [5 24 
00] Illegal request. Invalid field in cdb. (0)



** (xfburn:3769): WARNING **: [FATAL] 131339: Burn run failed (0)

^C

jeh@Mini:~$ 






-- System Information:

Debian Release: 8.0

 APT prefers testing-updates

 APT policy: (500, 'testing-updates'), (500, 'testing')

Architecture: amd64 (x86_64)

Foreign Architectures: i386



Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 xfburn depends on:

ii  libburn4 1.3.2-1.1

ii  libc62.19-13

ii  libexo-1-0   0.10.2-4

ii  libgdk-pixbuf2.0-0   2.31.1-2+b1

ii  libglib2.0-0 2.42.1-1

ii  libgstreamer-plugins-base0.10-0  0.10.36-2

ii  libgstreamer0.10-0   0.10.36-1.5

ii  libgtk2.0-0  2.24.25-1

ii  libgudev-1.0-0   215-8

ii  libisofs61.3.2-1.1

ii  libxfce4ui-1-0   4.10.0-6

ii  libxfce4util64.10.1-2



xfburn recommends no packages.



xfburn suggests no packages.



-- no debconf information





Porcine Associates +1.650.326.2669 www.porcine.com


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#773805: liblucene4-java: Incomplete poms installed in /usr/share/maven-repo

[tony mancill]

On 01/07/2015 10:41 PM, Niels Thykier wrote:
> On 2015-01-08 05:17, tony mancill wrote:
>> [...]
>>
>>
>> Hello Hilko, Emmanuel,
>>
>> I'm taking a look at this, but in the interest of the jessie release, I
>> wanted to ask Emmanuel whether it would be okay to decrease the severity.
>>
>> We have a number of other packages with missing or incomplete poms, and
>> propose that we discuss maven metadata for all Java library packages as
>> a release goal for jessie + 1.
>>
>> Otherwise, the package will be removed soonish (February 5th).
>>
>> https://tracker.debian.org/pkg/lucene4
>>
>> Thanks,
>> tony
>>
>> [...]
> 
> Hi,
> 
> If the bug is RC on its own, but you believe it is irrelevant for the
> Jessie release, the correct option would be to have it ignored (please
> file a bug against release.debian.org for that).
>   Mind you, the assumption is that the bug is in fact RC.  If not, the
> release team will probably recommend downgrading it instead.
> 
> If the bug only prevents "new packages" from being build (i.e. packages
> not already in Jessie/sid), it /sounds/ like it might not be RC after
> all (maybe "important").  However, please keep in mind that my answer is
> solely based on the above mail.

Hi Niels,

Thank you for the guidance.  In the case of #773805 (maven pom), I do
believe that it's not RC from a severity standpoint.

I think #773829 might fall into the same category, although I do have a
patch and will be uploading a new package with just this build change
tomorrow morning.

Cheers,
tony




signature.asc
Description: OpenPGP digital signature

Bug#775084: devscripts: [rmadison] No/wrong support for "-b TYPE"

[Cyril Brulebois]

Package: devscripts
Version: 2.15.1
Severity: important

Hi,

rmadison is supposed to be a remote madison aka. dak ls, but here's
another example of incorrect output:
| kibi@franck:~$ dak ls -b deb -s testing bash 
| bash   | 4.3-11+b1 | testing| amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x

but the source is included nonetheless:
| kibi@arya:~$ \rmadison -b deb -s testing bash 
|  bash | 4.3-11| jessie | source
|  bash | 4.3-11+b1 | jessie | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x

man rmadison and a quick glance at the script suggest that support is
supposed to be there, so it might just be some bug on the UDD side; but
since that's what rmadison relies on, I'm reporting here for the time
being.

Mraw,
KiBi.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775082: game-data-packager: move quake, quake2 to Python/YAML

[Simon McVittie]

Package: game-data-packager
Version: 39
Severity: wishlist
Control: block -1 by 775078 775079

I think my experiment with declarative game data has been a success
and I would like to use it for all the games. quake and quake2 need
a couple more features first, though.

Ideally, I would also like q2rogue and q2xatrix to become part of
quake2, but that requires either uploading Yamagi's game-code modules
to non-free (preferred, if the license is distributable, because they're
source code that we can patch) or doing a lot of custom code in
lib/game_data_packager/games/quake2.py.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775083: game-data-packager: move lgeneral-data-nonfree to Python/YAML

[Simon McVittie]

Package: game-data-packager
Version: 39
Severity: wishlist

lgeneral-data-nonfree should ideally be converted to be declarative.
This is going to need custom code in lib/game_data_packager/games/lgeneral.py
because there's no way its logic is going to be usefully generic.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775081: game-data-packager: convert doom-common packages to Python/YAML

[Simon McVittie]

Package: game-data-packager
Version: 39
Severity: wishlist
Control: block -1 by 775079

When #775079 has been fixed, it should be straightforward to move doom, doom2,
heretic, hexen, plutonia and tnt to YAML. We might as well add hexdd
(#737137) at the same time.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#733459: game-data-packager: md5 checksum error packing hexen II data

[Simon McVittie]

Control: tags -1 + pending

On Tue, 31 Dec 2013 at 15:41:56 +, Jonathan Dowland wrote:
> Finally, praevus is not yet supported, that should be pretty easy to
> add, I was not aware of hexenworld's pak4 and indeed we should manage
> that too.

g-d-p git supports packaging portals/pak3.pak (Portal of Praevus)
and hw/pak4.pak (HexenWorld, which seems to be redistributed
from the uHexen2 developers).

I've assumed that both of these are expansions that require the base
game in addition, like Quake III Team Arena.

S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775080: game-data-packager: Python code should be less trigger-happy about downloading expansions

[Simon McVittie]

Package: game-data-packager
Version: 39
Severity: wishlist

(Yes I know this is a bug report for a version I haven't even released
yet.)

If I add a download URL for hexenworld-pakfiles-0.15.tgz in hexen2.yaml,
every time I run "game-data-packager hexen2 /.../steamapps/common/Hexen 2",
it will download hexenworld-pakfiles-0.15.tgz and produce
hexen2-hexenworld-data. This is ... overly enthusiastic.
ja would have the same problem for the semi-official addons
if I had a download URL for them that didn't involve jumping through
JavaScript hoops.

This would become a serious problem if I added support for a
major mod, e.g. Threewave CTF for quake3, which I'm considering doing;
every time someone wanted to pack up Q3A or Q3TA, as a side-effect,
g-d-p would try to download Threewave, which is rather large.

g-d-p should not fill gaps in expansions via auto-download
unless it has seen some "key file" from the expansion, or the expansion
has been requested specifically. Purely downloadable expansions would
not have any key files listed, but g-d-p should still be prepared to
(for instance) download quake2-xatrix-2.00.tar.xz to fill in
missing files, *if* it has been given xatrix/pak0.pak as input.

S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775079: game-data-packager: Python/YAML needs support for installing files distributed in g-d-p

[Simon McVittie]

Package: game-data-packager
Version: 38
Severity: wishlist

The Python/YAML code does not yet know how to install misc files from
game-data-packager's datadir.

This is a prerequisite for porting all doom-common games (doom, doom2,
heretic, hexen, plutonia, tnt) to Python/YAML: they all want to install
doom2.xpm and a .desktop file.

It is also a prerequisite for quake, which uses a dummy executable
(need-exec.sh) to trigger the TryExec feature in .desktop files.

S


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775076: adt-setup-vm: sets force-unsafe-io for host dpkg, not guest

[Christian Kastner]

On Sun, 11 Jan 2015 02:12:25 +0100 Christian Kastner  wrote:
> adt-setup-vm creates /etc/dpkg/dpkg.cfg.d/autopkgtest on the host, 
> instead of in the guest, because the path is missing the $root
> prefix pointing to the directory where the guest's root is mounted.
> 
> This is very unfortunate, as that file sets force-unsafe-io for
> dpkg, so this puts the host at risk to data loss.

This was introduced by the following commit,

Regards,commit 86c333020caa05bcd6f964ef5fdcf2c8594065a1
Author: Martin Pitt 
Date:   Thu Oct 9 13:09:25 2014 +0200

tools/adt-setup-vm: Add setup steps that adt-buildvm-ubuntu-cloud does

So that vmdebootstrap generated VMs are functionally on par with the Ubuntu
cloud images: Set up serial console, dpkg unsafe-io, install some additional
packages, remove unnecessary packages, bump vmalloc on i386.

so it entered Jessie.

I have attached a debdiff for the version in Jessie which includes the
bugfix from my earlier patch, and adds a postinst in which the offending
file is removed.

If there's anything else I can do to help, please let me know.

Regards,
Christian
diff -Nru autopkgtest-3.6/debian/changelog autopkgtest-3.6+nmu1/debian/changelog
--- autopkgtest-3.6/debian/changelog2014-10-16 16:36:18.0 +0200
+++ autopkgtest-3.6+nmu1/debian/changelog   2015-01-11 02:44:56.0 
+0100
@@ -1,3 +1,16 @@
+autopkgtest (3.6+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * adt-setup-vm: Add the missing $root prefix (the mountpoint of the guest's
+root directory) when creating /etc/dpkg/dpkg.cfg.d/autopkgtest, otherwise
+it sets unforce-safe-io on the host instead, putting it at risk of data
+loss. Closes: #775076.
+  * Create debian/postinst and remove the file /etc/dpkg/dpkg.cfg.d/autopkgtest
+if its contents are just "force-unsafe-io", indicating that this file was
+generated by the above bug.
+
+ -- Christian Kastner   Sun, 11 Jan 2015 02:04:19 +0100
+
 autopkgtest (3.6) unstable; urgency=medium
 
   [ Antonio Terceiro ]
diff -Nru autopkgtest-3.6/debian/postinst autopkgtest-3.6+nmu1/debian/postinst
--- autopkgtest-3.6/debian/postinst 1970-01-01 01:00:00.0 +0100
+++ autopkgtest-3.6+nmu1/debian/postinst2015-01-11 02:34:02.0 
+0100
@@ -0,0 +1,17 @@
+#!/bin/sh
+
+set -e
+
+if [ "$1" != configure ]; then
+   exit 0
+fi
+
+# If this file exists and its only content is "force-unsafe-io", then it was
+# generated by #775076 and must be removed.
+if [ -e /etc/dpkg/dpkg.cfg.d/autopkgtest ]; then
+   if [ "`cat /etc/dpkg/dpkg.cfg.d/autopkgtest`" = "force-unsafe-io" ]; 
then
+   rm -f /etc/dpkg/dpkg.cfg.d/autopkgtest
+   fi
+fi
+
+#DEBHELPER#
diff -Nru autopkgtest-3.6/tools/adt-setup-vm 
autopkgtest-3.6+nmu1/tools/adt-setup-vm
--- autopkgtest-3.6/tools/adt-setup-vm  2014-10-16 16:36:18.0 +0200
+++ autopkgtest-3.6+nmu1/tools/adt-setup-vm 2015-01-11 01:58:38.0 
+0100
@@ -74,7 +74,7 @@
 
 # go-faster apt/dpkg
 echo "Acquire::Languages \"none\";" > "$root"/etc/apt/apt.conf.d/90nolanguages
-echo 'force-unsafe-io' > /etc/dpkg/dpkg.cfg.d/autopkgtest
+echo 'force-unsafe-io' > "$root"/etc/dpkg/dpkg.cfg.d/autopkgtest
 
 # auto-detect apt-cacher-ng
 if [ -z "${ADT_APT_PROXY:-}" ]; then

Bug#775078: game-data-packager: Python/YAML code should support ripping CD audio

[Simon McVittie]

Package: game-data-packager
Version: 38
Severity: wishlist

The Python code does not yet support ripping tracks 2+ of a mixed data/audio
CD to Ogg Vorbis, which is a prerequisite for porting the quake and quake2
subcommands to Python + YAML.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775077: autorun.inf line endings

[jnqnfe]

Package: live-build
Version: 4.0.4-1

One of the modifications introduced in my #772781 patch, but dropped in
the slightly modified copy adopted, was to switch autorun.inf creation
to use the 'todos' tool as debian-cd does, instead of 'cat', to ensure
Windows friendly line endings are written in this file. Unix line
endings may break its intended use (I haven't tested). I'm not sure if
the continued use of cat was deliberate or a mistake, and whether this
is a problem or not (needs testing).


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775072: openjdk-7-jre: cleanup broken alternatives left by openjdk-6-jre: javaws, pluginappletviewer

[Andreas Beckmann]

Followup-For: Bug #775072

Hi,

attached is an updated patch for openjdk-7-jre to clean up the ancient
alternatives.

Unfortunately I couldn't test it due to the "10 years" FTBFS #775044


Andreas
diff -Nru openjdk-7-7u71-2.5.3/debian/JB-jre.preinst.in openjdk-7-7u71-2.5.3/debian/JB-jre.preinst.in
--- openjdk-7-7u71-2.5.3/debian/JB-jre.preinst.in	2014-10-17 02:09:34.0 +0200
+++ openjdk-7-7u71-2.5.3/debian/JB-jre.preinst.in	2013-01-11 01:04:52.0 +0100
@@ -10,6 +10,18 @@
 old_basedir=/usr/lib/jvm/java-7-openjdk
 jre_tools='policytool'
 
+
+case "$1" in
+install|upgrade)
+	# cleanup obsolete alternatives left by openjdk-6-jre/squeeze
+	if dpkg --compare-versions "$2" lt "7u71-2.5.3-3~"; then
+	for i in javaws pluginappletviewer; do
+		update-alternatives --remove $i /usr/lib/jvm/java-6-openjdk/jre/bin/$i || true
+	done
+	fi
+	;;
+esac
+
 case "$1" in
 upgrade)
 	if [ -n "$multiarch" ] && [ -n "$2" ]; then
diff -Nru openjdk-7-7u71-2.5.3/debian/changelog openjdk-7-7u71-2.5.3/debian/changelog
--- openjdk-7-7u71-2.5.3/debian/changelog	2014-11-13 11:10:36.0 +0100
+++ openjdk-7-7u71-2.5.3/debian/changelog	2013-01-11 01:10:06.0 +0100
@@ -1,3 +1,10 @@
+openjdk-7 (7u71-2.5.3-3) UNRELEASED; urgency=medium
+
+  * Cleanup obsolete alternatives (javaws, pluginappletviewer) left by
+openjdk-6-jre/squeeze.  (Closes: #xx)
+
+ -- Andreas Beckmann   Sun, 11 Jan 2015 01:04:57 +0100
+
 openjdk-7 (7u71-2.5.3-2) unstable; urgency=medium
 
   * Regenerate the .orig.tar to omit a third hotspot tarball.

Bug#638720: Odoo packaging

[W. Martin Borgert]

Preliminary work is here:
http://anonscm.debian.org/gitweb/?p=collab-maint/odoo.git

Any help appreciated, e.g. with:

 * remove non-sources from source tree
 * package embedded JavaScript libraries separately
 * implement use of dbconfig-common?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#630199: stardict-tools: stardict-editor fails to compile tab dictionaries with duplicate words

[Hiroshi Miura]

Here is also a bug report on Ubuntu and posted a patch.

BTS: https://bugs.launchpad.net/ubuntu/+source/stardict-tools/+bug/1313920
A patch: 
https://launchpadlibrarian.net/194510738/stardict-tools-tabfile-fix-issue37.diff


Hiroshi


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775075: adt-setup-vm: set umask to 0022

[Christian Kastner]

Source: autopkgtest
Version: 3.9
Severity: normal
Tags: patch

Hi,

umask must be set to 0022, otherwise ordinary users will not be able to
read generated files, eg: /etc/apt/sources.list, if root has a stricter
umask then the default (and adt-setup-vm is called as root).

Regards,
Christian

>From 8fdcbf7b7e6983c58aed920ca839c40003d2d051 Mon Sep 17 00:00:00 2001
From: Christian Kastner 
Date: Sun, 11 Jan 2015 01:15:25 +0100
Subject: adt-setup-vm: set umask to 0022

adt-setup-vm is called as root. If root has a stricter umask, eg: 0027, then
ordinary users within the VM will not be able to read generated files such as
/etc/apt/sources.list. Therefore, ensure it is at 0022.
---
 tools/adt-setup-vm | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tools/adt-setup-vm b/tools/adt-setup-vm
index 933b1c0..cb0c9bb 100755
--- a/tools/adt-setup-vm
+++ b/tools/adt-setup-vm
@@ -15,6 +15,9 @@
 
 set -eu
 
+# Created files should be readable by user adt (this script is called as root)
+umask 0022
+
 if [ "${1:-}" = "--help" ]; then
 echo "Usage: $0 [chroot dir]"
 echo "if chroot dir is not given, run on the main system (for running in VMs)"
-- 
2.1.4

Bug#775076: adt-setup-vm: sets force-unsafe-io for host dpkg, not guest

[Christian Kastner]

Source: autopkgtest
Version: 3.9
Severity: serious
Justification: Unwittingly sets dpkg force-unsafe-io on host
Tags: patch

Hi,

adt-setup-vm creates /etc/dpkg/dpkg.cfg.d/autopkgtest on the host,
instead of in the guest, because the path is missing the $root prefix
pointing to the directory where the guest's root is mounted.

This is very unfortunate, as that file sets force-unsafe-io for dpkg,
so this puts the host at risk to data loss.

Regards,
Christian
>From c8e5aac84d1de20028e85ec236a4a998938bd361 Mon Sep 17 00:00:00 2001
From: Christian Kastner 
Date: Sun, 11 Jan 2015 01:28:36 +0100
Subject: adt-setup-vm: Modify guest's dpkg config, not host's

Add the missing $root prefix (the path to the directory where the guest's root
is mounted) when writing /etc/dpkg/dpkg.conf.d/autopkgtest, otherwise the
host's configuration is modified instead. As force-unsafe-io is being set, this
is very dangerous.
---
 tools/adt-setup-vm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/adt-setup-vm b/tools/adt-setup-vm
index cb0c9bb..b2f83d2 100755
--- a/tools/adt-setup-vm
+++ b/tools/adt-setup-vm
@@ -80,7 +80,7 @@ fi
 
 # go-faster apt/dpkg
 echo "Acquire::Languages \"none\";" > "$root"/etc/apt/apt.conf.d/90nolanguages
-echo 'force-unsafe-io' > /etc/dpkg/dpkg.cfg.d/autopkgtest
+echo 'force-unsafe-io' > "$root"/etc/dpkg/dpkg.cfg.d/autopkgtest
 
 # auto-detect apt-cacher-ng
 if [ -z "${ADT_APT_PROXY:-}" ]; then
-- 
2.1.4

Bug#775073: adt-run: result of execute() is a tuple, not a scalar

[Christian Kastner]

Source: autopkgtest
Version: 3.9
Severity: minor
Tags: patch

Hi,

when vmdebootstrapping with "--package build-essential" I saw this:

adt-run: DBG: testbed command ['which', 'dpkg-source'], kind short, sout 
pipe, serr pipe, env ['LANG=C.UTF-8']
adt-run: DBG: testbed command exited with code 0
adt-run: DBG: dpkg-source not available in testbed, installing dpkg-dev

Note how the last two lines contradict each other.

This is because the check for a 0 exit status is performed against the
entire tuple returned by execute() instead of its the first element,
where the exit status is actually to be found.

Regards,
Christian


>From d7c78dce6a28ec4dfdaa9899c9f1954c6318ec4e Mon Sep 17 00:00:00 2001
From: Christian Kastner 
Date: Sat, 10 Jan 2015 23:54:21 +0100
Subject: adt-run: result of execute() is a tuple, not a scalar

The result of testbed.execute is a tuple (returncode, stdout, stderr), so
a check for a 0 return code must look at the first element of that tuple.
---
 runner/adt-run | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/runner/adt-run b/runner/adt-run
index b8dea94..9172d3a 100755
--- a/runner/adt-run
+++ b/runner/adt-run
@@ -1561,7 +1561,7 @@ def build_source(kind, arg, built_binaries):
 testbed.install_deps([], False)
 if testbed.execute(['which', 'dpkg-source'],
stdout=subprocess.PIPE,
-   stderr=subprocess.PIPE) != 0:
+   stderr=subprocess.PIPE)[0] != 0:
 adtlog.debug('dpkg-source not available in testbed, installing dpkg-dev')
 # Install dpkg-source for unpacking .dsc
 testbed.satisfy_dependencies_string('dpkg-dev',
-- 
2.1.4

Bug#775074: suricata: Enable nflog support

[Hans-Kristian Bakke]

Package: suricata
Version: 2.0.4-1
Severity: wishlist

The source code in 2.0.4-1 has a fully working and very practical nflog 
implementation (I am using it at least), that was just recently added. The 
configure flag is not set hovever so the package is compiled without that 
support. I am running the source code in jessie just rebuilt with 
--enable-nflog set.

Could nflog please be enabled for the default build?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#766726: Assistance

[Justin Zobel]

Keen to assist with the packaging of this item if you need help. Really
want to get it in ASAP.

Bug#775071: Please add user "smmta" to TRUSTED_IDS list

[Michael Grant]

Package: procmail
Version: 3.22-20+deb7

sendmail on debian runs as user 'smmta'.

Please add this user to this user to the TRUSTED_IDS list in config.h:

#define TRUSTED_IDS   {"root","daemon","uucp","mail","x400","network",\
   "list","slist","lists","news", "smmta", 0}

Without this user in the TRUSTED_IDS list, when sendmail, running as smmta,
passes the message to procmail, an extra From line gets added to messages
which looks like this:

>From smmta  Sat Jan 10 18: 18:42 2015

For reference, this was discussed on the sendmail group back in 1999:

https://groups.google.com/forum/#!searchin/comp.mail.sendmail/unix$20from$20line/comp.mail.sendmail/YzCbxAwWQuM/QPaW9D76YjkJ

Bug#775070: startup crash with GL acceleration

[Eduard Bloch]

Package: iceweasel
Version: 31.3.0esr-1
Severity: normal

I made a couple of distupgrades in the last days, on a system running
Sid and using ACPI suspend.

Now it suddenly happened: iceweasel refused to start. Pointless error
message:
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 492: 
elf_machine_rela_relative: Assertion `((reloc->r_info) & 0x) == 8' 
failed!

It's not a hard crash either (no core dumped), it's normaly terminated:

28364 writev(2, [{"Inconsistency detected by ld.so:"..., 33}, 
{"../sysdeps/x86_64/dl-machine.h", 30}, {": ", 2}, {"492", 3}, {": ", 2}, 
{"elf_machine_rela_relative", 25}, {": ", 2}, {"Assertion `", 11}, 
{"((reloc->r_info) & 0x) ="..., 35}, {"' failed!\n", 10}], 10) = 153
28364 exit_group(127)   = ?
28377 +++ exited with 127 +++
28376 +++ exited with 127 +++
... etc.

But I could start it in safe mode. I disabled all add-ons and it was
still the same behaviour. I upgraded to experimental version and that
didn't help either.

So I looked around in the strace log and saw that the last opened
libraries are libdrm.so.2, libdrm_radeon.so.1 and some plugins of that
packages. This reminded me on a little change that I applied a couple
of months ago, see
http://askubuntu.com/questions/491750/force-enable-hardware-acceleration-in-firefox

And indeed, unsetting MOZ_USE_OMTC makes iceweasel happy again.

Regards,
Eduard.

-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled

Name: Add to Search Bar
Location: ${PROFILE_EXTENSIONS}/add-to-search...@maltekraus.de.xpi
Status: user-disabled

Name: Default theme
Location: 
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled

Name: Deutsch (DE) Language Pack locale
Location: 
/usr/lib/iceweasel/browser/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-de
Status: user-disabled

Name: Deutsches Wörterbuch dictionary
Location: ${PROFILE_EXTENSIONS}/de...@dictionaries.addons.mozilla.org
Status: user-disabled

Name: DOM Inspector
Location: ${PROFILE_EXTENSIONS}/inspec...@mozilla.org
Status: user-disabled

Name: DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}
Status: user-disabled

Name: DownThemAll!
Location: ${PROFILE_EXTENSIONS}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}.xpi
Status: user-disabled

Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: user-disabled

Name: Flashblock
Location: ${PROFILE_EXTENSIONS}/{3d7eb24f-2740-49df-8937-200b1cc08f8a}
Status: user-disabled

Name: FoxyProxy Standard
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/foxypr...@eric.h.jung
Package: xul-ext-foxyproxy-standard
Status: user-disabled

Name: HTTPS-Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org
Status: user-disabled

Name: LittleFox theme
Location: ${PROFILE_EXTENSIONS}/{29852C08-1E91-4889-A6BF-C77F91D6A8F3}.xpi
Status: user-disabled

Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: enabled

Name: PDF Download
Location: ${PROFILE_EXTENSIONS}/{37E4D8EA-8BDA-4831-8EA1-89053939A250}
Status: user-disabled

Name: ScrapBook
Location: ${PROFILE_EXTENSIONS}/{53A03D43-5363-4669-8190-99061B2DEBA5}.xpi
Status: user-disabled

Name: Screengrab
Location: ${PROFILE_EXTENSIONS}/{02450954-cdd9-410f-b1da-db804e18c671}
Status: app-disabled

Name: Sitzungs-Manager
Location: ${PROFILE_EXTENSIONS}/{1280606b-2510-4fe0-97ef-9b5a22eafe30}.xpi
Status: enabled

Name: Tab To Window
Location: ${PROFILE_EXTENSIONS}/tabtowin...@sogame.cat
Status: user-disabled

Name: Tree Style Tab
Location: ${PROFILE_EXTENSIONS}/treestyle...@piro.sakura.ne.jp.xpi
Status: enabled

Name: United States English Spellchecker dictionary
Location: ${PROFILE_EXTENSIONS}/en...@dictionaries.addons.mozilla.org
Status: user-disabled

Name: UnPlug
Location: ${PROFILE_EXTENSIONS}/unp...@compunach.xpi
Status: user-disabled

-- Plugins information
Name: Shockwave Flash (11.2.202.425)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled

Name: VLC Web Plugin
Location: /usr/lib/mozilla/plugins/libvlcplugin.so
Package: browser-plugin-vlc
Status: enabled


-- Addons package information
ii  browser-plugin 2.0.6-4  amd64multimedia plugin for web browser
ii  iceweasel  34.0-1   amd64Web browser based on Firefox
ii  iceweasel-l10n 1:34.0-1 all  German language package for Icewe
ii  xul-ext-foxypr 3.4-1.1  all  advanced proxy management tool fo

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

Kernel: Linux 3.18.1+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
S

Bug#775014: nfs-common: Degraded performance on nfs4 clients after upgrade to Jessie

[Leopold Palomo-Avellaneda]

El Dissabte, 10 de gener de 2015, a les 19:30:12, Martin Steigerwald va 
escriure:
[...]

> 
> I suggest you upgrade to 3.16 bpo kernel. Maybe that already makes a
> difference. And additionally there is greater chance you get security
> updates on that one, cause AFAIK older bpo kernels are not maintained
> anymore.

It's in one of the main server of my institute and it's not easy. Anyway, I 
have programed it to do it soon. Thanks for the suggestion.

[...]

> > cami:/recursos /home/recursos nfs4
> > rw,sync,nodev,noatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,pro
> > t
> > o=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.8,local_lock
> > =n one,addr=192.168.1.254 0 0
> 
> What is this on the wheezy machine?

all the servers are wheezy. The clients are Jessie.

> Look in grep nfs /proc/mounts or nfsstat -m
> 
> I suggest not to manually tune this. Current kernels use good default
> values. I have seen rsize and wsize of up to 1048576.

> Additionally are they all the same hardware, same network cards? If not,
> what is the fast system using and what is the slow system using?


well, I have worked on this issue and i have found some conclusions:

- now, with modern kernels (and nfs4) it has no sense to set rsize and wsize. 
The negotiation between client and server do the best one. So, all the pages 
in the net are outdated.

- the sync parameter works totally different (client side) in a 3.2 kernel than 
3.16 (also 3.12 or 3.8) . I'm talking for a similar hardware (Gigabyte NIC, 
similar cpu, etc) but on a 100 Mb network) from ~7MB/s (kernel 3.2 vs 63,8 
kB/s >3.8). In another environment with a Giga network the rates are ( ~145 
kB/s vs ~70,3 MB/s)

- no significant differences in with wsize. At least that I had found. But the 
default autonegotiation works very well.

- I still don't understand why, although I have a good hardware in the work, 
when my clients do:
 
$ dd if=/dev/zero of=myrandom bs=4096 count=7

obtains about ~70MB/s

and if I execute the same in the server I obtain 167 MB/s. About 2.5 time 
slower

I still consider this issue important, I think that a lot of people that 
upgrade to Jessie with nfs mounts will found some problem. but this is just 
MHO.

Leopold

-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


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

Bug#774819: unblock: neutron/2014.1.3-10

[Thomas Goirand]

On 01/10/2015 01:06 PM, Ivo De Decker wrote:
> Hi Thomas,
> 
> On Thu, Jan 08, 2015 at 12:17:47AM +0100, Thomas Goirand wrote:
>> Yet another patch that needs to enter Jessie.
> 
> Closing this bug, as this upload has been superseded by yet another upload.
> 
> Could you please make sure that the next unblock request(s) for your packages
> contain the remaining changes you want to get into jessie and that they are
> tested before you file an unblock request? Also, once packages are unblocked,
> it's preferable to let them migrate to jessie before uploading additional
> changes. This avoids the need to review the same changes again.  Obviously
> this only applies if the unblocked version doesn't introduce new issues in
> jessie.
> 
> If the number of uploads for these packages doesn't go down, it's unclear if
> these packages are suitable for a stable release.
> 
> Cheers,
> 
> Ivo

Hi Ivo,

Yes, I am sorry that I had to do some new uploads. I have found another
issue with openstack-pkg-tools and systemd. In fact, it's James Page
from Canonical who did (Canonical is also adopting openstack-pkg-tools
for their packaging of OpenStack): if using systemd, daemons were not
automatically started on the first install because dh_installinit was
called before dh_systemd_enable in the rules file. As a consequence, I
did another round of uploads. Then I have found some inconsistencies in
the whole OpenStack suite (like the /configure_db flag having
different values and some more...), which I have fixed. There's also
some more bugs which were filled in the BTS which I fixed.

As you wrote above, I do prefer to run a new battery of test before
asking for unblocks. This will take a bit of time, and I will let you
know soon when I'm done.

I'm sorry if this is a bit late in the release process, and also to have
wasted some of your time, but I really hope to improve quality of the
packages here (while keeping changes as minimal as possible).

Cheers,

Thomas Goirand (zigo)


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#757733: RTS2557 SD card reader does not work

[Johannes Schauer]

Hi,

On Mon, 11 Aug 2014 06:45:24 +  wrote:
> Would you please try this patch. If it does work, we will submit it to 
> upstream kernel.

I own a Lenovo Thinkpad T440s as well just as the original bug submitter
(Philipp) and that patch by Wei does not fix the problem for me (I applied it
to a 3.18 tree).

What does work is to follow Philipp's instructions to patch the out-of-tree
driver from realtek.com.tw. That module then gives me my SD card as /dev/sdbX.

Weirdly, my SD card reader used to work (but presented the SD card as
/dev/mmcblk0pX). I do not know why it stopped working though as I didn't reboot
my laptop for several months. Running an older kernel version (3.14 for
example) does not fix the problem. Maybe it is related to other parts of my
(Debian testing) OS. I'll see if I can find a Debian unstable snapshot that
restores the behaviour I observed last year and try to bisect to find the
source of the regression.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#775016: ITP: hovercraft -- impress.js presentations by reStructuredText

[Daniel Stender]

Thanks for appreciation. I'll prepare the initial package and RFS in
the next days, then.

Greetings,
Daniel Stender

On 10.01.2015 21:36, Torsten Landschoff wrote:
> Hi Daniel,
> 
> Am 2015-01-10 03:54, schrieb Daniel Stender:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Daniel Stender 
>>
>> * Package name: hovercraft
>>   Version : 2.0b1
>>   Upstream Author : Lennart Regebro 
>> * URL : https://github.com/regebro/hovercraft
> 
> Wow! That looks like a tool that I was searching for. Thanks for posting
> it here and looking forward for the package :-)
> 
> Greetings, Torsten

-- 
http://qa.debian.org/developer.php?login=debian%40danielstender.com
4096R/DF5182C8
46CB1CA89EA3B74376761DB915E09AF4DF5182C8


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775069: installation-reports: Sucessful install Jessie-DI-rc1-amd64-netinst

[Andy Simpkins]

Package: installation-reports
Severity: normal
Tags: d-i

Dear Maintainer,

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

   * What led up to the situation?
install test
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
installed from USB stick onto bare PC 
   * What was the outcome of this action?
Sucess
   * What outcome did you expect instead?
Sucess 
*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: usb stick
Image version: 
cdimage.debian.org/cdimage/.jessie_di_rc1/amd64/iso-cd/debian-Jessie-DI-rc1-amd64-netinst.iso
Date: 

Machine: scan 3XS - i7 4790 cpu | asus Z97-P mobo | 16GB RAM | XFC R9-280X GPU 
(twin DP displays)
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o ]
Detect network card:[o ]
Configure network:  [o ]
Detect CD:  [ ]
Load installer modules: [o ]
Clock/timezone setup:   [o ]
User/password setup:[o ]
Detect hard drives: [o ]
Partition hard drives:  [o ]
Install base system:[o ]
Install tasks:  [o ]
Install boot loader:[o ]
Overall install:[o ]

Comments/Problems:

It is Debian - It Just works (tm)

Minor wobble at detect hw stage - DI reported that firmware for NIC was missing 
(rtl_nic/rtl8168g-2.fw) but after ignooring the error everything just worked
perhaps if the NIC is working you shouldn't report an error message (first time 
installers may just give up at that point)

I Like the fact I can now select the X desktop environment(s) I want to install 
from a list  about time too!  Well done :-)

Thank you.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150107"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux RattusTest 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 
(2014-12-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core 
Processor DRAM Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: Kernel driver in use: hsw_uncore
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset 
Family USB xHCI Controller [8086:8cb1]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 9 Series 
Chipset Family ME Interface #1 [8086:8cba]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset 
Family USB EHCI Controller #2 [8086:8cad]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset 
Family HD Audio Controller [8086:8ca0]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8615]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset 
Family PCI Express Root Port 1 [8086:8c90] (rev d0)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 9 Series Chipset 
Family PCI Express Root Port 3 [8086:8c94] (rev d0)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev d0)
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset 
Family USB EHCI Controller #1 [8086:8ca6]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 9 Series Chipset 
Family Z97 LPC Controller [8086:8cc4]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset 
Family SATA Controller [AHCI Mode] [8086:8c82]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family 
SMBus Contro

Bug#775050: FTCBFS for arm64: failure to determine stack direction

[peter green]

Note: not wearing any partciular hat in this message, opinions are my own.

Helmut Grohne wrote:

Package: src:libsigsegv
Version: 2.10-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libsigsegv FTCBFS for arm64. 

Can you confirm that FTCBFS stands for "fails to cross build from source"?


The configure script fails to determine the
stack direction. The general way of determining stack direction in
libsigsegv is to have a long list of cpu names to look up the stack
direction and only then fall back to doing a compile-run test. For
native builds this check makes the package work for arm64, but it cannot
be run while cross compiling.

I argue that since libsigsegv covers lots of other architectures, it
should also cover arm64 (consistency). Alternatively, one can argue that
cross builders should set sv_cv_stack_direction. If you believe that the
latter is the right way to go, please close this bug after tagging it
wont-fix.
  
I do not know enough about autotools cross-building to get involved in 
the argument over which approach is better.


However I would expect that either way the release team will consider 
this something that should be dealt with post-jessie.



I am attaching a patch that adds the cached value for arm64. From a
quick glance it seems or1k isn't covered either.

Helmut


  



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#771762: [DEPEND] Dependency failed for X11 Display Manager.

[Adrian Immanuel Kieß]

Dear Michael,

thank you for taking the time to process my bug report.

Just as sidenote, when I try to start GDM3 I also set gdm3 as the
default display manager. 

I also get 'Failed dependency: x-display-manager" messages (a lot) at
startup from systemd.

Now I am using xdm again. Kdm also works for me. Just GDM3 fails. But I
would like to use GDM3 again because the login with GDM3 also unlocks my
GNOME keyring.

With many greetings,

Adrian Immanuel KIEß


On Sat, 2015-01-10 at 14:25 +0100, Michael Biebl wrote: 
> Am 10.01.2015 um 11:49 schrieb Adrian Immanuel Kiess:
> > Package: gdm3
> > Version: 3.14.1-3
> > Followup-For: Bug #771762
> > 
> > Dear Maintainer,
> > 
> >* What led up to the situation?
> >  Trying to run GDM3 at startup or with service gdm3 restart
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> >  service kdm stop; dpkg-reconfigure gdm3; service gdm3 start
> >* What was the outcome of this action?
> >  GDM3 does not work in Debian/testing
> >* What outcome did you expect instead?
> >  Running and working GDM3
> > 
> > currently in Debian/testing GDM3 is broken for me.
> > 
> > It seems it tries to spawn a Xorg instance but fails with that.
> > 
> > I'll give the system logs below:
> > 
> > adrian@g6 (~) % systemctl status gdm3.service
> > ● gdm.service - GNOME Display Manager
> >Loaded: loaded (/lib/systemd/system/gdm.service; static)
> >   Drop-In: /run/systemd/generator/gdm3.service.d
> >└─50-gdm3-$x-display-manager.conf
> >Active: failed (Result: start-limit) since Sat 2015-01-10 11:38:47 CET; 
> > 6min
> > ago
> >   Process: 7364 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-
> > manager 2>/dev/null)" = "/usr/sbin/gdm3" ] (code=exited, status=1/FAILURE)
> > 
> 
> I think we can consider that a systemd bug and how it implements the LSB
> $x-display-manager facility
> 
> Currently, this is a target, where every display manager can hook into
> via a insserv override snippet.
> 
> Whenever another service requests the start of $x-display-manager, all
> display managers hooked up into x-display-manager.target will be started.
> 
> Since gdm is not your default display-manager (but kdm), the
> ExecStartPre= check will fail and thus the unit as a whole will be
> marked as failed.
> 
> That's obviously not really the behaviour we want.
> 
> After careful consideration, I think it's better, to map
> $x-display-manager to display-manager.service, which will be a symlink
> to the default display manager.
> 
> With Didier's systemd-default-display-manager-generator, it should be
> guaranteed, that /etc/systemd/system/display-manager.service points to
> something sensible.
> 
> I'd propose something like the attached patch.
> 
> CCing the pkg-systemd-maintainers mailing list for input/review.
> 
> 
> 
> 
> 
> 

-- 
With greetings from Leipzig, Germany.
Adrian Immanuel Kieß 

Administrator & programmer
Unix / Perl / LaTeX

mail: 
www: http://www.kiess.at
www: http://www.totaleueberwachung.de


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

Bug#775068: emacs24: usage of quilt during build process is fragile

[David Bremner]

Source: emacs24
Version: 24.4+1-4.1
Severity: normal
Tags: patch


"quilt series" is not documented to prefix patch names with the
directory unless the environment variable QUILT_PATCHES_PREFIX is set.
I can't figure out exactly when it happens, but in particular it
doesn't happen in a wheezy sbuild chroot.


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From 8ee794b4688aacaaca593f70f19f8b07a208 Mon Sep 17 00:00:00 2001
From: David Bremner 
Date: Sat, 10 Jan 2015 23:23:46 +0100
Subject: [PATCH] d/rules: make use of "quilt series" less fragile

This use relies on the names of patches being prefixed with
debian/patches, which doesn't seem to be completely reliable (e.g. it
doesn't happen in a wheezy build environment).  The environment
variable QUILT_PATCHES_PREFIX is documented to do this.
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 208076f..c42064b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -18,7 +18,7 @@
 #export DH_VERBOSE=1
 
 SHELL := /bin/bash
-quilt := QUILT_PATCHES=debian/patches quilt
+quilt := QUILT_PATCHES=debian/patches QUILT_PATCHES_PREFIX=y quilt
 pf := set -o pipefail
 
 # This package uses debian/source/format 3.0 (quilt).
-- 
2.1.4

Bug#770286: Parcellite is supposed to keep the clipboard history

[Hugo Lefeuvre]

Hi Ricky,

I'll reassign the bug to KeepassX.
We'll see what we can do. :)

Thanks !

Cheers,
 Hugo

-- 
  Hugo Lefeuvre (hugo6390)|www.hugo6390.org
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: Digital signature

Bug#772546: syslinux-efi: syslinux.efi will not boot wheezy kernel via pxe

[Daniel Baumann]

close 772546
thanks

thanks, but since that this is documented in the upstream documentation,
i don't think a debian specific duplication of this is required.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775062: Acknowledgement (grok doesn't grok group name ('group name must start with a non-digit'))

[Gabriel Corona]

I bisected the issue and found it was fixed by this commit:

44ce9372a29319c01d4ac7f24287fb36315e0e34 is the first bad commit
commit 44ce9372a29319c01d4ac7f24287fb36315e0e34
Author: Guillaume Bour 
Date:   Thu Dec 11 14:07:21 2014 +0100

[fix] grok is not working anymore with PCRE >= 8.34 because the
latter does
not allow anymore a group name to start with digits (PCRE Changelog
version 8.34, point 36)

this commit fix the issue by prepending a '_' at the start of group
name.
It remains compatible with older versions of PCRE

Found with:

~~~sh
git bisect origin/master 11942705515393ef12a5ed438abff0fe7b3ca232
git run test.sh
~~~

with test.sh:

~~~sh
#!/bin/sh

main() {
  set -e

  export PREFIX=temp
  make clean
  make
  make install

  cd temp
  ./bin/grok -f /usr/share/doc/grok/examples/numberpredicate.grok
}

if main; then false ; else true ; fi
~~~

-- Gabriel


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775066: zeromq: New Upstream releases

[Josue Ortega]

Package: libzmq1
Version: 2.2.0+dfsg-6
Severity: wishlist
Tags: patch

Dear Maintainer,

I've found this package is 2 versions behind of the latesst upstream version.
Is there any reason to keep the version 2.2.0 in the archive?

Also I've found the watch file has the version 2 hardcoded. I am attaching a
patch to fix the watch file.


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

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

Versions of packages libzmq1 depends on:
ii  libc6  2.19-13
ii  libgcc11:4.9.2-10
ii  libpgm-5.1-0   5.1.118-1~dfsg-1
ii  libstdc++6 4.9.2-10
ii  libuuid1   2.25.2-4
ii  multiarch-support  2.19-13

libzmq1 recommends no packages.

libzmq1 suggests no packages.

-- no debconf information
Description: Updates zeromq watch file
Author: Josue Ortega 

--- debian/watch	2014-01-12 12:13:27.0 -0600
+++ debian/watch	2015-01-10 16:36:54.656981155 -0600
@@ -1,4 +1,4 @@
 version=3
 options=dversionmangle=s/\+dfsg// \
-http://download.zeromq.org/zeromq-(2.*)\.tar\.gz \
+http://download.zeromq.org/zeromq-(\d+.\d+.\d+)\.tar\.gz \
 debian sh debian/repack.stub

Bug#775067: systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC)

[Christian Seiler]

Package: systemd
Version: 215-8
Severity: grave
Tags: upstream patch
Justification: causes non-serious data loss

Dear Maintainer,

when using LXC containers without CAP_SYS_ADMIN, journald fails to
forward any messages to syslog by default. Since the journal is not
persistent by default, no logs are stored at all, hence the
classification as 'data loss'. Also, this is a regression from Wheezy,
where a container without CAP_SYS_ADMIN and syslog did indeed store
persistent logs in /var/log/{syslog,messages,...}.

Note that there is NO other problem with systemd related to missing
CAP_SYS_ADMIN in a container (that I have found so far), provided all
required (pseudo-) file systems are mounted beforehand (which can be
done by configuration with Jessie's LXC version). I do know that
upstream claims that CAP_SYS_ADMIN-less containers are currently not
really supported, but they do intend to work towards that, and, from
what I can tell, apart from this journald problem, I have found no
issue whatsoever with a missing CAP_SYS_ADMIN (it actually works even
better than under sysvinit because it doesn't try to do some stuff
it's not supposed to do in containers that cause error messages with
sysvinit) - and since these kinds of containers were working in
Wheezy with its default init, I think this should be supported in
Jessie, too, especially if the fix is really easy, see below.

This bug is independent of the syslog implementation used, because no
syslog implementation in Jessie supports reading directly from the
journal, as far as I can tell (syslog-ng is too old, rsyslog is built
without imjournal support), so all rely on ForwardToSyslog=yes.

The reason why this problem occurs is that journald tries to fake
SCM_CREDENTIALS before sending a packet to the syslog daemon. With
CAP_SETUID and CAP_SETGID, faking uid/gid is not a problem, but to fake
the pid in struct ucred, one needs CAP_SYS_ADMIN (according to current
kernel source).

Also note that without activating debugging in journald, this problem
can not be diagnosed easily (it took me a while with strace to find the
problem).

Note, however, two things:

 - journald does (and can) not guarantee that it can fake the pid,
   because the process could have already exited. If you look at the
   source, in case ESRCH is returned, it just fakes uid/gid and uses
   its own pid

 - both rsyslog and syslog-ng (haven't tried anything else yet) don't
   rely on SCM_CREDENTIAL's pid anyway in their default configuration,
   so at least in the default configuration there's no reason to fail
   in that case.

I have created (and tested) an absolutely trivial patch that fixes this
by not only checking for ESRCH but also EPERM and then avoid faking the
pid.

I have tested this with both rsyslog and syslog-ng and it works and
both store (the same ;-)) persistent log messages in
/var/log/{messages,syslog,...}.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (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
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-58
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-4
ii  libc6   2.19-13
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-4
ii  libgcrypt20 1.6.2-4+b1
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-8
ii  mount   2.25.2-4
ii  sysv-rc 2.88dsf-58
ii  udev215-8
ii  util-linux  2.25.2-4

Versions of packages systemd recommends:
ii  dbus1.8.12-3
ii  libpam-systemd  215-8

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information
Description: Make journald syslog fwd'ing work w/o CAP_SYS_ADMIN
 In case CAP_SYS_ADMIN is missing, one cannot fake pid in struct ucred
 (uid/gid are find if CAP_SETUID/CAP_SETGID are present), which is the
 case in some container setups.
 .
 This patch makes sure that journald will try again to forward the
 messages to syslog, without faking the SCM_CREDENTIALS pid this time
 (which isn't guaranteed anyway, since it also does the same thing if
 the process has already exited).
 .
 With this patch, journald will no longer silently discard messages
 that are supposed to be sent to syslog in these situations.
Author: Christian Seiler 
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: systemd-215/src/journal/journald-syslog.c
===
--- systemd-215.orig/src/journal/journald-syslog.c
+++ systemd-215/src/journal/journald-syslog.c
@@ -85,12 +85,12 @@ static void forward_syslog_iov

Bug#775065: dpkg --configure -a results in "Hangup" after first package

[Chris Carr]

Package: dpkg
Version: 1.17.23

Hi,

I have been away from Debian development for over a year due to some RL 
issues. I booted my Sid box and did apt-get update and then upgrade, and 
everything went wrong. Full story (badly told) is at


http://forums.debian.net/viewtopic.php?f=5&t=119834

The issue I have now is that whenever I try to use apt-get I am told 
 "dpkg was interrupted, you must manually run 'dpkg --configure -a' to 
correct the problem". Running this as root results in


Setting up cups-daemon (1.7.5-10) ...
Hangup

... without that package being configured, nor any others.

If this is not a bug in dpkg, please could someone tell me how to go 
about diagnosing and correcting it? I need to be able to finish 
installing and configuring the ~55 half-done packages so that I can get 
my system working again. At the moment it doesn't boot properly and 
drops me into emergency mode. I cannot run openssh-server or reportbug.


Thanks in advance for any help, and apologies for (mis)using the BTS in 
desperation. Google tells me that nobody else has reported this set of 
issues anywhere.


CC

Bug#775064: heimdall-flash: needs versioned build-dep for libusb-1.0-0-dev

[Andres Salomon]

Package: heimdall-flash
Version: 1.4.0-2
Tags: +patch


While building a heimdall-flash backport on wheezy, I hit the following
build error:

dh_auto_build -D heimdall
make[2]: Entering directory 
`/home/dilinger/Downloads/heimdall-flash-1.4.0/heimdall'
make  all-am
make[3]: Entering directory 
`/home/dilinger/Downloads/heimdall-flash-1.4.0/heimdall'
g++ -DHAVE_CONFIG_H -I.  -I/usr/include/libusb-1.0   -std=c++0x 
-I../libpit/Source -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o 
source/Arguments.o source/Arguments.cpp
g++ -DHAVE_CONFIG_H -I.  -I/usr/include/libusb-1.0   -std=c++0x 
-I../libpit/Source -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o 
source/BridgeManager.o source/BridgeManager.cpp
source/BridgeManager.cpp: In member function ‘bool 
Heimdall::BridgeManager::DetectDevice()’:
source/BridgeManager.cpp:503:36: error: ‘LIBUSB_LOG_LEVEL_NONE’ was not 
declared in this scope
source/BridgeManager.cpp:507:36: error: ‘LIBUSB_LOG_LEVEL_ERROR’ was not 
declared in this scope
source/BridgeManager.cpp:511:36: error: ‘LIBUSB_LOG_LEVEL_WARNING’ was not 
declared in this scope
source/BridgeManager.cpp:515:36: error: ‘LIBUSB_LOG_LEVEL_INFO’ was not 
declared in this scope
source/BridgeManager.cpp:519:36: error: ‘LIBUSB_LOG_LEVEL_DEBUG’ was not 
declared in this scope
source/BridgeManager.cpp: In member function ‘int 
Heimdall::BridgeManager::Initialise(bool)’:
source/BridgeManager.cpp:568:36: error: ‘LIBUSB_LOG_LEVEL_NONE’ was not 
declared in this scope
source/BridgeManager.cpp:572:36: error: ‘LIBUSB_LOG_LEVEL_ERROR’ was not 
declared in this scope
source/BridgeManager.cpp:576:36: error: ‘LIBUSB_LOG_LEVEL_WARNING’ was not 
declared in this scope
source/BridgeManager.cpp:580:36: error: ‘LIBUSB_LOG_LEVEL_INFO’ was not 
declared in this scope
source/BridgeManager.cpp:584:36: error: ‘LIBUSB_LOG_LEVEL_DEBUG’ was not 
declared in this scope
source/BridgeManager.cpp: In member function ‘void 
Heimdall::BridgeManager::SetUsbLogLevel(Heimdall::BridgeManager::UsbLogLevel)’:
source/BridgeManager.cpp:1354:37: error: ‘LIBUSB_LOG_LEVEL_NONE’ was not 
declared in this scope
source/BridgeManager.cpp:1358:37: error: ‘LIBUSB_LOG_LEVEL_ERROR’ was not 
declared in this scope
source/BridgeManager.cpp:1362:37: error: ‘LIBUSB_LOG_LEVEL_WARNING’ was not 
declared in this scope
source/BridgeManager.cpp:1366:37: error: ‘LIBUSB_LOG_LEVEL_INFO’ was not 
declared in this scope
source/BridgeManager.cpp:1370:37: error: ‘LIBUSB_LOG_LEVEL_DEBUG’ was not 
declared in this scope
make[3]: *** [source/BridgeManager.o] Error 1
make[3]: Leaving directory 
`/home/dilinger/Downloads/heimdall-flash-1.4.0/heimdall'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/home/dilinger/Downloads/heimdall-flash-1.4.0/heimdall'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory `/home/dilinger/Downloads/heimdall-flash-1.4.0'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1357:
dpkg-buildpackage -rfakeroot -D -us -uc -sa -v0.0 failed


It would appear that a build-dep against libusb-1.0-0-dev is not enough.  The
version of libusb-1.0-0-dev in wheezy is 2:1.0.11-1.  After upgrading to a
libusb backport (2:1.0.19-1~bpo70+1), the build succeeded.

The attached patch adds a versioned build-dep for libusb-1.0-0-dev.

--- heimdall-flash-1.4.0/debian/control.orig	2015-01-10 14:03:38.991753121 -0800
+++ heimdall-flash-1.4.0/debian/control	2015-01-10 14:03:35.559734583 -0800
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Steve Langasek 
 Build-Depends: debhelper (>= 9~),
-	libusb-1.0-0-dev,
+	libusb-1.0-0-dev (>> 2:1.0.19),
 	qt4-qmake,
 	libqt4-dev,
 	libz-dev,

Bug#775063: greylistd: fails to install, remove, distupgrade, and install again

[Andreas Beckmann]

Package: greylistd
Version: 0.8.8.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
(in 'wheezy'), remove (but not purge), distupgrade to 'jessie',
and install again.
Before the second installation the package is in config-files-remaining
state. The configuration is remaining from the last version that was
successfully configured - which is from the previous release.

Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.

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

  Selecting previously unselected package greylistd.
  Unpacking greylistd (from .../greylistd_0.8.8_all.deb) ...

  Setting up greylistd (0.8.8) ...
  Adding system user `greylist' (UID 100) ...
  Adding new group `greylist' (GID 150) ...
  Adding new user `greylist' (UID 100) with group `greylist' ...
  Not creating home directory `/var/lib/greylistd'.
  Creating directory /var/run/greylistd: Done.
  Copying /usr/share/doc/greylistd/examples/whitelist-hosts to /etc/greylistd:  
Done.
  invoke-rc.d: policy-rc.d denied execution of start.

  Removing greylistd ...
  invoke-rc.d: policy-rc.d denied execution of stop.

  Selecting previously unselected package greylistd.
  (Reading database ... 8369 files and directories currently installed.)
  Preparing to unpack .../greylistd_0.8.8.3_all.deb ...
  Unpacking greylistd (0.8.8.3) ...
  Setting up greylistd (0.8.8.3) ...
  insserv: script greylistd: service greylist already provided!
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package greylistd (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   greylistd

The fix should be rather simple: the preinst script actions but be
performed on both "install" and "upgrade" (install will get a second
argument if the conffiles from an old version were remaining):

[...]
case "$1" in
install|upgrade)
[...]


cheers,

Andreas


greylistd_0.8.8.3.log.gz
Description: application/gzip

Bug#775062: grok doesn't grok group name ('group name must start with a non-digit')

[Gabriel Corona]

Package: grok
Version: 1.20110708.1-4
Severity: grave
Justification: renders package unusable

Dear maintainer,

I tried to use the grok examples packaged with grok:

$ grok -f /usr/share/doc/grok/examples/number-predicate2.grok 
Failure compiling pattern '%{NUMBER > 20}': group name must start with a 
non-digit

All groke examples fail with this "group name must start with a
non-digit" error.

I recompiled grok from source (g...@github.com:jordansissel/grok.git)
and the problem does not appear:

$ ./bin/grok -f /usr/share/doc/grok/examples/number-predicate2.grok 
Got number: 33

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

Kernel: Linux 3.16.0-4-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 grok depends on:
ii  libc6 2.19-13
ii  libevent-2.0-52.0.21-stable-2
ii  libpcre3  2:8.35-3.3
ii  libtokyocabinet9  1.4.48-3

grok recommends no packages.

grok suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775060: Package: installation-reports

[Steve McIntyre]

On Sat, Jan 10, 2015 at 10:22:10PM +0100, Michael Kesper wrote:
>Package: installation-reports
>
>Boot method: usb stick (unetbootin media)
>Image version: 
>http://cdimage.debian.org/cdimage/jessie_di_beta_2/amd64/iso-cd/debian-jessie-DI-b2-amd64-netinst.iso
>Date:2015-01-09
>
>Comments/Problems:
>
>Unable to activate rescue mode.
>Adding boot parameter rescue/enable=true and/or manually loading the
>rescue udeb didn't change anything, only normal installation was
>shown.

Please try again without using unetbootin - it's known to break things.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775061: ITP: wmcalc -- dockable calculator application

[Doug Torrance]

Package: wnpp
Severity: wishlist
Owner: Doug Torrance 

* Package name: wmcalc
  Version : 0.5
  Upstream Author : Window Maker Developers Team 

* URL : http://windowmaker.org/dockapps/?name=wmcalc
* License : GPL-2
  Programming Lang: C
  Description : dockable calculator application

Wmcalc is a small calculator meant for the WindowMaker dock or
Afterstep Wharf. It is a simple calculator with basic functions and
memory slots, and can launch any external application for more
complex calculations.

wmcalc was removed from Debian in 2010 [1], but is now maintained again and a
new upstream version was just released.

[1] https://packages.qa.debian.org/w/wmcalc/news/20100124T163923Z.html


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775060: Package: installation-reports

[Michael Kesper]

Package: installation-reports

Boot method: usb stick (unetbootin media)
Image version: 
http://cdimage.debian.org/cdimage/jessie_di_beta_2/amd64/iso-cd/debian-jessie-DI-b2-amd64-netinst.iso

Date:2015-01-09

Comments/Problems:

Unable to activate rescue mode.
Adding boot parameter rescue/enable=true and/or manually loading the 
rescue udeb didn't change anything, only normal installation was shown.


Bye
Michael


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#768243: heimdal-clients: leaves alternatives after purge: rcp, rsh, telnet

[Andreas Beckmann]

Followup-For: Bug #768243

Hi,

here is a patch to clean up the obsolete alternatives on upgrades from
wheezy. It's based on top of the unstable branch in git, but could be
separated easily from these pending changes.
I verified in piuparts that this works correctly.

Please get this fixed in jessie - it's the last package leaving obsolete
alternatives after upgrades from wheezy. RT has approved alternatives
fixup on two other packages today, so this shouln't be a problem, but I
do not know about the other changes pending in git ...


Andreas

PS: How do you build from the git packaging repository? Since the
patches seem to be applied, git-buildpackage (or plain pbuilder) explode
while preparing a source package.
>From 9edefd09fe77c80c8a323fe3b32fae8bc0772796 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Sat, 10 Jan 2015 18:56:49 +0100
Subject: [PATCH] cleanup obsolete telnet, rsh and pop alternatives

---
 debian/changelog|  5 +
 debian/heimdal-clients.postinst | 11 +++
 2 files changed, 16 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 9454892..1472e70 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,14 @@
 heimdal (1.6~rc2+dfsg-9) UNRELEASED; urgency=medium
 
+  [ Jelmer Vernooij ]
   * Add 051_bug746486-memleak: cherry-pick memory leak fix in KDC from
 upstream. Thanks GALAMBOS Daniel. Closes: #746486
   * Add Turkish debconf translation. Thanks Mert Dirik. Closes: #759877
 
+  [ Andreas Beckmann ]
+  * heimdal-clients.postinst: Cleanup obsolete telnet, rsh and pop
+alternatives.  (Closes: #768243)
+
  -- Jelmer Vernooij   Mon, 25 Aug 2014 13:52:44 +0200
 
 heimdal (1.6~rc2+dfsg-8) unstable; urgency=low
diff --git a/debian/heimdal-clients.postinst b/debian/heimdal-clients.postinst
index f688df7..66879e9 100644
--- a/debian/heimdal-clients.postinst
+++ b/debian/heimdal-clients.postinst
@@ -1,5 +1,16 @@
 #!/bin/sh -e
 
+if [ "$1" = "configure" ]
+then
+if dpkg --compare-versions "$2" lt-nl "1.6~rc2+dfsg-9~"
+then
+	for i in telnet rsh rcp
+	do
+	update-alternatives --remove $i /usr/bin/k$i
+	done
+fi
+fi
+
 for i in ftp pagsh
 do
 update-alternatives --install /usr/bin/$i $i /usr/bin/k$i 23 \
-- 
2.1.4

Bug#775010: libmaven-archiver-java: please allow pom.properties' date to be deterministic

[Emmanuel Bourg]

Le 10/01/2015 17:54, Chris West a écrit :

> I've updated the patch to replace the line.  This assumes
> that it is present; would be great if this kind of thing
> was specified.  It's hard to verify the assumption as the
> date comes out in locale format.

Thank you for the update. It's safe to assume the date always follow the
comment specified, the Javadoc for the store() method states:

"Next, a comment line is always written, consisting of an ASCII #
character, the current date and time (as if produced by the toString
method of Date for the current time), and a line separator as generated
by the Writer."

The call to Arrays.sort() isn't necessary but it doesn't hurt.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#756627: postfix-pgsql broken with libpq5 (9.4~beta2-1) now in jessie and sid

[Christoph Berg]

Control: forwarded -1 
http://www.postgresql.org/message-id/20150109233240.ga30...@msg.df7cb.de

Re: Matthew Dawson 2014-12-27 <2311925.tgZUXzRVSD@ring00>
> Hi all,
> 
> I recently was doing a test upgrade of my server and ran into this problem, 
> using a non-proxy configuration.  I investigated further, and found this only 
> occurs when cleanup's chroot is missing my host's regular /etc/passwd file.  
> Copying in the file allows postfix to continue past the cleanup process.
> 
> I quickly edited the file to only include the root user, and now trivial-
> rewrite is failing the same way.  I'll keep investigating, but it appears 
> libpq5 wants a valid passwd file for some reason.
> 
> I'm running on libpq5 9.4.0-1.
> 
> PS If I was to find the root cause of this, is a patch likely to land in 
> Jessie at this point?

Hi,

I've seen this postfix bug report only now that I've received
independent complaints about the problem via the PostgreSQL IRC.
I've forwarded the problem to the pgsql-hackers list and a fix is
being prepared that should hopefully appear in libpq5 9.4.1.

Thanks for the /etc/passwd hint, I was somewhat stuck in my own
debugging attempts, and this explained the problem pretty well.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775059: linux-image-3.2.0-4-amd64: kernel update broke suspend to ram - system crashes instead

[John Pinder]

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

Dear Maintainer,
*** 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 lines ***



-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.65-1

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=5ff7dd5a-2630-4c04-a406-2b6ec7dd8a91 ro quiet

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[6.389929] Bluetooth: Core ver 2.16
[6.389958] NET: Registered protocol family 31
[6.389962] Bluetooth: HCI device and connection manager initialized
[6.389967] Bluetooth: HCI socket layer initialized
[6.389970] Bluetooth: L2CAP socket layer initialized
[6.389982] Bluetooth: SCO socket layer initialized
[6.413597] asus_wmi: Backlight controlled by ACPI video driver
[6.433822] Bluetooth: Generic Bluetooth USB driver ver 0.6
[6.433887] usbcore: registered new interface driver btusb
[6.441280] Bluetooth: Atheros AR30xx firmware driver ver 1.0
[6.463767] iTCO_vendor_support: vendor-support=0
[6.464781] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[6.464938] iTCO_wdt: Found a Panther Point TCO device (Version=2, 
TCOBASE=0x0460)
[6.465168] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[6.476063] EFI Variables Facility v0.08 2004-May-17
[6.569785] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X
[6.569848] snd_hda_intel :00:1b.0: setting latency timer to 64
[6.594295] psmouse serio4: elantech: assuming hardware version 4 (with 
firmware version 0x361f01)
[6.630708] psmouse serio4: elantech: Synaptics capabilities query result 
0x00, 0x15, 0x0c.
[6.706074] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio4/input/input6
[6.825207] Linux media interface: v0.10
[6.852041] Linux video capture interface: v2.00
[6.882632] usb 1-1.1: firmware: agent loaded ar3k/AthrBT_0x1102.dfu 
into memory
[6.921559] ath9k :02:00.0: setting latency timer to 64
[6.931970] ath: EEPROM regdomain: 0x60
[6.931974] ath: EEPROM indicates we should expect a direct regpair map
[6.931979] ath: Country alpha2 being used: 00
[6.931982] ath: Regpair used: 0x60
[6.947840] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[6.948642] Registered led device: ath9k-phy0
[6.948655] ieee80211 phy0: Atheros AR9462 Rev:2 mem=0xc9000aa0, 
irq=17
[6.956031] uvcvideo: Found UVC 1.00 device USB Camera (0bda:570c)
[6.961928] input: USB Camera as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input7
[6.962124] usbcore: registered new interface driver uvcvideo
[6.962129] USB Video Class driver (1.1.1)
[6.970879] usb 1-1.1: firmware: agent loaded ar3k/ramps_0x1102_40.dfu 
into memory
[6.974393] usbcore: registered new interface driver ath3k
[7.211737] usb 1-1.1: USB disconnect, device number 3
[7.411486] usb 1-1.1: new full-speed USB device number 5 using ehci_hcd
[7.446416] cfg80211: World regulatory domain updated:
[7.446422] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[7.446429] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 
2000 mBm)
[7.446435] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm)
[7.446440] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 
2000 mBm)
[7.446445] cfg80211: (517 KHz - 525 KHz @ 16 KHz), (N/A, 
2000 mBm)
[7.446450] cfg80211: (525 KHz - 533 KHz @ 16 KHz), (N/A, 
2000 mBm)
[7.446455] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 
2000 mBm)
[7.446460] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 
2000 mBm)
[7.446466] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 
0 mBm)
[7.504957] usb 1-1.1: string descriptor 0 read error: -22
[7.505074] usb 1-1.1: New USB device found, idVendor=13d3, idProduct=3393
[7.505079] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[8.273230] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
[8.273448] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input8
[8.273744] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[8.274672] checking generic (e000 30) vs hw (e000 1000)
[8.274678] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing 
generic driver
[8.274712] Console: switching to colour dummy device 80x25
[8.276716] i915 :00:02.0: setting latency timer to 64
[  

Bug#733459: game-data-packager: md5 checksum error packing hexen II data

[Andres Cimmarusti]

Thanks for your work. Here's the info you requested:

> cksum data1/pak0.pak (for the exact size)

2912412704 22704056 pak0.pak

> md5sum data1/pak0.pak

c9675191e75dd25a3b9ed81ee7e05eff  pak0.pak

> sha1sum data1/pak0.pak

7c6b19d76ce85771026ea8dbdc397cd1109355b7  pak0.pak

> sha256sum data1/pak0.pak

57936acc4cd9abed7acb480dd9c6d59c7c98e96e4eca4e2d04f390d2dfa5ffde  pak0.pak

> If you can say something about where you got your version of the data
> (e.g. gog.com; Steam; USA retail CD; EU retail CD; budget re-release from
> Sold Out; that sort of thing) that would also be useful information.

Mmm... unfortunately I don't have this info. I found the files in some
obscure website and it's been so long I can't remember it!

> Please repeat for any other necessary data files (e.g. the expansions),
> and say which expansion needs which file(s).

There's a pak1 file in the same directory. I think it's part of the
main game as well but I can't be sure:

$ cksum pak1.pak
4210700438 75601170 pak1.pak

$ md5sum pak1.pak
c2ac5b0640773eed9ebe1cda2eca2ad0  pak1.pak

$ sha1sum pak1.pak
34c17f508bb6cd9ae4401307d0930a6f00761826  pak1.pak

$ sha256sum pak1.pak
6940cc03dc731f9c19f4e8a21259d7f191bd60a7487b50ceed3f8268e0d32a56  pak1.pak

There's now pak3 which is part of the Portal of Praevus expansion

$ cksum pak3.pak
1873146513 49089114 pak3.pak

$ md5sum pak3.pak
77ae298dd0dcd16ab12f4a68067ff2c3  pak3.pak

$ sha1sum pak3.pak
84aaba667060e1f9c50fb4d140fb301ac7e81cb7  pak3.pak

$ sha256sum pak3.pak
f5f53e360d49af9d7f8bd3b136a0ebab70e9ddcace13cf8aa5e182d986a0a48c  pak3.pak

I also have pak4.pak, but I can't remember its origins. It's in a
folder I called 'hw'. It may be some unreleased mission pack. I will
not include it here.

I hope this helps and thanks for your work

Andres


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775016: ITP: hovercraft -- impress.js presentations by reStructuredText

[Torsten Landschoff]

Hi Daniel,

Am 2015-01-10 03:54, schrieb Daniel Stender:

Package: wnpp
Severity: wishlist
Owner: Daniel Stender 

* Package name: hovercraft
  Version : 2.0b1
  Upstream Author : Lennart Regebro 
* URL : https://github.com/regebro/hovercraft


Wow! That looks like a tool that I was searching for. Thanks for posting 
it here and looking forward for the package :-)


Greetings, Torsten


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#772611: horae: build-depend on libpod-latex-perl to fix FTBFS

[Carlo Segre]

Hi Logan:

It will be fixed in the next release

On Tue, 9 Dec 2014, Logan Rosen wrote:


Package: horae
Version: 071~svn537-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch

Dear Maintainer,

horae currently FTBFS on amd64 (and presumably i386 as well) due to a 
missing build dependency on libpod-latex-perl.


Here is the relevant extract from the build log:

# Generate man pages for artemis only cd lib/Ifeffit/lib/artemis.doc ; 
./make_doc --man Can't locate Pod/LaTeX.pm in @INC (you may need to 
install the Pod::LaTeX module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.20.1 /usr/local/share/perl/5.20.1 
/usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 
/usr/local/lib/site_perl .) at ./make_doc line 93. BEGIN 
failed--compilation aborted at ./make_doc line 93. debian/rules:29: 
recipe for target 'build-stamp' failed


In Ubuntu, the attached patch was applied to achieve the following:

 * Build-depend on libpod-latex-perl to fix FTBFS.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: jessie/sid
 APT prefers vivid-updates
 APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-25-generic (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



--
Carlo U. Segre -- Duchossois Leadership Professor of Physics
Director, Center for Synchrotron Radiation Research and Instrumentation
Illinois Institute of Technology
Voice: 312.567.3498Fax: 312.567.3494
se...@iit.edu   http://phys.iit.edu/~segre   se...@debian.org


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#731709: Updated EFI patch

[jnqnfe]

In regards to the point in the binary build stage sequence at which your
new code executes the efi script, and the below quoted comment besides
it, I'm curious about what exactly you are worried about that prompted it?

"After includes/hooks because it copies in efi.img files that can be
overriden by binary_includes and modified by binary_hooks"

Do you have examples of existing hooks/includes which actually clash
with the new files? Or are you simply worried about a user adding an
include/hook which overwrites/deletes a file and thus breaks their image?

If the latter, then I really don't agree that it's an issue. The
includes and hooks scripts are there to allow last minute customisations
before compiling the image, and if a user foolishly misuses them to
break their image, then that's on them.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775058: isc-dhcp-server: server does not start after upgrade from wheezy to jessie

[Toni Mueller]

Package: isc-dhcp-server
Version: 4.3.1-5
Severity: important

Dear Maintainer,

I have cross-upgraded a machine from Wheezy/i386 to Jessie/amd64 by
re-installing, then copying the configuration back. One result is that
my DHCP server does no longer start. The init script says "[ ok ]",
but ps shows that there is no dhcp server.

# /etc/init.d/isc-dhcp-server start
[ ok ] Starting isc-dhcp-server (via systemctl): isc-dhcp-server.service.
# 

However, if I start the DHCP server by hand, like

# dhcpd -d

it actually starts, although in the foreground.


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

Kernel: Linux 3.16.0-4-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 isc-dhcp-server depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  debianutils4.4+b1
ii  isc-dhcp-common4.3.1-5
ii  libc6  2.19-13
ii  libdns-export100   1:9.9.5.dfsg-8
ii  libirs-export911:9.9.5.dfsg-8
ii  libisc-export951:9.9.5.dfsg-8
ii  lsb-base   4.1+Debian13+nmu1

isc-dhcp-server recommends no packages.

Versions of packages isc-dhcp-server suggests:
pn  isc-dhcp-server-ldap  

-- Configuration Files:
/etc/dhcp/dhcpd.conf changed [not included]

-- debconf information:
  isc-dhcp-server/interfaces:
-- 

I have set the interface in /etc/defaults/isc-dhcp-server to be 'br0'.



Kind regards,
--Toni++


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#773992: RFS: xmlrpc-c/1.33.15+svn20141223~2672-1 [ITA]

[Paul Gevers]

On 10-01-15 20:59, Paul Gevers wrote:
>>> I think you don't need to add the version to the dpkg-gensymbols call,
>>> and if you do, why strip the Debian part of the version? Doesn't
>>> dh_makeshlibs call dpkg-gensymbols itself? So if you try to override
>>> anything, shouldn't the dpkg-gensymbols calls be BEFORE the
>>> dh_makeshlibs call? This doesn't look right to me. Have you seen
>>> https://wiki.debian.org/UsingSymbolsFiles where it describes a way to
>>> create a symbols file that contains as much history as possible?
>>>
>>
>> If the symbols file contains versions with the Debian revision lintian
>> displays a error[1].
>>
>> No dpkg-gensymbols must run manually. Without the separate call no
>> symbol files found. With I can found the diffs in the buildlog.
>>
>> And yes dpgk-gensymbols must be running befor dh_makeshlibs. Changed.
> 
> I will do some testing and come back to this. This is not my experience
> with libraries and symbols files.

I disabled the calls to dpkg-gensymbols in your d/rules file and I
manually removed the symbols for 1.39.2 for libxmlrpc-c++8 that you
already added and I find that the symbols files are created. Indeed,
lintian complains, but that is fixed by generating the symbols files
before the build such that you can also build on it later. Yes, you can
then strip them with -v (as you have them now in the package). Really,
no need for the override of dh_makeshlibs AFAICT. The reason why I
wouldn't want to have this in the rules is the risk of being forgetting
to update the symbols file the next time it needs to be updated. In the
end that would lead to to strict requirements on the version.

Oh, and by the way, your get-orig-source target is broken. If I run it
now, the $DATE string does not match the date in the changelog.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#775057: [libfreetype6] New Upstream available 2.5.5

[A.H.]

Package: libfreetype6
Version: 2.5.2-2
Severity: minor

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

Hello,

as there is a new upstream available it would be great if updating would 
be possible.

See http://www.freetype.org/

yours

Andreas Hausmann


--- System information. ---
Architecture: amd64
Kernel: Linux 3.17-2.towo-siduction-amd64

Debian Release: 8.0
500 unstable http.debian.net
500 unstable ftp.uni-stuttgart.de
500 unstable cdn.debian.net
500 trusty ppa.launchpad.net
100 wheezy-backports ftp.debian.org
1 experimental cdn.debian.net

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

Package's Recommends field is empty.

Package's Suggests field is empty.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775056: python3-llfuse: package unusable due to non-existent module dependency 'Queue'

[Daniel Danner]

Package: python3-llfuse
Version: 0.37.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

apparently, the package wants to import the 'Queue' python module, which
seems to have been renamed to 'queue' in python3.

Attempting to use the llfuse module fails like this:

$ python3 -c 'import llfuse'
Traceback (most recent call last):
File "", line 1, in 
File "llfuse.pyx", line 76, in init llfuse (src/llfuse.c:24898)
ImportError: No module named Queue


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python3-llfuse depends on:
ii  libc6 2.13-38+deb7u6
ii  libfuse2  2.9.0-2+deb7u1
ii  python3   3.2.3-6

python3-llfuse recommends no packages.

Versions of packages python3-llfuse suggests:
pn  python-llfuse-doc  

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#759530: CPU info?

[Helmut Grohne]

On Thu, Jan 01, 2015 at 10:09:58PM +0100, Yves-Alexis Perez wrote:
> I'm not experiencing that bug, but maybe it'd help if the submitters
> would provide their /proc/cpuinfo and maybe try to get a clue about
> where the segfault happens (maybe with coredumps)?

/proc/cpuinfo from Bernd Zeimetz (he was reporting segfaults as well):

processor   : 3
vendor_id   : GenuineIntel
cpu family  : 6
model   : 42
model name  : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
stepping: 7
microcode   : 0x29
cpu MHz : 813.769
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 2
apicid  : 3
initial apicid  : 3
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc aperfmperf 
eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr 
pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm 
ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips: 4983.78
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

Helmut


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775055: win32-loader: Support new versions of Windows

[jnqnfe]

Package: win32-loader
Version: 0.7.7
Severity: important

Running win32-loader on an up-to-date Windows 8.1 install results in a
not supported dialog. Creating this bug report as a reminder that
support for newer editions of Windows is needed.

Exact dialog message:
"This program doesn't support Windows 6.2.9200 SP0 yet"


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#773992: RFS: xmlrpc-c/1.33.15+svn20141223~2672-1 [ITA]

[Paul Gevers]

Hello Jörg,

On 07-01-15 13:12, Jörg Frings-Fürst wrote:
> Am Montag, den 05.01.2015, 21:55 +0100 schrieb Paul Gevers:
>> On 30-12-14 21:17, Jörg Frings-Fürst wrote:
>>> Am Montag, den 29.12.2014, 11:13 +0100 schrieb Paul Gevers:
 On 26-12-14 20:48, Jörg Frings-Fürst wrote:
>> Sure, saw that. I guess you want to follow the stable release tree?
> 
> Yes. And eventually the Advanced release in Experimental.

Ack.

>   * New missing debian/xmlrpc-c-config.man and debian/xmlrpc.man.

 You created these files with help2man. I prefer it when you do this at
 build time, so that the man page stays up-to-date. I think you can tweak
 the settings of help2man to not add the date and your name.

>>> Yes the manfiles was basically made with help2man, but also massive
>>> edited. Therefore I don't build them at build time.
>>
>> Then I really suggest you remove the first line of the man page file.
>> Did you send this manpage upstream then? Ideally you should be able to
>> drop this file again once upstream excepts it. Also I suggest to either
>> drop the statement about "may be used by others" or improve the wording
>> such that you actually really mention a common license name that applies
>> to your work on this man page.
>>
> 
> Are this ok?
> 
> "This manual page was written by Jörg Frings-Fürst for the Debian
> project and is licensed under BSD-3." 

It is ok for me. Maybe a nicer statement (less ambiguous in the sense
that the project has the full license), "is licensed under the same
license as xmlrpc-c."

 Just wondering (haven't check yet), but you only add symbols files for
 amd64 and i386. Is this working correctly with the other archs? Or are
 they going to be more strict as a result?

>>> My error. I have differences between amd64 and i386. So I have renamed
>>> the symbols file for libxmlrpc-c++8 to *.amd86 and *.i386.
>>>
>>> I have renamed libxmlrpc-c++8.symbols.amd64 to libxmlrpc-c++8.symbols.
>>
>> Wouldn't it be possible to merge the symbols files so that the common
>> part can still be used (haven't checked the content of the files myself
>> yet).
>>
> No, the symbols file are different between i386 and the other archs.

Ok.

>> I think you don't need to add the version to the dpkg-gensymbols call,
>> and if you do, why strip the Debian part of the version? Doesn't
>> dh_makeshlibs call dpkg-gensymbols itself? So if you try to override
>> anything, shouldn't the dpkg-gensymbols calls be BEFORE the
>> dh_makeshlibs call? This doesn't look right to me. Have you seen
>> https://wiki.debian.org/UsingSymbolsFiles where it describes a way to
>> create a symbols file that contains as much history as possible?
>>
> 
> If the symbols file contains versions with the Debian revision lintian
> displays a error[1].
> 
> No dpkg-gensymbols must run manually. Without the separate call no
> symbol files found. With I can found the diffs in the buildlog.
> 
> And yes dpgk-gensymbols must be running befor dh_makeshlibs. Changed.

I will do some testing and come back to this. This is not my experience
with libraries and symbols files.

 Please separate your commits to git to ease review and understanding.
>>>
>>> ok
>>
>> Thanks for doing this a bit. However, your commit dbfaa7a7cc is horrible
>> to review though, because you mix upstream changes due to the new
>> release with your changes. I recommend to have the new upstream release
>> in a clean commit and then add your changes nicely documented afterwards.
>>
> If you want I can make a "git reset" and push the changes separately. 

Please don't rewrite history in published git repositories, it is
considered (for good reasons) bad practice). I'll figure it out, but
just keep it in mind for next times (and other projects ;) ).

>> It looks like you are mixing ideas in your d/rules file. You export
>> DEB_BUILD_MAINT_OPTIONS = hardening=+all, but at the same time you
>> declare all the *FLAGS manually (which you shouldn't). Also you don't
>> use or export the *FLAGS. I think you should check the last section of
>> dpkg-buildflags(1). (I could be wrong here). I think it would make
>> 500-mk_gennnmtab.patch unnecessary.
> 
> First I think hardening all is requested for xmlrpc-c.
> 
> Only with "export DEB_BUILD_MAINT_OPTIONS = hardening=+all"
> 
> a get a FTBFS:
> 
> /usr/bin/ld: AbyssServer.osh: relocation R_X86_64_PC32 against symbol 
> `_ZN8xmlrpc_c11AbyssServer10ReqHandler9terminateEv' can not be used when 
> making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Bad value
> collect2: error: ld returned 1 exit status

I reproduce this behavior.

> With 
> 
> [C|CPP|CXX]FLAGS += -fPIC
> 
> the build runs, but I get by testing with blhc
> 
> CPPFLAGS missing (-D_FORTIFY_SOURCE=2): [..]
> 
> Then with 
> 
> [C|CPP|CXX]FLAGS += -fPIC -D_FORTIFY_SOURCE=2
> 
> blhc display on errors.

But still I don't understand it. Shouldn't the flags be exported to be
used, so why does this work. Also I think DEB_

Bug#775054: libmagickcore-6.q16-dev: MagickCore-config not in $PATH

[Mike Linksvayer]

Package: libmagickcore-6.q16-dev
Version: 8:6.8.9.9-3
Severity: minor

Dear Maintainer,

   * What led up to the situation?

I ran

  opam install imagemagick

to install the OCaml library for imagemagick. It failed to build.
I looked at the source http://www.linux-
nantes.org/~fmonnier/OCaml/ImageMagick/downloads/OCaml-ImageMagick-0.34.tgz and
found the makefile uses

  # path to the MagickCore-config utility
  MAGICK_INSTALLED_BIN := $(shell which MagickCore-config)

which fails because MagickCore-config is not in my path.

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

I found MagickCore-config in /usr/lib/i386-linux-gnu/ImageMagick-6.8.9/bin-Q16
and added that to my path.

   * What was the outcome of this action?

`opam install imagemagick` succeeded after I added above to my path.

   * What outcome did you expect instead?

I expected `opam install imagemagick` to succeed without tinkering.

Note https://packages.debian.org/search?suite=jessie&searchon=contents&keywords
=magickcore-config shows MagickCore-config is in /usr/bin for [ia64, sparc,
s390] so presumably this bug would not occur on those architectures.



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

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

Versions of packages libmagickcore-6.q16-dev depends on:
ii  libbz2-dev 1.0.6-7+b2
ii  libdjvulibre-dev   3.5.25.4-4+b1
ii  libexif-dev0.6.21-2
ii  libfreetype6-dev   2.5.2-2
ii  libgraphviz-dev2.38.0-7
ii  libjasper-dev  1.900.1-debian1-2.3
ii  libjpeg-dev1:1.3.1-11
ii  libjpeg62-turbo-dev [libjpeg-dev]  1:1.3.1-11
ii  liblcms2-dev   2.6-3+b3
ii  liblqr-1-0-dev 0.4.2-2
ii  libltdl-dev2.4.2-1.11
ii  libmagickcore-6-headers8:6.8.9.9-3
ii  libmagickcore-6.q16-2  8:6.8.9.9-3
ii  libmagickcore-6.q16-2-extra8:6.8.9.9-3
ii  libopenexr-dev 1.6.1-8
ii  libpng12-dev [libpng-dev]  1.2.50-2+b2
ii  librsvg2-dev   2.40.5-1
ii  libtiff5-dev [libtiff-dev] 4.0.3-12
ii  libwmf-dev 0.2.8.4-10.3+b2
ii  libx11-dev 2:1.6.2-3
ii  libxext-dev2:1.3.3-1
ii  libxml2-dev2.9.1+dfsg1-4
ii  libxt-dev  1:1.1.4-1+b1
ii  pkg-config 0.28-1
ii  zlib1g-dev 1:1.2.8.dfsg-2+b1

libmagickcore-6.q16-dev recommends no packages.

libmagickcore-6.q16-dev suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775053: debbugs: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/debbugs/examples/config

[Andreas Beckmann]

Package: debbugs
Version: 2.4.1
Severity: serious
Tags: wheezy-ignore squeeze-ignore
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package debbugs.
  (Reading database ... 9350 files and directories currently installed.)
  Preparing to unpack .../archives/debbugs_2.4.1_all.deb ...
  Unpacking debbugs (2.4.1) ...
  Setting up debbugs (2.4.1) ...
  cp: cannot stat '/usr/share/doc/debbugs/examples/config': No such file or 
directory
  No such file or directory at /usr/sbin/debbugsconfig line 75.
  dpkg: error processing package debbugs (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   debbugs


Cheers,

Andreas


debbugs_2.4.1.log.gz
Description: application/gzip

Bug#775052: qmail-run: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/qmail-run/examples/aliases

[Andreas Beckmann]

Package: qmail-run
Version: 2.0.2
Severity: serious
Tags: wheezy-ignore
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

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

  Selecting previously unselected package qmail-run.
  (Reading database ... 7981 files and directories currently installed.)
  Preparing to unpack .../qmail-run_2.0.2_all.deb ...
  Unpacking qmail-run (2.0.2) ...
  Setting up qmail-run (2.0.2) ...
  creating default /etc/aliases...
  cp: cannot stat '/usr/share/doc/qmail-run/examples/aliases': No such file or 
directory
  dpkg: error processing package qmail-run (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   qmail-run


Cheers,

Andreas


qmail-run_2.0.2.log.gz
Description: application/gzip

Bug#767028: ovirt-guest-agent: fails to install

[Holger Levsen]

Hi László,

On Freitag, 9. Januar 2015, László Böszörményi (GCS) wrote:
>  Digging deep into this, it seems the problem lies in an other thing.
> Do you have /proc mounted in your piuparts test environment?

since 0.17 piuparts mounts proc inside the tested chroot... :-)

so I *suspect* this something else, cc:ing the piuparts lists for further 
input or investigation.

(I wont have much time to look into this for at least the next 4 days probably 
rather 2 weeks...)

> This seems to be an udevadm 'bug' instead, it can't handle unreachable
> /proc/cmdline . Is there any policy that a package should install
> while /proc is unavailable?

packages may be in non working state, but I'd argue that installation itself 
must still not fail...


cheers,
Holger


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

Bug#766749: Fixed upstream, patch included

[Mike Gabriel]

Control: severity -1 serious

Hi Nachanon,

On  Sa 10 Jan 2015 07:41:43 CET, Nachanon Vetjasit wrote:


Control: tags -1 + upstream
Control: tags -1 + patch
Control: tags -1 + fixed-upstream

Hello everyone,

This bug also applies to Debian/wheezy-backports version,
but only if compositing window manager was not enabled.

The bug is now fixed upstream, see upstream bug report for details.
Upstream bug: 

Attached file is the upstream patch, originally tested against
1.8.0+dfsg1-2~bpo70+1 (Debian/wheezy-backports).
Patch URL: 

As the patch was merged verbatim on the upstream master

and Fedora MATE maintainer confirmed that it works with git checkout,
it should work on Debian/testing and Debian/unstable version too.

Cheers,
Nachanon Vetjasit


P.S. Current users can use this patch to fix the already-installed
mate-power-manager without rebuilding the package as well.

# cd /usr/share/mate-power-manager
# patch -p2 < /path/to/1003_fix-backlight-popup-gtkbuilder.patch

(Replace "/path/to/" with an actual folder that the patch resides in)
And logout then re-login to see the result.

This is method also tested against installed 1.8.0+dfsg1-2~bpo70+1
(Debian/wheezy-backports) too.


I will see to this at the beginning of the coming week. Let's hope  
that the release team agrees on my severity raisal (from the usability  
point of view, I really don't want this bug in a Debian stable release).


Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpcOM8lJB7e1.pgp
Description: Digitale PGP-Signatur

Bug#775051: cifs-utils: mount.cifs seems not to like passwords including # -char(s)

[Ulrich Schmidt]

Package: cifs-utils
Version: 2:6.4-1
Severity: normal
Tags: newcomer

/etc/fstab includes:
//192.168.12.201/vol1   /home/xx/vol1   cifs
uid=1000,umask=000,credentials=/usr/local/etc/whisper.credentials00



/usr/local/etc/whisper.credentials includes:
username=xx
domain=XXX
password=mypass#


trying a "mount /home/xx/vol1" i get this error:
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Now i removed the "password=mypass#"-line from
/usr/local/etc/whisper.credentials and the mount command asks me interactive
for a valid password. I enter my working password and i get an error too.

This setup worked 24 hours ago on a pc installed 2 days ago. Now i did a fresh
install and maybe i pulled newer version?
I am able to connect my remote drive in KDE and i am able tho copy files in KDE
but i am unable to use the mount command.
So at least i know my password is correct.



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

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

Versions of packages cifs-utils depends on:
ii  libc6 2.19-13
ii  libcap-ng00.7.4-2
ii  libkeyutils1  1.5.9-5+b1
ii  libkrb5-3 1.12.1+dfsg-16
ii  libtalloc22.1.1-2
ii  libwbclient0  2:4.1.13+dfsg-2
ii  samba-common  2:4.1.13+dfsg-2

Versions of packages cifs-utils recommends:
ii  keyutils  1.5.9-5+b1
ii  winbind   2:4.1.13+dfsg-2

Versions of packages cifs-utils suggests:
ii  smbclient  2:4.1.13+dfsg-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#746543: nmu: pinba-engine-mysql-5.5_1.0.0-4 (was: Re: pinba-engine-mysql-5.5: uninstallable: depends on obsolete version of mysql-5.5)

[Andreas Beckmann]

reassign 746543 release.debian.org
retitle 746543 nmu: pinba-engine-mysql-5.5_1.0.0-4
user release.debian@packages.debian.org
usertag 746543 binnmu
severity 746543 normal
thanks

On Thu, 1 May 2014 09:11:45 +0200 Ivo De Decker  wrote:
> The upload of mysql-5.5 5.5.37-1 makes pinba-engine-mysql-5.5 uninstallable in
> sid, as it depends on an older version. Either a new upload or a binnmu is
> necessary.

and now we have mysql-5.5 5.5.40-1 in sid ... so finally do a binNMU (testbuild 
succeeded on amd64)

nmu pinba-engine-mysql-5.5_1.0.0-4 . ALL . -m "Rebuild against mysql-5.5 5.5.40"

Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775050: FTCBFS for arm64: failure to determine stack direction

[Helmut Grohne]

Package: src:libsigsegv
Version: 2.10-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libsigsegv FTCBFS for arm64. The configure script fails to determine the
stack direction. The general way of determining stack direction in
libsigsegv is to have a long list of cpu names to look up the stack
direction and only then fall back to doing a compile-run test. For
native builds this check makes the package work for arm64, but it cannot
be run while cross compiling.

I argue that since libsigsegv covers lots of other architectures, it
should also cover arm64 (consistency). Alternatively, one can argue that
cross builders should set sv_cv_stack_direction. If you believe that the
latter is the right way to go, please close this bug after tagging it
wont-fix.

I am attaching a patch that adds the cached value for arm64. From a
quick glance it seems or1k isn't covered either.

Helmut


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774269: gnome-media: gstreamer-properties fails to starts; claims missing UI file

[Chris]

Package: gnome-media
Version: 3.4.0-2
Followup-For: Bug #774269

The problem is due to invalid "has_separator" properties on GtkDialogs in the
ui file, rather than missing UI file.

Upstream is supposedly uninterested in this part of gnome-media, but that's no
reason not to forward the bug, though.

I'm not aware of any other way to choose the default outputs/inputs - other
than editing the configuration manually with gconf-editor or similar, which is
cumbersome and requires undocumented knowledge.  Therefore, I'm providing an
(entirely trivial) patch for Debian.

With the patch applied, gstreamer-properties works as far as I'm able to test
(sound output selection/test, video output selection/test).



-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel

Kernel: Linux 3.16.0-4-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 gnome-media depends on:
ii  gconf-service3.2.6-3
ii  gstreamer0.10-gconf  0.10.31-3+nmu4+b1
ii  gstreamer0.10-plugins-base   0.10.36-2
ii  gstreamer0.10-plugins-good   0.10.31-3+nmu4+b1
ii  libc62.19-13
ii  libgconf-2-4 3.2.6-3
ii  libglib2.0-0 2.42.1-1
ii  libgstreamer-plugins-base0.10-0  0.10.36-2
ii  libgstreamer0.10-0   0.10.36-1.5
ii  libgtk-3-0   3.14.5-1
ii  x11-utils7.7+2

Versions of packages gnome-media recommends:
ii  gnome-control-center  1:3.14.2-2
ii  gstreamer0.10-pulseaudio  0.10.31-3+nmu4+b1
pn  pulseaudio

gnome-media suggests no packages.
--- gnome-media-3.4.0.debian-orig/gstreamer-properties/gstreamer-properties.ui	2012-03-28 05:50:00.0 -0500
+++ gnome-media-3.4.0/gstreamer-properties/gstreamer-properties.ui	2015-01-10 11:30:36.440106536 -0600
@@ -9,7 +9,6 @@
 False
 center
 dialog
-False
 
   
 True
@@ -880,7 +879,6 @@
 False
 True
 dialog
-False
 
   
 True

Bug#775014: nfs-common: Degraded performance on nfs4 clients after upgrade to Jessie

[Martin Steigerwald]

I am no debian kernel maintainer, but as I have seen this, some suggestions to 
try:

Am Samstag, 10. Januar 2015, 01:59:50 schrieb Leopold Palomo-Avellaneda:
> Package: nfs-common
> Version: 1:1.2.8-9
> Severity: important
> 
> I have a typical environment with a nfs server and some clients with home
> there, or shared resources. In the server I have a Wheezy (in one server
> with 3.12-0.bpo.1-amd64 version and in other 3.2.63). My clients basically
> are Wheezy but I'm preparing to Jessie and I wanted to test the upgrade.

I suggest you upgrade to 3.16 bpo kernel. Maybe that already makes a 
difference. And additionally there is greater chance you get security updates 
on that one, cause AFAIK older bpo kernels are not maintained anymore.

> I have realized that in the two cases that I have tested (at home and work)
> both, with the same parameters (fstab) that worked "normal" with Wheezy,
> now, they have an horrible performance in write operations. I'm having
> differences of several order of magnitude (37,9 KB/s Jessie vs 17,4 MB/s)
> 
> For instance:
> Wheezy machine:
> $ dd if=/dev/zero of=myrandom bs=1024 count=1000
[…]
> 1024000 octets (1,0 MB) copiats, 0,0590127 s, 17,4 MB/s
> 
> Jessie machine
> $ dd if=/dev/zero of=myrandom bs=1024 count=1000
[…]
> 1024000 octets (1,0 MB) copiats, 27,0021 s, 37,9 kB/s
> 
> I hope that the kernel developers have changed some default parameter and I
> have it wrong. But, with this version of the kernel, my nfs clients cannot
> work well.
> 
> I'm open to make any test or provide any needed information.
> 
> -- Package-specific info:
[…]
> -- /etc/fstab --
> #nfs4
> cami:/recursos   /home/recursos   
> nfs4  
auto,rw,nodev,sync,_netdev,retry=10,rsize=65536,wsize=65536,soft,noat
> ime,intr   0 0 -- /proc/mounts --
> cami:/recursos /home/recursos nfs4
> rw,sync,nodev,noatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,prot
> o=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.8,local_lock=n
> one,addr=192.168.1.254 0 0

What is this on the wheezy machine?

Look in grep nfs /proc/mounts or nfsstat -m

I suggest not to manually tune this. Current kernels use good default values. 
I have seen rsize and wsize of up to 1048576.

Additionally are they all the same hardware, same network cards? If not, what 
is the fast system using and what is the slow system using?

> -- System Information:
> Debian Release: 8.0
>   APT prefers testing
>   APT policy: (500, 'testing'), (1, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
[…]
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775048: hash-slinger: openpgpkey fails with TypeError

[cloos]

Package: hash-slinger
Version: 2.6-1
Severity: important

:; openpgpkey --create --output generic cl...@jhcloos.com
Traceback (most recent call last):
  File "/usr/bin/openpgpkey", line 190, in 
  ekey = gpgdisk.export_keys(pgpkey["keyid"],minimal=True, secret=False, 
armor=False)
  TypeError: export_keys() got an unexpected keyword argument 'minimal'


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

Kernel: Linux 3.12-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: sysvinit (via /sbin/init)

Versions of packages hash-slinger depends on:
ii  ca-certificates20141019
ii  dns-root-data  2014060201+2
ii  libpython2.7-stdlib [python-argparse]  2.7.9-1
ii  openssh-client 1:6.7p1-3
ii  python 2.7.8-2
ii  python-dnspython   1.12.0-1
ii  python-gnupg   0.3.6-1
ii  python-ipaddr  2.1.11-2
ii  python-m2crypto0.21.1-3
ii  python-unbound 1.4.22-3

hash-slinger recommends no packages.

hash-slinger suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775049: poppler-utils: "pdftohtml -s .pdf" produces multiple files.

[peter]

Package: poppler-utils
Version: 0.26.5-2
Severity: important
Tags: newcomer patch

Dear Maintainer,

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

   * What led up to the situation?
   pdftohtml was applied to a pdf file containing pixmap images.
   
   * What exactly did you do (or not do) that was effective (or ineffective)?
   The command was "pdftohtml -s .pdf".
   
   * What was the outcome of this action?
   All the text was in one .html but each picture was an additional file.
   
   * What outcome did you expect instead?
   With the -s option, text and pictures should all be in one .html.
   A JPEG or PNG picture can be included in an html document with Base64 
   encoding.  The syntax is very simple.  Examples here.
   http://easthope.ca/Category2.html
   Scroll down to the heading "Inline, Base64 encoded PNG bitmaps".
   The first instance of an embedded bitmap is 
   

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

Kernel: Linux 3.2.0-0.bpo.4-686-pae (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
Init: systemd (via /run/systemd/system)

Versions of packages poppler-utils depends on:
ii  libc6 2.19-13
ii  libcairo2 1.14.0-2.1
ii  libfreetype6  2.5.2-2
ii  libgcc1   1:4.9.1-19
ii  liblcms2-22.6-3+b3
ii  libpoppler46  0.26.5-2
ii  libstdc++64.9.1-19
ii  zlib1g1:1.2.8.dfsg-2+b1

poppler-utils recommends no packages.

poppler-utils suggests no packages.

-- no debconf information

-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202   http://carnot.yi.org/   Bcc: peter at easthope. ca


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#757298: Please add fallback boot entry for sysvinit when systemd is the active init

[Colin Watson]

On Sat, Jan 10, 2015 at 05:46:04PM +0100, I. Schrey wrote:
> So, before the 2.02~beta2-20 update "1>6" was
> 'Debian GNU/Linux, with Linux 3.12.0-svs-amd64'
> 
> After the update "1>6" would be
> 'Debian GNU/Linux, with Linux 3.14.0-svsi-amd64'
> because of the extra 'menuentry' lines, so I had to change the
> default entry to "1>9" to get the old behaviour back.
> 
> (that 3.14.0-svsi kernel package was missing some modules, so the
> system was unreachable after reboot. Now I guess you could say that was
> partly my fault for installing unsuitable kernels on a headless system,
> but still.. the new default boot took me by surprise)
> 
> 
> I guess if
> GRUB_DEFAULT="0" or
> GRUB_DEFAULT=""
> I wouldn't have noticed?

Oh, right, there's absolutely no guarantee that menu entry numbers won't
change.  This is exactly why the ability to set the default to a name
was introduced; you need to use that if you want predictable behaviour
across upgrades.

(In this case, of course, you'd need to use two names separated by ">"
to account for the submenu.)

-- 
Colin Watson   [cjwat...@debian.org]


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774939: unblock: grub2/2.02~beta2-20

[Colin Watson]

On Sat, Jan 10, 2015 at 01:19:47PM +, Colin Watson wrote:
> On Sat, Jan 10, 2015 at 01:22:56PM +0100, Ivo De Decker wrote:
> > On Fri, Jan 09, 2015 at 10:47:58AM +, Colin Watson wrote:
> > > Please unblock package grub2.  This mainly deals with implementing the
> > > discussions held with the Technical Committee on adding menu entries for
> > > alternative init daemons, which I strongly believe should be present in
> > > jessie in order to smooth migrations to systemd and make sure that
> > > sysadmins have a straightforward way out in case they're migrated
> > > accidentally.
> > 
> > Unblocked. But still needs the unblock-udeb.
> 
> Thanks.  Possibly we should wait with that until the recent follow-ups
> to #757298 are resolved.

Never mind; per my follow-up there, my interlocutor was relying on
unsupported behaviour.  No reason not to go ahead then AFAIK.

-- 
Colin Watson   [cjwat...@debian.org]


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775047: virtualbox-guest-source: provide a guest package for debian bsd

[Ritesh Raj Sarraf]

On 01/11/2015 05:00 AM, Ritesh Raj Sarraf wrote:
> Severity: wishlist
>
> VBox is supported on FreeBSD too. It would be nice if we provided guest 
> packages for the FreeBSD port. That'l allow more users to efficiently run 
> debian bsd on a vbox environment
The following webpages have details about bsd support.

https://wiki.freebsd.org/VirtualBox
https://www.freebsd.org/doc/handbook/virtualization-host-virtualbox.html
https://www.freebsd.org/doc/handbook/virtualization-guest.html

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."




signature.asc
Description: OpenPGP digital signature

Bug#775047: virtualbox-guest-source: provide a guest package for debian bsd

[Ritesh Raj Sarraf]

On 01/11/2015 05:00 AM, Ritesh Raj Sarraf wrote:
> Severity: wishlist
>
> VBox is supported on FreeBSD too. It would be nice if we provided guest 
> packages for the FreeBSD port. That'l allow more users to efficiently run 
> debian bsd on a vbox environment
The following webpages have details about bsd support.

https://wiki.freebsd.org/VirtualBox
https://www.freebsd.org/doc/handbook/virtualization-host-virtualbox.html
https://www.freebsd.org/doc/handbook/virtualization-guest.html

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."




signature.asc
Description: OpenPGP digital signature

Bug#775047: virtualbox-guest-source: provide a guest package for debian bsd

[Ritesh Raj Sarraf]

Package: virtualbox-guest-source
Severity: wishlist

VBox is supported on FreeBSD too. It would be nice if we provided guest 
packages for the FreeBSD port. That'l allow more users to efficiently run 
debian bsd on a vbox environment

-- System Information:
Debian Release: jessie/sid
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 10.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775046: [INTL:da] Danish translation of the debconf templates macchanger

[Joe Dalton]

Package: macchanger
Severity: wishlist
Tags: l10n patch

Please include the attached Danish macchanger translation.

joe@pc:~/over/debian/macchanger$ msgfmt --statistics -c -v -o /dev/null da.po
da.po: 2 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip

Bug#775045: firmware-atheros: ath9k_htc fails to connect

[Martti Ikonen]

Package: firmware-atheros
Version: 0.43
Severity: normal

Dear Maintainer,

   * What led up to the situation?
I installed Debian Jessie with XFCE4, replacing Wheezy, on my desktop computer
with a TP-LINK TL-WN721N wireless USB adapter.

$ lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
(M-BT58)
Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
To use the wifi connection, I installed the package firmware-atheros. After
that, my wifi network (SSID: wireless) was visible in Network Manager. I
clicked that and supplied my WPA2 protection key.

   * What was the outcome of this action?
   * What outcome did you expect instead?
Instead of establishing a connection, the NM visual indicator kept circling.
The top command indicated that systemd-journald was busy. The dmesg output ketp
repeating the following until I removed the USB adapter:

[  133.195538] [ cut here ]
[  133.195605] WARNING: CPU: 0 PID: 67 at /build/linux-
HsHI0x/linux-3.16.7-ckt2/drivers/usb/core/urb.c:450 usb_submit_urb+0x1bd/0x560
[usbcore]()
[  133.195610] usb 1-1: BOGUS urb xfer, pipe 1 != type 3
[  133.195614] Modules linked in: arc4 nfsd auth_rpcgss oid_registry nfs_acl
nfs lockd fscache sunrpc ath9k_htc ath9k_common ath9k_hw ath mac80211 cfg80211
rfkill nouveau iTCO_wdt iTCO_vendor_support ppdev mxm_wmi wmi video ttm
drm_kms_helper drm snd_intel8x0 evdev snd_ac97_codec i2c_algo_bit snd_wavefront
snd_cs4236 snd_opl3_lib snd_hwdep snd_wss_lib pcspkr snd_mpu401_uart serio_raw
lpc_ich mfd_core snd_pcm snd_rawmidi snd_timer snd_seq_device ns558 gameport
parport_pc shpchp rng_core ac97_bus snd soundcore i2c_i801 button parport
i2c_core processor thermal_sys fuse autofs4 ext4 crc16 mbcache jbd2 hid_generic
usbhid hid sg sd_mod crc_t10dif sr_mod cdrom crct10dif_generic crct10dif_common
ata_generic ata_piix uhci_hcd ehci_hcd libata usbcore usb_common scsi_mod 3c59x
e100 mii floppy
[  133.195725] CPU: 0 PID: 67 Comm: kworker/u2:2 Tainted: GW
3.16.0-4-686-pae #1 Debian 3.16.7-ckt2-1
[  133.195729] Hardware name: System Manufacturer System Name/P4B-MX  , BIOS
ASUS P4B-MX ACPI BIOS Revision 1003 01/28/2002
[  133.195745] Workqueue: phy0 ath9k_htc_ani_work [ath9k_htc]
[  133.195750]  f094eaf4 ef08ddd4 c14758d8 ef08dde4 c10569f4 f094eb64 ef08de00
0043
[  133.195762]  f094eaf4 01c2 f093c53d f093c53d 0009 ecd78100 0001
0003
[  133.195773]  ef08ddec c1056a43 0009 ef08dde4 f094eb64 ef08de00 ef08de34
f093c53d
[  133.195785] Call Trace:
[  133.195804]  [] ? dump_stack+0x3e/0x4e
[  133.195814]  [] ? warn_slowpath_common+0x84/0xa0
[  133.195848]  [] ? usb_submit_urb+0x1bd/0x560 [usbcore]
[  133.195872]  [] ? usb_submit_urb+0x1bd/0x560 [usbcore]
[  133.195880]  [] ? warn_slowpath_fmt+0x33/0x40
[  133.195910]  [] ? usb_submit_urb+0x1bd/0x560 [usbcore]
[  133.195937]  [] ? hif_usb_send+0xb9/0x310 [ath9k_htc]
[  133.195947]  [] ? htc_issue_send.constprop.2+0x59/0x70 [ath9k_htc]
[  133.195956]  [] ? htc_send_epid+0x1d/0x30 [ath9k_htc]
[  133.195967]  [] ? ath9k_wmi_cmd+0xdc/0x170 [ath9k_htc]
[  133.195977]  [] ? ath9k_regread+0x41/0x60 [ath9k_htc]
[  133.195997]  [] ? ath9k_hw_ani_monitor+0x5b/0x1e0 [ath9k_hw]
[  133.196083]  [] ? ath9k_htc_ani_work+0x157/0x180 [ath9k_htc]
[  133.196094]  [] ? process_one_work+0x115/0x380
[  133.196104]  [] ? pwq_activate_delayed_work+0x2d/0x70
[  133.196111]  [] ? worker_thread+0xf3/0x470
[  133.196120]  [] ? __wake_up_locked+0x1f/0x30
[  133.196127]  [] ? create_and_start_worker+0x50/0x50
[  133.196136]  [] ? kthread+0x9b/0xb0
[  133.196147]  [] ? ret_from_kernel_thread+0x21/0x30
[  133.196155]  [] ? kthread_create_on_node+0x110/0x110
[  133.196161] ---[ end trace ceb14f2cbdd1623a ]---
[  133.198902] systemd-journald[135]: /dev/kmsg buffer overrun, some messages
lost.
[  133.300158] [ cut here ]
[  133.300251] WARNING: CPU: 0 PID: 67 at /build/linux-
HsHI0x/linux-3.16.7-ckt2/drivers/usb/core/urb.c:450 usb_submit_urb+0x1bd/0x560
[usbcore]()
[  133.300260] usb 1-1: BOGUS urb xfer, pipe 1 != type 3
[  133.300264] Modules linked in: arc4 nfsd auth_rpcgss oid_registry nfs_acl
nfs lockd fscache sunrpc ath9k_htc ath9k_common ath9k_hw ath mac80211 cfg80211
rfkill nouveau iTCO_wdt iTCO_vendor_support ppdev mxm_wmi wmi video ttm
drm_kms_helper drm snd_intel8x0 evdev snd_ac97_codec i2c_algo_bit snd_wavefront
snd_cs4236 snd_opl3_lib snd_hwdep snd_wss_lib pcspkr snd_mpu401_uart serio_raw
lpc_ich mfd_core snd_pcm snd_rawmidi snd_timer snd_seq_device ns558 gameport
parport_pc shpchp rng_core ac97_bus snd soundcore i2c_i801 button parport
i2c_core processor thermal_sys fuse autofs4 ext4 crc16 mbcache jbd2 hid_generic
usbhid hid sg sd_mod crc_t10dif sr_mod cdrom crct10dif_generic crct10dif_common
ata_ge

Bug#775044: openjdk-7: FTBFS: java.lang.RuntimeException: time is more than 10 years from present: 1104530400000

[Daniel Schepler]

Source: openjdk-7
Version: 7u71-2.5.3-2
Severity: serious

>From my pbuilder build log (on amd64):

...
rm -f 
/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/lib/currency.data
/tmp/buildd/openjdk-7-7u71-2.5.3/build/bootstrap/jdk1.6.0/bin/java 
-XX:-PrintVMOptions -XX:+UnlockDiagnosticVMOptions -XX:-LogVMOutput -Xmx512m 
-Xms512m -XX:PermSize=32m -XX:MaxPermSize=160m -jar 
/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/btjars/generatecurrencydata.jar
 -o 
/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/lib/currency.data.temp
 \
< ../../../src/share/classes/java/util/CurrencyData.properties
Error: time is more than 10 years from present: 110453040
java.lang.RuntimeException: time is more than 10 years from present: 
110453040
   at 
build.tools.generatecurrencydata.GenerateCurrencyData.makeSpecialCaseEntry(GenerateCurrencyData.java:285)
   at 
build.tools.generatecurrencydata.GenerateCurrencyData.buildMainAndSpecialCaseTables(GenerateCurrencyData.java:225)
   at 
build.tools.generatecurrencydata.GenerateCurrencyData.main(GenerateCurrencyData.java:154)
Makefile:345: recipe for target 
'/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/lib/currency.data' 
failed
make[6]: *** 
[/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk.build-boot/lib/currency.data] 
Error 1
make[6]: Leaving directory 
'/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot/jdk/make/java/java'
Makefile:63: recipe for target 'all' failed
make[5]: *** [all] Error 1
make[5]: Leaving directory 
'/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot/jdk/make/java'
Makefile:253: recipe for target 'all' failed
make[4]: *** [all] Error 1
make[4]: Leaving directory 
'/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot/jdk/make'
make/jdk-rules.gmk:92: recipe for target 'jdk-build' failed
make[3]: *** [jdk-build] Error 2
make[3]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot'
Makefile:251: recipe for target 'build_product_image' failed
make[2]: *** [build_product_image] Error 2
make[2]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build/openjdk-boot'
Makefile:2301: recipe for target 'stamps/icedtea-boot.stamp' failed
make[1]: *** [stamps/icedtea-boot.stamp] Error 2
make[1]: Leaving directory '/tmp/buildd/openjdk-7-7u71-2.5.3/build'
debian/rules:1308: recipe for target 'stamps/build' failed
make: *** [stamps/build] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

(If I divide that number by 1000, it becomes Fri Dec 31 22:00:00 UTC 2004.
So I'm not sure where the number comes from, but it appears to be off by a
factor of 1000.)
-- 
Daniel Schepler


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775043: RSF: pyepr/0.8.2-1

[Antonio Valentino]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pyepr":

* Package name: pyepr
  Version : 0.8.2-1
  Upstream Author : Antonio Valentino 
* URL : http://avalentino.github.com/pyepr
* License : GPL-3.0+
  Section : python

It builds those binary packages:

python-epr - Python ENVISAT Product Reader API (Python 2)
python-epr-dbg - Python ENVISAT Product Reader API (debug extension for
Python 2)
python-epr-doc - Python ENVISAT Product Reader API (common documentation)
python3-epr - Python ENVISAT Product Reader API (Python 3)
python3-epr-dbg - Python ENVISAT Product Reader API (debug extension for
Python 3)

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

http://mentors.debian.net/package/pyepr


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

dget -x
http://mentors.debian.net/debian/pool/main/p/pyepr/pyepr_0.8.2-1.dsc

More information about pyepr can be obtained from
http://avalentino.github.io/pyepr.

Changes since the last upload:

  * New upstream release
  * debian/control
- added an explicit build dependency from dh-python
- Standard version bumped to 3.9.6 (no changes)
- fix Vcs-Browser URL
  * debian/patches
- updated 0001-Only-use-local-files-for-generating-sphinx-doc.patch:
  do not include links to the ohloh and travis-ci widgets


Regards

-- 
Antonio Valentino


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775042: RFS: epr-api/2.3~dev20140814b-1

[Antonio Valentino]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "epr-api":

* Package name: epr-api
  Version : 2.3~dev20140814b-1
  Upstream Author : Brockmann Consult 
* URL : http://github.com/bcdev/epr-api
* License : GPL-3.0+
  Section : libs

It builds those binary packages:

  libepr-api2 - ENVISAT Product Reader API for C
  libepr-api-dev - ENVISAT Product Reader API for C - Development files
  libepr-api2-dev - ENVISAT Product Reader API for C - Transitional package

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

http://mentors.debian.net/package/epr-api


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

dget -x
http://mentors.debian.net/debian/pool/main/e/epr-api/epr-api_2.3~dev20140814b-1.dsc

More information about epr-api can be obtained from
https://rawgit.com/bcdev/epr-api/master/docs/epr_c_api/index.html.

Changes since the last upload:

  * New upstream snapshot
  * Standard version bumped to 3.9.6 (no changes)
  * Compat have been set to 9
  * Removed all patches (applied upstream)
  * The -dev package has been renamed from libepr-api2-dev (that
is now a dummy package) into libepr-api-dev
  * Now the -dev package also provides a static version of the library
  * debian/control
- the -dev package is now architecture any
- the -dev package now Depends from libepr-api2 (= ${binary:Version})
  (Closes: #742332)
- fixed formatting of the package description
- use canonical URL for VCS fields
- added build dependency from cmake
- dropped build dependency from cdbs
  * debian/rules
- switch from cdbs to dh (debhelper command sequencer)
- fixed changelog installation (now dh_installchangelog is used)
  * debian/copyright
- use versioned copyright format uri
- updated dates in copyright statements
  * Added symbol file


Regards

-- 
Antonio Valentino


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#767822: xfce4-session: leaves alternatives after purge: /usr/bin/x-session-manager

[Andreas Beckmann]

Hi,

On 2014-11-02 22:47, Yves-Alexis Perez wrote:
> Thanks, I've pushed the changes to our svn.

I verified your svn changes in piuparts and asked the release team for
approval, which was granted: http://bugs.debian.org/774964

Please upload xfce-session with the changes currently in svn to sid - or
should I NMU?

Thanks

Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#775010: libmaven-archiver-java: please allow pom.properties' date to be deterministic

[Chris West]

Yeah, DEB_BUILD_DATE makes me less uneasy, too.

I've updated the patch to replace the line.  This assumes
that it is present; would be great if this kind of thing
was specified.  It's hard to verify the assumption as the
date comes out in locale format.

>From 4462124973f36a06d2e8695f789c4bc5beb8eaff Mon Sep 17 00:00:00 2001
From: "Chris West (Faux)" 
Date: Sat, 10 Jan 2015 16:48:22 +
Subject: [PATCH] honour DEB_BUILD_DATE when generating pom.properties (lines)

---
 .../apache/maven/archiver/PomPropertiesUtil.java   | 70 +-
 .../maven/archiver/PomPropertiesUtilTest.java  | 24 
 2 files changed, 93 insertions(+), 1 deletion(-)
 create mode 100644 src/test/java/org/apache/maven/archiver/PomPropertiesUtilTest.java

diff --git a/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java b/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java
index 5e0a41b..e294419 100644
--- a/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java
+++ b/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java
@@ -19,13 +19,21 @@ package org.apache.maven.archiver;
  * under the License.
  */
 
+import java.io.BufferedWriter;
 import java.io.File;
 import java.io.FileInputStream;
 import java.io.FileOutputStream;
 import java.io.IOException;
 import java.io.InputStream;
 import java.io.OutputStream;
+import java.io.OutputStreamWriter;
+import java.io.StringWriter;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.Arrays;
+import java.util.Date;
 import java.util.Properties;
+import java.util.regex.Pattern;
 
 import org.apache.maven.project.MavenProject;
 import org.codehaus.plexus.archiver.Archiver;
@@ -85,7 +93,7 @@ public class PomPropertiesUtil
 OutputStream os = new FileOutputStream( outputFile );
 try
 {
-properties.store( os, GENERATED_BY_MAVEN );
+storeWithCustomTimestamp( properties, os, GENERATED_BY_MAVEN );
 os.close(); // stream is flushed but not closed by Properties.store()
 os = null;
 }
@@ -95,6 +103,66 @@ public class PomPropertiesUtil
 }
 }
 
+private static Date findBuildDate() {
+final String envName = "DEB_BUILD_DATE";
+final String envVariable = System.getenv(envName);
+if (null == envVariable) {
+return null;
+}
+
+try {
+return new SimpleDateFormat("EEE, dd MMM  HH:mm:ss zzz").parse(envVariable);
+} catch (ParseException e) {
+throw new IllegalStateException("maven-archiver: " + envName + " not in recognised format", e);
+}
+}
+
+/**
+ * Replace the date in the file with the specified date, and sort the properties
+ *
+ * @param lines line 1: comment, line 2: date, line 3 onwards: properties
+ */
+static void mangle(String[] lines, Date buildDate) {
+lines[1] = "#" + buildDate.toString();
+Arrays.sort(lines, 2, lines.length);
+}
+
+private void storeWithCustomTimestamp(Properties properties, OutputStream os, String comment) throws IOException {
+final String[] lines = propertyFileLines(properties, comment);
+
+final Date buildDate = findBuildDate();
+if (null != buildDate) {
+mangle(lines, buildDate);
+}
+
+writeLines(os, lines);
+}
+
+private static String[] propertyFileLines(Properties properties, String comment) throws IOException {
+final StringWriter stringWriter = new StringWriter();
+try {
+properties.store(stringWriter, comment);
+} finally {
+stringWriter.close();
+}
+
+return stringWriter.toString()
+.split(Pattern.quote(System.getProperty("line.separator")));
+}
+
+private static void writeLines(OutputStream os, String[] lines) throws IOException {
+final BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(os, "ISO-8859-1"));
+try {
+for (String line : lines) {
+writer.write(line);
+writer.newLine();
+}
+} finally {
+writer.flush();
+writer.close();
+}
+}
+
 /**
  * Creates the pom.properties file.
  */
diff --git a/src/test/java/org/apache/maven/archiver/PomPropertiesUtilTest.java b/src/test/java/org/apache/maven/archiver/PomPropertiesUtilTest.java
new file mode 100644
index 000..b051b2d
--- /dev/null
+++ b/src/test/java/org/apache/maven/archiver/PomPropertiesUtilTest.java
@@ -0,0 +1,24 @@
+package org.apache.maven.archiver;
+
+import junit.framework.TestCase;
+
+import java.util.Arrays;
+import java.util.Date;
+
+import static org.apache.maven.archiver.PomPropertiesUtil.mangle;
+
+public class PomPropertiesUtilTest extends TestCase {
+
+public void testMangle() {
+final Date date = new Date(1);
+final String[] input = {"#foo bar", "#" + new Dat

Bug#775023: Please close bug

[Wolfgang Schnitker]

Dear Maintainer,

I just did a housecleaning in my box. Must be a USB misconnect due to dust.

dmesg now looks like this:

[0.697141] usbcore: registered new interface driver usbfs
[0.697171] usbcore: registered new interface driver hub
[0.700570] usbcore: registered new device driver usb
[0.712075] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[0.712078] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[0.712081] usb usb1: Product: EHCI Host Controller
[0.712083] usb usb1: Manufacturer: Linux 3.2.0-4-amd64 ehci_hcd
[0.712085] usb usb1: SerialNumber: :00:02.1
[0.770031] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[0.770035] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[0.770038] usb usb2: Product: OHCI Host Controller
[0.770040] usb usb2: Manufacturer: Linux 3.2.0-4-amd64 ohci_hcd
[0.770042] usb usb2: SerialNumber: :00:02.0
[1.248027] usb 1-5: new high-speed USB device number 4 using ehci_hcd
[2.183171] usb 1-5: New USB device found, idVendor=0bda, idProduct=0151
[2.183175] usb 1-5: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[2.183178] usb 1-5: Product: USB2.0-CRW
[2.183180] usb 1-5: Manufacturer: Generic
[2.183182] usb 1-5: SerialNumber: 2006041309210
[2.488031] usb 2-2: new full-speed USB device number 2 using ohci_hcd
[2.712053] usb 2-2: New USB device found, idVendor=03f0, idProduct=2d11
[2.712057] usb 2-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[2.712060] usb 2-2: Product: OfficeJet 6100 Series
[2.712067] usb 2-2: Manufacturer: Hewlett-Packard
[2.712070] usb 2-2: SerialNumber: MY47SJ33W22R
[3.016029] usb 2-3: new full-speed USB device number 3 using ohci_hcd
[3.238035] usb 2-3: New USB device found, idVendor=046d, idProduct=c52b
[3.238040] usb 2-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[3.238042] usb 2-3: Product: USB Receiver
[3.238044] usb 2-3: Manufacturer: Logitech
[5.922659] scsi4 : usb-storage 1-5:1.0
[5.922964] usbcore: registered new interface driver usb-storage
[5.999197] usbcore: registered new interface driver usbhid
[5.999204] usbhid: USB HID core driver
[6.056297] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0:
USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:02.0-3/input2
[6.062952] input: Logitech Unifying Device. Wireless PID:1024 as
/devices/pci:00/:00:02.0/usb2/2-3/2-3:1.2/0003:046D:C52B.0003/input/input4
[6.068846] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB
HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1024] on
usb-:00:02.0-3:1
[6.070745] input: Logitech Unifying Device. Wireless PID:2011 as
/devices/pci:00/:00:02.0/usb2/2-3/2-3:1.2/0003:046D:C52B.0003/input/input5
[6.071028] logitech-djdevice 0003:046D:C52B.0005: input,hidraw2: USB
HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:2011] on
usb-:00:02.0-3:2



Thank You!


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org