Processed: libtesseract-dev: headers broken: missing std::; headers missing

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:opencv
Bug #884903 [libtesseract-dev] libtesseract-dev: headers broken: missing std::; 
headers missing
Added indication that 884903 affects src:opencv

-- 
884903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884903: libtesseract-dev: headers broken: missing std::; headers missing

[Andreas Beckmann]

Package: libtesseract-dev
Version: 4.00~git2174-3b62badd-5
Severity: serious
Control: affects -1 src:opencv

Hi,

tesseract 4 causes opencv/experimental to FTBFS:

In file included from /usr/include/tesseract/ltrresultiterator.h:26:0,
 from /usr/include/tesseract/resultiterator.h:26,
 from /usr/include/tesseract/baseapi.h:31,
 from 
/build/opencv-3.3.0+dfsg/contrib/modules/text/src/precomp.hpp:51,
 from 
/build/opencv-3.3.0+dfsg/contrib/modules/text/src/erfilter.cpp:43:
/usr/include/tesseract/unichar.h:164:10: error: 'string' does not name a type; 
did you mean 'stdin'?
   static string UTF32ToUTF8(const std::vector& str32);
  ^~
  stdin
modules/text/CMakeFiles/opencv_text.dir/build.make:65: recipe for target 
'modules/text/CMakeFiles/opencv_text.dir/src/erfilter.cpp.o' failed
make[4]: *** [modules/text/CMakeFiles/opencv_text.dir/src/erfilter.cpp.o] Error 
1


Let's compile each tesseract header:

for header in /usr/include/tesseract/*.h ; do echo $header ; echo "#include 
<$(basename $header)>" | g++ -c -xc++ -o /tmp/o.o -I /usr/include/tesseract - ; 
done

I'll only list each error once:

In file included from :1:0:
/usr/include/tesseract/convolve.h:25:10: fatal error: matrix.h: No such file or 
directory
 #include "matrix.h"
  ^~
compilation terminated.

In file included from :1:0:
/usr/include/tesseract/functions.h:24:10: fatal error: tprintf.h: No such file 
or directory
 #include "tprintf.h"
  ^~~
compilation terminated.

In file included from /usr/include/tesseract/unicharset.h:29:0,
 from /usr/include/tesseract/osdetect.h:24,
 from :1:
/usr/include/tesseract/unichar.h:164:10: error: 'string' does not name a type; 
did you mean 'stdin'?
   static string UTF32ToUTF8(const std::vector& str32);
  ^~
  stdin
In file included from /usr/include/tesseract/osdetect.h:24:0,
 from :1:
/usr/include/tesseract/unicharset.h:241:10: error: 'string' does not name a 
type; did you mean 'stdin'?
   static string CleanupString(const char* utf8_str) {
  ^~
  stdin
/usr/include/tesseract/unicharset.h:244:10: error: 'string' does not name a 
type; did you mean 'stdin'?
   static string CleanupString(const char* utf8_str, int length);
  ^~
  stdin
/usr/include/tesseract/unicharset.h: In member function 'void 
UNICHARSET::unichar_insert_backwards_compatible(const char*)':
/usr/include/tesseract/unicharset.h:265:5: error: 'string' was not declared in 
this scope
 string cleaned = CleanupString(unichar_repr);
 ^~

In file included from :1:0:
/usr/include/tesseract/renderer.h:215:29: error: 'Pix' has not been declared
   static bool imageToPDFObj(Pix *pix, char *filename, long int objnum,
 ^~~


Andreas

Bug#884900: gnome-keysign: FTBFS on i386: Segmentation fault during tests

[Andreas Beckmann]

Source: gnome-keysign
Version: 0.9.6-1~exp1
Severity: serious
Justification: fails to build from source

Hi,

gnome-keysign/experimental FTBFS on i386:

   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/gnome-keysign-0.9.6/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
gpg: keybox '/tmp/tmpih30Kw/pubring.kbx' created
gpg: /tmp/tmpih30Kw/trustdb.gpg: trustdb created
gpg: key 1D4E64C28F62260A: public key "Bruce Wayne (https://bruce.wayne) 
" imported
gpg: key 1D4E64C28F62260A: secret key imported
gpg: Total number processed: 1
gpg:   imported: 1
gpg:   secret keys read: 1
gpg:   secret keys imported: 1
gpg: keybox '/tmp/tmpPlALvw/pubring.kbx' created
gpg: /tmp/tmpPlALvw/trustdb.gpg: trustdb created
gpg: key A5C89B8B383EE754: public key "Test Key " imported
gpg: key A5C89B8B383EE754: secret key imported
gpg: Total number processed: 1
gpg:   imported: 1
gpg:   secret keys read: 1
gpg:   secret keys imported: 1
Segmentation fault
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=139: cd 
/build/gnome-keysign-0.9.6/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:20: recipe for target 'build' failed
make: *** [build] Error 25

This failure happens every time.
It builds fine on amd64.


Andreas


gnome-keysign_0.9.6-1~exp1.log.gz
Description: application/gzip

Bug#884898: icu: fails to clean after build: parallel distclean race

[Andreas Beckmann]

Source: icu
Version: 60.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

during a pbuilder --twice test I noticed that icu failed to clean after
the first build. That cleaning is usually not performed during regular
builds since the build tree and chroot are discarded anyway.
I was not able to reproduce this failure with a sequential (parallel=1)
build, but with a paralle=2 and parallel=4 build it happened frequently:

 fakeroot debian/rules clean
dh clean --sourcedirectory=/build/icu-60.2/source/ --parallel
   dh_auto_clean -O--sourcedirectory=/build/icu-60.2/source/ -O--parallel
cd source && make -j2 distclean
make[1]: Entering directory '/build/icu-60.2/source'
test -z "*~" || rm -rf *~
rm -rf "test-*.xml"
rm -rf "perf-*.xml"
make[1]: Making `distclean' in `stubdata'
rm -rf ./config/icu-uc.pc ./config/icu-i18n.pc ./config/icu-lx.pc 
./config/icu-io.pc ./config/icuinfo.xml
rm -rf Doxyfile doc icu-docs.zip
make[2]: Entering directory '/build/icu-60.2/source/stubdata'
test -z "*~ stubdata.d   " || rm -rf *~ stubdata.d
rm -rf stubdata.o stubdata.ao libicudata.a libicudata.so.60.2 libicudata.so.60 
libicudata.so  libicudata.so.60.2
rm -rf ./config/Makefile.inc ./config/pkgdata.inc ./config/icu-config 
./config/icu.pc ./config/icu-uc.pc ./config/icu-i18n.pc ./config/icu-lx.pc 
./config/icu-io.pc
rm -rf Makefile
make[2]: Leaving directory '/build/icu-60.2/source/stubdata'
make[1]: Making `distclean' in `common'
rm -rf config.cache config.log config.status ./config/icucross.mk 
./config/icucross.inc autom4te.cache uconfig.h.prepend
make[2]: Entering directory '/build/icu-60.2/source/common'
make[2]: *** No rule to make target '../config.status', needed by 'Makefile'.  
Stop.
make[2]: Leaving directory '/build/icu-60.2/source/common'
Makefile:149: recipe for target 'distclean-recursive' failed
make[1]: *** [distclean-recursive] Error 2
make[1]: *** Waiting for unfinished jobs
rm -rf Makefile config/Makefile icudefs.mk ./lib ./bin
rm -rf dist
make[1]: Leaving directory '/build/icu-60.2/source'
dh_auto_clean: cd source && make -j2 distclean returned exit code 2
debian/rules:62: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2

 fakeroot debian/rules clean
dh clean --sourcedirectory=/build/icu-60.2/source/ --parallel
   dh_auto_clean -O--sourcedirectory=/build/icu-60.2/source/ -O--parallel
cd source && make -j4 distclean
make[1]: Entering directory '/build/icu-60.2/source'
test -z "*~" || rm -rf *~
rm -rf "test-*.xml"
make[1]: Making `distclean' in `stubdata'
rm -rf "perf-*.xml"
make[2]: Entering directory '/build/icu-60.2/source/stubdata'
test -z "*~ stubdata.d   " || rm -rf *~ stubdata.d   
rm -rf ./config/icu-uc.pc ./config/icu-i18n.pc ./config/icu-lx.pc 
./config/icu-io.pc ./config/icuinfo.xml
rm -rf stubdata.o stubdata.ao libicudata.a libicudata.so.60.2 libicudata.so.60 
libicudata.so  libicudata.so.60.2
rm -rf Doxyfile doc icu-docs.zip
rm -rf Makefile
make[2]: Leaving directory '/build/icu-60.2/source/stubdata'
make[1]: Making `distclean' in `common'
make[2]: Entering directory '/build/icu-60.2/source/common'
test -z "*~ errorcode.d putil.d umath.d utypes.d uinvchar.d umutex.d ucln_cmn.d 
uinit.d uobject.d cmemory.d charstr.d cstr.d udata.d ucmndata.d udatamem.d 
umapfile.d udataswp.d ucol_swp.d utrace.d uhash.d uhash_us
.d uenum.d ustrenum.d uvector.d ustack.d uvectr32.d uvectr64.d ucnv.d 
ucnv_bld.d ucnv_cnv.d ucnv_io.d ucnv_cb.d ucnv_err.d ucnvlat1.d ucnv_u7.d 
ucnv_u8.d ucnv_u16.d ucnv_u32.d ucnvscsu.d ucnvbocu.d ucnv_ext.d ucnv
mbcs.d ucnv2022.d ucnvhz.d ucnv_lmb.d ucnvisci.d ucnvdisp.d ucnv_set.d 
ucnv_ct.d resource.d uresbund.d ures_cnv.d uresdata.d resbund.d resbund_cnv.d 
ucurr.d messagepattern.d ucat.d locmap.d uloc.d locid.d locutil.
d locavailable.d locdispnames.d locdspnm.d loclikely.d locresdata.d 
bytestream.d stringpiece.d bytesinkutil.d stringtriebuilder.d 
bytestriebuilder.d bytestrie.d bytestrieiterator.d ucharstrie.d 
ucharstriebuilder.d
 ucharstrieiterator.d dictionarydata.d edits.d appendable.d ustr_cnv.d 
unistr_cnv.d unistr.d unistr_case.d unistr_props.d utf_impl.d ustring.d 
ustrcase.d ucasemap.d ucasemap_titlecase_brkiter.d cstring.d ustrfmt.d
 ustrtrns.d ustr_wcs.d utext.d unistr_case_locale.d ustrcase_locale.d 
unistr_titlecase_brkiter.d ustr_titlecase_brkiter.d normalizer2impl.d 
normalizer2.d filterednormalizer2.d normlzr.d unorm.d unormcmp.d loadedno
rmalizer2impl.d chariter.d schriter.d uchriter.d uiter.d patternprops.d uchar.d 
uprops.d ucase.d propname.d ubidi_props.d ubidi.d ubidiwrt.d ubidiln.d ushape.d 
uscript.d uscript_props.d usc_impl.d unames.d utrie.d
 utrie2.d utrie2_builder.d bmpset.d unisetspan.d uset_props.d uniset_props.d 
uniset_closure.d uset.d uniset.d usetiter.d ruleiter.d caniter.d unifilt.d 
unifunct.d uarrsort.d brkiter.d ubrk.d brkeng.d dictbe.d filt
eredbrk.d rbbi.d rbbidata.d 

Processed: Re: librsvg: FTBFS on (32-bit && !any-i386)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 884850 https://gitlab.gnome.org/GNOME/librsvg/issues/178
Bug #884850 [src:librsvg] librsvg: FTBFS on (32-bit && !any-i386): 
masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from 
reference image
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/librsvg/issues/178'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
884850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884889: lightdm: FTBFS twice in a row: No rule to make target 'liblightdm-gobject-1.deps'

[Andreas Beckmann]

Source: lightdm
Version: 1.18.3-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

lightdm/experimental fails to build twice in a row. (I didn't check the
version in sid). The first build succeeds, the subsequent
'debian/rules clean' runs 'make distclean' which deletes
'liblightdm-gobject/liblightdm-gobject-1.deps' but that file is not
regenerated during the second build, failing with

make[3]: *** No rule to make target 'liblightdm-gobject-1.deps', needed by 
'all-am'.  Stop.

In addition to that, also doc/html/ is cleaned up, probably resulting
in a similar problem as #884813 (xfce-panel).


Andreas


lightdm_1.18.3-5_twice.log.gz
Description: application/gzip

Processed: Re: pypar2: depends on vte which is deprecated

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790185 [src:pypar2] pypar2: depends on vte which is deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790185 [src:pypar2] pypar2: depends on vte which is deprecated
Removed tag(s) stretch.

-- 
790185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: guake: depends on vte which is deprecated

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790176 [src:guake] guake: depends on vte which is deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790176 [src:guake] guake: depends on vte which is deprecated
Removed tag(s) stretch.

-- 
790176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: hotssh: depends on vte which is deprecated

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790179 [src:hotssh] hotssh: depends on vte which is deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch +buster
Bug #790179 [src:hotssh] hotssh: depends on vte which is deprecated
Removed tag(s) stretch.
Bug #790179 [src:hotssh] hotssh: depends on vte which is deprecated
Ignoring request to alter tags of bug #790179 to the same tags previously set

-- 
790179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884668: marked as pending

[Aaron M . Ucko]

tag 884668 pending
thanks

Hello,

Bug #884668 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/python-dsv.git/commit/?id=0072281

---
commit 0072281fce98f2c2bbb43ac779f811ed4eb34029
Author: Aaron M. Ucko 
Date:   Wed Dec 20 18:45:58 2017 -0500

debian/control: Build depend on split-out 2to3.  (Closes: #884668.)

diff --git a/debian/changelog b/debian/changelog
index 947d15e..7b66b1f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,9 @@
 python-dsv (1.4.1-6) UNRELEASED; urgency=medium
 
   * NOT YET RELEASED.
+  * debian/control: Build depend on split-out 2to3.  (Closes: #884668.)
 
- -- Aaron M. Ucko   Wed, 20 Dec 2017 18:28:58 -0500
+ -- Aaron M. Ucko   Wed, 20 Dec 2017 18:45:57 -0500
 
 python-dsv (1.4.1-5) unstable; urgency=medium
 

Processed: Bug#884668 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 884668 pending
Bug #884668 [src:python-dsv] 2to3 binary moved to it's own 2to3 package
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#884048: gnome-shell: /usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with segfault

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #884048 [libical3] gnome-shell: 
/usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with 
segfault
Severity set to 'important' from 'serious'

-- 
884048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884048: gnome-shell: /usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with segfault

[Pino Toscano]

Control: severity -1 important

In data sabato 16 dicembre 2017 23:25:16 CET, Adrian Bunk ha scritto:
> Control: severity -1 serious
> 
> On Sat, Dec 16, 2017 at 09:19:18PM +0100, Michael Biebl wrote:
> > Control: severity -1 important
> > 
> > > Dec 10 13:17:40 lavaine kernel: [ 3324.799650] gnome-shell-cal[2352]: 
> > > segfault at 10812 ip 7f2eeafd0324 sp 7ffd0bc3d6d0 error 4 in 
> > > libical.so.2.0.0[7f2eeaf8d000+5e000]
> > To explain what's happening here:
> > gnome-shell links directly against libical (here against v2) and also
> > against libecal (from evolution-data-server).
> > evolution-data-server was updated to link against libical v3. The result
> > is, that gnome-shell was now loading libical2 (directly) and libical3
> > (indirectly via libecal) into its address space. This is not supported
> > and leads to the crash.
> > 
> > I decided to add a Conflicts: libical2 to libecal (see #884012) to avoid
> > this situation.
> > 
> > So from my POV, this bug can be closed. Other DDs mentioned on
> > #debian-devel though, that this conflicts should be added directly to
> > libical3. I'm thus leaving this bug report open for further discussion
> > but downgrade the severity, as the immediate issue (the segfault in
> > gnome-shell) is addressed by #884012.
> 
> KDE has/had similar problems, setting back to RC to prevent testing 
> migration until this is sorted out.

What are the "similar problems" of "KDE"? Neither the kdelibs 4.x nor
the KF5 stacks support libical3, so everything uses libical2 for now.
The only exception is digikam, for which I just requested a rebuild
(since kcalcore was fixed to properly use libical2, see #883921).

Since I don't see any other message in this bug regarding problems,
nor I see any bug filed in any part of the KDE stack, then I'm lowering
the severity of this bug, so this rushed doko-transition can be finally
unblocked (unblocking the marble+libkipi transition too).

-- 
Pino Toscano

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

Bug#884107: marked as done (apscheduler FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Wed, 20 Dec 2017 22:49:47 +
with message-id 
and subject line Bug#884107: fixed in apscheduler 3.4.0-2
has caused the Debian Bug report #884107,
regarding apscheduler FTBFS: test failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
884107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apscheduler
Version: 3.4.0-1
Severity: serious

Some recent change in unstable makes apscheduler FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/apscheduler-3.4.0'
dh_auto_test -- --system=custom --test-args="{interpreter} setup.py test"
I: pybuild base:184: python2.7 setup.py test
running test
running egg_info
creating APScheduler.egg-info
writing requirements to APScheduler.egg-info/requires.txt
writing APScheduler.egg-info/PKG-INFO
writing top-level names to APScheduler.egg-info/top_level.txt
writing dependency_links to APScheduler.egg-info/dependency_links.txt
writing entry points to APScheduler.egg-info/entry_points.txt
writing manifest file 'APScheduler.egg-info/SOURCES.txt'
reading manifest file 'APScheduler.egg-info/SOURCES.txt'
writing manifest file 'APScheduler.egg-info/SOURCES.txt'
running build_ext
tests.test_executors_py35 (unittest.loader.ModuleImportFailure) ... ERROR

==
ERROR: tests.test_executors_py35 (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: tests.test_executors_py35
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File "/build/1st/apscheduler-3.4.0/tests/test_executors_py35.py", line 44
async def waiter(sleep, exception):
^
SyntaxError: invalid syntax


--
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: 
error: Test failed: 
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
setup.py test
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 
--system=custom "--test-args={interpreter} setup.py test" returned exit code 13
debian/rules:17: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: apscheduler
Source-Version: 3.4.0-2

We believe that the bug you reported is fixed in the latest version of
apscheduler, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated apscheduler 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Dec 2017 19:22:46 +
Source: apscheduler
Binary: python-apscheduler python3-apscheduler
Architecture: source all
Version: 3.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 python-apscheduler - In-process task scheduler with Cron-like capabilities
 python3-apscheduler - In-process task scheduler with Cron-like capabilities
Closes: 884107
Changes:
 apscheduler (3.4.0-2) unstable; urgency=medium
 .
   * Patch to don't check for SCM source version.
   * Fix test with Python 2.7 (closes: #884107).
   * Add python{,3}-trollius to build depends.
   * Update debhelper level to 11 .
   * Update Standards-Version to 4.1.2 .
Checksums-Sha1:
 32356c21cda4556cbba221c8430e58d18e565427 2447 apscheduler_3.4.0-2.dsc
 893d5cb6abdf13801b9ae73d254d5709ecce302a 4184 apscheduler_3.4.0-2.debian.tar.xz
 

Processed: limit source to alt-ergo, tagging 882162

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source alt-ergo
Limiting to bugs with field 'source' containing at least one of 'alt-ergo'
Limit currently set to 'source':'alt-ergo'

> tags 882162 + pending
Bug #882162 [src:alt-ergo] alt-ergo FTBFS: Error: This expression has type 
Sim.Core.t * bool but an expression was expected of type Sim.Core.t
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
882162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884874: phonon-backend-vlc: Application using phonon are crashing with vlc 3.0.0~rc2

[Sandro Knauß]

Source: phonon-backend-vlc
Version: 0.9.0-2
Severity: serious

with the upload of vlc 3.0.0~rc2-1 at unstable phonon applications like
amarok and kcmshell4 kcm_phonon are constanly crashing. For the moment I
switched to gstreamer backend.


Best Regards,

sandro

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

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

Processed: fixed 884241 in 1.56-1+deb9u1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # add fixing version for stretch-security uploaded version which did not 
> contain bug closer
> fixed 884241 1.56-1+deb9u1
Bug #884241 {Done: Markus Koschany } [src:bouncycastle] 
bouncycastle: CVE-2017-13098
The source 'bouncycastle' and version '1.56-1+deb9u1' do not appear to match 
any binary packages
Marked as fixed in versions bouncycastle/1.56-1+deb9u1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 884291, tagging 884292

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 884291 + pending
Bug #884291 [src:akonadi-search] akonadi-search: Cannot fulfill the build 
dependencies
Added tag(s) pending.
> tags 884292 + pending
Bug #884292 [libkf5tnef5] ktnef: Cannot fulfill the build dependencies
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884291
884292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 801331 is grave, tagging 801331

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 801331 grave
Bug #801331 [jdresolve] jdresolve: malformed output in jessie
Severity set to 'grave' from 'important'
> tags 801331 + patch
Bug #801331 [jdresolve] jdresolve: malformed output in jessie
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
801331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884807: getmail: does not ship /usr/bin/getmail

[Daniel Kahn Gillmor]

Hi Osamu--

thanks very much for your packaging work for getmail!

On Thu 2017-12-21 00:48:44 +0900, Osamu Aoki wrote:
> On Tue, Dec 19, 2017 at 06:36:15PM -0500, Daniel Kahn Gillmor wrote:
>> On Tue 2017-12-19 16:47:01 -0500, Daniel Kahn Gillmor wrote:
>> > somehow /usr/bin/getmail got dropped from the getmail 5.5-1 packaging :/
>> 
>> I've pushed some changes to the master branch of
>> https://anonscm.debian.org/git/collab-maint/getmail.git that resolve
>> this matter for me.
>> 
>> they also do a little bit of packaging cleanup.  I hope they're useful!
>
> Thanks. I realized your change just before upload.  Good.
> Yes this cleans my rough edges.
>
> I had some changes locally with a bit different style too ;-) I have
> debian/rules with:
>
>   # Always use debian/getmail as destination (not debian/tmp)
>   # even when dummy getmail4 package exists
>   override_dh_auto_install:
>   dh_auto_install --destdir debian/getmail

ok, it looks like i tend to prefer the more declarative style, and you
prefer the imperative style.  You're the maintainer, so your decision
goes :)

Just so you know why i prefer the declarative style, though:

i think with your imperative changes to the debian/rules makefile, a new
upstreamversion that injects something funky into the filesystem will
just have it happen (possibly without the maintainer noticing).

With the declarative approach i'd outlined (that is, listing everything
explicitly in debian/getmail.{docs,install,manpages}, and including
dh_missing --fail-missing), the packager has to actively acknowledge
changes to the installed filesystem, which i like as a double-check
during packaging itself.

> So when we drop getmail4 transition package, migration needs only
> dropping it in the debian/control field.

I think that would happen either way :)

anyway, just thought i'd explain my reasoning.  I'm happy to follow your
lead on the package.

All the best,

 --dkg

Bug#884807: marked as done (getmail: does not ship /usr/bin/getmail)

[Debian Bug Tracking System]

Your message dated Wed, 20 Dec 2017 16:20:30 +
with message-id 
and subject line Bug#884807: fixed in getmail 5.5-2
has caused the Debian Bug report #884807,
regarding getmail: does not ship /usr/bin/getmail
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
884807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: getmail
Version: 5.5-1
Severity: grave
Justification: renders package unusable

0 dkg@alice:/tmp/cdtemp.ncMzG7$ apt download getmail
0 dkg@alice:/tmp/cdtemp.ncMzG7$ dpkg --contents getmail_5.5-1_all.deb  | grep 
bin/get
-rwxr-xr-x root/root  1636 2017-12-17 10:17 ./usr/bin/getmails
0 dkg@alice:/tmp/cdtemp.ncMzG7$ 


somehow /usr/bin/getmail got dropped from the getmail 5.5-1 packaging :/

This makes the package not useful!

 --dkg

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), 
(200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (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)

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: getmail
Source-Version: 5.5-2

We believe that the bug you reported is fixed in the latest version of
getmail, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Osamu Aoki  (supplier of updated getmail package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 21 Dec 2017 01:32:19 +0900
Source: getmail
Binary: getmail getmail4
Architecture: source all
Version: 5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki 
Changed-By: Osamu Aoki 
Description:
 getmail- mail retriever with support for POP3, IMAP4 and SDPS
 getmail4   - transitional dummy package
Closes: 884807
Changes:
 getmail (5.5-2) unstable; urgency=medium
 .
   * Fix regression caused by transition package. Closes: #884807
   * Package clean-up by Daniel Kahn Gillmor.  Thanks.
   * Proper versioned Breaks.
Checksums-Sha1:
 eb3a05667e4da35ef6e540520f9af25072d00be0 1902 getmail_5.5-2.dsc
 9701a346836a7cda732330b3c7c42dfbb5c6db94 7604 getmail_5.5-2.debian.tar.xz
 1122f556278f0e4d6115ca642f5cdededb87af5e 25468 getmail4_5.5-2_all.deb
 bbbfe6c9a14aab5334f538acb81d4738067fba24 177660 getmail_5.5-2_all.deb
 15dab531c1f7126e5f8f93e08ef00486001aee9f 6402 getmail_5.5-2_amd64.buildinfo
Checksums-Sha256:
 d709084b1aaa02001548a2f608c5bd2e9e66136c5a233683af3be2427341684f 1902 
getmail_5.5-2.dsc
 4cfcd2ac85cdbace53014446691e75245a5491fa33e11e8dce7bcec6acca9f4b 7604 
getmail_5.5-2.debian.tar.xz
 1bb6042bb321eb6daff64ad3c1070967cfd7685c4bf23915e9ca88c772c89329 25468 
getmail4_5.5-2_all.deb
 02ebd9eae6b3169ba539981e1ba8ee08e720c719fd8594cc268de8e305e018e2 177660 
getmail_5.5-2_all.deb
 dd48744cd298e02c39d8d97224eba9bc2e4151f4e3f821783ec4d1287b945744 6402 
getmail_5.5-2_amd64.buildinfo
Files:
 2238fee577499d675f23ef692ae4d3a1 1902 mail optional getmail_5.5-2.dsc
 82186c13d355326ee27b3f6f7d4746ed 7604 mail optional getmail_5.5-2.debian.tar.xz
 16be085a80b0d6bbfec21d7d0d34afb5 25468 mail optional getmail4_5.5-2_all.deb
 b992b144c26c6cb7a40b43eaf2db3e9b 177660 mail optional getmail_5.5-2_all.deb
 1a7623b0e5a079d9cd4e5445edc89fbb 6402 mail optional 
getmail_5.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEMTNyTWIHiBV56V1iHhNWiB3Y15EFAlo6ijkACgkQHhNWiB3Y
15FRXQ/+MxC4cyHQQWAoLkMJtX2S9zQQUyFTGsDMYZGEz9iuvovp2u7M8/gZBnFy
J7ZZ+phDdGi7Qo+vMenYl60eBTgzfQ/ZWMxweo4AbIaKHe4A4PaNP7YANzjV9kl3
jRHvMnrYmYLXRSVcLIbZ1qMm+aoCwiphAkLrJDVMkogeN0fDpjASyiTdnWNT7FBX
QXXS0Xhg//47SA6DOm4AL8t0kXM5PC+CIjSBg6sKN8xuR8IFe5qUvcqxzIMz7Qnx
9buJEtq/XFdE9Rln+X6Gvv/r+L3+X+f9X6x6T2+Ht4Q69HVs81af9VoY9bW7L5ic

Bug#884859: marked as done (phonon-backend-vlc: FTBFS against vlc 3.0.0~rc2)

[Debian Bug Tracking System]

Your message dated Wed, 20 Dec 2017 16:50:56 +0100
with message-id <20171220155056.ga11...@ramacher.at>
and subject line Re: Bug#884859: phonon-backend-vlc: FTBFS against vlc 3.0.0~rc2
has caused the Debian Bug report #884859,
regarding phonon-backend-vlc: FTBFS against vlc 3.0.0~rc2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
884859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phonon-backend-vlc
Version: 0.9.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid buster

phonon-backend-vlc failed to build while rebuilding reverse dependencies of
libvlccore:
| In file included from /<>/src/backend.cpp:45:0:
| /usr/include/vlc/plugins/vlc_common.h: At global scope:
| /<>/src/utils/libvlc.h:33:24: error: invalid use of 
qualified-name 'LibVLC::self'
|  #define libvlc LibVLC::self->vlc()

Full log is available at
https://buildd.debian.org/status/fetch.php?pkg=phonon-backend-vlc=amd64=0.9.0-2%2Bb1=1513777867=0

Please upload 0.9.1 to unstable.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.9.1-1

On 2017-12-20 16:40:44, Sebastian Ramacher wrote:
> Source: phonon-backend-vlc
> Version: 0.9.0-2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> Tags: sid buster
> 
> phonon-backend-vlc failed to build while rebuilding reverse dependencies of
> libvlccore:
> | In file included from /<>/src/backend.cpp:45:0:
> | /usr/include/vlc/plugins/vlc_common.h: At global scope:
> | /<>/src/utils/libvlc.h:33:24: error: invalid use of 
> qualified-name 'LibVLC::self'
> |  #define libvlc LibVLC::self->vlc()
> 
> Full log is available at
> https://buildd.debian.org/status/fetch.php?pkg=phonon-backend-vlc=amd64=0.9.0-2%2Bb1=1513777867=0
> 
> Please upload 0.9.1 to unstable.

Marking as fixed in 0.9.1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#884807: getmail: does not ship /usr/bin/getmail

[Osamu Aoki]

On Tue, Dec 19, 2017 at 06:36:15PM -0500, Daniel Kahn Gillmor wrote:
> On Tue 2017-12-19 16:47:01 -0500, Daniel Kahn Gillmor wrote:
> > somehow /usr/bin/getmail got dropped from the getmail 5.5-1 packaging :/
> 
> I've pushed some changes to the master branch of
> https://anonscm.debian.org/git/collab-maint/getmail.git that resolve
> this matter for me.
> 
> they also do a little bit of packaging cleanup.  I hope they're useful!

Thanks. I realized your change just before upload.  Good.
Yes this cleans my rough edges.

I had some changes locally with a bit different style too ;-) I have
debian/rules with:

  # Always use debian/getmail as destination (not debian/tmp)
  # even when dummy getmail4 package exists
  override_dh_auto_install:
  dh_auto_install --destdir debian/getmail

So when we drop getmail4 transition package, migration needs only
dropping it in the debian/control field.

So I made a bit more changes to simplify packaging.

Osamu

Bug#884859: phonon-backend-vlc: FTBFS against vlc 3.0.0~rc2

[Sebastian Ramacher]

Source: phonon-backend-vlc
Version: 0.9.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid buster

phonon-backend-vlc failed to build while rebuilding reverse dependencies of
libvlccore:
| In file included from /<>/src/backend.cpp:45:0:
| /usr/include/vlc/plugins/vlc_common.h: At global scope:
| /<>/src/utils/libvlc.h:33:24: error: invalid use of 
qualified-name 'LibVLC::self'
|  #define libvlc LibVLC::self->vlc()

Full log is available at
https://buildd.debian.org/status/fetch.php?pkg=phonon-backend-vlc=amd64=0.9.0-2%2Bb1=1513777867=0

Please upload 0.9.1 to unstable.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#884815: marked as done (jenkins-job-builder: debian/rules clean does not run dh_clean)

[Debian Bug Tracking System]

Your message dated Wed, 20 Dec 2017 15:09:53 +
with message-id 
and subject line Bug#884815: fixed in jenkins-job-builder 2.0.0~b2-2
has caused the Debian Bug report #884815,
regarding jenkins-job-builder: debian/rules clean does not run dh_clean
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
884815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jenkins-job-builder
Version: 2.0.0~b2-1
Severity: serious
Justification: Policy 4.9

Hi,

from the attached pbuilder --twice buildlog after the first build has
finished:

 dpkg-source --before-build jenkins-job-builder-2.0.0~b2
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from 
jenkins-job-builder-2.0.0~b2/debian/source/options: 
--extend-diff-ignore=^[^/]*[.]egg-info/
 fakeroot debian/rules clean
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh clean --with python2,python3,sphinxdoc
   dh_auto_clean
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py clean -a
running clean
removing 'build/lib.linux-x86_64-2.7' (and everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-2.7' does not exist -- can't clean it
find . -name \*.pyc -exec rm {} \+
   debian/rules override_dh_clean
make[1]: Entering directory '/build/jenkins-job-builder-2.0.0~b2'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
rm -rf doc/build build .testrepository
make[1]: Leaving directory '/build/jenkins-job-builder-2.0.0~b2'
 dpkg-source -b jenkins-job-builder-2.0.0~b2
dpkg-source: info: using options from 
jenkins-job-builder-2.0.0~b2/debian/source/options: 
--extend-diff-ignore=^[^/]*[.]egg-info/
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: error: unwanted binary file: 
debian/python3-jenkins-job-builder/usr/share/doc/python3-jenkins-job-builder/changelog.Debian.gz
dpkg-source: error: unwanted binary file: 
debian/python-jenkins-job-builder/usr/share/doc/python-jenkins-job-builder/changelog.Debian.gz
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/changelog.Debian.gz
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/objects.inv
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/ajax-loader.gif
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/comment-bright.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/comment-close.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/comment.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/down-pressed.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/down.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/file.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/minus.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/plus.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/up-pressed.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder-doc/usr/share/doc/jenkins-job-builder-doc/html/_static/up.png
dpkg-source: error: unwanted binary file: 
debian/jenkins-job-builder/usr/share/doc/jenkins-job-builder/changelog.Debian.gz
dpkg-source: error: detected 16 unwanted binary files (add them in 

Bug#884846: xserver-xorg-video-radeon: xrandr hang on resolution setup after xorg has been started

[Michel Dänzer]

On 2017-12-20 12:17 PM, Angelo Dureghello wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:7.8.0-1+b1
> Severity: grave
> Justification: renders package unusable

"renders the package unusable" in this context means the package cannot
be used for its intended purpose at all by anyone, which isn't the case.


> Dear Maintainer,
> 
> In xserver-xorg-video-radeon v.1.7.10.0-1 i am observing the following issue:
> 
> after xorg has been started, and openbox-session is called, xrandr seems to
> hang leaving interface with mouse pointer only, but not usable.
> 
> The line causing the issue is :
> (sleep 1s && xrandr --output VGA-0 --off --output DVI-0 --primary --mode
> 2560x1440 --output HDMI-0 --mode 1920x1080 --right-of DVI-0) &

When it hangs, can you attach gdb to the Xorg process and get a
backtrace? See
https://www.x.org/wiki/Development/Documentation/ServerDebugging/ for
detailed information about how this can be done. Make sure the
xserver-xorg-core-dbgsym and xserver-xorg-video-radeon-dbg packages are
installed.


> If i roll back to v.1.7.8.0.1+b1 version all works fine as usual and expected.

Can you use git bisect to determine which change introduced the problem?


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#884799: [Pkg-xfce-devel] Bug#884799: thunar: Shredding a file causes Thunar to block permanently. (USB)

[Yves-Alexis Perez]

control: severity -1 important
control: tag -1 unreproducible moreinfo

On Tue, 2017-12-19 at 20:58 +0100, Lorenzo Ancora wrote:
> Dear Maintainer,
> shredding a file in a mounted USB key causes `Thunar 1.6.11 (Xfce 4.12)` to
> block permanently.
> The window with the key won't close and Thunar must be killed manually; it can
> be restarted (must wait 2 minutes on a Intel Core i5) but is very slow and you
> can just eject the USB device. After ejecting the USB device the problem does
> not disappear and gets even worse.
> Logging out causes `lightdm 1.18.3` to restart... and it keeps restarting
> forever, in a loop.
> From `lightdm` it becames impossible to reboot, shutdown etc. and it must be
> done from a VT.
> Activating the rescue mode (single user mode) from `systemctl` and going back
> does not fix the problem.
> Apparently the only way to fix the problem is to stop lightdm.service and
> reboot the system.

Hi,

I'm sorry to hear that, but I don't think I can reproduce that (also it's
unclear what “shredding” exactly means here). Also it's quite likely that you
actually removed the USB key while the thunar process was still having open fd
on the usb key, which is definitely the wrong thing to do.

Regards,
-- 
Yves-Alexis

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

Processed: Re: [Pkg-xfce-devel] Bug#884799: thunar: Shredding a file causes Thunar to block permanently. (USB)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #884799 [thunar] thunar: Shredding a file causes Thunar to block 
permanently. (USB)
Severity set to 'important' from 'critical'
> tag -1 unreproducible moreinfo
Bug #884799 [thunar] thunar: Shredding a file causes Thunar to block 
permanently. (USB)
Added tag(s) moreinfo and unreproducible.

-- 
884799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#884216: libxfce4ui: FTBFS: dh_install: libxfce4ui-common missing files: usr/share/gtk-doc/*

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #884216 [src:libxfce4ui] libxfce4ui: FTBFS twice in a row
Severity set to 'important' from 'serious'

-- 
884216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884216: libxfce4ui: FTBFS: dh_install: libxfce4ui-common missing files: usr/share/gtk-doc/*

[Yves-Alexis Perez]

control: severity -1 important

On Tue, 2017-12-19 at 23:42 +0100, Andreas Beckmann wrote:
> > I just tried a build (in pbuilder/amd64) and it worked just fine. Can you
> > be
> > more specific about your test? Is it an arch-indep build for example?
> 
> This was a regular (arch+indep) build with pbuilder --twice (but the log
> was not labeled accordingly at that time) and only the second build failed.

Ah ok, thanks for the precision (and I didn't know about --twice, thanks for
that). I'm lowering the severity accordingly.
> 
> I just filed a similar bug with more analysis as #884813 against
> xfce-panel, it's probably the same underlying problem here, too.

Ok, thanks. I'll take a look when I can.

Regards,
-- 
Yves-Alexis

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

Processed: severity of 884813 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 884813 important
Bug #884813 [src:xfce4-panel] xfce4-panel: make distclean deletes 
docs/references/html/, which is not regenerated
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 884819 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 884819 important
Bug #884819 [src:parole] parole: make distclean deletes data/interfaces/*.h, 
which are not regenerated
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#875688: marked as done (report builder inactive; only legacy reports can be created and run)

[Debian Bug Tracking System]

Your message dated Wed, 20 Dec 2017 13:21:58 +
with message-id 
and subject line Bug#875688: fixed in libreoffice 1:5.4.4-1
has caused the Debian Bug report #875688,
regarding report builder inactive; only legacy reports can be created and run
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
875688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-report-builder
Version: 1:5.4.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

libreoffice-report-builder will not run in base. Critical reports built using
this tool cannot now be run. This occurred after the most recent upgrade to the
debian testing branch.

I tried reconfiguring the extension in dpkg. I also tried downloading the
extension for report builder available from open office - which had a java
incompatibility issue. I checked advanced tab options, and the oracle report
builder is listed there. I'm currently seeking a work around, but libreoffice
base is rendered useless for our purposes without those painstakingly
constructed reports.



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

Kernel: Linux 4.12.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 libreoffice-report-builder depends on:
ii  libbase-java   1.1.6-2
ii  libcommons-logging-java1.2-1
ii  libflute-java  1:1.1.6-3
ii  libfonts-java  1.1.6.dfsg-3
ii  libformula-java1.1.7.dfsg-2
ii  liblayout-java 0.2.10-2
ii  libloader-java 1.1.6.dfsg-4
ii  libpentaho-reporting-flow-engine-java  0.9.4-4
ii  libreoffice-common 1:5.4.1-1
ii  libreoffice-core   1:5.4.1-1
ii  libreoffice-java-common1:5.4.1-1
ii  libreoffice-report-builder-bin 1:5.4.1-1
ii  librepository-java 1.1.6-3
ii  libsac-java1.3+dfsg-2
ii  libserializer-java 1.1.6-4
ii  libxml-java1.1.6.dfsg-3

libreoffice-report-builder recommends no packages.

libreoffice-report-builder suggests no packages.

Versions of packages libreoffice-base depends on:
ii  libc6 2.24-17
ii  libgcc1   1:7.2.0-4
ii  libreoffice-base-core 1:5.4.1-1
ii  libreoffice-base-drivers  1:5.4.1-1
ii  libreoffice-core  1:5.4.1-1
ii  libstdc++67.2.0-4
ii  uno-libs3 5.4.1-1
ii  ure   5.4.1-1

Versions of packages libreoffice-base recommends:
ii  default-jre [java6-runtime]   2:1.8-59
ii  libreoffice-java-common   1:5.4.1-1
ii  libreoffice-writer1:5.4.1-1
ii  openjdk-7-jre [java6-runtime] 7u151-2.6.11-1
ii  openjdk-8-jre [java6-runtime] 8u144-b01-1
ii  oracle-java8-jdk [java6-runtime]  8u65

Versions of packages libreoffice-base suggests:
pn  unixodbc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:5.4.4-1

We believe that the bug you reported is fixed in the latest version of
libreoffice, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 15 Dec 2017 00:29:20 +0100
Source: libreoffice
Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core 
libreoffice-common libreoffice-java-common libreoffice-writer libreoffice-calc 
libreoffice-impress libreoffice-draw libreoffice-math libreoffice-base-core 

Bug#884850: librsvg: FTBFS on (32-bit && !any-i386): masking-mask-01-b.svg: 661 pixels differ (with maximum difference of 2) from reference image

[Simon McVittie]

Source: librsvg
Version: 2.40.20-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

librsvg fails the same test in the same way on all the 32-bit
architectures, except for (hurd-)i386 which have a different test
failure, m68k and powerpcspe which (IMO unwisely) build with nocheck,
and kfreebsd-i386 which hasn't been attempted yet. This seems too
well-correlated to be coincidence.

https://buildd.debian.org/status/fetch.php?pkg=librsvg=armel=2.40.20-1=1513733747=0
https://buildd.debian.org/status/fetch.php?pkg=librsvg=armhf=2.40.20-1=1513733897=0
https://buildd.debian.org/status/fetch.php?pkg=librsvg=mips=2.40.20-1=1513733801=0
https://buildd.debian.org/status/fetch.php?pkg=librsvg=mipsel=2.40.20-1=1513734074=0
https://buildd.debian.org/status/fetch.php?pkg=librsvg=hppa=2.40.20-1=1513745188=0
https://buildd.debian.org/status/fetch.php?pkg=librsvg=powerpc=2.40.20-1=1513733546=0
https://buildd.debian.org/status/fetch.php?pkg=librsvg=x32=2.40.20-1=1513734144=0
> # Storing test result image at /tmp/masking-mask-01-b-out.png
> # 661 pixels differ (with maximum difference of 2) from reference image
>
> # Storing test result image at /tmp/masking-mask-01-b-diff.png
> not ok 16 /rsvg/reftest/svg1.1/masking-mask-01-b.svg
> FAIL: rsvg-test 16 /rsvg/reftest/svg1.1/masking-mask-01-b.svg

i386 and hurd-i386 had a different test failure for which I've opened a
separate bug (wild guess: maybe it's to do with excess precision in the
387-compatible FPU, which is an i386 quirk).

Regards,
smcv

Bug#884849: librsvg: FTBFS on any-i386: masking-path-04-b.svg: 213 pixels differ (with maximum difference of 19) from reference image

[Simon McVittie]

Source: librsvg
Version: 2.40.20-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=librsvg=i386=2.40.20-1=1513733588=0
https://buildd.debian.org/status/fetch.php?pkg=librsvg=hurd-i386=2.40.20-1=1513734324=0
> # Storing test result image at /tmp/masking-path-04-b-out.png
> # 213 pixels differ (with maximum difference of 19) from reference image
> 
> # Storing test result image at /tmp/masking-path-04-b-diff.png
> not ok 22 /rsvg/reftest/svg1.1/masking-path-04-b.svg
> FAIL: rsvg-test 22 /rsvg/reftest/svg1.1/masking-path-04-b.svg

Various other architectures have a different test failure which I'll
file separately.

Regards,
smcv

Processed: fixed 884801 in 3.3.18-1+deb8u4, fixed 884801 in 5.0.16-1+deb9u5

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 884801 3.3.18-1+deb8u4
Bug #884801 {Done: Patrick Matthäi } [src:otrs2] otrs2: 
CVE-2017-17476: OSA-2017-10: Session hijacking
The source 'otrs2' and version '3.3.18-1+deb8u4' do not appear to match any 
binary packages
Marked as fixed in versions otrs2/3.3.18-1+deb8u4.
> fixed 884801 5.0.16-1+deb9u5
Bug #884801 {Done: Patrick Matthäi } [src:otrs2] otrs2: 
CVE-2017-17476: OSA-2017-10: Session hijacking
The source 'otrs2' and version '5.0.16-1+deb9u5' do not appear to match any 
binary packages
Marked as fixed in versions otrs2/5.0.16-1+deb9u5.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884846: xserver-xorg-video-radeon: xrandr hang on resolution setup after xorg has been started

[Angelo Dureghello]

Package: xserver-xorg-video-radeon
Version: 1:7.8.0-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

In xserver-xorg-video-radeon v.1.7.10.0-1 i am observing the following issue:

after xorg has been started, and openbox-session is called, xrandr seems to
hang leaving interface with mouse pointer only, but not usable.

The line causing the issue is :
(sleep 1s && xrandr --output VGA-0 --off --output DVI-0 --primary --mode
2560x1440 --output HDMI-0 --mode 1920x1080 --right-of DVI-0) &

If i roll back to v.1.7.8.0.1+b1 version all works fine as usual and expected.

Issue raised after the dist-upgrate at today.

Some other info:
HW: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Turks XT [Radeon HD 6670/7670]

╰─○ cat /proc/version
Linux version 4.13.3 (root@jerusalem) (gcc version 5.4.1 20170820
(Debian/Linaro 5.4.1-12)) #1 SMP Mon Sep 25 12:14:26 CEST 2017

xorg 1:7.7+19
openbox 3.6.1-5










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

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758]

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

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 817 Jan  5  2017 40-monitor.conf

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.13.3 (root@jerusalem) (gcc version 5.4.1 20170820 
(Debian/Linaro 5.4.1-12)) #1 SMP Mon Sep 25 12:14:26 CEST 2017

Xorg X server log files on system:
--
-rw-r--r-- 1 root   angelo 57026 Dec 17  2015 /var/log/Xorg.0.log
-rw-r--r-- 1 angelo angelo 40565 Aug 13 11:27 
/home/angelo/.local/share/xorg/Xorg.3.log
-rw-r--r-- 1 angelo angelo 46005 Aug 13 11:28 
/home/angelo/.local/share/xorg/Xorg.4.log
-rw-r--r-- 1 angelo angelo 41273 Aug 14 01:52 
/home/angelo/.local/share/xorg/Xorg.5.log
-rw-r--r-- 1 angelo angelo 62645 Sep 25 09:33 
/home/angelo/.local/share/xorg/Xorg.1.log
-rw-r--r-- 1 angelo angelo 66955 Sep 25 09:39 
/home/angelo/.local/share/xorg/Xorg.2.log
-rw-r--r-- 1 angelo angelo 41376 Dec 20 11:50 
/home/angelo/.local/share/xorg/Xorg.0.log

Contents of most recent Xorg X server log file 
(/home/angelo/.local/share/xorg/Xorg.0.log):
---
[   101.401] 
X.Org X Server 1.19.5
Release Date: 2017-10-12
[   101.402] X Protocol Version 11, Revision 0
[   101.402] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[   101.402] Current Operating System: Linux jerusalem 4.13.3 #1 SMP Mon Sep 25 
12:14:26 CEST 2017 x86_64
[   101.402] Kernel command line: BOOT_IMAGE=/vmlinuz-4.13.3 
root=/dev/mapper/jerusalem--vg-root ro quiet
[   101.403] Build Date: 16 October 2017  12:28:38PM
[   101.404] xorg-server 2:1.19.5-1 (https://www.debian.org/support) 
[   101.404] Current version of pixman: 0.34.0
[   101.405]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   101.405] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   101.407] (==) Log file: "/home/angelo/.local/share/xorg/Xorg.0.log", Time: 
Wed Dec 20 11:50:25 2017
[   101.408] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   101.408] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   101.409] (==) No Layout section.  Using the first Screen section.
[   101.409] (==) No screen section available. Using defaults.
[   101.409] (**) |-->Screen "Default Screen Section" (0)
[   101.409] (**) |   |-->Monitor ""
[   101.409] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[   101.409] (**) |   |-->Device "Radeon Turks"
[   101.409] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   101.409] (==) Automatically adding devices
[   101.409] (==) Automatically enabling devices
[   101.409] (==) Automatically adding GPU devices
[   101.409] (==) Max clients allowed: 256, resource mask: 0x1f
[   101.409] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   101.409]Entry deleted from font path.
[   101.409] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   101.409] (==) ModulePath set to "/usr/lib/xorg/modules"
[   101.409] (II) The server relies on udev to provide the list of input 
devices.
   

Bug#878216: Info received (Regression in linux in jessie-proposed-updates)

[vincent.ta...@amen.fr]

Hi Julien,

Do you now need more information to check the regression problem ?

Just for information kernel version: 3.16.0-4-amd64 #1 SMP Debian 
3.16.51-3 (2017-12-13) have the same problem.


Best regards
Vince

Bug#884801: marked as done (otrs2: CVE-2017-17476: OSA-2017-10: Session hijacking)

[Debian Bug Tracking System]

Your message dated Wed, 20 Dec 2017 09:20:26 +
with message-id 
and subject line Bug#884801: fixed in otrs2 6.0.3-1
has caused the Debian Bug report #884801,
regarding otrs2: CVE-2017-17476: OSA-2017-10: Session hijacking
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
884801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: otrs2
Version: 3.3.9-3
Severity: grave
Tags: patch security upstream

Hi

From 
https://www.otrs.com/security-advisory-2017-10-security-update-otrs-framework/

> An attacker can send a specially prepared email to an OTRS system. If
> this system has cookie support disabled, and a logged in agent clicks a
> link in this email, the session information could be leaked to external
> systems, allowing the attacker to take over the agent’s session.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: otrs2
Source-Version: 6.0.3-1

We believe that the bug you reported is fixed in the latest version of
otrs2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated otrs2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Dec 2017 09:25:55 +0100
Source: otrs2
Binary: otrs2 otrs
Architecture: source all
Version: 6.0.3-1
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 otrs   - Open Ticket Request System (OTRS 6)
 otrs2  - Open Ticket Request System
Closes: 884801
Changes:
 otrs2 (6.0.3-1) unstable; urgency=high
 .
   * New upstream release.
 - This fixes OSA-2017-10, also known as CVE-2017-17476: A session hijacking
   vulnerability.
   Closes: #884801
   * Merge 3.3.18-1+deb8u3, 3.3.18-1+deb8u4, 5.0.16-1+deb9u4 and 5.0.16-1+deb9u5
 changelog.
   * Bump Standards-Version to 4.1.2 (no changes required).
Checksums-Sha1:
 a1677d560237c175d4c30ef0c8ea5e17a3f83a5c 1789 otrs2_6.0.3-1.dsc
 75f10e8e42bc6e3e077a05d53fd8c07e879d0475 24314514 otrs2_6.0.3.orig.tar.bz2
 ca313c316b79392907e377660f43d77cf07a7cd2 28244 otrs2_6.0.3-1.debian.tar.xz
 0dc2801df2e3e82d32ba1adaca420465a1d5b70f 9504500 otrs2_6.0.3-1_all.deb
 e301e6fa41ddebdf2d0d62b94b4716a4d8c46edc 6077 otrs2_6.0.3-1_amd64.buildinfo
 e5a4842f79ead6b413df00bf764ad78fe9af2189 233812 otrs_6.0.3-1_all.deb
Checksums-Sha256:
 09648e0670f56e369ba99be8a7c3a9763eff618651a6b2eaa0ecbeb389ee860c 1789 
otrs2_6.0.3-1.dsc
 de4ee3e0aa1e4501551fc7af4a45cdd2686e5be1a61a9ecf601aa1b61e821cfb 24314514 
otrs2_6.0.3.orig.tar.bz2
 70b53e902126ff7c859e318105f8c116a47143be20ccaace62e801ba6011635e 28244 
otrs2_6.0.3-1.debian.tar.xz
 ee40f0a94722d1da713e01cc8e01e5e865500f37dbc5e78f434abb894c68380a 9504500 
otrs2_6.0.3-1_all.deb
 000cc127322695229918472ae63ceace251057e70463ad0ca1e2ca083d43fd2f 6077 
otrs2_6.0.3-1_amd64.buildinfo
 6131539d671557cae0a525200c6e9b9354669142e86f767597910f562472142a 233812 
otrs_6.0.3-1_all.deb
Files:
 3d906962101dc97e69089888de9deb41 1789 non-free/web optional otrs2_6.0.3-1.dsc
 32961cd15798e713ed65fc371789772c 24314514 non-free/web optional 
otrs2_6.0.3.orig.tar.bz2
 ad8e34382a18a50832972b28b073cec5 28244 non-free/web optional 
otrs2_6.0.3-1.debian.tar.xz
 ba0e073a4e53dcf03fe7edec6099a5c7 9504500 non-free/web optional 
otrs2_6.0.3-1_all.deb
 25298da8398360a259d01fe843bde397 6077 non-free/web optional 
otrs2_6.0.3-1_amd64.buildinfo
 9c44a6198485f81c8804102986fd6edc 233812 non-free/web optional 
otrs_6.0.3-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWKA9xYJCWk3IuQ4TEtmwSpDL2OQFAlo6KKcACgkQEtmwSpDL
2OTV8RAAk8twiyhuCoqqxRa2Ld0WQ4rj3hQkyOQN3EYxgzTlb9imjT9tH8W8PGzi
Rqui28fWodiQ4L1CEmGHHl8YUJpjBDFFckf3e1s9Q6dRusIMzqP806ZJB1n4mRPw
whpk8S9mx0B4p6E+8q0CmAEUyPPqM91OAzT+O/WsYrO0Zqte0ZAcosU73EoxqyBs
D2WSXe97DAufgVF3A9Arl/Jn93ayV2CT6lDaQ9/bPGG6MfyWEDSsTJLASraw9Kla
dQadpmjPmX0FQTXvFE4aR6etG5ehVGqWzCj647hwpEXB7ZfWYkE7HBSUEOOGsGzr

Bug#851086: [Pkg-citadel-devel] Bug#851086: Bug#859789: RFH: citadel/webcit

[Michael Meskes]

> We are one bugfix away from that release.  Hoping to get it out over
> the 
> next week or so.
> 
> It will have a new version number   :)

Great! Thanks Art! I'll do an upload when it's available.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL