Bug#808571: Does not support travelling across timezones

[Ritesh Raj Sarraf]

Hello Martin,

On Mon, 2015-12-21 at 16:53 +1300, martin f krafft wrote:
> Travelling through several timezones, I found that redshift neither
> updates its understanding of what nighttime is (based on the
> timezone), nor does it make any efforts to re-acquire its position.
> Maybe it could instead listen to appropriate events, or just reset
> itself every hour or so.

What desktop framework are you using ? And how exactly are you using
redshift ?

The current redshift now has support for geoclue2, which should give it
the information initially. But, like you have reported, I need to check
on how it behaves/honors changes in those events.

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



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

Bug#808579: apt: Very slow rred phase during update

[Stefan Fritsch]

Package: apt
Version: 1.1.5
Severity: normal

Since some time, the rred phase during aptitude/apt-get update is very
slow and produces very high system cpu-load.

Today I managed to get an strace of the relevant process (the one
matched by "pgrep -f rred", I don't know the exact name right now). It
does stuff like this:

2572  read(3, "P", 1)   = 1
2572  read(3, "a", 1)   = 1
2572  read(3, "c", 1)   = 1
2572  read(3, "k", 1)   = 1
2572  read(3, "a", 1)   = 1
2572  read(3, "g", 1)   = 1
2572  read(3, "e", 1)   = 1
2572  read(3, ":", 1)   = 1
2572  read(3, " ", 1)   = 1
2572  read(3, "o", 1)   = 1
2572  read(3, "p", 1)   = 1
2572  read(3, "e", 1)   = 1
2572  read(3, "n", 1)   = 1
2572  read(3, "s", 1)   = 1
2572  read(3, "l", 1)   = 1
2572  read(3, "i", 1)   = 1
2572  read(3, "d", 1)   = 1
2572  read(3, "e", 1)   = 1
2572  read(3, "-", 1)   = 1
2572  read(3, "p", 1)   = 1
2572  read(3, "y", 1)   = 1
2572  read(3, "t", 1)   = 1
2572  read(3, "h", 1)   = 1
2572  read(3, "o", 1)   = 1
2572  read(3, "n", 1)   = 1
2572  read(3, "\n", 1)  = 1
2572  write(4, "Package: openslide-python\n", 26) = 26
2572  read(3, "B", 1)   = 1
2572  read(3, "i", 1)   = 1
2572  read(3, "n", 1)   = 1

Maybe buffering is disabled for some file descriptor where it should not
be?

-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/sources.list present, but not submitted) --


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 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 apt depends on:
ii  adduser 3.113+nmu3
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.19-6
ii  gnupg2  2.1.10-3
ii  gpgv1.4.19-6
ii  libapt-pkg5.0   1.1.5
ii  libc6   2.21-4
ii  libgcc1 1:5.3.1-4
ii  libstdc++6  5.3.1-4

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.7.5-3
ii  dpkg-dev1.18.3
ii  python-apt  1.1.0~beta1

-- no debconf information

Bug#808578: openvpn client adds wrong routes and blackholes a big chunk of networks

[tobias]

Package: openvpn
Version: 2.3.4-5

Debian 8 Jessie amd64

I have a server and a client configured, the server is configured not to 
push a default route so that only the client adds a static route for the 
needed range but
instead I get a route for a very big internet range which blackholes the 
entire 10.0.0.0/8 RFC1918 range.


Don't know if this should go upstream so I'm hoping for some input here.

[root@box ~]# ifconfig tap0
tap0  Link encap:Ethernet  HWaddr e2:f3:f9:b6:d2:52
  inet addr:10.8.0.14  Bcast:255.255.255.254  Mask:252.0.0.0
  inet6 addr: fe80::e0f3:f9ff:feb6:d252/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:100
  RX bytes:0 (0.0 B)  TX bytes:10518 (10.2 KiB)

[root@box ~]# ip route
default via 172.16.80.1 dev eth0
8.0.0.0/6 dev tap0  proto kernel  scope link  src 10.8.0.14
172.16.80.0/23 dev eth0  proto kernel  scope link  src 172.16.80.35
192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1

Some times I also get a route with a even smaller net like 8.0.0.0/5
What i'm expecting is either a 10.8.0.0/24 route as configured on the 
server or no route at all for.


The same happens even if I comment out route-nopull on the client.
If I were to guess this must be related to me turning of the default 
route directive in the server config.


/etc/openvpn/server.conf
port 1194
proto tcp

dev tun

ca ca.crt
cert server.crt
key server.key

management localhost 7505

dh dh2048.pem
server 10.8.0.0 255.255.255.0

;push "redirect-gateway def1 bypass-dhcp"
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

keepalive 10 120
comp-lzo

user nobody
group nogroup

max-clients 50
persist-key
persist-tun

;username-as-common-name
client-cert-not-required

script-security 3 system
auth-user-pass-verify /etc/openvpn/auth.py via-env

status openvpn-status.log
verb 5



/etc/openvpn/client.conf
client
remote x.x.x.x
port 1194
proto tcp
dev tap

ca ca.crt

route-nopull
comp-lzo

user nobody
group nogroup

persist-key
persist-tun

auth-user-pass login.txt

verb 5

Best regards
Tobias

Bug#549303: icewm: Resizing jpeg images with display doesn't work

[Eduard Bloch]

On Sun, 4 Oct 2009 09:51:46 +0100 Anthony Campbell  
wrote:

> I don't know what else you want besides what is in the data generated by
> reportbug. Both machines are running Sid with no desktop manager. I'm
> not trying to set puzzles; it's not a major issue for me because I can
> get round the problem by converting jpeg files to gif or by using gimp,
> but I thought it was worth flagging up a bug report about it.
> 
> If I fire up "display", load the image, select "view" and then resize to
> half size the flicker appears. I attach a sample jpeg file but it seems
> to happen with all of them.
> 
> The flicker frequency is at least 10/sec. I've been using icewm for
> years (literally) and haven't seen this before.
> 
> As I said in my original post, it may well not be icewm per se that
> causes the problem; there have been various issues with X recently, but
> I have no means of knowing if it is that. But since it happens with
> icewm and not other WMs I assume it is connected in some way. I tried
> running icewm without any config files but the same thing happens.

Recently I stared seing things with the nouveau driver where I'd never
think it's possible to happen with X11, creepy rendering artifacts all
over the place. Maybe you had something similar.

In case you are still using IceWM, can you still reproduce this issue?

If you are not using IceWM, would you mind if I just close this report
as a temporary glitch?

Thanks for reporting anyway,
Eduard.

-- 
 kann mir mal jemand linux erklären und ganz von vorne anfangen?
 Also, alles ist ein file ;)

Bug#808476: Re : Bug#808476: Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[Rene Engelhard]

On Sun, Dec 20, 2015 at 10:32:18PM +0100, nicolas.patr...@gmail.com wrote:
> Le 20/12/2015 22:24:24, Rene Engelhard a écrit :
> 
> > libwhateverA -> libwhateverAv5 that is, of course.
> 
> I can’t upgrade because of gcc-5.3 that breaks so many packages.

This is what I mean above.

You can, and it's expected. But most packages shouuld be fixed by now.

You won't get *ANY* support for a version that old. As said, it's not in
testing (and anywhere) for months now.
There's MANY bugfixes in those months and even security fixes.

Come back whe you try with 5.0.4.

Regards,

Rene

Bug#808474: Re [Fix]: liblemonldap-ng-manager-perl: Manager shows garbage where the menu is supposed to be

[Xavier]

Hi Peter,

The problem occurs only with Debian-Testing. The fix is strange but works:

--- lemonldap-ng-manager/lib/Lemonldap/NG/Manager.pm 2015-09-28
08:18:25.740006529 +0200
+++ /usr/share/perl5/Lemonldap/NG/Manager.pm 2015-11-13
16:16:14.951924784 +0100
@@ -20,6 +20,9 @@
Lemonldap::NG::Manager::_i18n
);

+*li = *Lemonldap::NG::Manager::Downloader::li;
+*span = *Lemonldap::NG::Manager::Downloader::span;
+
## @cmethod Lemonldap::NG::Manager new(hashRef args)
# Class constructor.
#@param args hash reference


This patch has been pushed to alioth.

Note that Manager has been totaly rewritten for the next 1.9 which will
be publish in a few weeks.

Regards,
Xavier

Bug#808441: RFS: rfcdiff/1.42-1 ITP

[Peter Spiess-Knafl]

Hey Mattia!

Thanks again for taking the time.

On 12/21/2015 12:04 AM, Mattia Rizzolo wrote:
> wrap-and-sort doesn't touch debian/rules.
> Also, in this process you added new trailing whitespaces (`git diff`
> (and friends, like `git log -p` and `git show`) shows them in red
> here...)
> 

I did not know about that. I've gone over the manpages of wrap-and-sort.
Thanks for pointing that out.

Do you know some sort of command which lists me all occurrences of
trailing whitespaces?

> debian/patches/fix-changelog-typos.patch:1
> debian/patches/fix-changelog-typos.patch:2
> debian/patches/fix-fsf-address.patch:2
> 

Fixed

>>> there is really no need to do that useless
>>> override_dh_auto_install, just empty that target in d/rules, and
>>> write 'rfcdiff' in debian/rfcdiff.install
>>
>> The makefile seems to be for internal development use only. Also
>> Fedora is working around that faulty makefile.
> [...]
>> Therefore I would like to keep the current version until upstream
>> comes up with a fixed version, with proper test and install targets
>> (including DESTDIR and PREFIX variables).
> 
> yeah, I don't mean you to patch the makefile, please re-read my quote
> above.
> that work in override_dh_auto_install + .install file is duplicated for
> nothing.
> I'm proposing the attached patch, what do you think?
> 

I got you wrong there. I removed the lines from d/rules but changed your
patch a little bit for rfcdiff.install.

>> I re-uploaded a modified verion to mentors.
>> Thanks for taking the time.
> 
> btw, I'll happily work through git, given that you have a packaging
> repository, and you're using it sanely I'd use it, rather than going
> with tarballs, is way easier for me.
> Just poke when you do changes to review/upload.
> 

That is great, it also makes things easier for me.

Thanks again for taking the time.

Greetings
Peter

Bug#808577: ITP: ruby-mime-types-data -- registry for information about MIME media type definitions

[Balasankar C]

Package: wnpp
Owner: Balasankar C 
Severity: wishlist

* Package name : ruby-mime-types-data
  Version : 3.2015.1120
  Upstream Author  : Austin Ziegler 
* URL  :
https://github.com/mime-types/mime-types-data/
* License: Expat
  Programming Lang   : Ruby
  Description  : registry for information about MIME media
type definitions


-- 
Regards
Balasankar C
http://balasankarc.in

Bug#808405: [PATCH] Fix cli-common-dev build-dep(-indep) detection logic (Closes: #808405).

[Andrew Shadura]

---
 dh_cligacpolicy | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/dh_cligacpolicy b/dh_cligacpolicy
index 47eda19..b70b464 100755
--- a/dh_cligacpolicy
+++ b/dh_cligacpolicy
@@ -89,7 +89,8 @@ init();
   open(FILE, 'debian/control');
   my @filedata = ;
   close(FILE);
-  if (!($filedata[0] =~ /Build-Depends(-Indep)?: .*cli-common-dev \(>= 
0\.5\.7\)/)) {
+  if ($filedata[0] =~ 
m/Build-Depends(?:\-Indep)?\:(?:.*\n\s+)*.*cli\-common\-dev\s*\(>=\s*([^\)]+)\)/
 &&
+  system("dpkg", "--compare-versions", $1, ">=", "0.5.7") != 0) {
   warning("Warning! No Build-Depends(-Indep) on cli-common-dev (>= 
0.5.7)!");
   }
 }
-- 
2.5.0

Bug#786517: Remove swig 2.0 for Strech (python 3.5, octave 4.0 unsupported)

[Torsten Landschoff]

On 11/01/2015 07:08 AM, James McCoy wrote:
> On Sat, Oct 24, 2015 at 11:48:24PM +0200, Matthias Klose wrote:
>> As seen in #802906, this now becomes an RC issue, as Python 3.5 is a
>> supported Python version, and is not anymore supported by swig 2.0.
>>
>> Same for octave 4.0, and maybe other languages.
> Not everything that worked with swig2.0 works with swig3.0 (e.g.,
> subversion's swig bindings).  Why can't both be shipped?
I think they could be shipped but shouldn't.

For one swig 2.0 it not maintained upstream anymore.
The other thing is that swig 3.0 should be usable to build subversion,
so I have to get this fixed instead of using swig 2.0 as the way out.

Greetings, Torsten

Bug#808268: marco: context menu "Open With" list fails to maintain focus

[Mike Gabriel]

Control: tags -1 moreinfo

Hi Michael,

thanks for reporting your issue.

On  Fr 18 Dez 2015 02:22:11 CET, Michael wrote:


Package: marco
Version: 1.8.2+dfsg1-6
Severity: normal

Dear Maintainer,

I am a novice and apologize if I have reported for the wrong package.

1. I focus on (highlight) a file in a Caja window that I want to open
with Leafpad.

2. I press the context menu key and the context menu appears, showing
the "Open With" option.

3. I arrow down to "Open With" in the context menu and then I arrow
right to the list of available programs.

4. I try to arrow down in the "Open With" list to Leafpad, but half of
the time the focus returns to Open With in the main context menu before
I can reach Leafpad in the list. The list remains visible, but
unselected. The list can be reselected, but the same problem recurs.

I have noticed this immediately after installing Transmission.


I cannot reproduce the above.

Can you:

  o install a fresh system / virtual machine
  o install MATE from scratch on that system
  o try to reproduce your bug

I am quite certain that the issue is not reproducible on a fresh  
installation and that it somehow relates to settings in your user  
profile.


Thanks+Greets,
Mike
--

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

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

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de


pgpg_0jaPMDuc.pgp
Description: Digitale PGP-Signatur

Bug#808576: rustc cannot compile programs: "unrecognized relocation in section"

[Robbie Harwood]

Package: rustc
Version: 1.5.0+dfsg1-1
Severity: important

Dear Maintainer,

When I try to build any rust program, the following occurs:

$ cat > main.rs
fn main() {
  print!("Hello, world!\n");
  }
$ rustc main.rs
error: linking with `cc` failed: exit code: 1
note: "cc" "-Wl,--as-needed" "-m64" "-L" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib" "main.0.o" "-o" "main" 
"-Wl,--gc-sections" "-pie" "-nodefaultlibs" "-L" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-L" 
"/home/frozencemetery/.rust/lib/x86_64-unknown-linux-gnu" "-L" 
"/home/frozencemetery/lib/x86_64-unknown-linux-gnu" "-Wl,-Bstatic" 
"-Wl,-Bdynamic" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-35c36e89.rlib" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcollections-35c36e89.rlib" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_unicode-35c36e89.rlib" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/librand-35c36e89.rlib" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc-35c36e89.rlib" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc_jemalloc-35c36e89.rlib" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-35c36e89.rlib" 
"/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-35c36e89.rlib" "-l" "dl" 
"-l" "pthread" "-l" "gcc_s" "-l" "rt" "-l"
  "pthread" "-l" "c" "-l" "m" "-l" "compiler-rt"
note: /usr/bin/ld: 
/usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc_jemalloc-35c36e89.rlib(jemalloc.pic.o):
 unrecognized relocation (0x2a) in section `.text.malloc_conf_init'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status

error: aborting due to previous error
$

Please let me know if I can provide more information.  Thanks!

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (800, 'stable-updates'), (800, 'stable'), (600, 'testing'), (400, 
'unstable'), (200, '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 rustc depends on:
ii  libc62.19-18+deb8u1
ii  libstd-rust-dev  1.5.0+dfsg1-1

Versions of packages rustc recommends:
ii  rust-gdb  1.5.0+dfsg1-1

Versions of packages rustc suggests:
pn  rust-doc  

-- no debconf information

Bug#806594: python-skbio: issues fixed, upload required

[Kevin Murray]

Hi all,

On 13:22 21/12, Kevin Murray wrote:
> Hi Andreas,
> 
> On 09:07 06/12, Andreas Tille wrote:
> > Hi Kevin,
> > 
> > any news about building the docs?  I have reset the target distribution to
> > UNRELEASED since it does not build in a pbuilder chroot.
> > 
> 
> I'm still stuck on this one. Does someone with more Debian python knowledge 
> than
> I want to have a look? I'm sure it's some silly oversight on my behalf, but I
> seem to be having issues with PYTHONPATH during the build of the docs (the
> skbio module is imported by sphinx's conf.py). My latest attempt is pushed to:
> 
> ssh://git.debian.org/git/debian-med/python-skbio.git
> 

I've fixed the issues I was having after I worked out how to drop to a shell.
Could I please get someone to upload this package?


---
Kevin Murray
0xA4B4EE6A

Bug#808575: maybe use $PAGER when showing choices in command line mode

[積丹尼 Dan Jacobson]

Package: aptitude
Version: 0.7.5-3
Severity: wishlist

Got a problem here in command line mode.

  Upgrade the following packages:
7)  libapt-pkg-perl [0.1.29+b4 (now) -> 0.1.29+b5 (unstable)]
8)  libcairo-perl [1.106-1 (now) -> 1.106-1+b1 (unstable)]
9)  libcommon-sense-perl [3.74-1 (now) -> 3.74-1+b1 (unstable)]
...
38) libyaml-syck-perl [1.29-1 (now) -> 1.29-1+b1 (unstable)]
39) perl-tk [1:804.033-1 (now) -> 1:804.033-1+b1 (unstable)]



Accept this solution? [Y/n/q/?] **ALSO NOTE THE BIG 3 line gap above***

Well what about the first few? They have flown off my screen. So maybe
aptitude should honor PAGER?

The man page says

   PAGER
   If this environment variable is set, aptitude will use it to
   display changelogs when "aptitude changelog" is invoked. If not
   set, it defaults to more.

so maybe it should kick in optionally also in this case.

One notes one can still use less(1) $LESS with

   -F or --quit-if-one-screen
  Causes less to automatically exit if the entire file can be dis-
  played on the first screen.

Bug#605090:

[bancfc]

Is there other ways to deal with unwanted network stack modules like 
Appletalk besides going in and manually disabling them in config before 
compiling?


Is disabling module loading enough?

Please give some insight if its okay to discuss.

Bug#808574: wrap-and-sort: option to not modify any files

[Paul Wise]

Package: devscripts
Severity: wishlist
File: /usr/bin/wrap-and-sort
User: devscri...@packages.debian.org
Usertags: wrap-and-sort
Control: affects -1 check-all-the-things
Control: user check-all-the-thi...@packages.debian.org
Control: usertags -1 + new-check

I would like to add a new check to check-all-the-things that would
report any files that need to be modified by wrap-and-sort -sabt but
haven't yet. For that to be possible, wrap-and-sort needs an option
(maybe --dry-run) to prevent modification of any files.

https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#743581: crimson: diff for NMU version 0.5.2-1.1

[Markus Koschany]

Control: tags 743581 + pending

Dear maintainer,

I've prepared an NMU for crimson (versioned as 0.5.2-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards,

Markus
diff -Nru crimson-0.5.2/debian/changelog crimson-0.5.2/debian/changelog
--- crimson-0.5.2/debian/changelog	2015-12-21 06:11:52.0 +0100
+++ crimson-0.5.2/debian/changelog	2015-12-21 06:06:10.0 +0100
@@ -1,3 +1,20 @@
+crimson (0.5.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to source format 3.0 (quilt)
+  * Use compat level 9 and require debhelper >= 9.
+  * wrap-and-sort -sa.
+  * Declare compliance with Debian Policy 3.9.6.
+  * Fix lintian error global-data-in-games-directory.
+- debian/rules: Remove global data in /usr/share/games.
+- Install desktop file and icons to /usr/share/applications and
+  /usr/share/pixmaps. (Closes: #743581)
+  * Fix Lintian warning description-synopsis-starts-with-article.
+  * Add desktop-file.patch and create a valid desktop file. Add keywords.
+  * Add man-page-spelling.patch and fix minor spelling mistakes.
+
+ -- Markus Koschany   Mon, 21 Dec 2015 05:48:56 +0100
+
 crimson (0.5.2-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru crimson-0.5.2/debian/compat crimson-0.5.2/debian/compat
--- crimson-0.5.2/debian/compat	2015-12-21 06:11:52.0 +0100
+++ crimson-0.5.2/debian/compat	2015-12-21 06:06:10.0 +0100
@@ -1 +1 @@
-5
+9
diff -Nru crimson-0.5.2/debian/control crimson-0.5.2/debian/control
--- crimson-0.5.2/debian/control	2015-12-21 06:11:52.0 +0100
+++ crimson-0.5.2/debian/control	2015-12-21 06:06:10.0 +0100
@@ -2,14 +2,21 @@
 Section: games
 Priority: optional
 Maintainer: Uwe Hermann 
-Build-Depends: cdbs, debhelper (>= 5), libsdl1.2-dev (>= 1.2.5), libsdl-mixer1.2-dev (>= 1.2.1-2.1), libsdl-ttf2.0-dev
-Standards-Version: 3.8.0
+Build-Depends:
+ cdbs,
+ debhelper (>= 9),
+ libsdl-mixer1.2-dev (>= 1.2.1-2.1),
+ libsdl-ttf2.0-dev,
+ libsdl1.2-dev (>= 1.2.5)
+Standards-Version: 3.9.6
 Homepage: http://crimson.seul.org/
 
 Package: crimson
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: A hex-based tactical game
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends}
+Description: hex-based tactical game
  Crimson Fields is a hex-based tactical war game in the tradition of
  Battle Isle (tm). Two players command their units on a map of hexagons,
  trying to accomplish mission objectives ranging from defending important
@@ -18,4 +25,3 @@
  the computer. Tools are available to create custom maps and campaigns.
  You can also play the original Battle Isle maps if you have a copy of
  the game.
-
diff -Nru crimson-0.5.2/debian/copyright crimson-0.5.2/debian/copyright
--- crimson-0.5.2/debian/copyright	2015-12-21 06:11:52.0 +0100
+++ crimson-0.5.2/debian/copyright	2015-12-21 06:06:10.0 +0100
@@ -33,7 +33,7 @@
 Copyright: © 2004 Dave Fancella 
 License:
License for the soundtrack
-   
+
Quite simply, you have two choices. The music, as distributed with
Crimson Fields, is covered under the GNU General Public License, same
version(s) as the game itself. If you choose to separate the music from
@@ -46,42 +46,42 @@
recommended that you do so, because otherwise you may find yourself with
the GPL unenforceable on the music, and you will have no license for the
music otherwise.
-   
+
Copyright Notice
-   
+
	default.mid - Default Symphony
   		(c) 2004 by Dave Fancella, david.fance...@seul.org
-   
+
The Creative Commons License chosen guarantees all the same rights of
the GPL with the exception of a requirement of attribution.
-   
+
Creative Commons License
-   
+
http://creativecommons.org/licenses/by-sa/1.0/
-   
+
Attribution-ShareAlike 1.0
-   
+
You are free:
-   
+
* to copy, distribute, display, and perform the work
* to make derivative works
* to make commercial use of the work
-   
+
Under the following conditions:
-   
+
Attribution. You must give the original author credit.
-   
+
Share Alike. If you alter, transform, or build upon this work, you may
distribute the resulting work only under a license identical to this
one.
-   
+
  * For any reuse or distribution, you must make clear to others the
license terms of this work.
  * Any of these conditions can be waived if you get permission from
the author.
-   
+
Your fair use and other rights are in no way affected by the above.
-   
+
This is a human-readable summary of the Legal Code (the full license).
 
 ---
@@ -92,7 +92,7 @@
 License:
Copyright (c) 2003 by Bitstream, Inc. All Rights Reserved. Bitstream
Vera is a trademark of Bitstream, Inc.
-   
+
Permission is hereby granted, free of charge, to any person obtaining
a copy of the fonts accompa

Bug#808573: network-manager: undefined symbol: g_udev_enumerator_new

[Mike Dupont]

Subject: network-manager: undefined symbol: g_udev_enumerator_new
Package: network-manager
Version: 1.0.8-2
Justification: renders package unusable
Severity: grave

Job for NetworkManager.service failed because the control process
exited with error code. See "systemctl status NetworkManager.service"
and "journalctl -xe" for details.


● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service;
enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Sun 2015-12-20 23:03:04
CST; 4min 30s ago
  Process: 17718 ExecStart=/usr/sbin/NetworkManager --no-daemon
(code=exited, status=127)
 Main PID: 17718 (code=exited, status=127)

/usr/sbin/NetworkManager --no-daemon
/usr/sbin/NetworkManager: symbol lookup error:
/usr/sbin/NetworkManager: undefined symbol: g_udev_enumerator_new



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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.10.2-1
ii  init-system-helpers1.24
ii  isc-dhcp-client4.3.3-5
ii  libbluetooth3  5.36-1
ii  libc6  2.19-22
ii  libdbus-1-31.10.2-1
ii  libdbus-glib-1-2   0.102-1
ii  libglib2.0-0   2.46.1-2
ii  libgnutls-deb0-28  3.3.18-1
ii  libgudev-1.0-0 1:162-2.2
ii  libmm-glib01.0.0-4
ii  libndp01.4-2
ii  libnewt0.520.52.18-1+b1
ii  libnl-3-2003.2.26-1
ii  libnl-genl-3-200   3.2.26-1
ii  libnl-route-3-200  3.2.26-1
ii  libnm0 1.0.6-1
ii  libpam-systemd 227-2
ii  libpolkit-agent-1-00.105-13
ii  libpolkit-gobject-1-0  0.105-13
ii  libreadline6   6.3-8+b3
ii  libsoup2.4-1   2.52.1-1
ii  libsystemd0227-2
ii  libteamdctl0   1.18-1
ii  libuuid1   2.27.1-1
ii  lsb-base   9.20150917
ii  policykit-10.105-13
ii  udev   227-2
ii  wpasupplicant  2.3-2

Versions of packages network-manager recommends:
ii  crda3.13-1
ii  dnsmasq-base2.75-1
ii  iptables1.4.21-2+b1
ii  iputils-arping  3:20121221-5+b2
ii  modemmanager1.0.0-4
ii  ppp 2.4.7-1+1

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.32~rc+dfsg-1
pn  libteam-utils  

-- no debconf information


-- 
James Michael DuPont

Bug#799778: digikam: Not able to import pictures from CANON EOS350D after upgrading from 3.5

[Steve M. Robbins]

On Tue, 22 Sep 2015 15:34:20 +0200 Etienne BRETTEVILLE 
 wrote:

> After upgrading from LinuxMintDebianEdition LMDE 1 (based on debian 7) to 
LMDE2
> based on debian Jessie, digikam has been updated to 4.4.0 instead of 3.5.x.
> 
> Since then I'm no longer able to import my pictures from my CanonEOS350D 
using
> the importation tool from digikam.
> 
> You can see the error message in the screenshot here:
> https://framapic.org/AiUtTFceoQN0/lexIQ4R7
> 
> What about introducing the latest revsion of digikam, 4.13.0?!

I just uploaded 4.14 today.  If you are in a position to try that out, I'd be 
very glad to know if it fixes this issue.

If not, then as a work-around: I wonder if you can set the camera to act as a 
USB device and import from the filesystem?

Finally, while I realize this makes digikam unusable for you, the  bug 
severity "grave" is intended for a package completely unusable by most users.  
I don't believe it applies in this case.

Best,
-Steve



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

Bug#803456: digikam: Please package 5.0.0-beta1 that has been published for kde5

[Steve M. Robbins]

On Fri, 30 Oct 2015 10:55:05 +0100 valette  wrote:
> Package: digikam
> Severity: grave
> Justification: renders package unusable
> 
> digikam is not installable anymore in unstable or testing. 

That has just been fixed with upload of 4.14.

> The 5.0.0 is.

At this point, I expect we will wait for 5.x to emerge from beta status before 
packaging.

-Steve


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

Bug#808572: giflib-tools: gitinter is no longer shipped with the package

[Francois Marier]

Package: giflib-tools
Version: 5.1.1-0.2
Severity: normal

It looks like the gifinter tool was removed in version 5.1 of the
giflib-tools package. However, it's still in upstream CVS:

  
http://giflib.cvs.sourceforge.net/viewvc/giflib/giflib/util/gifinter.c?view=log

Was that a mistake? the fuzzyocr package makes use of that utility when
analyzing spam messages with gif files and complains about it being missing:

  Dec 16 11:05:30 hostname spamd[19002]: FuzzyOcr: Cannot exec gifinter, 
skipping image

Francois

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

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

Versions of packages giflib-tools depends on:
ii  libc6   2.21-4
ii  libgif7 5.1.1-0.2
ii  libperl4-corelibs-perl  0.003-2
ii  perl5.20.2-6

giflib-tools recommends no packages.

giflib-tools suggests no packages.

-- no debconf information

Bug#808320: Proposed fix with breaks / replaces

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

> +Replaces: libarrayfire-cpu-dev (<< 3.2.1+dfsg1-6) +Breaks:
> libarrayfire-cpu-dev (<< 3.2.1+dfsg1-6)

please check this wiky, that should have the most common use-cases
https://wiki.debian.org/PackageTransition

cheers,

G.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWd3sxAAoJEPNPCXROn13ZH3gP/0STTxRv6pNCQQpxdOKsgJgk
ClQUDbE8hdzKDIAFLCXgWnv1Hxq8GO0Z5xkAQoCAefzZd4hv2Q6ZaBb3v2K8OE/c
SVhkvRjr8JpZqbmCHeyk7wAmyrDHjhuofJge9M4NOOCuOLeac5lh8Fwo/O6i8bnN
MvqdYxWsyj218FKmOTZ55a/fR3HQ2yqiLXYBa+yNm0hdT0PF4eiOcgYDzR0oewtD
nIJAkkBOlRiw8tyLoJbn1UAd8nIughA651Xc/A+TSPpDtufUJdEbTdSORJyAiCYC
xXMxtZypZ1gHEdTthul+L3rcIjtgyUm6a1+slG2c76s39/nUuJgxDfpBtHkQNb//
lkxKSAEkIpyimNEw5PcItj1vrsNtFG1nwlTE3uqoSyzP1RNXRbsv6I7b0MQW/7eB
ORjL2vbFArgWlIdV8bMBL3fJaSFSpDX9kqZw4f99vTiomUPfGj9ZLZjyvg5vzAHb
Ds62w8dZAgS+BuTE7Og0LD//aJHn3s9D+l/QltAkNP5bl2OqO9Ku3F8y2ftcNLGG
9W+2HjdiXqnf8f8p1TIsI0ewhXFwJ/4QKlxQNEgMmip8iW7OxCZ9BuHa9MX0EujD
ucyR1BcXdgZsjDR8arG7J6MHPDwD+b70zv/qRwBsoB7pnq7qy2qyou0zs5jTUGqp
RUylV5wcr/oTA/o4dHAb
=xGg2
-END PGP SIGNATURE-

Bug#808571: Does not support travelling across timezones

[martin f krafft]

Package: redshift
Version: 1.10-5
Severity: normal

Travelling through several timezones, I found that redshift neither
updates its understanding of what nighttime is (based on the
timezone), nor does it make any efforts to re-acquire its position.
Maybe it could instead listen to appropriate events, or just reset
itself every hour or so.

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

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

Versions of packages redshift depends on:
ii  libc6  2.21-4
ii  libdrm22.4.65-3
ii  libglib2.0-0   2.47.1-1
ii  libx11-6   2:1.6.3-1
ii  libxcb-randr0  1.11.1-1
ii  libxcb11.11.1-1
ii  libxxf86vm11:1.1.4-1

Versions of packages redshift recommends:
ii  geoclue-2.0  2.4.0-2

redshift suggests no packages.

-- debconf-show failed


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#485832: aptitude: doesn't re-read apt.conf after dpkg run

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo
Control: severity -1 minor


Hi all,

2008-06-11 19:10 Jamey Sharp:

Package: aptitude
Version: 0.4.11.3-1
Severity: normal

After removing a package that installed files in /etc/apt/apt.conf.d,
such as apt-listchanges, aptitude still uses the configuration settings
from that package. In this case, it tried to invoke apt-listchanges at
the beginning of the next dpkg run in the same session, but that program
was no longer installed.


I tried to reproduce this (with apt-listchanges and apt-listbugs, from
the merged bug report).  When purging the file that they install is
removed now, rather than disabled.

With apt-listchanges, it just emits an error:

 Performing actions...
 /bin/sh: 1: /usr/bin/apt-listchanges: not found
 (Reading database ... 210066 files and directories currently installed.)

So the problem looks very very minor, perhaps with apt-listbugs or
others is more severe.

apt assumes that sessions are not "reused" since it works by single
invokations, but aptitude is mostly interactive.

I don't think that it's very feasible to re-read the config, because
after reading the config from apt in the beggining, aptitude adds
configuration on top (temporary for that session only, sometimes), so it
would basically need to be "restarted" again internally even if not
explicitly, so I don't think that there's much advantage.

The number of applications modifying apt's config or the frequency of
their installations should not very high, perhaps once every few years
in each system even if using these tools, so one of the suggested
solutions of re-reading it after every installation of any package seems
quite overkill to me, and the time investment needed quite high for
little benefit.

So at the moment I am leaning towards a +wontfix, leaving it open for
further consideration.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#808570: FTBFS: upstream bug causing FTBFS on i386

[Kevin Murray]

Package: axe-demultiplexer
Version: 0.3.0+dfsg-2
Severity: important
Tags: upstream

Dear Maintainer,

An upstream bug prevents tests passing on 32-bit systems. Upstream has fixed
this in the latest release.

Cheers,
Kevin


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

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

Versions of packages axe-demultiplexer depends on:
ii  libc62.21-4
ii  libgsl2  2.1+dfsg-2
ii  libqes0  0.1.20-1

axe-demultiplexer recommends no packages.

axe-demultiplexer suggests no packages.

-- no debconf information

Bug#781660: youtube-dl: --no-part can't handle fully downloaded files: KeyError: u'total_bytes'

[Rogério Brito]

Hi, Jakub.

On Dec 20 2015, Jakub Wilk wrote:
> * Jakub Wilk , 2015-04-01, 13:16:
> >When you use the --no-part option, and try to download a video that has
> >been already downloaded, youtube-dl fails with an exception:
> [...]
> >KeyError: u'total_bytes'
> 
> It no longer happens in the current version.


Thanks a lot for confirming this bug is closed.

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#110685: (Optional) apt-get clean after install

[Manuel A. Fernandez Montecelo]

2001-08-30 17:27 Steve Greenland:

Package: aptitude
Version: 0.2.5.3-2
Severity: wishlist

It would be nice if there was an option to clean (not just auto-clean)
after installing. Note the difference: clean removes all (successfully
installed?) .deb files from /var/cache/apt/archives, not just the ones
that are no longer available. Should be trivial, as all you need to do
is call 'apt-get clean'.

Hmm, apt supports this for dselect via the DSelect::Clean option (both
autoclean and clean), maybe you can hook into that? Or have Jason
provide a general hook?


2002-04-12 05:06 Andrew Pimlott:

This is just a "vote" for this wishlist bug, since it seems to have
been forgotten.  I think most users would want this behavior.



This has been implemented now, it will be present in the next release.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#782150: pbuilder: pdebuild fails with --changes-option=-[AaBbFg] or just -g

[Mattia Rizzolo]

control: tag -1 patch

Hi Ondřej!

Sorry for the late reply...

On Wed, Apr 08, 2015 at 04:15:23PM +0200, Ondřej Surý wrote:
> pdebuild doesn't work with -g or with any binary option given in

the -g bit was fixed some releases ago as part of another bug.

> --changes-option, simple workaround fixes that:

--changes-option is something totally new for me, instead.  I usually
pass only -g/-b/ without expliciting those are flags for
dpkg-genchanges, since dpkg-buildpackage seems to be is clever enough.

> echo "dpkg-buildpackage -S -us -uc -r${BUILDSOURCEROOTCMD} $DEBBUILDOPTS" | \
> perl -pe 's/(^|\s|=)-[AbBFg](\s|$|'\'')/$1-S$2/g' | \
> /bin/bash
> 
> Add = as a start delimiter and ' as end delimiter and -g to the list
> of stripped options.  It's probably not a complete solution, but it
> helps right now to build with --changes-option=-g that I use almost

that regex is tricky (see #802800), can you please check whether the
attached patch (which just adds '|=' in the the (^|\s)) works fine for
you?
it looks quite harmless, but you never know...

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diff --git a/pdebuild b/pdebuild
index fa76a9d..15522aa 100644
--- a/pdebuild
+++ b/pdebuild
@@ -80,7 +80,7 @@ else
log.w "Unmet build-dependency in source"
 fi
 echo "dpkg-buildpackage -S -d -us -uc -r${BUILDSOURCEROOTCMD} 
$DEBBUILDOPTS" | \
-   perl -pe 's/(^|\s)['\'']?-[AbBFgG]['\'']?(\s|$)/$1$2/g' | \
+   perl -pe 's/(^|\s|=)['\'']?-[AbBFgG]['\'']?(\s|$)/$1$2/g' | \
/bin/bash
 ${PBUILDERROOTCMD} \
${PDEBUILD_PBUILDER} \


signature.asc
Description: PGP signature

Bug#808569: ITP: awsshell -- The interactive productivity booster for the AWS CLI

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)" 

* Package name: awsshell
  Version : 0.0.1
  Upstream Author : James Saryerwinnie
* URL : https://github.com/awslabs/aws-shell
* License : Apache-2
  Programming Lang: python
  Description : The interactive productivity booster for the AWS CLI

 awsshell provides a interactive environment to control AWS services.
 The following features are supported:
 .
 * Auto completion of commands and options
 * Shorthand auto completion
 * Server side auto completion
 * Fuzzy searching
 * Inline documentation
 * Fish-style auto suggestions
 * Command history
 * Toolbar options
 * Dot commands
 * Executing Shell Commands

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


signature.asc
Description: PGP signature

Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

[Ben Hutchings]

On Mon, 2015-12-21 at 12:56 +1030, Arthur Marsh wrote:
> > This is no way an acceptable patch.  The driver needs to be converted
> > properly to the Linux 2.6+ device model, instead of adding further
> > kluges to it.
> > 
> > Ben.
> > 
> 
> Thanks, that patch wasn't provided by me. The old driver just broke 
> during other updates and that patch was provided as a workaround to me.

I understand, but I didn't want you to get the false impression that
this was properly solved already.

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that there are so many of them.

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

Bug#448334: Should switch to pbuilder-satisfydepends-classic when aptitude is not installable

[Mattia Rizzolo]

tag 448334 + wontfix
thanks

On Sat, Jan 02, 2010 at 03:51:34PM +0100, Loïc Minier wrote:
> Hi
> 
> On Sun, Oct 28, 2007, Robert Luberda wrote:
> > In current sid aptitude isn't installable, and pdebuild fails: 
> > 
> > The following packages have unmet dependencies:
> >   aptitude: Depends: libapt-pkg-libc6.6-6-4.4 but it is not installable
> > E: Broken packages
> > E: pbuilder-satisfydepends failed.
> > 
> > To get around the problem I set PBUILDERSATISFYDEPENDSCMD to 
> > "/usr/lib/pbuilder/pbuilder-satisfydepends-classic", but I think it would be
> > nice if pbuilder-satisfydepends could automatically switch to
> > pbuilder-satisfydepends-classic in this case.
> 
>  I don't think it's nice to change the core behavious of pbuilder
>  automatically; what you did is the right thing, and that's all which
>  should be done.  I think aptitude should be installed on pbuilder
>  create and kept on pbuilder update instead of being installed during
>  each build (as the code allows in the current version but it might or
>  might not be the case for you).  I committed a change to add/keep
>  aptitude in the environment when using the aptitude resolver, and not
>  otherwise.
> 
>  Is this good enough to close this bug?

I totally agree with Loïc here.
automagically change such a thing at runtime is Bad™.
nowadays if aptitude becomes uninstallable, either it's already
installed in the chroot and so we don't care it's not installable, or
just switch resolver.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

[Arthur Marsh]

This is no way an acceptable patch.  The driver needs to be converted
properly to the Linux 2.6+ device model, instead of adding further
kluges to it.

Ben.



Thanks, that patch wasn't provided by me. The old driver just broke 
during other updates and that patch was provided as a workaround to me.


Arthur.

Bug#806594: [Debian-med-packaging] Skbio upload?

[Kevin Murray]

Hi Andreas,

On 09:07 06/12, Andreas Tille wrote:
> Hi Kevin,
> 
> any news about building the docs?  I have reset the target distribution to
> UNRELEASED since it does not build in a pbuilder chroot.
> 

I'm still stuck on this one. Does someone with more Debian python knowledge than
I want to have a look? I'm sure it's some silly oversight on my behalf, but I
seem to be having issues with PYTHONPATH during the build of the docs (the
skbio module is imported by sphinx's conf.py). My latest attempt is pushed to:

ssh://git.debian.org/git/debian-med/python-skbio.git

Thanks!

Cheers,
Kevin

---
Kevin Murray
0xA4B4EE6A

Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

[Ben Hutchings]

Control: tag -1 - patch

On Mon, 2015-12-21 at 12:17 +1030, Arthur Marsh wrote:
> Package: src:linux
> Version: 4.3.3-2
> Severity: normal
> Tags: upstream patch
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
> 
> Attempting to load a kernel later than 4.2.0.
> 
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Reported the problem to the developer and linux-scsi mailing list, a patch
> was created that worked but it has not been applied upstream even though I 
> have confirmed that the patch works.]
[...]

This is no way an acceptable patch.  The driver needs to be converted
properly to the Linux 2.6+ device model, instead of adding further
kluges to it.

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that there are so many of them.

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

Bug#808568: ca-certificates: show certificates subjects

[Christoph Anton Mitterer]

Package: ca-certificates
Version: 20151214
Severity: wishlist


Hi.

Right now, the selection dialog when reconfiguring
the enabled certificates shows the pathnames of their
files, which in turn are apparently based on the OU
filed.
This seems in many cases pretty unclear, e.g.
"mozilla/ePKI_Root_Certification_Authority.crt"

It would help IMHO, if additionally the whole subject DN
would be printed, e.g.
"/C=TW/O=Chunghwa Telecom Co., Ltd./OU=ePKI Root Certification Authority"

Given that Mozilla includes for money basically any
CA nowadays, even such which are inherently untrustworthy
it seems especially helpful, if the C filed would
be shown, so that people who don't want to make themselves
unnecessarily victims of totalitarian countries, can
more easily sort out CAs from there.

Thanks,
Chris.

Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

[Arthur Marsh]

Package: src:linux
Version: 4.3.3-2
Severity: normal
Tags: upstream patch

Dear Maintainer,

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

   * What led up to the situation?

Attempting to load a kernel later than 4.2.0.

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

Reported the problem to the developer and linux-scsi mailing list, a patch
was created that worked but it has not been applied upstream even though I 
have confirmed that the patch works.

See: 

https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg45283.html

diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
index d7ffd66..8321c46 100644
--- a/drivers/pci/pci-driver.c
+++ b/drivers/pci/pci-driver.c
@@ -391,6 +391,7 @@ int __weak pcibios_alloc_irq(struct pci_dev *dev)
 {
 return 0;
 }
+EXPORT_SYMBOL_GPL(pcibios_alloc_irq);

 void __weak pcibios_free_irq(struct pci_dev *dev)
 {
diff --git a/drivers/scsi/eata.c b/drivers/scsi/eata.c
index 227dd2c..7e6eaf8 100644
--- a/drivers/scsi/eata.c
+++ b/drivers/scsi/eata.c
@@ -1061,6 +1061,7 @@ static void enable_pci_ports(void)
driver_name, dev->bus->number, dev->devfn);
 #endif

+pcibios_alloc_irq(dev);
 if (pci_enable_device(dev))
 printk
 ("%s: warning, pci_enable_device failed, bus %d devfn 0x%x.\n",
@@ -1520,6 +1521,7 @@ static void add_pci_ports(void)
 if (!(dev = pci_get_class(PCI_CLASS_STORAGE_SCSI << 8, dev)))
 break;

+pcibios_alloc_irq(dev);
 if (pci_enable_device(dev)) {
 #if defined(DEBUG_PCI_DETECT)
 printk

## end 

   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge 
[1106:0204]
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge [1106:0204]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: agpgart-amd64

00:00.1 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge 
[1106:1204]
Subsystem: VIA Technologies, Inc. K8M800 Host Bridge [1106:1204]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

00:0f.0 IDE interface [0101]: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 07) 
(prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. 
VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE [1106:0571]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: pata_via

00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 
Controller [1106:3038] (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller 
[1106:3038]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 
Controller [1106:3038] (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller 
[1106:3038]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:10.2 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 
Controller [1106:3038] (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller 
[1106:3038]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:10.3 USB controller [0c03]: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 
Controller [1106:3038] (rev 90) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller 
[1106:3038]
Control: I/O+ Mem+ BusMa

Bug#808563: really should be serious bug: data loss

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Mon, 2015-12-21 at 09:18 +0800, 積丹尼 Dan Jacobson wrote:
> The first time it happened I couldn't boot again without a fsck.ext4 via
> a rescue CD!

I'm so tired of this routine.

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that there are so many of them.

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

Bug#630932: pbuilder: --preserve-buildspace is ineffective

[Mattia Rizzolo]

control: tag -1 - patch + wontfix moreinfo
control: close -1

On Sun, Jun 19, 2011 at 01:27:10AM +0200, Toni Mueller wrote:
> while trying to debug a problem with my pbuilder configuration, I found
> that the build space (/var/cache/pbuilder/build) was always deleted.
> After some debugging, I contrived the following patch that solves the
> problem for me:

ahem, sadly --preserve-buildplace has a quite different purpose.
I find that sadly, since also the description is quite hard to grasp
(improvments welcome, I don't think I'm able to explain that better),
and imho that use case is particularly uncommon between pbuilder users:

   --preserve-buildplace
  Do not clean the --buildplace if it has the same contents as  the
  .tar.gz file, and no modifications are done.

  For preserving the build place for --create and --update targets,
  see --debug option.

  As with --no-targz, suppresses appending pbuilder's process ID to
  the --buildplace.

  This  is useful if you want to attempt to build a large number of
  packages successively, but you expect that many  of  them  cannot
  have their build dependencies satisfied.

  It  will clean up the build place on failure, or after a success‐
  ful build.

Though, if your problem is about the configuration for the update/create
phases, --debug will preserv the unpacked chroot in case of failures; in
the other cases, I'd like to suggest using a hook to inspect what's
going on.


I'm sorry for how long it took to get this reply, but as you might guess
pbuilder was unmaintained in the last few years.
If you want to share what's your use case more in details, I'd be glad
to work on a better solution.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#808566: lintian: Bogus tag on ddeb Build-Ids field in udebs

[Guillem Jover]

Package: lintian
Version: 2.5.39
Severity: normal

Hi!

When building libbsd with the latest debhelper with ddebs support, I
get this tag:

  I: libbsd0-udeb udeb: unknown-field-in-control build-ids

Thanks,
Guillem

Bug#793101: Yubikey core error: no yubikey present

[meskio]

Package: yubikey-personalization
Followup-For: Bug #793101

I just found out that my yubikey is a U2F-only key and the
yubikey-personalize tool can't be used with it:
https://www.yubico.com/products/yubikey-hardware/fido-u2f-security-key/#toggle-id-10

I'm not sure if is the same case for the original publisher of this bug,
as his usb-id is not the same than mine.

Sorry for the noise.

Bug#808565: broadcom-sta: many frame errors seemingly cause intolerable ssh

[Stephen Farrell]

Source: broadcom-sta
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

Standard ubuntu (now 15.10, kernel 4.2.0.22) install on Lenovo 
yoga pro 3. 

(First time using reportbug, so I'll add more text here. Sorry
if that's wrong.)

The issue is that WiFi connects fine, and is usable for web and
mail but intolerable for e.g. ssh sessions. The only "symptom"
I'm seeing is that ifconfig reports many frame errors, sometimes
about 10% of the #packets rx'd, sometimes 200% of that. A typical
ssh session (even to machines local on my LAN) stalls within a
few seconds/minutes and repeatedly does that. It is just possible
to login and run an update/reboot, but doing more in an ssh 
session isn't feasible. Netstat shows bytes queued up (on the
lenovo yoga machine) when this is happening.

I am seeing very poor link quality (currently 38/70) and 
signal level (-72 dBm) as reported by iwconfig even 
though I'm only ~10m from the access point and no other
device has any similarly bad signal.

All wired connections are fine. No other device on my n/w has
this issue. 

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

WiFi with the wl.ko driver always has this problem on my LAN.
I have seen similar issues on other WiFi networks, but in my
LAN the signal is probably weaker than in my office environment.

Building and installing the more recent code from broadcom
didn't help. (Sometimes slightly better, sometimes worse, 
never perfect.) I tried but failed to find a way to use 
ndiswrapper but maybe that's outmoded these days. I did not
try other linux drivers as the documentation always said
that they did not support the bcm4352. 

I suspect this is related to Bob Briscoe's theory [1] that 
the driver or chipset is trying for too high a speed even if 
the quality of the connection is not sufficiently good.
(Note though that the bug is not the same - I do get 
connection, just v. poor quality.)

   [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786699#10

   * What was the outcome of this action?

No improvement.

   * What outcome did you expect instead?

Improvement:-)

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


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

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

Bug#808563: really should be serious bug: data loss

[積丹尼 Dan Jacobson]

The first time it happened I couldn't boot again without a fsck.ext4 via
a rescue CD!

Bug#743638: RFP: shairport -- Play music streamed from iTunes/iPads/iPods

[Daniel Carter]

On Sun, 20 Dec 2015 09:47:23 + Chris Boot  wrote:
>
> I would *definitely* appreciate patches from anyone who wishes to help,
> or even co-maintenance.

Nice work.

I just put a bit of effort into getting the systemd service side of things
working.  Happy to contribute those, see attached diff. (not sure how
alioth works, cant see how to do a pull request there?).  The patch for the
systemd unit path i have done a pull request for, so if that is accepted
you can drop that.

Though perhaps you intend this not to be a daemon package?

Regards,
Dan.
diff --git a/debian/control b/debian/control
index d7b5e00..c777519 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: shairport-sync
 Section: sound
 Priority: extra
 Maintainer: Chris Boot 
-Build-Depends: debhelper (>= 9), dh-autoreconf, dh-systemd, libasound2-dev, 
libavahi-client-dev, libconfig-dev, libdaemon-dev, libpopt-dev, libpulse-dev, 
libsoxr-dev, libssl-dev
+Build-Depends: debhelper (>= 9), dh-autoreconf, dh-systemd, systemd, 
libasound2-dev, libavahi-client-dev, libconfig-dev, libdaemon-dev, libpopt-dev, 
libpulse-dev, libsoxr-dev, libssl-dev
 Standards-Version: 3.9.6
 Homepage: https://github.com/mikebrady/shairport-sync
 Vcs-Git: git://anonscm.debian.org/collab-maint/shairport-sync.git
@@ -10,7 +10,7 @@ Vcs-Browser: 
http://anonscm.debian.org/cgit/collab-maint/shairport-sync.git/
 
 Package: shairport-sync
 Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, adduser
 Description: AirPlay audio player
  Plays audio streamed from iTunes, iOS devices and third-party AirPlay
  sources such as ForkedDaapd and others. Audio played by a Shairport
diff --git a/debian/patches/correct-systemd-unit-path.diff 
b/debian/patches/correct-systemd-unit-path.diff
new file mode 100644
index 000..84b8f6c
--- /dev/null
+++ b/debian/patches/correct-systemd-unit-path.diff
@@ -0,0 +1,36 @@
+--- a/Makefile.am
 b/Makefile.am
+@@ -61,6 +61,6 @@ if INSTALL_SYSTEMV
+   [ -f $(DESTDIR)/etc/init.d/shairport-sync ] || cp 
scripts/shairport-sync $(DESTDIR)/etc/init.d/
+ endif
+ if INSTALL_SYSTEMD
+-  [ -e $(DESTDIR)/usr/lib/systemd/system ] || mkdir -p 
$(DESTDIR)/usr/lib/systemd/system
+-  cp scripts/shairport-sync.service $(DESTDIR)/usr/lib/systemd/system
++  [ -e $(DESTDIR)$(systemdsystemunitdir) ] || mkdir -p 
$(DESTDIR)$(systemdsystemunitdir)
++  cp scripts/shairport-sync.service $(DESTDIR)$(systemdsystemunitdir)
+ endif
+--- a/configure.ac
 b/configure.ac
+@@ -213,6 +213,22 @@ AC_ARG_WITH(dns_sd, [  --with-dns_sd = c
+   AC_SEARCH_LIBS([DNSServiceRefDeallocate], [dns_sd], , AC_MSG_ERROR(dns_sd 
support requires the dns_sd library!))], )
+ AM_CONDITIONAL([USE_DNS_SD], [test "x$HAS_DNS_SD" = "x1"])
+ 
++# Find systemd unit dir
++AC_ARG_WITH([systemdsystemunitdir],
++ [AS_HELP_STRING([--with-systemdsystemunitdir=DIR], [Directory for 
systemd service files])],,
++ [with_systemdsystemunitdir=auto])
++AS_IF([test "x$with_systemdsystemunitdir" = "xyes" -o 
"x$with_systemdsystemunitdir" = "xauto"], [
++ def_systemdsystemunitdir=$($PKG_CONFIG --variable=systemdsystemunitdir 
systemd)
++
++ AS_IF([test "x$def_systemdsystemunitdir" = "x"],
++   [AS_IF([test "x$with_systemdsystemunitdir" = "xyes"],
++[AC_MSG_ERROR([systemd support requested but pkg-config unable to query 
systemd package])])
++with_systemdsystemunitdir=no],
++   [with_systemdsystemunitdir="$def_systemdsystemunitdir"])])
++AS_IF([test "x$with_systemdsystemunitdir" != "xno"],
++  [AC_SUBST([systemdsystemunitdir], [$with_systemdsystemunitdir])])
++AM_CONDITIONAL([HAVE_SYSTEMD], [test "x$with_systemdsystemunitdir" != "xno"])
++
+ # Checks for header files.
+ AC_HEADER_STDC
+ AC_CHECK_HEADERS([getopt_long.h])
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..6a10cf6
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1,3 @@
+correct-systemd-unit-path.diff
+use-usr-bin-not-usr-local-bin-in-systemd.diff
+use-usr-bin-not-usr-local-bin-in-init.diff
diff --git a/debian/patches/use-usr-bin-not-usr-local-bin-in-init.diff 
b/debian/patches/use-usr-bin-not-usr-local-bin-in-init.diff
new file mode 100644
index 000..9340d5b
--- /dev/null
+++ b/debian/patches/use-usr-bin-not-usr-local-bin-in-init.diff
@@ -0,0 +1,11 @@
+--- a/scripts/shairport-sync
 b/scripts/shairport-sync
+@@ -17,7 +17,7 @@
+ PATH=/sbin:/usr/sbin:/bin:/usr/bin
+ DESC="AirPlay Synchronous Audio Service"
+ NAME=shairport-sync
+-DAEMON=/usr/local/bin/$NAME
++DAEMON=/usr/bin/$NAME
+ 
+ # We don't use the DAEMON_ARGS variable here because some of the identifiers 
may have spaces in them, and so are
+ # impossible to pass as arguments.
diff --git a/debian/patches/use-usr-bin-not-usr-local-bin-in-systemd.diff 
b/debian/patches/use-usr-bin-not-usr-local-bin-in-systemd.diff
new file mode 100644
index 000..2b1571c
--- /dev/null
+++ b/debian/patches/use-usr-bin-not-usr-local-bin

Bug#808564: RFP: searx -- privacy-respecting, hackable metasearch engine

[W. Martin Borgert]

Package: wnpp
Severity: wishlist

* Package name: searx
  Version : 0.8.0
  Upstream Author : Adam Tauber, 
* URL : https://github.com/asciimoo/searx/
* License : AGPL3+
  Programming Lang: Python
  Description : privacy-respecting, hackable metasearch engine

Features of searx are:
 * Tracking free
 * Supports multiple output formats
   * json curl https://searx.me/?format=json&q=[query]
   * csv curl https://searx.me/?format=csv&q=[query]
   * opensearch/rss curl https://searx.me/?format=rss&q=[query]
 * Opensearch support (you can set as default search engine)
 * Configurable search engines/categories
 * Different search languages
 * Duckduckgo like !bang functionality with engine shortcuts
 * Parallel queries - relatively fast

Bug#808461: sponsorship-requests: mdp [ITP] -- command-line based markdown presentation tool

[Paul Wise]

On Sun, Dec 20, 2015 at 9:24 PM, Lev Lamberov wrote:
> 20.12.2015 17:24, Andrew Shadura пишет:
>> we need to rename yours
>
> I've renames source package to mdp-src. Don't know whether it's a good name.

Maybe expand the 3 letters to words: markdown-presentation.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#802121: pysvn: FTBFS: error: ‘svn

[Josue Ortega]

On Sun, Dec 20, 2015 at 06:01:10PM +0100, Raphael Hertzog wrote:
> On Wed, 18 Nov 2015, Hideki Yamane wrote:
> > On Sat, 17 Oct 2015 17:00:45 +0100 "Chris West (Faux)" 
> >  wrote:
> > > Source: pysvn
> > > Version: 1.7.8-1
> > > Severity: serious
> > > Justification: fails to build from source
> > 
> >  This FTBFS bug is fixed in new upstream release 1.8.0
> 
> Upstream 1.8.0 seems to be in the git repository, though not uploaded.
> Josue, is there any reason for that?

My intention was to get ready the Python 3 version to uploaded, but it
was not ready.

> pysvn has been dropped from testing because nobody fixed this bug in two
> months...
> 
> It would be nice to fix it and get the package back in testing.

I have pushed the new upstream release (Python 2 version only) that fixes this
bug to the DPMT git repo[1], I have now DM upload permissions for this package,
Can you upload this package for me?

[1]: https://anonscm.debian.org/cgit/python-modules/packages/pysvn.git

Cheers!

---
Josue Ortega
«Happy Hacking»
http://josueortega.org

signature.asc
Description: PGP signature

Bug#808563: Boot with 4.3: SATA errors. Returning to 4.2: no errors

[積丹尼 Dan Jacobson]

Package: src:linux
Version: 4.3.3-2
Severity: important

I am getting these errors (sort -u'd here) with linux-image-4.3.0-1-686-pae

 res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: cmd 61/d0:d8:80:9e:10/05:00:26:00:00/40 tag 27 ncq 761856 out
ata1.00: configured for UDMA/133
ata1.00: exception Emask 0x60 SAct 0x1800 SErr 0x800 action 0x6 frozen
ata1.00: exception Emask 0x60 SAct 0x1f8 SErr 0x800 action 0x6 frozen
ata1.00: exception Emask 0x60 SAct 0xfe SErr 0x800 action 0x6 frozen
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: irq_stat 0x2000, host bus error
ata1.00: status: { DRDY }
ata1: EH complete
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: SError: { HostInt }
ata1: hard resetting link

Switching back to 4.2.6-3 solves it.

Did it twice so far. Consistent results.

Bug#808562: dput-ng: add support for a "progress bar"

[Sandro Tosi]

Package: dput-ng
Version: 1.10
Severity: wishlist
Tags: patch

Hello,
I just push a branch to dput-ng called 'progressbar' that contains a first
prototype for a progressbar (well, for the moment it just prints the percentage
of the file uploaded at the moment).

Given all the output in dput-ng is done via logger, there's no way to integrate
progressbar with logging, so that's done in a separate line.

the sftp is a preview of how a feedback on the upload could be done, if you like
(or have any suggestion on how to improve it) I can see to extend it to the
other uploaders (hoping they have a sort of callback mechanism as paramiko).

Regards,
Sandro

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

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

Versions of packages dput-ng depends on:
ii  python-dput  1.10
pn  python:any   

Versions of packages dput-ng recommends:
ii  bash-completion  1:2.1-4.2

dput-ng suggests no packages.

-- no debconf information

Bug#808561: apt: Apt does not check for lock before cleaning

[Thomas Ross]

Package: apt
Version: 1.1.5
Severity: normal

Hi,

When running `apt clean`, apt does not check for the package lock before
cleaning /var/cache/apt/archives, which can lead to installations or upgrades
to fail (due to missing .debs)

Thanks,
Thomas.



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.2\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.1\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.2\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "1";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "2";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-9n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "3";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "4";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-9";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::C

Bug#808560: sbuild: Use of uninitialized value $_ in concatenation (.)

[John David Anglin]

Package: sbuild
Version: 0.66.0-5
Severity: normal

Dear Maintainer,

After upgrading perl to 5.22.1-2, sbuild fails to move .debs to the upload
directory.  This can be seen for example in the following build log:
https://buildd.debian.org/status/fetch.php?pkg=r-cran-ape&arch=hppa&ver=3.4-1&stamp=1450633031

We have the following errors:
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1918.
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1919.
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1918.
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1919.
mv: cannot stat '/<>/<>/': No such file or directory
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1919.
E: Could not move  to .
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1918.
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1919.
mv: cannot stat '/<>/<>/': No such file or directory
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1919.
E: Could not move  to .
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1918.
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1919.
mv: cannot stat '/<>/<>/': No such file or directory
Use of uninitialized value $_ in concatenation (.) or string at 
/usr/share/perl5/Sbuild/Build.pm line 1919.
E: Could not move  to .
mv: cannot stat '/<>/<>/r-cran-ape-dbgsym_3.4-1_hppa.deb': No 
such file or directory
E: Could not move r-cran-ape-dbgsym_3.4-1_hppa.deb to .
mv: cannot stat '/<>/<>/r-cran-ape_3.4-1_hppa.deb': No such 
file or directory
E: Could not move r-cran-ape_3.4-1_hppa.deb to .
du: cannot access '/<>/<>': No such file or directory
du: cannot access '/home/buildd/upload/r-cran-ape-dbgsym_3.4-1_hppa.deb': No 
such file or directory
du: cannot access '/home/buildd/upload/r-cran-ape_3.4-1_hppa.deb': No such file 
or directory

Nothing changed in buildd configuration.

Regards,
Dave Anglin

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 3.18.24+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sbuild depends on:
ii  adduser 3.113+nmu3
ii  apt-utils   1.1.5
ii  libsbuild-perl  0.66.0-5
ii  perl5.22.1-2

Versions of packages sbuild recommends:
ii  debootstrap  1.0.75
ii  fakeroot 1.20.2-1

Versions of packages sbuild suggests:
ii  deborphan  1.7.28.8-0.2
ii  wget   1.17.1-1

-- no debconf information

Bug#808552: dh-dist-zilla: builds fail in recent pbuilder versions

[Sascha Steinbiss]

Hi Axel,

[…]
>> I have been able to fix the issue locally by setting
>> BUILD_HOME="/tmp" in my .pbuilderrc, and afterwards everything
>> builds fine for me. However, obviously that wouldn't help on build
>> machines where I don't have control over that (autobuilders, ...).
> 
> Exactly.
> 
>> Is it just me or can you confirm the problem?
> 
> Can confirm it.

OK, thanks.

[…]
> Looks as if its possible to set a specific environment variable named
> DZIL_GLOBAL_CONFIG_ROOT to skip the detection of $HOME and set a
> specific value. So I'll probably go down that road.

Sounds good. Thanks for working on this, dh-dist-zilla is quite helpful! :)

Best,
Sascha

Bug#808559: jessie-pu: package glibc/2.19-18+deb8u2

[Aurelien Jarno]

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

Dear stable release team,

We would like to update the glibc package in Jessie to fix the known
security issues, fix an issue with nscd affecting debian-edu and a
workaround for possible data corruption on Broadwell CPUs when not
using BIOS or microcode updates.

This is done partly by updating to the latest commit of the stable
branch and using a few additional patches. The diff can be found at the
bottom of this mail. It might looks big, but this is mostly due to the
new tests matching the issues fixed in the upstream stable branch and
the renaming of the Intel blacklisting patch to extend it to Broadwell
CPUs. All the corresponding changes are already in testing and unstable.

Thanks,
Aurelien


Index: debian/patches/git-updates.diff
===
--- debian/patches/git-updates.diff (révision 6511)
+++ debian/patches/git-updates.diff (copie de travail)
@@ -1,10 +1,75 @@
 GIT update of git://sourceware.org/git/glibc.git/release/2.19/master from 
glibc-2.19
 
 diff --git a/ChangeLog b/ChangeLog
-index 81c393a..0eb6c3f 100644
+index 81c393a..e82ba7d 100644
 --- a/ChangeLog
 +++ b/ChangeLog
-@@ -1,3 +1,341 @@
+@@ -1,3 +1,406 @@
++2015-12-20  Siddhesh Poyarekar  
++
++  [BZ #16758]
++  * nscd/netgroupcache.c (addinnetgrX): Succeed if triplet has
++  blank values.
++
++  [BZ #16759]
++  * inet/getnetgrent_r.c (get_nonempty_val): New function.
++  (nscd_getnetgrent): Use it.
++
++  [BZ #16760]
++  * nscd/netgroupcache.c (addgetnetgrentX): Use memmove instead
++  of stpcpy.
++
++2015-11-24  Andreas Schwab  
++
++  [BZ #17062]
++  * posix/fnmatch_loop.c (FCT): Rerrange loop for skipping over rest
++  of a bracket expr not to run off the end of the string.
++  * posix/Makefile (tests): Add tst-fnmatch3.
++  * posix/tst-fnmatch3.c: New file.
++
++2015-04-29  Florian Weimer  
++
++  [BZ #18007]
++  * nss/nss_files/files-XXX.c (CONCAT): Always enable stayopen.
++  (CVE-2014-8121)
++  * nss/tst-nss-getpwent.c: New file.
++  * nss/Makefile (tests): Add new test.
++
++2015-02-22  Paul Pluzhnikov  
++
++  [BZ #17269]
++  * libio/wstrops.c (_IO_wstr_overflow): Guard against integer overflow
++  (enlarge_userbuf): Likewise.
++
++2015-02-26  Andreas Schwab  
++
++  [BZ #18032]
++  * posix/fnmatch_loop.c (FCT): Remove extra increment when skipping
++  over collating symbol inside a bracket expression.  Minor cleanup.
++
++2014-06-23  Andreas Schwab  
++
++  [BZ #17079]
++  * nss/nss_files/files-XXX.c (get_contents): Store overflow marker
++  before reading the next line.
++
++2015-10-02  Andreas Schwab  
++
++  * sysdeps/posix/getaddrinfo.c (gaih_inet): Advance address pointer
++  when skipping over non-matching result from nscd.
++
++2015-09-11  Alan Modra  
++
++  [BZ #17153]
++  * elf/elf.h (DT_PPC64_NUM): Correct value.
++  * NEWS: Add to fixed bug list.
++
++2014-03-20  Andreas Schwab  
++
++  [BZ #16743]
++  * sysdeps/posix/getaddrinfo.c (gaih_inet): Properly skip over
++  non-matching result from nscd.
++
 +2015-04-21  Arjun Shankar  
 +
 +  [BZ #18287]
@@ -347,10 +412,10 @@
  
[BZ #16529]
 diff --git a/NEWS b/NEWS
-index 98b479e..7f9388f 100644
+index 98b479e..2972c4a 100644
 --- a/NEWS
 +++ b/NEWS
-@@ -5,6 +5,59 @@ See the end for copying conditions.
+@@ -5,6 +5,65 @@ See the end for copying conditions.
  Please send GNU C library bug reports via 
  using `glibc' in the "product" field.
  
@@ -358,8 +423,9 @@
 +
 +* The following bugs are resolved with this release:
 +
-+  15946, 16545, 16574, 16623, 16657, 16695, 16878, 16882, 16885, 16916,
-+  16932, 16943, 16958, 17048, 17069, 17137, 17213, 17263, 17325, 17555,
++  15946, 16545, 16574, 16623, 16657, 16695, 16743, 16758, 16759, 16760,
++  16878, 16882, 16885, 16916, 16932, 16943, 16958, 17048, 17062, 17069,
++  17079, 17137, 17153, 17213, 17263, 17269, 17325, 17555, 18007, 18032,
 +  18287.
 +
 +* A buffer overflow in gethostbyname_r and related functions performing DNS
@@ -406,6 +472,11 @@
 +  IBM937, IBM939, IBM1364 could result in an out-of-bounds array read,
 +  resulting a denial-of-service security vulnerability in applications which
 +  use functions related to iconv. (CVE-2014-6040)
++
++* CVE-2014-8121 The NSS files backend would reset the file pointer used by
++  the get*ent functions if any of the query functions for the same database
++  are used during the iteration, causing a denial-of-service condition in
++  some applications.
 +
  Version 2.19
  
@@ -423,6 +494,19 @@
  ifeq (yes,$(build-shared))
  tests-static += tst-tls9-static
  tst-tls9-static-ENV = \
+diff --git a/elf/elf.h b/elf/elf.h
+index 40e87b2..78815e8 100644
+--- a/elf/elf.h
 b/elf/elf.h
+@@ -2283,7 +2283,7 @@ typedef

Bug#605090:

[Jacob Appelbaum]

To make my Debian Jessie system work with pax, I had to set pax flags
for these three binaries:

  paxctl -c -m /usr/bin/gnome-shell
  paxctl -c -m /usr/bin/gnome-session
  paxctl -c -m /usr/bin/pulseaudio

If you don't want to modify the binary, you can also set the
attributes in the file system:

  setfattr -n user.pax.flags -v m /usr/bin/gnome-shell
  setfattr -n user.pax.flags -v m /usr/bin/gnome-session
  setfattr -n user.pax.flags -v m /usr/bin/pulseaudio

You will need the `attr` package to run the above command. See
https://wiki.debian.org/grsecurity/setfattr for more information. It
may make sense to add a suggestion on the grsec kernel package for
attr.

The above allowed me to properly start GDM and to login to my system.
To use iceweasel and other utilities, I had to modify other things. I
also was able to set `kernel.grsecurity.disable_priv_io=0` after
running the setfattr commands above.

I additionally had to set the following to make the following programs
"work" with this kernel:

  setfattr -n user.pax.flags -v m /usr/bin/seahorse
  setfattr -n user.pax.flags -v m /usr/bin/iceweasel
  setfattr -n user.pax.flags -v m /usr/bin/chromium
  setfattr -n user.pax.flags -v m /usr/lib/chromium/chromium

For those who care pulse audio was also making some log entries about
"denied resource overstep by requesting 25 for RLIMIT_NICE against
limit 0 for /usr/bin/pulseaudio" - I reconfigured it with an edit to
/etc/pulseaudio/daemon.conf to add 'high-priority = no' and the kernel
stopped complaining.

I now only see two grsec denied messages on by Debian jessie system after boot:

[9.560994] grsec: denied use of ioperm() by
/usr/lib/xorg/Xorg[Xorg:891] uid/euid:0/0 gid/egid:0/0, parent
/usr/sbin/gdm3[gdm3:885] uid/euid:0/0 gid/egid:0/0
[   12.091674] grsec: denied priority change of process
(rtkit-daemon:1066) by /usr/lib/rtkit/rtkit-daemon[rtkit-daemon:1066]
uid/euid:107/107 gid/egid:114/114, parent
/lib/systemd/systemd[systemd:1] uid/euid:0/0 gid/egid:0/0

After login - I see the following grsec messages:

[  448.243314] grsec: denied untrusted exec (due to not being in
trusted group and file in non-root-owned directory) of
/run/user/1000/orcexec.pIjl0t by
/usr/bin/pulseaudio[alsa-source-ALC:1617] uid/euid:1000/1000
gid/egid:1000/1000, parent /lib/systemd/systemd[systemd:1]
uid/euid:0/0 gid/egid:0/0
[  448.243366] grsec: denied untrusted exec (due to not being in
trusted group and file in non-root-owned directory) of
/home/error/orcexec.iEBctM by
/usr/bin/pulseaudio[alsa-source-ALC:1617] uid/euid:1000/1000
gid/egid:1000/1000, parent /lib/systemd/systemd[systemd:1]
uid/euid:0/0 gid/egid:0/0
[  448.243405] grsec: denied untrusted exec (due to not being in
trusted group and file in world-writable directory) of
/tmp/orcexec.VrI4V4 by /usr/bin/pulseaudio[alsa-source-ALC:1617]
uid/euid:1000/1000 gid/egid:1000/1000, parent
/lib/systemd/systemd[systemd:1] uid/euid:0/0 gid/egid:0/0
[  448.999276] grsec: denied RWX mmap of  by
/usr/share/system-config-printer/applet.py[applet.py:1661]
uid/euid:1000/1000 gid/egid:1000/1000, parent
/usr/bin/gnome-session[x-session-manag:1464] uid/euid:1000/1000
gid/egid:1000/1000
[  448.999349] grsec: denied untrusted exec (due to not being in
trusted group and file in world-writable directory) of /tmp/ffixSCBQp
by /usr/share/system-config-printer/applet.py[applet.py:1661]
uid/euid:1000/1000 gid/egid:1000/1000, parent
/usr/bin/gnome-session[x-session-manag:1464] uid/euid:1000/1000
gid/egid:1000/1000
[  448.999395] grsec: denied untrusted exec (due to not being in
trusted group and file in world-writable directory) of
/var/tmp/ffiQhZWhL by
/usr/share/system-config-printer/applet.py[applet.py:1661]
uid/euid:1000/1000 gid/egid:1000/1000, parent
/usr/bin/gnome-session[x-session-manag:1464] uid/euid:1000/1000
gid/egid:1000/1000
[  448.999422] grsec: denied untrusted exec (due to not being in
trusted group and file in world-writable directory) of
/dev/shm/ffi5YViJ6 by
/usr/share/system-config-printer/applet.py[applet.py:1661]
uid/euid:1000/1000 gid/egid:1000/1000, parent
/usr/bin/gnome-session[x-session-manag:1464] uid/euid:1000/1000
gid/egid:1000/1000
[  448.999457] grsec: more alerts, logging disabled for 10 seconds
[  449.760884] EXT4-fs (sdb1): mounted filesystem with ordered data
mode. Opts: (null)

To eliminate most of those issues, I ran:

  setfattr -n user.pax.flags -v m /usr/bin/seahorse
  setfattr -n user.pax.flags -v m /usr/bin/gjs-console
  setfattr -n user.pax.flags -v m /usr/bin/python

I was left with:

[ 1802.373906] grsec: denied untrusted exec (due to not being in
trusted group and file in non-root-owned directory) of
/run/user/1000/orcexec.bCtW1V by
/usr/bin/pulseaudio[alsa-source-ALC:3038] uid/euid:1000/1000
gid/egid:1000/1000, parent /lib/systemd/systemd[systemd:1]
uid/euid:0/0 gid/egid:0/0
[ 1802.373967] grsec: denied untrusted exec (due to not being in
trusted group and file in non-root-owned directory) of
/home/error/orcexec.SzaIXb by
/usr/bin/pulseaudio[a

Bug#808441: RFS: rfcdiff/1.42-1 ITP

[Mattia Rizzolo]

On Sun, Dec 20, 2015 at 11:48:07PM +0100, Peter Spiess-Knafl wrote:
> > trailing whitespaces: + debian/control:15 + debian/rules:3
> 
> Applied forgotten wrap-and-sort

wrap-and-sort doesn't touch debian/rules.
Also, in this process you added new trailing whitespaces (`git diff`
(and friends, like `git log -p` and `git show`) shows them in red
here...)

debian/patches/fix-changelog-typos.patch:1
debian/patches/fix-changelog-typos.patch:2
debian/patches/fix-fsf-address.patch:2

> > there is really no need to do that useless
> > override_dh_auto_install, just empty that target in d/rules, and
> > write 'rfcdiff' in debian/rfcdiff.install
> 
> The makefile seems to be for internal development use only. Also
> Fedora is working around that faulty makefile.
[...]
> Therefore I would like to keep the current version until upstream
> comes up with a fixed version, with proper test and install targets
> (including DESTDIR and PREFIX variables).

yeah, I don't mean you to patch the makefile, please re-read my quote
above.
that work in override_dh_auto_install + .install file is duplicated for
nothing.
I'm proposing the attached patch, what do you think?

> I re-uploaded a modified verion to mentors.
> Thanks for taking the time.

btw, I'll happily work through git, given that you have a packaging
repository, and you're using it sanely I'd use it, rather than going
with tarballs, is way easier for me.
Just poke when you do changes to review/upload.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diff --git a/debian/rfcdiff.install b/debian/rfcdiff.install
index e772481..ca62b14 100644
--- a/debian/rfcdiff.install
+++ b/debian/rfcdiff.install
@@ -1 +1 @@
-usr/bin
+rfcdiff
diff --git a/debian/rules b/debian/rules
index cd07313..04703b7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -17,8 +17,7 @@ override_dh_auto_test:
# nothing
 
 override_dh_auto_install:
-   mkdir -p $(CURDIR)$(DESTDIR)/debian/tmp/usr/bin
-   cp rfcdiff $(CURDIR)$(DESTDIR)/debian/tmp/usr/bin
+   # nothing
 
 override_dh_auto_clean:
rm -f debian/rfcdiff.1


signature.asc
Description: PGP signature

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[John Paul Adrian Glaubitz]

Emilio,

On 12/20/2015 11:42 PM, Emilio Pozuelo Monfort wrote:
> Cool. So now worrying about the situation and long-term status of a key 
> package
> in a release architecture is called nonsense. Way to go.

Could you just please stop trolling, you're not helping, ok?
ARM is not dead by far stretch, so your assumptions *are* non-sense.

Instead of telling others what to do, I suggest you use your energy
to fix bugs instead or sponsor packages for Debian maintainers or
maybe help new people become DDs by becoming an AM.

Cheers,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[John Paul Adrian Glaubitz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/20/2015 11:02 PM, Joachim Breitner wrote:
> ah, I was mislead by the mail address you use, but you are an
> uploading DD – so since you have built it anyways, why don’t you
> simply upload it?

No problem, will do. Just currently test-building the package on armhf
to be sure I didn't break anything. Then I'll have to make another
final clean build on armel since my first test patch wasn't cleaned
up yet.

> (If you are worried about historic Debian customs of being very
> careful about treading on other people’s packages – in my cases
> don’t :-))

Thanks. I just want to make sure I don't interfere with the work
of my fellow Debian Developers.

Adrian

- -- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWdzMKAAoJEHQmOzf1tfkTY/sP/2wUVGFLXW7surO6eBFo3ECg
yOUFZRE8qOXYiMs9++zJZfk1NZRcGHGrrO5OBNwrtO+CKldvDNBWPmO0zG/rhz+O
V4t8sk46pcPckVBt/IpOAa3MO8s7EQSOMl1pmFFQzJMIdh1BHeKkfbP/38g9H8QL
kYxKdQxFeyEw6yZrnMDV5443g5pxfw60zTo8hHTVQPjn+vk7uej2vq3BonB25eSN
SCVsN3aqKF24GZxurO9PwJl5M2lf3pqQdI0LVuK2F7WAFmBF3PJQ5Rs481+9/s0e
Rx0exzWEtrfzqP/eDA/+P5jiAETJERuMj2JiVZ60l2seBUvE9f9Jfo+oq395muEq
BPo42Zu+dhfoBBvxi2cGM2Fa04Tzbptq5q9R9SkGL4dnTV5Y8/yT86lYU79+IJh0
3CZGVSInsq//SF4lfK75rWrrSbjFgKZOyrYruoLl/G1XVLAYnyChKf9ty4FXbcPb
IQx3hup7kY/y+2urP7h0RLfW22pzG/3tEonfieDThK5v7M+qcKA39WJhmcSxVi+E
HAtvVUK9vWya8tJHA/VbKTcR9D9g/H1ZSrI4QOW2fKzYd0EetX37VeV6ioUIz2Yx
uIGPoA/v74GsJLYFg1oOMaKpWJC6prIxN9YTGoZcf3RCvM4z2egpGEnu08DPrMWX
ATZE9RXgfoVNJlmCrWP+
=g0dl
-END PGP SIGNATURE-

Bug#808073: geki3: Powerup system is unreliable

[Steve Cotton]

On Tue, Dec 15, 2015 at 08:30:06PM +0100, Andrej Mernik wrote:
> In Geki3 you can pick up three types of powerups during gameplay:
> 
> White pills restore your health and this works as advertised. 
> Blue and pink pills should powerup your weapons  but this almost never works:

Hi Andrej,

The powerups work, but the hitpoint bar is a cruel misdirection
by the UI.  It suggests that you can take hits, and you really
can't - you need 3 powerups to increase your firepower one level,
and getting hit removes a powerup.

BTW, even knowing the mechanics, I think the game is hard.  But
the misdirection and lack of documentation seems to be a bug.

Steve

Bug#796345: [Debian-ha-maintainers] Bug#796345: redhat-cluster/libdlm + lvm + perl transition

[Emilio Pozuelo Monfort]

On 17/12/15 14:09, Ferenc Wagner wrote:
> Ferenc Wagner  writes:
> 
>> Emilio Pozuelo Monfort  writes:
>>
>>> On 16/12/15 00:12, Ferenc Wagner wrote:
>>>
 Niko Tyni  writes:

> So the proper way out seems to be a separate libdlm source package, as
> discussed in [1]. Ferenc, do I understand right that a new pacemaker
> package is a blocker for this? Is that because the current pacemaker
> would be broken by the libdlm update?

 No: the new DLM package depends on the new Pacemaker package.  I'm
 already testing them, there's only some cleanup remaining before they
 can be uploaded.  Both will go through NEW though, so it will take some
 time.
>>>
>>> I can speed things up if they block a transition... Got an eta for this?
>>
>> That sounds useful!  I expect to get pacemaker_1.1.13-1 ready for upload
>> today, taking some shortcuts.
> 
> Now the Perl transition is rolling and I can't build Pacemaker anymore,
> because some of its build dependencies are broken.  Is there still a
> reason to hurry the uploads?

This is the last blocker for the perl transition. Packages should be installable
now in unstable. Please let us know if you make progress with this or if you hit
any blockers.

Cheers,
Emilio

Bug#808441: RFS: rfcdiff/1.42-1 ITP

[Peter Spiess-Knafl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Mattia!

Thank you very much for your review and also for introducing me
diffoscope.


On 12/20/2015 03:18 PM, Mattia Rizzolo wrote:
> 
> review:
> 
> trailing whitespaces: + debian/control:15 + debian/rules:3

Applied forgotten wrap-and-sort

> 
> there is really no need to do that useless
> override_dh_auto_install, just empty that target in d/rules, and
> write 'rfcdiff' in debian/rfcdiff.install
> 
> Makefile contains an 'include ../Makefile.common', while the file
> is in the same directory, guess it needs fixing?  once done so the 
> override_dh_auto_test and override_dh_auto_install can be removed 
> entirely.  This is a problem for upstream, please forward the
> issue.
> 

The makefile seems to be for internal development use only. Also
Fedora is working around that faulty makefile.

https://kojipkgs.fedoraproject.org//packages/rfcdiff/1.41/7.el7/src/rfcd
iff-1.41-7.el7.src.rpm

I reported it to upstream, hopefully he will rework it.

Therefore I would like to keep the current version until upstream
comes up with a fixed version, with proper test and install targets
(including DESTDIR and PREFIX variables).

> stuff check-all-the-things tells me:
> 
> $ cme check dpkg Warning in 'control binary:rfcdiff Depends:2'
> value 'diffutils': unnecessary unversioned dependency on essential
> package: diffutils
> 

Thanks for the hint.

> $ codespell --quiet-level=3 ./changelog:178: refering  ==>
> referring

Added a patch and forwareded it.
> 
> $ licensecheck --check=. --recursive --copyright . | grep -F 'with
> incorrect FSF address' ./copyright: GPL (v2 or later) (with
> incorrect FSF address)
> 
Added a patch and forwareded it.


> please forward the last 2 to upstream.
> 
> 
> The rest looks good, if you fix this few bits I'll upload it.
> 

I re-uploaded a modified verion to mentors.
Thanks for taking the time.

Greetings Peter

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWdzAnAAoJED/ImGelQYVW0fUP/isgWAQFI6VH8gbDRVY1DxKU
xJCvpVvEu0u1SWcZzGcEwHqe8QUgE1uZWLG4VLziAy+dKYakt5yx2dXD1fKQ7pEO
SljOv0JLZpsR0JQowkfQdLJeHWyROUY6lCEEPtwtERa3KpNzgDoEsbq3gRO0oeQn
XdTLXPqRYhMqa+q2X5Rf+bRx0shqzwB3sJaw/1naCw3ehKifNbcJL1TwbeSegDJr
INLzLzdmjldfC0/No1Mbs44DeBliE3xiOVaETkjGWzf34q4BQ9lrms/qt00aqaLT
WxIluAWslmDwNluM65TMd5+lJbq9BQo3Akxh82RQf0KVu+7nXMWosP/+Nzj31AgM
y6ZhL4VZS0xjqI/h8vU/uwk6JxYkwPIThirI9sCjLQDvQ8iKBixxLNCCdk38FdUN
q3H3d/oDLkjNhacy26b5do8oBavjegRTAUVo1rHNAmJyxQ5OJ+7GEp7Q5PEkQh3P
KH0KvQqjM8wF4vIVjQMtPc+oXIhhe4ayLDsJMFppl4nfCJdVQeZzpi4k5xOKsi+1
6b+aRz4YXeifusvx8z6sErGMVDpf7vwfH6qVnUPhbucY3ZLnDm41L53UcBJzKhXS
C6tKEbh38l69+c8Zz44nd/TYmlXKyg7Mg8oYxRY3H70qPg5wNYznF1anZp1pP17s
23RCVXkvh+RP8JgEK7Og
=DTKx
-END PGP SIGNATURE-

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[Emilio Pozuelo Monfort]

On 20/12/15 14:02, John Paul Adrian Glaubitz wrote:
> On 12/20/2015 01:42 PM, Emilio Pozuelo Monfort wrote:
>> I know nothing about haskell upstream, so the fact that armel got broken for 
>> so
>> long even though it was pointed out by Joachim in several mails made me think
>> that arm(el) development had indeed been stopped.
> 
> Sorry, but this is complete non-sense.

Cool. So now worrying about the situation and long-term status of a key package
in a release architecture is called nonsense. Way to go.

Emilio

Bug#808558: automatic -dbgsym packages in changes files rejected even with --ignore=surprisingbinary

[Christoph Berg]

Package: reprepro
Version: 4.16.0-1
Severity: important

Hi,

debhelper is now adding automatic -dbgsym packages to all packages in
sid that don't have a -dbg package yet. The problem with this in
combination with reprepro is that the .changes file produced will
contain a foo-dbgsym.deb file which isn't listed in the Binary: field.

The reasoning here is that Binary: is supposed to contain the list of
.debs from debian/control which is not necessarily the list of things
uploaded (e.g. d-i is uploading non-deb content using this way).

Unfortunately reprepro doesn't like this, even with
--ignore=surprisingbinary which should (according to the manpage)
allow exactly this situation:

$ reprepro --verbose --ignore=surprisingbinary processincoming pgdg
Name 'pgagent-dbgsym' of binary 'pgagent-dbgsym_3.4.1-1.pgdg+1_i386.deb' is not 
listed in Binaries header of 'pgagent_3.4.1-1.pgdg+1_i386.changes'!
Name 'pgagent-dbgsym' of binary 'pgagent-dbgsym_3.4.1-1.pgdg+1_amd64.deb' is 
not listed in Binaries header of 'pgagent_3.4.1-1.pgdg+1_amd64.changes'!
There have been errors!

$ cat pgagent_3.4.1-1.pgdg+1_amd64.changes
Format: 1.8
Date: Sun, 20 Dec 2015 10:29:52 +0100
Source: pgagent
Binary: pgagent
...
Files:
 b9f0f5130cb8093b5ff9fe4b368f8941 663372 debug extra 
pgagent-dbgsym_3.4.1-1.pgdg+1_amd64.deb
 30421be49e3669628c2cc75d14e53634 67068 database optional 
pgagent_3.4.1-1.pgdg+1_amd64.deb


Looking into the code, only checkindeb.c is evaluating
"surprisingbinary":

if (!strlist_in(allowed_binaries, pkg->deb.name) &&
!IGNORING(surprisingbinary,
"'%s' has packagename '%s' not listed in the .changes file!\n",
debfilename, pkg->deb.name)) {
deb_free(pkg);
return RET_ERROR;
}

... but incoming.c does not:

if (! strlist_in(&c->binaries, file->deb.name)) {
fprintf(stderr, 
"Name '%s' of binary '%s' is not listed in Binaries header of '%s'!\n",
file->deb.name, BASENAME(i, file->ofs),
BASENAME(i, c->ofs));
return RET_ERROR;
}

Thanks for maintaining reprepro,
Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: Digital signature

Bug#808541: [Reproducible-builds] Bug#808541: diffoscope TypeError with openocd/0.9.0-1 in testing/amd64

[Jérémy Bobbio]

Control: tag -1 + pending

Mattia Rizzolo:
> TypeError: unorderable types: bytes() < str()

I've pushed a fix. Thanks for the report.

(This only appeared when the default encoding was not Unicode-aware.)

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Bug#808395: libprelude: diff for NMU version 1.0.0-11.7

[gregor herrmann]

Dear maintainer,

I've uploaded an NMU for libprelude (versioned as 1.0.0-11.7). The diff
is attached to this message.

I apologize for uploading directly, but since this is one of the last
blockers for the perl 5.22 transition, I thought it is warrented in
this case.

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: Rolling Stones: Driftaway
diff -Nru libprelude-1.0.0/debian/changelog libprelude-1.0.0/debian/changelog
--- libprelude-1.0.0/debian/changelog	2015-07-25 13:21:14.0 +0200
+++ libprelude-1.0.0/debian/changelog	2015-12-20 23:03:06.0 +0100
@@ -1,3 +1,12 @@
+libprelude (1.0.0-11.7) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS everywhere": add patch swig-perl-lua-comments.patch
+to change comment signs in swig code.
+(Closes: #808395)
+
+ -- gregor herrmann   Sun, 20 Dec 2015 23:02:55 +0100
+
 libprelude (1.0.0-11.6) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru libprelude-1.0.0/debian/patches/series libprelude-1.0.0/debian/patches/series
--- libprelude-1.0.0/debian/patches/series	2015-07-25 13:18:08.0 +0200
+++ libprelude-1.0.0/debian/patches/series	2015-12-19 15:26:56.0 +0100
@@ -9,3 +9,4 @@
 016_ppc64el-isnan-tests-fix-for-little-endian-PowerPC.patch
 gcc5.diff
 020_Update-to-latest-GnuTLS-API.patch
+swig-perl-lua-comments.patch
diff -Nru libprelude-1.0.0/debian/patches/swig-perl-lua-comments.patch libprelude-1.0.0/debian/patches/swig-perl-lua-comments.patch
--- libprelude-1.0.0/debian/patches/swig-perl-lua-comments.patch	1970-01-01 01:00:00.0 +0100
+++ libprelude-1.0.0/debian/patches/swig-perl-lua-comments.patch	2015-12-20 21:44:04.0 +0100
@@ -0,0 +1,44 @@
+Description: change comments after swig changes
+Forwarded: no
+Bug-Debian: https://bugs.debian.org/808395
+Author: gregor herrmann 
+Last-Update: 2015-12-20
+
+--- a/bindings/lua/libpreludecpp-lua.i
 b/bindings/lua/libpreludecpp-lua.i
+@@ -1,9 +1,9 @@
+-# Exception map
++/* Exception map */
+ %typemap(throws) Prelude::PreludeError %{
+ SWIG_exception(SWIG_RuntimeError, $1.what());
+ %};
+ 
+-# Lua overloading fixes
++/* Lua overloading fixes */
+ %ignore IDMEFCriteria(std::string const &);
+ %ignore IDMEFValue(int8_t);
+ %ignore IDMEFValue(uint8_t);
+@@ -36,7 +36,7 @@
+ %ignore Set(char const *, float);
+ %ignore Set(char const *, std::string);
+ 
+-# Conversion not allowed
++/* Conversion not allowed */
+ %ignore *::operator =;
+ 
+ %ignore *::operator int() const;
+--- a/bindings/perl/libpreludecpp-perl.i
 b/bindings/perl/libpreludecpp-perl.i
+@@ -1,10 +1,10 @@
+-# Exception map
++/* Exception map */
+ %typemap(throws) Prelude::PreludeError %{
+ SWIG_exception(SWIG_RuntimeError, $1.what());
+ %};
+ 
+ 
+-# Conversion not allowed
++/* Conversion not allowed */
+ %ignore *::operator =;
+ %ignore *::operator int() const;
+ %ignore *::operator long() const;


signature.asc
Description: Digital Signature

Bug#808556: live-wrapper: use ansible for the vmdebootstrap hook script

[Iain R. Learmonth]

Hi,

On Sun, Dec 20, 2015 at 09:57:05PM +, Iain R. Learmonth wrote:
> Instead of trying to implement logic for configuring the live
> environments, just let ansible do it.

Ok, here are my thoughts on this:

Add an option to lwr, something like --ansible , that causes a
hook script to be run that does:

  * mount_support
  * disable daemons in the chroot
  * prepare_apt_source
  * create an ansible inventory containing a single host
where ansible_host is set to the rootdir (passed as the
first argument to the hook script) and use connection
type of chroot - the alias should probably be "live" or
something known so it can be used in the playbook
  * run the ansible playbook passing in the inventory
  * remove_daemon_block
  * replace_apt_source
  * blacklist_qemu_bochs (this is only really needed for qemu efi - should
investigate this futher)

This actually shouldn't be too hard. The blends-images package can then be a
series of ansible playbooks and bootloader configs as jinja2 templates
(#808557) which will be consistent with any templates used as part of the
ansible playbook.

Thanks,
Iain.

-- 

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[Joachim Breitner]

Hi,

Am Sonntag, den 20.12.2015, 22:52 +0100 schrieb John Paul Adrian
Glaubitz:
> Hi Joachim!
> 
> On 12/20/2015 10:36 PM, Joachim Breitner wrote:
> > Does any DD on this list have full access to a sufficiently strong
> >  armel machine and is willing to doe the steps as described by 
> > Adrian, described in the mail below? That would be great!
> 
> You actually don't need native hardware for that, just use qemu-user.
> 
> I have written a short (German) howto that should help you to setup
> an armel sbuild schroot on your amd64 box at home:
> 
> > https://people.debian.org/~glaubitz/sbuildsetup.html
> 
> With this setup, I was able to build ghc for armel without any issues,
> takes around 12 hours on my 4-core Xeon E31220.

ah, I was mislead by the mail address you use, but you are an uploading
DD – so since you have built it anyways, why don’t you simply upload
it? 

(If you are worried about historic Debian customs of being very careful
about treading on other people’s packages – in my cases don’t :-))

Greetings,
Joachim

-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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

Bug#808289: proposed RM: upstart -- RoQA; unmaintained

[Michael Biebl]

On Fri, 18 Dec 2015 12:25:50 +0100 Ansgar Burchardt 
wrote:
> I therefore suggest to remove the package.
> 
> If there are no objections, I'll reassign this bug report to ftp.d.o in
> a week or so.

I'm not going to comment on whether to remove upstart or not.
But if you do, the mountall package should probably be removed along
with it. The mountall tool is a helper for upstart and without upstart
it would be pretty useless to have this package in the archive.

Regards,
Michael


-- 
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#808556: live-wrapper: use ansible for the vmdebootstrap hook script

[Iain R. Learmonth]

Package: debian-live
Severity: wishlist

Hi,

The current method of using a shell script as the hook script means that
a lot of logic about the setup of the live environment has to be handled
by live-wrapper, where a tool like ansible can already do these things.

Instead of trying to implement logic for configuring the live
environments, just let ansible do it.

Thanks,
Iain.

Bug#808557: live-wrapper: use jinja2 for bootloader configuration templates

[Iain R. Learmonth]

Package: debian-live
Severity: wishlist

Hi,

Instead of creating logic for templating for installing bootloader
configurations, Jinja2 already exists, so we should just use it.

Thanks,
Iain.

Bug#605090: Git tag signing

[bancfc]

I just wanted to mention Git tag signing. Its a very useful security 
feature we use for protecting source code builds in our project.


https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[John Paul Adrian Glaubitz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Joachim!

On 12/20/2015 10:36 PM, Joachim Breitner wrote:
> Does any DD on this list have full access to a sufficiently strong
>  armel machine and is willing to doe the steps as described by 
> Adrian, described in the mail below? That would be great!

You actually don't need native hardware for that, just use qemu-user.

I have written a short (German) howto that should help you to setup
an armel sbuild schroot on your amd64 box at home:

> https://people.debian.org/~glaubitz/sbuildsetup.html

With this setup, I was able to build ghc for armel without any issues,
takes around 12 hours on my 4-core Xeon E31220.

Hope this helps,

Adrian

- -- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWdyMOAAoJEHQmOzf1tfkTEi8QAKvLkkonoyGFZeDtP+K0ZRVy
Rx14fuVU7A4IK3iL2XCw1uJ/RUQnd64PKWuIy9esEBeSefJ7LGwoWXEOJV5oUgyR
L/H+RZMX9vwnh8Qs5gIDMDBuuP2XaSCqXVfueFrWvuMsUCNlrxTktBO7UPi7e3L7
JE3UT/qS+ImCQyVlP8Yvqc3laqIJVXxYHKY+Ru4c0KnyfkWRom8UZrqII6joEMme
hynUOp8AOe/ViFlEFn4C36Fr9X58glD3Y6c5ZMqLV6A3IKGnGLVioY4HfiDQhskB
O7vZZ24NtJeE1rusYdyTh2dPJwtPzCKAOQ//0Tyr+w15sNqY/jzRN8MOd2Uehz6g
gtJqPRAKkmI0kqPX27l5YOb5dqygjoNbfiM0viGWIuK2Kh5xHRW+JhejzE5VSerA
ZdM+e2ExqsgEC5icwYRlW2wgUB3oMiwFVCaE9Sik9HmdHqfxM7f02X29kuCgB4DS
EoJ9CmTeTdoVyL8kDXBzlpVUiU9lUUWG+EabLDw1nVNqKy4vmwD7j8iFuzhp8vKo
Sh4tNoFoXq4twyPNGj5VlYMwrAiOLKkSsHJj+c1+OwzjNW0V3blKJ15pg0Vp3Wju
y+R+lWVu7/7QhVLAq/iklKdFiw4mcUkWF4M9yIp2thcD9/zHafhEfeigw2jgRqgT
LYkVgARbJQ6jO2l96pBi
=WtyU
-END PGP SIGNATURE-

Bug#808555: xserver-xorg-video-intel: [i915] DRM-related call crashes the xserver

[Gilles Sadowski]

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20151217-1~exp1
Severity: important

Dear Maintainer,

As you advised here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807598
I upgraded to the kernel 4.3, and removed the
  i915.preliminary_hw_support=1
kernel command-line argument.

Matters got worse.

I currently use the "wdm" session manager.
When logging on the graphical console, the desktop session is incompletely
set up: the background image appears but nothing else for many seconds from
the expected "cinnamon" environement; then the mouse cursor appears (a
right-click shows a contextual menu).

When I switch to a text console a kernel stacktrace appears.

After switching back and forth a few times, the xserver crashes (blank
screen on the graphical console, keyboard frozen).
This also happened when trying to restart the session manager
with
 # /etc/init.d/wdm restart

Is this a known problem?

Currently, my machine is mostly unusable with the i915 driver (no hardware
acceleration with kernel < 4.3, no graphical desktop with kernel = 4.3).

Would you recommend that I forego using the onboard graphics?

Thanks,
Gilles

-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated 
Graphics [8086:1912] (rev 06)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1

Kernel version (/proc/version):
---
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20151207 (Debian 5.3.1-3) ) #1 SMP Debian 4.3.3-2 (2015-12-17)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 23258 Dec 20 20:47 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  5771.210] 
X.Org X Server 1.17.3
Release Date: 2015-10-26
[  5771.210] X Protocol Version 11, Revision 0
[  5771.210] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[  5771.210] Current Operating System: Linux night 4.3.0-1-amd64 #1 SMP Debian 
4.3.3-2 (2015-12-17) x86_64
[  5771.210] Kernel command line: BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64 
root=/dev/mapper/night_vg1-root ro
[  5771.210] Build Date: 27 October 2015  11:41:02PM
[  5771.210] xorg-server 2:1.17.3-2 (http://www.debian.org/support) 
[  5771.210] Current version of pixman: 0.33.4
[  5771.210]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  5771.210] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  5771.210] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 20 20:47:05 
2015
[  5771.210] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  5771.211] (==) No Layout section.  Using the first Screen section.
[  5771.211] (==) No screen section available. Using defaults.
[  5771.211] (**) |-->Screen "Default Screen Section" (0)
[  5771.211] (**) |   |-->Monitor ""
[  5771.211] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  5771.211] (==) Automatically adding devices
[  5771.211] (==) Automatically enabling devices
[  5771.211] (==) Automatically adding GPU devices
[  5771.211] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  5771.211]Entry deleted from font path.
[  5771.211] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[  5771.211] (==) ModulePath set to "/usr/lib/xorg/modules"
[  5771.211] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  5771.211] (II) Loader magic: 0x55df69c83de0
[  5771.211] (II) Module ABI versions:
[  5771.211]X.Org ANSI C Emulation: 0.4
[  5771.211]X.Org Video Driver: 19.0
[  5771.211]X.Org XInput driver : 21.0
[  5771.211]X.Org Server Extension : 9.0
[  5771.215] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
[  5771.217] (II) xfree86: Adding drm device (/dev/dri/card0)
[  5771.217] (EE) systemd-logind: failed to take device /dev/dri/card0: 
Operation not permitted
[  5771.220] (--) PCI:*(0:0:2:0) 8086:1912:1043:8694 rev 6, Mem @ 
0xde00/16777216, 0xc000/268435456, I/O @ 0xf000/64
[  5771.220] (II) LoadModule: "glx"
[  5

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[Joachim Breitner]

Dear debian-arm,

Adrian has invested the time and come up with a way to keep GHC alive
on armel. (Thanks a lot!)

Unfortunately, there was a race condition with him coming up with a
solution and my removal bug being acted upon by the ftp-masters, which
now means that we have to re-bootstrap GHC on armel to get Adria’s fix
in. Due to the restricted possibility of installing additional and out-
of-archive-packages in the porterbox schroots, I cannot do that dance.

Does any DD on this list have full access to a sufficiently strong
armel machine and is willing to doe the steps as described by Adrian,
described in the mail below? That would be great!

Thanks,
Joachim

Am Sonntag, den 20.12.2015, 11:09 +0100 schrieb John Paul Adrian
Glaubitz:
> Hi!
> 
> So, here's my suggestion on how to fix this issue.
> 
> First, copy the attached patch to the ghc source package but do
> not add it to the series file. Instead, add the following to
> debian/rules:
> 
> ifeq (armel,$(DEB_HOST_ARCH))
> 
> patch -p1 < debian/patches/armel-revert-ticket-10375.patch
> endif
> 
> This will revert the fix from upstream ticket 10375 but only for
> armel which will make the package build on armel again (I am
> currently
> doing a testbuild to verify this but it's still building after two
> days on armel on qemu).
> 
> Then manually build ghc on an armel machine with the above changes
> in a prepared changeroot with the build dependencies taken from
> snapshots.debian.org. This way we workaround the fact that ghc
> is BD-Uninstallable on armel.
> 
> Then create a new version of hscolour (can be just a cosmetic change
> just so that we can create a new package version) and build and
> upload
> the package manually on armel.
> 
> This should resolve this issue and make ghc build all the haskell
> packages on armel again.
> 
> I have also talked to upstream and the general opinion is that ARM
> support generally still needs lots of work, independent of this
> particular bug now so I assume that in the future, we will be able
> to drop this workaround again and hopefully have ghc's build system
> differenriate between armel and armhf which is what would have
> prevented
> this regression in the first place.
> 
> Cheers,
> Adrian
> 
-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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

Bug#806949: ifupdown: some tweaks to networking.service

[Michael Biebl]

Am 20.12.2015 um 22:23 schrieb Guus Sliepen:
> On Sun, Dec 20, 2015 at 08:48:07PM +0100, Michael Biebl wrote:
> 
>> Guus already suggested to simply add
>>  WantedBy=network-online.target
>>
>> This would be a partial solution and better then nothing, I guess.
> 
> Since noone is against this, I'll go for this option. If I understand
> systemd correctly, I can just add a ifupdown-network-online.service
> later that also has a WantedBy=network-online.target, and only when both
> that one and networking.service has started will network-online.target
> be considered reached.

Correct. If multiple services hook into network-online.target and have
Before=network-online.target, all of them need to be started before
network-online.target is considered up.

>> The reason is, that the debian installer uses allow-hotplug by default.
>> And mounting remote file systems under systemd requires a properly
>> hooked up network-online.target.
>> Which means, for the vast majority of users with remote (NFS) mounts we
>> currently ship a broken setup.
> 
> Does the installer support configuring a Debian system which uses a NFS
> mount?

I don't know for sure, but I don't think so.


-- 
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#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[Joachim Breitner]

Dear haskell-arm,


Adrian has invested the time and come up with a way to keep GHC alive
on armel. (Thanks a lot!)

Unfortunately, there was a race condition with him coming up with a
solution and my removal bug being acted upon by the ftp-masters, which
now means that we have to re-bootstrap GHC on armel to get Adria’s fix
in. Due to the restricted possibility of installing additional and out-
of-archive-packages in the porterbox schroots, I cannot do that dance.

Does any DD on this list have full access to a sufficiently strong
armel machine and is willing to doe the steps as described by Adrian,
described in the mail below? That would be great!

Thanks,
Joachim

Am Sonntag, den 20.12.2015, 11:09 +0100 schrieb John Paul Adrian
Glaubitz:
> Hi!
> 
> So, here's my suggestion on how to fix this issue.
> 
> First, copy the attached patch to the ghc source package but do
> not add it to the series file. Instead, add the following to
> debian/rules:
> 
> ifeq (armel,$(DEB_HOST_ARCH))
> 
> patch -p1 < debian/patches/armel-revert-ticket-10375.patch
> endif
> 
> This will revert the fix from upstream ticket 10375 but only for
> armel which will make the package build on armel again (I am
> currently
> doing a testbuild to verify this but it's still building after two
> days on armel on qemu).
> 
> Then manually build ghc on an armel machine with the above changes
> in a prepared changeroot with the build dependencies taken from
> snapshots.debian.org. This way we workaround the fact that ghc
> is BD-Uninstallable on armel.
> 
> Then create a new version of hscolour (can be just a cosmetic change
> just so that we can create a new package version) and build and
> upload
> the package manually on armel.
> 
> This should resolve this issue and make ghc build all the haskell
> packages on armel again.
> 
> I have also talked to upstream and the general opinion is that ARM
> support generally still needs lots of work, independent of this
> particular bug now so I assume that in the future, we will be able
> to drop this workaround again and hopefully have ghc's build system
> differenriate between armel and armhf which is what would have
> prevented
> this regression in the first place.
> 
> Cheers,
> Adrian
> 
-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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

Bug#808476: Re : Bug#808476: Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[nicolas . patrois]

Le 20/12/2015 22:24:24, Rene Engelhard a écrit :

> libwhateverA -> libwhateverAv5 that is, of course.

I can’t upgrade because of gcc-5.3 that breaks so many packages.

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des 
humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Bug#805894: jessie-pu: package mdadm/3.3.2-5+deb8u1

[Marco Balestra]

On Fri, 18 Dec 2015 19:20:48 +0100 Marco Balestra  
wrote:

> I'm waiting with my brand new server, using 2*128GB pendrives for system, and 
> I failed installing grub using whatever combination of RAID1 with or without 
> LVM - it installs, then doesn't boot (or doesn't fine VGs and LVMs).
> While waiting, I'm trying to see whether the 32 bit version could work for 
> this.

Eventually, I succeeded! :-)

1. 2*USB3 pendrive in RAID1 /dev/md0 (now sde+sdf, during installation they 
where sdg+sdh).
2. 4*hd in RAID5 /dev/md1 (sda thru add)
3. NO LVM was used - I had errors when I tried to use LVM
4. debian-8.2.0-i386-netinst.iso on another pendrive, and network drivers on a 
4th pendrive

I've installed the whole operating system on /dev/md0, while /dev/md1 was 
mounted in /storage (each HD has a 8GB swap partition).
When asked to install grub:

1) switched to another shell - ctrl-alt-f2
2) # chroot /target /bin/bash
3) # mdadm -QDv /dev/md0 (to verify actual devices, in this case sdg and sdh)
4) # update-grub
5) # grub-install /dev/sdg
6) # grub-install /dev/sdh

At reboot power off, removed install+drivers pen drives, turn on: it works!

I tried to do the same with the amd64 8.2 netinstall, without success.
Now I'll have to understand why server doesn't boot, but it was a huge step 
forward :-)

Hope this helps,
Marco

Bug#743955: coreutils: corrupted files on heavily fragmented ext3 and ext4 partitions

[Andreas Mohr]

Hi,

just wanted to ask: what is the status on this now sufficiently old issue?

I keep hitting this via apt-listbugs reports
when trying to upgrade from coreutils 8.13-3 to 8.23-4.

However, note that the original report said
"[bug introduced in coreutils-8.11]"
(upstream version value, I assume)

So, while I am currently upgrading,
it looks like the issue actually already *is* present
on my system since I'm *post* 8.11,
thus the apt-listbugs warning is somewhat moot/useless here
since I'm already past potentially hitting a regression.

Thus, perhaps original attributes which were given as:
  Package: coreutils
  Version: 8.13-3.5
  Severity: grave

ought to be request-corrected to properly indicate an *earlier* Debian package 
version
that already was affected
(that way my apt-listbugs activity probably would not list this issue
during upgrade of the versions that are relevant on my system,
since there actually is no status change during this transition).

But perhaps the more modern version value was intentionally specified
in order to *do* always warn about this issue,
even on systems which already upgraded to an affected coreutils version...



And then, of course, there remains the question of
whether the currently provided (upgrade target) version (8.23-4)
already is one where this issue indeed is fixed.

However since original report said
"It is present in the wheezy coreutils version and is fixed in
jessie/sid.  A backport of the fix or an update of coreutils would be
welcomed for wheezy."

yet https://packages.debian.org/search?keywords=coreutils
reports version in jessie as 8.23-4 which is exactly my upgrade target
and which is a version which is said to be fixed,
I'd come to think that this bug report
is missing specification of some sort of "fixed-in" attribute.
Hmm, but there's no "fixed-in" tag (since I assume the way to mark this
is to simply and properly close a bug),
but perhaps using "wheezy" (https://www.debian.org/Bugs/Developer#tags)
would be the way to go?


As it stands, I'm predominantly irritated by the fact
that apt-listbugs somehow decides to keep reporting an issue
which *is* said to be fixed in this very upgrade target version
(and, to make matters much worse,
this warning report may actively and strongly deter people
from promoting an unhealthy system to a healthy state
i.e. an actually fixed version!!!)

[personally, I have now decided to proceed with the upgrade
since it seems correct and important]

Thanks,

Andreas Mohr

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[Joachim Breitner]

Am Sonntag, den 20.12.2015, 13:30 +0100 schrieb John Paul Adrian Glaubitz:
> 
> Well, the person who made the change which broke ghc on armel said that
> and I assume he is working on it in the future. His change, on the other
> hand, improved ghc on armhf. So nothing is saying he is not improved
> ghc on armel, too.

that is close, but not precisely true. Erik aimed to improve GHC on ARM
in general, and accidentally broke it on old ARM (armel in our speak).
I notified him of that problem, and he gave it a shot, but got stuck at
a segfaulting binary. Undoubtly he would have loved to have it fixed,
but could at that point not make progress. So the signal I got from him
was that it is unfortunate that it broke, but given that – in his
opinion – GHC on ARM was in a somewhat broken state before across the
board (after all, he had good reasons to do the change in the first
place), this is only superficially a regression. Also I noticed that he
stopped working on this particular issue. I do not blame him for that:
Quite contrary, I’m grateful for his work.

But the signal was: Upstream considered the ARM situation in 7.10.2,
although superficially compiling, so bad that his fix was of patch-
level-release urgency. Armel was broken, and no one actively and
urgently working on a patch. So therefore, it was only conclusive to
upload that to unstable and – after an early enough warning to d-arm
with none even saying that it would be pity, let along announce that
they would invest time – requests its removals.

In particular, I do not consider these actions premature.


I CCed Erik, not to necessarily to turn this into a wider discussion,
but just to give him the chance to correct any wrong statement I might
have made about what he did or the state of affairs.

Greetings,
Joachim


-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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

Bug#808476: Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[Rene Engelhard]

On Sun, Dec 20, 2015 at 09:31:57PM +0100, Rene Engelhard wrote:
> You can. And you should. (And at any libwhateverA -> libwhateverAx2 the
> removal of the former is expected.)

libwhateverA -> libwhateverAv5 that is, of course.

Regards,

Rene

Bug#806949: ifupdown: some tweaks to networking.service

[Guus Sliepen]

On Sun, Dec 20, 2015 at 08:48:07PM +0100, Michael Biebl wrote:

> Guus already suggested to simply add
>  WantedBy=network-online.target
> 
> This would be a partial solution and better then nothing, I guess.

Since noone is against this, I'll go for this option. If I understand
systemd correctly, I can just add a ifupdown-network-online.service
later that also has a WantedBy=network-online.target, and only when both
that one and networking.service has started will network-online.target
be considered reached.

> The reason is, that the debian installer uses allow-hotplug by default.
> And mounting remote file systems under systemd requires a properly
> hooked up network-online.target.
> Which means, for the vast majority of users with remote (NFS) mounts we
> currently ship a broken setup.

Does the installer support configuring a Debian system which uses a NFS
mount?

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Bug#792806: jessie-pu: package ieee-data/20150531.1

[Luciano Bello]

On Saturday 19 December 2015 19.39.26 Adam D. Barratt wrote:
> That's not quite what you meant. :-) The reversed diff looks 
okay, other
> than the version should be 20150531.1~deb8u1, please. With 
that change,
> feel free to upload.

done! thanks for your help and patience.

/l

Bug#808418: provide desktop entry file for taffybar

[Joachim Breitner]

Hi,

thanks!

Any reason why you don’t just add it to the packaging (now in Git!) and
upload it yourself? :-)

Greetings,
Joachim


Am Samstag, den 19.12.2015, 23:20 +0100 schrieb Thomas Koch:
> Package: taffybar
> Severity: wishlist
> Tags: upstream
> 
> Please install a file taffybar.desktop with the below content in
> /usr/share/applications. This is necessary to list taffybar in
> "RequiredComponents" in a session file. See man gnome-session or man
> cinnamon-session for reference.
> 
> [Desktop Entry]
> Version=1.0
> Type=Application
> Name=taffybar
> GenericName=Desktop Panel
> NoDisplay=true
> Exec=/usr/bin/taffybar
> TryExec=/usr/bin/taffybar
> Terminal=false
> Keywords=Status Bar;Notification Daemon;Systray
> 
> ___
> Pkg-haskell-maintainers mailing list
> pkg-haskell-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-m
> aintainers
> 
-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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

Bug#808476: Re : Re : Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[Rene Engelhard]

Hi,

On Sun, Dec 20, 2015 at 10:03:51PM +0100, nicolas.patr...@gmail.com wrote:
> > Again: please state how to reproduce it. With what unicode characters
> > and how you insert them *exactly*.
> 
> I select them from gucharmap and paste them in the equation editor (the 
> X-way with the mouse).

Ah, I see. gucharmap shows the U+ numbers.

> > And this is with version 5.0.4?
> 
> No:
> Version: 4.4.5.2
> Build ID: 40m0(Build:2)
> Locale : fr_FR.UTF-8

Again, please try with 5.0.4 and report back. I am not asking this for fun,
4.4.x is dead, not in testing since over 5 months and also unsupported upstream
(soon).

Regards,

Rene

Bug#798960: libvorbis: Please upgrade to 1.3.5

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> If the new library require a ABI change and a new soname, it is a
> good idea to talk to the release team before uploading thew new
> library, to check if it is a bad time to do such migration, but if
> there is no soname change and the library work for the cases we have
> time to test, lets get the library into wider testing.

I had a look and the library changes API and ABI in one case _ilog()
changed name to ov_ilog().  I suspect the _ilog() function is an
internal function. _ilog was presented lib/codebook.h and of_ilog() is
now presented in lib/misc.h.  None of these header files are present in
libvorbis-dev, so I guess no changes was done in the public API and ABI.
Based on this, I believe it is safe to upgrade libvorbis without
requering a rebuild and that no migration is needed.

Do you agree?

-- 
Happy hacking
Petter Reinholdtsen

Bug#808476: Re : Re : Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[nicolas . patrois]

Le 20/12/2015 22:00:48, Rene Engelhard a écrit :

> No. You say the "1" Unicode characters are affected. Your
> screenshots only show the resulting formula.

I tried some 1 characters, not only this F.

> Again: please state how to reproduce it. With what unicode characters
> and how you insert them *exactly*.

I select them from gucharmap and paste them in the equation editor (the 
X-way with the mouse).

> And this is with version 5.0.4?

No:
Version: 4.4.5.2
Build ID: 40m0(Build:2)
Locale : fr_FR.UTF-8

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des 
humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Bug#808433: nethogs doesn't start, saying "creating socket failed"

[Paul Kimoto]

On Sun, Dec 20, 2015 at 08:19:26PM +0100, Arnout Engelen wrote:
> I have released 0.8.1 with the fix.
>
> Could you get it from https://github.com/raboof/nethogs/releases and see if
> it works for you, too?

Yes, seems to work as before.

Bug#808476: Re : Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[Rene Engelhard]

On Sun, Dec 20, 2015 at 09:55:00PM +0100, nicolas.patr...@gmail.com wrote:
> Le 20/12/2015 21:31:57, Rene Engelhard a écrit :
> 
> > You can. And you should. (And at any libwhateverA -> libwhateverAx2
> > the removal of the former is expected.)
> 
> OK, goodbye kate, kdm, okular… O_o

I don't use kde, but kate ttbomk works, kdm -> sddm, ttbomk.
okular, well, don't know.

But yeah, KDE is a big mess.

> > Please. As you say it's only some part of characters it'd be good to
> > know which.
> 
> Here you are.

No. You say the "1" Unicode characters are affected. Your screenshots
only show the resulting formula.
Again: please state how to reproduce it. With what unicode characters and how
you insert them *exactly*.

And this is with version 5.0.4?

Regards,

Rene

Bug#808476: Re : Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[nicolas . patrois]

Le 20/12/2015 21:31:57, Rene Engelhard a écrit :

> You can. And you should. (And at any libwhateverA -> libwhateverAx2
> the removal of the former is expected.)

OK, goodbye kate, kdm, okular… O_o

> Please. As you say it's only some part of characters it'd be good to
> know which.

Here you are.
The blurred screenshot is what I see while editing the equation (the F 
character is the mathbb F, ie 𝔽), the other one is what I see while 
editing the text.
Note that sometimes the equation editor does not show correctly the 𝔽.
The same issue happens with other 1 utf8 characters.

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des 
humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Bug#802371: wheezy-pu: package eglibc/2.13-38+deb7u9

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2015-12-16 at 00:03 +0100, Aurelien Jarno wrote:
> On 2015-10-19 21:07, Aurelien Jarno wrote:
[...]
> > I would like to update the eglibc package in wheezy to fix the known
> > security issues for which there is a patch available. The changes match
> > the security bugs opened by the security team, their severity wasn't
> > high enough to warrant a DSA.
> > 
> > You'll find the corresponding diff against the current version in 
> > wheezy below.
> 
> A new security bug has been found in a meantime. Therefore please find
> below a new diff.

Apologies for the delay. Please go ahead.

Regards,

Adam

Bug#717313: lvm2: Enable issue_discards = 1 automatically on non-rotational (SSD) disks?

[Matt Taggart]

I agree that "issue_discards = 1" should become the default in lvm on 
Debian.

There is a case where you might not want TRIM/discards, there are security 
implications to enabling it with dm-crypt.  In the commit message which 
added this support, the author states:

  Note that discard will be never enabled by default because
  of security consequences, it is up to administrator
  to enable it for encrypted devices.

and in the added documentation:

  WARNING: allowing discard on encrypted device has serious irreversible
  security consequences, discarded blocks can be easily located on device
  later. This can lead to leak of information from ciphertext device
  (unique pattern for detecting filesystem type, used space etc).

https://www.redhat.com/archives/dm-devel/2011-July/msg00042.html

But if I understand it correctly, as long as dm-crypt defaults to not 
enabling it, it would still be fine if LVM did have it enabled, you just 
wouldn't have it all the way down the stack to the hardware and would lose 
the benefit but still be safe. It might be worth documenting that, 
something like:

  The option "issue_discards" is enabled by default on LVM in Debian.
  Note that in order to get the benefits of discard, it needs to be
  enabled in each block layer down to the actual hardware. Due to
  security implications, discard is disabled by default in dm-crypt,
  so if you are using that you should first consult the dm-crypt
  documentation to understand the implications before enabling.

Sound ok?

-- 
Matt Taggart
tagg...@debian.org

Bug#808554: dput-ng: doesnt respect --unchecked cli switch

[Sandro Tosi]

Package: dput-ng
Version: 1.10
Severity: normal

Hello,
running a test and using --unchecked, dput-ng still checks for a signature:

$ dput --unchecked people 
/home/morph/deb/build-area/sortedcontainers_1.4.4-1_amd64.changes 
Uploading sortedcontainers using sftp to people (host: people.debian.org; 
directory: /home/morph/tmp)
running allowed-distribution: check whether a local profile permits uploads to 
the target distribution
running checksum: verify checksums before uploading
running suite-mismatch: check the target distribution for common errors
running gpg: check GnuPG signatures before the upload
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.

No valid signature on sortedcontainers_1.4.4-1_amd64.changes: No signature on


I would expect not to.

Regards,
Sandro

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

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

Versions of packages dput-ng depends on:
ii  python-dput  1.10
pn  python:any   

Versions of packages dput-ng recommends:
ii  bash-completion  1:2.1-4.2

dput-ng suggests no packages.

-- no debconf information

Bug#808395: libprelude: FTBFS everywhere

[Niko Tyni]

On Sat, Dec 19, 2015 at 03:39:00PM +0100, gregor herrmann wrote:

> > /usr/bin/swig -c++ -I../bindings -I../bindings/c++/include -I../src/include 
> > -I../src/libprelude-error -perl5 -o perl/PreludeEasy.cxx libpreludecpp.i
> > perl/libpreludecpp-perl.i:1: Error: Unknown SWIG preprocessor directive: 
> > Exception (if this is a block of target language code, delimit it with %{ 
> > and %})

> The attached patch fixes these errors;

The patch looks good to me FWIW (but I don't really claim to know anything
about libprelude or swig :)

This seems to be fallout from 
 https://github.com/swig/swig/issues/217
and the #-comment lines were always ignored as unknown preprocessor
directives.

> now some warnings are left:

> ../bindings/c++/include/prelude-error.hxx:37: Warning 401: Nothing known 
> about base class 'std::exception'. Ignored.
> ../bindings/c++/include/prelude-error.hxx:48: Warning 503: Can't wrap 
> 'operator const char*' unless renamed to a valid identifier.
> ../bindings/c++/include/idmef.hxx:15: Warning 503: Can't wrap 'operator >>' 
> unless renamed to a valid identifier.

> In file included from PreludeEasy.cxx:1637:0:
> ../../config.h:1564:0: warning: "VERSION" redefined
>  #define VERSION "1.0.0"
>  ^
> :0:0: note: this is the location of the previous definition

All these were in the old build logs too, so at least they aren't
regressions.
-- 
Niko Tyni   nt...@debian.org

Bug#808057: cups braille dependencies [Was: Please release the cups-filters 1.4.0-2 Debian package]

[Samuel Thibault]

Hello,

Not much reaction on this issue for now :)

Samuel Thibault, on Tue 15 Dec 2015 19:56:54 +0100, wrote:
> - device-dependent drivers, which are basically simple shell scripts or
> C files, which don't depend on anything beyond bash and libc
> 
> - device-independent filters, which are able to convert documents to
> braille.  This part can make more or less use of liblouis, imagemagick,
> antiword, etc. to be able to turn documents into nice braille printing.

I'm thinking: the device-independent filters don't strictly depend on
all of that: they at least do support raw text conversion so at least
printing text will work.  When printing non-pure-text, we could make
the filters emit advices to users through the error messages, e.g.
"liblouisutdml-bin package missing for braille translation".

That way, users will have embosser drivers ready for testing, and will
immediately get advices about how to get further in a very logical way.

It then becomes a tasksel matter about what translation tools should be
preinstalled on a default Debian desktop system to provide at least
basic document printing support.

Samuel

Bug#798431: lvm2: OriginLV lost if CacheLV failed

[Matt Taggart]

Hi,

#798431 was filed against version 2.02.127-1, but looking at the upstream 
changelog at

https://git.fedorahosted.org/cgit/lvm2.git/tree/WHATS_NEW

I see lots of cache related changes in newer releases. Maybe someone can 
try to repeat this bug with the 2.02.133-2 package in stretch/sid or if the 
package could be updated to the latest 2.02.138 upstream release (just 
released on Dec 14) then you could test with that.

-- 
Matt Taggart
tagg...@debian.org

Bug#808476: Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[Rene Engelhard]

On Sun, Dec 20, 2015 at 09:21:31PM +0100, nicolas.patr...@gmail.com wrote:
> Le 20/12/2015 19:35:54, Rene Engelhard a écrit :
> 
> > Can you please try with a uptopdate version. A version from a > 5
> > months old testing is not really helpful here. (And it's unsupported 
> > by now.)
> 
> I can’t fully upgrade my testing because…
> OK, I try to remove 595 packages. O_o

You can. And you should. (And at any libwhateverA -> libwhateverAx2 the
removal of the former is expected.)

And if you use third-party stuff not transitioned... - well not my problem.
testing changes and if you can't keep up for 5 months...

> > How did you input them? (Just to reproduce.)
> 
> I copy them from gucharmap.
> Do you want a screenshot?

Please. As you say it's only some part of characters it'd be good to know
which.

Regards,

Rene

Bug#439080: drop severity of warned dbc issues

[Paul Gevers]

control: severity -1 wishlist

Since 1.8.50 at least the admin is warned about these issue, making them
wishlist items for now.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#605090: [RFC] Proposal for a new linux-grsec source package

[Jacob Appelbaum]

It may make sense for us to have a package of paxrat with common
configurations for Debian users:

  https://github.com/subgraph/paxrat

This would ensure that everyone can use this kernel and have xorg work
as expected, for example.

Otherwise, I think we will see a lot of people who just run:

  paxctl -m /usr/bin/Xorg

paxctl one off runs isn't great for a full solution.

paxrat improves on this as package updates and other things can stomp
on pax related xattributes. paxrat seems very very useful in this
context - we get configuration files as well as dpkg hooks.

Bug#793101: Yubikey core error: no yubikey present

[meskio]

Package: yubikey-personalization
Version: 1.17.2-1
Followup-For: Bug #793101

Dear Maintainer,

I see the same issue in my system. U2F works fine in chromium (I did
modify udev to give me rights no the device, but this is a different
bug). I'm failing on making OTP to work. All the yk* tools tell me the
same:

# ykinfo -v
Yubikey core error: no yubikey present

I tryed to compile yubikey-personalization from the git repo (using
libyubikey from debian) and I see the same problem. So I'm starting to
think is not a debian specific issue. Might it be a problem on my
system? Or a bug in upstream?

My lsusb output:

Bus 001 Device 069: ID 1050:0120 Yubico.com Yubikey Touch U2F Security Key
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x1050 Yubico.com
  idProduct  0x0120 Yubikey Touch U2F Security Key
  bcdDevice4.18
  iManufacturer   1 Yubico
  iProduct2 Security Key by Yubico
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   41
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower   30mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.10
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  34
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04  EP 4 OUT
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   2
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84  EP 4 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   2


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

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

Versions of packages yubikey-personalization depends on:
ii  libc6  2.19-22
ii  libjson-c2 0.11-4
ii  libusb-1.0-0   2:1.0.20-1
ii  libykpers-1-1  1.17.2-1
ii  libyubikey01.13-1

yubikey-personalization recommends no packages.

yubikey-personalization suggests no packages.

-- no debconf information

Bug#808476: Re : Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[nicolas . patrois]

Le 20/12/2015 19:35:54, Rene Engelhard a écrit :

> Can you please try with a uptopdate version. A version from a > 5
> months old testing is not really helpful here. (And it's unsupported 
> by now.)

I can’t fully upgrade my testing because…
OK, I try to remove 595 packages. O_o

> How did you input them? (Just to reproduce.)

I copy them from gucharmap.
Do you want a screenshot?

Ha, is-it possible to chose the font of a single char in the math 
editor without messing with the styles?

nicolas

Bug#808282: wheezy-pu: package dbconfig-common/1.8.47+nmu1

[Paul Gevers]

tags 808282 patch
retitle 808282 wheezy-pu: package dbconfig-common/1.8.47+nmu1+deb7u1
tags 806247 patch
retitle 806247 jessie-pu: package dbconfig-common/1.8.47+nmu3+deb8u1
thanks

On Fri, 04 Dec 2015 11:54:24 +0100 Paul Gevers  wrote:
> Please find attached my proposed fix for jessie. The delta for wheezy is
> nearly the same, minus the changelog.

And here is the debdiff for wheezy.

Paul
diff -Nru dbconfig-common-1.8.47+nmu1/debian/changelog 
dbconfig-common-1.8.47+nmu1+deb7u1/debian/changelog
--- dbconfig-common-1.8.47+nmu1/debian/changelog2011-12-24 
09:26:16.0 +0100
+++ dbconfig-common-1.8.47+nmu1+deb7u1/debian/changelog 2015-12-20 
20:58:03.0 +0100
@@ -1,3 +1,11 @@
+dbconfig-common (1.8.47+nmu1+deb7u1) wheezy; urgency=medium
+
+  * Fix permission of PostgreSQL backup files, thanks Simon Ruderich
+(Closes: #805638)
+  * Repair permissions of already created backups
+
+ -- Paul Gevers   Sun, 20 Dec 2015 20:19:30 +0100
+
 dbconfig-common (1.8.47+nmu1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru dbconfig-common-1.8.47+nmu1/debian/dbconfig-common.postinst 
dbconfig-common-1.8.47+nmu1+deb7u1/debian/dbconfig-common.postinst
--- dbconfig-common-1.8.47+nmu1/debian/dbconfig-common.postinst 2009-02-17 
23:05:34.0 +0100
+++ dbconfig-common-1.8.47+nmu1+deb7u1/debian/dbconfig-common.postinst  
2015-12-20 20:19:21.0 +0100
@@ -15,4 +15,11 @@
 
 dbc_write_global_config
 
+# Previously dumped databases in /var/cache/dbconfig-common/backups may
+# (depending on the local umask) be readable by everybody (bts: #805638). Limit
+# the permissions here on all files in that folder.
+if [ -d /var/cache/dbconfig-common/backups/ ] ; then
+find /var/cache/dbconfig-common/backups/ -type f -exec chmod 600 {} \;
+fi
+
 #DEBHELPER#
diff -Nru dbconfig-common-1.8.47+nmu1/internal/pgsql 
dbconfig-common-1.8.47+nmu1+deb7u1/internal/pgsql
--- dbconfig-common-1.8.47+nmu1/internal/pgsql  2010-03-28 12:11:37.0 
+0200
+++ dbconfig-common-1.8.47+nmu1+deb7u1/internal/pgsql   2015-12-20 
20:19:20.0 +0100
@@ -174,14 +174,14 @@
local extra retval PGSSLMODE localuser _dbc_asuser dumpfile old_umask
dumpfile=$1
localuser=`_dbc_psql_local_username`
-   touch $dumpfile
-   chown $localuser $dumpfile
PGSSLMODE="prefer"
retval=0
_dbc_psql_cmd_setup
if [ "$dbc_ssl" ]; then PGSSLMODE="require"; fi
old_umask=`umask`
umask 0066
+   touch $dumpfile
+   chown $localuser $dumpfile
extra=`_dbc_psql_cmd_args`
extra="-f \"$dumpfile\" $extra"
_dbc_debug "su -s /bin/sh $localuser -c \"env HOME='$_dbc_pgsql_tmpdir' 
PGPASSFILE='$_dbc_pgsql_tmpdir/.pgpass' PGSSLMODE='$PGSSLMODE' pg_dump $extra 
$dbc_dbname\" 2>&1"


signature.asc
Description: OpenPGP digital signature