Bug#786710: armada-backlight: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/armada-backlight.git/commit/?id=d994c086c57ba6afd6b62a16d5951240844e9d8a

Bug#718012: blhc: please check for unrecognized configure options

[Jari Aalto]

Hi Simon, please let me know if this might already been
fixed in latest version:

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

Thanks,
Jari

Bug#841475: False positive outdated-autotools-helper-file with dh compat 10

[Niels Thykier]

Michael Biebl:
> Package: lintian
> Version: 2.5.48
> Severity: normal
> 
> Hi,
> 
> I use dh compat 10 with a package that has very old config.{sub,guess}
> files:
> 
> W: libgnomecanvas source: outdated-autotools-helper-file config.guess
> 2009-11-20
> W: libgnomecanvas source: outdated-autotools-helper-file config.sub
> 2009-11-20
> 
> Since dh with compat level 10 run autoreconf and the autotools addon by
> default, [...]
> 

Clarification:
 * debhelper added this /before/ version 10 in a new helper which is
   enabled by default in all supported compat levels
 * it does not use the autotools-dev addon (but it does use the package
   to provide the updated files).

So basically all "dh $@" packages should be exempt from this tag.

> I've dropped explicit Build-Depends on dh-autoreconf or autotools-dev,
> since those are pulled in by debhelper (>= 10) now.
> 
> Regards,
> Michael
> 
> 
> [...]
> 

Thanks,
~Niels

Bug#727327: bbe: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/bbe.git/commit/?id=2b5c498771e1fac3a3801e19292423a93fda93fa

Bug#725484: A way to override blhc false-positives

[Jari Aalto]

Hi Simon, could you take a look at this and know what you
think:

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

I think the request is for reading configuration file at startup:

  /.blhc-ignore   OR if not exists, search ...
  $HOME/.blhc-ignore

An idea for the file format:

  - Each line contais regexp to MATCH. Matching lines
are ignored.
  - Empty lines are skipped
  - Comment lines starting with "^[ \t]*#" are skipped

Thanks,
Jari

Bug#784182: blhc: warns about disabled flags

[Jari Aalto]

Hi simon, let me know if this is possibly already fixed in
latest version:

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

Thanks,
Jari

Bug#796560: blhc: Please detect lack of sanitation flags

[Jari Aalto]

Hi Simon, Could you take a look at this report:

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

Thanks
Jari

Bug#782207: colortest: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/colortest.git/commit/?id=94f6c267912a2bce3f1172a5abb9571e78726503

Bug#794155: bsdiff FTCBFS: uses build arch compiler

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/bsdiff.git/commit/?id=f1268626610e2bbec29f3de2e2050f3397cd8261

Bug#744417: cbm: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/cbm.git/commit/?id=ee55b6a9f26c7be0780c3fb6149bfa82b47f021e

Bug#782206: cfourcc: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/cfourcc.git/commit/?id=2a7d76563380f70ba38bce343e85d6c618bde014

Bug#782211: desproxy: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/dbar.git/commit/?id=3e474047a5bcacf8fc0b3817a518531625e9593d

Bug#753281: colortest-python: New home page.

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/colortest-python.git/commit/?id=a9bb34289305909d36fa87a85d0e16472fa59d23

Bug#782751: corkscrew: IPv6 support

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/corkscrew.git/commit/?id=b67e821dfdf4ff1eb130e0754e620a9bf3625448

Bug#814751: copyright-update: Encode copyright sign to make regexp match

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/copyright-update.git/commit/?id=90ec12040c3b908e04473673a63c8934969c98f5

Bug#782209: dbar: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/dbar.git/commit/?id=3e474047a5bcacf8fc0b3817a518531625e9593d

Bug#782208: colortest-python: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/colortest-python.git/commit/?id=8fee33e0f8fd32396a75450c3beb35f83f26c8ff

Bug#841431: apt-cacher-ng: FTBFS on mips/mipsel: undefined reference to '__atomic_fetch_add_8'

[Eduard Bloch]

Control: retitle 841431 FTBFS on m68k/powerpcspe
Control: reopen 841431

I wanted to extend this patch to a couple of other architectures and
failed to commit the change prior to release :-(

To be fixed in an upstream release soon.

Regards,
Eduard.

Bug#785115: dos2unix: New upstream version

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/dos2unix.git/commit/?id=15f8d19191c2c9c087e4bdc64ab06cc1aa84b705

Bug#787303: dos2unix: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/dos2unix.git/commit/?id=99ea5a9c524d69ad34d3c9327f92323c6ee2e7af

Bug#782214: fspanel: please make the build reproducible

[Jari Aalto]

tags 782214 + pending
thanks

Fixed
https://anonscm.debian.org/cgit/collab-maint/fspanel.git/commit/?id=21b447e354c70f7e0f9d6477d1c9b6319bc494c4

Bug#782215: fuse-posixovl: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/fuse-posixovl.git/commit/?id=ce2f41d5d4ab4f5cb5a8afb7734f30ca84a04773

Bug#782216: please make the build reproducible

[Jari Aalto]

Fixed
https://anonscm.debian.org/cgit/collab-maint/hpanel.git/commit/?id=3572e50cfb35abb29a77bac7343b60e5bb8cbc7a

Bug#740678: new abiword release

[Adam Borowski]

Hi!
Arypsg and Carlos, you expressed interest about abiword.  Is either of you
going to update it to the just released new version?

I can do this myself, but, I don't use abiword and am just one of people
doing QA.  Such maintenance is much better done by a proper maintainer.

It's a package with a fair amount of users, thus it'd be nice to get the
bugfixed in.


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

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

[韓達耐]

Hi Hilmar

Thanks for the trace. I'm traveling now so I will need to test this.  At
home I only have access to amd64, but I'll test it on other architectures
too.
My guess is a behavioural change; the compiler warnings have been around
for quite a while and it's time to revisit some of the variable types.

Cheers

On 19 Oct 2016 22:01, "Hilmar Preuße"  wrote:

> Am 19.10.2016 um 17:20 schrieb Danai SAE-HAN (韓達耐):
>
> Hi all,
>
> It looks like a problem with the wftodm binary.  This is an important piece
>> in the creation of the fonts.
>> I will only have access to my PC next week Thursday (27 October 2016) to
>> check the C source code and replicate it on amd64.  Please bear with me
>> for
>> a while.
>>
>> I *think* I can reproduce the bug.
>
> Here is the gdb backtrace:
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  strlen () at ../sysdeps/x86_64/strlen.S:106
> 106 ../sysdeps/x86_64/strlen.S: No such file or directory.
> (gdb) bt
> #0  strlen () at ../sysdeps/x86_64/strlen.S:106
> #1  0x2ba08dfdbda3 in _IO_vfprintf_internal (s=s@entry=0x7ffd926eb3f0,
> format=, format@entry=0x5643d866b22e "/StdHW [ %s ]
> |-\n",
> ap=ap@entry=0x7ffd926eb518) at vfprintf.c:1637
> #2  0x2ba08dffcacb in __IO_vsprintf (
> string=0x7ffd926eb620 "/StdHW [ re{16 16} |-\n",
> format=0x5643d866b22e "/StdHW [ %s ] |-\n", args=args@entry
> =0x7ffd926eb518)
> at iovsprintf.c:42
> #3  0x2ba08dfe2327 in __sprintf (s=, format= out>)
> at sprintf.c:32
> #4  0x5643d866a8e2 in e_printf (form=, i0= out>,
> i1=, i2=, i3=,
> i4=, i5=1936353124, i6=-1838284703, i7=0,
> i8=-1909291776,
> i9=0) at wftodm.c:306
> #5  0x5643d866aa77 in output_pfa (file=1) at wftodm.c:255
> #6  0x5643d8669d3a in main (ac=, ag=)
> at wftodm.c:158
>
> And here is the function e_printf() in question:
>
> e_printf(form,i0,i1,i2,i3,i4,i5,i6,i7,i8,i9)
> char *form;
> {
>   int len,i;
>   unsigned char buf[4096];
>   sprintf(buf,form,i0,i1,i2,i3,i4,i5,i6,i7,i8,i9);
>   len=strlen(buf);
>   for(i=0;i e_putchar(buf[i]);
> }
>
> In line 255 (function output_pfa) it is called like this
>
> e_printf("/StdHW [ %s ] |-\n",StdHW);
>
> I /guess/ there is a thinks in string processing. Sorry, I don't have
> enough knowledge in C to help here. Does that ring anywhere a bell on your
> side? Is the problem reproducible e.g. in i386?
>
> Hilmar
> --
> http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org
>

Bug#841486: sakura: too many tabs -> window extends to other virtual screens

[Toni Mueller]

Package: sakura
Version: 3.3.4-2
Severity: normal

Dear Maintainer,

when I open enough tabs that the tab titles do not fit anymore, sakura
changes the window size to make the titles fit. The result is that I can
see parts of the terminal on a different monitor, obscuring other
windows there (at least in conjunction with awesome).

I did not find a way to adjust this behaviour.


Cheers,
Toni


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

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

Versions of packages sakura depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-3
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.1-1
ii  libgnutls30  3.5.4-2
ii  libgtk-3-0   3.22.1-1
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libvte-2.91-00.46.0-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

sakura recommends no packages.

sakura suggests no packages.

-- no debconf information

Bug#841113: ITP: extremetools -- tools for running processes under extreme uid and gid

[Adrian Bunk]

On Wed, Oct 19, 2016 at 09:33:14AM -0200, Henrique de Moraes Holschuh wrote:
> On Wed, Oct 19, 2016, at 06:56, Jan Mojzis wrote:
> > >I read manpage on github, but did not understood, what exactly this
> > > program provides.  Can it replace creation system users for dropping
> > > privileges?
> > 
> > It's doesn't create users.
> > It only drops privileges (extremesetuidgid) or sets $UID/$GID env.
> > variables (extremeenvuidgid).
> > 
> > For example:
> > extremesetuidgid -b 10 sleep 1
> > 
> > runs command 'sleep 1' under unprivileged uid/gid (computed getpid()
> > +10) 
> > e.g. for:
> > pid=10 ... uid=gid=100010
> > pid=11 ... uid=gid=100011
> > pid=12 ... uid=gid=100011
> 
> I am just wondering why is it called "extreme"?

"extremely outdated"?

This sounds like a hack from ~ 20 years ago when people realized that 
running several programs at the same time as nobody does not isolate
them from each other.

Much better solutions for restricting what a process can or cannot do 
are now available.

> It looks more like a functionality related to "exclusive" guid/uid,
> instead...

20 years ago such a hack would at least have ensured that every process 
has a unique uid.

Even this is no longer true.


tinysshd [1] is another worrisome example.

Writing an own "tiny" sshd from scratch, and the result is not even 
smaller than the dropbear everyone else uses for that purpose.

To make the NIH complete, it uses own versions of standard C library
string functions and an own (pretty primitive) build system.


cu
Adrian

[1] thank god only in experimental so far

-- 

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

Bug#841485: ITP: node-grunt-legacy-log-utils -- Static methods for the Grunt 0.4.x logger

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-grunt-legacy-log-utils
  Version : 1.0.0
  Upstream Author : "Cowboy" Ben Alman (http://benalman.com/)
* URL : http://gruntjs.com/
* License : Expat
  Programming Lang: JavaScript
  Description : Static methods for the Grunt 0.4.x logger.




signature.asc
Description: OpenPGP digital signature

Bug#826790: libset-scalar-perl: Package doesn't support multi-arch

[Randy Li]

Package: libva-dev
Source: libva
Version: 1.7.2-1
Installed-Size: 680
Maintainer: Debian Multimedia Maintainers 


Architecture: amd64
Depends: libva-drm1 (= 1.7.2-1), libva-egl1 (= 1.7.2-1), libva-glx1 (= 
1.7.2-1), libva-tpi1 (= 1.7.2-1), libva-wayland1 (= 1.7.2-1), 
libva-x11-1 (= 1.7.2-1), libva1 (= 1.7.2-1), libwayland-dev (>= 1.0.0), 
libset-scalar-perl


It problem still exists. I think the problem is that libset-scalar-perl 
is a non-arch package, which could use the build interrupter. But the 
multiarch didn't regard it as non-arch.

Bug#780275: pkexec: Synpatic & gParted fails to authenicate

[Michael Biebl]

Control: tags -1 + moreinfo unreproducible

On Wed, 11 Mar 2015 07:26:11 -0700 Thomas McAtee
 wrote:
> Package: pkexec
> Version: policykit
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> Found when going to check Synaptic Package manager. Tested gparted afterwards
> with same result. This is in Jessie 32bit on desktop and Wheezy 32bit on
> laptop. Wheezy 32bit on desktop seems to be ok for moment. I use XFCE.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> Created personal launchers using gksu on the two so I could use them.
>* What was the outcome of this action?
> That works for time being but still have issues when trying to sign in with
> regular login screens for the two.
> 
>* What outcome did you expect instead?
> Was waiting to see if an upgrade caused this and newer one would fix issue.

What is the exact error message(s) you get?
Do you have anything in /var/log/auth.log?

-- 
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#841484: openntpd: detects but fails to actually set time after suspend+resume

[Adam Borowski]

Package: openntpd
Version: 1:5.7p4-4
Severity: normal


Since this machine was suspended+resumed, I get a large clock skew, around
15 seconds per hour.  openntpd keeps logging "adjusting local clock by ..."
with every-increasing values but doesn't actually apply the adjustments.
Restarting the daemon doesn't seem to help.

Commented log attached.


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

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

Versions of packages openntpd depends on:
ii  adduser  3.115
ii  init-system-helpers  1.45
ii  libc62.24-5
ii  netbase  5.3

openntpd recommends no packages.

openntpd suggests no packages.

-- no debconf information
Oct 18 02:31:17 umbar ntpd[10526]: constraint certificate verification turned 
off
Oct 18 02:31:17 umbar ntpd[10526]: ntp engine ready
Oct 18 02:31:36 umbar ntpd[10526]: peer 94.125.129.7 now valid
Oct 18 02:31:38 umbar ntpd[10526]: peer 78.108.145.1 now valid
Oct 18 02:31:39 umbar ntpd[10526]: peer 193.106.216.30 now valid
Oct 18 02:31:39 umbar ntpd[10526]: peer 31.3.104.60 now valid
Oct 18 02:31:40 umbar ntpd[10526]: peer 178.79.160.57 now valid
Oct 18 02:31:40 umbar ntpd[10526]: peer 5.34.248.224 now valid
Oct 18 02:31:40 umbar ntpd[10526]: peer 163.172.216.210 now valid
Oct 18 02:34:35 umbar ntpd[2766]: constraint certificate verification turned off
Oct 18 02:34:35 umbar ntpd[2766]: ntp engine ready
Oct 18 02:34:36 umbar ntpd[2766]: reply from 91.232.160.1: not synced (alarm), 
next query 3129s
Oct 18 02:34:55 umbar ntpd[2766]: peer 194.29.130.252 now valid
Oct 18 02:34:56 umbar ntpd[2766]: peer 194.177.4.1 now valid
Oct 18 02:34:57 umbar ntpd[2766]: peer 62.148.67.62 now valid
Oct 18 02:34:57 umbar ntpd[2766]: peer 94.23.210.194 now valid
Oct 18 02:34:57 umbar ntpd[2766]: peer 78.46.189.152 now valid
Oct 18 02:34:58 umbar ntpd[2766]: peer 213.199.225.40 now valid
Oct 18 02:35:00 umbar ntpd[2766]: peer 194.177.4.2 now valid
Oct 18 02:35:01 umbar ntpd[2766]: peer 94.154.96.7 now valid
Oct 18 02:35:02 umbar ntpd[2766]: peer 213.199.225.30 now valid
Oct 18 02:35:57 umbar ntpd[2765]: adjusting local clock by -0.296188s
Oct 18 02:39:11 umbar ntpd[2765]: adjusting local clock by -0.198098s
Oct 18 02:39:35 umbar ntpd[2766]: 9 out of 20 peers valid

Oct 20 07:44:49 umbar ntpd[2690]: adjusting clock frequency by 0.343997 to 
31.548984ppm
Oct 20 07:45:30 umbar ntpd[2691]: peer 194.54.80.30 now invalid
Oct 20 07:45:50 umbar ntpd[2691]: peer 193.219.61.120 now invalid
Oct 20 07:50:49 umbar ntpd[2691]: peer 194.54.80.30 now valid
Oct 20 07:51:12 umbar ntpd[2691]: peer 193.219.61.120 now valid
Oct 20 08:03:03 umbar ntpd[2690]: adjusting clock frequency by 0.164055 to 
31.713036ppm
Oct 20 08:09:16 umbar ntpd[2691]: peer 2001:67c:24c:1::21 now invalid
Oct 20 08:14:36 umbar ntpd[2691]: peer 2001:67c:24c:1::21 now valid
Oct 20 08:15:14 umbar ntpd[2691]: peer 2001:67c:24c:1::21 now invalid
Oct 20 08:15:17 umbar ntpd[2691]: peer 95.154.26.34 now invalid
Oct 20 08:20:37 umbar ntpd[2691]: peer 2001:67c:24c:1::21 now valid
Oct 20 08:20:40 umbar ntpd[2691]: peer 95.154.26.34 now valid
Oct 20 08:30:06 umbar ntpd[2690]: adjusting clock frequency by 0.868006 to 
32.581034ppm
Oct 20 08:57:04 umbar ntpd[2691]: reply from 194.177.4.2: not synced (alarm), 
next query 3017s
suspended then resumed here
Oct 20 14:56:30 umbar ntpd[2691]: peer 2001:67c:24c:1::20 now invalid
Oct 20 14:56:30 umbar ntpd[2691]: peer 198.84.61.242 now invalid
Oct 20 15:10:07 umbar ntpd[2691]: peer 198.84.61.242 now valid
Oct 20 15:10:22 umbar ntpd[2691]: peer 2001:67c:24c:1::20 now valid
Oct 20 17:06:04 umbar ntpd[2690]: adjusting local clock by 14.930272s
Oct 20 17:13:34 umbar ntpd[2691]: peer 194.54.80.30 now invalid
Oct 20 17:14:52 umbar ntpd[2691]: peer 144.76.14.132 now invalid
Oct 20 17:16:59 umbar ntpd[2691]: peer 178.16.23.50 now invalid
Oct 20 17:18:55 umbar ntpd[2691]: peer 194.54.80.30 now valid
Oct 20 17:19:45 umbar ntpd[2691]: peer 198.84.61.242 now invalid
Oct 20 17:20:10 umbar ntpd[2691]: peer 144.76.14.132 now valid
Oct 20 17:22:16 umbar ntpd[2691]: peer 193.219.61.120 now invalid
Oct 20 17:22:19 umbar ntpd[2691]: peer 178.16.23.50 now valid
Oct 20 17:25:06 umbar ntpd[2690]: adjusting local clock by 39.116309s
Oct 20 17:25:06 umbar ntpd[2691]: clock is now unsynced
Oct 20 17:25:07 umbar ntpd[2691]: peer 178.16.23.50 now invalid
Oct 20 17:26:11 umbar ntpd[2690]: adjusting local clock by 39.472922s
Oct 20 17:27:50 umbar ntpd[2690]: adjusting local clock by 40.043074s
Oct 20 17:29:18 umbar ntpd[2691]: peer 91.236.251.5 now invalid
Oct 20 17:30:31 umbar ntpd[2691]: peer 198.84.61.242 now valid
Oct 20 17:30:54 umbar ntpd[2691]: peer 

Bug#841261: ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard

[Paul Wise]

Control: reassign -1 src:linux 4.8~rc8-1~exp1
Control: retitle -1 linux: 4.8 causes crashes in ulogd2 due to bug in netfilter 
code

On Thu, 2016-10-20 at 11:00 +0200, Julien Cristau wrote:

> I think this should just be reassigned, there's not much point working
> around a kernel bug.

Doing that with this mail.

Linux folks: please close this bug when this netfilter patch for Linux
4.8 reaches Debian.

https://patchwork.ozlabs.org/patch/680773/

It is needed for acker.d.o and aagaard.d.o, which run the Linux 4.8
version from Debian experimental.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#841434: whohas: cannot fetch ancient Fedora and OpenBSD releases

[Paul Wise]

Control: tags -1 + fixed-upstream

On Thu, 2016-10-20 at 17:09 +0100, James Cowgill wrote:

> Fedora 20 and 21 are no longer hosted on dl.fedoraproject.org.

You can work around the Fedora issue in your config:

/usr/share/doc/whohas/examples/whohas.cf

> Similarly OpenBSD 5.7 has gone away.

You can fix this in your config but the directory listing for 6.0 no
longer matches the hardcoded regexes in whohas.

I've fixed all of the above issues in upstream git.

> use whatever the latest version of a particular distribution is.

It doesn't currently know how to figure those out.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#841373: mv: cannot stat 'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such file or directory

[Trent W. Buck]

This is the same bug at Ubuntu; it has more analysis:

  
https://bugs.launchpad.net/ubuntu/+source/pepperflashplugin-nonfree/+bug/1632870

In short:

  * Google Chrome 54+ does not bundle libpepflashplayer.so.

  * pepperflashplugin-nonfree will have to get it from somewhere else;
either adobe.com directly, or Google's "redirector.gvtl.com" thing.

It looks like Ubuntu don't care about pepperflashplugin-nonfree,
because they recommend adobe-flashplugin from canonical-partners.

  https://wiki.ubuntu.com/Chromium/Getting-Flash

Debian has no equivalent.

Bug#841483: ITP: golang-gopkg-macaroon.v1 -- A native Go implementation of macaroons

[Michael Hudson-Doyle]

Package: wnpp
Severity: wishlist
Owner: "Michael Hudson-Doyle" 

* Package name: golang-gopkg-macaroon.v1
  Version : 0.0~git20150121.0.ab3940c
  Upstream Author : Roger Peppe 
* URL : http://gopkg.in/macaroon.v1
* License : BSD-3-clause
  Programming Lang: Go
  Description : A native Go implementation of macaroons

The macaroon package implements macaroons as described in the paper "Macaroons:
Cookies with Contextual Caveats for Decentralized Authorization in the Cloud"
(http://theory.stanford.edu/~ataly/Papers/macaroons.pdf).

This package is a new dependency of snapd.

It is packaged in Ubuntu already and the packaging only needs to be adapted
in the usual trivial ways for Debian. I've uploaded the packaging I intend to
upload to 
https://anonscm.debian.org/cgit/pkg-go/packages/golang-gopkg-macaroon.v1.git/

This package will be maintained in the pkg-go team. I will require a sponsor
for the initial upload (I am a DM).

Bug#840153: Should have various tutorial manpages

[Sean Whitton]

Dear Ian,

On Fri, Oct 21, 2016 at 01:28:14AM +0100, Ian Jackson wrote:
> All I saw in your commit message was the rewrapping.  But now I look
> at it again there is an additional blank line too.
> 
> The rewrapping replaces the semantic newlines (which I used when I
> rewrote that paragraph) with what looks like the result of an
> automatic wordwrap algorithm.

Yes, just my habit of hitting M-q in Emacs.

Are the semantic newlines for the benefit of someone editing the .pod,
or for the benefit of a future natural-language parsing computer?  I
think I see what you did, but I don't yet see the benefit.

I think it would be best if you just made a commit on your master branch
just adding a new line.  I can prepare a patch if you really want...

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#841482: override: libbonoboui2-0:oldlibs/optional, libbonoboui2-common:oldlibs/optional

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

Please move those packages to oldlibs
The library is obsolete nowadays and its use no longer encouraged.

Bug#841481: override: libgtksourceview2.0-*:oldlibs/optional

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

override: libgtksourceview2.0-0:oldlibs/optional
override: libgtksourceview2.0-common:oldlibs/optional
override: libgtksourceview2.0-dev:oldlibs/optional

Please move those packages to oldlibs
The library is obsolete nowadays and its use no longer encouraged.
It has been replaced by gtksourceview3

Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory"

[Anders Kaseorg]

On Thu, 20 Oct 2016, Ian Jackson wrote:
> Does that seem right ?

Sounds right to me.

> I have an outstanding question: do I need to lock against concurrent
> updates by other programs ?  That is, can I run git-gc and (say)
> git-receive-pack at the same time, safely ?

This is safe by default, as long as you don’t use something like 
--prune=all or gc.pruneExpire=all.

Anders

Bug#841480: euca2ools: please release 3.3.1

[Scott Moser]

Package: euca2ools
Version: 3.1.0-1
Severity: normal

Dear Maintainer,

Hi,
Bug 1527341 in ubuntu (http://bugs.launchpad.net/bugs/1527341) was
filed, requesting a fix for the lack of 'ppc64el' as an arch.
That bug fix is trivially pulled.  However, Ubuntu does not currently
have a delta on this package. And so we'd like to not pick one up.

Additionally, it seems like the maintainer has already done the work
of merging the debian branch at [1] with the upstream tag 3.3.1.
  [1] https://anonscm.debian.org/gitweb/?p=pkg-eucalyptus/euca2ools.git

So, I'm requesting a release of 3.3.1 to Debian that we would then sync
to Ubuntu.

I've quickly done a build of euca2ools from git and trivially verified
that euca-describe-images is functional and euca-bundle-image shows
the 'ppc64el' arch in its help output.


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

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

Bug#841479: xfce4-power-manager: Interface wider than screen when battery model is a long string.

[Beardy]

Package: xfce4-power-manager
Versions: 1.4.1-1 and 1.4.4-4
Severity: normal
Tags: upstream

Dear Maintainer,

* What led up to the situation?

Attempted to use the package on a General Dynamics / Itronics GD8200
notebook with
an original OEM battery installed.

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

I tried resizing fonts, changing theme, and internet searches for solutions.

* What was the outcome of this action?

The interface cannot be resized to fit on-screen, the screen having a
resolution
set at 1024x768.  I located an archived Debian bug #763713 which I believe
to be
related, the report also contains a proposed patch, which would fix the
issue if
the code is still applicable after the changes made upstream to half fix
this.

However, upstream adopted a different approach which only deals with the
case
where the battery is not recognised creating a long string of characters to
be
rendered on the devices tab, not where the manufacturer's name or model
details 
result in a long string, which is the case for GD/Itronix notebook
batteries.

* Additional information

In the original bug report at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763713

Message #42 links to additional information requested by upstream at the
time:
https://bugzilla.xfce.org/show_bug.cgi?id=11217#c1

As it is relevant to reproducing the issue, I provide it below:

* Begin paste from terminal *

beardy@GD8200-DB-BL:~$ upower --enumerate
/org/freedesktop/UPower/devices/line_power_AC0
/org/freedesktop/UPower/devices/battery_BAT1
/org/freedesktop/UPower/devices/DisplayDevice
beardy@GD8200-DB-BL:~$ upower -i
/org/freedesktop/UPower/devices/battery_BAT1
  native-path:  BAT1
  vendor:   SMP 
  model:GD8200 Primary Battery  018762
LiIon   SMP 
  serial:   018762  LiIon
SMP 
  power supply: yes
  updated:  Thu 20 Oct 2016 11:31:54 BST (56 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   fully-charged  
warning-level:   none
energy:  58.7088 Wh
energy-empty:0 Wh
energy-full: 58.7088 Wh
energy-full-design:  56.4516 Wh
energy-rate: 0.0108 W
voltage: 4.967 V
percentage:  100%
capacity:100%
icon-name:  'battery-full-charged-symbolic'
  History (rate):
1476959514  0.011   fully-charged

* End paste *

In this case the culprit is the long line provided as model, rather than 64
characters generated by an unrecognised battery, however, the basic issue is
identical.  The interface either needs to accommodate or truncate the
information
rather than increasing the window dimensions beyond what fits on a
reasonable
screen.

Upstream believe the issue to be fixed in this version. However, the basic
issue 
that the interface can't accommodate long strings without extending off
screen
is still present the versions cited at the beginning of this report.

-- System Information:
Distributor ID: BunsenLabs
Description:BunsenLabs GNU/Linux 8.5 (Hydrogen)
Release:8.5
Codename:   bunsen-hydrogen
Architecture: x86_64

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

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.19-18+deb8u6
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libglib2.0-0  2.42.1-1+b1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libnotify40.7.6-2
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libupower-glib3   0.99.1-3.2
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxfce4ui-1-04.10.0-6
ii  libxfce4util6 4.10.1-2
ii  libxfconf-0-2 4.10.0-3
ii  libxrandr22:1.4.2-1+b1
ii  upower0.99.1-3.2
ii  xfce4-power-manager-data  1.4.4-4~bpo8+1

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   215-17+deb8u5
pn  xfce4-power-manager-plugins  

xfce4-power-manager suggests no packages.

-- no debconf information


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Bug#579235: libgtksourceview2.0-0: Missing debug package

[Michael Biebl]

Version: 2.10.5-3

On Mon, 26 Apr 2010 14:30:31 +0200 Nicolas Joseph
 wrote:
> Package: libgtksourceview2.0-0
> Version: 2.10.0-1
> Severity: wishlist
> Tags: sid
> 
> Hello,
> 
> Can you add the debug package for libgtksourceview2.0-0?
> 
> It's a minor bug, but I have a problem and this will help me.
> 
> Thank's in advance.

We have automatic dbgsym packages now, so this issue is fixed.




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

Bug#841478: GC Warning: Repeated allocation of very large block

[積丹尼 Dan Jacobson]

X-debbugs-Cc: Katsumi Yamaoka 
Package: w3m
Version: 0.5.3-31
File: /usr/bin/w3m

Browse the following:
Title: 您的留言





臺中市政府交通局- 您的留言 
2016/10/21 上午 08:25:25
  

  積丹尼您好：
  
  已收到您的留言，我們將請相關人員了解問題及狀況後，再回覆您的問題，謝謝。 

  
  


  姓　名
  積丹尼


  電　話
  0963114343
  電子郵件信箱
  jida...@jidanni.org




  主　旨
  路牌竟然出現簡體字


  內　容
  路牌竟然出現簡體（豐）字！位於台中市豐原區豐勢路二段萬年路口：https://goo.gl/maps/Q2p4Ui3eCH22另參 http://tube.chinatimes.com/20150615003003-261402


  填寫時間
  2016/10/21 上午 08:25:25



  處理狀態
  處理中

  
  
  臺中市政府交通局　│電話：04-22289111 
此為系統發信，請勿直接回覆 
 


(I have changed  to make it valid HTML.)
1. See lots of GC Warning: Repeated allocation of very large block
2. q and ^C don't quit right away.

Bug#814396: twinkle: Unable to add myself to Uploaders

[Peter Colberg]

Hi Rolf,

On Fri, Oct 21, 2016 at 12:08:02AM +0200, Rolf Leggewie wrote:
> It seems like I was added a while ago.  But I only noticed it today.  I
> pushed a branch to git with a changeset to add myself as Uploader.  Feel
> free to commit or reject ;-)
> 
> I believe you've become DM yourself by now, so the urgency of requesting
> my DM flag for twinkle is lessened somewhat.

There is a new upstream release of twinkle; if you like, I think
it would be a good opportunity for you to package the new version,
besides adding yourself to Uploaders.

Are you familiar with gbp? Note the config file debian/gbp.conf that
causes `gbp import-orig` to automatically commit a pristine-tar delta.

For the changelog, I prefer to update it separately right before the
upload, which you can do using `gbp commit --release --commit`.

On a nitpicky note, please run `wrap-and-sort` when changing
debian/control, e.g., after adding yourself to Uploaders.

Let me know and I can review and upload. Welcome aboard!

Regards,
Peter

Bug#841477: 389-ds-base: 389 directory server fails to start TLS/SSL

[Michal Kaspar]

Package: 389-ds-base
Version: 1.3.5.13-1
Severity: important

Dear Maintainer,
After recent updates the 389 directory server fails to start SSL on port
636. The rest of server starts fine but in the logs, there is an error
message:
SSL alert: Security Initialization: Unable to create PinObj (Netscape Portable 
Runtime error -5977 - Failure to load dynamic library.)
ERROR: SSL Initialization Failed.  Disabling SSL.
When I ran strace on ns-slapd, I've noticed it's missing file
/etc/dirsrv/slapd-suffix/libnssckbi.so. After linking
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so from package libnss3 the
error message changed to:
SSL alert: Security Initialization: Unable to create PinObj (Netscape Portable 
Runtime error -8015 - The certificate/key database is in an old, unsupported 
format or failed to open.)
I've checked the cert db with certutil -L -d /etc/dirsrv/slapd-suffix
and it seems OK. The certificate is valid until the start of the
november so I have no idea now, where the problem might be. Is it some
libraries incompatibility or are there some other steps I can do to
debug the issue.
I'm running 389 server as a part of freeipa installation, so I'm now not
able to issue different certificate to test, becouse the CA can't start
without LDAP server running.

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

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

Versions of packages 389-ds-base depends on:
ii  389-ds-base-libs 1.3.5.13-1
ii  acl  2.2.52-3
ii  adduser  3.115
ii  debconf [debconf-2.0]1.5.59
ii  init-system-helpers  1.45
ii  ldap-utils   2.4.42+dfsg-2+b3
ii  libc62.24-5
ii  libdb5.3 5.3.28-12
ii  libgcc1  1:6.2.0-7
ii  libicu57 57.1-4
ii  libldap-2.4-22.4.42+dfsg-2+b3
ii  libmozilla-ldap-perl 1.5.3-2+b3
ii  libnetaddr-ip-perl   4.079+dfsg-1+b1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26-2
ii  libpam0g 1.1.8-3.3
ii  libpci3  1:3.3.1-1.1
ii  libperl4-corelibs-perl   0.003-2
ii  libsasl2-2   2.1.26.dfsg1-15
ii  libsasl2-modules-gssapi-mit  2.1.26.dfsg1-15
ii  libsensors4  1:3.4.0-3
ii  libsnmp305.7.3+dfsg-1.5+b1
ii  libsocket-getaddrinfo-perl   0.22-3
ii  libssl1.0.2  1.0.2j-1
ii  libstdc++6   6.2.0-7
ii  libsvrcore0  1:4.1.2+dfsg1-2
ii  libsystemd0  231-9
ii  libwrap0 7.6.q-25
ii  perl 5.24.1~rc3-3
ii  python   2.7.11-2
ii  systemd  231-9

389-ds-base recommends no packages.

389-ds-base suggests no packages.

-- Configuration Files:
/etc/default/dirsrv changed:
KRB5_KTNAME=/etc/dirsrv/ds.keytab
KRB5CCNAME=/tmp/krb5cc_114

/etc/default/dirsrv.systemd changed:
[Service]
TimeoutStartSec=10m
NotifyAccess=all
LimitNOFILE=8192


-- no debconf information

Bug#841476: override: libgnomecanvas2-0:oldlibs/optional, libgnomecanvas2-common:oldlibs/optional

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

Please adjust the section of libgnomecanvas2-0 and
libgnomecanvas2-common and move them to oldlibs.

The library is obsolete nowadays and its use no longer encouraged.

Bug#840153: Should have various tutorial manpages

[Ian Jackson]

Ian Jackson writes ("Re: Bug#840153: Should have various tutorial manpages"):
> I don't mind the additional paragraph break.

Ie, like this.  The output of pod2man | man -l is the same.

Ian.

>From de9555e90291fcfa3d374bc02d1a5fff8a3f7617 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Wed, 19 Oct 2016 19:59:34 -0700
Subject: [PATCH] dgit-maint-merge(7): spacing

Signed-off-by: Ian Jackson 
---
 dgit-maint-merge.7.pod | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dgit-maint-merge.7.pod b/dgit-maint-merge.7.pod
index 2900492..f785af7 100644
--- a/dgit-maint-merge.7.pod
+++ b/dgit-maint-merge.7.pod
@@ -314,6 +314,7 @@ Before merging the new 1.2.3+dfsg tag to master, you should 
first
 determine whether it would be legally dangerous for the non-free
 material to be publicly accessible in the git history on
 B.
+
 If it would be dangerous, there is a big problem;
 in this case please consult your archive administrators
 (for Debian this is the dgit administrator dgit-ow...@debian.org
-- 
2.9.3



-- 
Ian Jackson    These opinions are my own.

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

Bug#841475: False positive outdated-autotools-helper-file with dh compat 10

[Michael Biebl]

Package: lintian
Version: 2.5.48
Severity: normal

Hi,

I use dh compat 10 with a package that has very old config.{sub,guess}
files:

W: libgnomecanvas source: outdated-autotools-helper-file config.guess
2009-11-20
W: libgnomecanvas source: outdated-autotools-helper-file config.sub
2009-11-20

Since dh with compat level 10 run autoreconf and the autotools addon by
default, I think the lintian warning is a false positive.

I've dropped explicit Build-Depends on dh-autoreconf or autotools-dev,
since those are pulled in by debhelper (>= 10) now.

Regards,
Michael


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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 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 lintian depends on:
ii  binutils  2.27-9
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.28-4
ii  gettext   0.19.8.1-1
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.29+b6
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b1
ii  libdigest-sha-perl5.96-1+b1
ii  libdpkg-perl  1.18.10
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b1
ii  libparse-debianchangelog-perl 1.2.0-11
ii  libperl5.24 [libdigest-sha-perl]  5.24.1~rc3-3
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.63-1+b1
ii  man-db2.7.5-1
ii  patchutils0.3.4-1
ii  perl  5.24.1~rc3-3
ii  t1utils   1.39-2
ii  xz-utils  5.2.2-1.2

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

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

-- no debconf information

Bug#840153: Should have various tutorial manpages

[Ian Jackson]

Sean Whitton writes ("Bug#840153: Should have various tutorial manpages"):
> control: tag -1 -patch
> ^ since no patch for the other manpages listed in the first message

Thanks, yes.

> On Thu, Oct 20, 2016 at 08:38:48PM +0100, Ian Jackson wrote:
> > As for your final patch "dgit-maint-merge(7): spacing".  Is there a
> > reason in a .pod file not to use semantic whitespace ?
> > perlpod(1) suggests not AFAICT.
> 
> My commit message was poor.  I should have written "split into two
> paragraphs".  Does that make sense of the change?

Oh.  Yes, well, somewhat.

> I don't understand how a paragraph split can have anything to do with
> semantic whitespace -- unless there is already a paragraph break without
> the blank line, and the commit has no effect on the manpage output?

All I saw in your commit message was the rewrapping.  But now I look
at it again there is an additional blank line too.

The rewrapping replaces the semantic newlines (which I used when I
rewrote that paragraph) with what looks like the result of an
automatic wordwrap algorithm.

I don't mind the additional paragraph break.  I do rather mind the
rewrapping (which is just pointless noise in the diff), but I will
tolerate it if you convince me you have understood what I mean by
"semantic newlines" and explain that you are doing this deliberately
:-).  After all I don't want to have a stupid argument about
whitespace.

Ian.

-- 
Ian Jackson    These opinions are my own.

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

Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory"

[Ian Jackson]

Anders Kaseorg writes ("Re: Bug#841414: git "fatal: Out of memory? mmap failed: 
Cannot allocate memory""):
> Git really is running out of memory.  When I try this locally (using 
> file:// to force Git to go through the same git-upload-pack dance that it 
> does over a smart transport, and using ulimit -v as a poor but probably 
> sufficient approximation of a RAM-limited server), it fails with 920 MB of 
> virtual memory and succeeds with 940 MB:

Thanks for the investigation.  You have provided useful facts.

So I think in terms of the questions I asked, you are saying:

 * This is not a very unusual level of memory usage[1] so the server
   should be provisioned with more swap, at the very least, and
   probably more RAM.

 * Using git-gc more often might be beneficial.

Many (most?) of the dgit-repos will read much more than they are
written.  So that seens to emphasise the second point.  I'm still not
entirely sure whether I should just use the default options to git-gc
but that's probably a good starting point.

Does that seem right ?

I have an outstanding question: do I need to lock against concurrent
updates by other programs ?  That is, can I run git-gc and (say)
git-receive-pack at the same time, safely ?

Also, I still wonder if better documentation in git might help.

Thanks,
Ian.

[1] Large repos are to be expected occasionally.

-- 
Ian Jackson    These opinions are my own.

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

Bug#840153: Should have various tutorial manpages

[Sean Whitton]

control: tag -1 -patch
^ since no patch for the other manpages listed in the first message

Hello,

On Thu, Oct 20, 2016 at 08:38:48PM +0100, Ian Jackson wrote:
> As for your final patch "dgit-maint-merge(7): spacing".  Is there a
> reason in a .pod file not to use semantic whitespace ?
> perlpod(1) suggests not AFAICT.

My commit message was poor.  I should have written "split into two
paragraphs".  Does that make sense of the change?

I don't understand how a paragraph split can have anything to do with
semantic whitespace -- unless there is already a paragraph break without
the blank line, and the commit has no effect on the manpage output?

-- 
Sean Whitton

Bug#798111: Illegal instruction after compiling some code

[Daniel Stender]

Another case might be AFL:
https://bugs.debian.org/841474 afl: FTBFS on armhf (illegal instruction on 
test-instr.c)

DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/

Bug#841474: afl: FTBFS on armhf (illegal instruction on test-instr.c)

[Daniel Stender]

Package: afl
Version: 2.34b-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

>From 2.30b-1 onwards (the first package which was tried to build against 
>llvm-toolchain
> 3.7 on this arch), AFL build breaks with "illegal instruction" trying to 
> compile
test-instr.c with afl-clang-fast, now trying to build with clang 3.9 [1]:


[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; AFL_QUIET=1 AFL_PATH=. 
AFL_CC=clang-3.9
../afl-clang-fast -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign
-DAFL_PATH=\"/usr/lib/afl\" -DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.34b\"  
../test-instr.c -o
test-instr -fPIE -pie -Wl,-z,relro -Wl,-z,now
Illegal instruction


Julien Puydt has reported something similar for the flint package:
https://bugs.debian.org/798111 (Illegal instruction after compiling some code)

Strangely, the package builds fine in the porterbox and with a 
qemu-bootstrapped local
sbuild [2].

Thanks for any input (if this could be worked around in the AFL package),
I'll try to seek what's causing this in the build toolchain.
DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=afl=armhf=2.34b-2=1474836143

[2] 
http://www.danielstender.com/buildlogs/afl_2.34b-2_armhf-2016-10-20T23:40:16Z.build

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

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

Versions of packages afl depends on:
ii  build-essential  12.2
ii  libc62.24-3

Versions of packages afl recommends:
pn  afl-clang  
ii  afl-doc2.34b-2

Versions of packages afl suggests:
ii  gnuplot  5.0.4+dfsg1-3

-- no debconf information

Bug#841383: dgit: splitbrain push fails if package was previously pushed without splitbrain

[Sean Whitton]

Hello Ian,

On Thu, Oct 20, 2016 at 01:56:22PM +0100, Ian Jackson wrote:
> Control: severity -1 important
> 
> Sean Whitton writes ("Bug#841383: dgit: splitbrain push fails if package was 
> previously pushed without splitbrain"):
> > hephaestus ~/src/classic-theme-restorer % dgit --quilt=gbp push
> > canonical suite name for unstable is sid
> 
> Thanks.  I have reproduced this.  Looking at the code, and at my own
> attempts, I don't understand how this passes its tests.
> 
> I will get back to you.

Thanks for uploading a fix for this!

> I flailed about a bit trying to get gbp-buildpackage to DTRT to make
> me the .orig.  It complained about the lack of a 1.5.8 tag.  Looking
> through the history I guessed that the right answer was
>   git-tag 1.5.8 9d6ae94c885280ebf269ca9e4eb0a162c47037b2

It looks like I failed to push the tags -- sorry about that.

However, as I mentioned in the original message, the tarball was
available on the pristine-tar branch (I don't normally push that branch,
but I did in this case, for the sake of this bug).

--
Sean Whitton

Bug#841414: dgit clone fails with "Cannot allocate memory"

[Sean Whitton]

There are a lot of settings you can tweak to make git's repacking do
better on low memory hosts.  On my 256MB VM:

athena /home/git % cat .gitconfig
[pack]
windowMemory = 10m
packSizeLimit = 25m
threads = 1

It might be that you just need to tweak these settings.

-- 
Sean Whitton

Bug#840634: flashplugin-nonfree: Failed to download fp.11.2.202.637.sha512.amd64.pgp.asc

[Mika]

Debian testing is also affected. I just installed a new system on my
friends laptop and got the same error.

Mika

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Konstantin Demin]

2016-10-21 1:49 GMT+03:00 Ben Hutchings :
> It's a bug when a compiler fails to compile valid code.
>
> Ben.
>
> --
> Ben Hutchings
> Never put off till tomorrow what you can avoid all together.

Dear Ben, there are no actual bug in compiler, just a caveat to work with it.

Some time ago i had experience to build fully hardened nginx build,
and I was forced to build shared libraries with -fPIC but not -fPIE
due to linker errors.

Solution was to separate build to executable only and shared-libraries only;
this is semi-true: executable is successfully linked with -fPIC flag,
but it's not used in packaging because of executable already built with -fPIE.

This bug report is just another round of game with compiler/linker flags.
In my turn, I would rather define protective flags to provide backward
and forward compatibility.

-- 
SY,
Konstantin Demin
--- a/debian/rules.real
+++ b/debian/rules.real
@@ -168,6 +168,7 @@ else
 	echo 'override CROSS_COMPILE = $$(DEB_HOST_GNU_TYPE)-' >> '$(DIR)/.kernelvariables'
 	echo 'endif' >> '$(DIR)/.kernelvariables'
 endif
+	echo 'KCFLAGS += -fno-PIC -fno-PIE' >> '$(DIR)/.kernelvariables'
 ifdef CFLAGS_KERNEL
 	echo 'CFLAGS_KERNEL += $(CFLAGS_KERNEL)' >> '$(DIR)/.kernelvariables'
 	echo 'CFLAGS_MODULE += $(CFLAGS_KERNEL)' >> '$(DIR)/.kernelvariables'
 endif

Bug#841472: ITP: cowpatty -- Offline dictionary attack tool against WPA/WPA2

[Marcio de Souza Oliveira]

Package: wnpp
Severity: wishlist
Owner: Marcio de Souza Oliveira 

* Package name: cowpatty
  Version : 4.6
  Upstream Author : Joshua Wright 
* URL : http://www.willhackforsushi.com/?page_id=50
* License : GPL-2
  Programming Lang: C
  Description : Offline dictionary attack tool against WPA/WPA2

Implementation of an offline dictionary attack against WPA/WPA2 networks
using PSK-based authentication (e.g. WPA-Personal). Cowpatty can implement
an accelerated attack if a precomputed PMK file is available for the SSID
that is being assessed.

Bug#841473: linux-image-4.7.0-1-amd64: Nouveau driver stops working freezing system

[André Isidoro Fernandes Esteves]

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

Dear Maintainer,

   * What led up to the situation?

System video froze without any notice, all i could savage from the log files:

Oct 21 00:29:58 elektrum kernel: [98341.161363] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
Oct 21 00:29:58 elektrum kernel: [98341.161369] nouveau :01:00.0: fifo: gr 
engine fault on channel 2, recovering...

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

Video was broken, not even changing video modes (going to the console) worked
This has been happening at random intervals.

Tanking you for your time and attention,

Andre Esteves


-- Package-specific info:
** Version:
Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.6-1 (2016-10-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/elektrum--vg-root ro 
quiet

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[6.122988] usb 3-9: New USB device found, idVendor=05e3, idProduct=0608
[6.122989] usb 3-9: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[6.122989] usb 3-9: Product: USB2.0 Hub
[6.123628] hub 3-9:1.0: USB hub found
[6.123900] hub 3-9:1.0: 4 ports detected
[6.233897] usb 4-5: new SuperSpeed USB device number 2 using xhci_hcd
[6.250568] usb 4-5: New USB device found, idVendor=067b, idProduct=2773
[6.250569] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[6.250569] usb 4-5: Product: USB3.0 DUAL DOCK 
[6.250570] usb 4-5: Manufacturer: Prolific
[6.250570] usb 4-5: SerialNumber: PROLIFICM3
[6.251086] usb 4-5: Set SEL for device-initiated U1 failed.
[6.251168] usb 4-5: Set SEL for device-initiated U2 failed.
[6.264676] usb-storage 4-5:1.0: USB Mass Storage device detected
[6.264714] scsi host10: usb-storage 4-5:1.0
[6.264754] usbcore: registered new interface driver usb-storage
[6.265491] usbcore: registered new interface driver uas
[6.269997] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[6.361901] usb 3-13: new low-speed USB device number 15 using xhci_hcd
[6.497420] nouveau :01:00.0: fb1: nouveaufb frame buffer device
[6.497423] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on 
minor 1
[6.558895] usb 3-13: New USB device found, idVendor=045e, idProduct=0780
[6.558897] usb 3-13: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[6.558898] usb 3-13: Product: Comfort Curve Keyboard 3000
[6.558899] usb 3-13: Manufacturer: Microsoft
[6.729907] usb 3-14: new low-speed USB device number 16 using xhci_hcd
[6.896263] usb 3-14: New USB device found, idVendor=1bcf, idProduct=0005
[6.896265] usb 3-14: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
[6.896266] usb 3-14: Product: USB Optical Mouse
[6.913253] hidraw: raw HID events driver (C) Jiri Kosina
[6.925224] media: Linux media interface: v0.10
[6.926292] Bluetooth: Core ver 2.21
[6.926306] NET: Registered protocol family 31
[6.926307] Bluetooth: HCI device and connection manager initialized
[6.926309] Bluetooth: HCI socket layer initialized
[6.926311] Bluetooth: L2CAP socket layer initialized
[6.926316] Bluetooth: SCO socket layer initialized
[6.929517] usblp 3-5.1.1:1.0: usblp0: USB Bidirectional printer dev 8 if 0 
alt 0 proto 2 vid 0x04F9 pid 0x0027
[6.929540] usbcore: registered new interface driver usblp
[6.929665] Linux video capture interface: v2.00
[6.930036] usbcore: registered new interface driver btusb
[6.939646] usbcore: registered new interface driver usbhid
[6.939647] usbhid: USB HID core driver
[6.940890] input: Ver 1.0 USB To RS232 Interface (V1.0) BaudRate 2400bps as 
/devices/pci:00/:00:14.0/usb3/3-5/3-5.1/3-5.1.2/3-5.1.2:1.0/0003:0F03:0001.0001/input/input24
[6.965120] usb 3-5.3: set resolution quirk: cval->res = 384
[6.965375] usbcore: registered new interface driver snd-usb-audio
[6.965376] uvcvideo: Found UVC 1.00 device HD Webcam C525 (046d:0826)
[6.977518] uvcvideo 3-5.3:1.2: Entity type for entity Extension 5 was not 
initialized!
[6.977520] uvcvideo 3-5.3:1.2: Entity type for entity Camera 1 was not 
initialized!
[6.977522] uvcvideo 3-5.3:1.2: Entity type for entity Extension 6 was not 
initialized!
[6.977523] uvcvideo 3-5.3:1.2: Entity type for entity Extension 7 was not 
initialized!
[6.977524] uvcvideo 3-5.3:1.2: Entity type for entity Extension 8 was not 
initialized!
[6.977638] input: HD Webcam C525 as 
/devices/pci:00/:00:14.0/usb3/3-5/3-5.3/3-5.3:1.2/input/input25
[6.994083] hid-generic 0003:0F03:0001.0001: input,hidraw0: USB HID v1.00 
Gamepad [Ver 1.0 USB To RS232 Interface (V1.0) BaudRate 2400bps] on 
usb-:00:14.0-5.1.2/input0
[6.994131] usbcore: 

Bug#840296: [udd] upload_history table has stopped updating

[Eriberto Mota]

Control: severity 840296 important

> From: Chris Lamb 
> (#debian-qa)
>
> 11:04 < mapreri> lucas: upload_history seems to have stopped a month ago :(   
> > >
> https://paste.debian.net/hidden/8cef723c/
>
> I use this table a fair amount in various scripts, so would love to get it
> updated again… :)


Me too. Is there an estimate to fix this issue? It is breaking several
UDD reports.

Thanks a lot in advance.

Regards,

Eriberto

Bug#839109: [pkg-go] Bug#839109: Bug#839109: dh-golang: Possibly wrong XS- prefix for Go-Import-Path field

[Michael Hudson-Doyle]

On 21 October 2016 at 12:06, Martín Ferrari  wrote:

> Hi,
>
> On 29/09/16 03:44, Guillem Jover wrote:
>
> > It seems that many Go packages include an XS-Go-Import-Path field in
> > their control file, which AFAICT is only (?) used at build time from
> > inside the same source package.
>
> AFAIK, this is true.
>
> > The XS- prefix tells dpkg-source to propagate that field to the source
> > package (.dsc) and that in turn gets propagated to the Sources indices.
> > With the additional bloat. If this field is never used by querying the
> > Sources indices, I'd appreciate if you could switch to simply use the
> > X- prefix instead.
>
> I can imagine this at some point being used for finding packages based
> on their import path. But not sure if it is reason enough to keep the
> header..
>
> Maybe somebody else has a better argument for this?
>

I think this was the plan, that you'd be able to find the (Debian) package
provide a given (Go) by using grep-dctrl or whatever. The fact that it's
not used universally reduces its value, but the fix for that is different
to what you suggest :-)

Cheers,
mwh

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[S. R. Wright]

I agree.  When the version changes from 6.2.0-6 to 6.2.0-7,  only bug 
fixes should be included,  not changes in functionality.  In this case 
setting enable-default-pie essentially broke backwards compatibility.  
Kernel code that built in -6 failed to build in -7.  That, I agree,  
should be considered a bug,  and the change should be rolled back.


-- sRw

On 10/20/2016 05:49 PM, Ben Hutchings wrote:

On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote:

It's not a GCC bug but kind of new feature.

It's a bug when a compiler fails to compile valid code.

Ben.


Take a look at this changelog entry:
  gcc-6 (6.2.0-7) unstable; urgency=medium

[ Matthias Klose ]
* Configure with --enable-default-pie and pass -z now when pie is enabled;
  on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.
  Closes: #835148.

Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in
beginning of CFLAGS to build kernel successfully.

I'm currently looking for correct way to do this trick.

Bug#841467: Updating the pangomm Uploaders list

[Michael Biebl]

Control: tags -1 + pending

Am 20.10.2016 um 23:57 schrieb Mattia Rizzolo:
> Source: pangomm
> Version: 2.40.1-3
> Severity: minor
> User: m...@qa.debian.org
> Usertags: mia-teammaint
> 
> Michael Casadevall  has retired, so can't work on
> the pangomm package anymore (at least with this address).
> 
> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.
> 
> (If the person is listed as Maintainer, what we are asking is to please
> step in as a new maintainer.)

Thanks for the notification. I've updated the Uploaders field
accordingly so it will be part of the next upload.

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#839109: [pkg-go] Bug#839109: dh-golang: Possibly wrong XS- prefix for Go-Import-Path field

[Martín Ferrari]

Hi,

On 29/09/16 03:44, Guillem Jover wrote:

> It seems that many Go packages include an XS-Go-Import-Path field in
> their control file, which AFAICT is only (?) used at build time from
> inside the same source package.

AFAIK, this is true.

> The XS- prefix tells dpkg-source to propagate that field to the source
> package (.dsc) and that in turn gets propagated to the Sources indices.
> With the additional bloat. If this field is never used by querying the
> Sources indices, I'd appreciate if you could switch to simply use the
> X- prefix instead.

I can imagine this at some point being used for finding packages based
on their import path. But not sure if it is reason enough to keep the
header..

Maybe somebody else has a better argument for this?

-- 
Martín Ferrari (Tincho)

Bug#841471: fim: FTBFS on several architectures: default_font_byte_array.h:349:1: error: narrowing conversion of '905969664' from 'int' to 'unsigned char' inside { } [-Wnarrowing]

[Emilio Pozuelo Monfort]

Package: fim
Version: 0.5~rc2-1
Severity: serious

Your package failed to build on several architectures with this errors:

g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libpng16 -I/usr/include -I/usr/include/SDL -D_GNU_SOURCE=1 
-D_REENTRANT -c -o FontServer.o FontServer.cpp
In file included from FontServer.cpp:184:0:
default_font_byte_array.h: In static member function 'static fim::fs_font* 
fim::FontServer::fs_consolefont(const fim_char_t**)':
default_font_byte_array.h:349:1: error: narrowing conversion of '905969664' 
from 'int' to 'unsigned char' inside { } [-Wnarrowing]
 };
 ^
default_font_byte_array.h:349:1: error: narrowing conversion of '67108864' from 
'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '33554432' from 
'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '268435456' 
from 'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '2852126720u' 
from 'unsigned int' to 'unsigned char' inside { } [-Wnarrowing]
[...]

This seems to be happening on big-endian architectures, so may be an
endianness issue.

Full logs at:

https://buildd.debian.org/status/package.php?p=fim

Emilio

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

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

Bug#841469: libopendbx: build-depends on firebird2.5-dev, which is no longer available

[Emilio Pozuelo Monfort]

Source: libopendbx
Version: 1.4.6-10
Severity: serious

Your package build-depends on firebird2.5-dev, but that is no longer
available as firebird is at version 3.0. Thus your package is currently
unbuildable.

Emilio

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

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

Bug#841470: witty: build-depends on firebird2.5-dev, which is no longer available

[Emilio Pozuelo Monfort]

Source: witty
Version: 3.3.5+dfsg-1.1
Severity: serious

Your package build-depends on firebird2.5-dev, but that is no longer
available as firebird is at version 3.0. Thus your package is currently
unbuildable.

Emilio

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

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

Bug#841423: LVM: raid1 kernel module not loaded

[Ben Hutchings]

On Fri, 2016-10-21 at 00:17 +0200, Cesare Leonardi wrote:
> Here i've talked about raid1 because it is what i've tested myself, but 
> since LVM can handle raid0/1/4/5/6/10, perhaps the same arguments apply 
> also to the other raid types.
> 
> For example i've noticed that the initramfs' hook from mdadm takes care 
> of loading all the raid modules:
> ---
> for module in linear multipath raid0 raid1 raid456 raid5 raid6 raid10; do
>   force_load $module
> done

It should really use manual_add_modules to ensure the modules are
included in the initramfs.  It should not force them to be loaded.

> ---
> Maybe should also lvm2's hook load those modules?

Either dmsetup or lvm2 (I'm not quite sure what the division of
responsibilities is there) should ensure they are included.

Ben.

> And in fact if both lvm2 and mdadm are installed, what i'm reporting 
> here doesn't happen: raid modules are loaded by mdadm's hook.
> 
> Moreover, if i understand correctly, the grub2 package uploaded to 
> unstable 4 days ago (2.02-beta3) is the first that supports booting from 
> an LVM raid1: it would be wonderful if that setup could be supported out 
> of the box in Debian.
> 
> 
-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.



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

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Ben Hutchings]

On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote:
> It's not a GCC bug but kind of new feature.

It's a bug when a compiler fails to compile valid code.

Ben.

> Take a look at this changelog entry:
>  gcc-6 (6.2.0-7) unstable; urgency=medium
> 
>    [ Matthias Klose ]
>    * Configure with --enable-default-pie and pass -z now when pie is enabled;
>  on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.
>  Closes: #835148.
> 
> Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in
> beginning of CFLAGS to build kernel successfully.
> 
> I'm currently looking for correct way to do this trick.
> 
> 
-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.



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

Bug#841098: not fixed in rygel 0.32.1-1

[Santiago Vila]

On Thu, Oct 20, 2016 at 10:14:11PM +0200, Andreas Henriksson wrote:

> The above mentioned upload was done as a source-only upload.
> It built successfully not only in my local environment but also on *all*
> architectures (and thus on atleast one buildd for each architecture).
> 
> This is obviously a problem in your environment.

No, I think it's not, because it also happened in the official
autobuilders several times. For example:

https://buildd.debian.org/status/fetch.php?pkg=rygel=ppc64el=0.32.0-2=1475601506

Quote:

PASS: rygel-searchable-container-test
PASS: rygel-object-creator-test
PASS: rygel-database-test
../build-aux/test-driver: line 107: 17241 Aborted "$@" > 
$log_file 2>&1
FAIL: rygel-media-engine-test
PASS: rygel-playbin-renderer-test
PASS: rygel-environment-test

It's more like a bug which happens randomly (with low probability) and
it's still unfixed, but definitely not a problem in my environment.

Thanks.

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Konstantin Demin]

It's not a GCC bug but kind of new feature.

Take a look at this changelog entry:
 gcc-6 (6.2.0-7) unstable; urgency=medium

   [ Matthias Klose ]
   * Configure with --enable-default-pie and pass -z now when pie is enabled;
 on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.
 Closes: #835148.

Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in
beginning of CFLAGS to build kernel successfully.

I'm currently looking for correct way to do this trick.

-- 
SY,
Konstantin Demin

Bug#840574: Please backport libgo fixes for sparc64

[James Clarke]

Hi Matthias,
As promised yesterday on #debian-toolchain, here is a debdiff to fix the
libgo debug/elf testsuite failure by providing a uuencoded copy of
go-relocation-test-gcc620-sparc64.obj.

Regards,
James
diff -u gcc-6-6.2.0/debian/changelog gcc-6-6.2.0/debian/changelog
--- gcc-6-6.2.0/debian/changelog
+++ gcc-6-6.2.0/debian/changelog
@@ -1,3 +1,10 @@
+gcc-6 (6.2.0-9+sparc64) UNRELEASED; urgency=medium
+
+  * Include go-relocation-test-gcc620-sparc64.obj.uue to fix libgo's
+debug/elf TestDWARFRelocations test case.
+
+ -- James Clarke   Thu, 20 Oct 2016 20:32:51 +0100
+
 gcc-6 (6.2.0-9) unstable; urgency=medium
 
   * Regenerate the control file.
diff -u gcc-6-6.2.0/debian/patches/libgo-elf-relocations-sparc64.diff 
gcc-6-6.2.0/debian/patches/libgo-elf-relocations-sparc64.diff
--- gcc-6-6.2.0/debian/patches/libgo-elf-relocations-sparc64.diff
+++ gcc-6-6.2.0/debian/patches/libgo-elf-relocations-sparc64.diff
@@ -1,4 +1,7 @@
 # DP: Backport r241051 from trunk
+# DP: src/libgo/go/debug/elf/testdata/go-relocation-test-gcc620-sparc64.obj is
+# DP: encoded in debian/go-relocation-test-gcc620-sparc64.obj.uue and is
+# DP: decoded at patch time.
 
 debug/elf: add sparc64 relocations
 
@@ -104,4 +106,0 @@
-Index: b/src/libgo/go/debug/elf/testdata/go-relocation-test-gcc620-sparc64.obj
-===
-Cannot display: file marked as a binary type.
-svn:mime-type = application/octet-stream
diff -u gcc-6-6.2.0/debian/rules.patch gcc-6-6.2.0/debian/rules.patch
--- gcc-6-6.2.0/debian/rules.patch
+++ gcc-6-6.2.0/debian/rules.patch
@@ -392,6 +392,10 @@
  $(patchdir)/svn-updates.diff > src/LAST_UPDATED
 endif
 
+ifneq (,$(filter libgo-elf-relocations-sparc64, $(debian_patches)))
+   uudecode debian/go-relocation-test-gcc620-sparc64.obj.uue
+endif
+
: # only needed when we have changes, and currently fails with autogen 
5.18
: #cd $(srcdir)/fixincludes && ./genfixes
 
@@ -409,6 +413,11 @@
mv pxxx $@
 
 unpatch:
+ifneq (,$(filter libgo-elf-relocations-sparc64, $(debian_patches)))
+   # uudecoded in $(patch_stamp) rule
+   rm -f 
$(srcdir)/libgo/go/debug/elf/testdata/go-relocation-test-gcc620-sparc64.obj
+endif
+
QUILT_PATCHES=$(patchdir) \
  quilt --quiltrc /dev/null pop -a -R || test $$? = 2
rm -rf .pc
only in patch2:
unchanged:
--- gcc-6-6.2.0.orig/debian/go-relocation-test-gcc620-sparc64.obj.uue
+++ gcc-6-6.2.0/debian/go-relocation-test-gcc620-sparc64.obj.uue
@@ -0,0 +1,136 @@
+begin 644 src/libgo/go/debug/elf/testdata/go-relocation-test-gcc620-sparc64.obj
+M?T5,1@("`0`!`"L!
+M`!(``@!```!``!4`$IWCOU""$``8\G>HA\(GJ'\#D!!@`$``
+M```!`0```('/X`@!`+"!W;W)L9`-"``0`
+M"`$`#```+``"``+8
+M.`,(!P`#`0@``P('``,$!P`#`08``P(%``0$
+M!6EN=``#"`4``@`#@P```"``.$:0,(!P`%"`8(
+ME0,!!@`'E0@`V`3Q```"'@D`!/(```!B``D`
+M!/<```"/"`D`!/@```"/$`D`!/D```"/&`D`!/H```"/(`D`
+M!/L```"/*`D`!/P```"/,`D`!/T```"/.`D`!/X```"/
+M0`H`!`$`CT@*``0!`0```(]0"@`$`0(```"/6`H`
+M!`$$```"5F`*``0!!@```EQH"@`$`0@```!B<`H`!`$,
+M8G0*``0!#@```'!X"@`$`1(```!&@`H`!`$35((*
+M``0!%F*#"@`$`1@```)RB`H`!`$A>Y`*``0!*0``
+M`(V8"@`$`2H```"-H`H`!`$KC:@*``0!+(VP"@``
+M```$`2XMN`H`!`$O8L`*``0!,0```GC$``L`!)8(
+M`!@$GE8)``2=```"5@`)``2>```"7`@)``2B
+M8A``!@@```(E!@@```"A#)4```)R#0```(8```8(```"'@P```"5```"
+MB`T```"&$P`.``\`!`$[```"B`\`!`$\```"B`\`!`$]
+M```"B`8(G`<```*Q$``%J@```EP0``6K```"7!``!:P`
+M``)<$``&&@```&(,```"MP```O,1``<```+H$``&```O,2
+M``$$+`&<```#/Q,``00```!B`Y&``1,`
+M`00```,_`Y&(`0`&"(\``1$!)0X3"P,.`1('$!<```(6``,..@L[
+M"TD3```#)``+"SX+`PX```0D``L+/@L#"```!0\`"PL```8/``L+21,```7-?;F5R<@!?24]?F5?=`!S:7IE
+M='EP90!?;V9F7-?97)R;=`!?9FEL96YO`+F,`
+M

Bug#841423: LVM: raid1 kernel module not loaded

[Cesare Leonardi]

Here i've talked about raid1 because it is what i've tested myself, but 
since LVM can handle raid0/1/4/5/6/10, perhaps the same arguments apply 
also to the other raid types.


For example i've noticed that the initramfs' hook from mdadm takes care 
of loading all the raid modules:

---
for module in linear multipath raid0 raid1 raid456 raid5 raid6 raid10; do
force_load $module
done
---
Maybe should also lvm2's hook load those modules?

And in fact if both lvm2 and mdadm are installed, what i'm reporting 
here doesn't happen: raid modules are loaded by mdadm's hook.


Moreover, if i understand correctly, the grub2 package uploaded to 
unstable 4 days ago (2.02-beta3) is the first that supports booting from 
an LVM raid1: it would be wonderful if that setup could be supported out 
of the box in Debian.

Bug#841468: sorl-thumbnail: Python 2 package lists pgmagick while Python 3 doesn't

[Daniele Forsi]

Source: sorl-thumbnail
Severity: minor

Dear Maintainer,

while translating and revising the translations for this package's
descriptions I found that in the Python 3 version "pgmagick" is missing:

python-sorl-thumbnail
 * Pluggable Engine support (PIL, pgmagick, ImageMagick, GraphicsMagick,
   or Wand)

python3-sorl-thumbnail
 * Pluggable Engine support (PIL, ImageMagick, GraphicsMagick, or Wand)

I see that python3-sorl-thumbnail contains a pgmagick_engine.py file so
I think this omission is an error.

thanks,
Daniele

Bug#841438: --enable-default-pie breaks kernel build on amd64

[Ben Hutchings]

On Thu, 20 Oct 2016 19:05:51 +0200 Gianfranco Costamagna 
 wrote:
> control: severity -1 normal
> control: reassign -1 src:linux
> control: affects -1 gcc-6
> 
> Hi Linux Kernel maintainers,
> as you already know, the default PIE flag breaks the kernel build, can I 
> suggest you to apply a similar patch
> to the one that Ubuntu appplied some time ago?
> https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982/comments/39

Many Debian users do not use our packaged kernel, so working around
this in src:linux does not solve the problem.  The default compiler in
Debian *must* be able to compile the upstream Linux kernel.  I will not
accept any patches for this that have not been accepted upstream.

A better approach might be to make -mcmodel=kernel automatically
override the default of -fPIE.

Ben.

> --- a/Makefile
> +++ b/Makefile
> @@ -612,6 +612,12 @@ endif # $(dot-config)
>  # Defaults to vmlinux, but the arch makefile usually adds further targets
>  all: vmlinux
>  
> +# force no-pie for distro compilers that enable pie by default
> +KBUILD_CFLAGS += $(call cc-option, -fno-pie)
> +KBUILD_CFLAGS += $(call cc-option, -no-pie)
> +KBUILD_AFLAGS += $(call cc-option, -fno-pie)
> +KBUILD_CPPFLAGS += $(call cc-option, -fno-pie)
> +
>  # The arch Makefile can set ARCH_{CPP,A,C}FLAGS to override the default
>  # values of the respective KBUILD_* variables
>  ARCH_CPPFLAGS :=
> 
> thanks
> 
> Gianfranco
> 

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all togethe

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

Bug#841265: transition: cfitsio

[Aurelien Jarno]

On 2016-10-20 13:52, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> 
> On 19/10/16 07:47, Aurelien Jarno wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > The cfitsio library changed its ABI in the latest release version.
> > The new version, including the package rename from libcfitsio4 to
> > libcfitsio5 is available in experimental. It has been built successfully
> > on all official architecture and most ports architectures.
> > 
> > The transition involves 37 packages, you can find the list on the
> > transition tracker in the auto-cfitsio entry. I have been able to
> > successfully rebuild all of them on amd64, so I don't expect any
> > issue.
> > 
> > Thanks for considering.
> 
> Please go ahead.

Thanks, I have just uploaded it to sid.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#841459: bgpdump: FTBFS with bash as /bin/sh

[Christoph Biedl]

tags 841459 pending
thanks

Chris Lamb wrote...

> bgpdump fails to build from source in unstable/amd64 when 
> /bin/sh is set to bash. It looks like the autoreconfing is
> generating an invalid ./configure script:

Thanks for the catch. The actual problem is using m4_esyscmd which
does not remove trailing newlines, resulting the trailing dot to
dropped into the next line, better use m4_esyscmd_s. Lesson learned,
upload based on a new upstream version will follow soon.

Regards,

Christoph


signature.asc
Description: Digital signature

Bug#841467: Updating the pangomm Uploaders list

[Mattia Rizzolo]

Source: pangomm
Version: 2.40.1-3
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Michael Casadevall  has retired, so can't work on
the pangomm package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#841466: Updating the codeblocks Uploaders list

[Mattia Rizzolo]

Source: codeblocks
Version: 16.01+dfsg-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Michael Casadevall  has retired, so can't work on
the codeblocks package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#841465: Updating the sip4 Uploaders list

[Mattia Rizzolo]

Source: sip4
Version: 4.18.1+dfsg-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Michael Casadevall  has retired, so can't work on
the sip4 package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#841464: Updating the python-qt4 Uploaders list

[Mattia Rizzolo]

Source: python-qt4
Version: 4.11.4+dfsg-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Michael Casadevall  has retired, so can't work on
the python-qt4 package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#841463: O: nrss -- A ncurses-based RSS reader

[Mattia Rizzolo]

Package: wnpp

The current maintainer of nrss, Michael Casadevall ,
has retired.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: nrss
Binary: nrss
Version: 0.3.9-1
Maintainer: Michael Casadevall 
Build-Depends: debhelper (>= 5), libexpat1-dev, libncursesw5-dev, wget
Architecture: any
Standards-Version: 3.7.3
Format: 1.0
Files:
 24126a84ff9ee6e0651d52d1f8880bc4 632 nrss_0.3.9-1.dsc
 0673d5b18cee1f7229bed45db05f3c3e 27885 nrss_0.3.9.orig.tar.gz
 0f1505eee74328b7735683cf22328f00 1959 nrss_0.3.9-1.diff.gz
Checksums-Sha256:
 471c8c62c8184d6453f45c80ab19f7e76ef24bf223806c4fdb050fa350f5cee0 632 
nrss_0.3.9-1.dsc
 53494d61bbf31a32d880d25df44cbc0f2c437bcdff76bae6b8b443f3f34615aa 1959 
nrss_0.3.9-1.diff.gz
 c6a421b4a5da5037ca157bfd9c1eadd3115e89984d7180f2abc90933af007602 27885 
nrss_0.3.9.orig.tar.gz
Homepage: http://www.codezen.org/nrss/
Directory: pool/main/n/nrss
Priority: source
Section: net

Package: nrss
Binary: nrss
Version: 0.3.9-1
Maintainer: Michael Casadevall 
Build-Depends: debhelper (>= 5), libexpat1-dev, libncursesw5-dev, wget
Architecture: any
Standards-Version: 3.7.3
Format: 1.0
Files:
 24126a84ff9ee6e0651d52d1f8880bc4 632 nrss_0.3.9-1.dsc
 0673d5b18cee1f7229bed45db05f3c3e 27885 nrss_0.3.9.orig.tar.gz
 0f1505eee74328b7735683cf22328f00 1959 nrss_0.3.9-1.diff.gz
Checksums-Sha1:
 c5c1cf24efcb0c5319e95c06869cc0d65056fe49 632 nrss_0.3.9-1.dsc
 a74cd241272fb8b50d6085d0496c218a85999fa3 1959 nrss_0.3.9-1.diff.gz
 8770cf5cc2c02d88055801ff259c33717f90567d 27885 nrss_0.3.9.orig.tar.gz
Checksums-Sha256:
 471c8c62c8184d6453f45c80ab19f7e76ef24bf223806c4fdb050fa350f5cee0 632 
nrss_0.3.9-1.dsc
 53494d61bbf31a32d880d25df44cbc0f2c437bcdff76bae6b8b443f3f34615aa 1959 
nrss_0.3.9-1.diff.gz
 c6a421b4a5da5037ca157bfd9c1eadd3115e89984d7180f2abc90933af007602 27885 
nrss_0.3.9.orig.tar.gz
Homepage: http://www.codezen.org/nrss/
Directory: pool/main/n/nrss
Priority: source
Section: net

Package: nrss
Source: nrss (0.3.9-1)
Version: 0.3.9-1+b1
Installed-Size: 62
Maintainer: Michael Casadevall 
Architecture: amd64
Depends: libc6 (>= 2.2.5), libexpat1 (>= 2.0.1), libncursesw5 (>= 6), libtinfo5 
(>= 6), wget
Description: A ncurses-based RSS reader
Description-md5: 4f2ac91ddced437d80b5da3b2ad98830
Homepage: http://www.codezen.org/nrss/
Tag: interface::commandline, role::program, uitoolkit::ncurses,
 works-with-format::xml:rss
Section: net
Priority: extra
Filename: pool/main/n/nrss/nrss_0.3.9-1+b1_amd64.deb
Size: 22306
MD5sum: 901344193a1139e9cc8509063aedca17
SHA256: d0b34d8538e0a6fe54bedf4d2dce94d27dcfbab2b6570ded7f013e0ef99c05c8

Package: nrss
Source: nrss (0.3.9-1)
Version: 0.3.9-1+b1
Installed-Size: 62
Maintainer: Michael Casadevall 
Architecture: amd64
Depends: libc6 (>= 2.2.5), libexpat1 (>= 2.0.1), libncursesw5 (>= 6), libtinfo5 
(>= 6), wget
Description: A ncurses-based RSS reader
Description-md5: 4f2ac91ddced437d80b5da3b2ad98830
Homepage: http://www.codezen.org/nrss/
Tag: interface::commandline, role::program, uitoolkit::ncurses,
 works-with-format::xml:rss
Section: net
Priority: extra
Filename: pool/main/n/nrss/nrss_0.3.9-1+b1_amd64.deb
Size: 22306
MD5sum: 901344193a1139e9cc8509063aedca17
SHA256: d0b34d8538e0a6fe54bedf4d2dce94d27dcfbab2b6570ded7f013e0ef99c05c8


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#841438: This is agcc bug : upstream kernel irself fails to build with this gcc so reassigne to gcc-6

[Eric Valette]

I never use debian kernel and connaot compile upstream kernel with gcc-6 
now.


--eric

Bug#841420: --enable-default-pie breaks kernel builds

[Bálint Réczey]

Control: tags -1 - patch

2016-10-20 18:48 GMT+02:00 Sven Joachim :
> On 2016-10-20 17:54 +0200, Bálint Réczey wrote:
>
>> Control: reassign -1 linux 4.7.8-1
>> Control: severity -1 serious
>> Control: tags -1 patch
>>
>> Hi David,
>>
>> 2016-10-20 14:02 GMT+02:00 David Weinehall :
>>> Package: gcc-6
>>> Severity: important
>>> Version: 6.2.0-7
>>>
>>> --enable-default-pie (first enabled in gcc-6 6.2.0-7) causes kernel
>>> builds to fail.  If the kernel is configured with the stack protector
>>> enabled it'll fail with a rather unhelpful error message claiming
>>> that the compiler doesn't support -fstack-protector,
>>> but the problem is in fact caused by:
>>>
>>> kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
>>>
>>> (The kernel is built with -mcmodel=kernel)
>>>
>>> I think it's fair to say that the kernel is kind of an important piece
>>> of software and that it's imperative that we don't break kernel builds...
>>
>> The kernel is very important indeed and it did break in our build test.
>> I'm sorry, somehow I missed filing bug for the linux package, just for
>> user-mode-linux.
>> The following patch fixes the FTBFS:
>>
>> --- linux-4.7.8/debian/rules.d/Makefile.inc
>> +++ linux-4.7.8/debian/rules.d/Makefile.inc
>> @@ -5,7 +5,8 @@
>>
>>  SHELL = /bin/sh -e
>>
>> -CC = $(CROSS_COMPILE)gcc
>> +CC = $(CROSS_COMPILE)gcc -no-pie
>> +LD = $(CROSS_COMPILE)ld -no-pie
>>  CXX = $(CROSS_COMPILE)g++
>>  CFLAGS := $(shell dpkg-buildflags --get CFLAGS) -Wall
>>  CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) \
>>
>> Maybe the ld part is obsolete, I have not checked that.
>
> That patch might work for the Debian package, but has anybody contacted
> the upstream kernel developers about that?  At least the 4.8.3 vanilla
> kernel fails in the same way, I haven't tested 4.9-rc1 yet.

Fixing it upstream would certainly be better. I also haven't booted
the built image,
thus please use this patch only as inspiration. :-)

Cheers,
Balint

>
> FWIW, this issue has been discussed in Ubuntu for six months(!), see
> https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982.
>
> Cheers,
>Sven

Bug#841462: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016h

[gregor herrmann]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Another month, another tzdata update.
As usual, I've added a quilt patch for the Olson db, this time 2016h,
to libdatetime-timezone-perl.

Since this release contains changes that are effective in a bit more
than 2 hours from now, this is probably material for -updates before
the next point release, whenever it's convenient for you.

Manually stripped down debdiff attached.

Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYCTumXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGMYEQAJG4jlwjiLXZt+utT6t+rVwZ
PazB4FMTNsytyf/SHu63219jf9Llq5CmciBM5NOg+i4kObEMt+6OkKoCpFAkxY38
d8Jl+qcqQKwT+6XZ3NxRqEfjm/mtIHpOJi9bKRhmGOfxux0MWOixtzKDrE6zll0U
YXWuAplpUw3eMul+Br47Hhd4p+iveCwXC2qElMRL3sXRVgfZaAgRhkC1OBjRrfrT
OMWq84xXnjJQWPXMVwztK/Q6m8SfQqS+/lpyRMDjL0t1/qPcYaif1DTsTnnN9fQp
Km9efgROitLwPX6d3XGMX2+7FRYdyl88wb6rApM6WVMihzbD2sI8QSjJbUXvoQb9
AIO5GpYNvuy+/19ONh/iBESNmswLzmdMWl9EZvv7yhpSxR6BI+xO/xa227FJCGTI
3NsGJF4Z9HkXWK7pifFyECSyfxFJiBrBW026BU/s3SIQ42zr7S0Rkcev3ToBrYWL
deqFoekJUBSSH1qODyB3wSgaGdMZv09TeKXAWhU4DTCOivt4xJ7CDpEjK7Lz5B8S
/QMzhkAFosFi7KpTIBP2koSYumKxAOHveHHy+nmhLrQBmsu0WZJeIvkA4Gj1f4+O
Az9+FX0BWcIGrA7VoTU9FTqJOAYAWhObkV+x10Fgb0T7jAJPICUo530Ap+HlJ0pK
OiBGNIT8s9YRms1mt2N2
=zfUG
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-1.75/debian/changelog libdatetime-timezone-perl-1.75/debian/changelog
--- libdatetime-timezone-perl-1.75/debian/changelog	2016-09-27 23:20:52.0 +0200
+++ libdatetime-timezone-perl-1.75/debian/changelog	2016-10-20 23:40:02.0 +0200
@@ -1,3 +1,12 @@
+libdatetime-timezone-perl (1:1.75-2+2016h) UNRELEASED; urgency=medium
+
+  * Update to Olson database version 2016h.
+Add patch debian/patches/olson-2016h, which updates the timezone *.pm
+files, using upstream's tools/parse_olson script.
+This update contains contemporary changes for Palestine.
+
+ -- gregor herrmann   Thu, 20 Oct 2016 23:40:02 +0200
+
 libdatetime-timezone-perl (1:1.75-2+2016g) jessie; urgency=medium
 
   * Update to Olson database version 2016g.
diff -Nru libdatetime-timezone-perl-1.75/debian/patches/olson-2016h libdatetime-timezone-perl-1.75/debian/patches/olson-2016h
--- libdatetime-timezone-perl-1.75/debian/patches/olson-2016h	1970-01-01 01:00:00.0 +0100
+++ libdatetime-timezone-perl-1.75/debian/patches/olson-2016h	2016-10-20 23:40:02.0 +0200
@@ -0,0 +1,10713 @@
+Description: update to olson db 2016h
+Origin: vendor
+Author: gregor herrmann 
+Last-Update: 2016-10-20
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
 b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from debian/tzdata/africa.  Olson data version 2016g
++# Generated from debian/tzdata/africa.  Olson data version 2016h
+ #
+ # Do not edit this file directly.
+ #
+@@ -39,7 +39,7 @@
+ ],
+ ];
+ 
+-sub olson_version { '2016g' }
++sub olson_version { '2016h' }
+ 
+ sub has_dst_changes { 0 }
+ 
+--- a/lib/DateTime/TimeZone/Asia/Gaza.pm
 b/lib/DateTime/TimeZone/Asia/Gaza.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from debian/tzdata/asia.  Olson data version 2016g
++# Generated from debian/tzdata/asia.  Olson data version 2016h
+ #
+ # Do not edit this file directly.
+ #
+@@ -975,17 +975,17 @@
+ ],
+ [
+ 6359463, #utc_start 2016-03-25 23:00:00 (Fri)
+-63612680400, #  utc_end 2016-10-20 21:00:00 (Thu)
++63613375200, #  utc_end 2016-10-28 22:00:00 (Fri)
+ 63594640800, #  local_start 2016-03-26 02:00:00 (Sat)
+-63612691200, #local_end 2016-10-21 00:00:00 (Fri)
++63613386000, #local_end 2016-10-29 01:00:00 (Sat)
+ 10800,
+ 1,
+ 'EEST',
+ ],
+ [
+-63612680400, #utc_start 2016-10-20 21:00:00 (Thu)
++63613375200, #utc_start 2016-10-28 22:00:00 (Fri)
+ 63626079600, #  utc_end 2017-03-24 23:00:00 (Fri)
+-63612687600, #  local_start 2016-10-20 23:00:00 (Thu)
++63613382400, #  local_start 2016-10-29 00:00:00 (Sat)
+ 63626086800, #local_end 2017-03-25 01:00:00 (Sat)
+ 7200,
+ 0,
+@@ -993,17 +993,17 @@
+ ],
+ [
+ 63626079600, #utc_start 2017-03-24 23:00:00 (Fri)
+-63644734800, #  utc_end 2017-10-26 21:00:00 (Thu)
++63644824800, #  utc_end 2017-10-27 22:00:00 (Fri)
+ 63626090400, #  local_start 2017-03-25 02:00:00 (Sat)
+-63644745600, #local_end 2017-10-27 00:00:00 (Fri)
++63644835600, #local_end 2017-10-28 01:00:00 (Sat)
+ 10800,
+ 1,
+ 'EEST',
+ ],
+ [
+-63644734800, #utc_start 2017-10-26 21:00:00 (Thu)
++63644824800, #utc_start 2017-10-27 22:00:00 (Fri)
+ 63658134000, #  utc_end 2018-03-30 23:00:00 (Fri)
+-63644742000, #  local_start 2017-10-26 

Bug#841288: [Pkg-tigervnc-devel] Bug#841288: Bug#841288: tigervnc-common: amd64 has dep libgnutls-deb0-28

[Ola Lundqvist]

Hi all

I have made a source-only upload. This way the problem shall be solved.

// Ola

On 20 October 2016 at 08:49, Ola Lundqvist  wrote:
> Hi
>
> I'm the one to blame. I built it on stable.
>
> The problem is easy to solve by stepping the revision and building on
> unstable.
>
> I can not do that today but hopefully later this week.
>
> // Ola
>
> On 19 October 2016 at 23:26, Axel Beckert  wrote:
>>
>> Control: severity -1 serious
>>
>> Hi,
>>
>> Jacek Szafarkiewicz wrote:
>> > tigervnc-common needs libgnutls-deb0-28 on amd64 architecture.
>> > I think this dep should be for arm64.
>>
>> Nope, the amd64 package has been built on Debian Stable instead of
>> Debian Unstable and then uploaded to Debian Unstable anyways.
>>
>> See https://packages.debian.org/search?keywords=libgnutls-deb0-28
>>
>> (arm64 from debports doesn't count anymore, it's already in Debian
>> proper for multiple years.)
>>
>> Nevertheless, this is definitely a serious issue and tigervnc on
>> amd64 needs to be rebuilt in a clean chroot, e.g. by requesting a
>> BinNMU for it. (Which the maintainer of the package should do.
>>
>> Without that, the package won't migrate to testing.
>>
>> Regards, Axel
>> --
>>  ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
>> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
>> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>>   `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
>>
>> ___
>> Pkg-tigervnc-devel mailing list
>> pkg-tigervnc-de...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel
>
>
>
>
> --
>  - Ola Lundqvist ---
> /  o...@debian.org Folkebogatan 26  \
> |  o...@inguza.com  654 68 KARLSTAD  |
> |  http://inguza.com/  +46 (0)70-332 1551   |
> \  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
>  ---
>
>
> ___
> Pkg-tigervnc-devel mailing list
> pkg-tigervnc-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel



-- 
 - Ola Lundqvist ---
/  o...@debian.org Folkebogatan 26  \
|  o...@inguza.com  654 68 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Bug#841461: mate-screensaver: gtk3 theme errors still show up in .xsession-errors file

[shirish शिरीष]

Package: mate-screensaver
Version: 1.16.0-1
Severity: normal

Dear Maintainer,
The following errors still show up in .xsession-errors file.

(mate-screensaver:2523): Gtk-WARNING **: Theme parsing error:
gtk.css:63:28: The :prelight pseudo-class is deprecated. Use :hover
instead.

(mate-screensaver:2523): Gtk-WARNING **: Theme parsing error:
gtk.css:73:35: The :prelight pseudo-class is deprecated. Use :hover
instead.

Hopefully the above can be fixed in a future release.

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

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

Versions of packages mate-screensaver depends on:
ii  dbus-x11  1.10.12-1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-3
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.12-1
ii  libdbus-glib-1-2  0.108-1
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libgl1-mesa-glx [libgl1]  12.0.3-1
ii  libglib2.0-0  2.50.1-1
ii  libgtk-3-03.22.1-1
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.16.0-1
ii  libmate-menu2 1.16.0-1
ii  libmatekbd4   1.16.0-1
ii  libnotify40.7.7-1
ii  libpam0g  1.1.8-3.3
ii  libpango-1.0-01.40.3-2
ii  libpangocairo-1.0-0   1.40.3-2
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libsystemd0   231-9
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxklavier16 5.4-1
ii  libxss1   1:1.2.2-1
ii  libxxf86vm1   1:1.1.4-1
ii  mate-desktop-common   1.16.0-1
ii  mate-screensaver-common   1.16.0-1
ii  mate-session-manager  1.16.0-1

Versions of packages mate-screensaver recommends:
ii  mate-power-manager  1.16.0-1

Versions of packages mate-screensaver suggests:
ii  rss-glx0.9.1-6+b4
ii  xscreensaver-data  5.34-2

-- no debconf information


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

Bug#813212: Processed: retitle to O: polygen -- generator of random sentences from grammar definitions

[Adrian Bunk]

Control: retitle 813212 ITA: polygen -- generator of random sentences from 
grammar definitions
Control: owner 813212 Salvo Tomaselli 

On Wed, Oct 19, 2016 at 10:28:11PM +0200, Salvo Tomaselli wrote:
> Hey I'm still interested in packaging it, it's just that I didn't
> really see a reason for an upload.

Uploads are not really expensive.

Changing the maintainer is sufficient reason for an upload.

Additionally fixing the lintian warnings would be even more reason. ;-)

> But okay I'll start preparing it.

Thanks
Adrian

-- 

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

Bug#841460: mate-polkit: gtk3+ errors still persist in .xsession-errors. Package: mate-polkit

[shirish शिरीष]

Package: mate-polkit
Version: 1.16.0-1
Severity: normal

Dear Maintainer,
There are still errors logged in .xsession-errors about gtk3 and mate. See -

(polkit-mate-authentication-agent-1:2502): Gtk-WARNING **: Theme
parsing error: gtk.css:63:28: The :prelight pseudo-class is
deprecated. Use :hover instead.

(polkit-mate-authentication-agent-1:2502): Gtk-WARNING **: Theme
parsing error: gtk.css:73:35: The :prelight pseudo-class is
deprecated. Use :hover instead.

Hopefully the above can be fixed in a future release.

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

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

Versions of packages mate-polkit depends on:
ii  accountsservice0.6.40-3
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-3
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libglib2.0-0   2.50.1-1
ii  libgtk-3-0 3.22.1-1
ii  libpango-1.0-0 1.40.3-2
ii  libpangocairo-1.0-01.40.3-2
ii  libpolkit-agent-1-00.105-16
ii  libpolkit-gobject-1-0  0.105-16
ii  mate-polkit-common 1.16.0-1
ii  policykit-10.105-16

mate-polkit recommends no packages.

mate-polkit suggests no packages.

-- no debconf information

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

Bug#841459: bgpdump: FTBFS with bash as /bin/sh

[Chris Lamb]

Source: bgpdump
Version: 1.4.99.15+hg127-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

bgpdump fails to build from source in unstable/amd64 when 
/bin/sh is set to bash. It looks like the autoreconfing is
generating an invalid ./configure script:

  #! /bin/sh
  # From configure.ac 1.4.99.15+hg127-2
  .
  # Guess values for system-dependent variables and create Makefiles.
  # Generated by GNU Autoconf 2.69 for libbgpdump 1.4.99.15.
  #

  […]

 dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking
  ./configure: line 3: .: filename argument required
  .: usage: . filename [arguments]

The full build log is attached.


Regards,

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


bgpdump.1.4.99.15+hg127-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#841458: [src:libkf5ksieve] managing sieve scripts broken in kmail

[Maximilian Engelhardt]

Package: src:libkf5ksieve
Version: 4:16.04.2-2
Severity: important
Tags: patch

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

Managing sieve scripts from kmail is currently broken.  When trying to edit 
the rules I get this error:

Sieve operation failed.
The server responded:
require "fileinto";

This has been reported upstream here:
https://bugs.kde.org/show_bug.cgi?id=364394

Which seems to be caused by a broken fix of
https://bugs.kde.org/show_bug.cgi?id=328246

Cherry-picking upstream commit abc329d2b4d3a8efb489b0aa8dfb9cc2d2da9472 [1] 
(which reverts commit aa295b6cf15ee67a980b2858ccad6e6e8e769585 [2]) does 
indeed fix the problem.

So it would be great if ether a new upstream version with this fix included 
could be uploaded or if the fix can be backported to the current version.

[1] 
https://quickgit.kde.org/?p=libksieve.git=commit=abc329d2b4d3a8efb489b0aa8dfb9cc2d2da9472
[2] 
https://quickgit.kde.org/?p=libksieve.git=commit=aa295b6cf15ee67a980b2858ccad6e6e8e769585

Thanks,
Maxi


--- System information. ---
Architecture: amd64
Kernel:   Linux 4.7.0-1-amd64

Debian Release: stretch/sid
  500 testing httpredir.debian.org 
  500 stable  security.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-
libkf5ksieve-data(= 4:16.04.2-2) | 4:16.04.2-2
libc6  (>= 2.14) | 
libkf5i18n5  (>= 4.97.0) | 
libkf5kiocore5   (>= 4.96.0) | 
libkf5kiowidgets5(>= 4.96.0) | 
libkf5widgetsaddons5 (>= 4.96.0) | 
libqt5core5a (>= 5.6.0~beta) | 
libqt5network5   (>= 5.4.0~) | 
libqt5widgets5   (>= 5.4.0~) | 
libsasl2-2   | 
libstdc++6(>= 4.1.1) | 


Package's Recommends field is empty.

Package's Suggests field is empty.


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

Bug#839796: Ability to specify size for --skip-errors

[Andrew Wood]

I agree that this sounds like a good idea but there are some complications. 
What if we get an error while half-way through a block, because the disk is
failing but not wholly failed?  Do we skip a whole block, to half-way
through the next block, or only skip to the start of the next block?  How do
we know where the next block is?  Can we safely assume that all files on all
filesystems always start at the beginning of a block?

So perhaps if -E took an argument, we would explicitly state in the
documentation that on error, PV would skip to the start of the next block,
and would assume that the file starts at the beginning of a block.  So with
"-E 4k", an error at 2k would skip to 4k, an error at 4k would skip to 8k,
and so on.

Does this seem reasonable?



On Tue, Oct 04, 2016 at 09:10:36PM -0400, Anthony DeRobertis wrote:
> Package: pv
> Version: 1.6.0-1
> Severity: wishlist
> 
[...]
> So really it seems like -E ought to just skip 4k at once.
> 
> Or at least there ought to be an option to specify the skip size. I'd
> suggest -E should take an optional argument, the skip size, and default
> to 4k.

-- 
Andrew Wood

Bug#841457: ITP: conversant-disruptor -- Very low latency Java BlockingQueue

[Emmanuel Bourg]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: conversant-disruptor
  Version : 1.2.8
  Upstream Author : Conversant Inc
* URL : https://github.com/conversant/disruptor
* License : Apache-2.0
  Programming Lang: Java
  Description : Very low latency Java BlockingQueue

Disruptor is the highest performing intra-thread transfer mechanism
available in Java. Conversant Disruptor is the highest performing
implementation of this type of ring buffer queue because it has almost
no overhead and it exploits a particularly simple design.

This library is required to upgrade apache-log4j2 to the version 2.7.
It'll be maintained by the Java Team.

Bug#841456: light-locker: gtk3 theme errors logged in .xsession-errors.

[shirish शिरीष]

Package: light-locker
Version: 1.7.0-3
Severity: normal

Dear Maintainer,
There are few light-locker errors in .xsession-errors probably due to
move to gtk3+ . See -

(light-locker:2500): Gtk-WARNING **: Theme parsing error:
gtk.css:63:28: The :prelight pseudo-class is deprecated. Use :hover
instead.

(light-locker:2500): Gtk-WARNING **: Theme parsing error:
gtk.css:73:35: The :prelight pseudo-class is deprecated. Use :hover
instead.

(light-locker:2500): Gtk-WARNING **: Theme parsing error:
gtk.css:73:35: The :prelight pseudo-class is deprecated. Use :hover
instead.
mate-session[2251]: WARNING: Could not launch application
'gtk-redshift.desktop': Unable to start application: Failed to execute
child process "gtk-redshift" (No such file or directory)

I am running Debian-mate. Hopefully this can be fixed in near future.
Also, if there are any logs or anything which could help me to help
you please let me know.

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

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

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  libc62.24-3
ii  libcairo21.14.6-1+b1
ii  libdbus-1-3  1.10.12-1
ii  libdbus-glib-1-2 0.108-1
ii  libglib2.0-0 2.50.1-1
ii  libgtk-3-0   3.22.1-1
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libsystemd0  231-9
ii  libx11-6 2:1.6.3-1
ii  libxext6 2:1.3.3-1
ii  libxss1  1:1.2.2-1
ii  lightdm  1.18.2-2

light-locker recommends no packages.

light-locker suggests no packages.

-- no debconf information

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

Bug#831779: python-docutils: please make the output of rst2man reproducible

[Guenter Milde]

The reverted patch was buggy, incomplete and did not solve the problem of
non-reproducible builds due to timestamps in rst2man output.

Debian could solve the problem with a patch setting the config value::

  # Disables datestamp; equivalent to --no-datestamp:
  datestamp:
  
in /etc/docutils.conf or wait for a consensus among Docutils developers
after raising the issue on the docutils-devel list.

Günter

Bug#841425: dia-common: Fails to install with old xml-core.

[Adrian Bunk]

Control: tags -1 -newcomer
Control: severity -1 grave
Control: reassign -1 xml-core 0.14
Control: retitle -1 dh_installxmlcatalogs: xmlcorever must be increased to 0.14 
for sort
Control: affects -1 dia-common


On Thu, Oct 20, 2016 at 04:05:52PM +0200, Steven De Herdt wrote:
> Package: dia-common
> Version: 0.97.3+git20160930-1
> Severity: normal
> Tags: newcomer
> 
> Dear Maintainer,

Hi Steven,

> I tried to upgrade dia, with an old version (0.13+nmu2) of xml-core installed.
> It failed with the message "Unknown option: sort" and then the usage 
> instructions of update-xmlcatalog.  It appears this sort-option was added to 
> 0.14, upgrading my version of xml-core let me upgrade dia successfully.
> So I propose to bump the version dia-common requires accordingly.
> 
> Presumably the other dependants of xml-core are in the same situation, as
> this new option is used by dh_installxmlcatalogs.

thanks for your report, this should actually be fixed in xml-core.

The dependency on xml-core is generated automatically by 
dh_installxmlcatalogs.

Fixing it will include two parts:
1. fixed xml-core in unstable
2. rebuilding all affected packages with the fixed xml-core

> Thanks for maintaining!
> -Steven

cu
Adrian

-- 

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

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Andreas Tille]

Hi Sascha,

On Thu, Oct 20, 2016 at 10:17:03PM +0200, Sascha Steinbiss wrote:
> Hi all,
> 
> I have pushed a fix (9aac9cb) to Git, solving the FTBFS. Before doing an 
> upload I would be very happy if an Autotools-savvy person could take another 
> closer look because admittedly I am not really sure about the cause of the 
> problem.

May be asking for comments on debian-mentors@l.d.o might make sense.
 
> I also had to disable a test (test_usage) that otherwise also seems to 
> (mysteriously?) fail in my building chroot, resulting in:
> 
> pty_allocate(nonfatal): posix_openpt(): Permission denied at 
> /usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
> pty_allocate(nonfatal): getpt(): No such file or directory at 
> /usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
> pty_allocate(nonfatal): openpty(): No such file or directory at 
> /usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
> pty_allocate(nonfatal): open(/dev/ptmx): Permission denied at 
> /usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
> Cannot open a pty at test/test.pl line 551.

Strange as well.

I do not feel really competent here and have no spare time cycles to
have a deeper look in the next week(s).

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#831788: Closing the bug

[Anton Gladky]

fixed 831788 2.14.0+dfsg1-1
thanks

Hi,

there was no answer to the moreinfo mail. That is why I'm closing
the bug. Please, feel free to reopen it if you think the bug is still there, or
fill a new bug.

Kind regards,

Anton

Bug#840974: [Debian-med-packaging] Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Chris Lamb]

Sascha Steinbiss wrote:

> I fully agree and that was why I was asking for some extra pair of
> eyeballs before uploading

Excellent. For some reason I read your message as "I'm going to upload
anyway but if someone can take a look that would be nice I guess."

Mea culpa.  :)


Regards,

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

Bug#841455: lintian: tag r-other-* packages not in section "gnu-r"

[Dylan]

Package: lintian
Version: 2.5.48
Severity: wishlist
Tags: patch

Hi,
Please find attached another (the last) patch which enable the tag for
r-other-* packages not in section "gnu-r".

Thanks for having accepted all my patches related to R. :-)

Best,
Dylan
From 6bd22487288e4dbbc5205453e9230a43c73dc282 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dylan=20A=C3=AFssi?= 
Date: Thu, 20 Oct 2016 22:25:36 +0200
Subject: [PATCH] r-other-* packages should be in gnu-r section

---
 checks/fields.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/checks/fields.pm b/checks/fields.pm
index e1c5cdb..58eeec7 100644
--- a/checks/fields.pm
+++ b/checks/fields.pm
@@ -99,7 +99,7 @@ my @NAME_SECTION_MAPPINGS = (
 [qr/-dbg(?:sym)?$/=> 'debug'],
 [qr/^(?:python-)?zope/=> 'zope'],
 [qr/^python-/ => 'python'],
-[qr/^r-(?:cran|bioc)-/=> 'gnu-r'],
+[qr/^r-(?:cran|bioc|other)-/  => 'gnu-r'],
 [qr/^lib.*-perl$/ => 'perl'],
 [qr/^lib.*-cil(?:-dev)?$/ => 'cli-mono'],
 [qr/^lib.*-(?:java|gcj)$/ => 'java'],
-- 
2.1.4