Bug#772423: O: haskell-doc -- Assorted Haskell language documentation

[Robert Bihlmeyer]

Hi,

please summarise or give a pointer to the discussion.

br,
-- 
Robert BihlmeyerASSISTArrow ECS Internet Security AG


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

Bug#784712: semi: incorrect keys in encryption

[Tatsuya Kinoshita]

Control: fixed - 1.14.7~0.20120428-17

Fixed in unstable.

Thanks,
--
Tatsuya Kinoshita


pgpJJ1eniHTAn.pgp
Description: PGP signature

Bug#756129: gem2deb: dh_ruby should allow extra parameters to extconf.rb

[Lucas Nussbaum]

On 26/07/14 at 17:56 +0200, Gilles Filippini wrote:
> Package: gem2deb
> Version: 0.7.5
> Severity: wishlist
> 
> Hi,
> 
> Sometimes the maintainer needs passing hints to extconf.rb, such as
> --with-=
> 
> I tried:
>   dh_auto_install -- --with-=
> dh_ruby --install -- --with-=
> dh_ruby --install --with-=
> without success, and looking at the dh_ruby.rb source code it seems
> there is no way to do that.
> 
> Then the only solution I found is to quilt patch extconf.rb to hard
> code the hints, which isn't satisfactory.
> 
> Thanks in advance,

Hi Gilles,

Could you provide an example package that needs this?

Lucas


signature.asc
Description: Digital signature

Bug#784687: xserver-xorg-core: xhost +si:localuser:foo does not grant access to foo anymore

[Dirk Griesbach]

tags 784687 patch upstream
thanks

Am Do, 07. Mai 2015 um 20:52:21 +0200 schrieb Dirk Griesbach:
> xhost does not grant access despite claiming otherwise since the upgrade
> to 1.17.1.

Answering to myself: This is a known regression and the patch can be
found at [1] which is also attached for reference.

Dirk

[1] 
http://cgit.freedesktop.org/xorg/xserver/commit/os/access.c?id=9d9bd38fe1454590c303dc936ddac913808bf881
>From 9d9bd38fe1454590c303dc936ddac913808bf881 Mon Sep 17 00:00:00 2001
From: Dave Airlie 
Date: Tue, 17 Feb 2015 14:40:27 +1000
Subject: os/access: fix regression in server interpreted auth

This was reported on irc on Fedora when rawhide went to 1.17.1.

regression occured in: 2566835b4374edb3e5a8353d4f7c9e7ec4851c57
 os: Eliminate uninitialized value warnings from access.c

siAddrMatch doesn't need addr to be a useful value, it checks
some things like localuser without having an address at all.

Signed-off-by: Dave Airlie 
Tested-by: Peter Hutterer 
Signed-off-by: Peter Hutterer 

diff --git a/os/access.c b/os/access.c
index 28f2d32..8fa028e 100644
--- a/os/access.c
+++ b/os/access.c
@@ -1392,7 +1392,7 @@ InvalidHost(register struct sockaddr *saddr, int len, ClientPtr client)
 }
 for (host = validhosts; host; host = host->next) {
 if (host->family == FamilyServerInterpreted) {
-if (addr && siAddrMatch(family, addr, len, host, client)) {
+if (siAddrMatch(family, addr, len, host, client)) {
 return 0;
 }
 }
-- 
cgit v0.10.2

Bug#638619: Misleading "gpg: Ohhhh jeeee: no decrypt() for 17" message from gpg when trying to decrypt a file without the public key being imported

[NIIBE Yutaka]

Hello,

This is reply to old bug report to GnuPG 1.4.  Sorry, it took so long
time to looking into detail.

I tried to reproduce the bug with recent implementations (GnuPG 1.4,
2.0, and 2.1), but I couldn't.  Since importing secret key
automatically creates corresponding public key, something strange had
happened, I think.  I also tried with old secret keyring and no public
key.  In this case, it simply failed like:

gpg: key 39E94F90: secret key without public key - skipped
gpg: encrypted with ELG-E key, ID 9541DC07
gpg: decryption failed: secret key not available

The message "Ohhh j" itself means some severe bug of GnuPG (and it
is not primarily to users), which should not occur.

Now, I'm going to implement better handling of this kind of error for
GnuPG 2.1; if something going badly, it should be detected earlier to
emit better message to user.  I mean, the point of this bug report is
taken.

Please let us know reproducible scenario if it still exists in current
gpg 1.4.  If it is not reproducible, I wonder if we can close this bug?

On Sat, 20 Aug 2011 11:21:01 +0200 Xavier Roche  wrote:
> Package: gpgv
> Version: 1.4.10-4
> Severity: minor
> 
> Note: this is a minor problem, but which can greatly increase your blood 
> pressure when reinstalling backuped files during a crash recovery :)
> 
> Attempting to decypher a gpg encrypted file with the private key imported 
> (gpg --import < my_private_key) but without the public key actually imported 
> leads to a misleading gpg error message suggesting that the encrypted file is 
> somehow invalid because it was encrypted using an unsuitable (signing) 
> algorithm:
> gpg: O j: no decrypt() for 17
> 
> Importing the public key solves this minor issue.
> 
> Maybe a message such as:
> gpg: O j: no decrypt() for 17: did you forget to import the public 
> key ?
> 
> Would be better.
[...]
> Versions of packages gpgv suggests:
> ii  gnupg 1.4.10-4   GNU privacy guard - a free PGP 
> rep
--


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

Bug#784727: tshark doesn't recognise BPF filter at the end of the line

[Olivier Mehani]

Package: tshark
Version: 1.12.1+g01b65bf-4
Severity: important
Tags: upstream

Dear Maintainer,

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

   * What led up to the situation?
Install latest tshark
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Run
tshark tcp
where 'tcp' is a BPF, as per tshark(1)
   * What was the outcome of this action?
tshark dumped the usage message and terminateb
   * What outcome did you expect instead?
The same as when running
tshark -f tcp

Note: this bugs seems to be a superset of #782245.

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


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

Kernel: Linux 3.14.33.jessiemptcp (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tshark depends on:
ii  libc6 2.19-18
ii  libglib2.0-0  2.42.1-1
ii  libpcap0.81.6.2-2
ii  libwireshark5 1.12.1+g01b65bf-4
ii  libwiretap4   1.12.1+g01b65bf-4
ii  libwsutil41.12.1+g01b65bf-4
ii  wireshark-common  1.12.1+g01b65bf-4
ii  zlib1g1:1.2.8.dfsg-2+b1

tshark recommends no packages.

tshark 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#774430: systemd: service makes as not reloadable

[Christian Kujau]

I'm experience the same, also with syslog-ng on a Debian/Jessie system 
(powerpc, upgraded from Debian/Wheezy not too long ago):

# dpkg-query --status syslog-ng-core systemd | egrep ^Package\|^Version
Package: syslog-ng-core
Version: 3.5.6-2+b1
Package: systemd
Version: 215-17

# systemctl -p CanReload show syslog-ng.service
CanReload=no

The /etc/logrotate.d/syslog-ng configuration asks to do "invoke-rc.d 
syslog-ng reload" which fails with the same error Tollef mentioned.

I've put up some more details on http://paste.debian.net/172990/

A different machine has been running Debian/unstable (amd64) for a while 
but was not upgraded to systemd automatically and never encountered this
bug here. After doing "apt-get install systemd systemd-sysv" and
rebooting, I could not reproduce this issue here.

Thanks,
Christian.


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

Bug#712938: Qt4 and sni-qt

[Tsu Jan]

On Thu, 07 May 2015 11:28:28 -0300 "Lisandro 
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer"  wrote:
> - sni-qt seems to be dead-upstream:
> ...
> Uploading dead-upstream stuff to the archive doesn't seems a wise idea to me, 
> so if anyone wants this in then jump in as sni-qt upstream. Or **much** 
better 
> yet, just help porting the code to Qt5.

sni-qt is only for Qt4 and needs a patch. As far as I know, no change will be 
needed with Qt5 >= 5.4 for the systray icons to work.

sni-qt  may be "dead-upstream" but Qt4 is so too and yet there are so many Qt4 
apps. As mentioned above, Enlightenment already needs sni-qt for Qt4 apps to 
show their systray icons.


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

Bug#784676: Please port to libmediaart-2.0

[Andreas Henriksson]

Hello Michael Biebl!

On Thu, May 07, 2015 at 07:56:34PM +0200, Michael Biebl wrote:
> Source: rygel
> Version: 0.24.2-1
> Severity: normal
> User: bi...@debian.org
> Usertags: oldlibs libmediaart-2.0
> 
> Hi,
> 
> your package declares a build-depends on libmediaart-1.0-dev and has a
> dependency on either libmediaart-1.0-0 or gir1.2-mediaart-1.0.
[...]

Thanks for your bug report. The new upstream release of rygel, 0.26,
requires the new libmediaart. I'm ready to go when you are!

I might have to get rygel through NEW though because of bumped ABI/API
in the core libraries. Will try to look at getting it preparing an
upload for experimental ASAP.

Regards,
Andreas Henriksson


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

Bug#784695: gnumeric: Mouse cursor is garbled when showing Gnumeric-specific icon

[Dmitry Smirnov]

On Thu, 7 May 2015 13:25:54 Chad Wallace wrote:
> I'm not sure if this bug belongs to Gnumeric, or GTK, or Noveau or Xorg,
> but I'm sure you can reassign it if you know better.

Thanks for your report. I see the problem on your screenshot but I've never 
experienced it and I am clueless regarding its origin. I suspect it might be 
display adapter problem... You are using GNOME and free Nvidia driver, right?
Any chance you could try logging into another Desktop Environment to see if it 
makes any difference? Thank you.

-- 
All the best,
 Dmitry Smirnov.

---

Much of humankind's intellectual and emotional struggle has been not
for truth, but against truth. The advance of science has been
sporadically fought against for thousands of years.
-- C. W. Dalton, "The Right Brain and Religion"


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

Bug#783741: memtest fails to load

[Daniel Baumann]

On 05/08/15 03:15, Ben Caradoc-Davies wrote:
> This bug is still present in the most recent images/xfce-desktop from
> live-images

yes, thanks, that's why i've reopened the bug earlier and reassigned it
to live-images. we'll address it there soon.

Regards,
Daniel

-- 
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#784622: node-configuration fixed, network-configuration changed, still not workable

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[see attachments]
First I found, that the netmask was wrong in munin-node.conf this has to be /32 
not /24.
Then I thought, it might be due to the network-configuration, because of the
network-bridge, but it was not, the second remote host still does not show up.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVMRxYACgkQ5+rBHyUt5wuDqQCgpsEb6y/zm/CmY6e+2bSpdeiB
2aAAn0HodAfF0JZwcDThSdrAjaekWt/j
=YeUR
-END PGP SIGNATURE-


munin-node.conf.xz
Description: application/xz


interfaces.xz
Description: application/xz

Bug#753163: [pkg-gnupg-maint] Bug#753163: Bug#753163: Fix before first point release ?

[Daniel Kahn Gillmor]

over on https://bugs.debian.org/753163 ...

On Tue 2015-04-28 03:14:45 -0400, Werner Koch wrote:
> On Tue, 28 Apr 2015 06:32, raphael.hal...@gmail.com said:
>> Will this bug be fixed before the first point release ?
 [...]
> For the dependency problem there is a way out:  Since GnuPG 2.1.2:
>
>  * agent: Now tries to use a fallback pinentry if the standard
>pinentry is not installed.
>
> Thus depending on a "pinentry-basic" binary (which may either be -curses
> or -dumb) you have a working setup.  Any desktop may then install -gtk or
> -qt as "pinentry" and you get want you want.

We should already be able to support this approach in debian with
/etc/alternatives, i think.

This should be satisfied with the default /usr/bin/pinentry being
pinentry-curses if no other one is installed, and then if -gtk or -qt
are installed, /etc/alternatives will be updated to point to the newer
one.

Fixing https://bugs.debian.org/765406 in tasksel by making the desktop
tasks recommend the matching graphical pinentry would resolve this
problem.  There's even a patch for it:

 
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=12;filename=tasksel.diff;att=1;bug=765406

If we could get that patch into the next point release for tasksel, i'd
be happy to move pinentry-curses to the front of the gpg-agent
Recommends pinentry disjunction for the point release as well.

This is not an increase in the dependencies for the graphical
environments, since they likely already depend on pinentry through the
current dependency chain.  But it will be a reduction in the
dependencies for server users.

If we just update the gpg-agent recommends pinentry disjunction, it's
likely that some desktop jessie users will be stuck behind
pinentry-curses, which would be a bad user experience.

Making a coordinated change with both of these updates seems like the
right way to go.  tasksel folks, are you OK with this?

 --dkg


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

Bug#784726: docker.io: CVE-2015-3627 CVE-2015-3629 CVE-2015-3630 CVE-2015-3631

[Salvatore Bonaccorso]

Source: docker.io
Version: 1.6.0+dfsg1-1
Severity: grave
Tags: security upstream fixed-upstream

Hi,

the following vulnerabilities were published for docker.io.

CVE-2015-3627[0]:
Insecure opening of file-descriptor 1 leading to privilege escalation

CVE-2015-3629[1]:
Symlink traversal on container respawn allows local privilege escalation

CVE-2015-3630[2]:
Read/write proc paths allow host modification & information disclosure

CVE-2015-3631[3]:
Volume mounts allow LSM profile escalation

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-3627
[1] https://security-tracker.debian.org/tracker/CVE-2015-3629
[2] https://security-tracker.debian.org/tracker/CVE-2015-3630
[3] https://security-tracker.debian.org/tracker/CVE-2015-3631
[4] http://www.openwall.com/lists/oss-security/2015/05/07/10

Regards,
Salvatore


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

Bug#784720: systemd: issues SIGKILL too early (risk of data loss)

[Henrique de Moraes Holschuh]

On Fri, May 8, 2015, at 01:01, Martin Pitt wrote:
> Henrique de Moraes Holschuh [2015-05-07 23:01 -0300]:
> > As reported in other distros:
> > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259
> > https://bugzilla.redhat.com/show_bug.cgi?id=1183194
> > https://bugzilla.redhat.com/show_bug.cgi?id=1141137
> > 
> > This bug has been fixed in experimental[1], but this fix needs to be
> > cherry-picked into a Debian stable update, preferably soon enough that it
> > can still make it to the first jessie point release (Debian 8.1).
> 
> I agree, this is highly annoying up to dangerous. I cherry-picked the
> patch to master:

Thank you!

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique de Moraes Holschuh 


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

Bug#784714: jessie-pu: package semi/1.14.7~0.20120428-14+deb8u1

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Fri, 2015-05-08 at 09:25 +0900, Tatsuya Kinoshita wrote:
> I'd like to update package semi in jessie to fix an important bug.
> 
> See this changelog and the attached debdiff.
> 
> semi (1.14.7~0.20120428-14+deb8u1) jessie; urgency=medium
> 
>   * New patch 020_encrypt.patch to fix incorrect keys in encryption
> (closes: #784712)

The metadata for that bug indicates that it affects the version of
"semi" in unstable. Is that correct? If so, please fix the bug in
unstable; otherwise, please fix the metadata.

Regards,

Adam


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

Bug#784720: systemd: issues SIGKILL too early (risk of data loss)

[Martin Pitt]

Control: fixed -1 219-8
Control: tag -1 pending

Hello Henrique,

Henrique de Moraes Holschuh [2015-05-07 23:01 -0300]:
> As reported in other distros:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259
> https://bugzilla.redhat.com/show_bug.cgi?id=1183194
> https://bugzilla.redhat.com/show_bug.cgi?id=1141137
> 
> This bug has been fixed in experimental[1], but this fix needs to be
> cherry-picked into a Debian stable update, preferably soon enough that it
> can still make it to the first jessie point release (Debian 8.1).

I agree, this is highly annoying up to dangerous. I cherry-picked the
patch to master:

  http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=00aaecd711

and also added the bug ref to experimental.

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature

Bug#784682: systemd unable to boot when snoopy is enabled

[Martin Pitt]

Control: reassign -1 snoopy

Michael Biebl [2015-05-07 23:36 +0200]:
> > I just came across an issue with journald being unable to start up when
> > snoopy is enabled that prevents a Jessie/systemd installation to boot up
> > which i reported to upstream at
> > https://bugs.freedesktop.org/show_bug.cgi?id=90364 .
> > 
> > This is to let you know about the issue. Maybe we need to stick a
> > warning label somewhere. ;-)
> > 
> 
> 
> I'm going to re-assign this to snappy. This looks to me like something
> which needs to be addressed in the snappy package.

I'm 99% sure this was meant to be reassigned to snoopy, not snappy :-)

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature

Bug#784725: lxpanel 0.8.1/vertical panel defaults to 150 width on every boot/see my post on siduction forum-Upgrade Warnings

[millie]

Package: lxpanel
Version: 0.8.1-1
Severity: normal

Dear Maintainer,

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

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

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



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

Kernel: Linux 4.0.1-towo.2-siduction-686 (SMP w/2 CPU cores; PREEMPT)
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 lxpanel depends on:
ii  libasound2   1.0.28-1
ii  libatk1.0-0  2.16.0-2
ii  libc62.19-18
ii  libcairo21.14.0-2.1
ii  libfm-gtk4   1.2.3-1
ii  libfm-modules1.2.3-1
ii  libfm4   1.2.3-1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-4
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.44.0-2
ii  libgtk2.0-0  2.24.25-3
ii  libiw30  30~pre9-8
ii  libkeybinder00.3.0-3
ii  libmenu-cache3   1.0.0-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  libwnck222.30.7-2
ii  libx11-6 2:1.6.3-1
ii  libxml2  2.9.2+dfsg1-3
ii  lxmenu-data  0.1.4.siduction.1
ii  lxpanel-data 0.8.1-1

Versions of packages lxpanel recommends:
ii  xkb-data  2.14-1

Versions of packages lxpanel suggests:
ii  chromium [www-browser]  42.0.2311.135-1
ii  links [www-browser] 2.9-3
ii  lxsession   0.5.1-2
ii  menu2.1.47

-- 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#784604: systemd: can't remove systemd unless it is correctly running

[Brian May]

On Thu, 7 May 2015 at 22:30 Michael Biebl  wrote:

> So, systemd.postinst seems to fail in the trigger
> We do not call systemctl uncondionally here:
>
> _systemctl() {
> if [ -d /run/systemd/system ]; then
> systemctl "$@"
> fi
> }
>
>
> if [ "$1" = "triggered" ]; then
>_systemctl daemon-reload
>exit 0
> fi
>
> So, this looks like you (wrongly) had a /run/systemd/system directory at
> this point?
>

Yes, looks like it:

root@scrooge:/# ls -la /run/systemd/system/
total 0
drwxr-xr-x 2 root root  40 May  8 02:50
. drwxr-xr-x 6 root root
180 May  8 02:50 ..

That said, I'm still curious, why the systemctl call was made in the
> first place. systemctl also complains with a D-Bus error.
> Did you have a /var/run/dbus/system_bus_socket?


Doesn't look like I have that:

root@scrooge:/# ls -la  /var/run/
total 4
drwxr-xr-x  4 root root   80 May  8 02:50 .
drwxr-xr-x 20 root root 4096 May  8 02:50 ..
drwxrwxrwt  2 root root   40 May  8 02:50 lock
drwxr-xr-x  6 root root  180 May  8 02:50 systemd


If that socket does not
> exist, systemctl should fall back to use a private dbus socket which
> doesn't require a run dbus system bus.
> Was dbus installed at this point dbus.service and dbus.socket correctly
> running?
>

dbus is installed, however it is not running. In fact I think systemd
hasn't actually started anything.

root@scrooge:/# ps aufx
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  0.0  0.4   4892  2140 ?Ss   02:50   0:00 init -z
root 2  0.0  0.0  0 0 ?S02:50   0:00
[kthreadd/104]
root 3  0.0  0.0  0 0 ?S02:50   0:00  \_
[khelper/104]
root47  0.0  0.1  25540   708 ?Ss   02:51   0:00 vzctl:
pts/0
root48  0.0  0.4   4296  2612 pts/0Ss   02:51   0:00  \_ -bash
root   387  0.0  0.1   2872   916 pts/0R+   03:04   0:00  \_ ps
aufx
root@scrooge:/#

I suspect systemd might be trying to display something on the console,
however I am not sure how to display that stuff using openvz/proxmox
(thought there was a way...)

I think systemd has got into a very strange state, where it thinks it has
started, but it isn't really running properly, and as such hasn't started
anything it was suppose to.

Also, not just systemd that can trigger this problem (also: does the
following really mean hplip and colord can't be installed without systemd?)

root@scrooge:/var/log# apt-get install systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
systemd is already the newest version.
systemd set to manually installed.
The following packages were automatically installed and are no longer
required:
  consolekit hpijs libck-connector0 libcolord1 libffi5 libgd2-xpm
libgphoto2-2 libgphoto2-port0 libjpeg8 liblcms1 libopenjpeg2
  libpam-ck-connector libpoppler19 libslp1 libsystemd-login0 libtiff4
pciutils ttf-freefont usbutils
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@scrooge:/var/log# ls^C
(reverse-i-search)`': ^C
root@scrooge:/var/log# apt-get remove systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
  avahi-daemon colord-data consolekit cups cups-browsed cups-client
cups-core-drivers cups-daemon cups-filters cups-filters-core-drivers
  cups-ppdc cups-server-common dconf-gsettings-backend dconf-service
foomatic-db-compressed-ppds foomatic-db-engine gir1.2-glib-2.0
  hpijs hplip-data libart-2.0-2 libasn1-8-heimdal libavahi-core7
libavahi-glib1 libck-connector0 libcolord1 libcolord2 libcolorhug2
  libcupscgi1 libcupsmime1 libcupsppdc1 libdaemon0 libdbus-glib-1-2
libdconf1 libexif12 libffi5 libfile-copy-recursive-perl
  libfontembed1 libgd2-xpm libgd3 libgirepository-1.0-1 libgphoto2-2
libgphoto2-6 libgphoto2-l10n libgphoto2-port0 libgphoto2-port10
  libgssapi3-heimdal libgudev-1.0-0 libgusb2 libgutenprint2
libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhpmud0
  libhx509-5-heimdal libieee1284-3 libjim0.75 libjpeg8 libkrb5-26-heimdal
liblcms1 libldb1 libltdl7 libnss-mdns libntdb1 libopenjpeg2
  libpam-ck-connector libperl5.20 libpolkit-agent-1-0 libpolkit-backend-1-0
libpolkit-gobject-1-0 libpoppler19 libpython2.7 libqpdf13
  libroken18-heimdal libsane libsane-common libsane-extras
libsane-extras-common libsane-hpaio libsensors4 libslp1 libsmbclient
  libsnmp-base libsnmp30 libsystemd-login0 libtalloc2 libtcl8.6 libtdb1
libtevent0 libtiff4 libtk8.6 libusb-1.0-0 libv4l-0
  libv4lconvert0 libvpx1 libwbclient0 libwind0-heimdal libxss1 mscompress
pciutils printer-driver-all printer-driver-brlaser
  printer-driver-c2050 printer-driver-c2esp printer-driver-cjet
printer-driver-dymo printer-driver-escpr printer-driver-foo2zjs
  printer-driver-fo

Bug#733242: xserver-xorg-video-qxl: FullHD resolution (1920 x 1080) is missing

[intrigeri]

Control: tag -1 + moreinfo

Hi Lars,

Lars Cebulla wrote (27 Dec 2013 17:23:36 GMT) :
> I installed Debian Wheezy via virt-manager with Gnome 3 (Classic mode) and
> xserver-xorg-video-qxl.
> Now I wanted to change the resolution to my native monitor resolution but
> 1920x1080 is not available.

I can reproduce that with Wheezy guests. However, this has been
working fine here with Jessie guests on a sid host for many months
now. May you please confirm that this problem is fixed on Jessie, so
that this bug can be flagged as such?

Cheers!


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

Bug#521694: dvb-apps: dvbscan failes to set frontend

[Bernhard Übelacker]

Hello Sebastian, hello Eric,
I stumbled over the same error and found this report, so I attach
my findings to it - even when this report is alreay quite old ...

As of today it seems "dvbscan" has more than one problem:
- needed input file format seems more like
/usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
- polarization from the input file gets not used
(Failed to set frontend)
- return value of dvbfe_get_info is checked wrong
(Unable to query frontend status)
- when we succeed above we get into function dvbscan_scan_dvb
which is empty ???

Therefore, in my opinion, the file /usr/bin/dvbscan in its current
state is useless.

When you was building from source you already used instead
of util/dvbscan/dvbscan the executable util/scan/scan.

That one from the package worked flawless for me (at least DVB-S):

$ /usr/bin/scan /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
scanning /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 12551500 V 2200 5
>>> tune to: 12551:v:0:22000
DVB-S IF freq is 1951500
...
0x0011 0x0fa7: pmt_pid 0x (null) -- Thomson SAT IPDL (running)
Network Name 'BetaDigital'
dumping lists (1223 services)
...


Kind regards,
Bernhard
$ cat /usr/share/dvb/dvb-s/Astra-19.2E
# Astra 19.2E SDT info service transponder
# freq pol sr fec
[CHANNEL]
DELIVERY_SYSTEM = DVBS
FREQUENCY = 12551500
POLARIZATION = VERTICAL
SYMBOL_RATE = 2200
INNER_FEC = 5/6
INVERSION = AUTO


$ dvbscan /usr/share/dvb/dvb-s/Astra-19.2E
# no output at all


$ cat /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
S 12551500 V 2200 5/6


$ dvbscan /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
Failed to open frontend


$ id
uid=108(hts) gid=113(hts) Gruppen=113(hts)


$ ls -lisah /dev/dvb/adapter0/frontend0
4556 0 crw-rw 1 root video 212, 0 Apr 17 23:13 /dev/dvb/adapter0/frontend0


# adduser hts video
Füge Benutzer »hts« der Gruppe »video« hinzu ...
Benutzer hts wird zur Gruppe video hinzugefügt.
Fertig.


$ id
uid=108(hts) gid=113(hts) Gruppen=113(hts),44(video)


$ dvbscan /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
Failed to set frontend


--- dvbscan.c.orig  2015-05-08 04:22:10.509663577 +0200
+++ dvbscan.c   2015-05-08 04:22:16.729843422 +0200
@@ -104,6 +104,7 @@ static int scan_load_callback(struct dvb
struct transponder *t = new_transponder();
append_transponder(t, &toscan, &toscan_end);
memcpy(&t->params, &channel->fe_params, sizeof(struct 
dvbfe_parameters));
+   t->polarization = channel->polarization;
 
add_frequency(t, t->params.frequency);
t->params.frequency = 0;


$ util/dvbscan/dvbscan /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
Unable to query frontend status


while((time(NULL) - starttime) < TIMEOUT_WAIT_LOCK) {
if (dvbfe_get_info(fe, DVBFE_INFO_LOCKSTATUS, 
&feinfo,

DVBFE_INFO_QUERYTYPE_IMMEDIATE, 0) !=
-   DVBFE_INFO_QUERYTYPE_IMMEDIATE) {
+   DVBFE_INFO_LOCKSTATUS) {
fprintf(stderr, "Unable to query 
frontend status\n");
exit(1);
}


--- dvbscan_dvb.c.orig  2013-05-13 12:19:02.0 +0200
+++ dvbscan_dvb.c   2015-05-08 04:48:27.619113832 +0200
@@ -27,4 +27,5 @@
 void dvbscan_scan_dvb(struct dvbfe_handle *fe)
 {
// FIXME
+   fprintf(stderr, "dvbscan_scan_dvb: not implemented\n");
 }


$ util/dvbscan/dvbscan /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
dvbscan_scan_dvb: not implemented





$ /usr/bin/scan /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
scanning /usr/share/dvb/dvb-legacy/dvb-s/Astra-19.2E
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 12551500 V 2200 5
>>> tune to: 12551:v:0:22000
DVB-S IF freq is 1951500
...
0x0011 0x0fa7: pmt_pid 0x (null) -- Thomson SAT IPDL (running)
Network Name 'BetaDigital'
dumping lists (1223 services)
...

Bug#784724: transition: gloox

[Vincent Cheng]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

I'd like to request a transition slot for src:gloox. This is a relatively small
transition, with only 4 source packages affected (tested builds against newer
gloox, currently in experimental, results are as follows):

licq (build ok, needs binNMU)
0ad (build ok, needs binNMU)
uwsgi (build ok, needs binNMU)
fatrat (NOT in testing, removed due to boost-related FTBFS - #713663)

Ben file:

title = "gloox";
is_affected = .depends ~ "libgloox12" | .depends ~ "libgloox13";
is_good = .depends ~ "libgloox13";
is_bad = .depends ~ "libgloox12";

Regards,
Vincent

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

Kernel: Linux 3.18-3-vclaptop-amd64 (SMP w/8 CPU cores; PREEMPT)
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)


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

Bug#784723: alot: [PATCH] Please make the build reproducible

[Juan Picca]

Source: alot
Version: 0.3.6-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that alot could not be built reproducibly.

The attached patch removes extra timestamps from the build system
when creating the source archive. Once applied, alot can be built
reproducibly in our current experimental framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -rupN alot-0.3.6.old/debian/rules alot-0.3.6/debian/rules
--- alot-0.3.6.old/debian/rules	2014-08-22 06:52:14.0 -0300
+++ alot-0.3.6/debian/rules	2015-05-07 11:35:52.565732248 -0300
@@ -1,4 +1,6 @@
 #!/usr/bin/make -f
+LAST_CHANGE=$(shell dpkg-parsechangelog -S Date)
+BUILD_DATE=$(shell LC_ALL=C date -u "+%B %d, %Y" -d "$(LAST_CHANGE)")
 
 %:
 	dh $@ --with python2,sphinxdoc
@@ -6,7 +8,7 @@
 override_dh_auto_build:
 	dh_auto_build
 	rm -rf $(CURDIR)/docs/build
-	$(MAKE) -C docs html man
+	$(MAKE) -C docs html man SPHINXOPTS="-D today=\"$(BUILD_DATE)\""
 
 override_dh_auto_install:
 	dh_auto_install -- --install-lib=/usr/share/alot/

Bug#777777:

[Yurii Kolesnykov]

Looks like a bug in boost.

Bug#776293: ats2-lang_0.1.9-1_amd64.changes REJECTED

[Kiwamu Okabe]

Hi Matthew,

On Fri, May 8, 2015 at 1:19 AM, Matthew Danish
 wrote:
> I am rejecting your upload of ats2-lang 0.1.9-1, because it introduces
> the ats2-mode package, which is so very small, that it is hardly worth
> a full package.
>
> Instead, I would suggest including the Emacs mode in the main package,
> and simply suggesting emacsen-common (maybe not even that...). A few
> examples where this is done may be afnix, aribas, autoconf, etc.

O.K.
How about this patch for it?

Thank's,
-- 
Kiwamu Okabe at METASEPI DESIGN
diff -urN ats2-lang-0.1.8/debian/ats2-lang.emacsen-compat ats2-lang-0.1.11/debian/ats2-lang.emacsen-compat
--- ats2-lang-0.1.8/debian/ats2-lang.emacsen-compat	1970-01-01 09:00:00.0 +0900
+++ ats2-lang-0.1.11/debian/ats2-lang.emacsen-compat	2015-05-08 11:10:26.148566188 +0900
@@ -0,0 +1 @@
+0
diff -urN ats2-lang-0.1.8/debian/ats2-lang.emacsen-install ats2-lang-0.1.11/debian/ats2-lang.emacsen-install
--- ats2-lang-0.1.8/debian/ats2-lang.emacsen-install	1970-01-01 09:00:00.0 +0900
+++ ats2-lang-0.1.11/debian/ats2-lang.emacsen-install	2015-05-08 11:10:26.148566188 +0900
@@ -0,0 +1,36 @@
+#!/bin/sh -e
+# /usr/lib/emacsen-common/packages/install/ats2-mode
+
+FLAVOR=$1
+PACKAGE=ats2-mode
+
+# A number of old emacs versions are not supported by upstream:
+case $FLAVOR in
+emacs|emacs19|emacs20|emacs21|xemacs21)
+exit 0
+	;;
+esac
+
+echo install/${PACKAGE}: Handling install for emacsen flavor ${FLAVOR}
+
+# The byte-compiled files goes into the site-lisp directory.
+BCDIR=/usr/share/${FLAVOR}/site-lisp/${PACKAGE}
+install -m 755 -d ${BCDIR}
+
+# The elisp source files are in the generic site-list directory.
+SRCDIR=/usr/share/emacs/site-lisp/${PACKAGE}
+SRC=`find ${SRCDIR} -name '*.el' -exec basename '{}' ';'`
+
+# Prepare for byte-compiling the source files.
+cd ${BCDIR}
+ln -sf ${SRCDIR}/*.el .
+cat << EOF > path.el
+(setq load-path (cons "." load-path) byte-compile-warnings nil)
+EOF
+
+# Byte-compile elisp files.
+FLAGS="--no-site-file --no-init-file --batch -l path.el -f batch-byte-compile"
+${FLAVOR} ${FLAGS} ${SRC}
+rm -f path.el
+
+exit 0
diff -urN ats2-lang-0.1.8/debian/ats2-lang.emacsen-remove ats2-lang-0.1.11/debian/ats2-lang.emacsen-remove
--- ats2-lang-0.1.8/debian/ats2-lang.emacsen-remove	1970-01-01 09:00:00.0 +0900
+++ ats2-lang-0.1.11/debian/ats2-lang.emacsen-remove	2015-05-08 11:10:26.152566103 +0900
@@ -0,0 +1,15 @@
+#!/bin/sh -e
+# /usr/lib/emacsen-common/packages/remove/ats2-mode
+FLAVOR=$1
+PACKAGE=ats2-mode
+
+# A number of old emacs versions are not supported by upstream:
+case $FLAVOR in
+emacs|emacs19|emacs20|emacs21|xemacs21)
+exit 0
+	;;
+esac
+
+echo remove/${PACKAGE}: purging byte-compiled files for ${FLAVOR}
+rm -rf /usr/share/${FLAVOR}/site-lisp/${PACKAGE}
+exit 0
diff -urN ats2-lang-0.1.8/debian/ats2-lang.emacsen-startup ats2-lang-0.1.11/debian/ats2-lang.emacsen-startup
--- ats2-lang-0.1.8/debian/ats2-lang.emacsen-startup	1970-01-01 09:00:00.0 +0900
+++ ats2-lang-0.1.11/debian/ats2-lang.emacsen-startup	2015-05-08 11:10:26.152566103 +0900
@@ -0,0 +1,12 @@
+;; -*-emacs-lisp-*-
+(if (not (file-exists-p "/usr/share/emacs/site-lisp/ats2-mode"))
+(message "Package ats2-mode needs reinstall.  Skipping setup.")
+
+  (setq load-path (cons (concat "/usr/share/"
+(symbol-name debian-emacs-flavor)
+"/site-lisp/ats2-mode") load-path))
+  (add-to-list 'auto-mode-alist '("\\.\\(d\\|s\\)ats\\'" . ats-mode))
+  (autoload 'ats-mode "ats2-mode" "Major mode to edit ATS2 source code" t)
+  (require 'ats2-flymake)
+  (add-hook 'ats-mode-hook 'ats2-flymake-load)
+)
diff -urN ats2-lang-0.1.8/debian/ats2-lang.install ats2-lang-0.1.11/debian/ats2-lang.install
--- ats2-lang-0.1.8/debian/ats2-lang.install	1970-01-01 09:00:00.0 +0900
+++ ats2-lang-0.1.11/debian/ats2-lang.install	2015-05-08 11:10:26.152566103 +0900
@@ -0,0 +1 @@
+utils/emacs/*.el usr/share/emacs/site-lisp/ats2-mode/
diff -urN ats2-lang-0.1.8/debian/changelog ats2-lang-0.1.11/debian/changelog
--- ats2-lang-0.1.8/debian/changelog	2015-01-25 05:53:36.0 +0900
+++ ats2-lang-0.1.11/debian/changelog	2015-05-08 11:19:23.511306346 +0900
@@ -1,3 +1,10 @@
+ats2-lang (0.1.11-1) UNRELEASED; urgency=medium
+
+  * New upstream release
+  * Include emacs mode for ATS2
+
+ -- Kiwamu Okabe   Mon, 26 Jan 2015 18:32:04 +0900
+
 ats2-lang (0.1.8-1) unstable; urgency=medium
 
   * New upstream release
diff -urN ats2-lang-0.1.8/debian/control ats2-lang-0.1.11/debian/control
--- ats2-lang-0.1.8/debian/control	2014-11-25 09:07:53.0 +0900
+++ ats2-lang-0.1.11/debian/control	2015-05-08 11:15:49.751091058 +0900
@@ -2,13 +2,13 @@
 Section: devel
 Priority: optional
 Maintainer: Matthew Danish 
-Build-Depends: debhelper (>= 8.0.0), autotools-dev, libgmp3-dev
+Build-Depends: debhelper (>= 8.0.0), autotools-dev, libgmp-dev
 Standards-Version: 3.9.6
 Homepage: http://www.ats-lang.org/
 
 Package: ats2-lang
 Architect

Bug#784722: mew-beta: incorrect keys in encryption

[Tatsuya Kinoshita]

Package: mew-beta
Version: 7.0.50~6.6+0.20140902-1
Severity: important
Tags: jessie security

It was discovered that Mew, a mail reader supporting PGP/MIME for
Emacs, did not properly implement recipients matching to encrypt
mails.  This may allow unrelated person may decrypt the mails.

cf.
  - https://github.com/kazu-yamamoto/Mew/issues/77
From: Tatsuya Kinoshita
> When the following keys are imported,
>
>   - 1024D/97AA33D6 Dima Barsky 
>   - 1024D/1A944AD7 Martin Albert 
>
> I write a mail with To: m...@debian.org, and encrypt it,
> then it is encrypted with Dima's key instead of Martin's key.
Fixed in 
https://github.com/kazu-yamamoto/Mew/commit/5fa1fbd130f90b8afbeef66e256eead031f17e27

The security team suggested that is rather a candidate for a fix in
a point update instead of a Debian Security Advisory.

Thanks,
--
Tatsuya Kinoshita


pgp8fBxEGbVdk.pgp
Description: PGP signature

Bug#784721: mew: incorrect keys in encryption

[Tatsuya Kinoshita]

Package: mew
Version: 1:6.6-2
Severity: important
Tags: jessie security

It was discovered that Mew, a mail reader supporting PGP/MIME for
Emacs, did not properly implement recipients matching to encrypt
mails.  This may allow unrelated person may decrypt the mails.

cf.
  - https://github.com/kazu-yamamoto/Mew/issues/77
From: Tatsuya Kinoshita
> When the following keys are imported,
>
>   - 1024D/97AA33D6 Dima Barsky 
>   - 1024D/1A944AD7 Martin Albert 
>
> I write a mail with To: m...@debian.org, and encrypt it,
> then it is encrypted with Dima's key instead of Martin's key.
Fixed in 
https://github.com/kazu-yamamoto/Mew/commit/5fa1fbd130f90b8afbeef66e256eead031f17e27

The security team suggested that is rather a candidate for a fix in
a point update instead of a Debian Security Advisory.

Thanks,
--
Tatsuya Kinoshita


pgppOutTiAYqP.pgp
Description: PGP signature

Bug#784720: systemd: issues SIGKILL too early (risk of data loss)

[Henrique de Moraes Holschuh]

Package: systemd
Version: 215-17
Severity: grave
Tags: upstream fixed-in-experimental
Justification: causes non-serious data loss

As reported in other distros:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259
https://bugzilla.redhat.com/show_bug.cgi?id=1183194
https://bugzilla.redhat.com/show_bug.cgi?id=1141137

This bug has been fixed in experimental[1], but this fix needs to be
cherry-picked into a Debian stable update, preferably soon enough that it
can still make it to the first jessie point release (Debian 8.1).

For the record, I've been personally a victim of a non-serious, but still
rather annoying data loss episode most likely caused by this issue, as it
matches exactly what is described in the redhat bug reports.

[1]
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimental&id=6068e872da


-- Package-specific info:

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

Kernel: Linux 3.18.12 (SMP w/8 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.16-1
ii  libpam-systemd  215-17

Versions of packages systemd suggests:
ii  systemd-ui  3-2

-- no debconf information

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


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

Bug#784713: [Pkg-samba-maint] Bug#784713: samba-common: legacy config file /etc/samba/dhcp.conf

[Christoph Anton Mitterer]

Hey Jelmer

On Fri, 2015-05-08 at 01:04 +, Jelmer Vernooij wrote: 
> This file is current, and will be created/updated by the dhclient hook
> that lives in /etc/dhcp/dhclient-enter-hooks.d/samba.
Ah, I've just noticed it as well...

But AFAICS it wouldn't be removed on purging the package, would it?

If it would, then we can close the bug, I guess.


Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#783741: memtest fails to load

[Ben Caradoc-Davies]

This bug is still present in the most recent images/xfce-desktop from 
live-images (debian branch, commit c93ad8eb) built with live-build 4.0.3-1.


The underlying cause is that the default for "lb config --memtest" was 
set to "none" in this live-build commit for live-build 4.x:


commit 157ba674785b2856a56dfe7a0aeff0b11538be35
Author: Daniel Baumann 
Date:   Wed Mar 13 21:28:12 2013 +0100
Setting memtest default to none.

Wheezy is only up to live-build 3.0.5-1 and lacks this change, so 
memtest86+ is present in wheezy live images.


Jessie official live images have the memtest86+ isolinux menu options, 
but because live-build 4.x defaults to "lb config --memtest none", the 
memtest86+ binary is not present in jessie live images.


One solution may be to add "--memtest memtest86+" to auto/config for all 
images in live-images on the debian and debian-next branches.


Kind regards,

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


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

Bug#767353: clamav: ERROR: Can't save PID to file /var/run/clamav/freshclam.pid: No such file or directory

[Christoph Anton Mitterer]

Control: reopen -1


Hey.

I'm reopening this for now, since it seems the fix didn't get applied to
all installations of wheezy during upgrade to jessie.

AFAIU, part of the solution was to remove:
PidFile /var/run/clamav/freshclam.pid
from
/etc/clamav/freshclam.conf
which is done by the following snipped from the postinst: 
  if `dpkg --compare-versions "$2" lt 0.98.5+dfsg-4~`; then
# Remove the PidFile variable from the configuration, if it is the
previous default value.
if [ "$PidFile" = "/var/run/clamav/freshclam.pid" ]; then
  PidFile=''
fi
  fi

This works fine for wheezy itself, where the version was/is:
0.98.5+dfsg-0+deb7u2
but any site that had enabled e.g. wheezy-updates wouldn't be matched,
since it already has 0.98.7+dfsg-0+deb7u1 and this version's postinst,
doesn't apply the necessary changes.


Cheers,
Chris.



smime.p7s
Description: S/MIME cryptographic signature

Bug#784405: ITP: rnetclient -- Client to submit the Brazilian Income Tax Report to the Brazilian Tax Authority

[Sergio Durigan Junior]

On Thursday, May 07 2015, Henrique de Moraes Holschuh wrote:

>> That is actually a pretty good solution!  I am still learning the terms
>> and the whole process here, but jessie-updates, according to:
>> 
>>   
>>   (thanks to Cascardo for providing the link)
>> 
>> would indeed be the ideal place for rnetclient, according to this
>> criterion:
>> 
>>   - Packages that need to be current to be useful (e.g. clamav).
>
> I am well versed with stable-updates, I upload to it several times per
> year due to intel-microcode.  Unless there is previous arrangement with
> the stable release managers, an upload to stable-proposed-updates it is
> not always going to be fast enough for this.  "keep current" doesn't
> mean "rush into stable every time", after all.

Oh, sure, I did not mean to lecture you, I am well aware of your Debian
fame.  Sorry if it sounded like that.

As for being fast enough, Receita Federal usually gives 2 months to
prepare and submit your tax report, and the majority of the population
usually wait until the last week to fulfill their duties, so maybe it is
reasonable to expect that, if rnetclient enters the stable-updates repo
in the middle of the timeframe of 2 months (i.e., 1 month after RFB
published the proprietary versions of the softwares), we will still have
plenty of users benefitted by this.  Does this sound feasible?

> IMHO, it would be far better to have someone maintain the debian
> packaging of this stuff upstream, in a "apt-gettable" repository that
> can be added to sources.list.  Such a repository, although unofficial,
> could be both Debian and Ubuntu-friendly, and target also the LTS
> branches of Debian and Ubuntu.  This side-steps all the issues I raised.

It seems that the only remaining issue was deciding which repository
would be a better fit for the program, and if the proposal of putting it
in the stable-updates is accepted, then we're golden.

I had considered the option of maintaining the Debian infrastructure
upstream when I saw your first message (actually, even before I posted
the ITP!), but I still think it is more beneficial to have rnetclient in
the official repository.  It would, for example, be much harder to be
able to provide ports for different architectures just like Debian does
but without using Debian's infrastructure; I could mention other "good
to have" things as debbugs here, but I think you've got the point :-).

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


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

Bug#541637: I think I have ran into it as well

[Yaroslav Halchenko]

Today, that is 6 years after initial report ;)

here are the detail when running with git from current master
v2.4.0-53-g8440f74

Starting program: /home/yoh/proj/misc/git/git push origin master
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x0046de8d in map_refspec (ref=0x7fffe10a "master", 
remote=0x863810, local_refs=0x86c260) at builtin/push.c:63
63  if (branch->merge_nr == 1 && branch->merge[0]->src) {
(gdb) print branch
$1 = (struct branch *) 0x83dba0
(gdb) print (branch->merge_nr)
$2 = 1
(gdb) print (branch->merge[0]->src)
Cannot access memory at address 0x0
*(gdb) print (branch->merge[0])
Cannot access memory at address 0x0
*(gdb) print (branch->merge)
$3 = (struct refspec **) 0x0


when I added a remote for that (origin) branch -- push went fine.

-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


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

Bug#784719: not backward compatible and faulty manpage

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: cproto
Version: 4.7l-3
Severity: important


I appeares that cproto 4.7l-3 has a faulty manpage
and that some options have disappeared from the
oldstable (Wheezy) version 4.7j .
For example: the option -X is no more valid but it is
documented in the man page.

I realised it while using pbuilder to check a package
within unstable.

Thanks,
Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJVTA2lAAoJEIC/w4IMSybjNoEH/3/heDkN05SDSs+gLW9d0q9s
QE6sQ/iZCgaTmvh7TpFtALLFos/xRAlle/6bvzkodgmW9mKn2E/SKUeHgyMU9cg4
uD+n+Em+TH4twAjOU3alCXkTSTpnVek6LuvhOkUcvi7ddSdThYY4V2DopPEWSzTU
WWpgXwMJ4eZZDW33L1qP+aaRJoXFcfRnD1DBCnFf+44AZz6CXEo7qnweDmvjnslj
ofqh6Gu4u9LEeefCK8EmDjM0upslC/Q5lYeVzZ1nqaXcgTuVYJSFc8FA2poCu3GO
utrSOghOanq3JJfFPYnXReFfKYI7fBLUFx5YonewjjqNjdTOsW0W/b/jfVDw9VY=
=OIIt
-END PGP SIGNATURE-


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

Bug#784713: [Pkg-samba-maint] Bug#784713: samba-common: legacy config file /etc/samba/dhcp.conf

[Jelmer Vernooij]

On Fri, May 08, 2015 at 02:31:31AM +0200, Christoph Anton Mitterer wrote:
> Apparently until some versions the file /etc/samba/dhcp.conf was part of the
> package or created by it... however it seems to be no longer shipped/created
> with/by it nowadays.
> 
> OTOH it wasn't deleted and is now leftover empty.
> 
> To keep systems more consistent and get rid of legacy files, please
> please remove empty versions of it properly with one of the next package 
> versions.

This file is current, and will be created/updated by the dhclient hook
that lives in /etc/dhcp/dhclient-enter-hooks.d/samba.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629406 for some
discussion about moving this file to /run.

Cheers,

Jelmer


signature.asc
Description: Digital signature

Bug#784718: nmu: libdevel-cover-perl_1.18-1

[gregor herrmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

No idea how this happened:

% grep-excuses libdevel-cover-perl 
libdevel-cover-perl (1.17-1 to 1.18-1)
Maintainer: Debian Perl Group
11 days old (needed 5 days)
libdevel-cover-perl/arm64 unsatisfiable Depends: perl (<< 5.20.2~)
Valid candidate

but it seems like libdevel-cover-perl was built in a stale chroot on
arm64. Please binNMU it; maybe it needs an extra-depends on a recent
perl to make sure the chroot is updated.

nmu libdevel-cover-perl_1.18-1 . arm64 . -m "Rebuild against perl 5.20.2-4."


Thanks in advance,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJVTAo6XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGQhkQAMLMrcGnTR3L0BlWRf1TvWmF
O3Z2j7Kxryzhu578tPRT7BzwYgUmrpiCG7QHkYz7GQJ9QOExRMJ4Z1EUUbyiMtdg
4ATHSO1PUZJsZiecFZplneStaGfileeqm1GejwY2rlu8wjnW5i2W+ooH/V/jWHoB
7qUth7aMu0/hf51xRDAMnV+CzLaVJ8EIZn9tePZXoOJQacf9m0MQ5AkZoAeQy+Ri
gC5Hys9Of4jkDDvCVSbcTLnAhCgOiCnHvhc63jVRGQvvNDo9zYIBLSVpfUjItFA4
naO1bje+pFo793i0iGiV0Yr8OMx0+3kQEV82RFNaVdjp/H0i/JfIsZX5S2+xDPon
rZM1D9dG8jjm/pzXOazF4tZEItJVXJsRww3Nh1CY7oFFniursOAeJBfvWVVfmzs+
irFffGyVI1ha77DiTbdQN/WDP9Plt6Ic02ipPyWffhk1sHmIy62odBY2XXEiK5gY
9c9w/nP7hkPzlyMAj+w45R1J/CjZUg6I1wRLdMAThezK9e7aWjSYmmUx0WdgO/6Z
OXfL0mdF9Z9IFSu0RkBW0s+HCa7YYFbtPjzybDcMFLLLIuT22yJKlcmNh2wo5Yqp
TMjdewnAZR7xaKbehyk2erZefFkhCMski+pWjNOCByhvNV1EZvjfnBFwr//RsmxV
H7QMH4Br6/9VRQR+Re7S
=+SBM
-END PGP SIGNATURE-


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

Bug#747379: sensord: conffiles not removed

[Christoph Anton Mitterer]

Control: reopen -1

Hi.

It seems that this hasn't worked:

# apt-cache policy sensord 
sensord:
  Installed: 1:3.3.5-2
  Candidate: 1:3.3.5-2
  Version table:
*** 1:3.3.5-2 0
500 http://ftp.de.debian.org/debian/ unstable/main amd64
Packages
100 /var/lib/dpkg/status


However:
# dpkg -S /etc/logcheck/ignore.d.server/sensord 
sensord: /etc/logcheck/ignore.d.server/sensord

And my sensord didn't have any local modifcations.


Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#784717: mention why some -F items lack file size

[積丹尼 Dan Jacobson]

Package: youtube-dl
Version: 2015.02.28-1
Severity: wishlist
File: /usr/share/man/man1/youtube-dl.1.gz

Man page should mention that/why some -F items lack file size.
One would think they can't be downloaded, but that is not the case.

$ youtube-dl -F http://www.youtube.com/watch?v=6tur0xYbjqw
[youtube] 6tur0xYbjqw: Downloading webpage
[youtube] 6tur0xYbjqw: Extracting video information
[youtube] 6tur0xYbjqw: Downloading DASH manifest
[info] Available formats for 6tur0xYbjqw:
format code  extension  resolution note
140  m4aaudio only DASH audio  131k , m4a_dash container, aac  
@128k (44100Hz), 41.82MiB
141  m4aaudio only DASH audio  259k , m4a_dash container, aac  
@256k (44100Hz), 83.50MiB
160  mp4192x144DASH video  119k , 15fps, video only, 
35.51MiB
133  mp4320x240DASH video  254k , 30fps, video only, 
79.68MiB
134  mp4480x360DASH video  614k , 30fps, video only, 
138.45MiB
135  mp4640x480DASH video 1120k , 30fps, video only, 
246.91MiB
136  mp4960x720DASH video 2248k , 30fps, video only, 
508.96MiB
17   3gp176x144
36   3gp320x240
5flv400x240
43   webm   640x360
18   mp4640x360
22   mp41280x720   (best)


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

Bug#784716: mention -F exits and doesn't proceed to download anything

[積丹尼 Dan Jacobson]

Package: youtube-dl
Version: 2015.02.28-1
Severity: wishlist
File: /usr/share/man/man1/youtube-dl.1.gz

 -F, --list-formats   list all available formats
should say
 -F, --list-formats   just list all available formats and then exit


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

Bug#784715: qemu-system-x86: booting Debian install cd makes qemu window endless toggle between two window sizes

[Bernhard Übelacker]

Package: qemu-system-x86
Version: 1:2.1+dfsg-11
Severity: normal
Tags: upstream

Dear Maintainer,
I quite regularly install some qemu VMs by just doing something like this:
qemu-system-x86_64 --enable-kvm -drive file=disk.img -cdrom cd.iso

When cd.iso contains a Debian install cd then I encounter this strange
behaviour:
- qemu window openens
- bios screen is shown for half a second
- debian install cd boot screen is shown
- qemu window starts endlessly toggling between 640x480 and 720x400

One can then double click the window bar to hide the content, then this
flickering
stops, but now the content is scaled and the window will never change its size
when the guest resolution changes.

I was able to observe this with following CDs:
  debian-6.0.2.1-i386-CD-1.iso
  debian-7.3.0-i386-CD-1.iso
  debian-jessie-DI-rc1-i386-CD-1.iso

Also a upstream git qemu-v2.2.0 shows this behaviour.

Here are some things probably also need to be met:
- Using KDE as DE.
  I tried also starting it in an empty X server with just a xterm, there it
does
  not flicker. With a instance of twm in this X server it is also not shown.
  But by starting an instance of kwin in this empty X server it happens too.
- When adding at the command line to boot from network (-boot n) some time pass
  by not finding the network server - then falling back to the CD and then the
  flickering is not shown too.
- I observed a movement of the qemu window in the first second, like it is
created
  without window borders and aligned to one screen border, and then the border
  is added and therefore the window is moved.
  Adding "-no-frame" avoids the flickering too, but then there is no frame ...
- By default it seems that qemu uses the SDL output (-display sdl)


Kind regards,
Bernhard



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

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 qemu-system-x86 depends on:
ii  ipxe-qemu   1.0.0+git-20141004.86285d1-1
ii  libaio1 0.3.110-1
ii  libasound2  1.0.28-1
ii  libbluetooth3   5.23-2+b1
ii  libbrlapi0.65.2~20141018-5
ii  libc6   2.19-18
ii  libcurl3-gnutls 7.38.0-4+deb8u2
ii  libfdt1 1.4.0+dfsg-1
ii  libgcc1 1:4.9.2-10
ii  libglib2.0-02.42.1-1
ii  libgnutls-deb0-28   3.3.8-6+deb8u1
ii  libiscsi2   1.12.0-2
ii  libjpeg62-turbo 1:1.3.1-12
ii  libncurses5 5.9+20140913-1+b1
ii  libpixman-1-0   0.32.6-3
ii  libpng12-0  1.2.50-2+b2
ii  libpulse0   5.0-13
ii  librados2   0.80.7-2
ii  librbd1 0.80.7-2
ii  libsasl2-2  2.1.26.dfsg1-13
ii  libsdl1.2debian 1.2.15-10+b1
ii  libseccomp2 2.1.1-1
ii  libspice-server10.12.5-1+b1
ii  libssh2-1   1.4.3-4.1
ii  libtinfo5   5.9+20140913-1+b1
ii  libusb-1.0-02:1.0.19-1
ii  libusbredirparser1  0.7-1
ii  libuuid12.25.2-6
ii  libvdeplug2 2.3.2+r586-1
ii  libx11-62:1.6.2-3
ii  libxen-4.4  4.4.1-9
ii  libxenstore3.0  4.4.1-9
ii  qemu-system-common  1:2.1+dfsg-11
ii  seabios 1.7.5-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages qemu-system-x86 recommends:
ii  qemu-utils  1:2.1+dfsg-11

Versions of packages qemu-system-x86 suggests:
ii  kmod 18-3
ii  ovmf 0~20131112.2590861a-3
ii  samba2:4.1.17+dfsg-2
pn  sgabios  
pn  vde2 

-- 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#784714: jessie-pu: package semi/1.14.7~0.20120428-14+deb8u1

[Tatsuya Kinoshita]

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

Hi, the release team,

I'd like to update package semi in jessie to fix an important bug.

See this changelog and the attached debdiff.

semi (1.14.7~0.20120428-14+deb8u1) jessie; urgency=medium

  * New patch 020_encrypt.patch to fix incorrect keys in encryption
(closes: #784712)

 -- Tatsuya Kinoshita   Fri, 08 May 2015 09:09:01 +0900

Please let me know if I can upload it.

Thanks,
-- 
Tatsuya Kinoshita
diffstat for semi-1.14.7~0.20120428 semi-1.14.7~0.20120428

 changelog |7 ++
 patches/020_encrypt.patch |  114 ++
 patches/series|1 
 3 files changed, 122 insertions(+)

diff -Nru semi-1.14.7~0.20120428/debian/changelog 
semi-1.14.7~0.20120428/debian/changelog
--- semi-1.14.7~0.20120428/debian/changelog 2014-10-26 09:55:50.0 
+0900
+++ semi-1.14.7~0.20120428/debian/changelog 2015-05-08 09:10:00.0 
+0900
@@ -1,3 +1,10 @@
+semi (1.14.7~0.20120428-14+deb8u1) jessie; urgency=medium
+
+  * New patch 020_encrypt.patch to fix incorrect keys in encryption
+(closes: #784712)
+
+ -- Tatsuya Kinoshita   Fri, 08 May 2015 09:09:01 +0900
+
 semi (1.14.7~0.20120428-14) unstable; urgency=medium
 
   * Sync 010_semi-epg.patch from wanderlust on 2014-10-25
diff -Nru semi-1.14.7~0.20120428/debian/patches/020_encrypt.patch 
semi-1.14.7~0.20120428/debian/patches/020_encrypt.patch
--- semi-1.14.7~0.20120428/debian/patches/020_encrypt.patch 1970-01-01 
09:00:00.0 +0900
+++ semi-1.14.7~0.20120428/debian/patches/020_encrypt.patch 2015-05-08 
09:06:24.0 +0900
@@ -0,0 +1,114 @@
+Subject: Fix incorrect keys in encryption
+Origin: 
https://github.com/wanderlust/semi/commit/da44c8e0ea6baf5dac2b8debf86f720a541f31a5
+Bug: https://github.com/wanderlust/semi/issues/9
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784712
+
+diff --git a/mime-edit.el b/mime-edit.el
+index af64dc8..e7f2ea9 100644
+--- a/mime-edit.el
 b/mime-edit.el
+@@ -,6 +,7 @@ USAGE is a symbol denoting the intended usage."
+(std11-field-body "From" mail-header-separator))
+  ""
+   keys default-keys)
++(setq signer (and signer (concat "<" signer ">")))
+ (if mime-edit-pgp-verbose
+   (epa-select-keys
+context
+@@ -2375,23 +2376,34 @@ If no one is selected, symmetric encryption will be 
performed.  ")
+ (defvar mime-edit-encrypt-recipient-fields-list '("From" "To" "cc"))
+ 
+ (defun mime-edit-make-encrypt-recipient-header ()
+-  (let* ((names mime-edit-encrypt-recipient-fields-list)
+-   (values (std11-field-bodies names nil mail-header-separator))
+-   (from (car values))
+-   header recipients)
+-(while (and names values)
+-  (let ((name (car names))
+-  (value (car values)))
+-  (when (and (stringp value) (null (string-equal value "")))
+-(setq header (concat header (format "%s: %s\n" name value)))
+-(when (or mime-edit-pgp-encrypt-to-self
+-  (null (string-equal name "From")))
+-  (setq recipients (cons value recipients)
+-  (setq names (cdr names)
+-  values (cdr values))
+-  )
+-(setq recipients (mapconcat 'eval recipients " ,"))
+-(vector from recipients header)
++  (let ((field-names (mapcar 'downcase
++   mime-edit-encrypt-recipient-fields-list))
++  header recipients name value)
++(save-excursion
++  (save-restriction
++  (std11-narrow-to-header mail-header-separator)
++  (goto-char (point-min))
++  (while (re-search-forward
++  (concat "^\\(" std11-field-name-regexp "\\):[ \t]*") nil t)
++(when (member (downcase (match-string 1)) field-names)
++  (setq name (buffer-substring-no-properties
++  (match-beginning 1) (match-end 1))
++value (buffer-substring-no-properties
++   (match-end 0) (std11-field-end)))
++  (when (and (stringp value) (null (string-equal value "")))
++(setq header (cons (format "%s: %s\n" name value) header))
++(when (or mime-edit-pgp-encrypt-to-self
++  (null (string-equal (downcase name) "from")))
++  (setq recipients (cons (mapcar
++  'std11-address-string
++  (std11-parse-addresses-string value))
++ recipients
++(cons (apply #'nconc
++   (mapcar (lambda (recipient)
++ (or (epg-expand-group config recipient)
++ (list (concat "<" recipient ">"
++   (apply #'nconc recipients)))
++(apply #'concat (nreverse header)))
+ ))
+ 
+ (defun mime-edit-encrypt-pgp-mime 

Bug#784713: samba-common: legacy config file /etc/samba/dhcp.conf

[Christoph Anton Mitterer]

Package: samba-common
Version: 2:4.1.17+dfsg-4
Severity: normal


Hi.

Apparently until some versions the file /etc/samba/dhcp.conf was part of the
package or created by it... however it seems to be no longer shipped/created
with/by it nowadays.

OTOH it wasn't deleted and is now leftover empty.

To keep systems more consistent and get rid of legacy files, please
please remove empty versions of it properly with one of the next package 
versions.

Thanks,
Chris.


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

Bug#784273: cc1111: incompletely-disabled warning message 18

[Bdale Garbee]

Eric Cooper  writes:

> Why does the __code storage class affect it?

Neither Keith nor I have any idea.  Have you tried the same code with
current SDCC to see if things perhaps work better there?

Bdale



signature.asc
Description: PGP signature

Bug#784180: closed by gregor herrmann (Bug#784179: fixed in libnet-ldap-perl 1:0.6500+dfsg-1)

[gregor herrmann]

On Thu, 07 May 2015 22:12:49 +0200, Christian wrote:

> Thanks a lot for the quick fix! I can confirm that this fixes the issue.

It was a nice coincidence to have a new upstream release which fixes
this bug :)
Thanks for confirming that the problem is actually gone.

Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#784712: semi: incorrect keys in encryption

[Tatsuya Kinoshita]

Package: semi
Version: 1.14.7~0.20120428-14
Severity: important
Tags: jessie security

It was discovered that SEMI, an Emacs library to provide MIME
features, did not properly implement recipients matching to encrypt
mails.  This may allow unrelated person may decrypt the mails.

cf.
  - http://thread.gmane.org/gmane.mail.wanderlust.general.japanese/9819
From: Michael Welle
> I discovered strange behaviour while trying to encrypt mails (Emacs
> 24.4.1, SEMI is the current version from the melpa archive). The key
> ids that are fed to gpg are mostly totally unrelated to the mail's
> recipient. The problem seems to be in mime-edit.el. In
> mime-edit-encrypt-pgp-mime a recipient list is calculated. A to-header
> like 'foo bar ' is therefore parsed into three elements 'foo',
> 'bar' and 'foo@a.b', which results in three key ids (depending on the
> contents of your key ring). Unfortunately, the key ids resulting from
> 'foo' and 'bar' are unrelated to this mail in my case (tons of
> different keys can be found for foo). And even the key found for
> foo@a.b might not be the one one want to use.
>
> As a work around one can use plain mail addresses like 'foo@a.b'.
Fixed in 
https://github.com/wanderlust/semi/commit/9976269556c5bcc021e4edf1b0e1accd39929528

  - https://github.com/wanderlust/semi/issues/9
From: Tatsuya Kinoshita
> With SEMI-EPG 2015-05-03 and Wanderlust 2015-03-08, in encryption,
> a mail with To: m...@debian.org chooses d...@debian.org's key when
> the foolowing keys are imported.
>
>   - 1024D/97AA33D6 Dima Barsky 
>   - 1024D/1A944AD7 Martin Albert 
>
> It seems not exact match on an email address.
Fixed in
  - 
https://github.com/wanderlust/semi/commit/5c8466321d281d72850c298b9ebcd466b4b0160c
  - 
https://github.com/wanderlust/semi/commit/da44c8e0ea6baf5dac2b8debf86f720a541f31a5

The security team suggested that is rather a candidate for a fix in
a point update instead of a Debian Security Advisory.

Thanks,
--
Tatsuya Kinoshita


pgpOoasjw1XnB.pgp
Description: PGP signature

Bug#784310: apt update always fails on experimental/non-free

[Cesare Leonardi]

On 05/05/2015 14:58, Axel Beckert wrote:

I though currently can't reproduce it on i386.


I was almost sure that i got the error on a i386 PC of mine but since i 
haven't really tried for some time, the doubt started to arise and since 
your reply i've run some tests.
I confirm what Axel said: the error doesn't show under i386. And i've 
verified also on another i386 PCs (up to date Sid).


Then i've verified with two KVM virtual machine, both with updated Sid, 
same sources.list, but one i386 and one amd64: i can see the error only 
on amd64.


To be honest, now, while writing this mail, on the first i386 PC tested, 
i get error on experimental/main, but only using httpredir in 
sources.list and only in the first run after changing mirror. Don't know 
what to think...


Cesare.


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

Bug#784711: libwraster-dev: Fails to install due to file conflict with libwraster3-dev

[Axel Beckert]

Package: libwraster-dev
Severity: serious
Version: 0.95.6-1

Dear Maintainer,

installing libwraster-dev fails, if libwraster3-dev is still installed
as they share files with the same file name and path:

Unpacking libwraster-dev (0.95.6-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libwraster-dev_0.95.6-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/libwraster.a', which is also in package 
libwraster3-dev 0.95.5-2+b2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libwraster-dev_0.95.6-1_amd64.deb

libwraster-dev needs according Breaks and Replaces header.

Additional the "Provides: libwraster-dev" in libwraster-dev seems
useless. It's probably a leftover from libwraster3-dev where it made
sense.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), 
(111, 'buildd-experimental'), (110, 'experimental')
Architecture: amd64 (x86_64)

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


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

Bug#784405: ITP: rnetclient -- Client to submit the Brazilian Income Tax Report to the Brazilian Tax Authority

[Thadeu Lima de Souza Cascardo]

Let me add here some of the history about rnetclient and IRPF Livre,
concerning legal and government matters.

As already said, Oliva has been publishing IRPF Livre for a while. He
decompiled that software when it was using GPL libraries, which would
make it GPL software, even though SERPRO or Receita didn't distribute it
on the same terms. That could be interpreted as a legal liability, but
he has not found any problems since then. Here is what has happened
instead.

As Sergio also pointed out, Oliva has gone through the process of trying
to get the software released, claiming that recent law for transparency
meant the government needed to publish it. SERPRO, who is the developer
of the software, claimed there was secrets in the software that would
allow people's income to be leaked. That is a lie! As Oliva pointed out
in his counter-claim, his own IRPF Livre would allow such a leak if that
was true. And that would be a huge security breach in the whole
process of tax paying/refund. Unfortunately, the judge decided against
the publishing of the software. But Oliva stated that he has done the
reverse engineering, publishes the software, and no action against him
has been taken.

When I was developing rnetclient, I found some concerning problems in
its trust model (software trusts certificate that is shipped with
itself, certificate has a weak password, easily found on the software,
even software hashing checking can be easily circumvented, software is
not distributed with any signature - not even over https). I thought
that publishing that would put me into trouble. I gave a talk on a big
event in Brasil (FISL, >5k people, 300 watched the talk live, video was
published, SERPRO president was at FISL), and no action has been taken
against me. Oliva and I even talked to SERPRO president at the time, he
couldn't care less, or even seemed favorable to what we were doing.

I have been shipping rnetclient since then, 2013. This year I even
managed to have it updated at the same day that Receita has published
its own software (they didn't do Betas this year). The fix came the next
day. I have an intention to publish a version that should work for years
to come, until the protocol breaks from what it has been for the last 5
years. And, in fact, it's still useful to submit corrections to previous
years files. So, if you have to publish 2013 and 2014 again for any
reason, 2015.1 can be used. And the software will still be useful for at
least the next 5 years, when people might still want to resubmit their
2015 files. Unless Receita breaks the whole thing, as I mentioned, but
hasn't done for at least the last 5 years.

About my own process of reverse engineering: I did some decompiling and
read some of the code. I wrote a very small Java class to override the
certificate verification, allowing me to do some MITM. Most of the
process after that involved me writing tests to simulate a server and a
client, and see how the client and server responded. Reading the code
just helped me get the basics on the encoding so I could write the
tests. After that, I wrote the program from scratch. Even though it was
not completely clean room, it's hard to conceive there was any copy of
SERPRO's code. Their code is in Java, with its own APIs, I used C, with
GNUTLS, BSD sockets, zlib, my own decoding of the file that came after I
started writing the tests (so I didn't read any code related to that).

Also, Brazilian law says:

" Art. 6º Não constituem ofensa aos direitos do titular de programa de
computador:

[...]

III - a ocorrência de semelhança de programa a outro, preexistente,
quando se der por força das características funcionais de sua aplicação,
da observância de preceitos normativos e técnicos, ou de limitação de
forma alternativa para a sua expressão; "

Which means that it's not a copyright infringement when a program is
similar to a preexisting one because of its functional
characteristics, or because it follows technical or normative
references, or there is a limitation for other forms of expression.

Hope that helps moving the discussion forward. I, at least, found it
delightful to write this for posterity.

Cascardo.


signature.asc
Description: Digital signature

Bug#784405: ITP: rnetclient -- Client to submit the Brazilian Income Tax Report to the Brazilian Tax Authority

[Henrique de Moraes Holschuh]

On Thu, May 7, 2015, at 19:23, Sergio Durigan Junior wrote:
> On Thursday, May 07 2015, Frederic Peters wrote:
> >> Also, ReceitaNet is often updated, it went from version 4 (tax report of
...
> >> This can cause operational issues if rnetclient makes it to Debian
> >> stable, since the program must be working perfectly during the tax
> >> submission window.
...
> > This makes it an appropriate candidate for jessie-updates.
> 
> That is actually a pretty good solution!  I am still learning the terms
> and the whole process here, but jessie-updates, according to:
> 
>   
>   (thanks to Cascardo for providing the link)
> 
> would indeed be the ideal place for rnetclient, according to this
> criterion:
> 
>   - Packages that need to be current to be useful (e.g. clamav).

I am well versed with stable-updates, I upload to it several times per
year due to intel-microcode.  Unless there is previous arrangement with
the stable release managers, an upload to stable-proposed-updates it is
not always going to be fast enough for this.  "keep current" doesn't
mean "rush into stable every time", after all.

IMHO, it would be far better to have someone maintain the debian
packaging of this stuff upstream, in a "apt-gettable" repository that
can be added to sources.list.  Such a repository, although unofficial,
could be both Debian and Ubuntu-friendly, and target also the LTS
branches of Debian and Ubuntu.  This side-steps all the issues I raised.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique de Moraes Holschuh 


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

Bug#784515: [qlandkartegt] Qt4's WebKit removal

[Lisandro Damián Nicanor Pérez Meyer]

On Wednesday 06 May 2015 15:45:27 Sebastiaan Couwenberg wrote:
> Hi Ana,
> 
> Thanks for your work on Qt.
> 
> > As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
> > as announced in [announce].
> > 
> > [announce]
> > 
> 
> I'm very much aware of this, and starting the switch to the Qt5 port for
> the qlandkartegt package. See the discussion on the debian-gis list:
> 
> https://lists.debian.org/debian-gis/2015/05/msg7.html
> 
> The first revision is available in experimental, but it fails to build on
> armel & armhf due to an OpenGL issue that the other architectures don't
> suffer from.
> 
> I've haven't had the time to reproduce the issue on a porterbox, hopefully
> it specific to the package mix in experimental and doesn't affect
> unstable, so we can get the Qt5 port of qlandkartegt in unstable soon.

Hi Bas! I checked the code and the problem is that GLU () is not 
supported/does not supports OpenGL ES, which is the native OpenGL mode on 
those two archs.

In this case let me recommend you to limit qlandkartegt to build on !armel 
!armhf and ask for the binaries to be removed on those archs when you push the 
package to unstable.

Of course a much better solution is to port the code away from Glu, but that 
requires more manpower :-/ . On the other hand porting the code means it will 
be possible to run it on quite more embedded devices in a native (non software 
emulated) way.

Kinds regards, Lisandro.

-- 
http://www.phdcomics.com/comics/archive.php?comicid=56

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


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

Bug#784710: ITP: python-shade -- Client library for operating OpenStack clouds

[Clint Byrum]

Package: wnpp
Severity: wishlist
Owner: Clint Byrum 

* Package name: python-shade
  Version : 0.6.0
  Upstream Author : Various (See AUTHORS)
* URL : https://pypi.python.org/pypi/shade
* License : Apache-2
  Programming Lang: Python
  Description : Client library for operating OpenStack clouds

 Shade is a simple Python client library for operating OpenStack
 clouds. The key word here is simple. Clouds can do many many many
 things - but there are probably only about 10 of them that most people
 care about with any regularity. If you want to do complicated things,
 you should probably use the lower level client libraries - or even the
 REST API directly. However, if what you want is to be able to write an
 application that talks to clouds no matter what choices the deployer
 has made then shade is for you.


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

Bug#784243: [Pkg-ime-devel] ITP: fcitx-kkc -- Fcitx wrapper for libkkc IM engine

[Aron Xu]

On Thu, May 7, 2015 at 11:51 PM, Mitsuya Shibata  wrote:
> Hi Aron,
>
> 2015-05-07 5:20 GMT+09:00 Aron Xu :
>>> fcitx-kkc is packaged by git-buildpackage. If repmote repository created,
>>> I will push to it.
>>>
>>
>> You need to join pkg-ime team on alioth first. Please request and
>> we'll approve it.
>
> Thank you for your clarification.
> I already joined pkg-ime. Could you create fcitx-kkc repository?
>
> https://alioth.debian.org/users/shibata-guest/
>
> FYI, I pushed the working tree to Launchpad.
> https://git.launchpad.net/~cosmos-door/+git/fcitx-kkc
>

Created empty repository:
https://anonscm.debian.org/gitweb/?p=pkg-ime/fcitx-kkc.git

Access by:
git clone ssh://git.debian.org/git/pkg-ime/fcitx-kkc.git

Thanks,
Aron


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

Bug#781566: COPYING2 contains some armchair licensing

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi There !

Still waiting for the official release.

Thanks,
Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJVS+sOAAoJEIC/w4IMSybjf78IAJ359/cFFieg7SvJktgrwBGO
4w8rmDEyLhNK/tq8kOvJ1IlJOwpyJ0HIEXdpJ7FwvLu0dgOrxs/Wiv+VNdqgbiU4
R2xE9BEpUhUwHjOly7DBRihU0MxQIvmijISZ3+JxMJT0MiI4K8r1xiH9Upz6y4C6
DGvT6HpYg6/T4bI2Asa4fGyD1mOdp4QabM/C1aJmUOYe0WD3pi2lVgyiPb86IWmu
WhO/5R2dzsSI1AyhS8cjrIqHu2pwL5mpTklGsie+EvYGBHniFRfwc4c0NmtnVMQk
sDLOoF+MH/KAZvOLulwo52IY+wtJJsaaVCt9YLv1uYNWubXOEDoEZSAk/XxvTTc=
=uC8K
-END PGP SIGNATURE-


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

Bug#784405: ITP: rnetclient -- Client to submit the Brazilian Income Tax Report to the Brazilian Tax Authority

[Sergio Durigan Junior]

On Thursday, May 07 2015, Frederic Peters wrote:

>> What's the real point of this package?  One actually needs to install
>> the tax-report-building program from RFB (IRPF20xx) to have anything for
>> rnetclient to transmit, at which point you might as well install
>> ReceitaNet since you're already running RFB-provided java code anyway.
>
> It looks like the initial part wouldn't require network access; this
> would be quite an important difference.

I'm not sure I understood the sentence, but yeah, the program used to
prepare the tax report indeed does not need network access.

>> Regardless of whether the process of reverse engineering the ReceitaNet
>> protocol is legal or not (I don't know, so I am not assuming anything),
>> actually connecting to RFB servers using this program might well not be
>> legal.
>
> I don't know anything about Brazilian reverse engineering, or others,
> laws, and what would apply here.  But I wouldn't stop at "regardless
> it is legal or not" and "might not well be legal" without any details.

Thanks, that's my feeling as well.  And that's why those programs were
developed.  But as I said in my reply to Henrique, reverse engineering
is not against the Brazilian copyright law.

>> Also, ReceitaNet is often updated, it went from version 4 (tax report of
>> 2014) to version 7 (tax report of 2015), rnetclient would have to be
>> kept up-to-date if such changes in ReceitaNet are in any way related to
>> the protocol or servers it should connect to submit the tax report. 
>> This can cause operational issues if rnetclient makes it to Debian
>> stable, since the program must be working perfectly during the tax
>> submission window.
>> 
>> In fact, the upstream homepage has this notice (loosely translated from
>> pt_BR):
>> "Version 2015.0 did not support fully the tax report format for 2015.
>> This problem has been fixed in version 2015.1. We wait reports of both
>> sucessful and non-sucessful use of rnetclient 2015.1 in our mailing
>> list".
>
> This makes it an appropriate candidate for jessie-updates.

That is actually a pretty good solution!  I am still learning the terms
and the whole process here, but jessie-updates, according to:

  
  (thanks to Cascardo for providing the link)

would indeed be the ideal place for rnetclient, according to this
criterion:

  - Packages that need to be current to be useful (e.g. clamav).

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


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

Bug#707843: Gbirthday demands python-evolution

[Jérôme]

Evolution support was dropped from version 0.6.8.

-- 
Jérôme


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

Bug#784405: ITP: rnetclient -- Client to submit the Brazilian Income Tax Report to the Brazilian Tax Authority

[Frederic Peters]

Hi,

Henrique de Moraes Holschuh wrote:

> What's the real point of this package?  One actually needs to install
> the tax-report-building program from RFB (IRPF20xx) to have anything for
> rnetclient to transmit, at which point you might as well install
> ReceitaNet since you're already running RFB-provided java code anyway.

It looks like the initial part wouldn't require network access; this
would be quite an important difference.


> Regardless of whether the process of reverse engineering the ReceitaNet
> protocol is legal or not (I don't know, so I am not assuming anything),
> actually connecting to RFB servers using this program might well not be
> legal.

I don't know anything about Brazilian reverse engineering, or others,
laws, and what would apply here.  But I wouldn't stop at "regardless
it is legal or not" and "might not well be legal" without any details.


> Not to mention it can cause "harm" to rnetclient users if RFB decides
> that they object to tax reports submited through rnetclient, and we

This is GPL, "This program comes with ABSOLUTELY NO WARRANTY", of
course the user should be informed.


> might find ourselves in legal trouble over that as well, there's the
> whole "enticing others to use the rnetclient program" angle that could
> be played against Debian (in this case, it might well end up being
> directed at Brazillian DDs since RFB won't be able to target SPI or
> Debian itself).

We noted above there's no indication of an actual legal problem; so
again, "might", just like it's the case for many other programs (for a
common example, running a bittorrent client might not be legal in
$country).


> Also, ReceitaNet is often updated, it went from version 4 (tax report of
> 2014) to version 7 (tax report of 2015), rnetclient would have to be
> kept up-to-date if such changes in ReceitaNet are in any way related to
> the protocol or servers it should connect to submit the tax report. 
> This can cause operational issues if rnetclient makes it to Debian
> stable, since the program must be working perfectly during the tax
> submission window.
> 
> In fact, the upstream homepage has this notice (loosely translated from
> pt_BR):
> "Version 2015.0 did not support fully the tax report format for 2015.
> This problem has been fixed in version 2015.1. We wait reports of both
> sucessful and non-sucessful use of rnetclient 2015.1 in our mailing
> list".

This makes it an appropriate candidate for jessie-updates.


Fred


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

Bug#784709: os-prober prevent the upgrade to jessie

[Jerome Kieffer]

Package: os-prober
Version: 1.65
Severity: critical
Tags: newcomer
Justification: breaks the whole system

Dear Maintainer,

During the upgrade (apt-get dist-upgrade) of a computer from debian7 (Wheezy)
to Debian8 (Jessie) the system still runs the kernel 3.2 from Wheezy; but the
os-prober version used by update-grub is already the one from Jessie... and
hang.
According to:
https://lists.debian.org/debian-boot/2013/05/msg00077.html
(and related bugs at maegia), the new os-prober (from Jessie) is unable to scan
a hard-drive containing Extended partitions (like sdb4 hereafter) and locks
forever (at least 90mn), locking the debian system in the middle of a dist-
upgrade.

Disque /dev/sdb : 1,8 TiB, 2000398934016 octets, 3907029168 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x9a2578f7

Device Boot  StartEndSectors  Size Id Type
/dev/sdb1   63   33575849   33575787   16G 82 Linux swap / Solaris
/dev/sdb2 33575850  243304424  209728575  100G 83 Linux
/dev/sdb3243304425  453032999  209728575  100G 83 Linux
/dev/sdb4453033000 3907024064 3453991065  1,6T  5 Extended
/dev/sdb5453033063  557905319  104872257   50G 83 Linux
/dev/sdb6557905383  662777639  104872257   50G 83 Linux
/dev/sdb766203  767649959  104872257   50G 83 Linux
/dev/sdb8767650023  872522279  104872257   50G 83 Linux
/dev/sdb9872522343 1082250854  209728512  100G 83 Linux
/dev/sdb10  1082250918 3907024064 2824773147  1,3T 83 Linux

The system was fully occupied by a "mount" process trying to mount /dev/sdb4.
This process was uninteruptable (kill -9 being ineffective) and forced to
reboot exactly at the stage grub was updating.

The only solution found was to boot an external device with a rescue system and
a recent kernel (3.16) to finish the dist-upgrade. One solution may have been
to upgrade first the kernel via wheezy-backports packages before upgrading to
Jessie.

Best regards,

Jerome Kieffer



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

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

Versions of packages os-prober depends on:
ii  libc6  2.19-18

os-prober recommends no packages.

os-prober 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#784708: Only seeing configure iSCSI when installing Jessie. Weezy is fine, can select guided.

[Miles Gargaritano]

Package: installation-reports

Boot method: CD and Network (PXE)
Image version: 
http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-cd/debian-8.0.0-amd64-netinst.iso
Date: 5:00PM 07/05/2015

Machine: Dell Vostro 980
Processor:
Memory:
Partitions: Wiped - no partitions

Output of lspci -knn (or lspci -nn):

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:  [O]
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives:  [E]
Install base system:[E]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [E]
Install boot loader:[E]
Overall install:[E]

Comments/Problems:

When I get to the Partition Disks menu, I only have 1 option -
Configure iSCSI. Did a fdisk -l to view my disks and it saw my Maxtor
HD. I tried this on a different work station, same thing. Tried this
with a different ISO, same thing still wanted me to configure iSCSI. I
checked my BIOS and my HDD was listed on both workstations. I did this
for Network boot and Offline. I also changed the SATA configs went
from IDE, RAID, AHCI. NOTE: When installing Wheezy, I found my HDDs
and was able to select guided! Same HDD, Same Workstation.


-- 
*Miles Gargaritano*
*IT Analyst*

*T: *416-900-3830 ext. 2002
*E**: *miles.gargarit...@uberflip.com
*W:* uberflip.com

Bug#784342: jessie-pu: package openstack-debian-images/1.3

[Adam D. Barratt]

On Thu, 2015-05-07 at 00:01 +0200, Thomas Goirand wrote:
> On 05/05/2015 08:20 PM, Adam D. Barratt wrote:
> > I do have one pre-emptive question, having looked at the 1.2 -> 1.3 diff
> > in unstable:
> >
> >   contrib/official-debian-image-hook|   28 
> > --
> >   contrib/official-debian-openstack-image/README|6
> >   contrib/official-debian-openstack-image/debian-cd-pettersson-live |  107 
> > ++
> >   contrib/official-debian-openstack-image/openstack-hook|   28 
> > ++
> >
> > Which of the changelog entries covers the above changes?
> 
> I kind of consider this as the documentation of the package (it's 
> installed in /usr/share/doc/openstack-debian-images/contrib), so I 
> didn't care about documenting it in the changelog. Do you think I should 
> fix this?

I'd personally still expect it to be mentioned in the changelog (along
with e.g. changes to README.source, README.Debian and so on).

Regards,

Adam


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

Bug#784342: jessie-pu: package openstack-debian-images/1.3

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Thu, 2015-05-07 at 01:20 +0200, Thomas Goirand wrote:
> I have generated a new 1.3~deb8u1 version as suggested, and attached the 
> debdiff to this bug.

--- openstack-debian-images-1.2/debian/changelog2015-01-28 
13:48:30.0 +0100
+++ openstack-debian-images-1.3~deb8u1/debian/changelog 2015-05-07 
00:06:47.0 +0200
@@ -1,3 +1,18 @@
+openstack-debian-images (1.3~deb8u1) jessie-proposed-updates; urgency=medium
+
+  * Backport of the version 1.3 from Sid to Jessie.
+  * Fixed debian/gbp.conf to use debian/jessie as new packaging branch.
+  * Removed the tweak of /etc/modules, as acpiphp and pci_hotplug aren't in the
+Jessie kernel: they are built not as module (Closes: #783340).
+  * Also adds security repository if building an image for Jessie. Previously,
+this was done only for Wheezy (Closes: #783480).
+  * Adds dbus + libpam-systemd when building a Jessie image, and acpid +
+acpi-support-base when building a Wheezy image, so that ACPI shutdown works
+by default (Closes: #783448).
+  * Adds nano as default when not using the --minimal flag (Closes: #783341).
+
+ -- Thomas Goirand   Thu, 07 May 2015 00:03:47 +0200
+
 openstack-debian-images (1.2) unstable; urgency=medium

Generally one would take the 1.3 package, add a changelog entry and
rebuilt that in jessie. So most of the above would be in the 1.3 stanza
as it is in unstable, with the 1.3~deb8u1 stanza simply containing the
reference to rebuilding for jessie.

In any case, please go ahead.

Regards,

Adam


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

Bug#784682: systemd unable to boot when snoopy is enabled

[Michael Biebl]

Control: reassign -1 snoppy

Am 07.05.2015 um 23:36 schrieb Michael Biebl:
> Control: reassign -1 snappy
> Control: severity -1 serious
> Control: affects -1 systemd
> Control: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=948417
> 
> Am 07.05.2015 um 19:38 schrieb Stefan Schmidt:
>> Package: systemd
>> Version: 215-17
>>
>> I just came across an issue with journald being unable to start up when
>> snoopy is enabled that prevents a Jessie/systemd installation to boot up
>> which i reported to upstream at
>> https://bugs.freedesktop.org/show_bug.cgi?id=90364 .
>>
>> This is to let you know about the issue. Maybe we need to stick a
>> warning label somewhere. ;-)
>>
> 
> 
> I'm going to re-assign this to snappy. This looks to me like something
> which needs to be addressed in the snappy package.
> 

Grr, snoopy, of course...


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



signature.asc
Description: OpenPGP digital signature

Bug#784644: jessie-pu: package freeorion/0.4.4-2+b1

[Adam D. Barratt]

Control: tags -1 + pending

On Thu, 2015-05-07 at 14:24 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On 2015-05-07 13:30, Markus Koschany wrote:
> > it was reported that FreeOrion FTBFS in Jessie, apparently due to 
> > changes
> > in the freetype library. This is Debian bug
> > 
> > https://bugs.debian.org/783839
> > 
> > I have prepared a fix for this issue and would like to fix it an
> > upcoming point release for Jessie.
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam


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

Bug#784405: ITP: rnetclient -- Client to submit the Brazilian Income Tax Report to the Brazilian Tax Authority

[Sergio Durigan Junior]

[ Cc'ing Thadeu Cascardo, who developed rnetclient and is a DD. ]

On Thursday, May 07 2015, Henrique de Moraes Holschuh wrote:

> On Wed, May 6, 2015, at 01:51, Sergio Durigan Junior wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Sergio Durigan Junior 
>> 
>> * Package name: rnetclient
>>   Version : 2015.1
>>   Upstream author : Thadeu Cascardo, Sergio Durigan Junior, Alexandre Oliva
>> * URL : http://wiki.libreplanetbr.org/rnetclient/
>> * License : GPLv3+
>>   Programming Lang: C
>>   Description : A Client to submit the Brazilian Income Tax Report
>> to the Brazilian Tax Authority
>> 
>> rnetclient is a Free Software that can be used to submit the Brazilian
>> Income Tax Report to the Brazilian Tax Authority (Receita Federal).  It
>> is the outcome of reverse-engineering ReceitaNet, the official and
>> proprietary software that Receita Federal develops.
>
> What's the real point of this package?  One actually needs to install
> the tax-report-building program from RFB (IRPF20xx) to have anything for
> rnetclient to transmit, at which point you might as well install
> ReceitaNet since you're already running RFB-provided java code anyway.

Hey, Henrique!

Thanks for the comments.

The real point of this package is to provide freedom for those who have
to declare their income tax in Brazil.  Of course, as you have
mentioned, rnetclient solves one side of the equation, which is
sending the report to the Receita Federal.  As for the other side (which
is preparing the report), you do not necessarily have to install the
proprietary version of the program that is published by the Receita
Federal; instead, you can install IRPF-Livre, a Free Software made by
Alexandre Oliva (since 2007):

  

Every year, he releases a new code to be tested.  The reports generated
by IRPF-Livre can be successfully transmited by rnetclient, as has been
tested by Alexandre Oliva and others.  Unfortunately, IRPF-Livre is not
a Debian package (yet?), but then again, the proprietary version is
obviously not on Debian either.

> Also, what's the official position of RFB regarding the existence, and
> use of this program?

There is no official position about both programs so far, to the extent
of my knowledge.  What exists (or existed; I don't remember all the
details now) is a lawsuit by Alexandre Oliva who has been trying to make
RFB release the code of the proprietary softwares mentioned above.  But
this is offtopic to this discussion, I think.

> Regardless of whether the process of reverse engineering the ReceitaNet
> protocol is legal or not (I don't know, so I am not assuming anything),

IANAL, but in general reverse engineering is not forbidden in Brazil.  I
found some documents about this, and I can provide them if needed.

> actually connecting to RFB servers using this program might well not be
> legal.
>
> Not to mention it can cause "harm" to rnetclient users if RFB decides
> that they object to tax reports submited through rnetclient, and we
> might find ourselves in legal trouble over that as well, there's the
> whole "enticing others to use the rnetclient program" angle that could
> be played against Debian (in this case, it might well end up being
> directed at Brazillian DDs since RFB won't be able to target SPI or
> Debian itself).

That is indeed a good point; I don't know if Debian as a project is
willing to take this risk.  I mean, there is always a risk of RFB
deciding that they won't accept tax reports made by IRPF-Livre and/or
submitted by rnetclient; in this case, we would have to think in another
option.  As I said, Alexandre Oliva has been doing IRPF-Livre since
2007, and last year some people used rnetclient to submit their reports,
and nothing unusual happened.  I think it is not very...  "dangerous" (I
did not want to use that word, but...) for Debian to have rnetclient on
its repositories, but that is a personal opinion of someone who is
starting to contribute to Debian.

> Also, ReceitaNet is often updated, it went from version 4 (tax report of
> 2014) to version 7 (tax report of 2015), rnetclient would have to be
> kept up-to-date if such changes in ReceitaNet are in any way related to
> the protocol or servers it should connect to submit the tax report. 
> This can cause operational issues if rnetclient makes it to Debian
> stable, since the program must be working perfectly during the tax
> submission window.

Yes, that is another good point.  I don't know what would be the best
way to solve this.  I know rnetclient in stable would probably not be
updated as frequent as it should.

> In fact, the upstream homepage has this notice (loosely translated from
> pt_BR):
> "Version 2015.0 did not support fully the tax report format for 2015.
> This problem has been fixed in version 2015.1. We wait reports of both
> sucessful and non-sucessful use of rnetclient 2015.1 in our mailing
> list".

Yes, but I don

Bug#784682: systemd unable to boot when snoopy is enabled

[Michael Biebl]

Control: reassign -1 snappy
Control: severity -1 serious
Control: affects -1 systemd
Control: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=948417

Am 07.05.2015 um 19:38 schrieb Stefan Schmidt:
> Package: systemd
> Version: 215-17
> 
> I just came across an issue with journald being unable to start up when
> snoopy is enabled that prevents a Jessie/systemd installation to boot up
> which i reported to upstream at
> https://bugs.freedesktop.org/show_bug.cgi?id=90364 .
> 
> This is to let you know about the issue. Maybe we need to stick a
> warning label somewhere. ;-)
> 


I'm going to re-assign this to snappy. This looks to me like something
which needs to be addressed in the snappy package.


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



signature.asc
Description: OpenPGP digital signature

Bug#784707: seahorse: Generic error when attempting to add additional name to PGP Keys

[Michael Leer]

Package: seahorse
Version: 3.14.0-2
Severity: normal

Dear Maintainer,


* What led up to the situation?
Attempted to add an additional email to my existing PGP key

* What exactly did you do (or not do) that was effective (or ineffective)?
Open seahorse
Select GnuPG keys
Right Click the key and select Properties
Select Names and Signatures
Click Add Name
Enter details
i.e
===
Full Name: example
E-mail Address: exam...@example.com
Key Comment: This is an example
===
Click OK

* What was the outcome of this action?
Couldn't add user id
General error

* What outcome did you expect instead?
Additional email to be added.



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

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

Versions of packages seahorse depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gcr  3.14.0-2
ii  gnome-keyring3.14.0-1+b1
ii  gnupg1.4.18-7
ii  libassuan0   2.1.2-2
ii  libatk1.0-0  2.14.0-1
ii  libavahi-client3 0.6.31-5
ii  libavahi-common3 0.6.31-5
ii  libavahi-glib1   0.6.31-5
ii  libc62.19-18
ii  libcairo-gobject21.14.0-2.1
ii  libcairo21.14.0-2.1
ii  libgck-1-0   3.14.0-2
ii  libgcr-base-3-1  3.14.0-2
ii  libgcr-ui-3-13.14.0-2
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgpg-error01.17-3
ii  libgpgme11   1.5.1-6
ii  libgtk-3-0   3.14.5-1
ii  libldap-2.4-22.4.40+dfsg-1
ii  libp11-kit0  0.20.7-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libsecret-1-00.18-1+b1
ii  libsoup2.4-1 2.48.0-1

Versions of packages seahorse recommends:
ii  openssh-client  1:6.7p1-5

seahorse 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#784706: RM: squid-prefetch -- RoQA; obsolete, orphaned, depends on squid 2

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove squid-prefetch. It depends on squid 2, which is
scheduled for removal. The last maintainer upload was in 2006
and it's orphaned.

Cheers,
Moritz


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

Bug#784166: widelands: Game crashes on song change

[Bernhard Übelacker]

Hello Alex,


One last question: did you try to install the amd64 version specifically?
I'm not sure how the multi-arch support works these days. If not, would it
be easy for you to try to do it?

Yes, my tests were done on my regular amd64 desktop installation.
That was with widelands_18-3+b1_amd64.deb.



Thank you for taking the time to look into the issue! I wish I could
downgrade the libboost packages needed to compile the source code to see if
the build would have the bug or not. They are not in the dependencies but
are on the build-deps: https://packages.debian.org/source/jessie/widelands

I am actually running Squeeze with some packages from Stretch.

I did a manual build from the source code and the game runs fine, with
these exact packages you listed for me. I am still suspecting the problem
to be libboost (check the bug report I mentioned earlier for why) even
though I can't be sure. I guess I should probably close the bug if we
cannot reproduce it, since it could be due to my weird package mix?


For the fun of it I tried to really reproduce the situation (qemu-VM):
- installed Squeeze LTS with LXDE
- added Stretch sources.list

But I was not able to cleanly install widelands via apt.
Trying to manually installing via dpkg led also to some (for me) 
unresolvable dependencies (without doing nearly half of the dist-upgrade).
Therefore I am short before thinking that now your package system is in 
an inconsistent state.



> Unfortunately I got myself into a sort of a deadlock with that and
> need to reinstall the system from scratch.

As I think you also did a libc-upgrade (2.11.3-4+deb6u5 to 2.19-18 ?)
I cannot say how a downgrade of it has to be done.
Probably a dist-upgrade to Jessie or Stretch could work ...
(But for this to work the package system needs to be consistent - you 
have checked what "apt-get install -f" proposes?)


-

At least, the problem this report was opened for seems to be a result of 
the package mix of Squeeze and Stretch.


Kind regards,
Bernhard


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

Bug#784118: RM: squid -- RoQA; replaced by squid3

[Moritz Mühlenhoff]

On Mon, May 04, 2015 at 07:38:24AM -0400, Scott Kitterman wrote:
> On Sunday, May 03, 2015 11:25:39 AM you wrote:
> > Package: ftp.debian.org
> > Severity: normal
> > 
> > Hi,
> > please remove squid. It has been replaced by squid3 (672156)
> > and is already not part of jessie, so let's also remove it
> > from unstable now.
> 
> It still has rdepends:
> 
> Checking reverse dependencies...
> # Broken Depends:
> sqcwa: sqcwa
> squid-prefetch: squid-prefetch
> 
> Those either need to be removed as well or made to use squid3.  Please remove 
> the moreinfo tag once this has been resolved.

I've filed separate removal bugs for these.

Cheers,
Moritz


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

Bug#784704: postal: [PATCH] Crashes randomly due to buffer underflow

[Timo Sirainen]

Package: postal
Version: 0.73+nmu1
Severity: important

I can't run Postal for more than a few minutes before it crashes. Fix included 
below.

diff -ru postal-0.73/smtp.cpp ../postal-0.73+nmu1/smtp.cpp
--- postal-0.73/smtp.cpp2012-01-14 14:38:45.0 +0200
+++ ../postal-0.73+nmu1/smtp.cpp2015-02-13 13:36:06.583435283 +0200
@@ -77,7 +77,8 @@
 int offset = random() % (MAP_SIZE - (len - 2));
 memcpy(buf, &m_randBuf[offset], len - 2);
   }
-  strcpy(buf + len - 2, "\r\n");
+  if (len >= 2)
+strcpy(buf + len - 2, "\r\n");
 }

 const int max_line_len = 79;

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

Bug#784705: RM: sqcwa -- RoQA; unmaintained, depends on obsolete squid 2.7, dead upstream

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove sqcwa. The last maintainer upload was ten years ago
and it depends on squid 2 which is scheduled for removal. Upstream
has vanished.

Cheers,
Moritz


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

Bug#784703: [glabels] non-standard "paper" sizes (labeling optical discs)

[Christoph Franzen]

Package: glabels
Version: 3.0.1-4.1
Severity: normal

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

Hello,

the Brother MFC-J825DW fax/scanner/printer device allows printing
labels directly onto printable optical discs up to 12 cm in diameter.

Making a new template with the label designer function does not work.

You can only choose among a few well-known paper sizes, or enter
rectangular shaped special sizes, but not truly round ones, and you
cannot give those a name accordig to its appearance in the printer
driver's list of choices.

If I choose "119,9 mm x 119,9 mm", the size the Brother printer driver
reports for its choice "12 cm Disc", the driver will not print on the
disc, you HAVE to choose "12 cm Disc" as the "paper size" (like you can
choose "A4" or "letter"). This is impossible with Glabels.

Creating a template manually with a paper size of "12 cm Disc" instead
does also not work. Glabels will segfault after an error message:
'LibGlabels-Message: Unknown page size id "12 cm Disc", trying as name'.

--- System information. ---
Architecture: i386
Kernel:   Linux 3.14-1-amd64

Debian Release: 8.0
[…]

--- Package information. ---
Depends (Version) | Installed
=-+-==
glabels-data(= 3.0.1-4.1) | 3.0.1-4.1
libc6(>= 2.7) | 
libcairo2 (>= 1.10.0) | 
libebook-1.2-14   (>= 3.5.91) | 
libebook-contacts-1.2-0   (>= 3.7.90) | 
libedataserver-1.2-18 (>= 3.5.91) | 
libgdk-pixbuf2.0-0(>= 2.22.0) | 
libglib2.0-0  (>= 2.37.3) | 
libgtk-3-0 (>= 3.0.9) | 
libiec16022-0 | 
libpango-1.0-0(>= 1.28.1) | 
libpangocairo-1.0-0   (>= 1.28.1) | 
libqrencode3   (>= 3.2.0) | 
librsvg2-2(>= 2.32.0) | 
libxml2(>= 2.7.4) | 


Recommends  (Version) | Installed
=-+-===
evince| 3.12.1-1


Suggests   (Version) | Installed
-+-===
evolution-data-server| 

-- 
Christoph Franzen


signature.asc
Description: PGP signature

Bug#784691: transition: cgal

[Jonathan Wiltshire]

Control: tag -1 confirmed
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-cgal.html


On 2015-05-07 20:31, Joachim Reichel wrote:
the CGAL library bumped its SONAME due to some incompatible ABI change. 
None of
the reverse dependencies in sid actually use the affected part of the 
ABI, and
haven't hardcoded libcgal10 either. As far as I understand a round of 
binNMUs
for the reverse dependencies should be sufficient. The maintainers of 
the
reverse dependencies are aware of the SONAME change and my plan to ask 
for

binNMUs, no rejections so far.

Sorry, for not asking for a transition slot in advance. When reading up 
the
documentation for binNMU requests I realized that this is actually a 
transition


Fortunately it doesn't collide with anything currently in progress; I'll 
schedule rebuilds.


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

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

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


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

Bug#784702: wmweather+: Should Build-Depend on libwraster-dev.

[Doug Torrance]

Package: wmweather+
Version: 2.15-1
Severity: serious
Tags: patch
Justification: Policy 4.2

Beginning with wmaker version 0.95.6-1, libwraster3-dev has been renamed to
libwraster-dev.  As this is a build dependency of wdm, debian/control should
be updated accordingly.
diff --git a/debian/control b/debian/control
index 4be3317..c1cf0ac 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: wmweather+
 Section: x11
 Priority: optional
 Maintainer: Martin Stigge 
-Build-Depends: libpcre3-dev, libcurl4-gnutls-dev, libwraster3-dev, debhelper (>= 9)
+Build-Depends: libpcre3-dev, libcurl4-gnutls-dev, libwraster-dev, debhelper (>= 9)
 Standards-Version: 3.9.6
 Vcs-Browser: http://anonscm.debian.org/viewvc/collab-maint/deb-maint/wmweather%2B/
 Vcs-Svn: svn://anonscm.debian.org/collab-maint/deb-maint/wmweather+/

Bug#771544: its because of tmpdir collision

[Lucas Nussbaum]

On 30/11/14 at 22:19 +0530, Pirate Praveen wrote:
> control: severity 771544 grave
> 
> this is not because of sudo, but because /tmp/ruby-uuid is already
> created by another user. It should add a username prefix when creating
> state dir.

So according to the discussion in
https://github.com/assaf/uuid/issues/45, this is a bug in diaspora?

Are you OK with reassigning?

Lucas


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

Bug#784701: Should Build-Depend on libwraster-dev.

[Doug Torrance]

Package: wdm
Version: 1.28-17
Severity: serious
Tags: patch

Beginning with wmaker version 0.95.6-1, libwraster3-dev has been renamed to
libwraster-dev.  As this is a build dependency of wdm, debian/control should
be updated accordingly.
diff --git a/debian/control b/debian/control
index 2342db0..38ac52f 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,7 @@ Build-Depends: debhelper (>= 9~),
libpng-dev,
libselinux1-dev [linux-any],
libwings-dev,
-   libwraster3-dev,
+   libwraster-dev,
libx11-dev,
libxau-dev,
libxdmcp-dev,

Bug#784699: ruby-i18n: random test failures during build

[Lucas Nussbaum]

Package: ruby-i18n
Version: 0.6.11-2
Severity: normal

Hi,

When building ruby-i18n, there are various random test failures:

  1) Failure:
I18nFallbacksApiTest#test_lookup:_given_an_array_of_keys_it_translates_all_of_them
 
[/«PKGBUILDDIR»/debian/ruby-i18n/usr/lib/ruby/vendor_ruby/i18n/tests/lookup.rb:52]:
--- expected
+++ actual
@@ -1 +1 @@
-["bar", "baz"]
+"translation missing: de.foo.baz"



  2) Failure:
I18nFallbacksApiTest#test_lookup:_given_a_missing_key,_no_default_and_no_raise_option_it_returns_an_error_message
 
[/«PKGBUILDDIR»/debian/ruby-i18n/usr/lib/ruby/vendor_ruby/i18n/tests/lookup.rb:33]:
--- expected
+++ actual
@@ -1 +1 @@
-"translation missing: en.missing"
+"translation missing: de.missing"


It takes several attempts to get a successful build (apparently it's worse when
using sbuild, than when using git-buildpackage).

Lucas

-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable'), 
(300, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages ruby-i18n depends on:
ii  ruby1:2.1.5
ii  ruby2.1 [ruby-interpreter]  2.1.5-2+deb8u1

ruby-i18n recommends no packages.

ruby-i18n 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#784700: rygel: Rygel uses 100% cpu, does not shut down, does not work

[Andrew Kane]

Package: rygel
Version: 0.24.2-1+b1
Severity: important

Dear Maintainer,

   * What led up to the situation?

I installed rygel and rygel-preferences to share media files on my local 
network.
On testing with Windows Media Player the shares were enumerated but not 
browseable. Testing with Rhythmbox on a Debian machine worked as expected. Some 
hours later, I noticed rygel taking 100% cpu (one core out of four) in top. 
Shares no longer enumerate in Win Media Player nor in Rhythmbox. 

At this point I invoked `rygel -s` and got the following message:
(rygel:14818): Rygel-WARNING **: Failed to shut-down other rygel instance: The 
connection is closed

I don't know to what connection this message refers.


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

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

Versions of packages rygel depends on:
ii  libc6   2.19-18
ii  libgee-0.8-20.16.1-1
ii  libglib2.0-02.42.1-1
ii  libgssdp-1.0-3  0.14.11-1
ii  libgstreamer-plugins-base1.0-0  1.4.4-2
ii  libgstreamer1.0-0   1.4.4-2
ii  libgupnp-1.0-4  0.20.12-1
ii  libgupnp-av-1.0-2   0.12.7-1
ii  libgupnp-dlna-2.0-3 0.10.2-1
ii  libmediaart-1.0-0   0.7.0-2
ii  librygel-core-2.4-2 0.24.2-1+b1
ii  librygel-renderer-2.4-2 0.24.2-1+b1
ii  librygel-server-2.4-2   0.24.2-1+b1
ii  libsoup2.4-12.48.0-1
ii  libsqlite3-03.8.9-2
ii  libunistring0   0.9.3-5.2+b1
ii  libuuid12.25.2-6
ii  libxml2 2.9.1+dfsg1-5

Versions of packages rygel recommends:
ii  gstreamer1.0-libav 1.4.4-2
ii  gstreamer1.0-plugins-base  1.4.4-2
ii  gstreamer1.0-plugins-good  1.4.4-2
ii  gstreamer1.0-plugins-ugly  1.4.4-2+b1

Versions of packages rygel suggests:
pn  rygel-mediathek
pn  rygel-playbin  
ii  rygel-preferences  0.24.2-1+b1
pn  rygel-tracker  
pn  tumbler

-- 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#726500: AMD support request for fglrx legacy driver for jessie

[nabster]

I have requested an updated driver using AMD's contact form:

http://support.amd.com/en-us/contact/email-form

Will it help if more people request the same?


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

Bug#756084: Patch

[Jelmer Vernooij]

The attached patch fixes this issue.
Description: Fix listening on IPv6 when enabled.
Author: Jelmer Vernooij 
Bug: https://github.com/ejurgensen/forked-daapd/issues/147
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756084
Forwarded: https://github.com/ejurgensen/forked-daapd/pull/148

--- forked-daapd-22.3+dfsg1.orig/src/httpd.c
+++ forked-daapd-22.3+dfsg1/src/httpd.c
@@ -1356,7 +1356,7 @@ httpd_init(void)
* as IPv6 might not be supported on the system.
* We still warn about the failure, in case there's another issue.
*/
-  ret = evhttp_bind_socket(evhttpd, "0.0.0.0", port);
+  ret = evhttp_bind_socket(evhttpd, v6enabled?"::":"0.0.0.0", port);
   if (ret < 0)
 {
   DPRINTF(E_FATAL, L_HTTPD, "Could not bind INADDR_ANY:%d\n", port);


signature.asc
Description: Digital signature

Bug#784304: RFS: xerces-c/3.1.2+debian-1 [ITA] -- validating XML parser library for C++

[Bill Blough]

On Thu, May 07, 2015 at 04:36:58PM -0300, Henrique de Moraes Holschuh wrote:
> On Tue, May 5, 2015, at 01:27, Bill Blough wrote:
> >   * Added lintian overrides for issues that won't be fixed right now:
> >   no-upstream-changelog, no-symbols-control-file, shlib-calls-exit
> >   * Added lintian override for false positive (hardening)
> 
> Please don't add lintian overrides for real problems just because
> they're not going to be fixed soon.

Removed the overrides and reuploaded to mentors.

> 
> In this case, adding the hardening lintian override would be correct
> (assuming it really is a false-positive -- make really really sure it is
> a false positive before you add such an override), but the other ones
> are best not overriden.

blhc passes and a visual inspection of the build log shows that the flags are 
being  included on the command line.  Which leads me to wonder - am I missing
an edge case where it could *not* be a false positive?


Thanks for your feedback!

Bill


signature.asc
Description: Digital signature

Bug#784698: cobbler: [INTL:pt] Portuguese translation for debconf messages

[Américo Monteiro]

Package: cobbler
version: 2.6.6+dfsg1-1
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for cobbler's debconf messages.
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro


cobbler_2.6.6+dfsg1-1_pt.po.gz
Description: GNU Zip compressed data

Bug#784697: nib-ls has python3 shebang while comes from python2 package

[Yaroslav Halchenko]

Package: python-nibabel
Version: 1.3.0-2
Severity: normal


Detected on a wheezy backport

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

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

Versions of packages python-nibabel depends on:
ii  python  2.7.9-1
ii  python-numpy1:1.8.2-2
ii  python-scipy0.14.1-1
ii  python-support  1.0.15

Versions of packages python-nibabel recommends:
ii  python-dicom  0.9.8-1
ii  python-fuse   2:0.2.1-10

Versions of packages python-nibabel suggests:
pn  python-nibabel-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#784696: reportbug ignores -d - sends to Debian anyway

[Scott Wakeling]

Package: reportbug
Version: 6.6.3
Severity: normal

Dear Maintainer,

To explore how reportbug worked, and see what info was required to raise an ITP,
I ran:

reportbug -d --email sc...@diskfish.org wnpp

I expected reportbug to send an email only to myself, according to the man page:

-d, --debug
 Don't send a real bug  report  to  Debian;  send  it  to  yourself
 instead.  This is primarily used for testing by the maintainer.

Instead, the bug was sent to myself and Debian BTS (raising #784370) and cc'd
to debian-devel.

Luckily, I was happy with the content, but if I had trusted -d to work as
described and entered some junk in reportbug, I would have made a mess.

Could the maintainer please clarify if the man page is incorrect, if reportbug
should in fact support this option, or if there is some user error on my part.


-- Package-specific info:
** Environment settings:
EDITOR="vim"
VISUAL="vim"
DEBEMAIL="sc...@diskfish.org"
DEBFULLNAME="Scott Wakeling"
INTERFACE="text"

** /home/scott/.reportbugrc:
reportbug_version "6.6.3"
mode standard
ui text

-- System Information:
Debian Release: 8.0
Architecture: amd64 (x86_64)

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

Versions of packages reportbug depends on:
ii  apt   1.0.9.8
ii  python2.7.9-1
ii  python-reportbug  6.6.3
pn  python:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  claws-mail   3.11.1-3
ii  debconf-utils1.5.56
pn  debsums  
pn  dlocate  
ii  emacs24-bin-common   24.4+1-5
ii  file 1:5.22+15-2
ii  gnupg1.4.18-7
ii  python-gtk2  2.24.0-4
pn  python-gtkspell  
pn  python-urwid 
ii  python-vte   1:0.28.2-5
ii  sendmail-bin [mail-transport-agent]  8.14.4-8
ii  xdg-utils1.1.0~rc1+git20111210-7.4

Versions of packages python-reportbug depends on:
ii  apt   1.0.9.8
ii  python-debian 0.1.27
ii  python-debianbts  1.12
pn  python:any

python-reportbug 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#784667: www.debian.org: Merchandise vendors not listed alphabetically in /misc/merchandise

[Jeremías Casteglione]

Hi:

On Thu, 07 May 2015 18:20:58 +0200
Laura Arjona Reina  wrote:
> 
> A user reported [1] that the list of merchandise vendors is not listed
> alphabetically.
> 
> [1] https://lists.debian.org/debian-www/2015/05/msg00032.html
> 
> I believe the list is stored in the file
> https://anonscm.debian.org/viewvc/webwml/webwml/english/misc/merchandise.data
> 

I'm attaching a patch which I think could work. I sorted the list as
follows:

fgrep 'Index: english/misc/merchandise.data
===
RCS file: /cvs/webwml/webwml/english/misc/merchandise.data,v
retrieving revision 1.61
diff -u -u -r1.61 merchandise.data
--- english/misc/merchandise.data	6 Jan 2015 03:41:19 -	1.61
+++ english/misc/merchandise.data	7 May 2015 20:10:02 -
@@ -1,24 +1,6 @@
 #include "$(ENGLISHDIR)/misc/merchandise.def"
 
 
-
-  
-  http://www.digistickr.de/debian-sticker.html";>
-  >
-
-
-
-  
-  http://camisetas.punksmedia.org/?product_cat=debian";>
-  , , , , >
-
-
-
-  
-  http://www.enventelibre.org/debian";>
-  , , , , >
-
-
 # disables, doesn't exist
 #
 #  
@@ -33,6 +15,12 @@
 
 
 
+  
+  http://camisetas.punksmedia.org/?product_cat=debian";>
+  , , , , >
+
+
+
   
   http://common-shirts.org/?p=3444";>
   >
@@ -44,6 +32,12 @@
   , , >
 
 
+
+  
+  http://www.enventelibre.org/debian";>
+  , , , , >
+
+
 # Disabled, no longer operating
 #
 #  
@@ -58,17 +52,17 @@
 
 
 
+  
+  http://www.digistickr.de/debian-sticker.html";>
+  >
+
+
+
   
   http://www.freewear.org/?org=Debian";>
   , >
 
 
-#
-#  
-#  http://www.thinkgeek.com/";>
-#  >
-#
-
 # Not a trustworthy vendor:
 # <9f0a69bf0911122109t32e071b8pc7c01b243c4b2...@mail.gmail.com>
 # <6e67cdea-f626-400a-8095-d91aee6da...@thekurt.net>
@@ -94,7 +88,7 @@
  
  http://debian.koszulkomat.eu";>
  , >
- 
+
 
 # librestickers is on hiatus and will be back 2015-02
 #
@@ -111,6 +105,11 @@
 #  , , , >
 #
 
+#
+#  
+#  http://www.thinkgeek.com/";>
+#  >
+#
 
 # disabled, see <4f27fb57.1020...@gmail.com>
 # reenabled, see <668d08a0fccb4d50abe8e712f0e4b...@unixstickers.com>

Bug#784695: gnumeric: Mouse cursor is garbled when showing Gnumeric-specific icon

[Chad Wallace]

Package: gnumeric
Version: 1.12.18-2
Severity: normal

Dear Maintainer,

In Gnumeric, whenever I hover the mouse over the cells, and it renders
the chubby cross cursor, it is slightly garbled.  The cursor itself
renders OK, but there's a box around it (probably double the cursor's
width and height, and centered on the cursor) that has garbage, and
leaves traces of previous positions of the cursor.

It seems like the box under the cursor is a window into a different
region, where the artifacts from previous cursors all blend together and
persist in that region...  Not sure if I'm explaining it properly...
I'll try to attach a picture of it.

I had to take a picture with a cell phone, rather than a screenshot,
because the screenshots either didn't show the cursor, or they showed
the cursor properly without this problem.

The problem does not occur when Gnumeric is rendering a stock cursor
(like the skinny cross for fill-down on the selected cell, or the regular
arrow you get on the toolbars and menus).  The only one that's garbled
is the chubby cross that's specific to Gnumeric.

I tried to reproduce this problem in Chromium by trying every different
value of the cursor CSS style, but they all rendered properly, even some
that looked like they were Chromium-specific.  Gnumeric is the only
program I've seen this problem in.  If you know of any others that use
their own cursors, I can try them to see what happens.

I'm not sure if this bug belongs to Gnumeric, or GTK, or Noveau or Xorg,
but I'm sure you can reassign it if you know better.

Thanks!



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

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

Versions of packages gnumeric depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  gnumeric-common1.12.18-2
ii  gsfonts1:8.11+urwcyr1.0.7~pre44-4.2
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-18
ii  libcairo2  1.14.0-2.1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libglib2.0-0   2.42.1-1
ii  libgoffice-0.10-10 0.10.18-1
ii  libgsf-1-114   1.14.30-2
ii  libgtk-3-0 3.14.5-1
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libxml22.9.1+dfsg1-5
ii  procps 2:3.3.9-9
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages gnumeric recommends:
ii  evince3.14.1-2
ii  gnumeric-doc  1.12.18-2
ii  lp-solve  5.5.0.13-7+b1

Versions of packages gnumeric suggests:
ii  fonts-liberation   1.07.4-1
pn  gnumeric-plugins-extra 
ii  ttf-mscorefonts-installer  3.6

-- debconf information:
  gnumeric/existing-process: false
  gnumeric/existing-process-title:


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

Bug#784692: release-notes: package maradns is not updated, it has been removed

[Luca Bruno]

On Thu, 7 May 2015 21:53:34 +0200 Christian Garbs  wrote:

> I have not yet found out why maradns has been removed and I don't know
> if it could perhaps show up again with the next point release, but for
> now the listing of maradns in the table of the updated packages should
> be removed.

I'm in no way involved in this, but just for the sake of information it was 
autoremoved on 07/02/2015 due to RC bug #774874, see 
https://packages.qa.debian.org/m/maradns/news/20150207T163914Z.html

It surely won't show up in further jessie point releases, but if you need it 
you can ask the maintainer (Dariusz CCed here) to upload 2.0.09-4 into 
jessie-backports. 

Cheers, Luca

-- 
 .''`.  ** Debian GNU/Linux **  | Luca Bruno (kaeso)
: :'  :   The Universal O.S.| lucab (AT) debian.org
`. `'`  | GPG Key ID: 0x4F3BBEBF
  `- http://www.debian.org  | Debian GNU/Linux Developer


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

Bug#775312: system-config-printer, #775312, aborts on not-found

[hharrison]

(Sorry, the editor in the bug report dialog threw me. Here's what I 
entered before being unable to figure out easily how to send it.)


Just installed debian live 8.0 i386 xfce with both printers connected 
and

turned on,
but neither recognized. Run "Print settings" HP 940C, parallel port 
added fine


Choose "add". Identified Brother HL 2280DW. Popup "Searching for drivers 
"


After 30 sec. or so--poof, no print settings window. I'm back to 
desktop.

Run same again. Same popup. This time I move popup around in case it's
covering something. Popup goes away, leaves the window it came from
hung and not redrawing on the desktop. I move it, there's a blank
"print settings" window underneath (left over from first run, I
don't think so).

I'll now search for a driver manually and figure how to install.
I expected at lease a "not found" message, but even better "I've looked
at X Y and Z on the Web and found no driver for the HL 2280DW. Would you
like to try a driver for HL 2260 which should print but doesn't have
scanner support? And (here's what to do if you need to
uninstall 2260)" or some part of all that.

Hal Harrison
Boca Raton, FL.


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

Bug#755517: golang-go.net-dev: please package a new upstream version

[Tianon Gravi]

On 7 May 2015 at 14:18, Jonathan Dray  wrote:
> I was very busy lately and i didn't take the time to update / repackage
> everything.
>
> I will really take a close look at that this week end.
> At this point how can i help efficiently ?

IMO if you can get a newer "go.net" packaged, that's good enough for
me! :D  Feel free to reach out if you need any help doing so, too!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


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

Bug#784694: smcroute: please remove build date based buildid from version string

[Micha Lenk]

Package: smcroute
Version: 2.0.0-4
Severity: minor
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
Control: forwarded -1 
https://github.com/troglobit/smcroute/commit/73f6f14907f709e40689216291621ad26cd22ecd

Hi!

While working on the “reproducible builds” effort [1], I have noticed
that smcroute could not be built reproducibly.

The problematic bit is the BUILD id included in the 'smcroute -v' output,
which is based on a timestamp generated during build.  As this doesn't feel
like really crucial information, the fix committed upstream [2] simply
removes it by default.

 [1]: https://wiki.debian.org/ReproducibleBuilds
 [2]: 
https://github.com/troglobit/smcroute/commit/73f6f14907f709e40689216291621ad26cd22ecd

Regards,
Micha


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

Bug#784693: exim4-config: Exim configuration error in line 852 of /var/lib/exim4/config.autogenerated.tmp

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Thu, 2015-05-07 at 22:12 +0200, Damien Couroussé wrote:
> The installation of exim4 fails as copied below.
> Please also find attached the tmp file
> /var/lib/exim4/config.autogenerated.tmp created during the installation
[...]
> 2015-05-07 22:03:43 Exim configuration error in line 852 of
> /var/lib/exim4/config.autogenerated.tmp:
>   unknown rewrite flag character '"' (could be missing quotes round
> replacement item)

The problem, from the file that you supplied, is:

.ifndef MAIN_LOCAL_DOMAINS
MAIN_LOCAL_DOMAINS=@:localhost:# localhost.localdomain
.endif
.ifndef MAIN_RELAY_TO_DOMAINS
MAIN_RELAY_TO_DOMAINS=empty
.endif
.ifndef ETC_MAILNAME
ETC_MAILNAME=# localhost.localdomain
.endif

How have you ended up with mailname set to something invalid? (With a
leading "# ".)

Regards,

Adam


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

Bug#755517: golang-go.net-dev: please package a new upstream version

[Jonathan Dray]

hi,

I was very busy lately and i didn't take the time to update / repackage
everything.

I will really take a close look at that this week end.
At this point how can i help efficiently ?

2015-05-07 19:31 GMT+02:00 Tianon Gravi :

> On Mon, 21 Jul 2014 17:57:03 +0200 Alessandro Ghedini 
> wrote:
> > I'm working on a package that requires the module "go.net/html/charset",
> but it
> > doesn't appear to be present in the go.net version packaged for Debian
> yet.
> >
> > Could you please package a newer upstream snapshot?
>
> This is even more important now that upstream has moved their imports to "
> golang.org/x/net" (and moved to Git; https://github.com/golang/net).
>
> It's also blocking a newer version of "golang-go.tools" at this point. :(
>
> ♥,
> - Tianon
>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
>

Bug#784693: exim4-config: Exim configuration error in line 852 of /var/lib/exim4/config.autogenerated.tmp

[Damien Couroussé]

Package: exim4-config
Version: 4.84-8
Severity: important


hello,

The installation of exim4 fails as copied below.
Please also find attached the tmp file
/var/lib/exim4/config.autogenerated.tmp created during the installation
process.

regards,


root@puccini:~# LANG=C apt-get install exim4
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  bsd-mailx exim4-base exim4-config exim4-daemon-light
Suggested packages:
  eximon4 exim4-doc-html exim4-doc-info spf-tools-perl swaks
Recommended packages:
  mailx
The following NEW packages will be installed:
  bsd-mailx exim4 exim4-base exim4-config exim4-daemon-light
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/2266 kB of archives.
After this operation, 6148 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Preconfiguring packages ...
Selecting previously unselected package exim4-config.
(Reading database ... 209734 files and directories currently installed.)
Preparing to unpack .../exim4-config_4.84-8_all.deb ...
Unpacking exim4-config (4.84-8) ...
Selecting previously unselected package exim4-base.
Preparing to unpack .../exim4-base_4.84-8_amd64.deb ...
Unpacking exim4-base (4.84-8) ...
Selecting previously unselected package exim4-daemon-light.
Preparing to unpack .../exim4-daemon-light_4.84-8_amd64.deb ...
Unpacking exim4-daemon-light (4.84-8) ...
Selecting previously unselected package bsd-mailx.
Preparing to unpack .../bsd-mailx_8.1.2-0.20141216cvs-2_amd64.deb ...
Unpacking bsd-mailx (8.1.2-0.20141216cvs-2) ...
Selecting previously unselected package exim4.
Preparing to unpack .../archives/exim4_4.84-8_all.deb ...
Unpacking exim4 (4.84-8) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17) ...
Setting up exim4-config (4.84-8) ...
2015-05-07 22:03:43 Exim configuration error in line 852 of
/var/lib/exim4/config.autogenerated.tmp:
  unknown rewrite flag character '"' (could be missing quotes round
replacement item)
2015-05-07 22:03:43 Exim configuration error in line 852 of
/var/lib/exim4/config.autogenerated.tmp:
  unknown rewrite flag character '"' (could be missing quotes round
replacement item)
2015-05-07 22:03:43 Exim configuration error in line 852 of
/var/lib/exim4/config.autogenerated.tmp:
  unknown rewrite flag character '"' (could be missing quotes round
replacement item)
exim: could not open panic log - aborting: see message(s) above
Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not
installing
/var/lib/exim4/config.autogenerated.tmp to
/var/lib/exim4/config.autogenerated
dpkg: error processing package exim4-config (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of exim4-base:
 exim4-base depends on exim4-config (>= 4.82) | exim4-config-2; however:
  Package exim4-config is not configured yet.
  Package exim4-config-2 is not installed.
  Package exim4-config which provides exim4-config-2 is not configured yet.

dpkg: error processing package exim4-base (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of exim4-daemon-light:
 exim4-daemon-light depends on exim4-base (>= 4.84); however:
  Package exim4-base is not configured yet.

dpkg: error processing package exim4-daemon-light (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of bsd-mailx:
 bsd-mailx depends on default-mta | mail-transport-agent; however:
  Package default-mta is not installed.
  Package exim4-daemon-light which provides default-mta is not
configured yet.
  Package mail-transport-agent is not installed.
  Package exim4-daemon-light which provides mail-transport-agent is not
configured yet.

dpkg: error processing package bsd-mailx (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of exim4:
 exim4 depends on exim4-base (>= 4.84-8); however:
  Package exim4-base is not configured yet.
 exim4 depends on exim4-base (<< 4.84-8.1); however:
  Package exim4-base is not configured yet.
 exim4 depends on exim4-daemon-light | exim4-daemon-heavy |
exim4-daemon-custom; however:
  Package exim4-daemon-light is not configured yet.
  Package exim4-daemon-heavy is not installed.
  Package exim4-daemon-custom is not installed.

dpkg: error processing package exim4 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 exim4-config
 exim4-base
 exim4-daemon-light
 bsd-mailx
 exim4
E: Sub-process /usr/bin/dpkg returned an error code (1)



-- Package-specific info:
Exim version 4.84 #3 built 17-Feb-2015 17:45:49
Copyright (c) University of Cambridge, 1995 - 2014
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007
- 2014
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support

Bug#784180: closed by gregor herrmann (Bug#784179: fixed in libnet-ldap-perl 1:0.6500+dfsg-1)

[Christian]

Thanks a lot for the quick fix! I can confirm that this fixes the issue.
Best regards,

Christian


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

Bug#784692: release-notes: package maradns is not updated, it has been removed

[Christian Garbs]

Package: release-notes
Severity: normal

Dear Maintainer,

chapter 2.2 of the Jessie release notes mentions that the version of
the maradns package has been updated from 1.4.12 to 2.0.09

But maradns has not been updated, it's completely missing from
Jessie.  The package database lists no version for 'stable' (and my
local apt package lists agree):
https://packages.debian.org/search?keywords=maradns

I have not yet found out why maradns has been removed and I don't know
if it could perhaps show up again with the next point release, but for
now the listing of maradns in the table of the updated packages should
be removed.


-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (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)

-- 
Christian.Garbs.http://www.cgarbs.de

Ich bin zu doof, um einen Virus zu programmieren. Deshalb bitte ich
Sie, diese Nachricht selbständig zu vervielfältigen und an alle Ihnen
bekannten Email-Adressen zu senden. Vergessen Sie nicht, danach alle
Ihre Festplatten neu zu formatieren. Danke für Ihre Mitarbeit.


signature.asc
Description: Digital signature

Bug#784639: lintian: Reports on lintian.debian.org contain non-UTF8 encoding

[Niels Thykier]

Control: tags -1 confirmed
Control: notfound -1 2.5.30+deb8u4

On 2015-05-07 13:47, Andreas Ronnquist wrote:
> Package: lintian
> Version: 2.5.30+deb8u4
> Severity: minor
> 
> Dear Maintainer,
> 
> Being cursed with a surname containing non-ASCII characters, I notice
> that the reports on lintian.debian.org [1], encodes the 'ö' in my
> surname wrongly, which causes browsers set on UTF8 to show it wrongly.
> I have tested with Iceweasel from stable, and (non-debian-packaged)
> Midori.
> 
> [1] https://lintian.debian.org/maintainer/gus...@debian.org.html
> [...]
> 

Hi,

I have localised this to YAML::Any being useless when it comes to
encoding.  It turns out that YAML::XS (my local implementation) and
whatever YAML::Any picks on lindsay.d.o wildly disagrees on how to deal
with encoding:

 * YAML::XS croaks if given "decoded" text, but automatically converts
   byte streams into UTF-8 encoded YAML data structures
 * YAML::Something produces mojibake if given a "non-decoded" text (i.e.
   a byte stream) and only produces the correct result if given UTF-8
   text.

In conclusion - YAML::Any is /not/ a consistent interface of
interchangeable implementations, which I originally thought it was.  I
have asked DSA to install YAML::XS on lindsay.d.o and I intend to
replace YAML::Any with YAML::XS  in the code once that is done.

I have removed the found version as it is (strictly) speaking an
artefact of the unreleased version, which is currently running on
lindsay.d.o.

Thanks,
~Niels


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

Bug#714372: [Pkg-libvirt-maintainers] Bug#714372: libvirt: Please enable firewalld support

[Guido Günther]

Hi,
On Thu, May 07, 2015 at 10:39:20AM +0200, Laurent Bigonville wrote:
> Hello,
> 
> Any update on this?
> 
> In the debian/changelog, I see that the firewalld support was disabled
> because of the hard-dependency against dbus. But now we are indirectly
> depending against it via policykit anyway.

I think so, we need to properly test this though and check if we can
keep it as a optional dependency. Nigel, would that be something you
want to try out?

Cheers,
 -- Guido

> 
> Could the firewalld support now?
> 
> Cheers,
> 
> Laurent Bigonville
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
> 


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

Bug#784679: jessie-pu: package rdesktop/1.8.2-3+deb8u1

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Thu, 2015-05-07 at 21:47 +0200, László Böszörményi wrote:
> On Thu, May 7, 2015 at 8:13 PM, Adam D. Barratt
>  wrote:
> > On Thu, 2015-05-07 at 20:06 +0200, László Böszörményi wrote:
> >> There's a segmentation fault bug[1] in the Jessie version of rdesktop.
> >> As the fix is very easy, it would be nice to have in Jessie.
> > [...]
> >> [1] http://bugs.debian.org/784634
> >
> > The metadata of that bug indicates that it also affects the version of
> > rdesktop in unstable. Is that correct? If so, please fix the bug in
> > unstable; if not, please fix the metadata.
>  Updated. The bug affects Jessie only, the version in Stretch + Sid
> contains the fix.

Thanks. (I removed the "jessie" tag from the bug, as the
version-tracking information is perfectly adequate.)

Please go ahead.

Regards,

Adam


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

Bug#784679: jessie-pu: package rdesktop/1.8.2-3+deb8u1

[GCS]

On Thu, May 7, 2015 at 8:13 PM, Adam D. Barratt
 wrote:
> On Thu, 2015-05-07 at 20:06 +0200, László Böszörményi wrote:
>> There's a segmentation fault bug[1] in the Jessie version of rdesktop.
>> As the fix is very easy, it would be nice to have in Jessie.
> [...]
>> [1] http://bugs.debian.org/784634
>
> The metadata of that bug indicates that it also affects the version of
> rdesktop in unstable. Is that correct? If so, please fix the bug in
> unstable; if not, please fix the metadata.
 Updated. The bug affects Jessie only, the version in Stretch + Sid
contains the fix.

Cheers,
Laszlo/GCS


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

Bug#765124: caused by the upgrade from ruby-i18n 0.6.9 to 0.6.11

[Lucas Nussbaum]

On 21/10/14 at 12:00 +0200, Cédric Boutillier wrote:
> Control: found -1 ruby-i18n/0.6.11-1
> Control: notfound -1 ruby-i18n/0.6.9-2
> 
> Hi,
> 
> It seems that this bug has been caused by the upgrade of ruby-i18n rom
> 0.6.9 to 0.6.11. 
> 
> Something broke in the determination of whic locales are available.
> This is likely related to the following commit:
> 
> https://github.com/svenfuchs/i18n/commit/a65fffd6f0472bc413ba41809dafc6292e29d2ae

I bisected it with i18n usptream and can confirm that this is needed the
first bad commit.

Lucas


signature.asc
Description: Digital signature