Bug#899234: git-buildpackage: gbp-push fails when there is no upstream branch

[Guido Günther]

Hi,
On Mon, May 21, 2018 at 02:39:00PM +0200, Paride Legovini wrote:
> On 21/05/2018 13.04, Guido Günther wrote:
> > Hi,
> 
> Hi Guido, thanks for your reply.
> 
> > On Mon, May 21, 2018 at 11:22:31AM +0200, Paride Legovini wrote:
> >>
> >> When working with git remotes and tags (instead of importing upstream
> >> tarballs) an upstream branch is not normally not needed or wanted. This
> >> kind of workflow is not uncommon, in fact is is suggested by the gbp
> >> documentation:
> >>
> >> /usr/share/doc/git-buildpackage/manual-html/gbp.import.upstream-git.html
> > 
> > I think the documentation above does not suggest that there is no
> > upstream branch, rather that you don't need gbp import-orig to maintain
> > it. At least that's the intention. If that's not the case please let
> > me know where you read that not having a branch with pristine upstream
> > source is a good idea. We should fix that then.
> 
> I was hoping to get a comment on this. :)
> 
> The idea that gbp.import.upstream-git.html somehow suggests that an
> upstream branch is not necessary comes from the following facts:
> 
> (1) In the proposed workflow, an upstream branch is not mentioned. The
> document is almost a step-by-step guide, for example it shows how to
> fetch and merge a new upstream release, but no hint is given on how to
> maintain an upstream branch.
> 
> (2) By following that workflow, the master branch is almost what an
> upstream branch should be. Actually, in the beginning I thought that I
> had to consider the upstream branch to be "master". But this branch is
> never updated: the new upstream versions are merged directly in the
> Debian branch.
> 
> (3) When releases are tagged upstream, I don't see the advantage of
> maintaining an upstream branch. Tags can be checkedout and already
> represent the pristine upstream source. This seems to be a sound idea,
> and in fact by default we have upstream-tree=TAG.

Well by "maintaining" you mean having this ref in your repo? There certainly is 
a
branch where upstream development happens on.

> Should we conclude that I'm wrong and that there are good reasons to
> maintain an upstream branch, then the central point of this report will
> cease to exist.

The main reason is cherry-picking from this branch is simple with
gbp-pq, etc.

> >> and DEP14 somehow implies that an upstream branch may not exist by not
> >> mentioning it at all in the "Importing upstream releases from Git tags"
> >> section.
> 
> And, should we conclude that an upstream branch has to be maintained, I
> think DEP14 should be more explicit on this point.
> 
> >> Now, coming to the point of this report. When ‘gbp push’ is called, it
> >> will look for the branch where commit tagged with the release version
> >> lies, and it will try to push this refspec to the corresponding remote
> >> branch. When working without an upstream branch, the tag will refer to a
> >> commit in the debian branch, and this commit will be behind the branch tip.
> > 
> > "in the debian branch" is not defined in git. Upstream as well as Debian
> > tags are always reachable from the Debian branch. Upstream-tags are
> > reachable from the Upstream branch as well whereas Debian tags are not..
> > 
> > By released version do you refer to the Debian or upstream version?
> 
> I forgot to mention something here -- sorry. If there is no upstream
> branch, gbp-push fails as you may expect (debian-branch=debian/sid):
> 
> $ gbp push --verbose --dry-run
> gbp:debug: ['git', 'rev-parse', '--show-cdup']
> gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
> gbp:debug: ['git', 'rev-parse', '--git-dir']
> gbp:debug: ['git', 'symbolic-ref', 'HEAD']
> gbp:debug: ['git', 'show-ref', 'refs/heads/debian/sid']
> gbp:debug: ['git', 'config', 'branch.debian/sid.remote']
> gbp:debug: ['git', 'tag', '-l', 'debian/1.5.0-1']
> gbp:debug: ['git', 'tag', '-l', '1.5.0']
> gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', '1.5.0^{commit}']
> gbp:debug: ['git', 'rev-parse', '--quiet', '--verify',
> 'refs/heads/upstream']
> gbp:error: revision 'refs/heads/upstream' not found

O.k., this can be fixed by not pushing anything if the
corresponding branch or tag name is empty. E.g.

   gbp push --upstream-branch=''

would omit that branch. Same for debian-branch, debian-tag and
ustream-tag when set on the command line or in gbp.conf. I'll push a
patch for this once I'm near my smart card again.

Cheers,
 -- Guido

Bug#898816: closing 898816

[Yanhao Mo]

On Fri 05/18 09:46, Boyuan Yang wrote:
> close 898816 
> thanks
> 
> Uploaded. Thanks!
> 
> --
> Boyuan Yang

I am sorry boyuan, seems you don't have dm permission on this package.
I'm still waiting another interested DD to sponsor this package.

-- 
Yanhao Mo


signature.asc
Description: PGP signature

Bug#897210: nitrokey-app: Need to coordinate move of udev rule to libnitrokey

[Scott Kitterman]

On Sun, 13 May 2018 12:25:13 +0200 Jan Luca Naumann  
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Control: tags 897210 fixed-in-experimental
> 
> Dear Scott,
> 
> I have uploaded nitrokey-app in the current versiont to experimental
> as well to allow testing the changes. I have removed the udev-releated
> stuff from the package.
> 
> I found a small mistake in the libnitrokey package: The installation
> path for udev-rules seems to be /lib/udev/rules.d. I have opened a
> merge request on salsa to fix this:
> 
> https://salsa.debian.org/kitterman/libnitrokey/merge_requests/1
> 
> The other paths I have applied to the rules was just to get rid of
> linitan warnings that could not parse the IF/GOTO-statements
> correctly. The current version seems to be fixed so this patch is not
> necessary anymore.

Thanks.  I've uploaded libnitrokey to unstable, so you should be able to 
upload shortly.

Scott K

Bug#879619: Autopkgtest for ncbi-tools6

[Andreas Tille]

Hi Liubov,

On Tue, May 22, 2018 at 01:01:55AM +0200, Liubov Chuprikova wrote:
> 
> Aaron, thank you for the explanations! They helped me a lot!

+1
 
> Aaron, Andreas: what is your opinion about the whole test? Could we
> consider it as completed?

Your work looks very fine grained but for the decision of "completed"
Aaron is the expert we both need to trust.  Aaron, let me know if you
want me to upload or if you want to do it yourself.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#899278: blepvco FTCBFS: hard codes the build architecture compiler

[Helmut Grohne]

Source: blepvco
Version: 0.1.0-3
Tags: upstream patch
User: helm...@debian.org
Usertags: rebootstrap

blepvco fails to cross build from source, because the upstream build
system hard codes the build architecture compiler g++. After making it
substitutable, blepvco cross builds successfully. Please consider
applying the attached patch.

Helmut
--- blepvco-0.1.0.orig/Makefile
+++ blepvco-0.1.0/Makefile
@@ -4,7 +4,7 @@
 
 
 blepvco.so:	blepvco.o blepvco_if.o exp2ap.o minblep_tables.o
-	g++ -shared  blepvco.o blepvco_if.o exp2ap.o minblep_tables.o -o blepvco.so
+	$(CXX) -shared  blepvco.o blepvco_if.o exp2ap.o minblep_tables.o -o blepvco.so
 
 blepvco.o:	ladspaplugin.h blepvco.h minblep_tables.h
 blepvco_if.o:	ladspaplugin.h blepvco.h

Bug#899277: mm: runs tests despite DEB_BUILD_OPTIONS=nocheck

[Helmut Grohne]

Source: mm
Version: 1.4.2-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

mm runs tests even when built with DEB_BUILD_OPTIONS=nocheck. Doing so
breaks e.g. cross building. The attached patch implements support for
DEB_BUILD_OPTIONS=nocheck. Please consider applying it.

Helmut
diff -u mm-1.4.2/debian/changelog mm-1.4.2/debian/changelog
--- mm-1.4.2/debian/changelog
+++ mm-1.4.2/debian/changelog
@@ -1,3 +1,10 @@
+mm (1.4.2-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Honour DEB_BUILD_OPTIONS=nocheck (closes: #-1).
+
+ -- Helmut Grohne   Tue, 22 May 2018 06:25:09 +0200
+
 mm (1.4.2-5) unstable; urgency=low
 
   * Update to debhelper 9.
diff -u mm-1.4.2/debian/rules mm-1.4.2/debian/rules
--- mm-1.4.2/debian/rules
+++ mm-1.4.2/debian/rules
@@ -37,7 +37,9 @@
dh_testdir
 
$(MAKE)
+ifeq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
./mm_test
+endif
 
touch build-stamp
 

Bug#898259: RFP: vscode -- Microsoft Visual Studio Code

[Zebulon McCorkle]

On Wed, May 09, 2018 at 11:11:01AM +0100, Daniel Pocock wrote:
> They also distribute binary versions that may or not be built from an
> identical code base and contain other (non-free) license clauses.  The
> differences are discussed[2] in Github.  It is suggested that the
> difference between the source and binary version is like the difference
> between chromium and chrome.
> 
> Various people have commented about the product sending[3] telemetry
> data to the upstream but it is not clear if that happens if it is built
> from the source but presumably that can be patched.

This might have changed since I last looked into it, but last I checked
the only difference between the OSS project and the MS-distributed
builds is a list of URLs for extension repositor(y|ies), telemetry
server(s), etc. Source builds will likely not have the extension repo or
anything online, unlike Chrome/Chromium where Chromium still has access to
the webstore and Google integration.

See
https://github.com/Microsoft/vscode/issues/60#issuecomment-161792005,
though things may have changed since 2015 when that was written.

-- 
Zebulon McCorkle
Email: zebmccor...@zeb.fun
IRC:
 - zebmccorkle@Freenode
 - zebmccorkle@OFTC
 - zeb@EsperNet
 - zeb@hackint
 - zeb@PdgnCo
 - zeb@EFNet
PGP: 803A 0F47 82AD DDEA 46BE  055F F8F9 DB8C 1A54 6398
 (Zebulon McCorkle )


signature.asc
Description: PGP signature

Bug#899276: mark nkf Multi-Arch: foreign

[Helmut Grohne]

Package: nkf
Version: 1:2.1.4-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:cmigemo

cmigemo fails to cross build from source, because it fails running nkf
with an "Exec format error". That usually means it got the wrong nkf.
Either the nkf dependency needs to be annotated with :native or nkf
needs to be marked Multi-Arch: foreign. In this case, the latter looks
correct as nkf is a command line tool for converting between encodings.
These encodings happen to be independent of the CPU architecture, so the
behaviour of nkf does not vary depending on what kind of CPU it was run
on. Thus I think nkf should be marked Multi-Arch: foreign.

Helmut
diff --minimal -Nru nkf-2.1.4/debian/changelog nkf-2.1.4/debian/changelog
--- nkf-2.1.4/debian/changelog  2016-11-30 07:35:40.0 +0100
+++ nkf-2.1.4/debian/changelog  2018-05-21 18:36:14.0 +0200
@@ -1,3 +1,10 @@
+nkf (1:2.1.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark nkf Multi-Arch: foreign, closes: #-1.
+
+ -- Helmut Grohne   Mon, 21 May 2018 18:36:14 +0200
+
 nkf (1:2.1.4-1) unstable; urgency=medium
 
   [ Hideki Yamane ]
diff --minimal -Nru nkf-2.1.4/debian/control nkf-2.1.4/debian/control
--- nkf-2.1.4/debian/control2016-11-20 23:07:36.0 +0100
+++ nkf-2.1.4/debian/control2018-05-21 18:36:10.0 +0200
@@ -10,6 +10,7 @@
 
 Package: nkf
 Architecture: any
+Multi-Arch: foreign
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Network Kanji code conversion Filter
  Nkf is yet another kanji code converter among networks,

Bug#899273: ITP: fonts-ibm-plex -- IBM's corporate typeface

[Paul Wise]

On Mon, 2018-05-21 at 21:06 -0500, Zebulon McCorkle wrote:

> Alright, from reading that it looks like it'll have to be contrib?

I think it would be better to engage with upstream to fix the issue.

> So, IceCat style? What's the process around that?

Check out the RFN section in the OFL license and IBM's license grant.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#742170: Reaver man page is out of date

[Awtul]

Package: reaver
Version: 1.6.5-1
Followup-For: Bug #742170

Dear Maintainer,

Manual page of 1.6.5-1 still 1.3
https://github.com/t6x/reaver-wps-fork-t6x/issues/195

Cheers,
Awtul

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

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

Versions of packages reaver depends on:
ii  libc6   2.27-3
ii  libpcap0.8  1.8.1-6

Versions of packages reaver recommends:
ii  pixiewps  1.4.2-1

Versions of packages reaver suggests:
ii  aircrack-ng  1:1.2.0-5

-- no debconf information

Bug#899267: ruby2.5: 89267: Updated patches for directory kfreebsd-i386

[Svante Signell]

Hi again,

Attached are updated patches for directory debian/tests/excludes/kfreeebsd-
i386.


Thanks!--- /dev/null	2018-05-22 05:17:44.0 +0200
+++ b/debian/tests/excludes/kfreebsd-i386/TestGemSpecification.rb	2018-05-22 01:29:57.476472000 +0200
@@ -0,0 +1,2 @@
+# Actual is one day earlier than Expected
+exclude :test_date_equals_time, 'fails on kFreeBSD'
--- /dev/null	2018-05-22 05:20:07.0 +0200
+++ b/debian/tests/excludes/kfreebsd-i386/TestIO.rb	2018-05-22 02:05:37.053279000 +0200
@@ -0,0 +1,8 @@
+# pid 46356 killed by SIGABRT (signal 6)
+# | -:8: [BUG] rb_maygvl_fd_fix_cloexec: fcntl(-1, F_GETFD) failed: Bad file descriptor
+# | ruby 2.5.1p57 (2018-03-29 revision 63029) [i386-kfreebsd-gnu]
+# | [NOTE]
+# | You may have encountered a bug in the Ruby interpreter or extension libraries.
+# | Bug reports are welcome.
+# | For details: http://www.ruby-lang.org/bugreport.html
+exclude :test_dup_many, 'fails on kfreebsd-i386'
--- /dev/null	2018-05-22 05:20:27.0 +0200
+++ b/debian/tests/excludes/kfreebsd-i386/TestProcess.rb	2018-05-22 05:00:14.021298000 +0200
@@ -0,0 +1,2 @@
+# FIXME: pid 61155 SIGABRT (signal 6). <0> expected but was <6>.
+exclude :test_rlimit_nofile, 'fails on kfreebsd-i386'
--- /dev/null	2018-05-22 05:20:46.0 +0200
+++ b/debian/tests/excludes/kfreebsd-i386/TestRubyOptions.rb	2018-05-22 01:29:57.477214000 +0200
@@ -0,0 +1,3 @@
+# Output format of ps is different?
+exclude :test_set_program_name, 'fails on kFreeBSD'
+exclude :test_setproctitle, 'fails on kFreeBSD'
--- /dev/null	2018-05-22 05:21:01.0 +0200
+++ b/debian/tests/excludes/kfreebsd-i386/TestSocket_UNIXSocket.rb	2018-05-22 01:29:57.477937000 +0200
@@ -0,0 +1,2 @@
+# Output format of socket:LOCAL_CREDS differs?
+exclude :test_sendcred_sockcred, 'fails on kFreeBSD'

Bug#899275: epiphany-browser: Opening a new tab doesn't raise the window in XWayland

[Fina Wilke]

Package: epiphany-browser
Version: 3.28.1-1+b1
Severity: normal

Gnome Web doesn't raise the window to the top when clicking a link in another
application that causes it to open a new tab instead of a new window.

This behavior is inconsistent with the way it behaves when Web is closed. When
Web is closed the clicked link will be opened in the foreground.

Steps to reproduce:
1. Open gnome-web with any webpage
2. Open evolution and click on a link in an email message

Observed behavior:
The link opens in the background in a new tab

Expected behavior:
gnome-web should raise to the top of the window stack to display the newly
opened link



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (750, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages epiphany-browser depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.8-2
ii  dbus-x11 [dbus-session-bus]   1.12.8-2
ii  epiphany-browser-data 3.28.1-1
ii  gsettings-desktop-schemas 3.28.0-1
ii  iso-codes 3.79-1
ii  libc6 2.27-3
ii  libcairo2 1.15.10-3
ii  libgcr-base-3-1   3.28.0-1
ii  libgcr-ui-3-1 3.28.0-1
ii  libgdk-pixbuf2.0-02.36.11-2
ii  libglib2.0-0  2.56.1-2
ii  libgmp10  2:6.1.2+dfsg-3
ii  libgtk-3-03.22.29-3
ii  libhogweed4   3.4-1
ii  libicu60  60.2-6
ii  libjavascriptcoregtk-4.0-18   2.20.2-1+b1
ii  libjson-glib-1.0-01.4.2-4
ii  libnettle63.4-1
ii  libnotify40.7.7-3
ii  libpango-1.0-01.42.0-1
ii  libsecret-1-0 0.18.6-1
ii  libsoup2.4-1  2.62.1-1
ii  libsqlite3-0  3.23.1-1
ii  libwebkit2gtk-4.0-37  2.20.2-1+b1
ii  libxml2   2.9.4+dfsg1-6.1

Versions of packages epiphany-browser recommends:
ii  browser-plugin-evince  3.28.2-1
ii  ca-certificates20170717
ii  evince 3.28.2-1
ii  libwebkit2gtk-4.0-37-gtk2  2.20.2-1+b1
ii  yelp   3.28.1-1

epiphany-browser suggests no packages.

-- debconf-show failed

Bug#899274: KMail does not always remember the desired message list columns

[Steve M. Robbins]

Package: kmail
Version: 4:17.12.3-1
Severity: normal

In the folder list, KMail is able to display several columns: Name,
Unread, Total, and Size.  I have turned off all but Name.

Kmail regularly seems to ignore my wishes and displays all four
columns when I re-start.  But this does not happen all the time.




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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:17.12.3-2+b1
ii  kdepim-runtime   4:17.12.3-2
ii  kio  5.45.0-1
ii  libc62.27-3
ii  libgcc1  1:8.1.0-3
ii  libgpgmepp6  1.11.1-1
ii  libkf5akonadiagentbase5  4:17.12.3-2+b1
ii  libkf5akonadicontact54:17.12.3-2
ii  libkf5akonadicore5abi1   4:17.12.3-2+b1
ii  libkf5akonadimime5   4:17.12.3-1
ii  libkf5akonadisearch-bin  4:17.12.3-1
ii  libkf5akonadisearch-plugins  4:17.12.3-1
ii  libkf5akonadisearchdebug54:17.12.3-1
ii  libkf5akonadisearchpim5  4:17.12.3-1
ii  libkf5akonadiwidgets5abi14:17.12.3-2+b1
ii  libkf5bookmarks5 5.45.0-1
ii  libkf5calendarcore5abi1  4:17.12.3-1
ii  libkf5calendarutils5 4:17.12.3-1
ii  libkf5codecs55.45.0-1
ii  libkf5completion55.45.0-1
ii  libkf5configcore55.45.0-1
ii  libkf5configgui5 5.45.0-1
ii  libkf5configwidgets5 5.45.0-1
ii  libkf5contacts5  4:17.12.3-1
ii  libkf5coreaddons55.45.0-1
ii  libkf5crash5 5.45.0-1
ii  libkf5dbusaddons55.45.0-1
ii  libkf5followupreminder5  4:17.12.3-1
ii  libkf5grantleetheme-plugins  17.12.3-1
ii  libkf5gravatar5abi1  4:17.12.3-1
ii  libkf5guiaddons5 5.45.0-1
ii  libkf5i18n5  5.45.0-1
ii  libkf5iconthemes55.45.0-1
ii  libkf5identitymanagement517.12.3-1
ii  libkf5itemmodels55.45.0-1
ii  libkf5itemviews5 5.45.0-1
ii  libkf5jobwidgets55.45.0-1
ii  libkf5kcmutils5  5.45.0-1
ii  libkf5kiocore5   5.45.0-1
ii  libkf5kiofilewidgets55.45.0-1
ii  libkf5kiowidgets55.45.0-1
ii  libkf5kontactinterface5  17.12.3-1
ii  libkf5ksieveui5  4:17.12.3-1
ii  libkf5libkdepim-plugins  4:17.12.3-1
ii  libkf5libkdepim5 4:17.12.3-1
ii  libkf5libkdepimakonadi5  4:17.12.3-1
ii  libkf5libkleo5   4:17.12.3-2
ii  libkf5mailcommon5abi14:17.12.3-1
ii  libkf5mailtransport5 17.12.3-1
ii  libkf5mailtransportakonadi5  17.12.3-1
ii  libkf5messagecomposer5   4:17.12.3-1
ii  libkf5messagecore5   4:17.12.3-1
ii  libkf5messagelist5   4:17.12.3-1
ii  libkf5messageviewer5 4:17.12.3-1
ii  libkf5mime5abi1  17.12.3-2
ii  libkf5mimetreeparser54:17.12.3-1
ii  libkf5notifications5 5.45.0-2
ii  libkf5notifyconfig5  5.45.0-2
ii  libkf5parts5 5.45.0-1
ii  libkf5pimcommon5abi1 4:17.12.3-1
ii  libkf5pimcommonakonadi5  4:17.12.3-1
ii  libkf5pimtextedit5abi1   17.12.3-2
ii  libkf5sendlater5 4:17.12.3-1
ii  libkf5service-bin5.45.0-1
ii  libkf5service5   5.45.0-1
ii  libkf5sonnetui5  5.45.0-1
ii  libkf5templateparser54:17.12.3-1
ii  libkf5textwidgets5   5.45.0-2
ii  libkf5tnef5  4:17.12.3-1
ii  libkf5wallet-bin 5.45.0-1
ii  libkf5wallet55.45.0-1
ii  libkf5webengineviewer5   4:17.12.3-1
ii  libkf5widgetsaddons5 5.45.0-1
ii  libkf5windowsystem5  5.45.0-1
ii  libkf5xmlgui55.45.0-1
ii  libqgpgme7   1.11.1-1
ii  libqt5core5a 5.10.1+dfsg-6+b1
ii  libqt5dbus5  5.10.1+dfsg-6+b1
ii  libqt5gui5   5.10.1+dfsg-6+b1
ii  libqt5network5   5.10.1+dfsg-6+b1
ii  libqt5widgets5   5.10.1+dfsg-6+b1
ii  libqt5xml5   5.10.1+dfsg-6+b1
ii  libstdc++6   8.1.0-3

Versions of packages kmail recommends:
ii  accountwizard   4:17.12.3-1
ii  gnupg   2.2.5-1
ii  kdepim-addons   17.12.3-2
ii  kdepim-themeeditors 4:17.12.3-1
ii  mbox-importer   4:17.12.3-1
ii  pim-data-exporter   4:17.12.3-1
ii  pim-sieve-editor4:17.12.3-1
ii  pinentry-gnome3 [pinentry-x11]  1.1.0-1+b1
ii  pinentry-gtk2 [pinentry-x11]1.1.0-1+b1
ii  pinentry-qt [pinentry-x11]  1.1.0-1+b1

Versions of packages kmail suggests:
pn  clamav
ii  crm114

Bug#824904: bugs.debian.org: auto-fix common usertags mistakes

[Paul Wise]

Control: reassign -1 qa.debian.org
Control: retitle -1 qa.debian.org: detect common usertags mistakes

Thinking about this some more I think that this belongs with the Debian
QA services where it won't cause work for the BTS maintainers.

The script recently discovered some debian-perl usertags typos and I
discovered a bug in one of the regexen. I've attached a fixed version 
of the script. I'll be working on integrating it into qa.debian.org.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


debian-usertags-tests
Description: application/shellscript


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

Bug#872937: aspell: random crash (SIGABRT) when run from git gui

[Paul Wise]

Package: aspell
Version: 0.60.7~20110707-5
Followup-For: Bug #872937

I got another crash with the same backtrace:

$ gdb -batch -n -ex 'set pagination off' -ex bt -ex 'thread apply all bt full' 
--core 
/var/crash/1000/13318-1000-1000-6-1526886557-chianamo--usr-bin-aspell.core 
/usr/bin/aspell
[New LWP 13318]
Core was generated by `aspell --mode=none --encoding=utf-8 pipe'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7fd57600a231 in __GI_abort () at abort.c:79
#2  0x7fd57604b7b7 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x7fd5761540f3 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x7fd576051d5a in malloc_printerr (str=str@entry=0x7fd5761522fe 
"free(): invalid pointer") at malloc.c:5350
#4  0x7fd576055c0e in free_check (mem=, caller=) at hooks.c:274
#5  0x5572da7cf1db in acommon::String::~String (this=0x7ffd037e2fd0, 
__in_chrg=) at ./common/string.hpp:251
#6  pipe () at prog/aspell.cpp:868
#7  0x5572da7c78da in main (argc=4, argv=0x7ffd037e33c8) at 
prog/aspell.cpp:417

Thread 1 (LWP 13318):
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
set = {__val = {0, 146, 140554805041904, 8506698757163712523, 
93951811157568, 93951811180384, 93951811518784, 151, 93951811521584, 
93951811429568, 1258, 93951811164496, 0, 1024, 8, 0}}
pid = 
tid = 
#1  0x7fd57600a231 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x5572dc589e30, sa_sigaction 
= 0x5572dc589e30}, sa_mask = {__val = {93951782435984, 140554807320384, 
140724662054448, 93951782435968, 140554784824195, 93951811197734, 
140554804736095, 0, 93951811138720, 140724662054448, 140724662054224, 0, 0, 0, 
140724662054208, 140724662054496}}, sa_flags = 58600768, sa_restorer = 0x1000}
sigs = {__val = {32, 0 }}
#2  0x7fd57604b7b7 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x7fd5761540f3 "%s\n") at ../sysdeps/posix/libc_fatal.c:181
ap = {{gp_offset = 24, fp_offset = 21874, overflow_arg_area = 
0x7ffd037e2e70, reg_save_area = 0x7ffd037e2e00}}
fd = 
list = 
nlist = 
cp = 
written = 
#3  0x7fd576051d5a in malloc_printerr (str=str@entry=0x7fd5761522fe 
"free(): invalid pointer") at malloc.c:5350
No locals.
#4  0x7fd576055c0e in free_check (mem=, caller=) at hooks.c:274
p = 
#5  0x5572da7cf1db in acommon::String::~String (this=0x7ffd037e2fd0, 
__in_chrg=) at ./common/string.hpp:251
No locals.
#6  pipe () at prog/aspell.cpp:868
token = 
guesses = { = {_vptr.OStream = 0x5572da9e3c90 }, begin_ = 0x5572dc5498b0 ", C+EST", '\237' , "\207", end_ = 0x5572dc5498b7 '\237' , "\207", 
storage_end_ = 0x5572dc5498f0 "\207", static npos = 2147483647}
guess = { = {_vptr.OStream = 0x5572da9e3c90 }, begin_ = 0x5572dc549bb0 "C+EST", end_ = 
0x5572dc549bb5 "", storage_end_ = 0x5572dc549bf0 , 
static npos = 2147483647}
ci = 
suggestions = 
casep = 
terse_mode = 
do_time = false
suggest = true
include_guesses = false
start = 71893
finish = 73106
ret = 
speller = 0x5572dc547e40
real_speller = 0x5572dc547e40
iconv = { = {conv = 0x5572dc54c8b0, buf0 = 
{ = {> = std::vector of length 4, capacity 16 = 
{{chr = 67, width = 1}, {chr = 69, width = 1}, {chr = 83, width = 1}, {chr = 
84, width = 1}}, }, }, buf = 
{ = {_vptr.OStream = 0x5572da9e3c90 }, begin_ = 0x5572dc55e0b0 "CEST", end_ = 0x5572dc55e0b4 "", 
storage_end_ = 0x5572dc55e0f0 "\250", static npos = 2147483647}}, conv_obj = 
{ptr = 0x5572dc54c8b0}}
oconv = { = {conv = 0x5572dc54c950, buf0 = 
{ = {> = std::vector of length 5, capacity 8 = 
{{chr = 67, width = 1}, {chr = 43, width = 1}, {chr = 69, width = 1}, {chr = 
83, width = 1}, {chr = 84, width = 1}}, }, }, 
buf = { = {_vptr.OStream = 0x5572da9e3c90 }, begin_ = 0x5572dc54d8e0 "C+EST", end_ = 0x5572dc54d8e5 
"", storage_end_ = 0x5572dc54d920 "\201``\a!", static npos = 2147483647}}, 
conv_obj = {ptr = 0x5572dc54c950}}
mb_len = {encoding = acommon::MBLen::UTF8}
status_fun_inf = {real_speller = 0x5572dc547e40, oconv = 
{ = {conv = 0x5572dc54c9f0, buf0 = 
{ = {> = std::vector of length 0, capacity 0, 
}, }, buf = { = 
{_vptr.OStream = 0x5572da9e3c90 }, begin_ = 0x0, 
end_ = 0x0, storage_end_ = 0x0, static npos = 2147483647}}, conv_obj = {ptr = 
0x5572dc54c9f0}}, verbose = false}
print_star = @0x7ffd037e3110: false
checker = {ptr = 

Bug#899273: ITP: fonts-ibm-plex -- IBM's corporate typeface

[Zebulon McCorkle]

On Tue, May 22, 2018 at 09:53:19AM +0800, Paul Wise wrote:
> FYI, this cannot go to Debian main:

Alright, from reading that it looks like it'll have to be contrib?

> Also, due to the RFN requirements it probably would have to be renamed
> if packaged in Debian.

So, IceCat style? What's the process around that?

-- 
Zebulon McCorkle
Email: zebmccor...@zeb.fun
IRC:
 - zebmccorkle@Freenode
 - zebmccorkle@OFTC
 - zeb@EsperNet
 - zeb@hackint
 - zeb@PdgnCo
 - zeb@EFNet
PGP: 803A 0F47 82AD DDEA 46BE  055F F8F9 DB8C 1A54 6398
 (Zebulon McCorkle )


signature.asc
Description: PGP signature

Bug#804946: Processed: retitle to RFP: webwork-pg -- Problem rendering engine for WeBWorK

[Doug Torrance]

Control: retitle -1 ITP: webwork-pg -- Problem rendering engine for WeBWorK
Control: owner -1 !

On 05/21/2018 12:21 PM, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
>> retitle 804946 RFP: webwork-pg -- Problem rendering engine for WeBWorK
> Bug #804946 [wnpp] ITP: webwork-pg -- Problem rendering engine for WeBWorK
> Changed Bug title to 'RFP: webwork-pg -- Problem rendering engine for 
> WeBWorK' from 'ITP: webwork-pg -- Problem rendering engine for WeBWorK'.
>> noowner 804946
> Bug #804946 [wnpp] RFP: webwork-pg -- Problem rendering engine for WeBWorK
> Removed annotation that Bug was owned by Doug Torrance 
> .
>> stop

I still intend to package WeBWorK.

Bug#899273: ITP: fonts-ibm-plex -- IBM's corporate typeface

[Paul Wise]

On Mon, 21 May 2018 20:40:39 -0500 Zebulon McCorkle wrote:

> * Package name: fonts-ibm-plex
>   Version : 1.0.2
>   Upstream Author : IBM Corp.
> * URL : https://www.ibm.com/plex/
> * License : SIL-1.1
>   Programming Lang: FontLab Studio 5
>   Description : IBM's corporate typeface

FYI, this cannot go to Debian main:

https://github.com/IBM/plex/issues/98

Also, due to the RFN requirements it probably would have to be renamed
if packaged in Debian.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

[Antonio Terceiro]

Control: forwarded -1 
https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests/1

On Sun, May 20, 2018 at 06:15:08PM -0300, Antonio Terceiro wrote:
> Control: reopen -1
> 
> On Sun, May 20, 2018 at 10:32:38PM +0530, Vasudev Kamath wrote:
> > Antonio Terceiro  writes:
> > > 2) revert the changes in fonts-font-awesome in unstable, upload the
> > > new release to experimental, and give people a few months to adapt.
> > 
> > I'm okay with this solution. I've currently fixed the broken links and
> > uploaded the fixes. If you would like more time to adapt to the version
> > 5 of font, I can request its removal from unstable and re-upload old
> > version to unstable and then upload this new version to experimental.
> 
> There is no such thing as requesting removal. you need to upload it with
> a higher version number, but with the old contents. Something like
> 5.0.10+really4.7.0-1.
> 
> Or maybe not. I will try if I can work things out with the new version,
> so expect a few patches.
> 
> For now I'm reopening this bug (which was not really fixed by your -3
> upload), and let's see what I can get.

So here it is:
https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests/1

This merge request fixes usage of v5, and add a backwards compatibility
layer for the v4 when used with CSS (which was the only option in v4
AFAICT). It also adds autopkgtest to automatically test that the needed
files are in the right places both for v5 and for v4.

LESS and SCSS are not handled.


signature.asc
Description: PGP signature

Bug#899273: ITP: fonts-ibm-plex -- IBM's corporate typeface

[Zebulon McCorkle]

Package: wnpp
Severity: wishlist
Owner: Zebulon McCorkle 

* Package name: fonts-ibm-plex
  Version : 1.0.2
  Upstream Author : IBM Corp.
* URL : https://www.ibm.com/plex/
* License : SIL-1.1
  Programming Lang: FontLab Studio 5
  Description : IBM's corporate typeface

Meet IBM Plex, our new corporate typeface. It’s global, it’s versatile
and it’s distinctly IBM.

We designed Plex carefully to both meet our needs as a global tech company
and express who we are as people. It took two years and a lot of work to
get here, but today we have a signature typeface we’re proud and excited
to share with the world. Plex is an open-source project (OFL) and free to
download and use. The Plex family comes in a Sans, Serif, Mono and Sans
Condensed, all with roman and true italics. The fonts have been designed
to work well in user interface (UI) environments as well as other mediums.
This project provides all source files and file formats to support most
typographical situations.

I will need a sponsor and will be posting an RFS to the appropriate
package.

-- 
Zebulon McCorkle
Email: zebmccor...@zeb.fun
IRC:
 - zebmccorkle@Freenode
 - zebmccorkle@OFTC
 - zeb@EsperNet
 - zeb@hackint
 - zeb@PdgnCo
 - zeb@EFNet
PGP: 803A 0F47 82AD DDEA 46BE  055F F8F9 DB8C 1A54 6398
 (Zebulon McCorkle )


signature.asc
Description: PGP signature

Bug#899272: sssd fails to look up ONE specific group

[Daniel Lakeland]

Package: sssd
Version: 1.16.1-1+b1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

install and configure sssd

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

look up one specific group, happens to be the smallest gid in my ldap 
directory:

first we look it up by gid, and that works

root@pico:~# getent group 1000
dlakelan:*:1000:

immediately after we try to look it up by name, and it fails

root@pico:~# getent group dlakelan



Here's an edited version of my sssd, edited for privacy
[sssd]
config_file_version = 2
services = nss,pam
#services = nss
# SSSD will not start if you do not configure any domains.
# Add new domain configurations as [domain/] sections, and
# then add the list of domains (in the order you want them to be
# queried) to the "domains" attribute below and uncomment it.
domains = mydomain

[nss]

[pam]

[domain/mydomain]
lookup_family_order = ipv4_only
id_provider = ldap
auth_provider = krb5
ldap_schema=rfc2307
ldap_uri = ldap://domain0.mydomain.com, ldap://domain1.mydomain.com
ldap_search_base = dc=mydomain,dc=com
cache_credentials = true
krb5_realm = MYDOMAIN.COM
;ldap_id_use_start_tls = true
;ldap_tls_reqcert = hard
chpass_provider = krb5
krb5_store_password_if_offline = true
dns_discovery_domain = mydomain.com
krb5_ccname_template = /tmp/krb5cc_%U
;use_fully_qualified_names = true
min_id=1000

---

It has the flavor of an off-by-one type bug, since every other group 
with higher gid number is looked up both directions just fine.

It is, however, highly annoying


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

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

Versions of packages sssd depends on:
ii  python3-sss  1.16.1-1+b1
ii  sssd-ad  1.16.1-1+b1
ii  sssd-common  1.16.1-1+b1
ii  sssd-ipa 1.16.1-1+b1
ii  sssd-krb51.16.1-1+b1
ii  sssd-ldap1.16.1-1+b1
ii  sssd-proxy   1.16.1-1+b1

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information

Bug#899269: [Pkg-samba-maint] Bug#899269: Acknowledgement (samba: upgrade of samba causes smbd crash with "failed to setup guest info")

[Daniel Lakeland]

On 05/21/2018 04:06 PM, Andrew Bartlett wrote:


Can you turn up the log level until it gives a more useful answer?



Debug logs at log level 6 attached

On this machine the user "nobody" is listed in an LDAP directory, and 
sssd connects to that ldap directory. This seems to work fine on the 
command line:


root@pico:~# getent passwd nobody
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin


root@pico:~# getent group nogroup
nogroup:x:65534:

And it worked fine before on previous version of samba, would have been 
around 4.5.x or something like that (Debian stable?)



...
[2018/05/21 18:00:43.939048,  3] ../source3/smbd/server.c:1840(main)
  Becoming a daemon.
[2018/05/21 18:00:43.939552,  5] 
../source3/passdb/pdb_interface.c:79(smb_register_passdb)
  Attempting to register passdb backend smbpasswd
[2018/05/21 18:00:43.939601,  5] 
../source3/passdb/pdb_interface.c:92(smb_register_passdb)
  Successfully added passdb backend 'smbpasswd'
[2018/05/21 18:00:43.939628,  5] 
../source3/passdb/pdb_interface.c:79(smb_register_passdb)
  Attempting to register passdb backend tdbsam
[2018/05/21 18:00:43.939657,  5] 
../source3/passdb/pdb_interface.c:92(smb_register_passdb)
  Successfully added passdb backend 'tdbsam'
[2018/05/21 18:00:43.939683,  5] 
../source3/passdb/pdb_interface.c:79(smb_register_passdb)
  Attempting to register passdb backend samba_dsdb
[2018/05/21 18:00:43.939711,  5] 
../source3/passdb/pdb_interface.c:92(smb_register_passdb)
  Successfully added passdb backend 'samba_dsdb'
[2018/05/21 18:00:43.939737,  5] 
../source3/passdb/pdb_interface.c:79(smb_register_passdb)
  Attempting to register passdb backend samba4
[2018/05/21 18:00:43.939763,  5] 
../source3/passdb/pdb_interface.c:92(smb_register_passdb)
  Successfully added passdb backend 'samba4'
[2018/05/21 18:00:43.939794,  5] 
../source3/passdb/pdb_interface.c:79(smb_register_passdb)
  Attempting to register passdb backend ldapsam
[2018/05/21 18:00:43.939822,  5] 
../source3/passdb/pdb_interface.c:92(smb_register_passdb)
  Successfully added passdb backend 'ldapsam'
[2018/05/21 18:00:43.939848,  5] 
../source3/passdb/pdb_interface.c:79(smb_register_passdb)
  Attempting to register passdb backend NDS_ldapsam
[2018/05/21 18:00:43.939875,  5] 
../source3/passdb/pdb_interface.c:92(smb_register_passdb)
  Successfully added passdb backend 'NDS_ldapsam'
[2018/05/21 18:00:43.939902,  5] 
../source3/passdb/pdb_interface.c:155(make_pdb_method_name)
  Attempting to find a passdb backend to match tdbsam (tdbsam)
[2018/05/21 18:00:43.939929,  5] 
../source3/passdb/pdb_interface.c:176(make_pdb_method_name)
  Found pdb backend tdbsam
[2018/05/21 18:00:43.939963,  5] 
../source3/passdb/pdb_interface.c:187(make_pdb_method_name)
  pdb backend tdbsam has a valid init
[2018/05/21 18:00:43.943293,  5] 
../lib/dbwrap/dbwrap.c:130(dbwrap_lock_order_lock)
  dbwrap_lock_order_lock: check lock order 1 for 
/var/run/samba/smbXsrv_version_global.tdb
[2018/05/21 18:00:43.943451,  5] 
../lib/dbwrap/dbwrap.c:159(dbwrap_lock_order_unlock)
  dbwrap_lock_order_unlock: release lock order 1 for 
/var/run/samba/smbXsrv_version_global.tdb
[2018/05/21 18:00:43.946659,  3] ../source3/lib/util_procid.c:54(pid_to_procid)
  pid_to_procid: messaging_dgm_get_unique failed: No such file or directory
[2018/05/21 18:00:43.947453,  5] 
../source3/lib/messages.c:678(messaging_register)
  Registering messaging pointer for type 794 - private_data=0x55c82483c130
[2018/05/21 18:00:43.947543,  5] 
../source3/lib/messages.c:678(messaging_register)
  Registering messaging pointer for type 795 - private_data=0x55c82483c130
[2018/05/21 18:00:43.947571,  5] 
../source3/lib/messages.c:678(messaging_register)
  Registering messaging pointer for type 796 - private_data=0x55c82483c130
[2018/05/21 18:00:43.948791,  5] 
../source3/lib/messages.c:678(messaging_register)
  Registering messaging pointer for type 13 - private_data=0x55c824837f70
[2018/05/21 18:00:43.948896,  5] 
../source3/lib/messages.c:678(messaging_register)
  Registering messaging pointer for type 788 - private_data=0x55c824837f70
[2018/05/21 18:00:43.948925,  5] 
../source3/lib/messages.c:678(messaging_register)
  Registering messaging pointer for type 785 - private_data=(nil)
[2018/05/21 18:00:43.949133,  5] 
../source3/lib/messages.c:678(messaging_register)
  Registering messaging pointer for type 789 - private_data=0x55c8248376f0
[2018/05/21 18:00:43.949976,  5] ../source3/lib/username.c:181(Get_Pwnam_alloc)
  Finding user nobody
[2018/05/21 18:00:43.950016,  5] 
../source3/lib/username.c:120(Get_Pwnam_internals)
  Trying _Get_Pwnam(), username as lowercase is nobody
[2018/05/21 18:00:43.951037,  5] 
../source3/lib/username.c:159(Get_Pwnam_internals)
  Get_Pwnam_internals did find user [nobody]!
[2018/05/21 18:00:43.951106,  5] ../source3/lib/username.c:181(Get_Pwnam_alloc)
  Finding user PICO\nobody
[2018/05/21 18:00:43.951135,  5] 
../source3/lib/username.c:120(Get_Pwnam_internals)
  Trying _Get_Pwnam(), username as 

Bug#894481: nmu diff

[Unit 193]

Howdy,

A solution to this problem is in the debdiff attached, it is easily 
backported as it leaves support for the old location of laptop-detect, but 
otherwise will use the new location.  This is also what has been uploaded to 
Ubuntu.


~Unit 193
Unit193 @ OFTC
Unit193 @ freenodediff -Nru numlockx-1.2/debian/55numlockx numlockx-1.2/debian/55numlockx
--- numlockx-1.2/debian/55numlockx  2014-08-11 06:08:41.0 -0400
+++ numlockx-1.2/debian/55numlockx  2018-05-20 11:44:06.0 -0400
@@ -20,7 +20,11 @@
 ;;
 *)
 NUMLOCK=on
-ltd=/usr/sbin/laptop-detect
+if [ -x /usr/sbin/laptop-detect ];then
+ltd=/usr/sbin/laptop-detect
+else
+ltd=/usr/bin/laptop-detect
+fi
 [ ! -x $ltd ] || ! $ltd || NUMLOCK=off
 # Enable numlock for USB keyboard on laptop
 if [ -f /bin/udevadm ] ; then
diff -Nru numlockx-1.2/debian/changelog numlockx-1.2/debian/changelog
--- numlockx-1.2/debian/changelog   2014-08-11 06:08:41.0 -0400
+++ numlockx-1.2/debian/changelog   2018-05-20 11:47:27.0 -0400
@@ -1,3 +1,11 @@
+numlockx (1.2-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * d/55numlockx: Adjust to find laptop-detect after move to /usr/bin
+(Closes: #894481)
+
+ -- Unit 193   Sun, 20 May 2018 13:44:27 -0400
+
 numlockx (1.2-7) unstable; urgency=medium
 
   * Rewrite USB keyboard detection using pure udev (Closes: #757475).

Bug#896295: Tensorflow is missing

[Stephen Sinclair]

The upstream must have changed the default backend which is not surprising,
it should be fixable with a patch. I can look into it in a few days when I
am back from vacation and in front of a computer again. The autotestpkg
tests set KERAS_BACKEND=theano which is why this was missed. In the
meantime users can set this environment variable similarly as a
work-around. I don't really like changing upstream default behaviour but
perhaps in this case it is warranted as an interim solution.

Regarding Tensorflow packaging I do not know, someone on debian-science
mentioned difficulties with its build system. I do hope these are
resolvable but it seems to be a big issue.


On Mon, May 21, 2018, 1:16 AM Andreas Tille  wrote:

> Hi,
>
> the description says:
>
>  ...  Alternatively, Keras could run on Google's
>  TensorFlow (not yet available in Debian, but coming up).
>
> Is there some estimated time frame to package TensorFlow?
>
> If not please try to deactivate this alternative since the package does
> not work as this bug report explains.
>
> Kind regards
>
>   Andreas.
>
> --
> http://fam-tille.de
>

Bug#472199: need a tool to create dep-5 file from source file

[Lars Kruse]

Package: licensecheck
Followup-For: Bug #472199

Dear Maintainer,

currently the following methods for creating a DEP-5 compliant copyright
file:

 debmake -c
 cme check dpkg-copyright
 licensecheck -r --merge-licenses --deb-machine .

Thus this wishlist bug can probably be closed.

Cheers,
Lars

Bug#899267: ruby2.5: 89267: Updated patches for directory kfreebsd-amd64

[Svante Signell]

Attached are updated patches for directoriy debian/tests/excludes/kfreeebsd-
amd64 with the a/ removed from /dev/null and s/exclude/excludes/

kfreebsd-i386 needs one more file in debian/tests/exclude to build properly. An
updated kfree-i386.diff will be submitted soon. 

Thanks!--- /dev/null	2018-05-21 16:47:03.0 +0200
+++ b/debian/tests/excludes/kfreebsd-amd64/TestGemSpecification.rb	2018-05-19 00:48:47.195961000 +0200
@@ -0,0 +1,2 @@
+# Actual is one day earlier than Expected
+exclude :test_date_equals_time, 'fails on kFreeBSD'
--- /dev/null	2018-05-21 16:48:02.0 +0200
+++ b/debian/tests/excludes/kfreebsd-amd64/TestRubyOptions.rb	2018-05-21 16:31:16.537416000 +0200
@@ -0,0 +1,3 @@
+# Output format of ps is different?
+exclude :test_set_program_name, 'fails on kFreeBSD'
+exclude :test_setproctitle, 'fails on kFreeBSD'
--- /dev/null	2018-05-21 16:48:15.0 +0200
+++ b/debian/tests/excludes/kfreebsd-amd64/TestSocket_UNIXSocket.rb	2018-05-21 16:38:24.597803000 +0200
@@ -0,0 +1,2 @@
+# Output format of socket:LOCAL_CREDS differs?
+exclude :test_sendcred_sockcred, 'fails on kFreeBSD'

Bug#886887: unreproducible last crashing

[Paul Szabo]

Dear Andreas,

You are right in that the problem does not seem to occur anymore.

The crash seems to have been within libc.so.6 and that was updated
since my report: package libc6 changed from version 2.24-11+deb9u1
to 2.24-11+deb9u3 . (The last command itself was updated also, package
util-linux changed from version 2.29.2-1 to 2.29.2-1+deb9u1.)
Running the old "last" (but with the current libc.so.6) does not
reproduce the problem, and I do not want to downgrade libc6 to test.

I guess you may close this bug.

Thanks, Paul
--
Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Bug#899269: [Pkg-samba-maint] Bug#899269: Acknowledgement (samba: upgrade of samba causes smbd crash with "failed to setup guest info")

[Andrew Bartlett]

On Mon, 2018-05-21 at 15:50 -0700, Daniel Lakeland wrote:
> Sorry if that bug report is hard to read, debbugs crashed, so I tried to just 
> re-send the temporary file.
> The important bits are that after upgrade, smbd doesn't start up and says:
> [2018/05/21 14:57:03.582775,  0] 
> ../source3/auth/auth_util.c:1372(make_new_session_info_guest)
>   create_local_token failed: NT_STATUS_NO_MEMORY
> [2018/05/21 14:57:03.582858,  0] ../source3/smbd/server.c:1993(main)
>   ERROR: failed to setup guest info.
> 
> 
> In the log files

Can you turn up the log level until it gives a more useful answer?

Thanks,

Andrew Bartlett

-- 
Andrew Bartlett
https://samba.org/~abartlet/
Authentication Developer, Samba Team https://samba.org
Samba Development and Support, Catalyst IT   
https://catalyst.net.nz/services/samba

Bug#879619: Autopkgtest for ncbi-tools6

[Liubov Chuprikova]

Hi Aaron, Hi Andreas,

Please, have a look at my two last commits (
https://salsa.debian.org/med-team/ncbi-tools6/commits/master). Actually,
the first one was made a month ago.

On Tue, 17 Apr 2018 at 03:48 Aaron M. Ucko  wrote:

> Liubov Chuprikova  writes:
>
> > At the moment, the following commands are still lacking tests:
> >
> >- *asn2ff*, *gbseqget*, *findspl* (their output indicates they are
> >obsolete and/or unsupported)
>
> - asn2ff plays the same general role as asn2flat, and should be possible to
>   test similarly.
>

I tried to run it in a similar way to *asn2asn*. It throws an error which
starts with "The asn2ff flatfile generator is obsolete and unsupported.  Please
switch to using asn2gb/SeqEntryToGnbk in the future."

- gbseqget is like insdseqget, but formally uses GenBank-specific
>   notation; as such, it requires network access.


I added a test for *gbseqget* within if statement which checks for internet
connection.


> - findspl also requires network access, and will need to be patched in the
>
  same fashion as taxblast; I'll take care of it when I get a chance.
>
> >- *asndhuff*, *nps2gps* (I can't figure out what kind of inputs they
> >require)
>
> - I'm not sure where you'd find input for asndhuff.
> - nps2gps takes a text Bioseq-set or Seq-entry of class nuc-prot, as
>   obtained by (for instance) idfetch -g1234.


A test for *nps2gps* also presents now.


> >- *fa2htgs*, *spidey* (they look too complicated for me and require
> much
>
>time to understand how they work)
>
> That's fair.  You can always come back to them later if you feel inspired.
>

I have also finished with *spidey* and *fa2htgs* today.


> >- *taxblast* doesn't generate an output file and only generates an
> >*incomplete* html
>
> I'm not sure what's up with that, but as previously noted, it requires
> network access anyway.
>
> >- *errhdr*, *sortbyquote* (I can't figure out even what they are
> >supposed to do)
>
> - errhdr is a developer tool, working with files of the format found in
>   errmsg/.
> - sortbyquote is also a developer tool, essentially a variant of sort
>   that ignores everything outside quotation marks (and generally has far
>   fewer options).



> I'm not sure any of these is critical to test, but some
>
should be relatively straightforward to work in at this point, and as
> noted I'm not quite ready to upload a new version anyway.
>

Aaron, thank you for the explanations! They helped me a lot!

Aaron, Andreas: what is your opinion about the whole test? Could we
consider it as completed?

With regards,
Liubov

Bug#897953: dvtm: Please stop shipping dvtm and dvtm-256color terminfo entries

[Thomas Dickey]

On Mon, May 21, 2018 at 11:28:23PM +0300, kact...@gnu.org wrote:
> 
> [2018-05-21 05:16] Thomas Dickey 
> > - Original Message -
> > | From: "Sven Joachim" 
> > | To: kact...@gnu.org
> > | Cc: 897...@bugs.debian.org, ncur...@packages.debian.org
> > | Sent: Monday, May 21, 2018 5:07:15 AM
> > | Subject: Re: Bug#897953: dvtm: Please stop shipping dvtm and 
> > dvtm-256color terminfo entries
> > | 
> > | On 2018-05-12 16:23 +0300, kact...@gnu.org wrote:
> > | 
> > | > control: tags -1 +pending
> > | >
> > | > [2018-05-05 08:29] Sven Joachim 
> > | >> In early 2017, the dvtm and dvtm-256color terminfo entries were
> > | >> added to
> > | >> ncurses upstream, and I would like to include them in the
> > | >> ncurses-term
> > | >> package, replacing the ones shipped currently in the dvtm package.
> > | >> 
> > | >> This requires coordinated uploads of dvtm and ncurses, adding a
> > | >> versioned Breaks/Replaces on dvtm to ncurses-term and a versioned
> > | >> dependency on ncurses-term to dvtm.
> > | >
> > | > Sure. I just uploaded dvtm_0.15-3, that depends on
> > | > ncurses-term (>> 6.1+20180210-2) into DELAYED/10.
> > | >
> > | > As such, I expect it to arrive at 2018/05/22. I propose you to make new
> > | > upload of ncurses-term with apporiate Breaks/Depends into DELAYED in
> > | > such way, that our packages arrive at same time.
> > | 
> > | Just uploaded ncurses 6.1+20180210-4 to DELAYED/1, thanks.
> > 
> > The package's versions of the terminfo entries have 2-3 errors in them.
> 
> Could you please elaborate? Which package have errors? Which errors? What and 
> by whom
> should be done to fix them?

I was referring to the dvtm package, which appears unnecessary after
rereading Sven's comment.

I made these changes when I added the terminal descriptions to ncurses (with
ncurses on the left):

comparing dvtm to dvtm.
AX: T, F.
kf22: '\E[24$', '\E[24$kfnd=\E[1~'.
kfnd: '\E[1~', -.
rs1: '\E>\E[1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H', 
'\E>\E[?1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H'.
comparing dvtm-256color to dvtm-256color.
AX: T, F.
pairs: 65536, 32767.
kf22: '\E[24$', '\E[24$kfnd=\E[1~'.
kfnd: '\E[1~', -.
rs1: '\E>\E[1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H', 
'\E>\E[?1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H'.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#899269: Acknowledgement (samba: upgrade of samba causes smbd crash with "failed to setup guest info")

[Daniel Lakeland]

Sorry if that bug report is hard to read, debbugs crashed, so I tried to just 
re-send the temporary file.

The important bits are that after upgrade, smbd doesn't start up and says:

[2018/05/21 14:57:03.582775,  0] 
../source3/auth/auth_util.c:1372(make_new_session_info_guest)
  create_local_token failed: NT_STATUS_NO_MEMORY
[2018/05/21 14:57:03.582858,  0] ../source3/smbd/server.c:1993(main)
  ERROR: failed to setup guest info.


In the log files

Bug#877612: fsck: A tiny part of the Spanish translation makes no sense

[Theodore Y. Ts'o]

On Mon, May 21, 2018 at 11:14:11PM +0200, Andreas Henriksson wrote:
> > 
> > In my case, for instance, when talking about inodes or blocks, the
> > 'fsck.ext4 -v' output reads:
> [...]
> 
> fsck.ext4 is not part of util-linux, so reassigning.
> 
> Please provide the necessary information as needed to this bug report.
> (Starting with which version of e2fsprogs you experienced this with.)

Hi Manolo,

E2fsprogs uses the Translation Project to support its translations[1].
As a result, I will send any patches or suggestions for improvement to
the relevant translation maintainer for the language.  If that person
is no longer active, I'll forward it to the Translation Project's
Language Team.

[1]  https://translationproject.org/domain/e2fsprogs.html

The current translator for the Spanish translation is Antonio Ceballos
.  In past few years he has done a great job
getting the Spanish translation for e2fsprogs from about 60%
translated to 100% translated.  The current translation file can be
seen here:

https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/po/es.po

If you would like to help make the Spanish translation better, I'm
sure Antonio would appreciate the help.  

Antonio, the specific suggestion Manolo made can be found here:

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

Regards,

- Ted

Bug#877612: fsck: A tiny part of the Spanish translation makes no sense

[Antonio Ceballos]

Hi Ted, Manolo,

Thanks for spotting this translation bug. I agree on Manolo's suggestion
and I have patched the translation straight away, You can find it here:

https://translationproject.org/PO-files/es/e2fsprogs-1.44.0-rc2.es.po

Please let me know if you find any other bug. The extensive use of an
expansion mechanism makes the translation of this package particularly
difficult.

Regards,
Antonio




On Tue, May 22, 2018 at 12:07 AM Theodore Y. Ts'o  wrote:

> On Mon, May 21, 2018 at 11:14:11PM +0200, Andreas Henriksson wrote:
> > >
> > > In my case, for instance, when talking about inodes or blocks, the
> > > 'fsck.ext4 -v' output reads:
> > [...]
> >
> > fsck.ext4 is not part of util-linux, so reassigning.
> >
> > Please provide the necessary information as needed to this bug report.
> > (Starting with which version of e2fsprogs you experienced this with.)
>
> Hi Manolo,
>
> E2fsprogs uses the Translation Project to support its translations[1].
> As a result, I will send any patches or suggestions for improvement to
> the relevant translation maintainer for the language.  If that person
> is no longer active, I'll forward it to the Translation Project's
> Language Team.
>
> [1]  https://translationproject.org/domain/e2fsprogs.html
>
> The current translator for the Spanish translation is Antonio Ceballos
> .  In past few years he has done a great job
> getting the Spanish translation for e2fsprogs from about 60%
> translated to 100% translated.  The current translation file can be
> seen here:
>
> https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/po/es.po
>
> If you would like to help make the Spanish translation better, I'm
> sure Antonio would appreciate the help.
>
> Antonio, the specific suggestion Manolo made can be found here:
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877612
>
> Regards,
>
> - Ted
>

Bug#879669: agetty: use full hardening flags

[Andreas Henriksson]

Control: tags -1 + moreinfo

Hello,

On Tue, Oct 24, 2017 at 10:13:27AM +0200, Christian Göttsche wrote:
> Package: util-linux
> Version: 2.30.2-0.1
> Tags: patch security
> 
> Please activate full hardening flags for the agetty binary, e.g. use
> `export DEB_BUILD_MAINT_OPTIONS = hardening=+all`.

Have you done any testing on how much breakage this causes?
What was your testing strategy and how does it make us sure
that it's safe to enable these build options?

Regards,
Andreas Henriksson

Bug#899270: tracker.debian.org: show people who have DM rights for a package even if not in Uploaders

[Mattia Rizzolo]

Package: tracker.debian.org

With the new system where DM ACLs are handled entirely within DAK's
database, a DM could have rights for a package even if they are not
involved in it (i.e. they are no in either Maintainers or Uploaders
fields).
I would like for tracker.d.o to list such people in the 'General'
section as well.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#899269: samba: upgrade of samba causes smbd crash with "failed to setup guest info"

[Daniel Lakeland]

Package: samba
Version: 2:4.8.2+dfsg-1
Severity: important

Dear Maintainer,

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

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

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

Content-Type: multipart/mixed; boundary="===1266396388651744079=="
MIME-Version: 1.0
From: Daniel Lakeland 
To: Debian Bug Tracking System 
Subject: samba: upgraded smbd fails to start with error: "failed to setup guest 
info"
Message-ID: <152694041170.5538.15063006303745186013.report...@pico.lan>
X-Mailer: reportbug 6.6.3
Date: Mon, 21 May 2018 15:06:51 -0700

This is a multi-part MIME message sent by reportbug.


--===1266396388651744079==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: samba
Version: 2:4.8.2+dfsg-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

upgraded samba package

   * What was the outcome of this action?

smbd fails to start with errors reported:

[2018/05/21 14:57:03.582775,  0] 
../source3/auth/auth_util.c:1372(make_new_session_info_guest)
  create_local_token failed: NT_STATUS_NO_MEMORY
[2018/05/21 14:57:03.582858,  0] ../source3/smbd/server.c:1993(main)
  ERROR: failed to setup guest info.


   * What outcome did you expect instead?

smbd should work as it did before upgrade


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


-- Package-specific info:
* /etc/samba/smb.conf present, and attached
* /var/lib/samba/dhcp.conf present, and attached

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

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

Versions of packages samba depends on:
ii  adduser   3.113+nmu3
ii  dpkg  1.17.25
ii  libattr1  1:2.4.47-2+b2
ii  libbsd0   0.7.0-2
ii  libc6 2.27-3
ii  libldb1   2:1.3.3-1
ii  libpam-modules1.1.8-3.1
ii  libpam-runtime1.1.8-3.1
ii  libpopt0  1.16-10
ii  libpython2.7  2.7.12-3+b1
ii  libtalloc22.1.1-2
ii  libtdb1   1.3.15-2
ii  libtevent00.9.34-1
ii  lsb-base  4.1+Debian13+nmu1
ii  procps2:3.3.9-9
ii  python2.7.11-2
ii  python-dnspython  1.12.0-1
ii  python-samba  2:4.8.2+dfsg-1
pn  python2.7:any 
pn  python:any
ii  samba-common  2:4.8.2+dfsg-1
ii  samba-common-bin  2:4.8.2+dfsg-1
ii  samba-libs2:4.8.2+dfsg-1
ii  tdb-tools 1.3.1-1

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.8.7-1+b1
ii  samba-dsdb-modules  2:4.8.2+dfsg-1
ii  samba-vfs-modules   2:4.8.2+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.3+dfsg-1
ii  bind9utils 1:9.11.3+dfsg-1
pn  ctdb   
pn  ldb-tools  
ii  ntp1:4.2.8p10+dfsg-5
pn  smbldap-tools  
pn  ufw
pn  winbind

-- no debconf information

--===1266396388651744079==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="smb.conf"

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#behaviour of Samba but the option is considered important
#enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 

#=== Global Settings ===

[global]

smb encrypt = auto
unix extensions = no

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = LAN

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS 

Bug#882117: non-assignment options for nfs mounts neither recognized in /etc/fstab nor /etc/nfsmount.conf

[Andreas Henriksson]

Control: reassign -1 nfs-common

The nfsmount.conf file, the (no)rdirplus mount option, etc is all part
of nfs-common (mount.nfs, etc.) so I suspect that's where you really
wanted to report this issue against. I'm thus reassigning it for you.
Please supply the relevant information as needed (starting with which
version of nfs-common package you're using).

Full initial bug report quoted below.

Regards,
Andreas Henriksson


On Sun, Nov 19, 2017 at 07:07:53AM +, Kraus, Sebastian wrote:
> Package: mount
> Version: 2.29.2-1
> 
> Dear package maintainers,
> 
> simple (non-assignment) nfs mount options like acl, (no)rdirplus are neither 
> recognized within /etc/fstab nor /etc/nfsmount.conf.
> We need to mount some NFS shares at bootup on our client machines, while 
> setting the nordirplus option being mandatory
> cause of severe caching problems against our nfs servers.
> Manually mounting the nfs shares on the commandline recognizes these 
> non-assignment options.
> Manual mounts are not feasible in our case.
> 
> Tested with Debian stretch 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) 
> x86_64
> 
> Package: linux-image-4.9.0-4-amd64  Version: 4.9.51-1 .
> 
> 
> 
> Regards
> 
> 
> Sebastian Kraus
> 
> 
> 
> 
> 
> 
> 
> Sebastian Kraus
> Team IT am Institut für Chemie
> Gebäude C, Straße des 17. Juni 115, Raum C7
> 
> Technische Universität Berlin
> Fakultät II
> Institut für Chemie
> Sekretariat C3
> Straße des 17. Juni 135
> 10623 Berlin
> 
> 
> Tel.: +49 30 314 22263
> Fax: +49 30 314 29309
> Email: sebastian.kr...@tu-berlin.de
> 
> 
> 

Bug#899268: O: scanbd -- Scanner button daemon

[Mattia Rizzolo]

Package: wnpp

The current maintainer of scanbd, Rolf Leggewie ,
has orphaned this package in version 1.5.1-3.

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

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

Some information about this package:

Package: scanbd
Binary: scanbd, scanbuttond
Version: 1.5.1-3
Maintainer: Debian QA Group 
Build-Depends: debhelper (>= 9), autotools-dev, libconfuse-dev, libsane-dev, 
libudev-dev, libusb-1.0-0-dev | libusb-dev, pkg-config, libdbus-1-dev
Architecture: any all
Standards-Version: 4.0.0
Format: 3.0 (quilt)
Files:
 debf663a6ff2e2ac4a57dc80d3fcd639 1962 scanbd_1.5.1-3.dsc
 f6f7c2da260d2a1064654f2890d30ebd 953539 scanbd_1.5.1.orig.tar.gz
 c0333c88fe45eee7f762c8b0e38bd672 10096 scanbd_1.5.1-3.debian.tar.xz
Vcs-Browser: https://github.com/leggewie-DM/scanbd
Vcs-Git: https://github.com/leggewie-DM/scanbd.git
Checksums-Sha256:
 58bd3df1230f2b5af576279805e7ec2ada15a5c4c5fdb342ca2b8c443ac55973 1962 
scanbd_1.5.1-3.dsc
 b69ca5a474b81516d19c38082d949363c243df9ab9742315aaae499723267e5f 953539 
scanbd_1.5.1.orig.tar.gz
 25b799827fc09e08751939453e4596946520dd089b69ee5f84fa62d6c96ba817 10096 
scanbd_1.5.1-3.debian.tar.xz
Homepage: http://scanbd.sf.net/
Package-List: 
 scanbd deb misc optional arch=any
 scanbuttond deb oldlibs optional arch=all
Directory: pool/main/s/scanbd
Priority: optional
Section: misc

Package: scanbd
Version: 1.5.1-3
Installed-Size: 177
Maintainer: Debian QA Group 
Architecture: amd64
Depends: lsb-base (>= 3.0-6), sane-utils, openbsd-inetd | inet-superserver, 
update-inetd, libc6 (>= 2.4), libconfuse2 (>= 3.2.1~), libdbus-1-3 (>= 1.9.14), 
libsane (>= 1.0.24), libudev1 (>= 183)
Description: Scanner button daemon
Description-md5: d74871c46cb6f52c5de388d68a7032a4
Homepage: http://scanbd.sf.net/
Section: misc
Priority: optional
Filename: pool/main/s/scanbd/scanbd_1.5.1-3_amd64.deb
Size: 48752
MD5sum: e0849dcc590cf5de7316e70578fd34e9
SHA256: 13bed38f78c6342a591c5a75f68521f0fde7759249143f954a109475f184d499

Package: scanbuttond
Source: scanbd
Version: 1.5.1-3
Installed-Size: 22
Maintainer: Debian QA Group 
Architecture: all
Depends: scanbd
Description: Dummy transitional package - scanbuttond to scanbd
Description-md5: d7700d726d52ce8d290f757b35a3ff1b
Homepage: http://scanbd.sf.net/
Tag: role::shared-lib
Section: oldlibs
Priority: optional
Filename: pool/main/s/scanbd/scanbuttond_1.5.1-3_all.deb
Size: 6108
MD5sum: 464b36285052c2af31f47e2b9257b0be
SHA256: cf7d019496ce357918a3ffd55c123892e52c4ff8ec802d444ac0cf8e4f26b337


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#898520: u-boot-rockchip: firefly-rk3288 hangs on: Loading Environment from MMC

[Vagrant Cascadian]

On 2018-05-12, Vagrant Cascadian wrote:
> On 2018-05-12, Vagrant Cascadian wrote:
>> Booting firefly-rk3288 seems to hang looking for environment:
>>
>>   U-Boot 2018.05+dfsg-1 (May 10 2018 - 20:24:57 +)
>>   
>>   Model: Firefly-RK3288
>>   DRAM:  2 GiB
>>   MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0
>>   Loading Environment from MMC...
>>
>> And just hangs there.

I tried to bisect this, and got:

commit 04a2ea248f58b3b6216d0cd0a6b8698df8b14355
Author: Jean-Jacques Hiblot 
Date:   Thu Sep 21 16:30:08 2017 +0200

mmc: disable UHS modes if Vcc cannot be switched on and off


But it fails in a slightly different way:

  U-Boot 2018.01-00026-g04a2ea248f (May 21 2018 - 21:46:18 +)

  Model: Firefly-RK3288
  DRAM:  2 GiB
  MMC:   dwmmc@ff0c: 1, dwmmc@ff0f: 0

And just hangs without the "Loading Environment from MMC..."
part...


It is not a trivial revert on top of 2018.05, so I haven't been able to
do that simple test.


CONFIG_ENV_IS_IN_MMC has been enabled since at least:

  5dc4dfd2a94 (Tom Rini2017-08-28 07:16:32 -0400 36) 
CONFIG_ENV_IS_IN_MMC=y



live well,
  vagrant


signature.asc
Description: PGP signature

Bug#899267: ruby2.5: FTBFS on kfreebsd-any

[Svante Signell]

Source: ruby2.5
Version: 2.5.1-1
Severity: important
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

ruby2.5 FTBFS on kFreebsd-any due to not being ported to that architecture for a
long time.

Attached are patches for debian/tests/exclude/kfreebsd-{amd64,i386}/
and source changes in 0006-fix-kfreebsd-build.patch

Since extremely many packages build-depends on ruby2.5, e.g. aptitude please
incorporate these patches ASAP in the next version of ruby2.5. There are 3
remaining fixes needed for a full port, now solved by the directories in
debian/tests/exclude/

Thanks!Index: ruby2.5-2.5.1/ext/socket/option.c
===
--- ruby2.5-2.5.1.orig/ext/socket/option.c
+++ ruby2.5-2.5.1/ext/socket/option.c
@@ -10,6 +10,7 @@ VALUE rb_cSockOpt;
 #if defined(__linux__) || \
 defined(__GNU__) /* GNU/Hurd */ || \
 defined(__FreeBSD__) || \
+defined(__FreeBSD_kernel__) || \
 defined(__DragonFly__) || \
 defined(__APPLE__) || \
 defined(_WIN32) || \
Index: ruby2.5-2.5.1/ext/socket/raddrinfo.c
===
--- ruby2.5-2.5.1.orig/ext/socket/raddrinfo.c
+++ ruby2.5-2.5.1/ext/socket/raddrinfo.c
@@ -1670,10 +1670,21 @@ addrinfo_mload(VALUE self, VALUE ary)
 INIT_SOCKADDR_UN(, sizeof(struct sockaddr_un));
 
 StringValue(v);
+#ifdef __FreeBSD_kernel__
+	/* sys/un.h defines struct sockaddr_un as:
+	   char sun_path[104];
+	   char __sun_user_compat[4];
+	*/
+if (sizeof(uaddr.sun_path) + 4 < (size_t)RSTRING_LEN(v))
+rb_raise(rb_eSocket,
+"too long AF_UNIX path (%"PRIuSIZE" bytes given but %"PRIuSIZE" bytes max)",
+(size_t)RSTRING_LEN(v), sizeof(uaddr.sun_path) + 4);
+#else
 if (sizeof(uaddr.sun_path) < (size_t)RSTRING_LEN(v))
 rb_raise(rb_eSocket,
 "too long AF_UNIX path (%"PRIuSIZE" bytes given but %"PRIuSIZE" bytes max)",
 (size_t)RSTRING_LEN(v), sizeof(uaddr.sun_path));
+#endif
 memcpy(uaddr.sun_path, RSTRING_PTR(v), RSTRING_LEN(v));
 len = (socklen_t)sizeof(uaddr);
 memcpy(, , len);
@@ -2319,10 +2330,21 @@ addrinfo_unix_path(VALUE self)
 if (e < s)
 rb_raise(rb_eSocket, "too short AF_UNIX address: %"PRIuSIZE" bytes given for minimum %"PRIuSIZE" bytes.",
 (size_t)rai->sockaddr_len, (size_t)(s - (char *)addr));
+#ifdef __FreeBSD_kernel__
+	/* sys/un.h defines struct sockaddr_un as:
+	   char sun_path[104];
+	   char __sun_user_compat[4];
+	*/
+if (addr->sun_path + sizeof(addr->sun_path) + 4 < e)
+rb_raise(rb_eSocket,
+"too long AF_UNIX path (%"PRIuSIZE" bytes given but %"PRIuSIZE" bytes max)",
+(size_t)(e - addr->sun_path), sizeof(addr->sun_path) + 4);
+#else
 if (addr->sun_path + sizeof(addr->sun_path) < e)
 rb_raise(rb_eSocket,
 "too long AF_UNIX path (%"PRIuSIZE" bytes given but %"PRIuSIZE" bytes max)",
 (size_t)(e - addr->sun_path), sizeof(addr->sun_path));
+#endif
 while (s < e && *(e-1) == '\0')
 e--;
 return rb_str_new(s, e-s);
Index: ruby2.5-2.5.1/test/fiddle/test_handle.rb
===
--- ruby2.5-2.5.1.orig/test/fiddle/test_handle.rb
+++ ruby2.5-2.5.1/test/fiddle/test_handle.rb
@@ -169,6 +169,7 @@ module Fiddle
 end unless /mswin|mingw/ =~ RUBY_PLATFORM
 
 def test_dlerror
+  return /kfreebsd/ =~ RUBY_PLATFORM
   # FreeBSD (at least 7.2 to 7.2) calls nsdispatch(3) when it calls
   # getaddrinfo(3). And nsdispatch(3) doesn't call dlerror(3) even if
   # it calls _nss_cache_cycle_prevention_function with dlsym(3).
@@ -177,7 +178,7 @@ module Fiddle
   require 'socket'
   Socket.gethostbyname("localhost")
   Fiddle.dlopen("/lib/libc.so.7").sym('strcpy')
-end if /freebsd/=~ RUBY_PLATFORM
+end if /freebsd/ =~ RUBY_PLATFORM
 
 def test_no_memory_leak
   assert_no_memory_leak(%w[-W0 -rfiddle.so], '', '100_000.times {Fiddle::Handle.allocate}; GC.start', rss: true)
Index: ruby2.5-2.5.1/test/socket/test_socket.rb
===
--- ruby2.5-2.5.1.orig/test/socket/test_socket.rb
+++ ruby2.5-2.5.1/test/socket/test_socket.rb
@@ -507,7 +507,7 @@ class TestSocket < Test::Unit::TestCase
   end
 
   def test_bintime
-return if /freebsd/ !~ RUBY_PLATFORM
+return if /freebsd/ !~ RUBY_PLATFORM || /kfreebsd/ =~ RUBY_PLATFORM
 t1 = Time.now.strftime("%Y-%m-%d")
 stamp = nil
 Addrinfo.udp("127.0.0.1", 0).bind {|s1|
--- a/dev/null	2018-05-21 16:47:03.0 +0200
+++ b/debian/tests/exclude/kfreebsd-amd64/TestGemSpecification.rb	2018-05-19 00:48:47.195961000 +0200
@@ -0,0 +1,2 @@
+# Actual is one day earlier than Expected
+exclude :test_date_equals_time, 'fails on kFreeBSD'
--- a/dev/null	2018-05-21 16:48:02.0 +0200
+++ 

Bug#897709: Fwd: Bug#897709: aspectc++: ftbfs with GCC-8

[Reinhard Tartler]

Control: tag -1 upstream


Hi AspectC++ team,

Matthias, the Debian/Ubuntu GCC maintainer is preparing for the new GCC 
release, and has kindly filed a bug in the Debian bug tracking system.


I have just tried to compile a snapshot from today against 
g++=4:8-20180425-2, and am able to reproduce this issue.


The error messages makes perfect sense, here is the full context of the 
function in question:


void assign(const basic_re_tokeniser_state _) 



{ 



_start = rhs_._start; 



_end = rhs_._end; 



_curr = rhs_._curr; 



_id = rhs_._id; 



_flags = rhs_._flags; 



_flags_stack = rhs_._flags_stack; 



_locale = rhs_._locale; 



_macro_name = rhs_._macro_name; 



_paren_count = rhs_._paren_count; 



_in_string = rhs_._in_string; 



_nl_id = rhs_._nl_id; 



return this; 



} 




I don't understand why earlier versions of GCC didn't complain about 
this. Is the right fix here to remove the "return this;"?


The file is part of the lexertl package, which has been most recently 
updated my Matthias in August 2015. It appears it needs another update 
for GCC 8. Olaf, is Matthias still around and can have a look at this?


Best,
Reinhard

 Forwarded Message 
Subject: Bug#897709: aspectc++: ftbfs with GCC-8
Resent-Date: Fri, 04 May 2018 12:24:43 +
Resent-From: Matthias Klose 
Resent-To: Reinhard Tartler 
Date: Fri, 04 May 2018 12:20:51 +
From: Matthias Klose 
Reply-To: Matthias Klose , 897709-mainto...@bugs.debian.org
To: mainto...@bugs.debian.org

Package: src:aspectc++
Version: 1:2.2+git20170823-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/aspectc++_2.2+git20170823-5_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
Generating dependencies for List.cc...
Generating dependencies for KeyboardSource.cc...
Generating dependencies for DString.cc...

Compiling DString.cc...
Compiling KeyboardSource.cc...
---
Compiling List.cc...
Compiling PUMA for TARGET=linux-release
Compiling MemPool.cc...
Compiling Pipe.cc...
  Compiler = g++ -DNDEBUG  -std=gnu++11 -I 
/build/aspectc++-foANom/aspectc++-2.2+git20170823/Puma/extern -I 
/build/aspectc++-foANom/aspectc++-2.2+git20170823/Puma/gen-release/step2/inc 
-O2 -g -Wall -pipe -Wno-deprecated-declarations -Wall -pipe 
-Wno-deprecated-declarations -Wall -pipe -Wno-deprecated-declarations 
Compiling PipedCmd.cc...
  Linker   = g++ -O2 -g -Wall -pipe -Wno-deprecated-declarations -Wall 
-pipe -Wno-deprecated-declarations -Wall -pipe 
-Wno-deprecated-declarations   ---

Compiling RegComp.cc...

Compiling StrCol.cc...
Compiling StrHashTable.cc...
Compiling SysCall.cc...
Compiling TerminalSink.cc...
Compiling VerboseMgr.cc...
Compiling VoidPtrArray.cc...
Compiling WChar.cc...
Compiling Config.cc...
Compiling ErrorCollector.cc...
Compiling ErrorSeverity.cc...
Compiling ErrorSink.cc...
Compiling ErrorStream.cc...
Compiling FilenameInfo.cc...
In file included from 
/build/aspectc++-foANom/aspectc++-2.2+git20170823/Puma/extern/lexertl/parser/tokeniser/re_tokeniser_helper.hpp:14,
 from 
/build/aspectc++-foANom/aspectc++-2.2+git20170823/Puma/extern/lexertl/parser/tokeniser/re_tokeniser.hpp:15,
 from 
/build/aspectc++-foANom/aspectc++-2.2+git20170823/Puma/extern/lexertl/rules.hpp:15,
 from 
/build/aspectc++-foANom/aspectc++-2.2+git20170823/Puma/gen-release/step2/src/RegComp.cc:22:
/build/aspectc++-foANom/aspectc++-2.2+git20170823/Puma/extern/lexertl/parser/tokeniser/re_tokeniser_state.hpp: 
In member function 'void 
lexertl::detail::basic_re_tokeniser_state::assign(const 
lexertl::detail::basic_re_tokeniser_state&)':
/build/aspectc++-foANom/aspectc++-2.2+git20170823/Puma/extern/lexertl/parser/tokeniser/re_tokeniser_state.hpp:80:16: 
error: 

Bug#899265: lintian: False positive for header-has-overly-generic-name with bsd/libutil.h

[Guillem Jover]

Package: lintian
Version: 2.5.87
Severity: important

Hi!

The new header-has-overly-generic-name tag triggers on libbsd-dev,
which is IMO a false positive.

The libbsd-dev headers are namespaced under bsd/, so they do not
pollute the global namespace. And this one needs to be named libutil.h
because it's an overlay over the standard header of the same name.

Thanks,
Guillem

Bug#899266: [node-backbone] FTBFS documentation

[Bastien ROUCARIÈS]

Package: src:backbone
Severity: serious

docs/*.html are build with docco not packaged for debian

So FTBFS could you please rip it ?

BTW you could also remove:
docs/*.css
docs/public

A and you could also remove normalize.c

If packaged docco will add it for you.

BTW I could not find copyright information about docs/js/*.js (it is lazy 
load)

And favicon.ico is generated from svg file.So you could remove and regenerated 
from svg file (found it on wikipedia uploaded by original author).

Thank you

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

Bug#896133: closed by Chris Lamb <la...@debian.org> (Bug#896133: fixed in lintian 2.5.84)

[Guillem Jover]

Control: reopen -1
Control: found -1 2.5.87

Hi!

On Mon, 2018-04-23 at 12:21:10 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the lintian package:
> 
> #896133: lintian: False positives on 
> binary-package-depends-on-toolchain-package with Breaks/Conflicts
> 
> It has been closed by Chris Lamb .

Unfortunately this is still triggering for at least dpkg-dev.
Reopening.

Thanks,
Guillem

Bug#899264: libnewlib-arm-none-eabi: Multilib directory structure incapatible with

[Thomas Preud'homme]

Package: libnewlib-arm-none-eabi
Version: 2.4.0.20160527-4
Severity: important

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Thomas Preud'homme 
To: Debian Bug Tracking System 
Subject: libnewlib-arm-none-eabi: Multilib directory structure incapatible with
 gcc-arm-none-eabi >= 6
Message-ID: 
<152693762196.22500.8895484219841600078.report...@e108577-lin.cambridge.arm.com>
X-Mailer: reportbug 6.6.6ubuntu1
Date: Mon, 21 May 2018 22:20:21 +0100

Package: libnewlib-arm-none-eabi
Version: 2.4.0.20160527-4
Severity: important

Dear Maintainer,

gcc-arm-none-eabi 15:6.3.1+svn253039-1 introduced a new multilib
directory structure which libnewlib must follow for the right C library
variant to be linked. Eg. compiling with:

-mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16

now looks for library under the thumb/v7e-m/fpv4-sp/hard subdirectory
instead of the armv7e-m/fpu subdirectory used by currently packaged
newlib. Users have come accross this problem in Ubuntu (which takes the
packaging straight from Debian), see [1].

[1] https://bugs.launchpad.net/gcc-arm-embedded/+bug/1772332

I believe newlib asks GCC for the scheme to use and thus doing a
binNMU of newlib should be enough.

Best regards,

Thomas Preud'homme


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

Kernel: Linux 4.4.0-121-generic (SMP w/16 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

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

Kernel: Linux 4.4.0-121-generic (SMP w/16 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

Bug#898065: general: Since linux-headers-4.9.0-6-amd64:amd64, Intel HD 3000 gives lower resolution

[Brian Kelly]

Hi,

Can you cancel this please? It might have been a once off, it got fixed
with reinstalling grub. Sorry for wasting your time if it wasn't a bug.

Thanks for all your work,

Brian


On 06/05/18 16:40, Brian wrote:
> Package: general
> Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
> Normal system update:
>
> user@debian:~$ less /var/log/apt/history.log
> Start-Date: 2018-05-02  12:11:40
> Commandline: apt upgrade
> Upgrade: linux-libc-dev:amd64 (4.9.82-1+deb9u3, 4.9.88-1), linux-libc-dev:i386
> (4.9.82-1+deb9u3, 4.9.88-1), linux-headers-4.9.0-6-amd64:amd64
> (4.9.82-1+deb9u3, 4.9.88-1), linux-compiler-gcc-6-x86:amd64 (4.9.82-1+deb9u3,
> 4.9.88-1), linux-kbuild-4.9:amd64 (4.9.82-1+deb9u3, 4.9.88-1), linux-
> image-4.9.0-6-amd64:amd64 (4.9.82-1+deb9u3, 4.9.88-1), linux-
> headers-4.9.0-6-common:amd64 (4.9.82-1+deb9u3, 4.9.88-1)
> End-Date: 2018-05-02  12:38:46
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
>
> -- System Information:
> Debian Release: 9.4
>   APT prefers stable
>   APT policy: (1001, 'stable'), (500, 'stable-updates'), (500, 'stable-debug')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_IE:en (charmap=UTF-8)

Bug#877612: fsck: A tiny part of the Spanish translation makes no sense

[Andreas Henriksson]

Control: reassign -1 e2fsprogs

On Tue, Oct 03, 2017 at 03:08:17PM +0200, Manolo Díaz wrote:
> Package: util-linux-locales
> Version: 2.29.2-5
> Severity: minor
> Tags: l10n
> 
> Dear Maintainer,
> 
> In my case, for instance, when talking about inodes or blocks, the
> 'fsck.ext4 -v' output reads:
[...]

fsck.ext4 is not part of util-linux, so reassigning.

Please provide the necessary information as needed to this bug report.
(Starting with which version of e2fsprogs you experienced this with.)

Even better would be if you could look up where upstream handles
translations and help improve it there and it'll eventually appear in
Debian.

Regards,
Andreas Henriksson

Bug#899262: dracut: after upgrade the system do not boot and enter in emergency shell

[Thomas Lange]

> On Mon, 21 May 2018 22:34:22 +0200, Vincenzo Demasi  
> said:

> The emergency recovery shell report 'failed to mount /sysroot'.
> I suspect the issue is caused by the missing crc32c module. Indeed
Can you please check with lsinitrd if the crc32c module is missing and
needed? I removed the Debian patch for including the crc32c module, but
upstream now handles this.

-- 
regards Thomas

Bug#895866: Bug 895866

[Alan Orth]

Dear Emmanuel, Tomcat 8.5.31 was released a few weeks ago. Have you had time to 
look at this since then? It seems there are quite a few people watching this 
bug now. Thanks.
-- 
Alan Orth
ao...@mjanja.ch
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch

> On May 21, 2018, at 7:59 PM, Mirko Raner  wrote:
> 
> I'm a little surprised at the nonchalance here. In my mind, this is a pretty 
> serious bug that will cause many people a good amount of headaches, myself 
> included.
> Tomcat 8.5 does not intrinsically require Java 9, so, introducing a 
> dependency by compiling it with Java 9 seems the wrong choice to begin with. 
> And having a package declare a dependency on Java 8 when it really depends on 
> Java 9 is a major bug; the package will install without errors but will not 
> actually work.
> 
> Personally, I would like to see a higher priority on this bug. And I'm sure I 
> will not be the only one who will appreciate this problem being fixed.

Bug#891812: util-linux: FTBFS on hurd-i386: calls pty_init_slave unconditionally

[Andreas Henriksson]

On Thu, Mar 01, 2018 at 01:55:22AM +0100, Samuel Thibault wrote:
> Aaron M. Ucko, on mer. 28 févr. 2018 19:47:40 -0500, wrote:
> >   login-utils/su-common.c:1427:3: warning: implicit declaration of function 
> > 'pty_init_slave'; did you mean 'initstate'? 
> > [-Wimplicit-function-declaration]
> >   [...]
> >   ./login-utils/su-common.c:1427: undefined reference to `pty_init_slave'
> 
> IIRC I got a fix commited upstream

Your fix should now be part of the latest upload (2.32-0.1),
unfortunately there's another problem now.

Any chance you can test if by any chance the following upstream commit
fixes the (libmount-related) build issue on hurd (or if additional
upstream fixing is needed for hurd)?

https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=061d1a51097c3c025ff46173f10aa135f9a610d4

(FYI, I've just committed making rfkill linux-any to git.)

Regards,
Andreas Henriksson

Bug#899263: libanyevent-yubico-perl: Make autopkgtests proxy-safe

[Steve Langasek]

Package: libanyevent-yubico-perl
Version: 0.9.3-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch autopkgtest

Dear maintainers,

The libanyevent-yubico-perl autopkgtests pass NO_INTERNET=1 in the
environment, which is probably sensible if you want the autopkgtests to be
maximally portable, and to not fail due to network resource failures outside
of your control.  However, the autopkgtests still fail on Ubuntu's
infrastructure with this error:

[...]
autopkgtest [01:38:59]: test command1: [---
t/AnyEvent-Yubico.t .. 
1..6
ok 1 - use AnyEvent::Yubico;
ok 2 - new() works
ok 3 - sign() works
not ok 4 - invalid URL

#   Failed test 'invalid URL'
#   at t/AnyEvent-Yubico.t line 40.
#  got: 'Bad Request'
# expected: 'Connection refused'
ok 5 - timeout
[...]

  
(http://autopkgtest.ubuntu.com/packages/liba/libanyevent-yubico-perl/cosmic/amd64)

This is because the Ubuntu autopkgtest infrastructure does have Internet
access, but it's proxied; therefore, an attempt to connect to
http://127.0.0.1:0 in this test respects the proxy setting, and therefore
fails because the API call gets a 'Bad Request' instead of a 'Connection
refused'.

Perhaps you could argue that the proxy environment is misconfigured because
127.0.0.1 is not excluded, but given that these tests should not hit the
network anyway, it seems more straightforward to me to simply clean the
proxy settings from the environment than to dictate additional constraints
on the autopkgtest environments.

The attached patch has been uploaded to Ubuntu, allowing the autopkgtests to
now pass there.  Please consider applying this patch in Debian as well.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libanyevent-yubico-perl-0.9.3/debian/tests/pkg-perl/smoke-env 
libanyevent-yubico-perl-0.9.3/debian/tests/pkg-perl/smoke-env
--- libanyevent-yubico-perl-0.9.3/debian/tests/pkg-perl/smoke-env   
2016-06-05 05:56:41.0 -0700
+++ libanyevent-yubico-perl-0.9.3/debian/tests/pkg-perl/smoke-env   
2018-05-21 10:50:14.0 -0700
@@ -1 +1,3 @@
+http_proxy=
+https_proxy=
 NO_INTERNET=1

Bug#899262: dracut: after upgrade the system do not boot and enter in emergency shell

[Vincenzo Demasi]

Package: dracut
Version: 047+31-1
Severity: important

Dear Maintainer,

The emergency recovery shell report 'failed to mount /sysroot'.
I suspect the issue is caused by the missing crc32c module. Indeed
in the recovery shell I tryed to mount the system partition but 
it failed to mount with a message indicating that was not possible
to load crc32c module. I was able to reboot again after downgrade
to version 047-2.



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

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

Versions of packages dracut depends on:
ii  dracut-core  047+31-1

dracut recommends no packages.

Versions of packages dracut suggests:
pn  dracut-network  

-- no debconf information

Bug#897953: dvtm: Please stop shipping dvtm and dvtm-256color terminfo entries

[KAction]

[2018-05-21 05:16] Thomas Dickey 
> - Original Message -
> | From: "Sven Joachim" 
> | To: kact...@gnu.org
> | Cc: 897...@bugs.debian.org, ncur...@packages.debian.org
> | Sent: Monday, May 21, 2018 5:07:15 AM
> | Subject: Re: Bug#897953: dvtm: Please stop shipping dvtm and dvtm-256color 
> terminfo entries
> | 
> | On 2018-05-12 16:23 +0300, kact...@gnu.org wrote:
> | 
> | > control: tags -1 +pending
> | >
> | > [2018-05-05 08:29] Sven Joachim 
> | >> In early 2017, the dvtm and dvtm-256color terminfo entries were
> | >> added to
> | >> ncurses upstream, and I would like to include them in the
> | >> ncurses-term
> | >> package, replacing the ones shipped currently in the dvtm package.
> | >> 
> | >> This requires coordinated uploads of dvtm and ncurses, adding a
> | >> versioned Breaks/Replaces on dvtm to ncurses-term and a versioned
> | >> dependency on ncurses-term to dvtm.
> | >
> | > Sure. I just uploaded dvtm_0.15-3, that depends on
> | > ncurses-term (>> 6.1+20180210-2) into DELAYED/10.
> | >
> | > As such, I expect it to arrive at 2018/05/22. I propose you to make new
> | > upload of ncurses-term with apporiate Breaks/Depends into DELAYED in
> | > such way, that our packages arrive at same time.
> | 
> | Just uploaded ncurses 6.1+20180210-4 to DELAYED/1, thanks.
> 
> The package's versions of the terminfo entries have 2-3 errors in them.

Could you please elaborate? Which package have errors? Which errors? What and 
by whom
should be done to fix them?

Bug#899261: ITP: qasm-simulator-cpp -- C++ quantum circuit simulator with realistic noise

[Enrique de la Torre]

Package: wnpp
Severity: wishlist
Owner: Enrique de la Torre 

* Package name : qasm-simulator-cpp
  Version : 0.5.1
  Upstream Author : QISKit Development Team 
* URL : https://qiskit.org/
* License : Apache-2.0
  Programming Lang: C++
  Description : C++ quantum circuit simulator with realistic noise

QASM Simulator is a quantum circuit simulator written in C++
that includes a variety of realistic circuit level noise models.
The simulator may be run as a command line application to
evaluate quantum programs specified by a Quantum program OBJect
(QObj). It is part of QISKit (Quantum Information Software Kit),
developed by IBM.

The simulator is currently distributed as part of open source
QISKit Python SDK. By making it into a Debian package, I will
be able to integrate it in other frameworks like QISKit Swift
Framework. Also, if we simplify the installation process, it
will be a lot easier for other developers/researchers to use it
with different purposes.

The package is already under development here:
https://github.com/indisoluble/qasm-simulator-cpp-debian-pkg

Bug#899260: ITP: fonts-myanmar -- Myanmar Fonts Packs for Debian Upstream

[kokoye2007]

Package: wnpp
Severity: wishlist
Owner: kokoye2007 

* Package name: fonts-myanmar
  Version : 1.0-1
  Upstream Author : kokoye2007 
* URL : http://launchpad.net/ttf-burmese-fonts
* License : GPL2
  Programming Lang: C++
  Description : Myanmar Fonts Packs for Debian Upstream

Inculde fonts packs
fonts-myanmar - ttf myanmar fonts:
fonts-myanmar-angoun - myanmar fonts: angoun;
fonts-myanmar-ayar - ttf myanmar fonts: ayar;
fonts-myanmar-chatu - myanmar fonts: chatu;
fonts-myanmar-chatulight - myanmar fonts: chatulight;
fonts-myanmar-gantgaw - myanmar fonts: gantgaw;
fonts-myanmar-khyay - myanmar fonts: khyay;
fonts-myanmar-kuttar - myanmar fonts: kuttar;
fonts-myanmar-mon - myanmar fonts: MON3 Anonta 1 ;
fonts-myanmar-myanmar3 - ttf myanmar fonts: Myanmar3;
fonts-myanmar-myanmarcensus - ttf myanmar fonts: MyanmarCensus;
fonts-myanmar-myanmarsanspro - myanmar fonts: Myanmar Sans Pro;
fonts-myanmar-namkhome - myanmar fonts: Namkhone;
fonts-myanmar-nayone - myanmar fonts: nayone;
fonts-myanmar-njaun - myanmar fonts: njaun;
fonts-myanmar-pauklay - myanmar fonts: pauklay;
fonts-myanmar-phetsot - myanmar fonts: phetsot;
fonts-myanmar-phiksel - myanmar fonts: phiksel;
fonts-myanmar-phikselsmooth - myanmar fonts: phikselsmooth;
fonts-myanmar-ponenyet - myanmar fonts: ponenyet;
fonts-myanmar-pyidaungsu - ttf myanmar fonts: Pyidaungsu;
fonts-myanmar-sabae - myanmar fonts: sabae;
fonts-myanmar-sagar - myanmar fonts: sagar;
fonts-myanmar-sanpya - myanmar fonts: sanpya;
fonts-myanmar-squarelight - myanmar fonts: squarelight;
fonts-myanmar-tagu - myanmar fonts: tagu;
fonts-myanmar-thuriya - myanmar fonts: thuriya;
fonts-myanmar-unicode - ttf myanmar unicode fonts
fonts-myanmar-waso - myanmar fonts: waso;
fonts-myanmar-yinmar - myanmar fonts: yinmar;
fonts-myanmar-zawgyi - ttf myanmar fonts: ZawgyiOne2008;

we need sponsor for fonts-myanmar, its migrate from ttf-myanmar-fonts

who can support for our country

we love DFSG & SC.

with regards

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

[Francesco Poli (wintermute)]

Package: cups-daemon
Version: 2.2.7-5
Severity: normal

Dear Debian Printing Team,
this bug report is a sort of "sequel" of #894762...

After some preliminary tests, I concluded that socket activation
was working again.

Well, I was wrong!   :-(

After some further testing, I found out the following misbehavior.

 a) in my preliminary tests, the "lpq" command correctly woke cupsd up,
and the daemon correclty exited after 60 s of inactivity
(I have set "IdleExitTimeout 60" in /etc/cups/cupsd.conf)
 
 b) on the other hand, if I print something with the "lpr" command, cupsd
is correctly started, but it seems to never exit for inactivity:

$ systemctl status cups.service
● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor 
preset: ena
   Active: active (running) since Mon 2018-05-21 11:59:07 CEST; 9h ago
 Docs: man:cupsd(8)
 Main PID: 15103 (cupsd)
Tasks: 1 (limit: 4915)
   Memory: 6.6M
   CGroup: /system.slice/cups.service
   └─15103 /usr/sbin/cupsd -l

May 21 11:59:07 HOSTNAME systemd[1]: Started CUPS Scheduler.

  c) now, after manually quitting cupsd and after re-enabling socket
 activation:

 # systemctl stop cups.service
 # systemctl daemon-reload
 # systemctl restart cups.socket

 an "lpq" command correctly starts cupsd (again), but the daemon
 fails to exit after 60 s of inactivity



Why does cupsd fail to exit?
What's wrong?

Please help me.

Thanks for your time!


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages cups-daemon depends on:
ii  adduser   3.117
ii  bc1.07.1-2+b1
ii  dpkg  1.19.0.5+b1
ii  libavahi-client3  0.7-4
ii  libavahi-common3  0.7-4
ii  libc6 2.27-3
ii  libcups2  2.2.7-5
ii  libcupsmime1  2.2.7-5
ii  libdbus-1-3   1.12.8-2
ii  libgssapi-krb5-2  1.16-2
ii  libpam0g  1.1.8-3.7
ii  libpaper1 1.1.24+nmu5
ii  libsystemd0   238-4
ii  lsb-base  9.20170808
ii  procps2:3.3.14-1+b1
ii  ssl-cert  1.0.39

Versions of packages cups-daemon recommends:
pn  avahi-daemon  
ii  colord1.3.3-2
ii  cups-browsed  1.20.3-1+b1

Versions of packages cups-daemon suggests:
ii  cups 2.2.7-5
ii  cups-bsd 2.2.7-5
ii  cups-client  2.2.7-5
ii  cups-common  2.2.7-5
ii  cups-filters [foomatic-filters]  1.20.3-1+b1
pn  cups-pdf 
ii  cups-ppdc2.2.7-5
ii  cups-server-common   2.2.7-5
ii  foomatic-db  20180306-1
ii  ghostscript  9.22~dfsg-2.1
pn  hplip
ii  poppler-utils0.63.0-2
ii  printer-driver-gutenprint5.2.13-2+b1
ii  printer-driver-hpcups3.17.10+repack0-5
pn  smbclient
ii  udev 238-4

-- no debconf information

Bug#899258: RM: ttf-adf -- ROM; all binaries built by src:fonts-adf now

[Adam Borowski]

Package: ftp.debian.org
Severity: normal


Hi!
Please remove source package ttf-adf -- all of its binaries are now dummies
built from src:fonts-adf.  The new version has transitioned to testing a few
days ago, but the old one hasn't been decrufted automatically, thus I'm
filing this RM -- please remove the old source.


Meow!

Bug#899248: debhelper/11.3 appears to break gem2deb/0.39 autopkgtest in testing

[Paul Gevers]

user debian...@lists.debian.org
usertags 899248 needs-update
thanks

On 21-05-18 20:43, gregor herrmann wrote:
> On Mon, 21 May 2018 18:07:43 +, Paul Gevers wrote:
> 
>> tl;dr: debhelper/11.3 appears to break gem2deb/0.39 autopkgtest in testing
>> see: https://ci.debian.net/packages/g/gem2deb/testing/amd64/
>> and https://qa.debian.org/excuses.php?package=debhelper
> 
> This looks like #899248.
> 
> | Failure: test: Gem2Deb should install CHANGELOG.rdoc as upstream changelog. 
> (Gem2DebTest):
> 
> 
> Cheers,
> gregor
> 



signature.asc
Description: OpenPGP digital signature

Bug#897435: eureka: please bring back the "add sidedef" button

[Jonathan Dowland]

There is a option in the config file called "sidedef_add_del_buttons"
setting it to 1 (by editing the config file) will restore those buttons.


That's satisfactory for me. I accept it's a bit of an expert-user "here
be dragons" feature.


Thanks,

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄

Bug#899118: Aw: Re: Bug#899118: flash-kernel: add missing arm64 boards

[Heinrich Schuchardt]

I will try to build those 60 images and analyze which conform to your requirements. But that will take some time.

Best regards

Heinrich

Bug#899118: flash-kernel: add missing arm64 boards

[Karsten Merker]

On Mon, May 21, 2018 at 01:01:56AM +0200, Heinrich Schuchardt wrote:
> On 05/20/2018 09:15 PM, Karsten Merker wrote:
> > On Sat, May 19, 2018 at 02:57:41PM +0200, Heinrich Schuchardt wrote:
> > 
> >> Package: flash-kernel
> >> Version: 3.94
> >> Severity: normal
> >> Tags: patch
> >>
> >> Add 60 missing database entries for arm64 boards
> >> supported both by U-Boot and by Linux:
[...]
> > many thanks for the patch.  Just to make sure that we don't run
> > into problems later on: do all these boards really use u-boot's
> > config_distro_bootcmd.h and thereby work properly with
> > bootscr.uboot-generic?
> > 
> > When looking at the defconfigs for several of these systems, I
> > see e.g. CONFIG_BOOTARGS settings that don't really match what I
> > would expect for systems using config_distro_bootcmd.h.
> > Three random examples:
> > 
> > - r8a77995_draak_defconfig:
> >   CONFIG_BOOTARGS="console=ttySC0,115200 rw root=/dev/nfs 
> > nfsroot=192.168.0.1:/export/rfs ip=192.168.0.20"
> > 
> > - ls1088ardb_sdcard_qspi_defconfig:
> >   CONFIG_BOOTARGS="console=ttyS0,115200 root=/dev/ram0 
> > earlycon=uart8250,mmio,0x21c0500 ramdisk_size=0x300 
> > default_hugepagesz=2m hugepagesz=2m hugepages=256"
> > 
> > - hikey_defconfig:
> >   CONFIG_BOOTARGS="console=ttyAMA0,115200n8 root=/dev/mmcblk0p9 rw"
[,,,]
> For a board to be able to benefit from flash-kernel U-Boot must:
> 
> - be capable to load and execute boot.scr
> - provide the booti command
> - allow the definition of the following environment variables:
>   - devtype, devnum, partition
>   - fdtfile
>   - kernel_addr_r
>   - fdt_addr_r
>   - ramdisk_addr_r
> 
> In your examples above I could not find any evidence that U-Boot cannot
> be configured and built to fulfill these requirements.
> 
> For instance build
> 
> make r8a77995_draak_defconfig
> make menuconfig
> CONFIG_DISTRO_DEFAULTS=y
> CONFIG_BOOTARGS="console=ttySC0,115200"
> CONFIG_ENV_IS_IN_MMC=y (this is a default value)
> make -j6
> 
> Setup missing environment variables interactively and save them to MMC
> and you can rely on flash-kernel for booting.
> 
> ls1088ardb_sdcard_qspi_defconfig and hikey_defconfig select
> CONFIG_DISTRO_DEFAULTS=y. CONFIG_BOOTARGS has to be reconfigured.
> 
> This patch is only about providing flash-kernel for the boards. It is
> not about providing U-Boot configured to match flash-kernel's requirements.
> 
> I think that even for boards for which we do not provide U-Boot as a
> Debian package we should allow the usage of flash-kernel without setting
> up a local override for the machine database (/etc/flash-kernel/db).

Hello,

our policy has always been to only add an entry for an
armhf/arm64 system to the flash-kernel database if this entry
works out of the box with the default mainline u-boot
configuration for the respective device.  Users usually expect
that a system boots out of the box without having to build a
non-standard u-boot configuration and modify the default
environment if the system is listed in the flash-kernel machine
db.

I'm open to arguments to the contrary, but for now I believe that
is makes sense to keep this policy.

Having to build u-boot with an undocumented non-standard
configuration and having to modify various non-obvious parts of
the default environment (which possibly includes having to find
out the platform-specific kernel_addr_r, fdt_addr_r and
ramdisk_addr_r values for systems where they are not already
defined in the default environment) to make the system boot is an
extremely high and completely unexpected hurdle for a "normal"
user, and I believe that we would do a large part of our userbase
a misservice by including entries that do not work out of the
box.

For somebody who has the knowledge to perform all the
aforementioned steps on the u-boot side, it's usually easy to
also add a corresponding local entry to /etc/flash-kernel/db.

I'm CCing debian-arm for further opinions on the matter.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

Bug#897127: psensor FTBFS on i386/armhf: FAIL: test-cppcheck.sh

[Enrico Tröger]

On 05/13/2018 02:36 PM, Joachim Reichel wrote:
> See bug 898327.

Thanks.
Just for the records, for me the problem is gone with the new version.

I guess this bug report can be closed.




signature.asc
Description: OpenPGP digital signature

Bug#899248: debhelper/11.3 appears to break gem2deb/0.39 autopkgtest in testing

[gregor herrmann]

On Mon, 21 May 2018 18:07:43 +, Paul Gevers wrote:

> tl;dr: debhelper/11.3 appears to break gem2deb/0.39 autopkgtest in testing
> see: https://ci.debian.net/packages/g/gem2deb/testing/amd64/
> and https://qa.debian.org/excuses.php?package=debhelper

This looks like #899248.

| Failure: test: Gem2Deb should install CHANGELOG.rdoc as upstream changelog. 
(Gem2DebTest):


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: Willi Resetarits + Stubnblues: da r abr


signature.asc
Description: Digital Signature

Bug#899257: RFP: crelay -- Controlling different relay cards for home automation with a Linux software

[Victoria Ivanova]

Package: wnpp
Severity: wishlist

https://github.com/ondrej1024/crelay It is licensed under
GNU General Public License Version 2
https://github.com/ondrej1024/crelay/blob/master/LICENSE.  It makes it
possible to control USB relay cards from different manufacturers under
Linux in unified way.

Bug#899256: calibre: Closing "Table of Content" in viewer when switching gnome workspaces

[Jureq]

Package: calibre
Version: 3.23.0+dfsg-1
Severity: minor

Dear Maintainer,

I open any ebook in calibre viewer. Table of Content panel is open. Then I
switch to another gnome workspace and back. Table of Content panel gets closed.
I have to reopen it with Ctrl-T (or icon).
The same error in calibre 2.75 in stable (stretch).



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

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

Versions of packages calibre depends on:
ii  calibre-bin  3.23.0+dfsg-1
ii  fonts-liberation 1:1.07.4-6
ii  imagemagick  8:6.9.9.34+dfsg-3+b1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.9.34+dfsg-3+b1
ii  libjs-coffeescript   1.12.7~dfsg-3
ii  libjs-mathjax2.7.3+dfsg-1
ii  poppler-utils0.63.0-2
ii  python-apsw  3.16.2-r1-2+b1
ii  python-chardet   3.0.4-1
ii  python-cherrypy3 8.9.1-2
ii  python-cssselect 1.0.3-1
ii  python-cssutils  1.0.2-1
ii  python-dateutil  2.6.1-1
ii  python-dbus  1.2.6-1
ii  python-feedparser5.2.1-1
ii  python-html5-parser  0.4.4-1
ii  python-lxml  4.2.1-1
ii  python-markdown  2.6.9-1
ii  python-mechanize 1:0.2.5-3
ii  python-msgpack   0.5.6-1
ii  python-netifaces 0.10.4-1
ii  python-pil   4.3.0-2
ii  python-pkg-resources 39.1.0-1
ii  python-pyparsing 2.2.0+dfsg1-2
ii  python-pyqt5 5.10.1+dfsg-1
ii  python-pyqt5.qtsvg   5.10.1+dfsg-1
ii  python-pyqt5.qtwebkit5.10.1+dfsg-1
ii  python-regex 0.1.20171212-2
ii  python-routes2.4.1-1
ii  python2.72.7.15-1
ii  xdg-utils1.1.2-2

Versions of packages calibre recommends:
ii  python-dnspython  1.15.0-1

calibre suggests no packages.

-- no debconf information

Bug#899255: [fortunes-debian-hints] Some Debian hints are outdated

[Alexander Kernozhitsky]

Package: fortunes-debian-hints
Version: 2.01.1
Severity: normal

Some hints about Debian found in this package are outdated. For example, #31 
says about services in sysv, while systemd is used by Debian now. There are 
hints saying about packages apt-spy and apt-zip, which don't exist in archives 
now. Please update these hints for new Debian version.

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

Debian Release: buster/sid
  990 testing ftp.by.debian.org 
  500 unstableftp.by.debian.org 

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

Recommends (Version) | Installed
-+-=
fortune-mod (>= 9708-31) | 1:1.99.1-7+b1


Package's Suggests field is empty.
-- 
-
Alexander Kernozhitsky

Bug#898495: [pkg-cryptsetup-devel] Bug#898495: cryptsetup: [patch] make failsleep configurable

[Guilhem Moulin]

Hi Chris,

On Sat, 12 May 2018 at 19:10:43 +0100, Chris Lamb wrote:
> It would be nice if the sleep-on-failure time was configurable, just
> like tries=N, etc.
> 
> Patch attached.

Thanks for the patch!  (We discussed about this bug IRL but let me
follow up here for the sake of transparency.)  The sleep-on-failure
behavior was added in 2:1.7.3-2 as mitigation for local brute-force
attacks (CVE-2016-4484).  See mejo's blogpost about it:

https://blog.freesources.org/posts/2016/12/CVE-2016-4484/

Given that a major refactoring of the initramfs integration is ongoing,
I didn't merge your patch.  In fact we all seem to agree that the attack
vector described in the CVE isn't really related to cryptsetup nor its
initramfs integration (if one protects the BIOS and passes the
‘panic=’ parameter to the kernel command line, the boot script no
longer yields a debug shell after a couple of failed attempts at
unlocking the root device), and that our mitigation gives a marginal
security gain.  So we're likely to remove said mitigation as part of our
refactoring.  You intended to use the ‘failsleep=’ boot parameter
to disable it, right?

Of course, since it was our response to the CVE we shouldn't remove it
silently.  I guess a follow-up to mejo's blog post and/or an entry in
the NEWS file are appropriate.  Either way, we'll keep that bug open
until we either merge your patch, or decide to remove the mitigation.

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#898940: lastpass-cli: error: Peer certificate cannot be authenticated with given CA certificates

[Troy Heber]

On 05/18/18 15:56, Chris Lamb wrote:
> 
> Would you be interested in letting me adopt this package (or co-
> maintaining it?).

I would be more that happy for you to take over maintenance of
this package!

Troy

Bug#898940: lastpass-cli: error: Peer certificate cannot be authenticated with given CA certificates

[Chris Lamb]

Dear Troy,

> I would be more that happy for you to take over maintenance of
> this package!

Thanks for letting me know. I'll get around to this soon :)


Best wishes,

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

Bug#898991: deja-dup: Deja-Dup backups failing. Calls to dbus service timing out.

[Don Alexander]

False bug. Error was in a corrupt /var/lib/Packagekit/transaactions.db 
which cause packagkitd to fail to start.

This in turn caused deja-dup not to work.


Maybe demote bug and flag it as a needed dependency.


-- 
==

Don Alexander

It's a tough job, but some mug has to do it...

RooSoft Ltd




signature.asc
Description: OpenPGP digital signature

Bug#855034: debdiff to update to Protobuf 3.2.1 and add ruby-google-protobuf

[GCS]

On Fri, May 18, 2018 at 7:02 PM Pirate Praveen  wrote:
> On Fri, 14 Apr 2017 11:06:10 + Maarten 
> wrote:
> > tag 855034 +patch
> > retitle 855034 update to Protobuf 3.2.1 and add ruby-google-protobuf
> >
> > I attached a debdiff to update to protobuf 3.2.1 and also added a
> > decleration for the ruby-google-protobuf package.

> protobuf 3.5.2 is available in experimental.

> ruby-google-protobuf is a separate source package now.
  Indeed.

> Laszlo and other maintainers, what is the plan for uploading this
> version to unstable? I need this for gitlab.
  As I see, I'm the only maintainer at the moment - or other please speak up.
About the upload timing: I'll do it when I could test everything and I'm
allowed to do it.

Cheers,
Laszlo/GCS

Bug#885947: marco: After updating, restart (user or pc) and log in, desktop fails

[Santiago]

Package: marco
Version: 1.18.1-3
Followup-For: Bug #885947

Thanks for answering and for the questions.

> Also, I assume, you are on Debian buster, correct?

lsb_release -ds
Debian GNU/Linux testing (buster)

cat /etc/debian_version 
buster/sid


> And what are the versions of the underlying Xserver?

dpkg -l xserver-xorg-video-*


||/ Nombre Versión  Arquitectura 
Descripción
+++-==---=
ii  xserver-xorg-video-all 1:7.7+19 amd64X.Org 
X server -- output driver metapackage
ii  xserver-xorg-video-amdgpu  18.0.1-1 amd64X.Org 
X server -- AMDGPU display driver
ii  xserver-xorg-video-ati 1:18.0.1-1   amd64X.Org 
X server -- AMD/ATI display driver wrapper
ii  xserver-xorg-video-fbdev   1:0.4.4-1+b5 amd64X.Org 
X server -- fbdev display driver
ii  xserver-xorg-video-intel   2:2.99.917+git20171229-1 amd64X.Org 
X server -- Intel i8xx, i9xx display driver
ii  xserver-xorg-video-ivtv1.1.2-2+b5   amd64X.Org 
X server -- IVTV display driver
un  xserver-xorg-video-mach64  (no 
hay ninguna descripción disponible)
un  xserver-xorg-video-modesetting (no 
hay ninguna descripción disponible)
ii  xserver-xorg-video-nouveau 1:1.0.15-2   amd64X.Org 
X server -- Nouveau display driver
ii  xserver-xorg-video-qxl 0.1.5-2  amd64X.Org 
X server -- QXL display driver
un  xserver-xorg-video-r128(no 
hay ninguna descripción disponible)
ii  xserver-xorg-video-radeon  1:18.0.1-1   amd64X.Org 
X server -- AMD/ATI Radeon display driver
ii  xserver-xorg-video-vesa1:2.3.4-1+b2 amd64X.Org 
X server -- VESA display driver
ii  xserver-xorg-video-vmware  1:13.2.1-1+b1amd64X.Org 
X server -- VMware display driver


> And what version of libxpresent do you have?
>
>   dpkg -l libxpresent1

Before updating marco (1.18.1-3 => 1.20.1-2), the libxpresent1 (1.0.0-2+b10) is 
not installed, it is a new package that will install.


> Have you already tried creating a new user with a fresh user profile?  
> Does that new user show the same symptons?

Moreover, I installed a recent DVD image (20180402-04: 13 Binary-1 amd64) on 
another disk from scratch, with the same symptoms.


> What is the exact specification of your graphics card?

lspci -nnk | grep VGA -A3
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV25 [GeForce4 Ti 
4200] [10de:0253] (rev a3)
Subsystem: Micro-Star International Co., Ltd. [MSI] NV25 [GeForce4 Ti 
4200] [1462:8700]
Kernel driver in use: nouveau
Kernel modules: nouveau


The PC woks fine in Debian 9, and too in Debian 10 with mate 1.18.1-3, just 
until I update to the following versions.

Santiago.


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

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

Versions of packages marco depends on:
ii  libatk1.0-0   2.28.1-1
ii  libc6 2.27-3
ii  libcairo-gobject2 1.15.10-3
ii  libcairo2 1.15.10-3
ii  libcanberra-gtk3-00.30-6
ii  libcanberra0  0.30-6
ii  libgdk-pixbuf2.0-02.36.11-2
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.29-3
ii  libgtop-2.0-112.38.0-2
ii  libice6   2:1.0.9-2
ii  libmarco-private1 1.18.1-3
ii  libpango-1.0-01.42.0-1
ii  libpangocairo-1.0-0   1.42.0-1
ii  libsm62:1.2.2-1+b3
ii  libstartup-notification0  0.12-5
ii  libx11-6  2:1.6.5-1
ii  libxcomposite11:0.4.4-2
ii  libxcursor1   1:1.1.15-1
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxinerama1  2:1.1.3-1+b3
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1
ii  marco-common  1.18.1-3
ii  mate-desktop-common   1.20.1-2
ii  zenity3.28.1-1

marco recommends no packages.

marco suggests no packages.

-- no debconf information

Bug#899254: mkpasswd(1) truncates passwords to 127 characters

[Aaron Toponce]

Package: whois
Version: 5.3.0

The mkpasswd(1) binary is truncating passwords longer than 127-characters:

Unique password string for 126 characters:

$ printf 'a%.0s' {1..126} | mkpasswd -m SHA-512 -S '' -s

$6$$W.thEL8diDVRFeHWlFLX3uJQViSwuCRjGgQNzFHsGNmaRKC2opCC5Kn075sSXTyzjQu8KB36qYKzDuokqspu91

Same password string for both 127 and 128 characters:

$ printf 'a%.0s' {1..127} | mkpasswd -m SHA-512 -S '' -s

$6$$ohe17aZZw6Y3jUoSMm3bz3npIzYz2TBeXUPuvxc2LpQ.ARle/n5CF3.9yLYUPmGuLHGbc1jJKz3J/nJ5B5/yb1
$ printf 'a%.0s' {1..128} | mkpasswd -m SHA-512 -S '' -s

$6$$ohe17aZZw6Y3jUoSMm3bz3npIzYz2TBeXUPuvxc2LpQ.ARle/n5CF3.9yLYUPmGuLHGbc1jJKz3J/nJ5B5/yb1

This behavior does not match passwd(1) behavior when updating passwords in the
shadow(5) file. In this first example, a 127-character "a" string is printed,
and copy/pasted to passwd(1) for a "testing" user. The password generated by
passwd(1), which is believe is calling crypt(3), matches the password generated
with mkpasswd(1), which is also calling crypt(3), when using the same salt:

# printf 'a%.0s' {1..127}; echo

aaa
# passwd testing
Enter new UNIX password: (copy/paste from above)
Retype new UNIX password: 
passwd: password updated successfully
# grep testing /etc/shadow

testing:$6$rounds=5$3ideW/N8$6fTBlETOHVxEaxkQ/bAzuV2zd006reQXl..swD4VOevqM6scHykTuGKEU0AH06fz.56czYRYn37zoBDoy2WTx0:17672:0:9:7:::
# printf 'a%.0s' {1..127} | mkpasswd -R 5 -S '3ideW/N8' -m SHA-512 -s

$6$rounds=5$3ideW/N8$6fTBlETOHVxEaxkQ/bAzuV2zd006reQXl..swD4VOevqM6scHykTuGKEU0AH06fz.56czYRYn37zoBDoy2WTx0

In this second example, a 128-character "a" string is printed, and copy/pasted
to passwd(1), for the "testing" user, just as in the first example. However,
the password generated by mkpasswd(1) does not match, when using the same salt:

# printf 'a%.0s' {1..128}; echo


# passwd testing
Enter new UNIX password: (copy/paste from above)
Retype new UNIX password: 
passwd: password updated successfully
# grep testing /etc/shadow

testing:$6$rounds=5$qkMTUfnR$iZi0HouwMMgCPDLkrMTWbLAP7rxFvlQJrVhWWoTD6yyfG9prX2xQHkfqW4rB17hRwV5BMnugV8H9osy3cXbKo1:17672:0:9:7:::
# printf 'a%.0s' {1..128} | mkpasswd -R 5 -S 'qkMTUfnR' -m SHA-512 -s

$6$rounds=5$qkMTUfnR$ViyQ1KWaHVjBWxJbQikeSZfbp1MXyfRn2.KbTnMqcI7I/gqKmVXPW64rK/qz18LAtL5QjHoOn2CBhbWrZ/jRe.

This seems to be a bug with mkpasswd(1), by truncating passwords at 127
characters.

-- 
. o .   o . o   . . o   o . .   . o .
. . o   . o o   o . o   . o o   . . o
o o o   . o .   . o o   o o .   o o o


signature.asc
Description: PGP signature

Bug#899036: libgit2 0.27 transition

[Pirate Praveen]

Control: clone -1 -2
Control: reassign -2 libgit2-dev
Control: retitle -2 libgit2.pc requires openssl even though we use 
mbedtls now

Control: found -2 0.27.0+dfsg.1-0.1

On Mon, 21 May 2018 22:33:43 +0530 Pirate Praveen  
wrote:


The build failed, but it could be a bug in libgit2 itself as new version 
is supposed to be using mbedtls instead of openssl.


cloning and assigning to libgit2.

Bug#899036: libgit2 0.27 transition

[Pirate Praveen]

On Fri, 18 May 2018 21:20:16 +0530 Pirate Praveen 
 wrote:


libgit2 0.27 is now available in experimental. Please make sure your 
package is ready for this version by the time we upload this package to 
unstable in one to two weeks. The severity of this report will be raised 
to serious once libgit2 0.27 is uploaded to unstable.


The build failed, but it could be a bug in libgit2 itself as new version 
is supposed to be using mbedtls instead of openssl.


configure:19592: checking for GITCHANGEBAR
configure:19601: $PKG_CONFIG --exists --print-errors "$GP_GTK_PACKAGE >= 
2.18

  glib-2.0
  libgit2 >= 0.21"
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'libgit2', not found
configure:19606: $? = 1
configure:19624: $PKG_CONFIG --exists --print-errors "$GP_GTK_PACKAGE >= 
2.18

  glib-2.0
  libgit2 >= 0.21"
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'libgit2', not found
configure:19629: $? = 1
configure:19645: result: no
Package 'openssl', required by 'libgit2', not found
configure:19665: error: Package requirements (gtk+-3.0 >= 2.18
  glib-2.0
  libgit2 >= 0.21) were not met:

Package 'openssl', required by 'libgit2', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GITCHANGEBAR_CFLAGS
and GITCHANGEBAR_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

Bug#895866: Bug 895866

[Mirko Raner]

I'm a little surprised at the nonchalance here. In my mind, this is a
pretty serious bug that will cause many people a good amount of headaches,
myself included.
Tomcat 8.5 does not intrinsically require Java 9, so, introducing a
dependency by compiling it with Java 9 seems the wrong choice to begin
with. And having a package declare a dependency on Java 8 when it really
depends on Java 9 is a major bug; the package will install without errors
but will not actually work.

Personally, I would like to see a higher priority on this bug. And I'm sure
I will not be the only one who will appreciate this problem being fixed.

Bug#899248: debhelper: upstream changelog no longer installed

[Sven Joachim]

On 2018-05-21 16:28 +, Niels Thykier wrote:

> Control: tags -1 patch
> Control: severity -1 serious
>
> On Mon, 21 May 2018 17:05:54 +0200 Sven Joachim  wrote:
>> Package: debhelper
>> Version: 11.3
>> 
>> Upon rebuilding (binary-arch only) ncurses with debhelper 11.3, I found
>> that lintian would notice missing upstream changelogs:
>> 
>> ,
>> | P: libtinfo6: no-upstream-changelog
>> | P: libtinfo5: no-upstream-changelog
>> | P: lib64tinfo6: no-upstream-changelog
>> | P: ncurses-bin: no-upstream-changelog
>> | P: ncurses-examples: no-upstream-changelog
>> `
>> 
>> In debian/rules I have "dh_installchangelogs -a NEWS", nothing fancy.
>> And dh_installchangelogs silently skipped this file.
>> 
>> 
>> [...]
> Hi Sven,
>
> Thanks for reporting this bug.
>
> Could you please try the attached patch and see/confirm it fixes the
> issue for you?

Yep, that seems to work. :-)

Thanks,
   Sven

Bug#876478: ben tracker --global-conf ignores settings

[Mehdi Dogguy]

Hi,

On 2018-05-21 18:43, Sebastiaan Couwenberg wrote:


Do you still have to for the documentation update?



I've published new instructions on Ben's website (which
is generated from Ben's git repository). You can read
them here: https://ben.debian.net/#_tracker

Basically, it is:
$ ocamlbuild -pkg ben foo.cmx
$ ocamlopt -shared -o foo.cmxs _build/foo.cmx

In short: Do not use ocamlbuild to generate the .cmxs
file.

--
Mehdi

Bug#876478: ben tracker --global-conf ignores settings

[Sebastiaan Couwenberg]

On 05/15/2018 11:15 AM, Mehdi Dogguy wrote:
> On 2018-05-14 18:46, Sebastiaan Couwenberg wrote:
>> On 05/14/2018 08:26 AM, Mehdi Dogguy wrote:
>>> On 2018-05-14 08:01, Sebastiaan Couwenberg wrote:
 Unfortunately that doesn't apply cleanly on top of 0.7.4 for
 stretch. If
 you can provide a rebased commit for 0.7.4 I'm willing to test that.

>>>
>>> No problem. Here it is (attached). Thanks for your tests!
>>
>> Thanks for the patch, it doesn't seem to work as expected, though.
>>
>> `ben tracker` downloads the Packages & Sources files again even when
>> `ben download` downloaded them just before. It also uses the current
>> working directory for the downloaded files instead of the cache-dir from
>> the global.conf.
>>
>> It looks like this is caused by the custom template that was built with
>> the old ben, because switching the template to debianrt in global.conf
>> results in the expected behaviour.
>>
> 
> Indeed. I didn't explain fully how to apply the patch. My apologies.
> 
> The only effect of my second patch is to build templates differently to
> avoid linking and include all Ben's library. So in order to have this
> bug fixed, templates must be recompiled.
> 
>> Rebuilding the template fails when executed from the root of the git
>> directory:
>>
>>  $ ocamlbuild -pkg ben debiangis.cmxs
>>  + /usr/bin/ocamlopt unix.cmxa -I /usr/lib/ocaml/ocamlbuild
>> /usr/lib/ocaml/ocamlbuild/ocamlbuildlib.cmxa -I /usr/lib/ocaml -I
>> /usr/lib/ocaml/ben -I /usr/lib/ocaml/bytes -I /usr/lib/ocaml/ocamlgraph
>> -I /usr/lib/ocaml/pcre -I /usr/lib/ocaml/tyxml -I /usr/lib/ocaml/uutf
>> /usr/lib/ocaml/unix.cmxa /usr/lib/ocaml/pcre/pcre.cmxa
>> /usr/lib/ocaml/ocamlgraph/graph.cmxa /usr/lib/ocaml/str.cmxa
>> /usr/lib/ocaml/uutf/uutf.cmxa /usr/lib/ocaml/tyxml/tyxml.cmxa
>> /usr/lib/ocaml/ben/benl.cmxa myocamlbuild.ml
>> /usr/lib/ocaml/ocamlbuild/ocamlbuild.cmx -o myocamlbuild
>>  File "myocamlbuild.ml", line 1:
>>  Error: Files /usr/lib/ocaml/unix.cmxa and /usr/lib/ocaml/unix.cmxa
>>     both define a module named Unix
>>
> 
> It is true that the fix needs a documentation update to specify how
> templates should be built. I'll send you one very soon.
> 
> If you have an already built plugin, you may use the /usr/lib/ocaml/expunge
> tool to hide/remove non-necessary modules (that you can list using
> ocamlobjinfo). But, in any case, I'll provide a new procedure to build
> custom plugins.

Do you still have to for the documentation update?

Kind Regards,

Bas

Bug#894762: cups-daemon: with IdleExitTimeout 60, correctly exits when idle for 60 s, but immediately respawns [regression]

[Brian Potkin]

forcemerge 894762 898745
thanks


On Sun 20 May 2018 at 12:01:04 +0200, Francesco Poli wrote:

> On Fri, 18 May 2018 18:58:21 +0100 Brian Potkin wrote:
> 
> > On Wed 04 Apr 2018 at 22:29:07 +0200, Francesco Poli wrote:
> > 
> > > Looking forward to hearing back from you.
> > > Thanks for your time and patience!
> > 
> > Not too long a wait, I hope, Francesco.
> > 
> > Please try the technique in #898745
> > 
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898745
> > 
> > and see how you go on.
> 
> Hello,
> I have just given cups-daemon/2.2.7-5 a try with socket activation
> re-enabled.
> 
> I really seems to work as intended.
> The bug fix appears to solve the issue!
> Thank you so much.
> 
> I think this bug report may be forcemerged with #898745 (and thus
> closed). Please do so, if you agree

Doing as you suggest. Thanks for the update.

Cheers,

Brian.

Bug#899232: thunderbird: Main screen corrupted with 52.8.0-1

[Jean-Luc]

Hello Carsten,

Le 21/05/2018 à 17:02, Carsten Schoenert a écrit :

Hello Jean-Luc,

On Mon, May 21, 2018 at 11:18:36AM +0200, Jean-Luc Coulon (f5ibh) wrote:
  

Since the latest update to 52.8.0-1, the main window is corrupted. And
the problem is becoming worse as I use thunderbird: it seems that the
old data arent correctly overwritten.

I remarked this kind of behaviour also with the experimental version.

looks like a GTK+3 related issue which I can't reproduce on my
installations (under Testing). If you say you see this also with
Thunderbird from experimental I even more think this is mostly related
to GTK+3. The Thunderbird version 52.7.0-1 is now almost 6 weeks old,
version 52.8.0 and 60.0 are just some days or weeks and things in
unstable moving fast.

Thanks for the informations.

Currently there is nothing I can suggest to do. Except to play around
with Wayland/X11 and some other Desktop Environment.
FYI, I just tried gnome/xwayland , gnome/x11, gnome flashback 
(metacity): all these flavours of gnome give the same problem (them 
icorrectly managed).

But on the other hand, it works fine with xfce.

But I will not switch to xfce, I still have some colour managment with it.

I think it will not be easy to have a fix. The gtk guys have sometimes a 
stange way to manage the updates (API change without correct versioning 
for instance)


Regards

Jean-Luc

Bug#899038: libgit2 0.27 transition

[Pirate Praveen]

On Fri, 18 May 2018 21:22:48 +0530 Pirate Praveen 
 wrote:


libgit2 0.27 is now available in experimental. Please make sure your 
package is ready for this version by the time we upload this package to 
unstable in one to two weeks. The severity of this report will be raised 
to serious once libgit2 0.27 is uploaded to unstable.


I rebuilt cargo with libgit2 0.27 and got 4 test failures.

failures:

 dont_require_submodules_are_checked_out stdout 
	running `/<>/target/x86_64-unknown-linux-gnu/release/cargo 
build -v`

thread 'dont_require_submodules_are_checked_out' panicked at '
Expected: execs
but: exited with signal: 11
--- stdout

--- stderr
', debian/../vendor/hamcrest-0.1.1/src/core.rs:31:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.

stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::_print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: std::panicking::begin_panic_fmt
   7: hamcrest::core::assert_that
   8: git::dont_require_submodules_are_checked_out
   9: >::call_box
  10: __rust_maybe_catch_panic

 git_dep_build_cmd stdout 
	running `/<>/target/x86_64-unknown-linux-gnu/release/cargo 
build`

thread 'git_dep_build_cmd' panicked at '
Expected: execs
but: exited with signal: 11
--- stdout

--- stderr
warning: path 
`/<>/target/x86_64-unknown-linux-gnu/cit/t20/foo/src/foo.rs` 
was erroneously implicitly accepted for binary `foo`,

please set bin.path in Cargo.toml
', debian/../vendor/hamcrest-0.1.1/src/core.rs:31:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.

stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::_print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: std::panicking::begin_panic_fmt
   7: hamcrest::core::assert_that
   8: git::git_dep_build_cmd
   9: >::call_box
  10: __rust_maybe_catch_panic

 git_build_cmd_freshness stdout 
	running `/<>/target/x86_64-unknown-linux-gnu/release/cargo 
build`

thread 'git_build_cmd_freshness' panicked at '
Expected: execs
but: exited with signal: 6
--- stdout

--- stderr
malloc_consolidate(): invalid chunk size
', debian/../vendor/hamcrest-0.1.1/src/core.rs:31:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.

stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::_print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: std::panicking::begin_panic_fmt
   7: hamcrest::core::assert_that
   8: git::git_build_cmd_freshness
   9: >::call_box
  10: __rust_maybe_catch_panic


failures:
dont_require_submodules_are_checked_out
git_build_cmd_freshness
git_dep_build_cmd

test result: FAILED. 34 passed; 3 failed; 1 ignored; 0 measured; 0 
filtered out

Bug#899252: sloccount FTCBFS: uses the build architecture compiler

[Helmut Grohne]

Source: sloccount
Version: 2.26-5.2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

sloccount fails to cross build from source, because it uses the build
architecture compiler. The easiest way of passing cross tools to make is
letting dh_auto_build do it. After doing so, sloccount cross builds
successfully. Please consider applying the attached patch.

Helmut
diff --minimal -Nru sloccount-2.26/debian/changelog 
sloccount-2.26/debian/changelog
--- sloccount-2.26/debian/changelog 2017-03-17 15:01:31.0 +0100
+++ sloccount-2.26/debian/changelog 2018-05-21 18:30:08.0 +0200
@@ -1,3 +1,10 @@
+sloccount (2.26-5.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 21 May 2018 18:30:08 +0200
+
 sloccount (2.26-5.2) unstable; urgency=low
 
   * Non-maintainer upload.
diff --minimal -Nru sloccount-2.26/debian/rules sloccount-2.26/debian/rules
--- sloccount-2.26/debian/rules 2017-03-17 14:53:01.0 +0100
+++ sloccount-2.26/debian/rules 2018-05-21 18:30:05.0 +0200
@@ -62,7 +62,7 @@
dh_testdir
 
# Add here commands to compile the package.
-   $(MAKE)
+   dh_auto_build
 
touch build-stamp
 

Bug#899248: debhelper: upstream changelog no longer installed

[Niels Thykier]

Control: tags -1 patch
Control: severity -1 serious

On Mon, 21 May 2018 17:05:54 +0200 Sven Joachim  wrote:
> Package: debhelper
> Version: 11.3
> 
> Upon rebuilding (binary-arch only) ncurses with debhelper 11.3, I found
> that lintian would notice missing upstream changelogs:
> 
> ,
> | P: libtinfo6: no-upstream-changelog
> | P: libtinfo5: no-upstream-changelog
> | P: lib64tinfo6: no-upstream-changelog
> | P: ncurses-bin: no-upstream-changelog
> | P: ncurses-examples: no-upstream-changelog
> `
> 
> In debian/rules I have "dh_installchangelogs -a NEWS", nothing fancy.
> And dh_installchangelogs silently skipped this file.
> 
> 
> [...]
Hi Sven,

Thanks for reporting this bug.

Could you please try the attached patch and see/confirm it fixes the
issue for you?

Thanks,
~Niels
diff --git a/dh_installchangelogs b/dh_installchangelogs
index 6f4c7e9c..b1594411 100755
--- a/dh_installchangelogs
+++ b/dh_installchangelogs
@@ -152,6 +152,7 @@ init();
 my $news_name="NEWS.Debian";
 my $changelog_name="changelog.Debian";
 
+my $explicit_changelog = @ARGV ? 1 : 0;
 my $default_upstream = $ARGV[0];
 my $default_upstream_text=$default_upstream;
 my $default_upstream_html;
@@ -198,11 +199,15 @@ on_pkgs_in_parallel {
 		my $tmp=tmpdir($package);
 		my $changelog=pkgfile($package,"changelog");
 		my $news=pkgfile($package,"NEWS");
-		my $upstream_changelog = $ARGV[0];
+		my $upstream_changelog;
 		my ($upstream_changelog_text, $upstream_changelog_html);
 		my $changelog_from_tmp_dir = 0;
 
-		if (! defined($upstream_changelog)) {
+		if ($explicit_changelog) {
+			$upstream_changelog = $default_upstream;
+			$upstream_changelog_text = $default_upstream_text;
+			$upstream_changelog_html = $default_upstream_html;
+		} else {
 			# Check if the upstream build system provided a
 			# changelog
 			$upstream_changelog = find_changelog("${tmp}/usr/share/doc/${package}");
@@ -211,11 +216,6 @@ on_pkgs_in_parallel {
 $changelog_from_tmp_dir = 1;
 			}
 		}
-		if (not $upstream_changelog || defined($ARGV[0])) {
-			$upstream_changelog = $default_upstream;
-			$upstream_changelog_text = $default_upstream_text;
-			$upstream_changelog_html = $default_upstream_html;
-		}
 
 		if (!$changelog) {
 			$changelog="debian/changelog";

Bug#794983: More info needed

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo unreproducible

Hi! I can not reproduce this bug with the Qt version in testing. Can you still 
reproduce it?




-- 
16: De quien es Internet
* De DIOS dado que todas las cosas del mundo le pertenecen
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

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


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

Bug#862473: Unreproducible, mor einfo needed

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo unreproducible

Hi! I can not reproduce this bug. Are you still able to reproduce it with Qt 
in testing/unstable?

Thanks!

-- 
15: Que es el "Correo Electronico"
* El correo que te llega por la corriente
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

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


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

Bug#804204:

[Shriramana Sharma]

This and #798931 are the same bug though phrased differently.

As of Kubuntu Bionic the command service seems to be replaced by
systemctl so the requisite steps are:

#! /bin/sh
sudo a2enmod cgid
sudo systemctl restart apache2

-- 
Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा ူ၆ိျိါအူိ၆ါး

Bug#899248: debhelper: upstream changelog no longer installed

[Sven Joachim]

On 2018-05-21 17:05 +0200, Sven Joachim wrote:

> Package: debhelper
> Version: 11.3
>
> Upon rebuilding (binary-arch only) ncurses with debhelper 11.3, I found
> that lintian would notice missing upstream changelogs:
>
> ,
> | P: libtinfo6: no-upstream-changelog
> | P: libtinfo5: no-upstream-changelog
> | P: lib64tinfo6: no-upstream-changelog
> | P: ncurses-bin: no-upstream-changelog
> | P: ncurses-examples: no-upstream-changelog
> `
>
> In debian/rules I have "dh_installchangelogs -a NEWS", nothing fancy.
> And dh_installchangelogs silently skipped this file.

For the reference, commit 406bd37eb469 ("dh_installchangelogs: Prefer
existing changelog in d//u/s/d/") is the culprit.

Cheers,
   Sven

Bug#798931:

[Shriramana Sharma]

This and #804204 are the same bug though phrased differently.

As of Kubuntu Bionic the command service seems to be replaced by
systemctl so the requisite steps are:

#! /bin/sh
sudo a2enmod cgid
sudo systemctl restart apache2

-- 
Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा ူ၆ိျိါအူိ၆ါး

Bug#858294: Unreproducible, moreinfo needed

[Lisandro Damián Nicanor Pérez Meyer]

forwarded 858294 https://bugreports.qt.io/browse/QTBUG-68380
tag 858294 - moreinfo
thanks

El miércoles, 11 de abril de 2018 18:11:25 -03 Vladimir Berezenko escribió:
> Lisandro Dami?n Nicanor P?rez Meyer wrote:
> > > This is definitely reproducible. The current Qt5 version is 5.9.2-2 on
> > > my
> > > quad G5, and 5.8.4 on G4 powerbook. Both machines are not reacting on
> > > mousewheel events at all. I've tried KDE, LXQt. GTK2/3 apps are not
> > > affected at all.
> > 
> > Well, this is totally strange, as the only report we have heard so far is
> > from you.
> 
> This might be because others are not using Qt5 at all. It's strange, but
> understandable in case that newer Qt5 is using chromium as a web backend and
> it is not compileable to anything except x86 and arm and this renders Qt5
> almost unusable in modern cases.

While I agree that using chromium is not a great idea I still have to mae the 
point that there are lots of apps using Qt5 without the webengine submodule. 
So I tstill think it's weird we have only heard this from you so far.

> > I understand that you tried on two machines. Just to be clear: have you
> > tried with a new user?
> 
> The older installation on G5 is working the same in all users (tried new
> one). The G4 installation on powerbook is the fresh one.

ACK

> > There is the chance that you might have configured something in the same
> > way in both machines. If you still can reproduce this bug with a new user
> > then we can file a bug upstream.
> 
> Both installations are independent and on older one (G5 one) I've tried
> several users.

ACK.

> > Actually you should do it yourself, as I don't have any ways of
> > reproducing
> > this bug. Please file the upstream bug at https://bugreports.qt.io and
> > then
> > please send the bug number here. I'll happily subscribe to the bug to
> > follow it and, if possible at all, help.
> 
> Reading the bugs there I've found that it is possible that the problem is in
> QXcbAtom::ButtonWheel* wrong detection. I'm yet unable to find how does Qt5
> detects wheel buttons and where from it is getting the mouse events. The
> xinput shows everything ok, and Qt4 and GTK2/3 apps all are using the wheel
> perfectly
> Regarding the bugreport. I should register on the site and when I will fill
> bug report I'll attach it here.

Done, the URL is on the first line of the mail's body.

-- 
"Any sufficiently advanced technology is indistinguishable from magic"
 Arthur C. Clarke

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


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

Bug#897583: haskell-graphviz: FTBFS: unsatisfiable build-dependency: libghc-fgl-dev (< 5.6) but 5.6.0.0-2 is to be installed

[Gianfranco Costamagna]

control: fixed -1  2999.19.0.0.git20180507-1
control: close -1

fixed :)

G.

On Thu, 3 May 2018 08:09:38 +0200 Lucas Nussbaum  wrote:
> Source: haskell-graphviz
> Version: 2999.19.0.0-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20180502 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > +--+
> > | Install package build dependencies
> >|
> > +--+
> > 
> > 
> > Setup apt archive
> > -
> > 
> > Merged Build-Depends: cdbs, debhelper (>= 9), ghc (>= 8), ghc-prof, 
> > haskell-devscripts (>= 0.13), libghc-colour-dev (<< 2.4), libghc-colour-dev 
> > (>= 2.3), libghc-colour-prof, libghc-dlist-dev (<< 0.9), libghc-dlist-dev 
> > (>= 0.5), libghc-dlist-prof, libghc-fgl-dev (<< 5.6), libghc-fgl-dev (>= 
> > 5.4), libghc-fgl-prof, libghc-polyparse-dev (<< 1.13), libghc-polyparse-dev 
> > (>= 1.9), libghc-polyparse-prof, libghc-temporary-dev (<< 1.3), 
> > libghc-temporary-dev (>= 1.1), libghc-temporary-prof, libghc-text-dev, 
> > libghc-text-prof, libghc-wl-pprint-text-dev (<< 1.2.0.0), 
> > libghc-wl-pprint-text-dev (>= 1.1.0.0), libghc-wl-pprint-text-prof, 
> > ghc-doc, libghc-colour-doc, libghc-dlist-doc, libghc-fgl-doc, 
> > libghc-polyparse-doc, libghc-temporary-doc, libghc-text-doc, 
> > libghc-wl-pprint-text-doc
> > Filtered Build-Depends: cdbs, debhelper (>= 9), ghc (>= 8), ghc-prof, 
> > haskell-devscripts (>= 0.13), libghc-colour-dev (<< 2.4), libghc-colour-dev 
> > (>= 2.3), libghc-colour-prof, libghc-dlist-dev (<< 0.9), libghc-dlist-dev 
> > (>= 0.5), libghc-dlist-prof, libghc-fgl-dev (<< 5.6), libghc-fgl-dev (>= 
> > 5.4), libghc-fgl-prof, libghc-polyparse-dev (<< 1.13), libghc-polyparse-dev 
> > (>= 1.9), libghc-polyparse-prof, libghc-temporary-dev (<< 1.3), 
> > libghc-temporary-dev (>= 1.1), libghc-temporary-prof, libghc-text-dev, 
> > libghc-text-prof, libghc-wl-pprint-text-dev (<< 1.2.0.0), 
> > libghc-wl-pprint-text-dev (>= 1.1.0.0), libghc-wl-pprint-text-prof, 
> > ghc-doc, libghc-colour-doc, libghc-dlist-doc, libghc-fgl-doc, 
> > libghc-polyparse-doc, libghc-temporary-doc, libghc-text-doc, 
> > libghc-wl-pprint-text-doc
> > dpkg-deb: building package 'sbuild-build-depends-haskell-graphviz-dummy' in 
> > '/<>/resolver-leDeuw/apt_archive/sbuild-build-depends-haskell-graphviz-dummy.deb'.
> > dpkg-scanpackages: warning: Packages in archive but missing from override 
> > file:
> > dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> > sbuild-build-depends-haskell-graphviz-dummy
> > dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> > Ign:1 copy:/<>/resolver-leDeuw/apt_archive ./ InRelease
> > Get:2 copy:/<>/resolver-leDeuw/apt_archive ./ Release [963 B]
> > Ign:3 copy:/<>/resolver-leDeuw/apt_archive ./ Release.gpg
> > Get:4 copy:/<>/resolver-leDeuw/apt_archive ./ Sources [714 B]
> > Get:5 copy:/<>/resolver-leDeuw/apt_archive ./ Packages [780 B]
> > Fetched 2457 B in 0s (0 B/s)
> > Reading package lists...
> > Reading package lists...
> > 
> > Install haskell-graphviz build dependencies (apt-based resolver)
> > 
> > 
> > Installing build dependencies
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> > 
> > The following packages have unmet dependencies:
> >  sbuild-build-depends-haskell-graphviz-dummy : Depends: libghc-fgl-dev (< 
> > 5.6) but 5.6.0.0-2 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> > apt-get failed.
> 
> The full build log is available from:
>
> http://aws-logs.debian.net/2018/05/02/haskell-graphviz_2999.19.0.0-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

Bug#899250: bcpp FTCBFS: does not pass --host to ./configure

[Helmut Grohne]

Source: bcpp
Version: 0.0.20131209-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

bcpp fails to cross build from source, because it does not pass --host
to ./configure. The easiest way of doing so is deferring the task to
dh_auto_configure. After doing so, bcpp cross builds successfully.
Please consider applying the attached patch.

Helmut
diff --minimal -Nru bcpp-0.0.20131209/debian/changelog 
bcpp-0.0.20131209/debian/changelog
--- bcpp-0.0.20131209/debian/changelog  2015-08-02 13:56:56.0 +0200
+++ bcpp-0.0.20131209/debian/changelog  2018-05-21 16:56:06.0 +0200
@@ -1,3 +1,10 @@
+bcpp (0.0.20131209-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 21 May 2018 16:56:06 +0200
+
 bcpp (0.0.20131209-1) unstable; urgency=medium
 
   * New Upstream Release
diff --minimal -Nru bcpp-0.0.20131209/debian/rules 
bcpp-0.0.20131209/debian/rules
--- bcpp-0.0.20131209/debian/rules  2015-08-02 16:47:59.0 +0200
+++ bcpp-0.0.20131209/debian/rules  2018-05-21 16:55:15.0 +0200
@@ -21,10 +21,7 @@
cp -f /usr/share/misc/config.guess config.guess
 endif
 
-   ./configure \
-   --prefix=/usr \
-   --mandir=\$${prefix}/share/man \
-   --infodir=\$${prefix}/share/info \
+   dh_auto_configure -- \
CFLAGS="$(CFLAGS) $(CPPFLAGS) 
-DBCPP_CONFIG_DIR=\\\"/etc/bcpp/\\\"" \
CXXFLAGS="$(CXXFLAGS) $(CPPFLAGS) 
-DBCPP_CONFIG_DIR=\\\"/etc/bcpp/\\\"" \
LDFLAGS="$(LDFLAGS) $(LDFLAGS2)"

Bug#899251: installation-reports

[Luis Alberto SOSA]

Package: installation-reports

Boot method: 
Image version: 
Date: 

Machine: 
Processor: 
Memory: <2GB>
Partitions: 


Output of lspci -knn (o lspci -nn): < > Base System Installation Checklist: 
 [O] = OK, 
[E] = Error (descríbalo a continuación), [ ] = didn't try it Initial boot: [O] 
<¿Funcionó el arranque inicial?> Detect network card: [O] <¿Se configuró el 
hardware de red?> Configure network: [0] <¿Se configuró la red?> Detect CD: [0] 
<¿Se detectó la unidad de CD?> Load installer modules: [0] <¿Se cargaron los 
módulos del instalador?> Detect hard drives: [0] <¿Se detectaron los discos 
duros?> Partition hard drives: [0] <¿Se particionó el disco duro?> Install base 
system: [0] <¿Se instaló el sistema base?> Clock/timezone setup: [0] <¿Se 
configuró bien la zona horaria?> User/password setup: [0] <¿Se configuró 
correctamente el usuario?> Install tasks: [E] <¿Se instalaron bien las tareas?> 
Install boot loader: [ ] <¿Se instaló el gestor de arranque?> Overall install: 
[ ] <¿Reinició correctamente?> Comments/Problems: 

Bug#897893: (no subject)

[Eugene Budanov]

Hi!

I tried to make the kernel dump, but I found a strange situation. I can't 
create it when sending echo c > /proc/sysrq-trigger .

My settings:

# cat /etc/default/kdump-tools
USE_KDUMP=1
KDUMP_RUNLEVEL="1"
KDUMP_SAVEDIR="file:///var/crash"
KDUMP_NET="none"
KDUMP_SYSCTL="kernel.panic_on_oops=1"
KDUMP_COREDIR="/var/crash"
KDUMP_FAIL_CMD="reboot -f"
DEBUG_KERNEL=/usr/lib/debug/boot/vmlinux-4.9.0-6-amd64
MAKEDUMP_ARGS="-c -d 17

# cat /etc/sysctl.conf
#
# /etc/sysctl.conf - Configuration file for setting system variables
# See /etc/sysctl.d/ for additonal system variables
# See sysctl.conf (5) for information.
#

fs.file-max = 2097152
net.core.somaxconn = 1
net.core.rmem_max = 1048576
net.core.wmem_max = 16777216
net.ipv4.tcp_fin_timeout = 1
net.ipv4.tcp_keepalive_time = 1800
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
net.ipv4.tcp_syncookies = 1
net.ipv4.ip_local_port_range = 31000 65535
vm.swappiness = 0
kernel.core_pattern = /tmp/core.%e.%p.%h.%t
kernel.core_uses_pid = 1
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
vm.dirty_bytes = 536870912
vm.dirty_background_bytes = 268435456
net.netfilter.nf_conntrack_max = 12621440
net.nf_conntrack_max = 12621440
net.ipv4.netfilter.ip_conntrack_generic_timeout = 120
net.ipv4.netfilter.ip_conntrack_tcp_timeout_established = 120
net.ipv4.tcp_tw_recycle = 0
net.ipv4.tcp_tw_reuse = 0
net.ipv4.tcp_window_scaling = 1
kernel.shmmax = 40802189312
kernel.shmall = 9961473
vm.zone_reclaim_mode = 0
vm.min_free_kbytes = 524288
net.core.wmem_default = 65536
net.core.rmem_default = 1048576
net.core.netdev_max_backlog = 5
net.ipv4.tcp_low_latency = 1
net.ipv4.tcp_congestion_control = htcp
net.ipv6.conf.eth0.disable_ipv6 = 1
# KERNEL PANIC OPTIONS
kernel.panic = 1
kernel.hung_task_panic = 1
kernel.panic_on_io_nmi = 1
kernel.panic_on_oops = 1
kernel.panic_on_unrecovered_nmi = 1
kernel.softlockup_panic = 1

Of course, kdump-tools is running.

Additional information:
# dmesg |  grep "Reserving"
[    0.00] Reserving 512MB of memory at 336MB for crashkernel (System RAM: 
130958MB)

# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/system-root ro nomodeset 
net.ifnames=0 biosdevname=0 consoleblank=0 rootdelay=120 
transparent_hugepage=never quiet crashkernel=512M (yes, server have 128 GB RAM)

# cat /sys/kernel/kexec_crash_loaded
1

The packages kdump-tools linux-image-dbg crash kexec-tools makedumpfile is 
installed too.

What is I'm missing?

---
With best regards,
Eugene Budanov.

Bug#894703: davmail: Disconnects after IMAP FETCH command issued

[Sam Morris]

On Thu, Apr 05, 2018 at 01:30:14PM +0200, Alexandre Rossi wrote:
> Do you run with log4j.logger.davmail=DEBUG?
> Can you reproduce with upstream's prebuilt binaries?

I gave this a go today but can no longer reproduce this. I'm going to
put it down to flakey networking. :/

Thanks for taking a look anyway!

-- 
Sam Morris 
CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9

Bug#899249: ncmpcpp: symbol lookup error on launch - boost related?

[Robbie Harwood]

Package: ncmpcpp
Version: 0.8.1-1+b1
Severity: important

Dear Maintainer,

This may be the same bug as #899163 so feel free to handle appropriately, but
I didn't perform any forcing.  This just happened during an upgrade.

Anyway, whenever I try to launch ncmpcpp, it fails like so:

rharwood@seton:~$ ncmpcpp
ncmpcpp: symbol lookup error: ncmpcpp: undefined symbol: 
_ZNK5boost16re_detail_10620031icu_regex_traits_implementation12do_transformEPKiS3_PKN6icu_608CollatorE

Thanks!

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 
'unstable-debug'), (400, 'unstable'), (200, 'experimental-debug'), (200, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_US.UTF-8, LC_CTYPE=es_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ncmpcpp depends on:
ii  libboost-date-time1.62.01.62.0+dfsg-5+b1
ii  libboost-filesystem1.62.0   1.62.0+dfsg-5+b1
ii  libboost-locale1.62.0   1.62.0+dfsg-5+b1
ii  libboost-program-options1.62.0  1.62.0+dfsg-5+b1
ii  libboost-regex1.62.01.62.0+dfsg-5+b1
ii  libboost-system1.62.0   1.62.0+dfsg-5+b1
ii  libboost-thread1.62.0   1.62.0+dfsg-5+b1
ii  libc6   2.27-3
ii  libcurl3-gnutls 7.58.0-2
ii  libfftw3-double33.3.7-1+b1
ii  libgcc1 1:8.1.0-3
ii  libicu6060.2-6
ii  libmpdclient2   2.11-1
ii  libncursesw66.1+20180210-3
ii  libreadline77.0-5
ii  libstdc++6  8.1.0-3
ii  libtag1v5   1.11.1+dfsg.1-0.2+b1
ii  libtinfo6   6.1+20180210-3

ncmpcpp recommends no packages.

Versions of packages ncmpcpp suggests:
pn  desktop-file-utils  
ii  mpd 0.20.19-1+b1

-- no debconf information

Bug#899232: thunderbird: Main screen corrupted with 52.8.0-1

[Carsten Schoenert]

Hello Jean-Luc,

On Mon, May 21, 2018 at 11:18:36AM +0200, Jean-Luc Coulon (f5ibh) wrote:
 
> Since the latest update to 52.8.0-1, the main window is corrupted. And
> the problem is becoming worse as I use thunderbird: it seems that the
> old data arent correctly overwritten.
> 
> I remarked this kind of behaviour also with the experimental version.

looks like a GTK+3 related issue which I can't reproduce on my
installations (under Testing). If you say you see this also with
Thunderbird from experimental I even more think this is mostly related
to GTK+3. The Thunderbird version 52.7.0-1 is now almost 6 weeks old,
version 52.8.0 and 60.0 are just some days or weeks and things in
unstable moving fast.

Currently there is nothing I can suggest to do. Except to play around
with Wayland/X11 and some other Desktop Environment.

Regards
Carsten

Bug#899248: debhelper: upstream changelog no longer installed

[Sven Joachim]

Package: debhelper
Version: 11.3

Upon rebuilding (binary-arch only) ncurses with debhelper 11.3, I found
that lintian would notice missing upstream changelogs:

,
| P: libtinfo6: no-upstream-changelog
| P: libtinfo5: no-upstream-changelog
| P: lib64tinfo6: no-upstream-changelog
| P: ncurses-bin: no-upstream-changelog
| P: ncurses-examples: no-upstream-changelog
`

In debian/rules I have "dh_installchangelogs -a NEWS", nothing fancy.
And dh_installchangelogs silently skipped this file.


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20180224.1
ii  dh-autoreconf19
ii  dh-strip-nondeterminism  0.041-1
ii  dpkg 1.19.1
ii  dpkg-dev 1.19.1
ii  dwz  0.12-2
ii  file 1:5.33-2
ii  libdpkg-perl 1.19.1
ii  man-db   2.8.3-2
ii  perl 5.26.2-5
ii  po-debconf   1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201701

-- no debconf information

Bug#899234: git-buildpackage: gbp-push fails when there is no upstream branch

[Paride Legovini]

On 21/05/2018 13.04, Guido Günther wrote:
> On Mon, May 21, 2018 at 11:22:31AM +0200, Paride Legovini wrote:
>>
>> /usr/share/doc/git-buildpackage/manual-html/gbp.import.upstream-git.html
> 
> I think the documentation above does not suggest that there is no
> upstream branch, rather that you don't need gbp import-orig to maintain
> it. At least that's the intention.
> [...]
> (I'm maintaining several packages directly out of git).

I didn't lose the opportunity to have a look at the state of the art.

Well, it seems to me that calypso has a branch layout that will bring to
the issue I'm describing (no upstream branch). I don't think it is
currently possible to use gbp-push with it.

Paride

Bug#899247: openshot-qt: fails to start - requires pyhton module 'requests'

[Cesare Tirabassi]

Package: openshot-qt
Version: 2.4.1+dfsg1-1
Severity: important



-- 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-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openshot-qt depends on:
ii  fonts-cantarell 0.0.25-4
ii  libjs-jquery3.2.1-1
ii  python3 3.6.5-3
ii  python3-openshot0.1.9+dfsg1-3+b2
ii  python3-pyqt5   5.10.1+dfsg-2
ii  python3-pyqt5.qtsvg 5.10.1+dfsg-2
ii  python3-pyqt5.qtwebkit  5.10.1+dfsg-2
ii  python3-zmq 17.0.0-1

Versions of packages openshot-qt recommends:
ii  blender   2.79.b+dfsg0-1
pn  inkscape  

Versions of packages openshot-qt suggests:
pn  openshot-qt-doc  

-- no debconf information

Attemping to run openshot-qt on my system leads to the following error:

Loaded modules from installed directory: 
/usr/lib/python3/dist-packages/openshot_qt
  launch:INFO 
  launch:INFOOpenShot (version 2.4.1)
  launch:INFO 
qt.qpa.screen: Output DisplayPort-0 is not connected
qt.qpa.screen: Output HDMI-A-0 is not connected
qt.qpa.screen: Failed to parse EDID data for output "DVI-I-0" edid data:  ""
qt.qpa.screen: Failed to parse EDID data for output "DVI-D-1" edid data:  ""
qt.qpa.screen: adding QXcbScreen(0x25951c0, name="DVI-I-0", 
geometry=1920x1080+0+0, availableGeometry=1920x1080+0+0, devicePixelRatio=1.0, 
logicalDpi=QPair(96.1,96.3), physicalSize=521.0x293.0mm, screenNumber=0, 
virtualSize=3200x1080 (3200.0x1080.0mm), 
orientation=Qt::ScreenOrientation(LandscapeOrientation), depth=24, 
refreshRate=60.0, root=5ea, windowManagerName="Openbox") (Primary: true )
qt.qpa.screen: adding QXcbScreen(0x25952b0, name="DVI-D-1", 
geometry=1280x1024+1920+0, availableGeometry=1280x1024+1920+0, 
devicePixelRatio=1.0, logicalDpi=QPair(96.1,96.3), physicalSize=338.0x270.0mm, 
screenNumber=0, virtualSize=3200x1080 (3200.0x1080.0mm), 
orientation=Qt::ScreenOrientation(LandscapeOrientation), depth=24, 
refreshRate=60.0, root=5ea, windowManagerName="Openbox") (Primary: false )
qt.qpa.screen: primary output is "DVI-I-0"
qt.qpa.gl: Choosing xcb gl-integration based on following priority
 ("xcb_glx", "xcb_egl")
qt.qpa.gl: Xcb GLX gl-integration created
qt.qpa.gl: Xcb GLX gl-integration successfully initialized
 app:INFO openshot-qt version: 2.4.1
 app:INFO libopenshot version: 0.1.9
 app:INFO platform: Linux-4.16.0-1-amd64-x86_64-with-debian-buster-sid
 app:INFO processor: 
 app:INFO machine: x86_64
 app:INFO python version: 3.6.5
 app:INFO qt5 version: 5.10.1
 app:INFO pyqt5 version: 5.10.1
  logger:ERROR Traceback (most recent call last):
  logger:ERROR   File "/usr/bin/openshot-qt", line 11, in 
  logger:ERROR load_entry_point('openshot-qt==2.4.1', 'gui_scripts', 
'openshot-qt')()
  logger:ERROR   File 
"/usr/lib/python3/dist-packages/openshot_qt/launch.py", line 70, in main
  logger:ERROR app = OpenShotApp(sys.argv)
  logger:ERROR   File 
"/usr/lib/python3/dist-packages/openshot_qt/classes/app.py", line 91, in 
__init__
  logger:ERROR from classes import exceptions
  logger:ERROR   File 
"/usr/lib/python3/dist-packages/openshot_qt/classes/exceptions.py", line 30, in 

  logger:ERROR from classes.metrics import track_exception_stacktrace
  logger:ERROR   File 
"/usr/lib/python3/dist-packages/openshot_qt/classes/metrics.py", line 30, in 

  logger:ERROR import requests
  logger:ERROR ModuleNotFoundError
  logger:ERROR :
  logger:ERROR No module named 'requests'

Installing python3-requests solves the issue. Perhaps python3-requests should
be a dependency of openshot-qt?