Bug#903373: kitty: image rendering seems to be broken

2018-07-08 Thread Ritesh Raj Sarraf
Package: kitty
Version: 0.11.2-3
Severity: normal

Thank you for packaging the newer version of kitty.

With this version, the `icat` and `diff` commands fail with the
following error:


rrs@priyasi:~$ kitty diff rrs-home/Data/Pictures/debian-transparent.png 
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:87:34: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:88:29: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:89:29: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:90:29: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:91:29: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:92:27: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:93:27: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:94:27: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:95:27: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:96:29: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:97:29: string literal 
is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:97:29: too many errors
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:97:29: failed to 
parse file
[190 11:11:39.666312] [glfw error 65544]: Failed to create XKB compose table


Looking at upstream bug report:
https://github.com/kovidgoyal/kitty/issues/495
It looks like you need to bump a dependency on xkbcommon to >= 0.9.
FYI, xkbcommon (0.9) isn't yet in Debian.



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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kitty depends on:
ii  kitty-terminfo  0.9.0-1
ii  libc6   2.27-3
ii  libfontconfig1  2.13.0-5
ii  libfreetype62.8.1-2
ii  libharfbuzz0b   1.8.2-2
ii  libpng16-16 1.6.34-1
ii  libpython3.63.6.6-1
ii  libx11-62:1.6.5-1
ii  libx11-xcb1 2:1.6.5-1
ii  libxkbcommon-x11-0  0.8.0-2
ii  libxkbcommon0   0.8.0-2
ii  python3 3.6.5-3
ii  python3.6   3.6.6-1
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages kitty recommends:
ii  kitty-doc  0.11.2-3

kitty suggests no packages.

-- no debconf information



Bug#902967: RFS: ddnet/11.2.1-1

2018-07-08 Thread Yangfl
2018-07-05 6:10 GMT+08:00 Adam Borowski :
> On Wed, Jul 04, 2018 at 12:23:25PM +0800, Yangfl wrote:
>>  * Package name: ddnet
>>Version : 11.2.1-1
>   ^
>
>>   dget -x 
>> https://mentors.debian.net/debian/pool/main/d/ddnet/ddnet_11.2.1-2.dsc
>  ^
>>
>> Changes since the last upload:
>>
>>   * New upstream release
>
> Hi!
> The version you're requesting sponsorship for, and the one you pointed to,
> are different.  The changelog in the latter is:
>
> +ddnet (11.2.1-2) unstable; urgency=medium
> +
> +  * New upstream release
> +
> + -- Yangfl   Wed, 04 Jul 2018 00:17:11 +0800
> +
>  ddnet (11.1.8-1) unstable; urgency=medium
>
> with no trace of 11.2.1-1 anywhere.
>
> Is something amiss?
>
>
> 喵!
> --
> // If you believe in so-called "intellectual property", please immediately
> // cease using counterfeit alphabets.  Instead, contact the nearest temple
> // of Amon, whose priests will provide you with scribal services for all
> // your writing needs, for Reasonable And Non-Discriminatory prices.

Oops, sorry for fat-finger.

It should be fine now. lintain and sbuild passed.



Bug#902174: #902174: RFP: mes

2018-07-08 Thread Jan Nieuwenhuizen
Matt Wette writes:

> I don't understand why `eval' is needed, esp when forcing the shell to
> be bash.
> Is there any reference to this usage?

Debian's configure looks like what I wrote in the commit message (it
uses more options)

./configure --prefix=/usr --infodir=\${prefix}/share/info

Without the eval, this results in a Makfile with this snippet

GUILE=guile
SITE_SCM_DIR=/usr/share/guile/site/2.2
SITE_SCM_GO_DIR=/usr/lib/guile/2.2/site-ccache
INFODIR=${prefix}/share/info

Adding eval fixes this, it produces

GUILE=guile
SITE_SCM_DIR=/usr/share/guile/site/2.2
SITE_SCM_GO_DIR=/usr/lib/guile/2.2/site-ccache
INFODIR=/usr/share/info

Another fix would have been to also set `prefix' in Makefile

GUILE=guile
prefix=/usr

but that would have meant a much bigger Makefile change.  Reasons
of symmetry would demand

prefix=/usr
GUILE=guile
SITE_SCM_DIR=${prefix}/share/guile/site/2.2
SITE_SCM_GO_DIR=${prefix}/lib/guile/2.2/site-ccache
INFODIR=${prefix}/share/info

but then, because Nyacc uses

make -C .. -f Makefile.nyacc

we probably also need to pass prefix variable to the sub-makes...So I
chose the easy solution.

Greetings,
janneke

-- 
Jan Nieuwenhuizen  | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com



Bug#902744: plasma-workspace: Applications won't stay pinned to their Activity

2018-07-08 Thread Michael Haag
I would like to add some info regarding the bug report below. I subsequently 
did a complete reinstall of my system and recreated my original Activities, 
except for one of the lesser used.

Afterwards, all was good. Apps stayed pinned to their Activities. After many 
days of trouble free interaction, I decided to reinstate the one Activity I 
failed to create after the reinstall. Doing so resulted in the same behavior as 
before, apps being opened across ALL Activities.

It seems it's due to one particular KDE app, KInfocenter (Info Center). 
Immediately after pinning that app to the new Activity, then logging out and 
back in, the problem reappeared.


On Sat, Jun 30, 2018, at 14:56, MH wrote:
> Package: plasma-workspace
> Version: 4:5.12.5-1
> Severity: important
> 
> Dear Maintainer,
> 
> Applications will not stay "pinned" or "locked" to their assigned 
> Activity. I've tried using 
> window placement rules by right-clicking on the window title bar and 
> choosing the 
> appropriate Activity. I've tried to set application placement under 
> Advanced window settings
> using both "Remember" and "Force" options--nothing works. After logging 
> out and logging
> back in, various applications (all native KDE apps) will show up on in 
> ALL Activities. This
> does not happen every time. Sometimes it will be days before it happens, 
> sometimes after
> two or three logouts during a single day. This has been happening across 
> several versions
> of plasma-workspace. The problem pretty much makes using Actitities 
> pointless. Given the
> severity of it, I thought it would eventually be fixed. It hasn't.
> 
> The problem is repeatable. I tried cleaning out old config files. I even 
> created a new 
> user. Same problem. I tried going back to Virtual Desktops, but it 
> happens there as well.
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages plasma-workspace depends on:
> ii  dbus-x11 1.12.8-3
> ii  drkonqi  5.12.5-1
> ii  frameworkintegration 5.46.0-1
> ii  gdb-minimal [gdb]7.12-6+b2
> ii  iso-codes3.79-1
> ii  kactivitymanagerd5.12.5-1
> ii  kde-cli-tools4:5.12.5-1
> ii  kded55.46.0-1
> ii  kinit5.46.0-1
> ii  kio  5.46.0-1
> ii  kpackagetool55.46.0-1
> ii  kwin-common  4:5.12.5-1
> ii  libappstreamqt2  0.12.1-1
> ii  libc62.27-3
> ii  libcln6  1.3.4-4
> ii  libcolorcorrect5 4:5.12.5-1
> ii  libgcc1  1:8.1.0-8
> ii  libgps23 3.17-5+b1
> ii  libice6  2:1.0.9-2
> ii  libkf5activities55.46.0-1
> ii  libkf5auth5  5.46.0-1
> ii  libkf5baloo5 5.46.0-1
> ii  libkf5bookmarks5 5.46.0-1
> ii  libkf5calendarevents55.46.0-1
> ii  libkf5completion55.46.0-1
> ii  libkf5config-bin 5.46.0-1
> ii  libkf5configcore55.46.0-1
> ii  libkf5configgui5 5.46.0-1
> ii  libkf5configwidgets5 5.46.0-1
> ii  libkf5coreaddons55.46.0-1
> ii  libkf5crash5 5.46.0-1
> ii  libkf5dbusaddons55.46.0-1
> ii  libkf5declarative5   5.46.0-1
> ii  libkf5globalaccel-bin5.46.0-1
> ii  libkf5globalaccel5   5.46.0-1
> ii  libkf5guiaddons5 5.46.0-1
> ii  libkf5holidays5  1:5.47.0-1
> ii  libkf5i18n5  5.46.0-1
> ii  libkf5iconthemes55.46.0-1
> ii  libkf5idletime5  5.46.0-1
> ii  libkf5itemviews5 5.46.0-1
> ii  libkf5jobwidgets55.46.0-1
> ii  libkf5js55.46.0-1
> ii  libkf5jsembed5   5.46.0-1
> ii  libkf5kdelibs4support5   5.46.0-1
> ii  libkf5kiocore5   5.46.0-1
> ii  libkf5kiofilewidgets55.46.0-1
> ii  libkf5kiogui55.46.0-1
> ii  libkf5kiowidgets5

Bug#894757: libmypaint-common: file conflict with mypaint-data

2018-07-08 Thread Chris Waters
One possible solution here is to change the translation domain used
either by libmypaint or by mypaint.

I think it would be better to change the domain used by mypaint (to,
e.g., "mypaint12"), since that change would only have to be a
temporary one, until the next version comes out, which will (if I
understand correctly) *use* libmypaint. But of course, you'd have to
coordinate with the maintainer(s) to make that happen.

I took a look at the mypaint source, and unfortunately they don't have
a centralized location where the translation domain is defined. (Say
what you want about autoconf, but if they used it, this wouldn't have
been a problem.) I think I *might* be able to make a patch, but it's
enough effort (without autoconf) that I'd want to know the mypaint
maintainer was interested before I bothered.

Or you could change the translation domain used by libmypaint (perhaps
to "libmypaint"), but that is a lesser solution, since the patch
wouldn't have a clearly defined expiration date.



Bug#903372: please upload 0.27 to unstable

2018-07-08 Thread Lumin
Package: libgit2-dev
Version: 0.26.0+dfsg.1-1.2
Severity: wishlist

Dear libgit2 maintainer,

We wish to upload Julia to unstable. It depends on libgit2 >= 0.27,
which ships mbedtls support so that https:// is supported.

Could you please upload libgit2 to unstable?



Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

2018-07-08 Thread Mario.Limonciello
> -Original Message-
> From: Joel Cross [mailto:j...@kazbak.co.uk]
> Sent: Saturday, July 7, 2018 10:00 AM
> To: Michael Biebl; Limonciello, Mario; 902...@bugs.debian.org
> Subject: Re: Bug#902416: systemd: systemctl hibernate: unable to resume after
> upgrade
> 
> On Fri, 6 Jul 2018, at 5:31 PM, Michael Biebl wrote:
> > Am 06.07.2018 um 17:02 schrieb mario.limoncie...@dell.com:
> > >> -Original Message-
> > >> From: Michael Biebl [mailto:bi...@debian.org]
> >
> > >> If you have multiple swap partitions and you run
> > >> echo "disk" > /sys/power/state
> > >> which partition does the kernel use?
> > >>
> > >
> > > Whichever one was configured in /sys/power/resume prior to running that
> command.
> > >
> > > The kernel can't know which one /to/ hibernate to unless it was 
> > > configured in
> advance.
> > > Just like the initramfs can't know which one to resume /from/ unless it 
> > > knew
> which one
> > > it resumed to.
> > >
> >
> > Joel, can you please tell us,
> > - which partition you have configured in /etc/initramfs-tools/conf.d/resume
> > - which partition you have configured in /sys/power/resume
> > - the size of both swap partitions
> >
> 
> $ cat /proc/swaps
> Filename  TypeSizeUsedPriority
> /dev/sdb4   partition 9752572 1473128 100
> /dev/sda8   partition 6236156 0   10
> 
> $ blkid /dev/sdb4 /dev/sda8
> /dev/sdb4: LABEL="Swap" UUID="0797ee37-d1b9-49ea-a865-c73682cd96a7"
> TYPE="swap" PARTUUID="57f4c922-04"
> /dev/sda8: UUID="84f3e7a4-c3af-4ac1-a789-cc554395a50b" TYPE="swap"
> PARTUUID="170bc00e-08"
> 
> $ grep resume /boot/grub/grub.cfg|head -n 1
>   linux   /vmlinuz-4.16.0-2-amd64 root=UUID=033d10f2-5402-4632-bed0-
> 5e24842cf1b7 ro  quiet splash resume=UUID=84f3e7a4-c3af-4ac1-a789-
> cc554395a50b
> 
> $ cat /etc/initramfs-tools/conf.d/resume
> cat: /etc/initramfs-tools/conf.d/resume: No such file or directory
> 
> $ cat /sys/power/resume
> 8:8
> 
> From the above (especially grub.cfg) you can see that the smaller, 
> lower-priority
> partition is set as the resume partition (this was actually an oversight on 
> my part
> when I installed the second drive). Do you think this could be what's 
> preventing
> hibernate from working properly?
> 
> Also, do you think it is significant that the 
> /etc/initramfs-tools/conf.d/resume file
> does not exist on my system?
> 
> -Joel

I think I have an understanding on what's happening here.  So when you 
configured
your system to have a RESUME= variable on the DEFAULT kernel command line then
the kernel chooses to fill this one at bootup (hence the 8:8).  This kernel 
command line
is also what's passed to the initramfs, so even if you didn't configure that 
resume file
it's what is used for resuming.

Now the systemd changes have messed this up for you because they are writing to 
the
biggest swap (changing your 8:8).

As a simple fix, I expect if you change your RESUME= to the other swap 
partition your
resume behavior will be fine.

That being said, I think it makes sense to amend the systemd logic to also look 
for the
kernel command line RESUME= variable and choose that if the user had put it on 
kernel
command line.


Bug#903015: stretch-pu: package gridengine/8.1.9+dfsg-4

2018-07-08 Thread Afif Elghraoui



على الأحد  8 تـمـوز 2018 ‫14:38، كتب Adam D. Barratt:
> 
> Unfortunately, the build failed on armhf:
> 
> 
>  [java]  [exec] /usr/bin/ld: cannot find -ljvm
>  [java]  [exec] collect2: error: ld returned 1 exit status
>  [java]  [exec] make[2]: *** [jgdi_test] Error 1
> 
> BUILD FAILED
> /<>/gridengine-8.1.9+dfsg/source/build.xml:85: The following error 
> occurred while executing this line:
> /<>/gridengine-8.1.9+dfsg/source/build.xml:30: Java returned: 1
> 
> 
> Looking at buildd.d.o, this seems to have been happening in unstable
> for a few months now as well, but I can't find a related bug report.
> Any idea what's going on here?
> 

I asked the java team about this in December [1] and never heard back.
It seemed to me that the path to the openjdk libraries on armhf changed
so that the gridengine build system wasn't looking in the right place
anymore and thought the java team would know more about it. I didn't
pursue it further, though.


regards
Afif

1. https://lists.debian.org/debian-java/2017/12/msg00050.html

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name



Bug#903293: Please update elsarticle

2018-07-08 Thread Norbert Preining
Hi,

> Please update elsarticle to a newer version. The elsarticle version shipped 
> with
> Debian stable (and, to the best of my knowledge, 2018.20180505-1 from Debian
> testing), is 1.2.0 from 2009. In the meantime, I saw version 2.0 from 2012, 
> still
> available from rivervalley. The current version is 3.0 from 2018 and is 
> available

3.0 was upload less than a week ago to CTAN ... yes, it will be updated
in due time. Patience or a polite ping to upstream TeX Live is what
would be the proper path. I have cared for that already.

Best

Norbert

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



Bug#879030: 375.82-5: glxgears segmentation fault in glXCreateContext

2018-07-08 Thread Andreas Beckmann
Control: tag -1 moreinfo

On 2017-11-13 18:59, Vincas Dargis wrote:
> Feel free to let me know when some testing is needed.

Is this still an issue with the latest driver (390.67) available in sid,
buster, and (soon) stretch-backports?


Andreas



Bug#891957: netbeans "loading module" modules.netbinox NullPointerException

2018-07-08 Thread Kent West
Me, too.

westk@westkent64:~$ cat .netbeans/8.1/var/log/messages.log
---
>Log Session: Sunday, July 8, 2018 10:11:58 PM CDT
>System Info:
  Product Version = NetBeans IDE 8.1 (Build 20180424-debian-8.1)
  Operating System= Linux version 4.15.0-1-amd64 running on amd64
  Java; VM; Vendor= 1.8.0_171; OpenJDK 64-Bit Server VM 25.171-b11;
Oracle Corporation
  Runtime = OpenJDK Runtime Environment
1.8.0_171-8u171-b11-2-b11
  Java Home   = /usr/lib/jvm/java-8-openjdk-amd64/jre
  System Locale; Encoding = en_US (nb); UTF-8
  Home Directory  = /home/westk
  Current Directory   = /home/westk
  User Directory  = /home/westk/.netbeans/8.1
  Cache Directory = /home/westk/.cache/netbeans/8.1
  Installation= /usr/share/netbeans/8.1/nb
/usr/share/netbeans/8.1/ide
/usr/share/netbeans/8.1/java
/usr/share/netbeans/8.1/apisupport
/usr/share/netbeans/8.1/harness
/usr/share/netbeans/8.1/platform
  Boot & Ext. Classpath   =
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/classes:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/sunjce_provider.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/java-atk-wrapper.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/dnsns.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/cldrdata.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/icedtea-sound.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/sunpkcs11.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/localedata.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/jaccess.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/sunec.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/zipfs.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/nashorn.jar
  Application Classpath   =
/usr/share/java/jcodings.jar:/usr/share/netbeans/8.1/platform/lib/boot.jar:/usr/share/netbeans/8.1/platform/lib/org-openide-modules.jar:/usr/share/netbeans/8.1/platform/lib/org-openide-util.jar:/usr/share/netbeans/8.1/platform/lib/org-openide-util-lookup.jar:/usr/share/netbeans/8.1/platform/lib/org-openide-util-ui.jar:/usr/lib/jvm/java-8-openjdk-amd64/lib/dt.jar:/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar
  Startup Classpath   =
/usr/share/netbeans/8.1/platform/core/asm-all-5.0.1.jar:/usr/share/netbeans/8.1/platform/core/org-openide-filesystems.jar:/usr/share/netbeans/8.1/platform/core/core-base.jar:/usr/share/netbeans/8.1/platform/core/core.jar:/usr/share/netbeans/8.1/platform/core/org-openide-filesystems-compat8.jar:/usr/share/netbeans/8.1/platform/core/org-netbeans-libs-asm.jar:/usr/share/netbeans/8.1/nb/core/org-netbeans-upgrader.jar:/usr/share/netbeans/8.1/nb/core/locale/core_nb.jar
---
INFO [org.netbeans.modules.netbinox]: Install area set to
file:/usr/share/netbeans/8.1/
java.lang.NullPointerException
at
org.eclipse.osgi.baseadaptor.BaseAdaptor.initializeStorage(BaseAdaptor.java:123)
at
org.eclipse.osgi.framework.internal.core.Framework.(Framework.java:192)
at
org.eclipse.osgi.framework.internal.core.EquinoxLauncher.internalInit(EquinoxLauncher.java:67)
at
org.eclipse.osgi.framework.internal.core.EquinoxLauncher.init(EquinoxLauncher.java:37)
at org.eclipse.osgi.launch.Equinox.init(Equinox.java:178)
at org.netbeans.modules.netbinox.Netbinox.init(Unknown Source)
at org.netbeans.core.netigso.Netigso.prepare(Unknown Source)
at org.netbeans.NetigsoHandle.turnOn(Unknown Source)
at org.netbeans.ModuleManager.enable(Unknown Source)
INFO [null]: Last record repeated again.
at org.netbeans.core.startup.ModuleList.installNew(Unknown Source)
at org.netbeans.core.startup.ModuleList.trigger(Unknown Source)
at org.netbeans.core.startup.ModuleSystem.restore(Unknown Source)
at org.netbeans.core.startup.Main.getModuleSystem(Unknown Source)
INFO [null]: Last record repeated again.
at org.netbeans.core.startup.Main.start(Unknown Source)
at org.netbeans.core.startup.TopThreadGroup.run(Unknown Source)
at java.lang.Thread.run(Thread.java:748)
westk@westkent64:~$

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com


Bug#903371: ITP: ocaml-qcheck -- QuickCheck inspired property-based testing for OCaml

2018-07-08 Thread Andy Li
Package: wnpp
Severity: wishlist
Owner: Andy Li 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: ocaml-qcheck
  Version : 0.8
  Upstream Author : Simon Cruanes 
Rudi Grinberg 
Jacques-Pascal Deplaix 
Jan Midtgaard 
* URL : https://github.com/c-cube/qcheck
* License : BSD
  Programming Lang: OCaml
  Description : QuickCheck inspired property-based testing for OCaml

This module allows to check invariants (properties of some types) over randomly
generated instances of the type. It provides combinators for generating
instances and printing them.

This is one of the dependencies of the next version of Haxe (4.0.0).




-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJbQtJ5AAoJENYPsCrEEWxpQp4H/RzEQbLn54kzqCmwbpZLWcI1
U/ygzXbw8BXKtmisOm209gEnCVi265cuidbxRt9WPT8bxlNJb270/KUU0r4W0+Xd
sa90yYBVwRM/esWcrklTSkQBUCp0oVGMv5vVkEuw95i3OKJtS+ENuAox6Mj49l7X
EcdiQZ2vkrXBfq2NHVLT4wwLmnXhcau2xFJyAfMiL/Jqw3jhemu9oYJwc+pnrE83
LryrYt5s1c75hYySH2ZJiPrUmSotpeu2/1Ol3Tq0LElTEnMUwMMYe+09jTdqe82t
Rm1llmd0bWm6XElApArThzWnXsFcSBcTcy4cjLuIsqBcx7H79C4z8gsn1QgF2T0=
=n5Qp
-END PGP SIGNATURE-



Bug#884917: nvidia-driver: Black screen after SDDM login

2018-07-08 Thread Andreas Beckmann
Control: tag -1 - moreinfo
Control: close -1 390.67-1

On 2018-07-09 04:09, Michael Haag wrote:
> On Mon, Jul 9, 2018, at 08:05, Andreas Beckmann wrote:

>> Is this still an issue with the latest driver (390.67) available in sid,
>> buster, and (soon) stretch-backports?

> No. The problem was resolved with 390.67

Thanks for confirming!


Andreas



Bug#903288: systemd-container: container does not reboot when it is started by machinectl or systemctl,Re: Bug#903288: systemd-container: container does not reboot when it is started by machinectl or

2018-07-08 Thread Ryutaroh Matsumoto
Control: tags -1 + upstream

It turns out to be an upsteam bug standing for two years...

https://github.com/systemd/systemd/issues/9540#issuecomment-403342632



Bug#903110: [Pkg-rust-maintainers] Bug#903110: rustc: wasm32 target is enabled, but doesn't work

2018-07-08 Thread Angus Lees
Fwiw: Unless there is something that acts on `rustc --print target-list`
without applying some human judgement first, I would rather we just
reassigned this bug to LLVM and enabled wasm.  "Fixing" this in rustc, and
then unfixing it again once we add support to LLVM seems a little bit like
chasing our tails...

Ditto for other cross-compile targets (windows, android, etc) that are
reported in `target-list` but don't _actually_ work due to other missing
parts of the toolchain.

 - Gus

On Fri, 6 Jul 2018 at 19:39 Niels Langager Ellegaard <
niels.langager.ellega...@greve-gym.dk> wrote:

>
> Package: rustc
> Version: 1.26.2+dfsg1-1
> Severity: minor
>
> Dear Maintainers,
>
> The wasm32-unknown-unknown target is enabled in rustc, but it doesn't
> work.
> Alledgedly the problem is that the coresponding webassembly target isn't
> enabled in
> llvm. I guess that the target should be disabled in rustc if it doesn't
> work.
> (But in the long run it would be great to have the target enabled)
>


Bug#903370: transition: petsc

2018-07-08 Thread Drew Parsons
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

I'd like to proceed with the transition of petsc from 3.8 to 3.9 now.
All reverse dependencies are now ready for PETSc 3.9.

This transition applies also to slepc (from 3.8 to 3.9).

Ben file:

title = "petsc";
is_affected = .depends ~ "libpetsc-real3.8-dev" | .depends ~ 
"libpetsc-real3.9-dev";
is_good = .depends ~ "libpetsc-real3.9-dev";
is_bad = .depends ~ "libpetsc-real3.8-dev";


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

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



Bug#903176: jags: FTBFS in buster/sid (dh_installdocs: Cannot find "doc/manual/jags_installation_manual.pdf")

2018-07-08 Thread Dirk Eddelbuettel


On 7 July 2018 at 11:40, Santiago Vila wrote:
| Package: src:jags
| Version: 4.3.0-1
| Severity: serious
| Tags: ftbfs
| 
| Dear maintainer:
| 
| I tried to build this package in buster but it failed:
| 
| 

| [...]
|  debian/rules build-arch
| dh build-arch --with autoreconf
|dh_update_autotools_config -a
|dh_autoreconf -a
| sh: 1: hg: not found
| sh: 1: hg: not found
| sh: 1: hg: not found
| sh: 1: hg: not found
| sh: 1: hg: not found
| sh: 1: hg: not found
| sh: 1: hg: not found
| sh: 1: hg: not found
| sh: 1: hg: not found
| libtoolize: putting auxiliary files in '.'.
| 
| [... snipped ...]
| 
| make[5]: Leaving directory '/<>/win/runtime64'
| make[4]: Leaving directory '/<>/win/runtime64'
| make[4]: Entering directory '/<>/win'
| make[5]: Entering directory '/<>/win'
| make[5]: Nothing to be done for 'install-exec-am'.
| make[5]: Nothing to be done for 'install-data-am'.
| make[5]: Leaving directory '/<>/win'
| make[4]: Leaving directory '/<>/win'
| make[3]: Leaving directory '/<>/win'
| Making install in doc
| make[3]: Entering directory '/<>/doc'
| Making install in manual
| make[4]: Entering directory '/<>/doc/manual'
| make[5]: Entering directory '/<>/doc/manual'
| make[5]: Nothing to be done for 'install-exec-am'.
| make[5]: Nothing to be done for 'install-data-am'.
| make[5]: Leaving directory '/<>/doc/manual'
| make[4]: Leaving directory '/<>/doc/manual'
| make[4]: Entering directory '/<>/doc'
| make[5]: Entering directory '/<>/doc'
| make[5]: Nothing to be done for 'install-exec-am'.
|  /bin/mkdir -p '/<>/debian/jags/usr/share/man/man1'
|  /usr/bin/install -c -m 644 jags.1 
'/<>/debian/jags/usr/share/man/man1'
| make[5]: Leaving directory '/<>/doc'
| make[4]: Leaving directory '/<>/doc'
| make[3]: Leaving directory '/<>/doc'
| Making install in test
| make[3]: Entering directory '/<>/test'
| make[4]: Entering directory '/<>/test'
| make[4]: Nothing to be done for 'install-exec-am'.
| make[4]: Nothing to be done for 'install-data-am'.
| make[4]: Leaving directory '/<>/test'
| make[3]: Leaving directory '/<>/test'
| make[3]: Entering directory '/<>'
| make[4]: Entering directory '/<>'
| make[4]: Nothing to be done for 'install-exec-am'.
| make[4]: Nothing to be done for 'install-data-am'.
| make[4]: Leaving directory '/<>'
| make[3]: Leaving directory '/<>'
| make[2]: Leaving directory '/<>'
| find debian/ -name \*.la | \
|   xargs perl -p -i -e "s/dependency_libs='.*'/dependency_libs=''/" 
| make[1]: Leaving directory '/<>'
|dh_installdocs -a
| dh_installdocs: Cannot find (any matches for) 
"doc/manual/jags_installation_manual.pdf" (tried in .)
| 
| debian/rules:27: recipe for target 'binary-arch' failed
| make: *** [binary-arch] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
returned exit status 2
| 

| 
| The build was made with "dpkg-buildpackage -B" in my autobuilder
| but it also fails in reproducible builds:
| 
| https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jags.html
| 
| [ Note: There has been a recent change in debhelper behaviour, the current
|   behaviour is the intended one. See Bug #903133 for details ].
| 
| Thanks.

Trying to replicate now in my pbuilder. Seems to work here, even though I see
the 'hg missing' line it is building just fine.

If I add hg to Build-Depends and commit, could you test the package via the
salsa repo (which I just created) ?  It would be nice to have it tested
before I upload it.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Bug#903187: pyjwt: FTBFS in buster/sid (dh_installdocs: Cannot find "README.md")

2018-07-08 Thread Daniele Tricoli
Hello Santiago,

On Saturday, July 7, 2018 1:40:38 PM CEST Santiago Vila wrote:
> Package: src:pyjwt
> Version: 1.5.3+ds1-1
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:

Many thanks for the report, I will work on this today!

Cheers,

-- 
 Daniele Tricoli 'eriol'
 https://mornie.org



Bug#903302: nvidia-graphics-drivers: Unusable Vcs-Browser and Vcs-Git in debian/control

2018-07-08 Thread Andreas Beckmann
On 2018-07-08 16:58, Kevin Locke wrote:
> The Vcs-Browser and Vcs-Git fields in debian/control point to
> https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers
> which does not appear to exist.

That is intentional. Until I'm finished with the svn conversion
(backports and legacy still need to be checked, but I had to do too many
uploads in the last weeks so no time for that), history may still be
rewritten and there is only a temporary partial repository at a
non-advertised (but public) location.


Andreas



Bug#872988: nvidia-driver-libs: sudden crash (segmentation fault at address 0x0) in /usr/lib/xorg/modules/drivers/nvidia_drv.so

2018-07-08 Thread Andreas Beckmann
Control: tag -1 moreinfo

On 2017-08-23 15:35, Luca Boccassi wrote:
> On Wed, 2017-08-23 at 14:58 +0200, Vincent Lefevre wrote:
>> On 2017-08-23 11:55:44 +0100, Luca Boccassi wrote:
>>> Unfortunately it's in the binary blob, so there's nothing we can
>>> do.

Is this still an issue with the latest driver (390.67) available in sid,
buster, and (soon) stretch-backports?


Andreas



Bug#900428: nvidia-driver: Drop the glx-alternative system.

2018-07-08 Thread Andreas Beckmann
Control: tag -1 wontfix

On 2018-05-30 18:33, floris wrote:
> The new version of the Xserver (1.20) has support for a xorg.conf
> OutputClass section.
> This makes the glx-alternative system obsolete.

WONTFIX, at least as long as the 340xx legacy series is still supported,
since that does not support glvnd.


Andreas



Bug#818763: nvidia-kernel-dkms: fail to load nvidia-uvm (again)

2018-07-08 Thread Andreas Beckmann
Control: tag -1 moreinfo

On Tue, 22 Mar 2016 19:48:29 +0100 Michael Below  wrote:

> $ nvidia-modprobe -u
> modprobe: ERROR: could not insert 'nvidia_current_uvm': Operation not
> permitted 
> modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do()
> Error running install command for nvidia_uvm modprobe: ERROR: could not
> insert 'nvidia_uvm': Operation not permitted

Looking at this bug report again, this was likely an issue with
nvidia-modprobe (#888952), fixed in nvidia-modprobe 384.111-2, also
available in stretch.


Andreas



Bug#897207: nvidia-driver: redshift is now greenshift

2018-07-08 Thread Andreas Beckmann
Control: tag -1 moreinfo upstream

On 2018-04-30 04:29, Heikki Hokkanen wrote:
> Package: nvidia-driver
> Version: 390.48-2~bpo9+1

> After upgrading nvidia-driver from backports to version 390.48-2~bpo9+1,
> redshift is no longer red, but green. It kind of ruins the whole
> experience.

Is this still an issue with the latest driver (390.67) available in sid,
buster, and (soon) stretch-backports?


Andreas



Bug#900326: nvidia-driver: Nvidia 390.48.3 install erroneously enables Orca screen reader.

2018-07-08 Thread Andreas Beckmann
Control: tag -1 moreinfo unreproducible

On 2018-06-22 23:34, Luca Boccassi wrote:

> This sounds... strange. There is nothing anywhere referencing Orca. Are
> you _sure_ that it wasn't due to some other package?

I also don't think that this is caused by the nvidia driver.
And I have no idea how debug this issue.
Did you ask the orca maintainers for help?


Andreas



Bug#884917: nvidia-driver: Black screen after SDDM login

2018-07-08 Thread Andreas Beckmann
Control: tag -1 moreinfo

On 2017-12-21 11:47, MH wrote:
> Package: nvidia-driver
> Version: 384.98-3

> Video is broken when passed from PC through AVR. No problem when video is
> passed directly to TV using the same HDMI cabling. 
> 
> Hardware setup as follows: HTPC>HDMI>AVR>HDMI>HDTV
> 
> Black screen after logging in via SDDM. I can access a terminal, login in as 
> root, run startx and my KDE desktop will display but no audio device is 
> detected. I can also do this as a regular user via the su command.
> 
> This problem did not exist with an older card using the nvidia-legacy driver.
> The problem first exhibited as a black SDDM screen. However, I was still able
> to login. After login, KDE desktop worked normally, both video and audio.
> After a recent update, the SDDM login screen appeared normally, but I could
> no longer see my desktop. Keyboard navigation is still possible with the
> black screen.

Is this still an issue with the latest driver (390.67) available in sid,
buster, and (soon) stretch-backports?


Andreas



Bug#903288: systemd-container: container does not reboot when it is started by machinectl or systemctl,Re: Bug#903288: systemd-container: container does not reboot when it is started by machinectl or

2018-07-08 Thread Ryutaroh Matsumoto
Control: forwarded -1 https://github.com/systemd/systemd/issues/9540

Hi Michael, Thanks for your quick response.
I reported this to the upstream as above.
Ryutaroh


From: Michael Biebl 
Date: Sun, 8 Jul 2018 19:28:08 +0200
> We don't really ship any Debian specific patches in that regard, so it
> would be great if you can file this upstream.



Bug#884439: xserver-xorg-video-nvidia: xserver does not start because maximum pixel clock is not detected correctly

2018-07-08 Thread Andreas Beckmann
Control: tag -1 moreinfo

On 2017-12-15 09:27, Stefan Bischoff wrote:
> Package: xserver-xorg-video-nvidia
> Version: 384.98-3

> after the last update of the nvidia proprietary drivers, the xserver does not
> start any longer. The logs show, that the maximum pixel clock is not detected
> correctly for my Samsung Syncmaster 245B. GfxCard is a NVS315. Thus, there is
> no suitable mode and xserver does not start.

Is this still an issue with the latest driver (390.67) available in sid,
buster, and (soon) stretch-backports?


Andreas



Bug#903265: systemd-container: --property=Delegate=... does not work with systemd-nspawn,Re: Bug#903265: systemd-container: --property=Delegate=... does not work with systemd-nspawn

2018-07-08 Thread Ryutaroh Matsumoto
Control: forwarded -1 https://github.com/systemd/systemd/issues/9539

Hi Michael, Thanks for your quick response.
I reported this to the upstream as above.
Ryutaroh

From: Michael Biebl 
Date: Sun, 8 Jul 2018 19:29:52 +0200
> Try with apparmor disabled (apparmor=0 on the kernel command line) and
> with kernel 4.16. If it still fails, I would report it upstream.



Bug#902881: [debian-installer] Cannot partition disk in Testing installer

2018-07-08 Thread Andrey Gursky

Version: 20180625

This critical issue is still not fixed. Dear maintainers, please comment 
on this issue.


Thanks,
Andrey



Bug#903246: [pkg-cryptsetup-devel] Bug#903246:

2018-07-08 Thread Guilhem Moulin
Control: retitle -1 crypttab source specifications shouldn't be converted to 
/dev/block/$maj:$min
Control: severity -1 important
Control: tag -1 pending

On Sun, 08 Jul 2018 at 18:53:07 +1000, Ian Tester wrote:
> Upon further exploration, it appears the problem is that /dev/block is not
> being created and populated on this system. I'll have to figure out why
> that is. This report may be closed or at least knocked down in severity.

With a running udev daemon `udevadm trigger --type=devices --action=add`
creates and populates that directory.  This is done at early boot stage
and I'm not able to create a bootable environment where this is not the
case, so I'm lowering the severity to non-RC.

That being said there is no reason to convert the crypttab source
specifications to /dev/block/$maj:$min.  (We do want to do the
conversion when traversing the sysfs hierarchy, but for the crypttab
it's unnecessary.)  This commit should do it:


https://salsa.debian.org/cryptsetup-team/cryptsetup/commit/0d03f850113b3e5bd0d8211f0bc0161455e09368

-- 
Guilhem.


signature.asc
Description: PGP signature


Bug#903224: udev: Fails to upgrade

2018-07-08 Thread Michael Biebl
Am 09.07.2018 um 02:22 schrieb Michael Biebl:
> 2/ We remove the sandboxing features which trip up older systemd
> versions. Specifically this is the commit which turns the seccomp
> filters from a black into a whitelist. Specifically this would mean
> removing
> 
> SystemCallFilter=@system-service @module @raw-io
> SystemCallErrorNumber=EPERM
> 
> from systemd-udevd.service. With that change, the service file should
> work with systemd v232 from stretch. That patch would be dropped in
> buster+1.

> [1]
> https://github.com/systemd/systemd/commit/ee8f26180d01e3ddd4e5f20b03b81e5e737657ae

Given the comments in [1], removing the seccomp filter whitelist for
udev might be a good idea anyway, as this has the potential for breaking
(3rd party) udev rules.

Atm I'm leaning towards removing those 2 lines (and re-adding them for
buster+1) and dropping the versioned Breaks again we added for #902185,
which seemingly wasn't sufficient on its own.

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#903369: nagvis: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2018-07-08 Thread Adriano Rafael Gomes

Package: nagvis
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature


Bug#903224: udev: Fails to upgrade

2018-07-08 Thread Michael Biebl
Am 08.07.2018 um 17:51 schrieb Michael Biebl:
> Am 08.07.2018 um 17:42 schrieb Michael Biebl:

>> Any ideas how we can convince apt to upgrade the packages in the correct
>> order, ie. make sure that udev's postinst is run after systemd's
>> postinst without adding a versioned systemd Depends to udev?
> 
> 
> Bringing David and Julian into the loop here. Maybe they have a clever idea.
> 
> It's interesting to note, that apt does upgrade the packages in a proper
> order for me, but doesn't for others.

Atm, I see two options:

1/ We call systemctl daemon-reexec in udev.postinst before we restart
udev. The existing versioned Breaks ensures that we have systemd 239 or
newer unpacked. Triggering a daemon-reexec from udev is a bit icky but
it should be reasonably safe. Atm we don't have any upgrade code in
systemd.postinst which needs to run before we can re-exec PID 1 (which
doesn't mean this might not change before buster is released.
The daemon-reexec in udev.postinst would be a one-time only thing,
guarded by  dpkg --compare-versions "$1" lt 239-6

2/ We remove the sandboxing features which trip up older systemd
versions. Specifically this is the commit which turns the seccomp
filters from a black into a whitelist. Specifically this would mean
removing

SystemCallFilter=@system-service @module @raw-io
SystemCallErrorNumber=EPERM

from systemd-udevd.service. With that change, the service file should
work with systemd v232 from stretch. That patch would be dropped in
buster+1.



Thoughts, preferences?

[1]
https://github.com/systemd/systemd/commit/ee8f26180d01e3ddd4e5f20b03b81e5e737657ae
-- 
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#903368: phonon: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2018-07-08 Thread Adriano Rafael Gomes

Package: phonon
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature


Bug#903367: vcdimager: FTBFS in buster/sid (dh_installinfo: Cannot find "docs/vcd-info.info")

2018-07-08 Thread Santiago Vila
Package: src:vcdimager
Version: 2.0.1+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh_testdir
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:72: installing './compile'
configure.ac:51: installing './config.guess'
configure.ac:51: installing './config.sub'

[... snipped ...]

 /usr/bin/install -c -m 644 vcdxbuild.1 vcdxgen.1 vcdxrip.1 vcdxminfo.1 
'/<>/vcdimager-2.0.1+dfsg/debian/tmp/usr/share/man/man1'
make[5]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends/xml'
make[4]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends/xml'
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends/xml'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg/frontends'
make[4]: Entering directory '/<>/vcdimager-2.0.1+dfsg/frontends'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends'
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/frontends'
Making install in test
make[2]: Entering directory '/<>/vcdimager-2.0.1+dfsg/test'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg/test'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/test'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/test'
Making install in docs
make[2]: Entering directory '/<>/vcdimager-2.0.1+dfsg/docs'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg/docs'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/docs'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/docs'
Making install in example
make[2]: Entering directory '/<>/vcdimager-2.0.1+dfsg/example'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg/example'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/example'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg/example'
make[2]: Entering directory '/<>/vcdimager-2.0.1+dfsg'
make[3]: Entering directory '/<>/vcdimager-2.0.1+dfsg'
make[3]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p 
'/<>/vcdimager-2.0.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 libvcdinfo.pc 
'/<>/vcdimager-2.0.1+dfsg/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>/vcdimager-2.0.1+dfsg'
make[2]: Leaving directory '/<>/vcdimager-2.0.1+dfsg'
make[1]: Leaving directory '/<>/vcdimager-2.0.1+dfsg'
dh_testdir -a
dh_testroot -a
dh_installdocs -a
dh_installinfo -a
dh_installinfo: Cannot find (any matches for) "docs/vcd-info.info" (tried in .)

debian/rules:68: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vcdimager.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903366: starpu: FTBFS in buster/sid (dpkg-shlibdeps: error: cannot find library libsocl-1.2.so.0)

2018-07-08 Thread Santiago Vila
Package: src:starpu
Version: 1.2.4+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --parallel -Bbuild --with autoreconf
   dh_testdir -a -O--parallel -O-Bbuild
   dh_update_autotools_config -a -O--parallel -O-Bbuild
   dh_autoreconf -a -O--parallel -O-Bbuild
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,

[... snipped ...]

   dh_compress -a -O--parallel -O-Bbuild
   dh_fixperms -a -O--parallel -O-Bbuild
   dh_missing -a -O--parallel -O-Bbuild
   dh_strip -a -O--parallel -O-Bbuild
   dh_makeshlibs -a -O--parallel -O-Bbuild
   dh_shlibdeps -a -O--parallel -O-Bbuild
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/libstarpu-1.2-4/usr/lib/x86_64-linux-gnu/libstarpu-1.2.so.4.0.0 was not 
linked against libstdc++.so.6 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/libstarpufft-1.2-0/usr/lib/x86_64-linux-gnu/libstarpufft-1.2.so.0.0.1 
was not linked against libm.so.6 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/libstarpufft-1.2-0/usr/lib/x86_64-linux-gnu/libstarpufft-1.2.so.0.0.1 
was not linked against libOpenCL.so.1 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/libstarpufft-1.2-0/usr/lib/x86_64-linux-gnu/libstarpufft-1.2.so.0.0.1 
was not linked against libpthread.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/libstarpufft-1.2-0/usr/lib/x86_64-linux-gnu/libstarpufft-1.2.so.0.0.1 
was not linked against librt.so.1 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: symbol MPI_Isend used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_size used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Finalize used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol ompi_mpi_errors_return used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Type_size used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_c2f used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Type_get_contents used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Comm_f2c used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Type_free used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol MPI_Type_get_envelope used by 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
found in none of the libraries
dpkg-shlibdeps: warning: 19 other similar warnings have been skipped (use -v to 
see them all)
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
was not linked against librt.so.1 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/libstarpumpi-1.2-3/usr/lib/x86_64-linux-gnu/libstarpumpi-1.2.so.3.0.0 
was not linked against libm.so.6 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/starpu-tools/usr/bin/starpu_machine_display 
debian/starpu-tools/usr/bin/starpu_perfmodel_plot 
debian/starpu-tools/usr/bin/starpu_sched_display 
debian/starpu-tools/usr/bin/starpu_lp2paje 
debian/starpu-tools/usr/bin/starpu_calibrate_bus 
debian/starpu-tools/usr/bin/starpu_perfmodel_display were not linked against 
libpthread.so.0 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if 

Bug#903365: iptables: FTBFS in buster/sid (dh_installman: Cannot find "debian/nfnl_osf.8")

2018-07-08 Thread Santiago Vila
Package: src:iptables
Version: 1.6.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with autoreconf
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:13: installing 'build-aux/compile'
configure.ac:12: installing 'build-aux/missing'

[... snipped ...]

make[3]: Entering directory '/<>/iptables'
make[4]: Entering directory '/<>/iptables'
 /bin/mkdir -p '/<>/debian/tmp/usr/sbin'
  /bin/bash ../libtool   --mode=install /usr/bin/install -c xtables-multi 
xtables-compat-multi '/<>/debian/tmp/usr/sbin'
libtool: warning: '../libiptc/libip4tc.la' has not been installed in 
'/usr/lib/x86_64-linux-gnu'
libtool: warning: '../libiptc/libip6tc.la' has not been installed in 
'/usr/lib/x86_64-linux-gnu'
libtool: warning: '../libxtables/libxtables.la' has not been installed in 
'/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/xtables-multi 
/<>/debian/tmp/usr/sbin/xtables-multi
libtool: warning: '../libxtables/libxtables.la' has not been installed in 
'/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/xtables-compat-multi 
/<>/debian/tmp/usr/sbin/xtables-compat-multi
 /bin/mkdir -p '/<>/debian/tmp/usr/sbin'
 /usr/bin/install -c iptables-apply '/<>/debian/tmp/usr/sbin'
make  install-exec-hook
make[5]: Entering directory '/<>/iptables'
if test -z "/<>/debian/tmp"; then /sbin/ldconfig; fi;
/usr/bin/install -c -dm0755 "/<>/debian/tmp/usr/bin";
for i in iptables-xml; do ln -s -f "/usr/sbin/xtables-multi" 
"/<>/debian/tmp/usr/bin/$i"; done;
for i in iptables iptables-restore iptables-save; do ln -s -f xtables-multi 
"/<>/debian/tmp/usr/sbin/$i"; done;
for i in ip6tables ip6tables-restore ip6tables-save; do ln -s -f xtables-multi 
"/<>/debian/tmp/usr/sbin/$i"; done;
for i in iptables-compat iptables-compat-restore iptables-compat-save 
ip6tables-compat ip6tables-compat-restore ip6tables-compat-save 
iptables-translate ip6tables-translate iptables-restore-translate 
ip6tables-restore-translate arptables-compat ebtables-compat; do ln -s -f 
xtables-compat-multi "/<>/debian/tmp/usr/sbin/$i"; done;
ln -s -f iptables-apply "/<>/debian/tmp/usr/sbin/ip6tables-apply"
make[5]: Leaving directory '/<>/iptables'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man1'
 /usr/bin/install -c -m 644 iptables-xml.1 
'/<>/debian/tmp/usr/share/man/man1'
 /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man8'
 /usr/bin/install -c -m 644 iptables.8 iptables-restore.8 iptables-save.8 
ip6tables.8 ip6tables-restore.8 ip6tables-save.8 iptables-extensions.8 
iptables-apply.8 ip6tables-apply.8 
'/<>/debian/tmp/usr/share/man/man8'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 xtables.pc 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[4]: Leaving directory '/<>/iptables'
make[3]: Leaving directory '/<>/iptables'
make[2]: Leaving directory '/<>/iptables'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p '/<>/debian/tmp/etc'
 /usr/bin/install -c -m 644 etc/ethertypes '/<>/debian/tmp/etc'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_install -a
   dh_installdocs -a
   dh_installchangelogs -a
   dh_installman -a
dh_installman: Cannot find (any matches for) "debian/nfnl_osf.8" (tried in .)

dh_installman: Aborting due to earlier error
debian/rules:10: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/iptables.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#902809: want git-debrebase(?) smash-working-tree-timestamps

2018-07-08 Thread Ian Jackson
Maybe this should be in gdr rather than in dgit ?  gdr users might
want it too :-/.  One one hand gdr is for maintaining one's own
packages, and would would hope they will not have these we may not
have these kind of bugs.  On the other hand, this function is useful
on non-gdr-maintained branches too.  On the gripping hand, this
function might be necessary even with a pure-git workflow when dgit is
not needed.

Ian.

-- 
Ian JacksonThese 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#903361: haskell-tagsoup: FTBFS in buster/sid (dh_installexamples: Cannot find "Main.hs")

2018-07-08 Thread Santiago Vila
Package: src:haskell-tagsoup
Version: 0.14.6-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
make_setup_recipe
Running ghc --make Setup.hs -o debian/hlibrary.setup
[1 of 1] Compiling Main ( Setup.hs, Setup.o )
Linking debian/hlibrary.setup ...
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
configure_recipe
Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
--builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/tagsoup-0.14.6/ --datasubdir=tagsoup 
--htmldir=/usr/share/doc/libghc-tagsoup-doc/html/ --enable-library-profiling -f 
download
Configuring tagsoup-0.14.6...

[... snipped ...]

[ 4 of 13] Compiling Text.HTML.TagSoup.Match ( src/Text/HTML/TagSoup/Match.hs, 
dist-ghc/build/Text/HTML/TagSoup/Match.o )
[ 5 of 13] Compiling Text.HTML.TagSoup.Render ( 
src/Text/HTML/TagSoup/Render.hs, dist-ghc/build/Text/HTML/TagSoup/Render.o )
[ 6 of 13] Compiling Text.HTML.TagSoup.Options ( 
src/Text/HTML/TagSoup/Options.hs, dist-ghc/build/Text/HTML/TagSoup/Options.o )
[ 7 of 13] Compiling Text.HTML.TagSoup.Implementation ( 
src/Text/HTML/TagSoup/Implementation.hs, 
dist-ghc/build/Text/HTML/TagSoup/Implementation.o )
[ 8 of 13] Compiling Text.HTML.TagSoup.Specification ( 
src/Text/HTML/TagSoup/Specification.hs, 
dist-ghc/build/Text/HTML/TagSoup/Specification.o )
[ 9 of 13] Compiling Text.HTML.TagSoup.Manual ( 
src/Text/HTML/TagSoup/Manual.hs, dist-ghc/build/Text/HTML/TagSoup/Manual.o )
[10 of 13] Compiling Text.HTML.TagSoup.Generated ( 
src/Text/HTML/TagSoup/Generated.hs, 
dist-ghc/build/Text/HTML/TagSoup/Generated.o )
[11 of 13] Compiling Text.HTML.TagSoup.Parser ( 
src/Text/HTML/TagSoup/Parser.hs, dist-ghc/build/Text/HTML/TagSoup/Parser.o )
[12 of 13] Compiling Text.HTML.TagSoup ( src/Text/HTML/TagSoup.hs, 
dist-ghc/build/Text/HTML/TagSoup.o )
[13 of 13] Compiling Text.HTML.TagSoup.Tree ( src/Text/HTML/TagSoup/Tree.hs, 
dist-ghc/build/Text/HTML/TagSoup/Tree.o )
[ 1 of 13] Compiling Text.HTML.TagSoup.Entity ( 
src/Text/HTML/TagSoup/Entity.hs, dist-ghc/build/Text/HTML/TagSoup/Entity.p_o )
[ 2 of 13] Compiling Text.StringLike  ( src/Text/StringLike.hs, 
dist-ghc/build/Text/StringLike.p_o )
[ 3 of 13] Compiling Text.HTML.TagSoup.Type ( src/Text/HTML/TagSoup/Type.hs, 
dist-ghc/build/Text/HTML/TagSoup/Type.p_o )
[ 4 of 13] Compiling Text.HTML.TagSoup.Match ( src/Text/HTML/TagSoup/Match.hs, 
dist-ghc/build/Text/HTML/TagSoup/Match.p_o )
[ 5 of 13] Compiling Text.HTML.TagSoup.Render ( 
src/Text/HTML/TagSoup/Render.hs, dist-ghc/build/Text/HTML/TagSoup/Render.p_o )
[ 6 of 13] Compiling Text.HTML.TagSoup.Options ( 
src/Text/HTML/TagSoup/Options.hs, dist-ghc/build/Text/HTML/TagSoup/Options.p_o )
[ 7 of 13] Compiling Text.HTML.TagSoup.Implementation ( 
src/Text/HTML/TagSoup/Implementation.hs, 
dist-ghc/build/Text/HTML/TagSoup/Implementation.p_o )
[ 8 of 13] Compiling Text.HTML.TagSoup.Specification ( 
src/Text/HTML/TagSoup/Specification.hs, 
dist-ghc/build/Text/HTML/TagSoup/Specification.p_o )
[ 9 of 13] Compiling Text.HTML.TagSoup.Manual ( 
src/Text/HTML/TagSoup/Manual.hs, dist-ghc/build/Text/HTML/TagSoup/Manual.p_o )
[10 of 13] Compiling Text.HTML.TagSoup.Generated ( 
src/Text/HTML/TagSoup/Generated.hs, 
dist-ghc/build/Text/HTML/TagSoup/Generated.p_o )
[11 of 13] Compiling Text.HTML.TagSoup.Parser ( 
src/Text/HTML/TagSoup/Parser.hs, dist-ghc/build/Text/HTML/TagSoup/Parser.p_o )
[12 of 13] Compiling Text.HTML.TagSoup ( src/Text/HTML/TagSoup.hs, 
dist-ghc/build/Text/HTML/TagSoup.p_o )
[13 of 13] Compiling Text.HTML.TagSoup.Tree ( src/Text/HTML/TagSoup/Tree.hs, 
dist-ghc/build/Text/HTML/TagSoup/Tree.p_o )
touch build-ghc-stamp
debian/hlibrary.setup copy --builddir=dist-ghc --destdir=debian/tmp-inst-ghc
Installing library in 
debian/tmp-inst-ghc/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.2.2/tagsoup-0.14.6-Jl6qrF2IhECHKiNpGpgAS2
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
extra_depends_recipe ghc
Running dh_haskell_extra_depends ghc tagsoup-0.14.6.conf
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
install_doc_recipe "libghc-tagsoup-doc"
Running mkdir -p 
debian/libghc-tagsoup-doc/usr/share/doc/libghc-tagsoup-doc/html/
Running cd debian/tmp-inst-ghc/
Running find ./usr/share/doc/libghc-tagsoup-doc/html/ \! -name \*.haddock \! 
-type d -exec install -Dm 644 \{\} ../libghc-tagsoup-doc/\{\} \;
Running mkdir -p 
debian/libghc-tagsoup-doc/usr/lib/ghc-doc/haddock/tagsoup-0.14.6/
Running cp -r 
debian/tmp-inst-ghc/usr/lib/ghc-doc/haddock/tagsoup-0.14.6//tagsoup.haddock 

Bug#903363: plainbox: FTBFS in buster/sid (dh_installman: Cannot find "build/sphinx/man/CHECKBOX_DATA.7")

2018-07-08 Thread Santiago Vila
Package: src:plainbox
Version: 0.25-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with=python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build --buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.6_plainbox/build/plainbox
copying plainbox/abc.py -> 
/<>/.pybuild/cpython3_3.6_plainbox/build/plainbox

[... snipped ...]

byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/providers/test_special.py
 to test_special.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/providers/manifest/manage.py
 to manage.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/providers/v1.py
 to v1.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/providers/stubbox/manage.py
 to manage.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/box.py
 to box.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/censoREd.py
 to censoREd.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/test_symbol.py
 to test_symbol.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/test_buildsystems.py
 to test_buildsystems.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/ctrl.py
 to ctrl.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/test_xscanners.py
 to test_xscanners.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/test_color.py
 to test_color.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/developer.py
 to developer.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/resource.py
 to resource.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/_argparse.py
 to _argparse.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/test_validation.py
 to test_validation.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/impl/test_resource.py
 to test_resource.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/test_abc.py
 to test_abc.cpython-36.pyc
byte-compiling 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/public.py
 to public.cpython-36.pyc
running install_egg_info
Copying plainbox.egg-info to 
/<>/debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox-0.25.egg-info
Skipping SOURCES.txt
running install_scripts
Installing plainbox script to /<>/debian/python3-plainbox/usr/bin
Installing plainbox-qml-shell script to 
/<>/debian/python3-plainbox/usr/bin
Installing plainbox-trusted-launcher-1 script to 
/<>/debian/python3-plainbox/usr/bin
Installing stubbox script to /<>/debian/python3-plainbox/usr/bin
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
mkdir -p debian/plainbox/usr/bin
mkdir -p debian/python3-plainbox/usr/share/python3-plainbox/
mv debian/python3-plainbox/usr/bin/plainbox debian/plainbox/usr/bin/
cp -R plainbox/data debian/python3-plainbox/usr/share/python3-plainbox/
cp -R plainbox/test-data debian/python3-plainbox/usr/share/python3-plainbox/
rm -rf  debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/data
rm -rf  
debian/python3-plainbox/usr/lib/python3.6/dist-packages/plainbox/test-data
rm -f debian/python3-plainbox/usr/bin/stubbox
make[1]: Leaving directory '/<>'
   dh_installdocs -i -O--buildsystem=pybuild
   dh_sphinxdoc -i -O--buildsystem=pybuild
dh_sphinxdoc: Sphinx documentation not found
   dh_installchangelogs -i -O--buildsystem=pybuild
   dh_installman -i -O--buildsystem=pybuild
dh_installman: Cannot find (any matches for) "build/sphinx/man/CHECKBOX_DATA.7" 
(tried in .)

dh_installman: Aborting due to earlier error
debian/rules:8: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2

Bug#903360: goocanvasmm-2.0: FTBFS in buster/sid (dh_installexamples: Cannot find "usr/share/doc/goocanvasmm-2.0/examples")

2018-07-08 Thread Santiago Vila
Package: src:goocanvasmm-2.0
Version: 1.90.11-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with gnome
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build'.
libtoolize: copying file 'build/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build'.
libtoolize: copying file 'build/libtool.m4'
libtoolize: copying file 'build/ltoptions.m4'
libtoolize: copying file 'build/ltsugar.m4'
libtoolize: copying file 'build/ltversion.m4'
libtoolize: copying file 'build/lt~obsolete.m4'
configure.ac:47: installing 'build/compile'
configure.ac:26: installing 'build/missing'

[... snipped ...]

 /usr/bin/install -c -m 644 reference/goocanvasmm-2.0.tag 
'/<>/debian/tmp/usr/share/doc/goocanvasmm-2.0/reference'
make[3]: Leaving directory '/<>/doc'
make[2]: Leaving directory '/<>/doc'
Making install in examples
make[2]: Entering directory '/<>/examples'
make[3]: Entering directory '/<>/examples'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/examples'
make[2]: Leaving directory '/<>/examples'
Making install in tests
make[2]: Entering directory '/<>/tests'
make[3]: Entering directory '/<>/tests'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/tests'
make[2]: Leaving directory '/<>/tests'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p '/<>/debian/tmp/usr/include/goocanvasmm-2.0'
 /usr/bin/install -c -m 644 goocanvas/goocanvasmm.h 
'/<>/debian/tmp/usr/include/goocanvasmm-2.0'
 /bin/mkdir -p 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/goocanvasmm-2.0/include'
 /usr/bin/install -c -m 644 goocanvas/goocanvasmmconfig.h 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/goocanvasmm-2.0/include'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 goocanvas/goocanvasmm-2.0.pc 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install-indep
make[1]: Entering directory '/<>'
find debian/tmp -name jquery.js -delete
ln -sf /usr/share/javascript/jquery/jquery.js \
debian/tmp/usr/share/doc/goocanvasmm-2.0/reference/html/jquery.js
dh_install
make[1]: Leaving directory '/<>'
   dh_installdocs -i
   dh_installchangelogs -i
   debian/rules override_dh_installexamples
make[1]: Entering directory '/<>'
dh_installexamples -XMakefile -X.deps -X.libs -X.o -X.dirstamp
dh_installexamples: Cannot find (any matches for) 
"usr/share/doc/goocanvasmm-2.0/examples" (tried in .)

debian/rules:29: recipe for target 'override_dh_installexamples' failed
make[1]: *** [override_dh_installexamples] Error 2
make[1]: Leaving directory '/<>'
debian/rules:13: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/goocanvasmm-2.0.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903364: ruby-jira: FTBFS in buster/sid (dh_installdocs: Cannot find "README.rdoc")

2018-07-08 Thread Santiago Vila
Package: src:ruby-jira
Version: 1.4.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
rake jira:generate_public_cert
Executing 'openssl req -x509 -nodes -newkey rsa:1024 -sha1 -keyout rsakey.pem 
-out rsacert.pem'
Generating a 1024 bit RSA private key
.++

[... snipped ...]

  should search an issue with a jql query string and array expand
  should return meta data available for editing an issue
  provides direct accessors to the fields
  #respond_to?
when decorated by SimpleDelegator
  responds to key
  does not raise an error
  relationships
has the correct relationships

JIRA::Resource::ProjectFactory
  initializes correctly

JIRA::Resource::Project
  relationships
has the correct relationships
  issues
returns issues
with changelog
  returns issues
  users
pagination
  doesn't use pagination parameters by default
  accepts start_at option
  accepts max_results option
  accepts start_at and max_results options

JIRA::Resource::UserFactory
  #myself
returns a JIRA::Resource::User with correct attrs

JIRA::Resource::Worklog
  relationships
has the correct relationships

Finished in 0.09517 seconds (files took 0.54893 seconds to load)
183 examples, 0 failures


┌──────────────────────────────────────────────────────────────────────────────┐
│ dh_ruby --install finished  
 │
└──────────────────────────────────────────────────────────────────────────────┘

   dh_installdocs -i -O--buildsystem=ruby
dh_installdocs: Cannot find (any matches for) "README.rdoc" (tried in .)

debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-jira.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903362: percol: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:percol
Version: 0.2.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   dh_auto_build -i
dh_auto_build: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_build: This feature will be removed in compat 12.
python setup.py build --force
running build
running build_py
creating build

[... snipped ...]

python setup.py install --force --root=/<>/debian/percol 
--no-compile -O0 --install-layout=deb
running install
running build
running build_py
running build_scripts
running install_lib
creating /<>/debian/percol/usr
creating /<>/debian/percol/usr/lib
creating /<>/debian/percol/usr/lib/python2.7
creating /<>/debian/percol/usr/lib/python2.7/dist-packages
creating /<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/command.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/action.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/info.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/actions.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/tty.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/cli.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/lazyarray.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/finder.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/view.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/__init__.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/model.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/markup.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/key.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/debug.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/display.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
copying build/lib.linux-x86_64-2.7/percol/ansi.py -> 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol
running install_egg_info
running egg_info
creating percol.egg-info
writing requirements to percol.egg-info/requires.txt
writing percol.egg-info/PKG-INFO
writing top-level names to percol.egg-info/top_level.txt
writing dependency_links to percol.egg-info/dependency_links.txt
writing manifest file 'percol.egg-info/SOURCES.txt'
reading manifest file 'percol.egg-info/SOURCES.txt'
writing manifest file 'percol.egg-info/SOURCES.txt'
Copying percol.egg-info to 
/<>/debian/percol/usr/lib/python2.7/dist-packages/percol-0.2.1.egg-info
Skipping SOURCES.txt
running install_scripts
creating /<>/debian/percol/usr/bin
copying build/scripts-2.7/percol -> /<>/debian/percol/usr/bin
changing mode of /<>/debian/percol/usr/bin/percol to 775
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:4: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/percol.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#900469: firefox: Spell checker stopped working after upgrading from version 60 to 61.0~b8

2018-07-08 Thread Ben Caradoc-Davies

Confirmed fixed in 61.0-2. Thanks!

Kind regards,

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



Bug#903359: mailman-hyperkitty: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2018-07-08 Thread Adriano Rafael Gomes

Package: mailman-hyperkitty
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature


Bug#903358: lava: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2018-07-08 Thread Adriano Rafael Gomes

Package: lava
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature


Bug#892945: Cannot start domain using user session

2018-07-08 Thread Michael Biebl
Related to that is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887852

systemd upstream removed the uaccess bits, as they install /dev/kvm with
0666 permissions by default, claiming this would be safe nowadays.

See
https://github.com/systemd/systemd/pull/5597
https://github.com/systemd/systemd/commit/b8fd3d82205f632ce001fade74fed287e1564a1a

I think long term it would be best if the udev package setups up the
correct permissions for /dev/kvm, the question is whether we follow the
upstream default and make /dev/kvm 0666 or we chose 0640 (root:kvm) and
revert the bits from b8fd3d82205f632ce001fade74fed287e1564a1a to re-add
the uaccess tag.


Thoughts, Preferences?

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#902174: #902174: RFP: mes

2018-07-08 Thread Vagrant Cascadian
On 2018-07-08, Jan Nieuwenhuizen wrote:
> Vagrant Cascadian writes:
>> Packaging branch for nyacc:
>>
>>   https://salsa.debian.org/vagrant/nyacc
>>
>> Fails to build as it installs info pages to /share/info. Doesn't appear
>> to respect DESTDIR= ... but setting --infodir doesn't work as I would
>> expect either, suddently appending --prefix to it.
>
> I have looked into this; please see `debian' branch at
>
> http://gitlab.com/janneke/nyacc

Built!


>> And also a packaging branch for mes itself, but of course can't test it
>> until nyacc is working:
>>
>>   https://salsa.debian.org/vagrant/mes
>
> I will have a look at this later.  You will probably want to rebase on
> my `wip-gnu' branch: it has (experimental) DESTDIR and other Debian
> build support (e.g.: do not assume /bin/sh is bash, resurrect guile-2.0).

Tried building with this, and had a couple issues.

The clean target assumes a git checkout:

  clean:
git clean -dfx

But Debian builds against tarballs of the source, and running 'git clean
-dfx' from a directory with the source unpackaged but no .git directory
fails.

The configure target doesn't take some common options, and fails when
unknown options are passed, such as --includedir. The default build
passed these:

  ./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 --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking

From the ./configure help output, it suggests that only --prefix and
--sysconfdir are supported, but maybe not all the supported options are
documented.


Working around that by only passing:

  ./configure --prefix=/usr --sysconfdir=/etc

And a no-op clean target...


Still fails to build:

build-aux/build-cc.sh
...
;;; WARNING: compilation of 
/<>/mes-0.16+0.3da4d01/build-aux/mes-snarf.scm failed:
;;; ERROR: failed to create path for auto-compiled file 
"/<>/mes-0.16+0.3da4d01/build-aux/mes-snarf.scm"
mes-snarf[guile]...
lib/libmes.c:21:10: fatal error: libmes.h: No such file or directory
 #include 
  ^~
compilation terminated.
make[2]: *** [GNUmakefile:39: cc] Error 1
make[2]: Leaving directory '/<>/mes-0.16+0.3da4d01'
make[1]: *** [GNUmakefile:123: src/mes.gcc-out] Error 2
make[1]: *** Waiting for unfinished jobs
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;   or pass the --no-auto-compile argument to disable.
;;; compiling /<>/mes-0.16+0.3da4d01/build-aux/mes-snarf.scm
;;; WARNING: compilation of 
/<>/mes-0.16+0.3da4d01/build-aux/mes-snarf.scm failed:

;;; ERROR: failed to create path for auto-compiled file 
"/<>/mes-0.16+0.3da4d01/build-aux/mes-snarf.scm"
mes-snarf[guile]...
lib/libmes.c:21:10: fatal error: libmes.h: No such file or directory
 #include 
  ^~
compilation terminated.
make[1]: *** [GNUmakefile:36: build] Error 1
make[1]: Leaving directory '/<>/mes-0.16+0.3da4d01'
dh_auto_build: make -j4 returned exit code 2


So, some progress, but still some work left to do! :)


live well,
  vagrant


signature.asc
Description: PGP signature


Bug#903357: minissdpd: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2018-07-08 Thread Adriano Rafael Gomes

Package: minissdpd
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature


Bug#903356: expeyes: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2018-07-08 Thread Adriano Rafael Gomes

Package: expeyes
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature


Bug#903355: iproute2: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2018-07-08 Thread Adriano Rafael Gomes

Package: iproute2
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature


Bug#903354: charliecloud: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2018-07-08 Thread Adriano Rafael Gomes

Package: charliecloud
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: Digital signature


Bug#903132: -fdiverged when `git debrebase convert-from-gbp` after `dgit push --gbp`

2018-07-08 Thread Ian Jackson
Ian Jackson writes ("Re: Bug#903132: -fdiverged when `git debrebase 
convert-from-gbp` after `dgit push --gbp`"):
> Ian Jackson writes ("Re: Bug#903132: -fdiverged when `git debrebase 
> convert-from-gbp` after `dgit push --gbp`"):
> > Also what should it do if the user just specifies --force ?  I guess
> > not make the pseudomerge and expect the user to do some suitable
> >   git merge -s ours
> > later.
> 
> So, that.  The result will be:
> 
>   All is well: automatic pseudomerge of archive/debian/something
> 
>   Things aren't quite right: Snags reported: reasons why things aren't
>   right, and `diverged'.  Without -f or --force, failure (HEAD left
>   unchanged).
> 
>   -f used for "Reasons why things aren't right": pseudomerge
>   made anyway, `diverged' not reported any more.
> 
>   -fdiverged used, or --force: no pseudomerge made.

This all turned out not to be necessary.  There are no checks done
before making the pseudomerge which it would be sensible to offer
forcing for.  So:

  All is well: automatic pseudomerge.

  Something is not well enough for that: No pseduomerge (and a message
  to stderr saying why).  Likely need for -fdiverged.

Ian.

-- 
Ian JacksonThese 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#902658: apache2: apachectl graceful/restart results in segfault

2018-07-08 Thread gregor herrmann
On Fri, 29 Jun 2018 10:35:32 +0200, mer.at wrote:

> Package: apache2
> Version: 2.4.33-3+b1
> Severity: grave
> Tags: a11y
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> when i do an "apachectl graceful" or "apachectl restart", i get
> segfaults.


Same here.
As graceful restarts happen on all kinds of package updates but also
during the daily logrotate, this is quit problematic.

[Mon Jul 09 00:29:00.690201 2018] [mpm_prefork:notice] [pid 25910] AH00163: 
Apache/2.4.33 (Debian) SVN/1.10.0 mod_fcgid/2.3.9 mod_jk/1.2.43 OpenSSL/1.1.0h 
mod_wsgi/4.5.17 Python/2.7 configured -- resuming normal operations
[Mon Jul 09 00:29:00.690266 2018] [core:notice] [pid 25910] AH00094: Command 
line: '/usr/sbin/apache2'
[Mon Jul 09 00:29:01.704980 2018] [core:notice] [pid 25910] AH00051: child pid 
12011 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Mon Jul 09 00:29:01.705096 2018] [cgid:error] [pid 25910] AH01239: cgid daemon 
process died, restarting
[Mon Jul 09 00:29:01.707171 2018] [core:notice] [pid 25910] AH00051: child pid 
12012 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Mon Jul 09 00:29:01.707220 2018] [fcgid:error] [pid 25910] mod_fcgid: fcgid 
process manager died, restarting the server
[Mon Jul 09 00:29:01.800253 2018] [core:error] [pid 25910] AH00546: no record 
of generation 0 of exiting child 12167
[Mon Jul 09 00:29:03.063634 2018] [mpm_prefork:notice] [pid 25910] AH00173: 
SIGHUP received.  Attempting to restart


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bjørn Berge: Buena


signature.asc
Description: Digital Signature


Bug#903353: gnucash: internal date corruption near summer time change

2018-07-08 Thread Vincent Lefevre
Package: gnucash
Version: 1:3.2-1
Severity: grave
Justification: causes non-serious data loss

After the upgrade to gnucash 3.x (well, I assume this is the cause),
some dates in the .gnc file have changed incorrectly. For instance:

   
-2012-03-25 03:47:47 +0200
+2012-03-25 02:47:47 +0100
   

   
-2012-03-25 03:50:40 +0200
+2012-03-25 02:50:40 +0100
   

   
-2012-03-25 03:51:02 +0200
+2012-03-25 02:51:02 +0100
   

   
-2012-03-25 03:48:15 +0200
+2012-03-25 02:48:15 +0100
   

   
-2017-10-29 02:53:42 +0200
+2017-10-29 01:53:42 +0100
   

   
-2017-10-29 02:53:54 +0200
+2017-10-29 01:53:54 +0100
   

The dates are equivalent in term of UTC times, but the timezones
silently became incorrect.

These entries were entered with the Europe/Paris timezone. But:

$ TZ=Europe/Paris date +'%F %T %z' -d '2012-03-25 02:47:47 +0100'
2012-03-25 03:47:47 +0200

So, 2012-03-25 03:47:47 +0200 was really the correct local date+time,
not 2012-03-25 02:47:47 +0100.

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

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

Versions of packages gnucash depends on:
ii  gnucash-common   1:3.2-1
ii  guile-2.22.2.3+1-5
ii  guile-2.2-libs   2.2.3+1-5
ii  libaqbanking35   5.7.8-1
ii  libaqbanking35-plugins   5.7.8-1
ii  libatk1.0-0  2.28.1-1
ii  libboost-date-time1.62.0 1.62.0+dfsg-6
ii  libboost-filesystem1.62.01.62.0+dfsg-6
ii  libboost-locale1.62.01.62.0+dfsg-6
ii  libboost-regex1.62.0 1.62.0+dfsg-6
ii  libboost-system1.62.01.62.0+dfsg-6
ii  libc62.27-4
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libcrypt-ssleay-perl 0.73.06-1
ii  libdate-manip-perl   6.72-1
ii  libdbi1  0.9.0-5
ii  libfinance-quote-perl1.47-1
ii  libgc1c2 1:7.4.2-8.3
ii  libgcc1  1:8.1.0-9
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-2
ii  libgwenhywfar60  4.20.0-1
ii  libhtml-tableextract-perl2.15-1
ii  libhtml-tree-perl5.07-1
ii  libicu60 60.2-6
ii  libjavascriptcoregtk-4.0-18  2.20.3-1
ii  libktoblzcheck1v51.49-4
ii  libofx7  1:0.9.13-2
ii  libpango-1.0-0   1.42.1-1
ii  libpangocairo-1.0-0  1.42.1-1
ii  libsecret-1-00.18.6-2
ii  libsoup2.4-1 2.62.2-2
ii  libstdc++6   8.1.0-9
ii  libwebkit2gtk-4.0-37 2.20.3-1
ii  libwww-perl  6.34-1
ii  libxml2  2.9.4+dfsg1-7+b1
ii  libxslt1.1   1.1.32-2
ii  perl 5.26.2-6
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gnucash recommends:
ii  gnucash-docs 3.2-1
ii  python3-gnucash  1:3.2-1
ii  yelp 3.28.1-1

Versions of packages gnucash suggests:
pn  libdbd-mysql
pn  libdbd-pgsql
pn  libdbd-sqlite3  

-- no debconf information



Bug#900658: Acknowledgement (Intel HD graphics display rotation broken with 2:1.20.0-2)

2018-07-08 Thread Yuri D'Elia
FIY, this is not only related to Intel, and has been fixed upstream:

  https://bugs.freedesktop.org/show_bug.cgi?id=106715

I tested manually the patch and it fixes the issue for me as well.
Would it be possible to backport the fix into the current package?

  https://patchwork.freedesktop.org/series/44802/

Thanks



Bug#903352: pytools: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:pytools
Version: 2018.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
find pytools/ -name decorator.py -delete
find pytools/ -name log.py -delete

[... snipped ...]

copying /<>/.pybuild/cpython3_3.6/build/pytools/convergence.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/persistent_dict.py 
-> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/test.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/datatable.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/__init__.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/stopwatch.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/version.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/prefork.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/py_codegen.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/obj_array.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying /<>/.pybuild/cpython3_3.6/build/pytools/diskdict.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
copying 
/<>/.pybuild/cpython3_3.6/build/pytools/arithmetic_container.py -> 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/mpi.py
 to mpi.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/debug.py
 to debug.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/lex.py
 to lex.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/spatial_btree.py
 to spatial_btree.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/batchjob.py
 to batchjob.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/mpiwrap.py
 to mpiwrap.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/convergence.py
 to convergence.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/persistent_dict.py
 to persistent_dict.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/test.py
 to test.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/datatable.py
 to datatable.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/stopwatch.py
 to stopwatch.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/version.py
 to version.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/prefork.py
 to prefork.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/py_codegen.py
 to py_codegen.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/obj_array.py
 to obj_array.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/diskdict.py
 to diskdict.cpython-36.pyc
byte-compiling 
/<>/debian/python3-pytools/usr/lib/python3.6/dist-packages/pytools/arithmetic_container.py
 to arithmetic_container.cpython-36.pyc
running install_egg_info
running egg_info
writing pytools.egg-info/PKG-INFO
writing dependency_links to pytools.egg-info/dependency_links.txt
writing requirements to pytools.egg-info/requires.txt
writing top-level names to pytools.egg-info/top_level.txt
reading manifest file 'pytools.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest 

Bug#903350: golang-github-gosuri-uitable: FTBFS in buster/sid (dh_installdocs: Cannot find "README.rst")

2018-07-08 Thread Santiago Vila
Package: src:golang-github-gosuri-uitable
Version: 0.0~git20170830.36ee7e94-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/golang-github-gosuri-uitable-0.0\~git20170830.36ee7e94/obj-x86_64-linux-gnu/src\"
 
-asmflags=\"-trimpath=/<>/golang-github-gosuri-uitable-0.0\~git20170830.36ee7e94/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/gosuri/uitable github.com/gosuri/uitable/example 
github.com/gosuri/uitable/util/strutil github.com/gosuri/uitable/util/wordwrap
github.com/mattn/go-runewidth
github.com/gosuri/uitable/util/strutil
github.com/gosuri/uitable/util/wordwrap
github.com/gosuri/uitable
github.com/gosuri/uitable/example
   dh_auto_test -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/gosuri/uitable github.com/gosuri/uitable/example 
github.com/gosuri/uitable/util/strutil github.com/gosuri/uitable/util/wordwrap
=== RUN   TestCell
--- PASS: TestCell (0.00s)
=== RUN   TestRow
--- PASS: TestRow (0.00s)
=== RUN   TestAlign
--- PASS: TestAlign (0.00s)
=== RUN   TestAddRow
--- PASS: TestAddRow (0.00s)
PASS
ok  github.com/gosuri/uitable   0.001s
?   github.com/gosuri/uitable/example   [no test files]
=== RUN   TestResize
--- PASS: TestResize (0.00s)
=== RUN   TestAlign
--- PASS: TestAlign (0.00s)
=== RUN   TestJoin
--- PASS: TestJoin (0.00s)
=== RUN   TestPadRight
--- PASS: TestPadRight (0.00s)
=== RUN   TestPadLeft
--- PASS: TestPadLeft (0.00s)
PASS
ok  github.com/gosuri/uitable/util/strutil  0.001s
=== RUN   TestWrapString
--- PASS: TestWrapString (0.00s)
PASS
ok  github.com/gosuri/uitable/util/wordwrap 0.001s
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=golang --with=golang
   dh_testroot -i -O--buildsystem=golang
   dh_prep -i -O--buildsystem=golang
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install
cd obj-x86_64-linux-gnu && mkdir -p 
/<>/golang-github-gosuri-uitable-0.0\~git20170830.36ee7e94/debian/golang-github-gosuri-uitable-dev/usr
cd obj-x86_64-linux-gnu && cp -r bin 
/<>/golang-github-gosuri-uitable-0.0\~git20170830.36ee7e94/debian/golang-github-gosuri-uitable-dev/usr
cd obj-x86_64-linux-gnu && mkdir -p 
/<>/golang-github-gosuri-uitable-0.0\~git20170830.36ee7e94/debian/golang-github-gosuri-uitable-dev/usr/share/gocode/src/github.com/gosuri/uitable
cd obj-x86_64-linux-gnu && cp -r -T src/github.com/gosuri/uitable 
/<>/golang-github-gosuri-uitable-0.0\~git20170830.36ee7e94/debian/golang-github-gosuri-uitable-dev/usr/share/gocode/src/github.com/gosuri/uitable
rm -rf ./debian/golang-github-gosuri-uitable-dev/usr/bin/example
make[1]: Leaving directory '/<>'
   dh_installdocs -i -O--buildsystem=golang
dh_installdocs: Cannot find (any matches for) "README.rst" (tried in .)

debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-gosuri-uitable.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903351: latexml: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:latexml
Version: 0.8.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh_testdir
# Add here commands to compile the package.
perl Makefile.PL INSTALLDIRS=vendor NOMKTEXLSR=1
/usr/local/share/texmf
Warning: prerequisite Text::Unidecode 0 not found.
Checking if your kit is complete...
Looks good
'NOMKTEXLSR' is not a known MakeMaker parameter name.
Generating a Unix-style Makefile
Writing Makefile for LaTeXML
Writing MYMETA.yml and MYMETA.json
===
| If you plan on developing code, please consider using

[... snipped ...]

Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Tokens.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::MuDimension.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::MuGlue.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Mouth::file.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Mouth::http.3pm
Installing /<>/debian/latexml/usr/share/man/man3/LaTeXML.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Whatsit.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Config.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Definition::Expandable.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Number.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Definition::Register.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Color::hsb.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Error.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Definition::Constructor.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Package.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Color::gray.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Util::Pack.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Color::cmy.3pm
Installing /<>/debian/latexml/usr/share/man/man3/LaTeXML::Post.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Font.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Parameter.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Array.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::Definition.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Model::DTD.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Core::State.3pm
Installing /<>/debian/latexml/usr/share/man/man3/LaTeXML::Core.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Pre::BibTeX.3pm
Installing 
/<>/debian/latexml/usr/share/man/man3/LaTeXML::Common::Color.3pm
Installing /<>/debian/latexml/usr/bin/latexmlfind
Installing /<>/debian/latexml/usr/bin/latexmlpost
Installing /<>/debian/latexml/usr/bin/latexmlc
Installing /<>/debian/latexml/usr/bin/latexml
Installing /<>/debian/latexml/usr/bin/latexmlmath
Installing 
/<>/debian/latexml/usr/share/texmf/tex/latex/latexml/latexml.sty
Installing 
/<>/debian/latexml/usr/share/texmf/tex/latex/latexml/lxRDFa.sty
make[1]: Leaving directory '/<>'
# install documentation file
mkdir -p debian/latexml/usr/share/texmf/doc/latexml
cp manual.pdf debian/latexml/usr/share/texmf/doc/latexml/
find debian/latexml -type f -name .packlist | xargs rm -f
dh_testdir
dh_testroot
dh_installchangelogs
dh_installdocs
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:43: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/latexml.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903349: codespell: FTBFS in buster/sid (dh_installdocs: Cannot find "NEWS")

2018-07-08 Thread Santiago Vila
Package: src:codespell
Version: 1.13.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3 --parallel --buildsystem=pybuild
   dh_update_autotools_config -i -O--parallel -O--buildsystem=pybuild
   dh_autoreconf -i -O--parallel -O--buildsystem=pybuild
   dh_auto_configure -i -O--parallel -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
sed -i -e "s|python3|python2|g" ./bin/codespell
make codespell.1
make[2]: Entering directory '/<>'
PYTHONPATH=. help2man ./bin/codespell --include codespell.1.include --no-info 
--output codespell.1
sed -i '/\.SS \"Usage/,+2d' codespell.1

[... snipped ...]

   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --with python3 --parallel --buildsystem=pybuild
   dh_testroot -i -O--parallel -O--buildsystem=pybuild
   dh_prep -i -O--parallel -O--buildsystem=pybuild
   dh_auto_install -i -O--parallel -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py install --root 
/<>/debian/codespell 
running install
running build
running build_py
running egg_info
writing codespell.egg-info/PKG-INFO
writing dependency_links to codespell.egg-info/dependency_links.txt
writing entry points to codespell.egg-info/entry_points.txt
writing top-level names to codespell.egg-info/top_level.txt
reading manifest file 'codespell.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'codespell.egg-info/SOURCES.txt'
running install_lib
creating /<>/debian/codespell/usr
creating /<>/debian/codespell/usr/lib
creating /<>/debian/codespell/usr/lib/python3.6
creating /<>/debian/codespell/usr/lib/python3.6/dist-packages
creating 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib
creating 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data
copying 
/<>/.pybuild/cpython3_3.6/build/codespell_lib/data/linux-kernel.exclude
 -> 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data
copying 
/<>/.pybuild/cpython3_3.6/build/codespell_lib/data/dictionary.txt 
-> 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data
copying 
/<>/.pybuild/cpython3_3.6/build/codespell_lib/data/__init__.py -> 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data
copying /<>/.pybuild/cpython3_3.6/build/codespell_lib/__init__.py 
-> 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib
creating 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests
copying 
/<>/.pybuild/cpython3_3.6/build/codespell_lib/tests/__init__.py -> 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests
copying 
/<>/.pybuild/cpython3_3.6/build/codespell_lib/tests/test_basic.py 
-> 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests
copying 
/<>/.pybuild/cpython3_3.6/build/codespell_lib/_codespell.py -> 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib
byte-compiling 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/data/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/tests/test_basic.py
 to test_basic.cpython-36.pyc
byte-compiling 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell_lib/_codespell.py
 to _codespell.cpython-36.pyc
running install_egg_info
Copying codespell.egg-info to 
/<>/debian/codespell/usr/lib/python3.6/dist-packages/codespell-1.13.0.egg-info
Skipping SOURCES.txt
running install_scripts
Installing codespell script to /<>/debian/codespell/usr/bin
   dh_installdocs -i -O--parallel -O--buildsystem=pybuild
dh_installdocs: Cannot find (any matches for) "NEWS" (tried in .)

debian/rules:4: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/codespell.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903104: [Pkg-mailman-hackers] Bug#903104: Bug#903104: Configuration of base url

2018-07-08 Thread Pierre-Elliott Bécue
Le dimanche 08 juillet 2018 à 13:03:06+0200, bgr...@toplitzer.net a écrit :
> > > 
> > >  2. setting the ROOT_URLCONF = 'urls2' in the /etc/mailman3/mailman-web.py
> > >  
> > > or /usr/share/mailman3-web/settings.py
> > > and adding a link in /usr/share/mailman3-web/urls2.py to
> > > file /etc/mailman3/mailman-web.urls2.py
> > > 
> > > containing:
> > > ==
> > > from django.conf.urls import include, url
> > > from django.contrib import admin
> > > from django.core.urlresolvers import reverse_lazy
> > > from django.views.generic import RedirectView
> > > 
> > > urlpatterns = [
> > > 
> > > url(r'^', include('urls')),
> > > 
> > > ]
> > > =
> > > 
> > 
> > Can you give me a little more intel on what you'd like to achieve by
> > modifying/allowing modifications of the urls set of the application?
> > 
> > Mind that adding such feature means allowing the shared memory of the django
> > app to be accessed by non-upstream code. Should a user badly implement
> > features, this could possibly compromise all his mailman3 setup. I'm not
> > sure it's a sane thing to do, but I'm not opposed to it either.
> > 
> > So, let's discuss, think, and we'll try to find an appropriate solution that
> > pleases anyone but does not compromise the app stability.
> 
> I just don't want to expose mailman on the default URL, similar as
> other sites like 
> https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ do.
> 
> If there is an other simple method to achieve this I'm happy too.
> 
> Thank you for you question!
> Cheers!

Via the webserver, without any trouble. :)

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature


Bug#903348: libvirt-daemon-system: libvirt-guests.sh service can't connect on system shutdown when using polkit access driver

2018-07-08 Thread Fabricio
Package: libvirt-daemon-system
Version: 3.0.0-4+deb9u3
Severity: normal

Dear Maintainer,

libvirt-guests service can't connect to qemu:///system on system shutdown when
using polkit auth_driver.

Steps to reproduce:

1 - Activate polkit access driver (access_drivers = [ "polkit" ]
[/etc/libvirt/libvirtd.conf])

2 - Do the apropriate configuration (.pkla files, as debian still uses 1.05)

3 - Shutdown the system. Service libvirt-guests reports: "Unable to connect to
libvirt currently. Retrying .."

Related libvirt log message:

2018-07-08 20:44:28.092+: 867: info : virDBusCall:1548 : DBUS_METHOD_CALL:
'org.freedesktop.PolicyKit1.Authority.CheckAuthorization' on
'/org/freedesktop/PolicyKit1/Authority' at 'org.freedesktop.PolicyKit1'
2018-07-08 20:44:28.092+: 867: info : virDBusCall:1558 : DBUS_METHOD_ERROR:
'org.freedesktop.PolicyKit1.Authority.CheckAuthorization' on
'/org/freedesktop/PolicyKit1/Authority' at 'org.freedesktop.PolicyKit1' error
org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting
down.
2018-07-08 20:44:28.092+: 867: error : virDBusCall:1570 : error from
service: CheckAuthorization: Refusing activation, D-Bus is shutting down.


From the libvirt's log messages i have found that it seems polkitd services
stops before libvirt-guests shutdown. So, adding the following line to the unit
section in/lib/systemd/system/libvirt-guests.services solved the problem:

After=polkit.service

Ragards



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

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

Versions of packages libvirt-daemon-system depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
ii  gettext-base   0.19.8.1-2
ii  init-system-helpers1.48
ii  iptables   1.6.0+snapshot20161117-6
ii  libapparmor1   2.11.0-3+deb9u2
ii  libaudit1  1:2.6.7-2
ii  libblkid1  2.29.2-1+deb9u1
ii  libc6  2.24-11+deb9u3
ii  libcap-ng0 0.7.7-3+b1
ii  libdbus-1-31.10.26-0+deb9u1
ii  libdevmapper1.02.1 2:1.02.137-2
ii  libnl-3-2003.2.27-2
ii  libnl-route-3-200  3.2.27-2
ii  libnuma1   2.0.11-2.1
ii  librados2  10.2.5-7.2
ii  librbd110.2.5-7.2
ii  libselinux12.6-3+b3
ii  libvirt-clients3.0.0-4+deb9u3
ii  libvirt-daemon 3.0.0-4+deb9u3
ii  libvirt0   3.0.0-4+deb9u3
ii  libxml22.9.4+dfsg1-2.2+deb9u2
ii  libyajl2   2.1.0-2+b3
ii  logrotate  3.11.0-0.1
ii  lsb-base   9.20161125
ii  policykit-10.105-18

Versions of packages libvirt-daemon-system recommends:
ii  bridge-utils  1.5-13+deb9u1
ii  dmidecode 3.0-4
ii  dnsmasq-base  2.76-5+deb9u1
ii  ebtables  2.0.10.4-3.5+b1
ii  iproute2  4.9.0-1+deb9u1
ii  parted3.2-17

Versions of packages libvirt-daemon-system suggests:
ii  apparmor2.11.0-3+deb9u2
pn  auditd  
pn  nfs-common  
pn  pm-utils
pn  radvd   
ii  systemd 232-25+deb9u3
pn  systemtap   
pn  zfsutils

-- Configuration Files:
/etc/libvirt/libvirtd.conf changed [not included]
/etc/libvirt/nwfilter/allow-arp.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/allow-arp.xml'
/etc/libvirt/nwfilter/allow-dhcp-server.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/allow-dhcp-server.xml'
/etc/libvirt/nwfilter/allow-dhcp.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/allow-dhcp.xml'
/etc/libvirt/nwfilter/allow-incoming-ipv4.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'
/etc/libvirt/nwfilter/allow-ipv4.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/allow-ipv4.xml'
/etc/libvirt/nwfilter/clean-traffic.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/clean-traffic.xml'
/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-spoofing.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/no-arp-spoofing.xml'
/etc/libvirt/nwfilter/no-ip-multicast.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/no-ip-multicast.xml'
/etc/libvirt/nwfilter/no-ip-spoofing.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/no-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-mac-broadcast.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/no-mac-broadcast.xml'
/etc/libvirt/nwfilter/no-mac-spoofing.xml [Errno 13] Permissão negada: 
'/etc/libvirt/nwfilter/no-mac-spoofing.xml'

Bug#902174: #902174: RFP: mes

2018-07-08 Thread Vagrant Cascadian
On 2018-07-08, Jan Nieuwenhuizen wrote:
> Vagrant Cascadian writes:
>
> @Matt: some Nyacc patches attached.
>
>>> I took a quick stab at this, and it first requires packaging:
...
>> Packaging branch for nyacc:
>>
>>   https://salsa.debian.org/vagrant/nyacc
>>
>> Fails to build as it installs info pages to /share/info. Doesn't appear
>> to respect DESTDIR= ... but setting --infodir doesn't work as I would
>> expect either, suddently appending --prefix to it.
>
> I have looked into this; please see `debian' branch at
>
> http://gitlab.com/janneke/nyacc

Thanks!


> I have created patches for Nyacc to aid Debian packaging; see attached.
> They are on my debian branch, as well as on my master.  I also made some
> WIP changes to the debian packaging: most notably: I could not find
> guile-2.2.

guile-2.2 is in Debian testing and unstable, though guile-2.0 is in
stable, testing and unstable. For upload to Debian, it would probably be
best to use the newest guile version available, unless there's a
compelling reason to use guile-2.0, or possibly work the package to
support both guile-2.2 and guile-2.0.


>> And also a packaging branch for mes itself, but of course can't test it
>> until nyacc is working:
>>
>>   https://salsa.debian.org/vagrant/mes
>
> I will have a look at this later.  You will probably want to rebase on
> my `wip-gnu' branch: it has (experimental) DESTDIR and other Debian
> build support (e.g.: do not assume /bin/sh is bash, resurrect guile-2.0).

Will take a look, thanks!


live well,
  vagrant


signature.asc
Description: PGP signature


Bug#899189: nmu: unison_2.48.3-1

2018-07-08 Thread Adam D. Barratt
On Fri, 2018-07-06 at 03:15 +0200, Cyril Brulebois wrote:
> Hey again,
> 
> Cyril Brulebois  (2018-07-06):
> > For the sake of completeness, here's an extra data point. If
> > someone
> > ends up with two peers with versions 2.48.3-1 vs. 2.48.3-1+b1
> > (hosts
> > with s-p-u enabled, but not dist-upgraded at the same time), one
> > can
> > get this very issue:
> > > Uncaught exception Failure("input_value: bad bigarray kind")
> > 
> > with extra unfriendly debug messages (hey, look at those in the
> > github
> > bug tracker, the ones we wanted to get rid of).
> > 
> > I thought I'd mention the possibly surprising outcome for people
> > not
> > following debian-release@ closely.
> 
> Also, that seems to completely invalidate the on-disk cache, which is
> likely the reason why the first run with an upgraded version (on
> either
> side, by the way) can take several (dozens of) minutes instead of a
> couple of seconds.
> 
> It might have been a good idea to mention that in the binNMU request.
> It might also be a good idea to document those consequences in some
> way.
> 

Stéphane, any comments on this?

Regards,

Adam



Bug#902703: Acknowledgement (RFS: hw-probe/1.4-4-git20180614 [ITP])

2018-07-08 Thread Михаил Новоселов

To build it:

dget -x 
https://mentors.debian.net/debian/pool/main/h/hw-probe/hw-probe_1.4-5-git20180614.dsc

git init
git clone ./hw-probe_1.4-5-git20180614.dsc master
cd master
sudo mk-build-deps --install debian/control
dpkg-buildpackage



Bug#902700: Info received (Bug#902700: Acknowledgement (RFS: pulseeffects/4.1.1))

2018-07-08 Thread Михаил Новоселов
Oh, I completely forgot, that PulseEffects needs calf-plugins >= 0.90.0 
(https://github.com/wwmm/pulseeffects/issues/227), while is's still 
0.0.60 in Debian Sid.


I also package calf-plugins 0.90.0 in my Ubuntu PPA 
ppa:mikhailnov/pulseeffects 
https://launchpad.net/~mikhailnov/+archive/ubuntu/pulseeffects . The 
problem is that it's buildable only for i386 and x86_64 and is not 
buildable for arm, powerpc and other architectures.


My build is here: https://mentors.debian.net/package/calf . It's based 
on Deepin's package (dget -x 
https://mentors.debian.net/debian/pool/main/c/calf/calf_0.90.0-2.dsc)


I CCed pkg-multimedia-maintain...@lists.alioth.debian.org to this email 
because probably you can help to solve the problem and have a look at 
updating calf-plugins 0.0.60 --> 0.90.0 in Debian, at least for i386 and 
x86_64.


Thank you.



Bug#902174: #902174: RFP: mes

2018-07-08 Thread Matt Wette

On 07/08/2018 03:47 AM, Jan Nieuwenhuizen wrote:

Vagrant Cascadian writes:

@Matt: some Nyacc patches attached.


I took a quick stab at this, and it first requires packaging:

   https://github.com/oriansj/mescc-tools

Packaging branch for mescc-tools:

   https://salsa.debian.org/vagrant/mescc-tools

Compiles, maybe it even works!

Wow, thanks!


   https://gitlab.com/janneke/nyacc

Packaging branch for nyacc:

   https://salsa.debian.org/vagrant/nyacc

Fails to build as it installs info pages to /share/info. Doesn't appear
to respect DESTDIR= ... but setting --infodir doesn't work as I would
expect either, suddently appending --prefix to it.

I have looked into this; please see `debian' branch at

 http://gitlab.com/janneke/nyacc

I have created patches for Nyacc to aid Debian packaging; see attached.
They are on my debian branch, as well as on my master.  I also made some
WIP changes to the debian packaging: most notably: I could not find
guile-2.2.


And also a packaging branch for mes itself, but of course can't test it
until nyacc is working:

   https://salsa.debian.org/vagrant/mes

I will have a look at this later.  You will probably want to rebase on
my `wip-gnu' branch: it has (experimental) DESTDIR and other Debian
build support (e.g.: do not assume /bin/sh is bash, resurrect guile-2.0).

Greetings,
janneke




I don't understand why `eval' is needed, esp when forcing the shell to 
be bash.

Is there any reference to this usage?

Matt



Bug#903347: libnlopt-cxx-dev: missing dependency on libnlopt-cxx0 (= ${binary:Version})

2018-07-08 Thread Adrian Bunk
Package: libnlopt-cxx-dev
Version: 2.4.2+dfsg-5
Severity: serious

This makes /usr/lib/x86_64-linux-gnu/libnlopt_cxx.so a dangling
symlink, resulting in users silently using the static library instead.



Bug#903279: meson removed debcrossgen

2018-07-08 Thread Jussi Pakkanen
On Sun, Jul 8, 2018 at 3:23 PM, Helmut Grohne  wrote:

> The changelog does not give a reason for why this happened, which
> suggests that this may be accidental. Please add it back where debhelper
> expects it.
>
> Given the amount of packages that depend on meson, please fix this in a
> timely manner (a few days).

Crap, this was accidentally lost due to installation command rewrtie.
We will have a bugfix point release tomorrow, this will be fixed in
that upload.



Bug#903219: Acknowledgement (journald crashes)

2018-07-08 Thread Yuri D'Elia
After further debugging I figured this seems to be related to the
internal watchdog. I filed a bug report upstream:

https://github.com/systemd/systemd/issues/9538



Bug#903346: RFS: gcstar/1.7.1+repack-2

2018-07-08 Thread Jörg Frings-Fürst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

   Package name: gcstar
   Version : 1.7.1+repack-2
   Upstream Author : Tian 
   URL : http://www.gcstar.org/
   License : GPL-2+, Expat
   Section : x11

It builds those binary packages:

gcstar - Manage your collections of movies, games, books, 
 music and more

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/g/gcstar/gcstar_1.7.1+repack-2.dsc

 
  Changes since the last upload:

  * debian/control:
- Switch Vcs-* to new loacation.
  * Change to my new mail address.
  * Declare compliance with Debian Policy 4.1.5 (no changes required).
  * Migrate to debhelper 11:
- Change debian/compat to 11.
- Bump minimum debhelper version in debian/control to >= 11.
  * Remove trailing whitespaces from
- debian/changelog
- debian/control
- debian/rules
  * debian/copyright:
- Use secure URI for the copyright format.
- Add year 2018 for packaging.
  * Add missing perl module to Depends (Closes: #892568, #903298):
- libdate-calc-perl
- libgd-graph-perl
- libgd-text-perl
- liblocale-codes-perl
  * New README.source to explain the branching model used.


Regards,
   Jörg Frings-Fürst

- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltCe/kACgkQCfifPIyh
0l0h2Q/9FayHlNd2PzbaIxpbQvSaCxd3Rz1WIvqgOAga0sxYaFMTyviIyzutrks7
2mRHOCgm/FFYUiy9ZpfHPu0lx5iEdD6684EtMRfPcDXx1sLOZaD/M/1pKLhcJI0W
EVWL89wvrIeV0eKItGZbAKZy/bU+Mml2b1MhAxIPqtXje6Ue+0M7Y12MdvdhNfeB
E2RFO9/W5/EdDtF5YQc/nj7aiPpwfP7SDwjV9cGr4oaz7zyNt45Gmu0cINSkxYY/
xQQMx3/Yxl+dxWKf6nd/9koDOzVtVTeJGQBjMYACASY1vnhst+RCH/fxnMDRAhlu
VN21ntCyIowzD2Tiyd2AGRcWt1K8Y2TKKT8SlkO9B6A9UfVEbLN00aWKMsdulWtn
6pES+BFoHUqVjpOItP9cQ3zng01OWCkzwY/474eCkVYUny0cNDU9nOATtRHk9KH5
ZmDPegOgM1nPvS1Ugboz7vikPuKUR1IXslljKCGseSgjIFfcIXPUkT7es9nU6mNV
+wdD41Qc3/RMMRmg8L3e4+X6ICZHHTjh4hjq9/qJU5b1GmMLoCkp7GRfsurOEJx5
ZlLcJZS3sAGTjLarKzLdvxR6+M0geu6uChFIQH3MaZilAzQu2SqDVntal/Sis4sp
4cvUW6SKCahFmi8uB1f/EptaGf+SgBN+U1ntZoxbuPxr7nT73MQ=
=BC/Z
-END PGP SIGNATURE-



Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)

2018-07-08 Thread Steven R. Wright
I am not claiming that things aren't going to break, since as unstable 
users we are functioning as beta testers, which is understood, but when 
a significantly critical bug is identified, there is no logical reason 
to continue to pass it around.  I've been using the unstable branch 
since the 1990s and this has usually what i have seen -- save in rare 
cases -- when fixes are not able to be included in a timely manner.  
Obviously I merely downgraded to the last functioning version of 
virtualbox et. al. (5.2.12-dfsg-3) in unstable but since 5.2.14-dfsg-1 
is a known NBG, there is little (or actually no) motivation for it to be 
in the repos.

On 07/08/18 15:23, Evgeny Kapun wrote:

On 08.07.2018 22:54, Steven R. Wright wrote:
This is a critical enough bug to warrant removing 5.2.14-dfsg-1 from 
the repos.  I have to do selective upgrades now to avoid pulling it in.


Unstable repo is called unstable for a reason. If you want a system 
that doesn't break, use stable (you can install VirtualBox from 
backports) or testing.






Bug#903345: ITP: python-seqcluster -- analysis of small RNA in NGS data

2018-07-08 Thread Steffen Moeller
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller 

* Package name: python-seqcluster
* URL : https://github.com/lpantano/seqcluster
* License : MIT
  Programming Lang: Python
  Description : analysis of small RNA in NGS data

About to appear at https://salsa.debian.org/med-team/python-seqcluster



Bug#903135: intel-microcode: Kabby Lake microcode rev 0x84 instead of rev 0x8e

2018-07-08 Thread Henrique de Moraes Holschuh
On Fri, 06 Jul 2018, Matt Stamp wrote:
> After applying an update to my UEFI/BIOS my microcode is rev 0x8e.  A
> package seperate for your, needrestart said that the available
> microcode did not match my currently applied version 0x84.  Though
> even after the recent update from Intel I am still getting that
> message.

That's a limitation in the needsrestart logic, which isn't easy to fix
at all.  The kernel doesn't help (it doesn't tell you the BIOS microcode
revision on Intel, only the current revision), and Intel doesn't help
(they sometimes downgrade or recall microcode updates so you can't
assume it will just go up on intel-microcode updates), so it can't do a
perfect job.

Maybe it can be improved, but that would be something to explore in a
bug report against needrestart, not intel-microcode.

> Is this correct?  Is the revision in intel-microcode-3.20180703.2 for
> Kabby Lake really 0x84?  According to some of my reading Intel

Yes, it is really 0x84, unfortunately(?)

This information can be found in /usr/share/doc/intel-microcode/
changelog.gz, although it can be a bit cryptic unless you've read the
README or tried running "iucode_tool -Sv" to know your processor's
signature.

> released the 0x8e version and so I thought it would be included in
> their recent release.

We wish.  No, it isn't.  From the Debian changelog of intel-microcode:

--8<--
+ First batch of fixes for: Intel SA-00115, CVE-2018-3639, CVE-2018-3640
+ SSBD support (Spectre-v4 mitigation) and fix Spectre-v3a for:
  Sandybridge server, Ivy Bridge server, Haswell server, Skylake server,
  Broadwell server, a few HEDT Core i7/i9 models that are actually gimped
  server dies.
--8<--

As you can see, the vast majority of the processors affected, Kaby lake
included, are still missing in the public update release of 2018-07-03.

> If this is some issue with the needrestart package or perl within than
> no big deal and please feel free to close this ticket.

I will close the bug report when we get a Kabi Lake update with revision
0x8e or higher.

If you want to ask the needrestart package to improve their detection,
please open a bug against that package.  I am not sure much can be done
on that regard without kernel changes, though.

-- 
  Henrique Holschuh



Bug#902700: Acknowledgement (RFS: pulseeffects/4.1.1)

2018-07-08 Thread Михаил Новоселов

Hello,

I updated PulseEffects to version 4.1.3. You can get and build it as:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pulseeffects/pulseeffects_4.1.3-1.dsc

git init
git clone ./pulseeffects_4.1.3-1.git master
cd master
sudo mk-build-deps --install debian/control
dpkg-buildpackage

Please answer something...



Bug#903002: mc reset confuses ipmievd

2018-07-08 Thread Sergio Gelato
* Jörg Frings-Fürst [2018-07-08 08:38:55 +0200]:
> Can you please file a bug report to the upstream author[1] ?

I'd much prefer that someone else do it. Among other reasons,
https://www.debian.org/Bugs/Reporting says "If necessary, the maintainer
of the package will forward the bug upstream."

Instead, I'll provide additional information here, in the form of partial
output of ipmievd -v -v -v sel nodaemon. Additional comments at the end.

[...]
Sensors cached
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x40
SEL count is 40
SEL freespace is 384
SEL Percent Used: 62%

SEL Overflow: false
Current SEL count is 40
[...]
SEL Next ID: 0028
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x43
OpenIPMI Request Message Data (6 bytes)
 00 00 28 00 00 ff
SEL Entry: 2800022f55425b24083b0b01
SEL lastid is 0028
Current SEL lastid is 0028
Waiting for events...
[...][ipmitool mc reset warm][...]
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x40
SEL count is 41
SEL freespace is 368
SEL Percent Used: 64%

SEL Overflow: false
New Events
SEL Read ID: 0028
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x43
OpenIPMI Request Message Data (6 bytes)
 00 00 28 00 00 ff
SEL Entry: 0070018e58425b0bdbf25202
SEL Read ID: 2951
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x43
OpenIPMI Request Message Data (6 bytes)
 00 00 51 29 00 ff
SEL Entry: 2800022f55425b24083b0b01
Power Supply sensor Power Supplies Redundancy Lost Asserted
SEL Read ID: 0029
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x43
OpenIPMI Request Message Data (6 bytes)
 00 00 29 00 00 ff
Get SEL Entry 29 command failed: Requested sensor, data, or record not found
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x43
OpenIPMI Request Message Data (6 bytes)
 00 00 29 00 00 ff
SEL Entry: 2900028e58425b24083b0b01
Power Supply sensor Power Supplies Redundancy Lost Asserted
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x40
SEL count is 10751
SEL freespace is 512
SEL Percent Used: 98%

SEL Overflow: false
SEL buffer is 98% full, please consider clearing the SEL buffer
New Events
SEL Read ID: 0029
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x43
OpenIPMI Request Message Data (6 bytes)
 00 00 29 00 00 ff
SEL Entry: 0070018e58425b0bdbf25202
SEL Read ID: 2951
OpenIPMI Request Message Header:
  netfn = 0xa
  cmd   = 0x43
OpenIPMI Request Message Data (6 bytes)
 00 00 51 29 00 ff
[...]

This looks to me like a loss of synchronisation between requests and
responses. 2951 looks like a plausible start for a "Get SEL Info" response.



Bug#902700: Acknowledgement (RFS: pulseeffects/4.1.1)

2018-07-08 Thread Михаил Новоселов

Hello,

I updated PulseEffects to version 4.1.3. You can get and build it as:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pulseeffects/pulseeffects_4.1.3-1.dsc

git init
git clone ./pulseeffects_4.1.3-1.git master
cd master
sudo mk-build-deps --install debian/control
dpkg-buildpackage

Please answer something...



Bug#903333: jpy: FTBFS in buster/sid (dh_installdocs: Cannot find "README.rst")

2018-07-08 Thread Santiago Vila
Package: src:jpy
Version: 0.9.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
dh build-arch --with python2,python3
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
dh_auto_build

[... snipped ...]

INFO: jpy Java API configuration written to 
'/<>/build/lib.linux-x86_64-2.7/jpyconfig.properties'
INFO: Configuration completed successfully
running install_lib
Writing jpy configuration to build/lib.linux-x86_64-2.7 using install_dir 
/<>/debian/tmp/usr/lib/python2.7/dist-packages/
INFO: jpy Python API configuration written to 
'/<>/build/lib.linux-x86_64-2.7/jpyconfig.py'
DEBUG: Searching for Python shared library file
DEBUG: Potential Python shared library search dirs: 
['/usr/lib/x86_64-linux-gnu', '/usr', '..', '/usr/bin', '/usr/lib/python2.7', 
'/usr/lib/python2.7/lib-dynload', '/usr/lib']
DEBUG: Potential Python shared library file names: ['libpython2.7.so', 
'libpython2.so', 'libpython.so']
DEBUG: Exists '/usr/lib/x86_64-linux-gnu/libpython2.7.so'? yes
INFO: jpy Java API configuration written to 
'/<>/build/lib.linux-x86_64-2.7/jpyconfig.properties'
INFO: Configuration completed successfully
copying build/lib.linux-x86_64-2.7/jpyconfig.properties -> 
/<>/debian/tmp/usr/lib/python2.7/dist-packages
copying build/lib.linux-x86_64-2.7/jpyutil.py -> 
/<>/debian/tmp/usr/lib/python2.7/dist-packages
copying build/lib.linux-x86_64-2.7/jdl.so -> 
/<>/debian/tmp/usr/lib/python2.7/dist-packages
copying build/lib.linux-x86_64-2.7/jpyconfig.py -> 
/<>/debian/tmp/usr/lib/python2.7/dist-packages
copying build/lib.linux-x86_64-2.7/jpy.so -> 
/<>/debian/tmp/usr/lib/python2.7/dist-packages
copying build/lib.linux-x86_64-2.7/jpyutil.pyc -> 
/<>/debian/tmp/usr/lib/python2.7/dist-packages
running install_egg_info
running egg_info
writing jpy.egg-info/PKG-INFO
writing top-level names to jpy.egg-info/top_level.txt
writing dependency_links to jpy.egg-info/dependency_links.txt
reading manifest file 'jpy.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'lib/*.jar'
writing manifest file 'jpy.egg-info/SOURCES.txt'
removing 
'/<>/debian/tmp/usr/lib/python2.7/dist-packages/jpy-0.9.0.egg-info'
 (and everything under it)
Copying jpy.egg-info to 
/<>/debian/tmp/usr/lib/python2.7/dist-packages/jpy-0.9.0.egg-info
Skipping SOURCES.txt
running install_scripts
writing list of installed files to 'setup.out'
find . -name '*.so' -exec chrpath -d {} \;
# Strip build path; the libs will exist under /usr, not debian/tmp
find . -name 'jpyconfig.properties' -exec sed -i -e 
's,/<>/debian/tmp,,g' {} \;
make[1]: Leaving directory '/<>'
   dh_install -a
install -d debian/python-jpy//usr/lib
cp --reflink=auto -a debian/tmp/usr/lib/python2.7 
debian/python-jpy//usr/lib/
install -d debian/.debhelper/generated/python-jpy
install -d debian/python3-jpy//usr/lib
cp --reflink=auto -a debian/tmp/usr/lib/python3 
debian/python3-jpy//usr/lib/
install -d debian/.debhelper/generated/python3-jpy
   dh_installdocs -a
dh_installdocs: Cannot find (any matches for) "README.rst" (tried in .)

install -d debian/python-jpy/usr/share/doc/python-jpy
debian/rules:10: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jpy.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#895596: stretch-pu: package xrdp/0.9.1-9+deb9u2

2018-07-08 Thread Dominik George
Hi,

> Note that the uploading window for 9.5 is closing this weekend, so I
> took the liberty to build and upload with your debdiff. Hope this if
> fine with you otherwise I will ask Adam to reject my upload!

Oh thanks!

We had a work meeting of Teckids, the Free software (and mostly Debian)
youth organisation all the weekend, so I missed that.

Thanks a lot for tkaing care of that!

Cheers,
Nik


signature.asc
Description: PGP signature


Bug#903342: sshfs-fuse: FTBFS in buster/sid (dh_installdocs: Cannot find "FAQ")

2018-07-08 Thread Santiago Vila
Package: src:sshfs-fuse
Version: 2.10-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --with autoreconf
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
./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: WARNING: unrecognized options: --disable-maintainer-mode
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no

[... snipped ...]

<./sshfs.1.in >sshfs.1.tmp || exit 1; \
mv sshfs.1.tmp sshfs.1
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test -a
make -j1 check VERBOSE=1
make[1]: Entering directory '/<>'
Making check in test
make[2]: Entering directory '/<>/test'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/<>/test'
make[2]: Entering directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
 fakeroot debian/rules binary-arch
dh binary-arch --with autoreconf
   dh_testroot -a
   dh_prep -a
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
/usr/bin/make install DESTDIR=/<>/debian/sshfs
make[2]: Entering directory '/<>'
Making install in test
make[3]: Entering directory '/<>/test'
make[4]: Entering directory '/<>/test'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/test'
make[3]: Leaving directory '/<>/test'
make[3]: Entering directory '/<>'
make[4]: Entering directory '/<>'
 /bin/mkdir -p '/<>/debian/sshfs/usr/bin'
  /usr/bin/install -c sshfs '/<>/debian/sshfs/usr/bin'
 /bin/mkdir -p '/<>/debian/sshfs/usr/share/man/man1'
 /usr/bin/install -c -m 644 sshfs.1 
'/<>/debian/sshfs/usr/share/man/man1'
make[4]: Leaving directory '/<>'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_install -a
   dh_installdocs -a
dh_installdocs: Cannot find (any matches for) "README*" (tried in .)

dh_installdocs: Cannot find (any matches for) "FAQ" (tried in .)

debian/rules:6: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sshfs-fuse.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903341: ruby-rubymail: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:ruby-rubymail
Version: 1.1.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_ruby --build
   dh_ruby --build
rake rdoc
Parsing sources...
  5% [ 1/19]  ChangeLog
 10% [ 2/19]  README.md

[... snipped ...]

test_transparency_absolute_05:  .: (0.000842)
test_transparency_absolute_06:  .: (0.002141)
test_transparency_message_01:   .: (0.001448)
test_transparency_message_02:   .: (0.001710)
test_transparency_message_03:   .: (0.001168)
test_transparency_message_04:   .: (0.000559)
test_transparency_message_05:   .: (0.000655)
test_transparency_message_06:   .: (0.001684)
test_transparency_nested_multipart: .: (0.001611)
test_transparency_rfc822:   .: (0.001081)
test_transparency_simple_mime:  .: (0.001027)
  TestTestBase: 
test_cleandir:  .: (0.000897)
test_file_contains: .: (0.000511)
test_name:  .: (0.000259)
test_ruby_program:  .: (0.000272)
test_scratch_dir:   .: (0.000263)
test_scratch_filename:  .: (0.000313)
test_string_as_file:.: (0.000787)
  TextRMailMBoxReader: 
test_mbox_chunksize:.: (0.012013)
test_mbox_odd:  .: (0.000415)
test_mbox_randomly: .: (0.086029)
test_mbox_s_new:.: (0.000324)
test_mbox_simple:   .: (0.000422)
  TextRMailParserPushbackReader: 
test_pushback:  .: (0.000352)

Finished in 0.727013135 seconds.
---
168 tests, 24214 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
100% passed
---
231.08 tests/s, 33306.14 assertions/s

┌──────────────────────────────────────────────────────────────────────────────┐
│ dh_ruby --install finished  
 │
└──────────────────────────────────────────────────────────────────────────────┘

# Remove script files from ruby-rubymail-doc
rm -rf /<>/debian/ruby-rubymail-doc/usr/lib
make[1]: Leaving directory '/<>'
   dh_install -i -O--buildsystem=ruby
   dh_installdocs -i -O--buildsystem=ruby
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rubymail.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903344: wxglade: FTBFS in buster/sid (dh_installdocs: Cannot find "TODO.txt")

2018-07-08 Thread Santiago Vila
Package: src:wxglade
Version: 0.8.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
echo "not running the tests since the test tests/test_gui.py will fail"
not running the tests since the test tests/test_gui.py will fail
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --with python2
   dh_testroot -i
   dh_prep -i
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
ln -s underscore-1.3.1.js docs/html/_static/underscore.js
ln -s jquery-3.1.0.js docs/html/_static/jquery.js
echo "__version__ = '0.8.0'" > /<>/version.py
dh_auto_install
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "TODO.txt" (tried in .)

debian/rules:16: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/wxglade.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903334: libtomcrypt: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:libtomcrypt
Version: 1.18.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --parallel
   dh_update_autotools_config -a -O--parallel
   dh_auto_configure -a -O--parallel
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make V=1 docs
make[2]: Entering directory '/<>'
/usr/bin/make -C doc/ docs V=1
make[3]: Entering directory '/<>/doc'
rm -f crypt.pdf *.dvi *.log *.aux *.toc *.idx *.ilg *.ind *.out *.lof
cp crypt.tex crypt.bak
touch -r crypt.tex crypt.bak
(printf "%s" "\def\fixedpdfdate{"; date +'D:%Y%m%d%H%M%S%:z' -d @$(stat 
--format=%Y crypt.tex) | sed "s/:\([0-9][0-9]\)$/'\1'}/g") > 
crypt-deterministic.tex

[... snipped ...]

libtool --mode=compile --tag=CC gcc -I./src/headers/ -Wall -Wsign-compare 
-Wshadow -DLTC_SOURCE -Wextra -Wsystem-headers -Wbad-function-cast -Wcast-align 
-Wstrict-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Wwrite-strings -Wno-type-limits -O3 -funroll-loops -fomit-frame-pointer 
-DGIT_VERSION=\"1.18.1\" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DGMP_DESC -DLTM_DESC 
-DUSE_LTM -Wdate-time -D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now -o 
src/stream/sober128/sober128_test.o -c src/stream/sober128/sober128_test.c
libtool: compile:  gcc -I./src/headers/ -Wall -Wsign-compare -Wshadow 
-DLTC_SOURCE -Wextra -Wsystem-headers -Wbad-function-cast -Wcast-align 
-Wstrict-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Wwrite-strings -Wno-type-limits -O3 -funroll-loops -fomit-frame-pointer 
-DGIT_VERSION=\"1.18.1\" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DGMP_DESC -DLTM_DESC 
-DUSE_LTM -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -c 
src/stream/sober128/sober128_test.c  -fPIC -DPIC -o 
src/stream/sober128/.libs/sober128_test.o
libtool: compile:  gcc -I./src/headers/ -Wall -Wsign-compare -Wshadow 
-DLTC_SOURCE -Wextra -Wsystem-headers -Wbad-function-cast -Wcast-align 
-Wstrict-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Wwrite-strings -Wno-type-limits -O3 -funroll-loops -fomit-frame-pointer 
-DGIT_VERSION=\"1.18.1\" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DGMP_DESC -DLTM_DESC 
-DUSE_LTM -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -c 
src/stream/sober128/sober128_test.c -o src/stream/sober128/sober128_test.o 
>/dev/null 2>&1
libtool --mode=link --tag=CC gcc -I./src/headers/ -Wall -Wsign-compare -Wshadow 
-DLTC_SOURCE -Wextra -Wsystem-headers -Wbad-function-cast -Wcast-align 
-Wstrict-prototypes -Wpointer-arith -Wdeclaration-after-statement 
-Wwrite-strings -Wno-type-limits -O3 -funroll-loops -fomit-frame-pointer 
-DGIT_VERSION=\"1.18.1\" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DGMP_DESC -DLTM_DESC 
-DUSE_LTM -Wdate-time -D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now 
src/ciphers/aes/aes.lo src/ciphers/aes/aes_enc.lo src/ciphers/anubis.lo 
src/ciphers/blowfish.lo src/ciphers/camellia.lo src/ciphers/cast5.lo 
src/ciphers/des.lo src/ciphers/kasumi.lo src/ciphers/khazad.lo 
src/ciphers/kseed.lo src/ciphers/multi2.lo src/ciphers/noekeon.lo 
src/ciphers/rc2.lo src/ciphers/rc5.lo src/ciphers/rc6.lo 
src/ciphers/safer/safer.lo src/ciphers/safer/saferp.lo src/ciphers/skipjack.lo 
src/ciphers/twofish/twofish.lo src/ciphers/xtea.lo 
src/encauth/ccm/ccm_add_aad.lo src
 /encauth/ccm/ccm_add_nonce.lo src/encauth/ccm/ccm_done.lo 
src/encauth/ccm/ccm_init.lo src/encauth/ccm/ccm_memory.lo 
src/encauth/ccm/ccm_process.lo src/encauth/ccm/ccm_reset.lo 
src/encauth/ccm/ccm_test.lo src/encauth/chachapoly/chacha20poly1305_add_aad.lo 
src/encauth/chachapoly/chacha20poly1305_decrypt.lo 
src/encauth/chachapoly/chacha20poly1305_done.lo 
src/encauth/chachapoly/chacha20poly1305_encrypt.lo 
src/encauth/chachapoly/chacha20poly1305_init.lo 
src/encauth/chachapoly/chacha20poly1305_memory.lo 
src/encauth/chachapoly/chacha20poly1305_setiv.lo 
src/encauth/chachapoly/chacha20poly1305_setiv_rfc7905.lo 
src/encauth/chachapoly/chacha20poly1305_test.lo 
src/encauth/eax/eax_addheader.lo src/encauth/eax/eax_decrypt.lo 
src/encauth/eax/eax_decrypt_verify_memory.lo src/encauth/eax/eax_done.lo 
src/encauth/eax/eax_encrypt.lo 
src/encauth/eax/eax_encrypt_authenticate_memory.lo src/encauth/eax/eax_init.lo 
src/encauth/eax/eax_test.lo src/encauth/gcm/gcm_add_aad.lo 
src/encauth/gcm/gcm_add_iv.lo src/
 encauth/gcm/gcm_done.lo src/encauth/gcm/gcm_gf_mult.lo 
src/encauth/gcm/gcm_init.lo src/encauth/gcm/gcm_memory.lo 
src/encauth/gcm/gcm_mult_h.lo src/encauth/gcm/gcm_process.lo 
src/encauth/gcm/gcm_reset.lo src/encauth/gcm/gcm_test.lo 
src/encauth/ocb/ocb_decrypt.lo src/encauth/ocb/ocb_decrypt_verify_memory.lo 
src/encauth/ocb/ocb_done_decrypt.lo 

Bug#903339: pdf2djvu: FTBFS in buster/sid (dh_installdocs: Cannot find "doc/cjk.txt")

2018-07-08 Thread Santiago Vila
Package: src:pdf2djvu
Version: 0.9.9-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
Copying file ABOUT-NLS
Copying file tools/config.rpath
Copying file m4/codeset.m4
Copying file m4/glibc2.m4
Copying file m4/glibc21.m4
Copying file m4/iconv.m4
Copying file m4/intdiv0.m4
Copying file m4/intl.m4
Copying file m4/intldir.m4
Copying file m4/intmax.m4

[... snipped ...]


--
Ran 84 tests in 6.342s

OK (SKIP=1)
make[3]: Leaving directory '/<>/tests'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-arch
dh binary-arch
   dh_testroot -a
   dh_prep -a
   dh_auto_install -a
make -j1 install DESTDIR=/<>/debian/pdf2djvu 
AM_UPDATE_INFO_DIR=no
make[1]: Entering directory '/<>'
/usr/bin/install -c -d /<>/debian/pdf2djvu/usr/bin
/usr/bin/install -c pdf2djvu /<>/debian/pdf2djvu/usr/bin
INSTALL='/usr/bin/install -c' tools/install-manpages 
/<>/debian/pdf2djvu/usr/share/man doc/pdf2djvu.1 
doc/po/pdf2djvu.ru.1 doc/po/pdf2djvu.de.1 doc/po/pdf2djvu.pl.1 
doc/po/pdf2djvu.pt.1 doc/po/pdf2djvu.fr.1
$ /usr/bin/install -c -d /<>/debian/pdf2djvu/usr/share/man//man1
$ /usr/bin/install -c -m 644 doc/pdf2djvu.1 
/<>/debian/pdf2djvu/usr/share/man//man1/pdf2djvu.1
$ /usr/bin/install -c -d /<>/debian/pdf2djvu/usr/share/man/ru/man1
$ /usr/bin/install -c -m 644 doc/po/pdf2djvu.ru.1 
/<>/debian/pdf2djvu/usr/share/man/ru/man1/pdf2djvu.1
$ /usr/bin/install -c -d /<>/debian/pdf2djvu/usr/share/man/de/man1
$ /usr/bin/install -c -m 644 doc/po/pdf2djvu.de.1 
/<>/debian/pdf2djvu/usr/share/man/de/man1/pdf2djvu.1
$ /usr/bin/install -c -d /<>/debian/pdf2djvu/usr/share/man/pl/man1
$ /usr/bin/install -c -m 644 doc/po/pdf2djvu.pl.1 
/<>/debian/pdf2djvu/usr/share/man/pl/man1/pdf2djvu.1
$ /usr/bin/install -c -d /<>/debian/pdf2djvu/usr/share/man/pt/man1
$ /usr/bin/install -c -m 644 doc/po/pdf2djvu.pt.1 
/<>/debian/pdf2djvu/usr/share/man/pt/man1/pdf2djvu.1
$ /usr/bin/install -c -d /<>/debian/pdf2djvu/usr/share/man/fr/man1
$ /usr/bin/install -c -m 644 doc/po/pdf2djvu.fr.1 
/<>/debian/pdf2djvu/usr/share/man/fr/man1/pdf2djvu.1
INSTALL='/usr/bin/install -c' tools/install-mo 
/<>/debian/pdf2djvu/usr/share/locale po/pt.mo po/de.mo po/ru.mo 
po/pl.mo po/uk.mo
$ /usr/bin/install -c -d 
/<>/debian/pdf2djvu/usr/share/locale/pt/LC_MESSAGES
$ /usr/bin/install -c -m 644 po/pt.mo 
/<>/debian/pdf2djvu/usr/share/locale/pt/LC_MESSAGES/pdf2djvu.mo
$ /usr/bin/install -c -d 
/<>/debian/pdf2djvu/usr/share/locale/de/LC_MESSAGES
$ /usr/bin/install -c -m 644 po/de.mo 
/<>/debian/pdf2djvu/usr/share/locale/de/LC_MESSAGES/pdf2djvu.mo
$ /usr/bin/install -c -d 
/<>/debian/pdf2djvu/usr/share/locale/ru/LC_MESSAGES
$ /usr/bin/install -c -m 644 po/ru.mo 
/<>/debian/pdf2djvu/usr/share/locale/ru/LC_MESSAGES/pdf2djvu.mo
$ /usr/bin/install -c -d 
/<>/debian/pdf2djvu/usr/share/locale/pl/LC_MESSAGES
$ /usr/bin/install -c -m 644 po/pl.mo 
/<>/debian/pdf2djvu/usr/share/locale/pl/LC_MESSAGES/pdf2djvu.mo
$ /usr/bin/install -c -d 
/<>/debian/pdf2djvu/usr/share/locale/uk/LC_MESSAGES
$ /usr/bin/install -c -m 644 po/uk.mo 
/<>/debian/pdf2djvu/usr/share/locale/uk/LC_MESSAGES/pdf2djvu.mo
make[1]: Leaving directory '/<>'
   dh_installdocs -a
dh_installdocs: Cannot find (any matches for) "doc/cjk.txt" (tried in .)

debian/rules:8: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pdf2djvu.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903335: mxml: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:mxml
Version: 2.11-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch 
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
./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: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no

[... snipped ...]

Compiling mmd.c
Linking mxmldoc...
Creating libmxml.a...
a - mxml-attr.o
a - mxml-entity.o
a - mxml-file.o
a - mxml-get.o
a - mxml-index.o
a - mxml-node.o
a - mxml-search.o
a - mxml-set.o
a - mxml-private.o
a - mxml-string.o
Compiling testmxml.c
Linking testmxml...
Testing library...
Stdio file test passed!
String test passed!
File descriptor test passed!
Linking mxmldoc-static...
Generating API documentation...
make[1]: Leaving directory '/<>'
   dh_auto_test -a
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-arch
dh binary-arch 
   dh_testroot -a
   dh_prep -a
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
/usr/bin/make BUILDROOT=/<>/debian/tmp install
make[2]: Entering directory '/<>'
Installing libmxml.so to /<>/debian/tmp/usr/lib/x86_64-linux-gnu...
Installing libmxml.a to /<>/debian/tmp/usr/lib/x86_64-linux-gnu...
Installing mxmldoc in /<>/debian/tmp/usr/bin...
Installing documentation in /<>/debian/tmp/usr/share/doc/mxml...
Installing header files in /<>/debian/tmp/usr/include...
Installing pkgconfig files in 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig...
Installing man pages in /<>/debian/tmp/usr/share/man...
make[2]: Leaving directory '/<>'
cp debian/mxml.man ./debian/tmp/usr/share/man/man3/mxml.3
make[1]: Leaving directory '/<>'
   dh_install -a
   dh_installdocs -a
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:4: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mxml.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903338: opencryptoki: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:opencryptoki
Version: 3.8.1+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:11: installing './compile'
configure.ac:5: installing './config.guess'

[... snipped ...]

 /bin/mkdir -p 
'/<>/opencryptoki-3.8.1+dfsg/debian/tmp/lib/systemd/system'
 /usr/bin/install -c -m 644 pkcsslotd.service tmpfiles.conf 
'/<>/opencryptoki-3.8.1+dfsg/debian/tmp/lib/systemd/system'
make  install-data-hook
make[5]: Entering directory '/<>/opencryptoki-3.8.1+dfsg/misc'
mkdir -p /<>/opencryptoki-3.8.1+dfsg/debian/tmp/usr/lib/tmpfiles.d
cp tmpfiles.conf 
/<>/opencryptoki-3.8.1+dfsg/debian/tmp/usr/lib/tmpfiles.d/opencryptoki.conf
/bin/chmod 0644 
/<>/opencryptoki-3.8.1+dfsg/debian/tmp/usr/lib/tmpfiles.d/opencryptoki.conf
rm -f 
/<>/opencryptoki-3.8.1+dfsg/debian/tmp/usr/lib/systemd/system/tmpfiles.conf
make[5]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg/misc'
make[4]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg/misc'
make[3]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg/misc'
make[3]: Entering directory '/<>/opencryptoki-3.8.1+dfsg'
make[4]: Entering directory '/<>/opencryptoki-3.8.1+dfsg'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
make[3]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
make[2]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
# create links to .so-files in usr/lib
( cd debian/tmp/usr/lib/x86_64-linux-gnu && \
 for FILE in ./opencryptoki/*.so.* ./opencryptoki/stdll/*.so.*; \
 do \
ln -s $FILE ; \
 done \
)
# Remove broken symlinks in /usr/lib/pkcs11/
cd debian/tmp/usr/lib/x86_64-linux-gnu/pkcs11 && rm -f \
libopencryptoki.so PKCS11_API.so
# Removing useless files
rm -rf debian/tmp/etc/ld.so.conf.d
rm -rf debian/tmp/etc/init.d
rm -f debian/tmp/usr/include/Makefile*
rm -f debian/tmp/usr/include/*/Makefile*
rm -f debian/tmp/usr/lib/x86_64-linux-gnu/opencryptoki/*.la \
debian/tmp/usr/lib/x86_64-linux-gnu/opencryptoki/stdll/*.la
rm -f debian/tmp/lib/systemd/system/tmpfiles.conf
make[1]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
   debian/rules override_dh_install
make[1]: Entering directory '/<>/opencryptoki-3.8.1+dfsg'
dh_install --fail-missing  --sourcedir=debian/tmp
dh_install: Please use dh_missing --list-missing/--fail-missing instead
dh_install: This feature will be removed in compat 12.
make[1]: Leaving directory '/<>/opencryptoki-3.8.1+dfsg'
   dh_installdocs -a
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:8: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/opencryptoki.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903343: voikko-fi: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:voikko-fi
Version: 2.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --fail-missing
   dh_update_autotools_config -a -O--fail-missing
   dh_auto_configure -a -O--fail-missing
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make vvfst EXTRA_LEX=vocabulary/erikoisalat/linux-distributions.lex
make[2]: Entering directory '/<>'
python3 vvfst/generate_taivutuskaavat.py   --destdir=vvfst
python3 vvfst/generate_lex.py  --destdir=vvfst
##
touch vvfst/joukahainen.lexc.stamp
python3 vvfst/filter_lexc.py vvfst/all.lexc   vvfst/root.lexc 
vvfst/taivutuskaavat.lexc vvfst/joukahainen-ee.lexc vvfst/joukahainen-em.lexc 
vvfst/joukahainen-ep.lexc vvfst/joukahainen-es.lexc vvfst/joukahainen-h.lexc 
vvfst/joukahainen-l.lexc vvfst/joukahainen-n.lexc vvfst/joukahainen-nl.lexc 
vvfst/joukahainen-t.lexc vvfst/joukahainen-p.lexc vvfst/joukahainen-a.lexc 
vvfst/joukahainen-s.lexc vvfst/joukahainen-c.lexc vvfst/suomi.lexc 
vvfst/olla-ei.lexc vvfst/poikkeavat.lexc vvfst/lukusanat.lexc 
vvfst/asemosanat.lexc vvfst/seikkasanat.lexc vvfst/suhdesanat.lexc
sed -e "s,VVFST_BUILDDIR,vvfst," < vvfst/main.foma.in > vvfst/main.foma

[... snipped ...]

7.5 MB. 429607 states, 490840 arcs, Cyclic.
Writing AT file: vvfst/all.att
! grep ']]' vvfst/all.att
cat vvfst/all.att | sort -n | voikkovfstc -o vvfst/mor.vfst
Symbols: 288
Transitions: 490840
Final states: 1
Overflow cells: 1
python3 vvfst/autocorrect_to_lexc.py vocabulary/autocorrect/fi.xml 
vvfst/autocorrect.lexc
sed -e "s,VVFST_BUILDDIR,vvfst," < vvfst/autocorrect.foma.in > 
vvfst/autocorrect.foma
foma -f vvfst/autocorrect.foma 2>&1 | grep -v "defined but not used"
Root...Building lexicon...
228
Determinizing...
Minimizing...
Done!
22.8 kB. 1188 states, 1411 arcs, 227 paths.
defined Lexicon: 22.8 kB. 1188 states, 1411 arcs, 227 paths.
variable flag-is-epsilon = ON
22.8 kB. 1188 states, 1411 arcs, 227 paths.
22.8 kB. 1188 states, 1411 arcs, 227 paths.
Writing AT file: vvfst/autocorrect.att
cat vvfst/autocorrect.att | sort -n | voikkovfstc -o vvfst/autocorr.vfst
Symbols: 22
Transitions: 1411
Final states: 1
Overflow cells: 0
sed -e "s/SM_VOIKKO_VARIANT/standard/; s/SM_VOIKKO_DESCRIPTION/suomi 
(perussanasto)/; s/SM_VERSION/2.2/; s/SM_PATCHINFO//; 
s/SM_BUILDCONFIG/GENLEX_OPTS= 
EXTRA_LEX=vocabulary\\/erikoisalat\\/linux-distributions.lex/; 
s/SM_BUILDDATE/Fri, 08 Sep 2017 13:05:40 +/" < vvfst/index.txt.in > 
vvfst/index.txt
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test -a -O--fail-missing
 fakeroot debian/rules binary-arch
dh binary-arch --fail-missing
   dh_testroot -a -O--fail-missing
   dh_prep -a -O--fail-missing
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
/usr/bin/make vvfst-install 
DESTDIR=/<>/debian/voikko-fi/usr/lib/voikko
make[2]: Entering directory '/<>'
install -m 755 -d 
/<>/debian/voikko-fi/usr/lib/voikko/5/mor-standard
install -m 644 vvfst/index.txt vvfst/mor.vfst vvfst/autocorr.vfst 
/<>/debian/voikko-fi/usr/lib/voikko/5/mor-standard
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_installdocs -a -O--fail-missing
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:7: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/voikko-fi.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903340: prettify.js: FTBFS in buster/sid (dh_installdocs: Cannot find "README.html")

2018-07-08 Thread Santiago Vila
Package: src:prettify.js
Version: 2015.12.04+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/prettify.js-2015.12.04+dfsg'
mkdir -p loader/skins/
make distrib.tstamp
make[2]: Entering directory '/<>/prettify.js-2015.12.04+dfsg'
Compiling
1570 src/prettify.css
 675 distrib/google-code-prettify/prettify.css
62985 src/prettify.js
14514 distrib/google-code-prettify/prettify.js
src/run_prettify.js:95: WARNING - "function (this:Window, 
(Function|null|string), number, ...[*]): number" must be called with a "this" 
type

[... snipped ...]

1909 src/lang-tex.js
 858 distrib/google-code-prettify/lang-tex.js
3938 src/lang-vb.js
2404 distrib/google-code-prettify/lang-vb.js
2846 src/lang-vhdl.js
2035 distrib/google-code-prettify/lang-vhdl.js
1928 src/lang-wiki.js
1139 distrib/google-code-prettify/lang-wiki.js
25439 src/lang-xq.js
23276 distrib/google-code-prettify/lang-xq.js
1468 src/lang-yaml.js
1002 distrib/google-code-prettify/lang-yaml.js
make[2]: Leaving directory '/<>/prettify.js-2015.12.04+dfsg'
make[1]: Leaving directory '/<>/prettify.js-2015.12.04+dfsg'
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>/prettify.js-2015.12.04+dfsg'
tar cf distrib/prettify-small.tar -C distrib google-code-prettify
/bin/bash: line 2: zip: command not found
wc: distrib/prettify-small.zip: No such file or directory
37202 distrib/prettify-small.tar.bz2
37826 distrib/prettify-small.tgz
1645 styles/desert.css
 940 loader/skins/desert.css
2726 styles/doxy.css
1604 loader/skins/doxy.css
1519 styles/sons-of-obsidian.css
 698 loader/skins/sons-of-obsidian.css
1945 styles/sunburst.css
1147 loader/skins/sunburst.css
tools/lang-handler-aliases.sh \
distrib/google-code-prettify \
  | perl -ne 'system("cp $1 $2") if m/^(\S+) (\S+)$/ && ! -e $2' \
  && touch lang-aliases.tstamp
cp: cannot stat 'to': No such file or directory
make[1]: Leaving directory '/<>/prettify.js-2015.12.04+dfsg'
   dh_auto_test -i
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
   dh_install -i
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README.html" (tried in .)

debian/rules:12: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prettify.js.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903337: node-traverse: FTBFS in buster/sid (dh_installdocs: Cannot find "README.markdown")

2018-07-08 Thread Santiago Vila
Package: src:node-traverse
Version: 0.6.6-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
install -D -m644 index.js 
/<>/debian/node-traverse/usr/lib/nodejs/traverse.js
install -D -m644 index.js 
/<>/debian/libjs-traverse/usr/share/javascript/traverse/traverse.js
make[1]: Leaving directory '/<>'
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README.markdown" (tried in .)

debian/rules:8: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-traverse.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903336: node-babel-plugin-add-module-exports: FTBFS in buster/sid (dh_installdocs: Cannot find "README.md")

2018-07-08 Thread Santiago Vila
Package: src:node-babel-plugin-add-module-exports
Version: 0.2.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   dh_install -i
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README.md" (tried in .)

debian/rules:8: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-babel-plugin-add-module-exports.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903328: cobertura: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:cobertura
Version: 2.1.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
mh_patchpoms -plibcobertura-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
[ERROR] Cannot find parent dependency 
net.sourceforge.cobertura.poms:cobertura-api-parent:pom:2.1.1, use --no-parent 
option to resolve this issue or install the parent POM in the Maven repository
[ERROR] Cannot find parent dependency 
net.sourceforge.cobertura.poms:cobertura-parent:pom:2.1.1, use --no-parent 
option to resolve this issue or install the parent POM in the Maven repository
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred

[... snipped ...]

[INFO] [ pom ]-
[INFO] 
[INFO] --- debian-maven-plugin:2.3:install (default-cli) @ cobertura-runtime ---
[INFO] Cleaning pom file: /<>/cobertura-runtime/pom.xml.save with 
options:
[INFO]  --keep-pom-version --package=libcobertura-java --has-package-version
[INFO]  --rules=/<>/debian/maven.rules
[INFO]  --ignore-rules=/<>/debian/maven.ignoreRules
[INFO]  --published-rules=/<>/debian/maven.ignoreRules
[INFO]  --no-parent
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] cobertura-parent ... SUCCESS [  0.469 s]
[INFO] cobertura-api-parent ... SUCCESS [  0.190 s]
[INFO] cobertura-reactor 2.1.1  SUCCESS [  0.044 s]
[INFO] cobertura-poms-reactor . SUCCESS [  0.097 s]
[INFO] cobertura-annotations-api .. SUCCESS [  0.087 s]
[INFO] cobertura-interaction-reactor .. SUCCESS [  0.026 s]
[INFO] cobertura-annotations-reactor .. SUCCESS [  0.032 s]
[INFO] Cobertura code coverage  SUCCESS [  0.180 s]
[INFO] Cobertura Limited Runtime 2.1.1  SUCCESS [  0.034 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2.551 s
[INFO] Finished at: 2018-07-08T09:42:45Z
[INFO] 
mh_resolve_dependencies --non-interactive --offline --build 
-plibcobertura-java --base-directory=/<> --non-explore
Analysing pom.xml...
Analysing cobertura/pom.xml...
Analysing cobertura-runtime/pom.xml...
Analysing interaction/pom.xml...
Checking the parent dependency in the sub project interaction/pom.xml
Analysing interaction/annotations/pom.xml...
Checking the parent dependency in the sub project 
interaction/annotations/pom.xml
Analysing interaction/annotations/annotations-api/pom.xml...
Analysing poms/pom.xml...
Checking the parent dependency in the sub project poms/pom.xml
Analysing poms/cobertura-api-parent/pom.xml...
Analysing poms/cobertura-parent/pom.xml...
mh_unpatchpoms -plibcobertura-java
   dh_install -i
   jh_installjavadoc -i
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:4: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cobertura.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903331: golang-golang-x-net-dev: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:golang-golang-x-net-dev
Version: 1:0.0+git20180124.0ed95ab+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang --builddirectory=build
   dh_update_autotools_config -i -O--buildsystem=golang -O--builddirectory=build
   debian/rules override_dh_auto_configure
make[1]: Entering directory 
'/<>/golang-golang-x-net-dev-0.0+git20180124.0ed95ab+dfsg'
dh_auto_configure -O--buildsystem=golang
install -d build
Copy idna/idna_test.go -> build/src/golang.org/x/net/idna/idna_test.go
Copy idna/idna.go -> build/src/golang.org/x/net/idna/idna.go
Copy idna/example_test.go -> 
build/src/golang.org/x/net/idna/example_test.go
Copy idna/punycode_test.go -> 
build/src/golang.org/x/net/idna/punycode_test.go
Copy idna/trie.go -> build/src/golang.org/x/net/idna/trie.go
Copy idna/trieval.go -> build/src/golang.org/x/net/idna/trieval.go
Copy idna/tables.go -> build/src/golang.org/x/net/idna/tables.go

[... snipped ...]

=== RUN   TestParseAuthority
--- PASS: TestParseAuthority (0.00s)
=== RUN   TestClose
--- PASS: TestClose (0.00s)
=== RUN   TestOrigin
--- PASS: TestOrigin (0.00s)
=== RUN   TestCtrlAndData
--- PASS: TestCtrlAndData (0.00s)
=== RUN   TestCodec_ReceiveLimited
--- PASS: TestCodec_ReceiveLimited (0.00s)
websocket_test.go:629: payload #0 (size 1024, exceeds limit: false)
websocket_test.go:629: payload #1 (size 2048, exceeds limit: false)
websocket_test.go:629: payload #2 (size 4096, exceeds limit: true)
websocket_test.go:629: payload #3 (size 2048, exceeds limit: false)
PASS
ok  golang.org/x/net/websocket  0.012s
=== RUN   TestValidToken
--- PASS: TestValidToken (0.00s)
=== RUN   TestSeparatorReplacement
--- PASS: TestSeparatorReplacement (0.00s)
=== RUN   TestInvalidToken
--- PASS: TestInvalidToken (0.00s)
=== RUN   TestValidateBadData
--- PASS: TestValidateBadData (0.00s)
PASS
ok  golang.org/x/net/xsrftoken  0.001s
make[1]: Leaving directory 
'/<>/golang-golang-x-net-dev-0.0+git20180124.0ed95ab+dfsg'
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=golang --with=golang --builddirectory=build
   dh_testroot -i -O--buildsystem=golang -O--builddirectory=build
   dh_prep -i -O--buildsystem=golang -O--builddirectory=build
rm -f -- debian/golang-golang-x-net-dev.substvars 
debian/golang-go.net-dev.substvars
rm -fr -- debian/.debhelper/generated/golang-golang-x-net-dev/ 
debian/golang-golang-x-net-dev/ debian/tmp/ 
debian/.debhelper/generated/golang-go.net-dev/ debian/golang-go.net-dev/
   dh_auto_install -i -O--buildsystem=golang -O--builddirectory=build
install -d debian/golang-golang-x-net-dev debian/golang-go.net-dev
cd build && mkdir -p 
/<>/golang-golang-x-net-dev-0.0\+git20180124.0ed95ab\+dfsg/debian/tmp/usr/share/gocode/src/golang.org/x/net
cd build && cp -r -T src/golang.org/x/net 
/<>/golang-golang-x-net-dev-0.0\+git20180124.0ed95ab\+dfsg/debian/tmp/usr/share/gocode/src/golang.org/x/net
   dh_install -i -O--buildsystem=golang -O--builddirectory=build
install -d debian/golang-golang-x-net-dev//usr/share
cp --reflink=auto -a debian/tmp/usr/share/gocode 
debian/golang-golang-x-net-dev//usr/share/
install -d debian/.debhelper/generated/golang-golang-x-net-dev
install -d debian/.debhelper/generated/golang-go.net-dev
   dh_installdocs -i -O--buildsystem=golang -O--builddirectory=build
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

install -d 
debian/golang-golang-x-net-dev/usr/share/doc/golang-golang-x-net-dev
debian/rules:13: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-golang-x-net-dev.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903329: eric: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:eric
Version: 18.05-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
make: Nothing to be done for 'build-indep'.
 fakeroot debian/rules binary-indep
#   generate API files
#mkdir -p debian/qtapis
#mkdir -p debian/apis
#debian/kdeapis debian/pyapis debian/apis
#python3 debian/gen_qt_apis.py debian/qtapis/
#python debian/gen_kde_apis.py debian/kdeapis/
#python debian/gen_python_api.py debian/pyapis/
#sort -u debian/qtapis/*.api > debian/apis/pyqt.api
#sort -u debian/kdeapis/*.api > debian/apis/pykde.api
#sort -u debian/pyapis/*.api > 
touch apifile-stamp

[... snipped ...]


Installation complete.


dh_installdirs -i
for i in eric/i18n/*.ts; do\
lrelease -qt=5 $i -qm debian/eric/usr/share/qt5/translations/`basename 
$i .ts`.qm;\
done
Updating 'debian/eric/usr/share/qt5/translations/eric6_de.qm'...
Generated 16413 translation(s) (16413 finished and 0 unfinished)
Updating 'debian/eric/usr/share/qt5/translations/eric6_empty.qm'...
Generated 0 translation(s) (0 finished and 0 unfinished)
Ignored 16413 untranslated source text(s)
Updating 'debian/eric/usr/share/qt5/translations/eric6_en.qm'...
Generated 109 translation(s) (98 finished and 11 unfinished)
Ignored 16304 untranslated source text(s)
Updating 'debian/eric/usr/share/qt5/translations/eric6_es.qm'...
Generated 16413 translation(s) (16413 finished and 0 unfinished)
Updating 'debian/eric/usr/share/qt5/translations/eric6_ru.qm'...
Generated 16413 translation(s) (16413 finished and 0 unfinished)
rm -f debian/eric/usr/share/doc/eric/LICENSE.GPL3
rm -f debian/eric/usr/share/eric/modules/LICENSE.GPL3
rm -f debian/eric/usr/share/eric/modules/install*.py
mv debian/eric/usr/share/eric/api/* debian/eric-api-files/usr/share/eric/api
#for i in debian/apis/pyqt.api debian/apis/python.api; do \
#   install -o root -g root -m 644 $i \
#   debian/eric-api-files/usr/share/eric/api/python; \
#done
rm -f debian/eric/usr/share/doc/eric/README-PyXML.txt
rm -rf debian/eric/usr/share/eric/modules/ThirdParty/CharDet
rm -rf debian/eric/usr/share/eric/modules/ThirdParty/enum
rm -rf debian/eric/usr/share/eric/modules/ThirdParty/Pygments
find debian/eric/ -name '*.py[co]' -delete
rm -f debian/eric/usr/share/applications/eric6.desktop
find . -name __pycache__ -prune | xargs rm -rf
#Removing eric6_browser. QtWebEngineWidgets is not included in Debian
rm -f debian/eric/usr/share/eric/modules/eric6_browser.py
rm -f debian/eric/usr/share/eric/modules/eric6_browser.pyw
rm -f debian/eric/usr/share/applications/eric6_browser.desktop
rm -f debian/eric/usr/bin/eric6_browser
dh_testdir -i
dh_testroot -i
dh_installchangelogs
dh_installdocs -i --exclude=LICENSE.GPL3 --exclude=README
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:90: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/eric.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903332: happy: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:happy
Version: 1.19.9-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
enable.
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
/bin/bash: /usr/bin/licensecheck: No such file or directory
0 combinations of copyright and licensing found.
diff: debian/copyright_hints: No such file or directory
No new copyright notices found - assuming no news is good news...

[... snipped ...]

 fakeroot debian/rules binary-arch
CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
enable.
test -x debian/rules
dh_testroot
dh_prep 
dh_installdirs -A 
mkdir -p "."
CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
/bin/bash: /usr/bin/licensecheck: No such file or directory
0 combinations of copyright and licensing found.
diff: debian/copyright_hints: No such file or directory
No new copyright notices found - assuming no news is good news...
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
# doc/configure is not shipped, generate it
cd doc && autoconf && rm -r autom4te.cache &&  ./configure --prefix=/usr
checking for xmllint... no
configure: WARNING: cannot find xmllint in your PATH, you will not be able to 
validate your documentation
checking for xsltproc... /usr/bin/xsltproc
checking for DocBook XSL stylesheet directory... 
/usr/share/xml/docbook/stylesheet/nwalsh
checking for dblatex... no
configure: creating ./config.status
config.status: creating config.mk
config.status: creating happy.1
# used in build to stick version into man page
ghc --make debian/get_version.hs -o debian/get_version
/usr/bin/make -C doc html
make[1]: Entering directory '/<>/doc'
make[1]: Nothing to be done for 'html'.
make[1]: Leaving directory '/<>/doc'
sed -e "s#@LIBDIR@#/usr/share/happy-`debian/get_version`#g" \
-e "s#@DOCDIR@#/usr/share/doc/happy#g" \
-e "s#@VERSION@#`debian/get_version`#g" \
  doc/happy.1.in > doc/happy.1
Adding cdbs dependencies to debian/happy.substvars
dh_installdirs -phappy \

dh_haskell_blurbs "ghc" -phappy
dh_installdocs -phappy ./TODO
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

/usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 
'binary-install/happy' failed
make: *** [binary-install/happy] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/happy.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903325: blinker: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:blinker
Version: 1.4+dfsg1-0.1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:217: /usr/bin/python setup.py build 
running build

[... snipped ...]

dh_auto_install: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:217: /usr/bin/python setup.py install --root 
/<>/blinker-1.4+dfsg1/debian/tmp 
running install
running build
running build_py
running install_lib
creating /<>/blinker-1.4+dfsg1/debian/tmp
creating /<>/blinker-1.4+dfsg1/debian/tmp/usr
creating /<>/blinker-1.4+dfsg1/debian/tmp/usr/lib
creating /<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7
creating 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages
creating 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython2_2.7/build/blinker/_utilities.py
 -> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython2_2.7/build/blinker/__init__.py 
-> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython2_2.7/build/blinker/_saferef.py 
-> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython2_2.7/build/blinker/base.py -> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker/_utilities.py
 to _utilities.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker/__init__.py
 to __init__.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker/_saferef.py
 to _saferef.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker/base.py
 to base.pyc
running install_egg_info
Writing 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python2.7/dist-packages/blinker-1.4.egg-info
I: pybuild base:217: /usr/bin/python3 setup.py install --root 
/<>/blinker-1.4+dfsg1/debian/tmp 
running install
running build
running build_py
running install_lib
creating /<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6
creating 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages
creating 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython3_3.6/build/blinker/_utilities.py
 -> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython3_3.6/build/blinker/__init__.py 
-> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython3_3.6/build/blinker/_saferef.py 
-> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
copying 
/<>/blinker-1.4+dfsg1/.pybuild/cpython3_3.6/build/blinker/base.py -> 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker/_utilities.py
 to _utilities.cpython-36.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker/_saferef.py
 to _saferef.cpython-36.pyc
byte-compiling 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker/base.py
 to base.cpython-36.pyc
running install_egg_info
Writing 
/<>/blinker-1.4+dfsg1/debian/tmp/usr/lib/python3.6/dist-packages/blinker-1.4.egg-info
   dh_install -i -O--buildsystem=pybuild
dh_install: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_installdocs -i -O--buildsystem=pybuild
dh_installdocs: Compatibility levels before 9 are deprecated (level 7 in use)
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:4: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.

Bug#903326: calcurse: FTBFS in buster/sid (dh_installdocs: Cannot find "NEWS")

2018-07-08 Thread Santiago Vila
Package: src:calcurse
Version: 4.3.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_auto_configure -a
./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: WARNING: unrecognized options: --disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether NLS is requested... yes

[... snipped ...]

 /bin/mkdir -p '/<>/debian/calcurse/usr/bin'
 /usr/bin/install -c calcurse-upgrade '/<>/debian/calcurse/usr/bin'
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/scripts'
make[3]: Leaving directory '/<>/scripts'
Making install in contrib/caldav
make[3]: Entering directory '/<>/contrib/caldav'
make[4]: Entering directory '/<>/contrib/caldav'
 /bin/mkdir -p '/<>/debian/calcurse/usr/bin'
 /usr/bin/install -c calcurse-caldav '/<>/debian/calcurse/usr/bin'
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>/contrib/caldav'
make[3]: Leaving directory '/<>/contrib/caldav'
Making install in doc
make[3]: Entering directory '/<>/doc'
make[4]: Entering directory '/<>/doc'
make[4]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p '/<>/debian/calcurse/usr/share/man/man1'
 /usr/bin/install -c -m 644 calcurse.1 
'/<>/debian/calcurse/usr/share/man/man1'
 /bin/mkdir -p '/<>/debian/calcurse/usr/share/doc/calcurse'
 /bin/mkdir -p '/<>/debian/calcurse/usr/share/doc/calcurse/nl'
 /usr/bin/install -c -m 644  nl/enote.txt nl/view.txt nl/general.txt 
nl/priority.txt nl/other.txt nl/add.txt nl/config.txt nl/repeat.txt 
nl/displacement.txt nl/vnote.txt nl/tab.txt nl/pipe.txt nl/save.txt nl/goto.txt 
nl/edit.txt nl/flag.txt nl/export.txt nl/delete.txt nl/credits.txt 
nl/import.txt nl/copy-paste.txt nl/intro.txt 
'/<>/debian/calcurse/usr/share/doc/calcurse/nl'
 /bin/mkdir -p '/<>/debian/calcurse/usr/share/doc/calcurse/pt_BR'
 /usr/bin/install -c -m 644  pt_BR/enote.txt pt_BR/view.txt pt_BR/general.txt 
pt_BR/priority.txt pt_BR/other.txt pt_BR/add.txt pt_BR/config.txt 
pt_BR/repeat.txt pt_BR/displacement.txt pt_BR/vnote.txt pt_BR/tab.txt 
pt_BR/pipe.txt pt_BR/save.txt pt_BR/goto.txt pt_BR/edit.txt pt_BR/flag.txt 
pt_BR/export.txt pt_BR/delete.txt pt_BR/credits.txt pt_BR/import.txt 
pt_BR/copy-paste.txt pt_BR/intro.txt 
'/<>/debian/calcurse/usr/share/doc/calcurse/pt_BR'
 /bin/mkdir -p '/<>/debian/calcurse/usr/share/doc/calcurse/ru'
 /usr/bin/install -c -m 644  ru/enote.txt ru/view.txt ru/general.txt 
ru/priority.txt ru/other.txt ru/add.txt ru/config.txt ru/repeat.txt 
ru/displacement.txt ru/vnote.txt ru/tab.txt ru/pipe.txt ru/save.txt ru/goto.txt 
ru/edit.txt ru/flag.txt ru/export.txt ru/delete.txt ru/credits.txt 
ru/import.txt ru/copy-paste.txt ru/intro.txt 
'/<>/debian/calcurse/usr/share/doc/calcurse/ru'
 /bin/mkdir -p '/<>/debian/calcurse/usr/share/doc/calcurse/de'
 /usr/bin/install -c -m 644  de/enote.txt de/view.txt de/general.txt 
de/priority.txt de/other.txt de/add.txt de/config.txt de/repeat.txt 
de/displacement.txt de/vnote.txt de/tab.txt de/pipe.txt de/save.txt de/goto.txt 
de/edit.txt de/flag.txt de/export.txt de/delete.txt de/credits.txt 
de/import.txt de/copy-paste.txt de/intro.txt 
'/<>/debian/calcurse/usr/share/doc/calcurse/de'
 /bin/mkdir -p '/<>/debian/calcurse/usr/share/doc/calcurse/es'
 /usr/bin/install -c -m 644  es/enote.txt es/view.txt es/general.txt 
es/priority.txt es/other.txt es/add.txt es/config.txt es/repeat.txt 
es/displacement.txt es/vnote.txt es/tab.txt es/pipe.txt es/save.txt es/goto.txt 
es/edit.txt es/flag.txt es/export.txt es/delete.txt es/credits.txt 
es/import.txt es/copy-paste.txt es/intro.txt 
'/<>/debian/calcurse/usr/share/doc/calcurse/es'
 /usr/bin/install -c -m 644  manual.html submitting-patches.html add.txt 
config.txt copy-paste.txt credits.txt delete.txt displacement.txt edit.txt 
enote.txt export.txt flag.txt general.txt goto.txt import.txt intro.txt 
manual.txt other.txt pipe.txt priority.txt reload.txt repeat.txt save.txt 
tab.txt view.txt vnote.txt 
'/<>/debian/calcurse/usr/share/doc/calcurse/.'
 /bin/mkdir -p '/<>/debian/calcurse/usr/share/doc/calcurse/fr'
 /usr/bin/install -c -m 644  fr/enote.txt fr/view.txt fr/general.txt 
fr/priority.txt fr/other.txt fr/add.txt fr/config.txt fr/repeat.txt 

Bug#903327: cl-usocket: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:cl-usocket
Version: 0.7.0.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh_testdir
dh_testroot
dh_prep
dh_installdirs
dh_install
dh_testdir
dh_testroot
dh_installchangelogs
dh_installdocs
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:28: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cl-usocket.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#903330: glogg: FTBFS in buster/sid (dh_installdocs: Cannot find "README")

2018-07-08 Thread Santiago Vila
Package: src:glogg
Version: 1.1.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_MD5SUMS_ARGS is deprecated since 0.4.85
cd . && qmake -qt=5 VERSION=1.1.4-1 'QMAKE_CC = cc' 'QMAKE_CXX = g++' 
'QMAKE_CFLAGS_RELEASE = -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security' 'QMAKE_CXXFLAGS_RELEASE = -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security' 
'QMAKE_LFLAGS_RELEASE = -Wl,-z,relro'
Info: creating stash file /<>/.qmake.stash
Project MESSAGE: Building using system dynamic Boost libraries
Project MESSAGE: Support for D-BUS will be included
Project MESSAGE: Version checker will NOT be included
Project MESSAGE: File watching using inotify
/usr/bin/make -C . 
make[1]: Entering directory '/<>'
markdown doc/documentation.markdown | sed -f finish.sed >doc/documentation.html
/usr/lib/qt5/bin/uic src/optionsdialog.ui -o 
.ui/release-shared/ui_optionsdialog.h

[... snipped ...]

g++ -c -g -Wextra -std=c++0x -DGLOGG_VERSION=\"1.1.4-1\" -DGLOGG_SUPPORTS_DBUS 
-DGLOGG_SUPPORTS_INOTIFY -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -D_REENTRANT -fPIC 
-DFILELOG_MAX_LEVEL="logDEBUG" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -Isrc -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc/release-shared -isystem 
/usr/include/libdrm -I.ui/release-shared 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
.obj/release-shared/moc_overviewwidget.o 
.moc/release-shared/moc_overviewwidget.cpp
/usr/lib/qt5/bin/moc -DFILELOG_MAX_LEVEL="logDEBUG" -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB 
--include /<>/.moc/release-shared/moc_predefs.h 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -I/<> 
-I/<>/src -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/include/c++/7 
-I/usr/include/x86_64-linux-gnu/c++/7 -I/usr/include/c++/7/backward 
-I/usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/local/include 
-I/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed -I/usr/include/x86_64-linux-gnu 
-I/usr/include src/quickfindmux.h -o .moc/release-shared/moc_quickfindmux.cpp
g++ -c -g -Wextra -std=c++0x -DGLOGG_VERSION=\"1.1.4-1\" -DGLOGG_SUPPORTS_DBUS 
-DGLOGG_SUPPORTS_INOTIFY -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -D_REENTRANT -fPIC 
-DFILELOG_MAX_LEVEL="logDEBUG" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -Isrc -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc/release-shared -isystem 
/usr/include/libdrm -I.ui/release-shared 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
.obj/release-shared/moc_quickfindmux.o .moc/release-shared/moc_quickfindmux.cpp
/usr/lib/qt5/bin/moc -DFILELOG_MAX_LEVEL="logDEBUG" -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB 
--include /<>/.moc/release-shared/moc_predefs.h 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -I/<> 
-I/<>/src -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/include/c++/7 
-I/usr/include/x86_64-linux-gnu/c++/7 -I/usr/include/c++/7/backward 
-I/usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/local/include 
-I/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed -I/usr/include/x86_64-linux-gnu 
-I/usr/include src/tabbedcrawlerwidget.h -o 
.moc/release-shared/moc_tabbedcrawlerwidget.cpp
g++ -c -g -Wextra -std=c++0x -DGLOGG_VERSION=\"1.1.4-1\" -DGLOGG_SUPPORTS_DBUS 
-DGLOGG_SUPPORTS_INOTIFY -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -D_REENTRANT 

Bug#903324: adasockets: FTBFS in buster/sid (dh_installdocs: Cannot find "README.Debian")

2018-07-08 Thread Santiago Vila
Package: src:adasockets
Version: 1.10.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'support'.
libtoolize: copying file 'support/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'support'.
libtoolize: copying file 'support/libtool.m4'
libtoolize: copying file 'support/ltoptions.m4'
libtoolize: copying file 'support/ltsugar.m4'
libtoolize: copying file 'support/ltversion.m4'
libtoolize: copying file 'support/lt~obsolete.m4'
configure.ac:12: installing 'support/compile'
configure.ac:12: installing 'support/config.guess'

[... snipped ...]

Copyright (C) 1992-2017, Free Software Foundation, Inc.
  "stream_listener.ali" being checked ...
   s-oscons.ads: up to date, different timestamps but same checksum
  "sockets.ali" is in an Ada library
  "sockets-stream_io.ali" is in an Ada library
End of compilation
gnatmake: "stream_listener" up to date.
gnatmake -j1 -R -v -eS -m -A../src -A../src -I. stream_sender -cargs -g -O2 
-Wall -Werror -gnatag -gnatwa -gnatwe -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -largs 
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-z,defs

GNATMAKE 7.3.0
Copyright (C) 1992-2017, Free Software Foundation, Inc.
  "stream_sender.ali" being checked ...
  "sockets.ali" is in an Ada library
  "sockets-stream_io.ali" is in an Ada library
End of compilation
gnatmake: "stream_sender" up to date.
make[3]: Entering directory '/<>/examples'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/examples'
make[2]: Leaving directory '/<>/examples'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install -plibadasockets7-dev usr/bin/adasockets-config
dh_install -plibadasockets7-dev usr/lib/x86_64-linux-gnu/libadasockets.a
dh_install -plibadasockets7-dev usr/lib/x86_64-linux-gnu/pkgconfig/adasockets.pc
dh_install -plibadasockets7-dev usr/lib/x86_64-linux-gnu/libadasockets.so
dh_install -plibadasockets7 usr/lib/x86_64-linux-gnu/libadasockets.so.*
dh_install -plibadasockets7-dev usr/lib/x86_64-linux-gnu/adasockets/*.ad[bs] \
  usr/share/ada/adainclude/adasockets
dh_install -plibadasockets7-dev usr/lib/x86_64-linux-gnu/adasockets/*.ali \
  usr/lib/x86_64-linux-gnu/ada/adalib/adasockets
dh_install -plibadasockets7-dev debian/adasockets.gpr usr/share/gpr
dh_install --remaining-packages
dh_install: No packages to build. Architecture mismatch: amd64, want: any
make[1]: Leaving directory '/<>'
   dh_installdocs -a
dh_installdocs: Cannot find (any matches for) "README.Debian" (tried in .)

debian/rules:34: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/adasockets.html

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.



Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)

2018-07-08 Thread Evgeny Kapun

On 08.07.2018 22:54, Steven R. Wright wrote:

This is a critical enough bug to warrant removing 5.2.14-dfsg-1 from the repos. 
 I have to do selective upgrades now to avoid pulling it in.


Unstable repo is called unstable for a reason. If you want a system that 
doesn't break, use stable (you can install VirtualBox from backports) or 
testing.



  1   2   3   >