Bug#896192: marked as done (cloudcompare FTBFS on architectures where char is unsigned)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 08:15:29 +0100
with message-id <71d53c25888f65e4aafd9209766d6...@phys.ethz.ch>
and subject line cloudcompare FTBFS on architectures where char is unsigned
has caused the Debian Bug report #896192,
regarding cloudcompare FTBFS on architectures where char is unsigned
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.)


-- 
896192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cloudcompare
Version: 2.9.1+git20180223-1
Severity: important

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

...
cd /<>/cloudcompare-2.9.1+git20180223/obj-aarch64-linux-gnu/CC && 
/usr/bin/c++  -DCC_CORE_LIB_EXPORTS -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_DEBUG -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DUSE_QT 
-I/<>/cloudcompare-2.9.1+git20180223/obj-aarch64-linux-gnu/CC 
-I/<>/cloudcompare-2.9.1+git20180223/CC 
-I/<>/cloudcompare-2.9.1+git20180223/obj-aarch64-linux-gnu/CC/CC_CORE_LIB_autogen/include
 -isystem /usr/include/aarch64-linux-gnu/qt5 
-I/usr/include/aarch64-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/aarch64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/aarch64-linux-gnu/qt5/QtGui -isystem 
/usr/include/aarch64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/aarch64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/aarch64-linux-gnu/qt5/QtConcurrent 
-I/usr/include/aarch64-linux-gnu/qt5/QtPrintSupport 
-I/<>/cloudcompare-2.9.1+git20180223/CC/include  -g -O2 
-fdebug-prefix-map=/<>/cloudcompare-2.9.1+git20180223=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11 -fPIC -fopenmp -O3 -DNDEBUG -fPIC   -fPIC 
-std=gnu++11 -o CMakeFiles/CC_CORE_LIB.dir/src/ChamferDistanceTransform.cpp.o 
-c 
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
 };
 ^
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/cloudcompare-2.9.1+git20180223/CC/src/ChamferDistanceTransform.cpp:44:1:
 error: narrowing conversion of '-1' from 'int' to 'char' 

Bug#912627: marked as done (asymptote: Asymptote crashes on attempt to create pdf file)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 06:04:15 +
with message-id 
and subject line Bug#912627: fixed in asymptote 2.47-2
has caused the Debian Bug report #912627,
regarding asymptote: Asymptote crashes on attempt to create pdf file
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.)


-- 
912627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asymptote
Version: 2.44-1+b1
Severity: normal

Dear Maintainer, here is the code:


draw((0, 0) -- (1, 1), opacity(0.7));

Here is error:

Error: /undefined in .setopacityalpha
Operand stack:
   0.7
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   2043   1   3   %oparray_pop   
2042   1   3   %oparray_pop   --nostringval--   2023   1   3   %oparray_pop   
1884   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   
--nostringval--   --nostringval--   --nostringval--   2   %stopped_push   
--nostringval--
Dictionary stack:
   --dict:970/1684(ro)(G)--   --dict:0/20(G)--   --dict:82/200(L)--
Current allocation mode is local
Current file position is 247
GPL Ghostscript 9.25: Unrecoverable error, exit code 1
/usr/share/asymptote/plain_shipout.asy: 87.10: runtime: shipout failed

I believe I compiled this code with 2.42 fine.


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=eo.utf8, LC_CTYPE=eo.utf8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE=eo.utf8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages asymptote depends on:
ii  freeglut32.8.1-3
ii  ghostscript  9.25~dfsg-4
ii  imagemagick  8:6.9.10.14+dfsg-4
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.14+dfsg-4
ii  install-info 6.5.0.dfsg.1-4
ii  libc62.27-8
ii  libfftw3-double3 3.3.8-2
ii  libgc1c2 1:7.6.4-0.4
ii  libgcc1  1:8.2.0-9
ii  libglu1-mesa [libglu1]   9.0.0-2.1
ii  libgsl23 2.5+dfsg-5
ii  libgslcblas0 2.5+dfsg-5
ii  libosmesa6   18.1.9-1
ii  libreadline7 7.0-5
ii  libsigsegv2  2.12-2
ii  libstdc++6   8.2.0-9
ii  libtinfo66.1+20181013-1
ii  python3  3.6.7-1
ii  python3-pil  5.3.0-1
ii  python3-pil.imagetk  5.3.0-1
ii  tex-common   6.10
ii  texlive-binaries 2018.20180907.48586-2
ii  texlive-latex-base   2018.20181009-1
ii  texlive-plain-generic2018.20181009-1
ii  texlive-pstricks 2018.20181009-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages asymptote recommends:
ii  asymptote-doc  2.44-1

Versions of packages asymptote suggests:
pn  gv
ii  zathura-pdf-poppler [pdf-viewer]  0.2.9-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: asymptote
Source-Version: 2.47-2

We believe that the bug you reported is fixed in the latest version of
asymptote, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated asymptote 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: Mon, 28 Jan 2019 13:58:38 +0900
Source: asymptote
Binary: asymptote asymptote-dbgsym asymptote-doc
Architecture: source amd64 all
Version: 2.47-2

Bug#635619: marked as done (ipe: Segfaults on JPG import)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:51:10 -0600
with message-id <21525102.7Na66R36Bd@riemann>
and subject line Re: ipe: Segfaults on JPG import
has caused the Debian Bug report #635619,
regarding ipe: Segfaults on JPG import
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.)


-- 
635619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ipe
Version: 7.0.14-1
Severity: normal
Tags: upstream

When selecting Ipelets -> Insert Image -> Insert JPEG image with the attached
image, ipe crashes. gdb says only:

Program received signal SIGSEGV, Segmentation fault.
0x7751b8ab in DCTStream::readHuffSym(DCTHuffTable*) ()
   from /usr/lib/libipe.so.7.0.14
(gdb) bt
#0  0x7751b8ab in DCTStream::readHuffSym(DCTHuffTable*) ()
   from /usr/lib/libipe.so.7.0.14
#1  0xfffe0004 in ?? ()


The image was created with Gimp.



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

Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ipe depends on:
ii  gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 Fonts for the Ghostscript interpre
ii  libc6   2.13-10  Embedded GNU C Library: Shared lib
ii  libcairo2   1.10.2-6 The Cairo 2D vector graphics libra
ii  libgcc1 1:4.6.1-4GCC support library
ii  libipe7.0.1 7.0.14-1 Ipe library used by ipelets
ii  liblua5.1-0 5.1.4-5  Simple, extensible, embeddable pro
ii  libqtcore4  4:4.7.3-5Qt 4 core module
ii  libqtgui4   4:4.7.3-5Qt 4 GUI module
ii  libstdc++6  4.6.1-4  GNU Standard C++ Library v3
ii  texlive-lat 2009-11  TeX Live: Basic LaTeX packages

Versions of packages ipe recommends:
ii  lua5.15.1.4-5Simple, extensible, embeddable pro

Versions of packages ipe suggests:
ii  texlive-latex-recommended 2009-11TeX Live: LaTeX recommended packag

-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,

On Wednesday, July 27, 2011 12:06:11 PM CST Nikolaus Rath wrote:
> Package: ipe
> Version: 7.0.14-1
> Severity: normal
> Tags: upstream
> 
> When selecting Ipelets -> Insert Image -> Insert JPEG image with the
> attached image, ipe crashes. gdb says only:
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x7751b8ab in DCTStream::readHuffSym(DCTHuffTable*) ()
>from /usr/lib/libipe.so.7.0.14
> (gdb) bt
> #0  0x7751b8ab in DCTStream::readHuffSym(DCTHuffTable*) ()
>from /usr/lib/libipe.so.7.0.14
> #1  0xfffe0004 in ?? ()

I have just tested on current Ipe 7.2.7-3.  The "import jpeg" functionality is 
no longer an Ipelet, but is an item on the "File" menu.  I tested with your 
perturbed-plasma.jpg and it now imports just fine.

Closing this bug.

-Steve--- End Message ---


Bug#728479: marked as done (ipe: buffer overflow! I cannot complete snapping examples 2, 3, and 6)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:41:34 -0600
with message-id <5283578.GYRp15vA60@riemann>
and subject line Re: ipe: buffer overflow! I cannot complete snapping examples 
2, 3, and 6
has caused the Debian Bug report #728479,
regarding ipe: buffer overflow! I cannot complete snapping examples 2, 3, and 6
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.)


-- 
728479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ipe
Version: 7.1.3-1
Severity: important

Hello and thanks for maintaining this fantastic vector drawing editor!

While studying its manual, I encountered an issue that seems to be
related to angular snapping.
I cannot complete the following snapping examples: 2, 3, and 6.
These three examples all involve angular snapping in modes other than
the default 45 degrees mode (I am not sure this is the key element
to trigger the issue, but it could be...).
As you sure know, these examples are described in
/usr/share/ipe/7.1.3/doc/manual_26.html

While attempting to follow the instructions of any of the above
mentioned examples, I cannot complete the exercise, since
ipe aborts, as soon as a buffer overflow is detected.

For instance, while doing example 3, I can follow the istructions up
to hitting [F1]. Then, as soon as I move the mouse a little, ipe aborts
and writes the following backtrace:

*** buffer overflow detected ***: ipe terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f56beb38dc7]
/lib/x86_64-linux-gnu/libc.so.6(+0xfbd80)[0x7f56beb37d80]
/lib/x86_64-linux-gnu/libc.so.6(+0xfb209)[0x7f56beb37209]
/lib/x86_64-linux-gnu/libc.so.6(__printf_fp+0x1ce3)[0x7f56bea89f63]
/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x1136)[0x7f56bea83b26]
/lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x97)[0x7f56beb372a7]
/lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x7f56beb371ed]
ipe[0x411f61]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0xbf5)[0x7f56c0230eb5]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c)[0x7f56c01e175c]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3ad)[0x7f56c01e7f0d]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d)[0x7f56bfcb233d]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x153)[0x7f56c01e76c3]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x24041b)[0x7f56c025941b]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0x5fc)[0x7f56c0257e8c]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x2667e2)[0x7f56c027f7e2]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x146)[0x7f56bdc71ea6]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x481f8)[0x7f56bdc721f8]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f56bdc7229c]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x86)[0x7f56bfcdf4d6]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x266896)[0x7f56c027f896]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f)[0x7f56bfcb0f9f]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175)[0x7f56bfcb1295]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x8b)[0x7f56bfcb68db]
ipe[0x40fd29]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xbf88)[0x7f56c0ccff88]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0x166cf)[0x7f56c0cda6cf]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xc3cd)[0x7f56c0cd03cd]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(lua_call+0x25)[0x7f56c0ccc295]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0x1ffcc)[0x7f56c0ce3fcc]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xbf88)[0x7f56c0ccff88]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0x166cf)[0x7f56c0cda6cf]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xc3cd)[0x7f56c0cd03cd]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xb6bb)[0x7f56c0ccf6bb]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xc55a)[0x7f56c0cd055a]
/usr/lib/x86_64-linux-gnu/liblua5.1.so.0(lua_pcall+0x4d)[0x7f56c0ccc31d]
ipe[0x40fb49]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f56bea5d995]
ipe[0x40fc39]
=== Memory map: 
0040-0042b000 r-xp  fe:04 64861  
/usr/bin/ipe
0062a000-0062b000 r--p 0002a000 fe:04 64861 

Bug#808957: marked as done (/usr/bin/ipetoipe: ipetoipe does not export in the EPS format any more)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:43:30 -0600
with message-id <2588569.XG2dRNVXPi@riemann>
and subject line Re: Bug#808957: /usr/bin/ipetoipe: ipetoipe does not export in 
the EPS format any more
has caused the Debian Bug report #808957,
regarding /usr/bin/ipetoipe: ipetoipe does not export in the EPS format any more
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.)


-- 
808957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ipe
Version: 7.1.10-1
Severity: important
File: /usr/bin/ipetoipe

Dear Maintainer,

Previous versions of the ipetoipe tool were able to export ipe files to EPS
format. It was very useful for preparation of LaTeX documents, where
vector graphics in the ".ipe" source format could be automatically
converted into ".eps" format handled by the graphics package in LaTeX.
It seems, that current version of ipetoipe supports only the XML .ipe format
and the .pdf format.

With best regards,
Wojtek

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

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

Versions of packages ipe depends on:
ii  gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2
ii  libc6   2.21-4
ii  libcairo2   1.14.4-1
ii  libgcc1 1:5.3.1-3
ii  libipe7.1.107.1.10-1
ii  liblua5.2-0 5.2.4-1
ii  libqt5core5a5.5.1+dfsg-8
ii  libqt5gui5  5.5.1+dfsg-8
ii  libqt5widgets5  5.5.1+dfsg-8
ii  libstdc++6  5.3.1-3
ii  texlive-latex-base  2015.20151116-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages ipe recommends:
ii  lua5.2  5.2.4-1

Versions of packages ipe suggests:
ii  texlive-latex-recommended  2015.20151116-1

-- no debconf information
--- End Message ---
--- Begin Message ---
On Thursday, December 24, 2015 4:45:40 PM CST Wojciech Zabołotny wrote:
> On 24.12.2015 23:02, David Bremner wrote:
> > "Wojciech M. Zabolotny"  writes:
> >> Previous versions of the ipetoipe tool were able to export ipe files to
> >> EPS
> >> format. It was very useful for preparation of LaTeX documents, where
> >> vector graphics in the ".ipe" source format could be automatically
> >> converted into ".eps" format handled by the graphics package in LaTeX.
> >> It seems, that current version of ipetoipe supports only the XML .ipe
> >> format and the .pdf format.
> > 
> > According to the release announcement [1] iperender should now be used
> > to export eps files.
> > 
> > Since the debian package includes iperender, perhaps this bug can be
> > closed? Or maybe a NEWS.Debian item would be appropriate.
> > 
> > d
> 
> Yes, of course. I've noticed it shortly after filling the bug report :-(.
> Please close the bug.

Closing bug as requested.
-Steve--- End Message ---


Bug#920597: marked as done (docker.io: Unable to start daemon: "containerd" executable file not found in PATH)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 03:20:43 +
with message-id 
and subject line Bug#920597: fixed in docker.io 18.09.1+dfsg1-4
has caused the Debian Bug report #920597,
regarding docker.io: Unable to start daemon: "containerd" executable file not 
found in PATH
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.)


-- 
920597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 18.09.1+dfsg1-2
Severity: serious
X-Debbugs-CC: arnaud.rebill...@collabora.com

Docker daemon is unable to start:


Failed to start containerd: exec: "containerd": executable file not found in 
$PATH



signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: docker.io
Source-Version: 18.09.1+dfsg1-4

We believe that the bug you reported is fixed in the latest version of
docker.io, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated docker.io 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: Mon, 28 Jan 2019 10:16:28 +1100
Source: docker.io
Binary: docker-doc docker.io docker.io-dbgsym golang-docker-dev 
golang-github-docker-docker-dev vim-syntax-docker
Architecture: source all amd64
Version: 18.09.1+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 docker-doc - Linux container runtime -- documentation
 docker.io  - Linux container runtime
 golang-docker-dev - Transitional package for golang-github-docker-docker-dev
 golang-github-docker-docker-dev - reusable Go packages included with Docker
 vim-syntax-docker - Docker container engine - Vim highlighting syntax files
Closes: 920597
Changes:
 docker.io (18.09.1+dfsg1-4) unstable; urgency=medium
 .
   * Updated "containerd" executable name patch;
 renamed "containerd-shim" executable (Closes: #920597).
Checksums-Sha1:
 8a07c196d37ef4eb2a0bb3de718b9370aab45806 8933 docker.io_18.09.1+dfsg1-4.dsc
 0583888c8cc1c2cc039067e2ce8063013265b9dc 40788 
docker.io_18.09.1+dfsg1-4.debian.tar.xz
 b2ac09e69ba0350a69b3e42d39a8fae76f637743 974668 
docker-doc_18.09.1+dfsg1-4_all.deb
 ae16e244d457d00fe4743542ea6941ec3690cb20 7012584 
docker.io-dbgsym_18.09.1+dfsg1-4_amd64.deb
 aa732281def2092c8dc692f771d1c5b3151a36cb 25559 
docker.io_18.09.1+dfsg1-4_amd64.buildinfo
 358cc779624ef96b7e26facf867bb5b73e263233 53137976 
docker.io_18.09.1+dfsg1-4_amd64.deb
 e19f34cc5ff67d6b205e12b7166b556bdced3d3d 20124 
golang-docker-dev_18.09.1+dfsg1-4_all.deb
 0fb9dd2d31629b4da69106a0c5b042ec2d0ef258 532584 
golang-github-docker-docker-dev_18.09.1+dfsg1-4_all.deb
 a1b82a8670ca801d961ff80d37f49f5578bb6784 21292 
vim-syntax-docker_18.09.1+dfsg1-4_all.deb
Checksums-Sha256:
 e028aabcdff4b00fea95ed57da65966561d6c05c543713ddf5dfca75e55f3b99 8933 
docker.io_18.09.1+dfsg1-4.dsc
 30de40e854148ad70c507ea7696e32da09465fa776ee6816269ff08925e1a880 40788 
docker.io_18.09.1+dfsg1-4.debian.tar.xz
 4ddf75d5c66b1d1770ea2dbd8df520f0c777880ebf8f86b5c3e1694f192a15b1 974668 
docker-doc_18.09.1+dfsg1-4_all.deb
 889b70bc3755a9c30742cdc496f2086d7f0185313a7b1282f451f64857a422e4 7012584 
docker.io-dbgsym_18.09.1+dfsg1-4_amd64.deb
 a831eecd67c4608839f92119f68da9f681430e6aa6d80740c8f66a6284d92725 25559 
docker.io_18.09.1+dfsg1-4_amd64.buildinfo
 a55abb3b2343db054b593b44812dd72f648473c0768bc5de48ad5b5737d8dce8 53137976 
docker.io_18.09.1+dfsg1-4_amd64.deb
 01687e97044197abcdb30589cbd4fa3d59c913a7947760c54e2dda41f94f89c9 20124 
golang-docker-dev_18.09.1+dfsg1-4_all.deb
 147acca65656f7f25b00fa92212839f0fe75ae5f3a79855cf7d488be8406f1d6 532584 
golang-github-docker-docker-dev_18.09.1+dfsg1-4_all.deb
 005e9f05f5bc5a0bbf20e6afeb4e2ddb5e441a61a828478aacc95b1b753537c8 21292 
vim-syntax-docker_18.09.1+dfsg1-4_all.deb
Files:
 658bd0028e1a4f9b92425f90cf1caecc 8933 admin optional 
docker.io_18.09.1+dfsg1-4.dsc
 925a8d5bba407ecfeacaf85b5aea1ef3 40788 admin optional 
docker.io_18.09.1+dfsg1-4.debian.tar.xz
 80b25c06b111421958ace24695c538f3 974668 doc 

Bug#920661: marked as done (docker.io: failed to start shim: exec: "containerd-shim": executable file not found in $PATH: unknown)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 13:53:15 +1100
with message-id <2177541.J6sLav8ZAG@deblab>
and subject line Re: Bug#920661: docker.io: failed to start shim: exec: 
"containerd-shim": executable file not found in $PATH: unknown
has caused the Debian Bug report #920661,
regarding docker.io: failed to start shim: exec: "containerd-shim": executable 
file not found in $PATH: unknown
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.)


-- 
920661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 18.09.1+dfsg1-3
Severity: important


Hi,

I cannot build docker image due to the following error. It looks like
there is some path related problem?


$ docker build .
Sending build context to Docker daemon  57.34kB
...
...
...
failed to start shim: exec: "containerd-shim": executable file not found in 
$PATH: unknown



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

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

Versions of packages docker.io depends on:
ii  adduser 3.118
ii  iptables1.8.2-3
ii  libc6   2.28-5
ii  libdevmapper1.02.1  2:1.02.155-1
ii  libltdl72.4.6-8
ii  libnspr42:4.20-1
ii  libnss3 2:3.41-1
ii  libseccomp2 2.3.3-3
ii  libsystemd0 240-4
ii  lsb-base10.2018112800
ii  runc1.0.0~rc6+dfsg1-1
ii  tini0.18.0-1

Versions of packages docker.io recommends:
ii  ca-certificates  20190110
ii  cgroupfs-mount   1.4
ii  git  1:2.20.1-2
ii  needrestart  3.3-2
ii  xz-utils 5.2.2-1.3

Versions of packages docker.io suggests:
ii  aufs-tools   1:4.9+20170918-2
pn  btrfs-progs  
ii  debootstrap  1.0.114
pn  docker-doc   
ii  e2fsprogs1.44.5-1
pn  rinse
pn  xfsprogs 
pn  zfs-fuse | zfsutils  

-- no debconf information

-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Package: docker.io
Version: 18.09.1+dfsg1-4

> failed to start shim: exec: "containerd-shim": executable file not found in
> $PATH: unknown

Apologies for troubles. This has been fixed in just uploaded 18.09.1+dfsg1-4.

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

-- 
Cheers,
 Dmitry Smirnov.

---

Before a man speaks, it is always safe to assume that he is a fool. After
he speaks it is seldom necessary to assume.
-- H. L. Mencken


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


Bug#882729: marked as done (signing-party: spelling fixes)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:49:15 +
with message-id 
and subject line Bug#882729: fixed in signing-party 2.8-1
has caused the Debian Bug report #882729,
regarding signing-party: spelling fixes
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.)


-- 
882729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: signing-party
Version: 2.6-1
Severity: minor
Tags: patch

Dear Maintainer,

I ran codespell on pgp-tools and found five spelling mistakes.

Here is a patch to correct the spelling errors.

Best wishes,

Edward.
Index: caff/README.many-keys
===
--- caff/README.many-keys   (revision 899)
+++ caff/README.many-keys   (working copy)
@@ -18,7 +18,7 @@
   For convenience, caff also allows spaces in fingerprints/keyids as output by
   gpg --fingerprint.
 
-* Use gpgparticipants(1) formated input when possible.
+* Use gpgparticipants(1) formatted input when possible.
 
   When the KSP organizer provides a gpgparticipants(1) compatible list
   of all the participants, it can be convenient to transcribe the
Index: caff/caff
===
--- caff/caff   (revision 899)
+++ caff/caff   (working copy)
@@ -1131,7 +1131,7 @@
 my ($message_entity) = @_;
 
 if ((scalar @{$CONFIG{'mailer-send'}} > 0) && 
!$warned_about_broken_mailer_send) {
-mywarn("You have set arguments to pass to Mail::Mailer.  Better fix 
your MTA.  (Also, Mail::Mailer's error reporting is non existant, so it won't 
tell you when it doesn't work.)");
+mywarn("You have set arguments to pass to Mail::Mailer.  Better fix 
your MTA.  (Also, Mail::Mailer's error reporting is non existent, so it won't 
tell you when it doesn't work.)");
 $warned_about_broken_mailer_send = 1;
 };
 $message_entity->send(@{$CONFIG{'mailer-send'}});
@@ -1870,7 +1870,7 @@
 foreach my $u (@signers) {
 my @signeduids; # uids signed by $u
 foreach my $uid (@uids) {
-# we use UIDs hashes to distinguish and select UIDs; it's the 
only reliable way to identify them accross keyrings
+# we use UIDs hashes to distinguish and select UIDs; it's the 
only reliable way to identify them across keyrings
 push @signeduids, $uid if grep { $u eq $_ } (keys 
%{$uid->{xsigners}}) and
  !grep { $uid->{hash} eq $_->{hash} } 
@signeduids;
 }
Index: keyanalyze/pgpring/lib.c
===
--- keyanalyze/pgpring/lib.c(revision 899)
+++ keyanalyze/pgpring/lib.c(working copy)
@@ -482,7 +482,7 @@
   }
   else
   {
-ungetc (c, fp); /* undo our dammage */
+ungetc (c, fp); /* undo our damage */
 /* There wasn't room for the line -- increase ``s'' */
 offset = *size - 1; /* overwrite the terminating 0 */
 *size += STRING;
Index: keyart/doc/druken-bishop.txt
===
--- keyart/doc/druken-bishop.txt(revision 899)
+++ keyart/doc/druken-bishop.txt(working copy)
@@ -51,7 +51,7 @@
 (9,5), which is position 104, the center of the board.
 
 Movement is defined by taking the fingerprint, and coverting each
-character to its binary value. For exmaple, the fingerprint:
+character to its binary value. For example, the fingerprint:
 
   E041 3539 273A 6534 A3E1  9259 22EE E048 8086 060F
 
--- End Message ---
--- Begin Message ---
Source: signing-party
Source-Version: 2.8-1

We believe that the bug you reported is fixed in the latest version of
signing-party, 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 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated signing-party 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: Mon, 28 Jan 2019 03:05:33 +0100
Source: signing-party
Architecture: source
Version: 2.8-1
Distribution: 

Bug#872529: marked as done (caff: should put the TTY in a sane state before prompts)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:49:15 +
with message-id 
and subject line Bug#872529: fixed in signing-party 2.8-1
has caused the Debian Bug report #872529,
regarding caff: should put the TTY in a sane state before prompts
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.)


-- 
872529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: signing-party
Version: 2.5-1
Severity: normal
File: /usr/bin/caff

The only way to get past the prompt into type Ctrl+J (yes, hold down Control
and press J).

##gpg> save
[INFO] Key 0x283681BA6FE7F41D UID 1 Sam Hartman  done
[INFO] Key 0x283681BA6FE7F41D UID 2 Sam Hartman  done
Mail signature for 'Sam Hartman ' to 
'hartm...@debian.org'? [Y/n] ^M^JWhat about [Y/n] is so hard to understand?
Answer with either 'n' or 'y' or just press enter for the default.
^JMail signature for 'Sam Hartman ' to 
'hartm...@debian.org'? [Y/n] Mail signature for 'Sam Hartman 
' to 'hartm...@mit.edu'? [Y/n] ^J[INFO] Key 
0x283681BA6FE7F41D done

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

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

Versions of packages signing-party depends on:
ii  gnupg  2.1.18-6
ii  libc6  2.24-11+deb9u1
ii  libclass-methodmaker-perl  2.24-1+b2
ii  libgnupg-interface-perl0.52-9
ii  libmailtools-perl  2.18-1
ii  libmd0 0.0.0-2
ii  libmime-tools-perl 5.508-1
ii  libnet-idn-encode-perl 2.400-1
ii  libterm-readkey-perl   2.37-1
ii  libtext-template-perl  1.46-1
ii  perl   5.24.1-3+deb9u1
ii  python 2.7.13-2
ii  qprint 1.1.dfsg.2-2+b1

Versions of packages signing-party recommends:
ii  dialog  1.3-20160828-2
ii  libgd-perl [libgd-gd2-perl] 2.53-3
ii  libpaper-utils  1.1.24+nmu5
ii  postfix [mail-transport-agent]  3.1.4-7
ii  whiptail0.52.19-1+b1

Versions of packages signing-party suggests:
pn  fonts-noto-cjk   
ii  fonts-noto-mono  20161116-1
ii  imagemagick  8:6.9.7.4+dfsg-11+deb9u1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-11+deb9u1
ii  mutt 1.7.2-1
pn  qrencode 
ii  texlive-font-utils   2016.20170123-5
ii  texlive-latex-extra  2016.20170123-5
ii  texlive-latex-recommended2016.20170123-5
pn  texlive-xetex
pn  wipe 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: signing-party
Source-Version: 2.8-1

We believe that the bug you reported is fixed in the latest version of
signing-party, 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 872...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated signing-party 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: Mon, 28 Jan 2019 03:05:33 +0100
Source: signing-party
Architecture: source
Version: 2.8-1
Distribution: unstable
Urgency: low
Maintainer: Guilhem Moulin 
Changed-By: Guilhem Moulin 
Closes: 872529 882729 905097
Changes:
 signing-party (2.8-1) unstable; urgency=low
 .
   [ Guilhem Moulin ]
   * keyart, gpgparticipants-prefill: port to python3.
   * keyart:
 + Don't print ASCII art for subkeys, only the master key.
 + Pass --no-auto-check-trustdb flag to gpg(1).
 + Fix crash with non-ASCII UIDs.  Patch from Grégoire Detrez.
   * Fix a couple of spelling errors.  Thanks to Edward Betts for the report
 and patch. (Closes: #882729)
   * caff:
 + Add the "only-sign-text-ids" to the list of gpg(1) options imported from
   ~/.gnupg/gpg.conf.
 + Ensure the terminal is "sane enough" when asking questions ('echo',
   'echok', 

Bug#917595: marked as done (umoci: FTBFS (cannot find package "github.com/fatih/color"))

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:49:28 +
with message-id 
and subject line Bug#917595: fixed in umoci 0.4.3+dfsg-1
has caused the Debian Bug report #917595,
regarding umoci: FTBFS (cannot find package "github.com/fatih/color")
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.)


-- 
917595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:umoci
Version: 0.4.0+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --buildsystem=golang --with=golang
   dh_update_autotools_config -a -O--buildsystem=golang
   dh_autoreconf -a -O--buildsystem=golang
   dh_auto_configure -a -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/umoci-0.4.0+dfsg'
COMMIT=1 COMMIT_NO=1 /usr/bin/make doc
make[2]: Entering directory '/<>/umoci-0.4.0+dfsg'
go-md2man -in doc/man/umoci-unpack.1.md -out doc/man/umoci-unpack.1
go-md2man -in doc/man/umoci-raw-runtime-config.1.md -out 
doc/man/umoci-raw-runtime-config.1
go-md2man -in doc/man/umoci-config.1.md -out doc/man/umoci-config.1
go-md2man -in doc/man/umoci-ls.1.md -out doc/man/umoci-ls.1
go-md2man -in doc/man/umoci-remove.1.md -out doc/man/umoci-remove.1

[... snipped ...]

src/github.com/openSUSE/umoci/oci/config/generate/save.go
src/github.com/openSUSE/umoci/oci/config/generate/spec.go
src/github.com/openSUSE/umoci/oci/config/generate/spec_test.go
src/github.com/openSUSE/umoci/oci/layer/generate.go
src/github.com/openSUSE/umoci/oci/layer/generate_test.go
src/github.com/openSUSE/umoci/oci/layer/tar_extract.go
src/github.com/openSUSE/umoci/oci/layer/tar_extract_test.go
src/github.com/openSUSE/umoci/oci/layer/tar_generate.go
src/github.com/openSUSE/umoci/oci/layer/tar_generate_test.go
src/github.com/openSUSE/umoci/oci/layer/tar_unix.go
src/github.com/openSUSE/umoci/oci/layer/unpack.go
src/github.com/openSUSE/umoci/oci/layer/unpack_test.go
src/github.com/openSUSE/umoci/oci/layer/utils.go
src/github.com/openSUSE/umoci/oci/layer/utils_test.go
src/github.com/openSUSE/umoci/pkg/fseval/fseval.go
src/github.com/openSUSE/umoci/pkg/fseval/fseval_default.go
src/github.com/openSUSE/umoci/pkg/fseval/fseval_rootless.go
src/github.com/openSUSE/umoci/pkg/idtools/idtools.go
src/github.com/openSUSE/umoci/pkg/idtools/idtools_test.go
src/github.com/openSUSE/umoci/pkg/mtreefilter/mask.go
src/github.com/openSUSE/umoci/pkg/mtreefilter/mask_test.go
src/github.com/openSUSE/umoci/pkg/rootlesscontainers-proto/rootlesscontainers_generate.go
src/github.com/openSUSE/umoci/pkg/system/mknod_linux.go
src/github.com/openSUSE/umoci/pkg/system/mknod_linux_test.go
src/github.com/openSUSE/umoci/pkg/system/utime_linux.go
src/github.com/openSUSE/umoci/pkg/system/utime_linux_test.go
src/github.com/openSUSE/umoci/pkg/system/xattr_linux.go
src/github.com/openSUSE/umoci/pkg/unpriv/unpriv.go
src/github.com/openSUSE/umoci/pkg/unpriv/unpriv_test.go
src/github.com/openSUSE/umoci/pkg/unpriv/unpriv_utimes_test.go
src/github.com/openSUSE/umoci/third_party/shared/util.go
src/github.com/openSUSE/umoci/third_party/user/lookup.go
src/github.com/openSUSE/umoci/third_party/user/lookup_unix.go
src/github.com/openSUSE/umoci/third_party/user/user.go
src/github.com/openSUSE/umoci/third_party/user/user_test.go
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/umoci-0.4.0\+dfsg/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/umoci-0.4.0\+dfsg/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/openSUSE/umoci/cmd/umoci github.com/openSUSE/umoci/mutate 
github.com/openSUSE/umoci/oci/cas github.com/openSUSE/umoci/oci/cas/dir 
github.com/openSUSE/umoci/oci/casext 
github.com/openSUSE/umoci/oci/config/convert 
github.com/openSUSE/umoci/oci/config/generate 
github.com/openSUSE/umoci/oci/layer github.com/openSUSE/umoci/pkg/fseval 
github.com/openSUSE/umoci/pkg/idtools github.com/openSUSE/umoci/pkg/mtreefilter 
github.com/openSUSE/umoci/pkg/rootlesscontainers-proto 
github.com/openSUSE/umoci/pkg/system github.com/openSUSE/umoci/pkg/unpriv 
github.com/openSUSE/umoci/third_party/shared 
github.com/openSUSE/umoci/third_party/user
src/github.com/apex/log/handlers/cli/cli.go:12:2: cannot find package 
"github.com/fatih/color" in any of:
/usr/lib/go-1.10/src/github.com/fatih/color (from $GOROOT)

/<>/umoci-0.4.0+dfsg/obj-x86_64-linux-gnu/src/github.com/fatih/color 
(from $GOPATH)

Bug#917406: marked as done (ITA: elinks -- advanced text-mode WWW browser)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#917406: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #917406,
regarding ITA: elinks -- advanced text-mode WWW browser
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.)


-- 
917406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: normal

I'm orphaning elinks. It's been mostly dead upstream for a while
(although there's a fork at https://github.com/rkd77/felinks which
is seeing some activity) and it's deficits wrt fully-fledged TLS
support make it less and less useful as a web browser (I'm actually
using links2 myself these days).

elinks still has some features not found in other text-based browsers
(like support for rendering the actual colours of an HTML document),
but if noone picks it up, it's probably best to remove it when the
bullseye development cycle starts.


The package description is:
 ELinks is a feature-rich program for browsing the web in text mode.  It is
 like enhanced Lynx and Links.  The most noteworthy features of ELinks are:
 .
  * Lots of protocols (local files, finger, HTTP(S), FTP, IPv4/6 etc.)
  * Internationalized domain names
  * Persistent cookies, HTTP authentication and proxy authentication
  * Tabbed browsing, good looking menus and dialogs, and key-binding manager
  * History browsing and typeahead searches
  * Forms history and completion, and history in commonly used input dialogs
  * CSS support and support for browser scripting (Perl, Lua, Guile etc.)
  * Tables and frames rendering, and configurable color support
  * Compressed and background (non-blocking) downloads, and download resuming
 ELinks is a feature-rich program for browsing the web in text mode.  It is
 like enhanced Lynx and Links.  The most noteworthy features of ELinks are:
 .
  * Lots of protocols (local files, finger, HTTP(S), FTP, IPv4/6 etc.)
  * Internationalized domain names
  * Persistent cookies, HTTP authentication and proxy authentication
  * Tabbed browsing, good looking menus and dialogs, and key-binding manager
  * History browsing and typeahead searches
  * Forms history and completion, and history in commonly used input dialogs
  * CSS support and support for browser scripting (Perl, Lua, Guile etc.)
  * Tables and frames rendering, and configurable color support
  * Compressed and background (non-blocking) downloads, and download resuming
--- End Message ---
--- Begin Message ---
Source: elinks
Source-Version: 0.13~20190125-1

We believe that the bug you reported is fixed in the latest version of
elinks, 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 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated elinks 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: Sat, 26 Jan 2019 02:53:52 +0100
Source: elinks
Architecture: source
Version: 0.13~20190125-1
Distribution: experimental
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 740981 757631 797931 797934 797968 856852 866015 891575 917406
Changes:
 elinks (0.13~20190125-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #891575, #797931, #797934, #757631,
 #866015, #797968, #740981, #856852)
   * Add git-buildpackage conf file
   * Refreshed patches & removed patches that were includes upstream.
 Removed patches:
 08-drop-deprecated-gnutls-functions.diff
 08_524696_fix_imdb_urls.diff
 09-Switch-to-use-lua-5.1.diff
 11-fix-compat-with-gnutls36.patch
   * Add libgcrypt20-dev to build deps
   * Re-added 14_debug_disable_Werror.diff to enable development versions debug
 support
   * Added 16_POST_BUFFER_SIZE.diff patch which to enable  uploading large files
 over https:// connections.
   * Add ascii-replacement-utf8-console.diff patch to print ASCII replacement
 for characters not found in current codepage in utf8 mode
   * Enable LZMA support
   * Enable BitTorrent
   * 

Bug#797934: marked as done (elinks: Support for SSL authentication using client certs)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#797934: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #797934,
regarding elinks: Support for SSL authentication using client certs
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.)


-- 
797934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elinks
Version: 0.12~pre6-10
Severity: wishlist

Hi!

Was checking into the Debian SSO implementation
, and noticed that elinks
does not support client certs. I've implemented this, but due to the
GnuTLS rehandshake issue, I've not been able to test them. Once the
other issue is fixed I could probably take another look at this. It
might also make sense to have two options, one for the public and
private key files.

Thanks,
Guillem
diff --git a/src/network/ssl/ssl.c b/src/network/ssl/ssl.c
index 363245d..6310018 100644
--- a/src/network/ssl/ssl.c
+++ b/src/network/ssl/ssl.c
@@ -147,6 +147,21 @@ init_gnutls(struct module *module)
 GNUTLS_VERIFY_ALLOW_X509_V1_CA_CRT);
 	}
 
+	if (get_opt_bool("connection.ssl.client_cert.enable")) {
+		unsigned char *client_cert;
+
+		client_cert = get_opt_str("connection.ssl.client_cert.file");
+		if (!*client_cert) {
+			client_cert = getenv("X509_CLIENT_CERT");
+			if (client_cert && !*client_cert)
+client_cert = NULL;
+		}
+
+		if (client_cert) {
+			gnutls_certificate_set_x509_key_file(xcred,
+client_cert, client_cert, GNUTLS_X509_FMT_PEM);
+		}
+	}
 }
 
 static void
@@ -181,6 +196,22 @@ static union option_info gnutls_options[] = {
 		"restart ELinks for the changes to take effect. "
 		"This option affects GnuTLS but not OpenSSL.")),
 
+	INIT_OPT_TREE("connection.ssl", N_("Client Certificates"),
+		"client_cert", OPT_SORT,
+		N_("X509 client certificate options.")),
+
+	INIT_OPT_BOOL("connection.ssl.client_cert", N_("Enable"),
+		"enable", 0, 0,
+		N_("Enable or not the sending of X509 client certificates "
+		"to servers which request them.")),
+
+	INIT_OPT_STRING("connection.ssl.client_cert", N_("Certificate File"),
+		"file", 0, "",
+		N_("The location of a file containing the client certificate "
+		"and unencrypted private key in PEM format. If unset, the "
+		"file pointed to by the X509_CLIENT_CERT variable is used "
+		"instead.")),
+
 	NULL_OPTION_INFO,
 };
 
--- End Message ---
--- Begin Message ---
Source: elinks
Source-Version: 0.13~20190125-1

We believe that the bug you reported is fixed in the latest version of
elinks, 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 797...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated elinks 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: Sat, 26 Jan 2019 02:53:52 +0100
Source: elinks
Architecture: source
Version: 0.13~20190125-1
Distribution: experimental
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 740981 757631 797931 797934 797968 856852 866015 891575 917406
Changes:
 elinks (0.13~20190125-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #891575, #797931, #797934, #757631,
 #866015, #797968, #740981, #856852)
   * Add git-buildpackage conf file
   * Refreshed patches & removed patches that were includes upstream.
 Removed patches:
 08-drop-deprecated-gnutls-functions.diff
 08_524696_fix_imdb_urls.diff
 09-Switch-to-use-lua-5.1.diff
 11-fix-compat-with-gnutls36.patch
   * Add libgcrypt20-dev to build deps
   * Re-added 14_debug_disable_Werror.diff to enable development versions debug
 support
   * Added 16_POST_BUFFER_SIZE.diff patch which to enable  uploading large files
 over https:// connections.
   * Add ascii-replacement-utf8-console.diff patch to print ASCII replacement
 for characters not found in current codepage in utf8 mode
   * Enable LZMA support
   * Enable BitTorrent
   * Enable NNTP Support
   * Enable Unicode combining characters support
   * 

Bug#919473: marked as done (zapping: Settings schema 'net.sf.Zapping.plugins.teletext' does not contain a key named 'method')

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:49:50 +
with message-id 
and subject line Bug#919473: fixed in zapping 0.10~cvs6-16
has caused the Debian Bug report #919473,
regarding zapping: Settings schema 'net.sf.Zapping.plugins.teletext' does not 
contain a key named 'method'
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.)


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

Package: zapping
Version: 0.10~cvs6-15
Severity: grave

zapping doesn't start:

  $ zapping

  (zapping:3191): dbind-WARNING **: 13:01:17.865: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files

  (zapping:3191): GLib-GIO-ERROR **: 13:01:18.527: Settings schema 
'net.sf.Zapping.plugins.teletext' does not contain a key named 'method'
  Trace/breakpoint trap


-- System Information:
Architecture: i386

Versions of packages zapping depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  libc62.28-5
ii  libcairo21.16.0-2
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libglib2.0-0 2.58.2-3
ii  libgtk-3-0   3.24.3-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblirc-client0  0.10.1-5
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpng16-16  1.6.36-3
ii  libpython2.7 2.7.15-5
ii  libx11-6 2:1.6.7-1
ii  libxext6 2:1.3.3-1+b2
ii  libxinerama1 2:1.1.4-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxmu6  2:1.1.2-2
ii  libxv1   2:1.0.11-1
ii  libxxf86dga1 2:1.1.4-1+b3
ii  libxxf86vm1  1:1.1.4-1+b2
ii  libzvbi0 0.2.35-15

Versions of packages zapping recommends:
pn  gconf2  

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: zapping
Source-Version: 0.10~cvs6-16

We believe that the bug you reported is fixed in the latest version of
zapping, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated zapping 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: Fri, 25 Jan 2019 16:53:10 +0200
Source: zapping
Architecture: source
Version: 0.10~cvs6-16
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Yavor Doganov 
Closes: 919473
Changes:
 zapping (0.10~cvs6-16) unstable; urgency=medium
 .
   * QA upload.
   * debian/patches/24-GConf-to-GSettings.patch: Assign each GSettings
 instance to its own unique variable; otherwise things get really messy
 when plugins are loaded (Closes: #919473).
   * debian/patches/27-zsfb-manpage.patch: New; build and install
 zapping_setup_fb's manpage conditionally based on the same
 AM_CONDITIONAL that is used for the binary.
   * debian/patches/series: Update.
   * debian/rules: Pass --disable-v4l --disable-bktr on GNU/Hurd; remove
 hurd-specific CPPFLAGS.
 (override_dh_auto_install): Conditionally move zapping_setup_fb to
 /usr/bin as it's only built on GNU/Linux architectures.
   * debian/control (Build-Depends): Remove freebsd-glue; that was a really
 stupid idea that I should be ashamed of.  And I am.
 (Depends): Add gsettings-desktop-schemas -- the code loads one schema
 from this package which will be a hard error if it is not installed.
 (Standards-Version): Bump to 4.3.0; no changes needed.
   * debian/copyright: Update copyright years, add Jeremy Bicha.
Checksums-Sha1:
 4790602f3b639c038a83b85a1cd9de55f84ae809 2157 

Bug#905097: marked as done (signing-party: gpglist crashes for (some?) signature revocations)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:49:15 +
with message-id 
and subject line Bug#905097: fixed in signing-party 2.8-1
has caused the Debian Bug report #905097,
regarding signing-party: gpglist crashes for (some?) signature revocations
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.)


-- 
905097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: signing-party
Version: 2.7-2
Severity: normal

Dear Maintainer,
'rev' packet parsing is incorrect and may result in:

  hi, i'm a bug. please report me to my owner
  input: rev:::1:HASH:1533019781User Example
:30x,00::HASH:::10:, key: user@example at /usr/bin/gpglist line
165, <$fh> line 5.

The problem is with ',00' just after '30x' which is not accounted for.

I already committed a fix in https://salsa.debian.org/debian/signing-
party/commit/c62477e3086c33af14493337227ec219f151d5b4.

I should also propose to use the colon format correctly, not with regexpes. :)

Tomasz



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

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

Versions of packages signing-party depends on:
ii  gnupg  2.2.9-1
ii  libc6  2.27-5
ii  libclass-methodmaker-perl  2.24-1+b4
ii  libgnupg-interface-perl0.52-10
ii  libmailtools-perl  2.18-1
ii  libmd0 1.0.0-1
ii  libmime-tools-perl 5.509-1
ii  libnet-idn-encode-perl 2.400-1+b2
ii  libterm-readkey-perl   2.37-1+b2
ii  libtext-template-perl  1.53-1
ii  perl   5.26.2-6
ii  python 2.7.15-3
ii  qprint 1.1.dfsg.2-2+b1

Versions of packages signing-party recommends:
ii  dialog  1.3-20171209-1+b1
ii  libgd-perl [libgd-gd2-perl] 2.66-1+b2
ii  libpaper-utils  1.1.24+nmu5
ii  postfix [mail-transport-agent]  3.3.0-1+b1
ii  whiptail0.52.20-5

Versions of packages signing-party suggests:
pn  fonts-noto-cjk   
ii  fonts-noto-mono  20171026-2
ii  imagemagick  8:6.9.10.2+dfsg-3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.2+dfsg-3
ii  mutt 1.10.1-1
ii  qrencode 3.4.4-1+b2
pn  texlive-font-utils   
ii  texlive-latex-extra  2018.20180505-1
ii  texlive-latex-recommended2018.20180505-1
ii  texlive-xetex2018.20180505-1
pn  wipe 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: signing-party
Source-Version: 2.8-1

We believe that the bug you reported is fixed in the latest version of
signing-party, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated signing-party 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: Mon, 28 Jan 2019 03:05:33 +0100
Source: signing-party
Architecture: source
Version: 2.8-1
Distribution: unstable
Urgency: low
Maintainer: Guilhem Moulin 
Changed-By: Guilhem Moulin 
Closes: 872529 882729 905097
Changes:
 signing-party (2.8-1) unstable; urgency=low
 .
   [ Guilhem Moulin ]
   * keyart, gpgparticipants-prefill: port to python3.
   * keyart:
 + Don't print ASCII art for subkeys, only the master key.
 + Pass --no-auto-check-trustdb flag to gpg(1).
 + Fix crash with non-ASCII UIDs.  Patch from Grégoire Detrez.
   * Fix a couple of spelling errors.  Thanks to Edward Betts for the report
 and patch. (Closes: #882729)
   * caff:
 + Add the "only-sign-text-ids" to the list of gpg(1) options imported from
   ~/.gnupg/gpg.conf.
 + Ensure the terminal is "sane 

Bug#866015: marked as done (elinks: SSL error with some websites)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#866015: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #866015,
regarding elinks: SSL error with some websites
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.)


-- 
866015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elinks
Version: 0.12~pre6-12
Severity: important

Dear Maintainer,

ELinks fails to load some websites:

$ elinks -verbose 2 -dump https://metrocom-chat.ml/
ELinks: SSL error

Wget, curl and all modern browsers have no problems with this website,
for example.


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

Kernel: Linux 4.9.0-3-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/bash
Init: systemd (via /run/systemd/system)

Versions of packages elinks depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  dpkg   1.18.24
ii  elinks-data0.12~pre6-12
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.24-11+deb9u1
ii  libcomerr2 1.43.4-2
ii  libexpat1  2.2.0-2+deb9u1
ii  libfsplib0 0.11-2
ii  libgnutls303.5.8-5+deb9u1
ii  libgpm21.20.4-6.2+b1
ii  libgssapi-krb5-2   1.15-1
ii  libidn11   1.33-1
ii  libk5crypto3   1.15-1
ii  libkrb5-3  1.15-1
ii  liblua5.1-05.1.5-8.1+b2
ii  libperl5.245.24.1-3
ii  libtre50.8.0-6
ii  zlib1g 1:1.2.8.dfsg-5

elinks recommends no packages.

Versions of packages elinks suggests:
pn  elinks-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: elinks
Source-Version: 0.13~20190125-1

We believe that the bug you reported is fixed in the latest version of
elinks, 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 866...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated elinks 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: Sat, 26 Jan 2019 02:53:52 +0100
Source: elinks
Architecture: source
Version: 0.13~20190125-1
Distribution: experimental
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 740981 757631 797931 797934 797968 856852 866015 891575 917406
Changes:
 elinks (0.13~20190125-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #891575, #797931, #797934, #757631,
 #866015, #797968, #740981, #856852)
   * Add git-buildpackage conf file
   * Refreshed patches & removed patches that were includes upstream.
 Removed patches:
 08-drop-deprecated-gnutls-functions.diff
 08_524696_fix_imdb_urls.diff
 09-Switch-to-use-lua-5.1.diff
 11-fix-compat-with-gnutls36.patch
   * Add libgcrypt20-dev to build deps
   * Re-added 14_debug_disable_Werror.diff to enable development versions debug
 support
   * Added 16_POST_BUFFER_SIZE.diff patch which to enable  uploading large files
 over https:// connections.
   * Add ascii-replacement-utf8-console.diff patch to print ASCII replacement
 for characters not found in current codepage in utf8 mode
   * Enable LZMA support
   * Enable BitTorrent
   * Enable NNTP Support
   * Enable Unicode combining characters support
   * Enable EX mode support
   * Enable SpiderMonkey support
   * Enable terminfo support
   * Build documentation
   * Build with libev
   * Bumped to compat level 12.
 No need to have dh-autoreconf, autotools-dev from build deps
 Also no need to explicitly call the respective sequences in rules
   * Remove old upstream gpg key.
   * Remove whitespaces
   * Renamed elinks.config to elinks.conf, old name confused build scrips
   * debian/rules: Override dh_installexamples to exclude .gitignore
   * Add typos.diff patch to fix spelling mistakes
   * debian/control:
 + 

Bug#891575: marked as done (elinks: CVE-2012-6709)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#891575: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #891575,
regarding elinks: CVE-2012-6709
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.)


-- 
891575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elinks
Version: 0.12~pre5-9
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

the following vulnerability was published for elinks.

CVE-2012-6709[0]:
| ELinks 0.12 and Twibright Links 2.3 have Missing SSL Certificate
| Validation.

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-2012-6709
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6709

Please adjust the affected versions in the BTS as needed.

-- 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: elinks
Source-Version: 0.13~20190125-1

We believe that the bug you reported is fixed in the latest version of
elinks, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated elinks 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: Sat, 26 Jan 2019 02:53:52 +0100
Source: elinks
Architecture: source
Version: 0.13~20190125-1
Distribution: experimental
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 740981 757631 797931 797934 797968 856852 866015 891575 917406
Changes:
 elinks (0.13~20190125-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #891575, #797931, #797934, #757631,
 #866015, #797968, #740981, #856852)
   * Add git-buildpackage conf file
   * Refreshed patches & removed patches that were includes upstream.
 Removed patches:
 08-drop-deprecated-gnutls-functions.diff
 08_524696_fix_imdb_urls.diff
 09-Switch-to-use-lua-5.1.diff
 11-fix-compat-with-gnutls36.patch
   * Add libgcrypt20-dev to build deps
   * Re-added 14_debug_disable_Werror.diff to enable development versions debug
 support
   * Added 16_POST_BUFFER_SIZE.diff patch which to enable  uploading large files
 over https:// connections.
   * Add ascii-replacement-utf8-console.diff patch to print ASCII replacement
 for characters not found in current codepage in utf8 mode
   * Enable LZMA support
   * Enable BitTorrent
   * Enable NNTP Support
   * Enable Unicode combining characters support
   * Enable EX mode support
   * Enable SpiderMonkey support
   * Enable terminfo support
   * Build documentation
   * Build with libev
   * Bumped to compat level 12.
 No need to have dh-autoreconf, autotools-dev from build deps
 Also no need to explicitly call the respective sequences in rules
   * Remove old upstream gpg key.
   * Remove whitespaces
   * Renamed elinks.config to elinks.conf, old name confused build scrips
   * debian/rules: Override dh_installexamples to exclude .gitignore
   * Add typos.diff patch to fix spelling mistakes
   * debian/control:
 + Replace Conflicts with Breaks+Replaces
 + Update standards version to 4.3.0
 + New maintainer (Closes: #917406)
 + Add Vcs-* fields
   * Add upstream metadata
   * Switch to DEP-5 copyright format
   * Disable pristine-tar, since we are getting the release from upstream git
Checksums-Sha1:
 31dfa7b9392b6a51c14f3aac843f424faaa1818a 2340 elinks_0.13~20190125-1.dsc
 8ce05dc4aa86056e00ad4b4c8900b88966e02b82 1768440 
elinks_0.13~20190125.orig.tar.xz
 9e424e8b0e8954ef768fe4025f62e2e09375e0e3 23044 
elinks_0.13~20190125-1.debian.tar.xz
 9216b6f327a31103886df8add7071e19fc1c3727 6496 
elinks_0.13~20190125-1_source.buildinfo
Checksums-Sha256:
 fedc16fc62d261f0767562a4a48045e684015ea82053956c2df6b86d919bf8ac 2340 
elinks_0.13~20190125-1.dsc
 

Bug#919820: marked as done (mysql-connector-python: CVE-2019-2435)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:48:06 +
with message-id 
and subject line Bug#919820: fixed in mysql-connector-python 8.0.14-1
has caused the Debian Bug report #919820,
regarding mysql-connector-python: CVE-2019-2435
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.)


-- 
919820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql-connector-python
Version: 8.0.11-1
Severity: grave
Tags: security upstream
Control: found -1 2.1.6-1

Hi,

The following vulnerability was published for mysql-connector-python.

CVE-2019-2435[0]:
| Vulnerability in the MySQL Connectors component of Oracle MySQL
| (subcomponent: Connector/Python). Supported versions that are affected
| are 8.0.13 and prior and 2.1.8 and prior. Easily exploitable
| vulnerability allows unauthenticated attacker with network access via
| TLS to compromise MySQL Connectors. Successful attacks require human
| interaction from a person other than the attacker. Successful attacks
| of this vulnerability can result in unauthorized creation, deletion or
| modification access to critical data or all MySQL Connectors
| accessible data as well as unauthorized access to critical data or
| complete access to all MySQL Connectors accessible data. CVSS 3.0 Base
| Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector:
| (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).

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-2019-2435
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2435
[1] 
http://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html#CVE-2019-2435

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mysql-connector-python
Source-Version: 8.0.14-1

We believe that the bug you reported is fixed in the latest version of
mysql-connector-python, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated mysql-connector-python 
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: Sun, 27 Jan 2019 21:07:55 -0500
Source: mysql-connector-python
Binary: python-mysql.connector python3-mysql.connector
Architecture: source all
Version: 8.0.14-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-mysql.connector - pure Python implementation of MySQL Client/Server 
protocol
 python3-mysql.connector - pure Python implementation of MySQL Client/Server 
protocol (Pytho
Closes: 919820
Changes:
 mysql-connector-python (8.0.14-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
 .
   [ Sandro Tosi ]
   * New upstream release, fix CVE-2019-2435; Closes: #919820
   * debian/copyright
 - extend packaging copyright years
 - update upstream copyright years
   * debian/patches/support_alternative_mysqld_implementation.patch
 - refresh patch
   * debian/control
 - bump Standards-Version to 4.3.0 (no changes needed)
Checksums-Sha1:
 bbe743d4875450c9f58fd77db2b6109fb24035a6 2347 
mysql-connector-python_8.0.14-1.dsc
 cb8982fed0fd89c3f15e724f3059dd9e208073ab 12000443 
mysql-connector-python_8.0.14.orig.tar.gz
 7be2ff258ac2b9c7becf9b504724a06ec036fd82 5172 
mysql-connector-python_8.0.14-1.debian.tar.xz
 c0851d2fb1d33a62746e13a754917403fbee67b2 9267 
mysql-connector-python_8.0.14-1_amd64.buildinfo
 2af93ab1dcad31e132c3b75a9269fe90a9063e27 167512 
python-mysql.connector_8.0.14-1_all.deb
 6e8245f136fc2cd04ac21d68d992cb3dda75b808 167660 
python3-mysql.connector_8.0.14-1_all.deb
Checksums-Sha256:
 7516bb41696e491c4dd20114f4f755feb4aa7278654b891a1a74ffac4e5ed380 2347 
mysql-connector-python_8.0.14-1.dsc
 ebe252ec11aa9b9c5cbeeecac760f1bc13308c8a4904782caa8a485fd01be8b1 12000443 
mysql-connector-python_8.0.14.orig.tar.gz
 

Bug#797931: marked as done (elinks: Does not support SSL rehandshakes)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#797931: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #797931,
regarding elinks: Does not support SSL rehandshakes
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.)


-- 
797931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elinks
Version: 0.12~pre6-10
Severity: normal

Hi!

I've been playing a bit with the new Debian SSO setup, and when trying
elinks, it could not even connect to the sites before authenticating:

  
  
  
  

It gives the following error message:

,---
  Unable to retrieve https://tracker.debian.org/:

  Resource temporarily unavailable
`---

When tracking this down, it appears one of the problems is due to not
handling SSL rehandshakes at all. When trying to fix that with the
attached patch, it started complaining about being unable to rehandshake
with:

,---
elinks: SSL rehandshake error: No or insufficient priorities were set.
`---

And, here I've run out of time. Hope at least this serves as a
starting point for someone else.

Thanks,
Guillem
diff --git a/src/network/ssl/socket.c b/src/network/ssl/socket.c
index 2ecdd71..f763ebd 100644
--- a/src/network/ssl/socket.c
+++ b/src/network/ssl/socket.c
@@ -246,8 +246,18 @@ ssl_read(struct socket *socket, unsigned char *data, int len)
 #endif
 
 #ifdef CONFIG_GNUTLS
-		if (err == GNUTLS_E_REHANDSHAKE)
-			return -1;
+		if (err == GNUTLS_E_REHANDSHAKE) {
+			err = gnutls_handshake(socket->ssl);
+			if (err < 0) {
+fprintf(stderr, "elinks: SSL rehandshake error: %s\n", gnutls_strerror(err));
+errno = S_SSL_ERROR;
+return SOCKET_INTERNAL_ERROR;
+			}
+			rd = gnutls_record_recv(socket->ssl, data, len);
+			if (rd > 0)
+return rd;
+			err = rd;
+		}
 #endif
 
 		if (err == SSL_ERROR_WANT_READ ||
--- End Message ---
--- Begin Message ---
Source: elinks
Source-Version: 0.13~20190125-1

We believe that the bug you reported is fixed in the latest version of
elinks, 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 797...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated elinks 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: Sat, 26 Jan 2019 02:53:52 +0100
Source: elinks
Architecture: source
Version: 0.13~20190125-1
Distribution: experimental
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 740981 757631 797931 797934 797968 856852 866015 891575 917406
Changes:
 elinks (0.13~20190125-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #891575, #797931, #797934, #757631,
 #866015, #797968, #740981, #856852)
   * Add git-buildpackage conf file
   * Refreshed patches & removed patches that were includes upstream.
 Removed patches:
 08-drop-deprecated-gnutls-functions.diff
 08_524696_fix_imdb_urls.diff
 09-Switch-to-use-lua-5.1.diff
 11-fix-compat-with-gnutls36.patch
   * Add libgcrypt20-dev to build deps
   * Re-added 14_debug_disable_Werror.diff to enable development versions debug
 support
   * Added 16_POST_BUFFER_SIZE.diff patch which to enable  uploading large files
 over https:// connections.
   * Add ascii-replacement-utf8-console.diff patch to print ASCII replacement
 for characters not found in current codepage in utf8 mode
   * Enable LZMA support
   * Enable BitTorrent
   * Enable NNTP Support
   * Enable Unicode combining characters support
   * Enable EX mode support
   * Enable SpiderMonkey support
   * Enable terminfo support
   * Build documentation
   * Build with libev
   * Bumped to compat level 12.
 No need to have dh-autoreconf, autotools-dev from build deps
 Also no need to explicitly call the respective sequences in rules
   * Remove old upstream gpg key.
   * Remove whitespaces
   * Renamed elinks.config to elinks.conf, old name confused build 

Bug#797968: marked as done (elinks: Please add support for TLS SNI)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#797968: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #797968,
regarding elinks: Please add support for TLS SNI
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.)


-- 
797968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elinks
Version: 0.12~pre6-10
Severity: wishlist
Tags: patch

Hi!

Here's a patch implementing TLS SNI support.

Thanks,
Guillem
From d0443df4b849b951ca0e51d0f651bc8ef780c384 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Fri, 4 Sep 2015 04:16:11 +0200
Subject: [PATCH] Add support for TLS SNI

Set the server name to the URI HTTP host name.
---
 src/network/socket.c  | 5 +
 src/network/socket.h  | 3 +++
 src/network/ssl/ssl.c | 9 +
 3 files changed, 13 insertions(+), 4 deletions(-)

diff --git a/src/network/socket.c b/src/network/socket.c
index e0f6b40..9166943 100644
--- a/src/network/socket.c
+++ b/src/network/socket.c
@@ -445,6 +445,11 @@ check_if_local_address4(struct sockaddr_in *addr)
 	return local;
 }
 
+const unsigned char *
+get_socket_host_name(struct socket *socket)
+{
+	return get_uri_string(socket->connect_info->uri, URI_HTTP_HOST);
+}
 
 void
 complete_connect_socket(struct socket *socket, struct uri *uri,
diff --git a/src/network/socket.h b/src/network/socket.h
index 0f085a6..85260f6 100644
--- a/src/network/socket.h
+++ b/src/network/socket.h
@@ -121,6 +121,9 @@ void timeout_socket(struct socket *socket);
 
 /* Connection establishing: */
 
+/* Return the socket connection HTTP host name. */
+const unsigned char *get_socket_host_name(struct socket *socket);
+
 /* End successful connect() attempt to socket. */
 void complete_connect_socket(struct socket *socket, struct uri *uri,
 			 socket_connect_T done);
diff --git a/src/network/ssl/ssl.c b/src/network/ssl/ssl.c
index 363245d..80640f8 100644
--- a/src/network/ssl/ssl.c
+++ b/src/network/ssl/ssl.c
@@ -230,7 +230,7 @@ init_ssl_connection(struct socket *socket)
 	socket->ssl = SSL_new(context);
 	if (!socket->ssl) return S_SSL_ERROR;
 #elif defined(CONFIG_GNUTLS)
-	/* const unsigned char server_name[] = "localhost"; */
+	const unsigned char *server_name = get_socket_host_name(socket);
 	ssl_t *state = mem_alloc(sizeof(ssl_t));
 
 	if (!state) return S_SSL_ERROR;
@@ -241,6 +241,9 @@ init_ssl_connection(struct socket *socket)
 		return S_SSL_ERROR;
 	}
 
+	gnutls_server_name_set(*state, GNUTLS_NAME_DNS, server_name,
+	   strlen(server_name));
+
 	if (gnutls_cred_set(*state, GNUTLS_CRD_ANON, anon_cred) < 0) {
 		/* DBG("sslanoncred %s", gnutls_strerror(ret)); */
 		gnutls_deinit(*state);
@@ -269,9 +272,7 @@ init_ssl_connection(struct socket *socket)
 	/* gnutls_handshake_set_private_extensions(*state, 1); */
 	gnutls_cipher_set_priority(*state, cipher_priority);
 	gnutls_kx_set_priority(*state, kx_priority);
-	/* gnutls_certificate_type_set_priority(*state, cert_type_priority);
-	gnutls_server_name_set(*state, GNUTLS_NAME_DNS, server_name,
-			   sizeof(server_name) - 1); */
+	/* gnutls_certificate_type_set_priority(*state, cert_type_priority); */
 #endif
 
 	socket->ssl = state;
-- 
2.5.1

--- End Message ---
--- Begin Message ---
Source: elinks
Source-Version: 0.13~20190125-1

We believe that the bug you reported is fixed in the latest version of
elinks, 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 797...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated elinks 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: Sat, 26 Jan 2019 02:53:52 +0100
Source: elinks
Architecture: source
Version: 0.13~20190125-1
Distribution: experimental
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 740981 757631 797931 797934 797968 856852 866015 891575 917406
Changes:
 elinks (0.13~20190125-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #891575, #797931, #797934, #757631,
 

Bug#757631: marked as done (elinks: HTML5 source element display missing)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#757631: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #757631,
regarding elinks: HTML5 source element display missing
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.)


-- 
757631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elinks
Version: 0.12~pre6-4
Severity: normal
Tags: patch

Dear Maintainer,

HTML5 has a source element, to provide content for audio and video elements.

Elinks currently ignores it. With my patch though, it looks nice, like this:


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages elinks depends on:
ii  elinks-data   0.12~pre6-4
ii  libbz2-1.01.0.6-5
ii  libc6 2.18-5
ii  libcomerr21.42.9-3
ii  libexpat1 2.1.0-4
ii  libfsplib00.11-2
ii  libgnutls26   2.12.23-15
ii  libgpm2   1.20.4-6.1
ii  libgssapi-krb5-2  1.12.1+dfsg-1
ii  libidn11  1.28-2
ii  libk5crypto3  1.12.1+dfsg-1
ii  libkrb5-3 1.12.1+dfsg-1
ii  libperl5.18   5.18.2-3
ii  libtre5   0.8.0-4
ii  zlib1g1:1.2.8.dfsg-1

elinks recommends no packages.

Versions of packages elinks suggests:
pn  elinks-doc  

-- no debconf information
>From 028caca7954e58ea6d15e0f27a6bace73f6f03f0 Mon Sep 17 00:00:00 2001
From: Nils Dagsson Moskopp 
Date: Sun, 10 Aug 2014 02:10:16 +0200
Subject: [PATCH] + rendering for html source element

---
 src/document/html/parser/link.c  | 31 +++
 src/document/html/parser/link.h  |  1 +
 src/document/html/parser/parse.c |  1 +
 3 files changed, 33 insertions(+)

diff --git a/src/document/html/parser/link.c b/src/document/html/parser/link.c
index b1816cd..4ecc426 100644
--- a/src/document/html/parser/link.c
+++ b/src/document/html/parser/link.c
@@ -356,6 +356,37 @@ html_img(struct html_context *html_context, unsigned char *a,
 	html_img_do(a, NULL, html_context);
 }
 
+void
+html_source(struct html_context *html_context, unsigned char *a,
+   unsigned char *xxx3, unsigned char *xxx4, unsigned char **xxx5)
+{
+	unsigned char *src, *title;
+	struct document_options *options = html_context->options;
+	int display_style = options->image_link.display_style;
+
+	src = get_url_val(a, "src", html_context->doc_cp);
+	if (!src) return;
+
+	title = get_attr_val(a, "title", html_context->doc_cp);
+	if (!title || !*title) {
+		if (display_style == 3)
+			title = get_image_filename_from_src(options->image_link.filename_maxlen, src);
+	}
+
+	html_focusable(html_context, a);
+
+	if (title && *title) {
+		put_link_line("Source: ", title, src,
+			  html_context->options->framename, html_context);
+	} else {
+		put_link_line("", "Source", src,
+			  html_context->options->framename, html_context);
+	}
+
+	mem_free_if(title);
+	mem_free(src);
+}
+
 /* prefix can have entities in it, but linkname cannot.  */
 void
 put_link_line(unsigned char *prefix, unsigned char *linkname,
diff --git a/src/document/html/parser/link.h b/src/document/html/parser/link.h
index 5b4d720..4f9990c 100644
--- a/src/document/html/parser/link.h
+++ b/src/document/html/parser/link.h
@@ -14,6 +14,7 @@ element_handler_T html_iframe;
 element_handler_T html_img;
 element_handler_T html_link;
 element_handler_T html_object;
+element_handler_T html_source;
 element_handler_T html_embed;
 
 #endif
diff --git a/src/document/html/parser/parse.c b/src/document/html/parser/parse.c
index 87d3b59..d461f4c 100644
--- a/src/document/html/parser/parse.c
+++ b/src/document/html/parser/parse.c
@@ -479,6 +479,7 @@ static struct element_info elements[] = {
  {"S",   html_underline,   NULL, 0, ET_NESTABLE},
  {"SCRIPT",  html_script,  NULL, 0, ET_NESTABLE},
  {"SELECT",  html_select,  NULL, 0, ET_NESTABLE},
+ {"SOURCE",  html_source,  NULL, 1, ET_NON_PAIRABLE},
  {"SPAN",html_span,NULL, 0, ET_NESTABLE},
  {"STRIKE",  html_underline,   NULL, 0, ET_NESTABLE},
  {"STRONG",  html_bold,NULL, 0, ET_NESTABLE

Bug#856852: marked as done (cert_verify is disabled by default)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#856852: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #856852,
regarding cert_verify is disabled by default
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.)


-- 
856852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elinks
Version: 0.12~pre6-12
Tags: elinks, browser, ssl, certificate, verification

Certificate verification is disabled by default.

To protect users again malicious websites using fake certificates,
certificate verification has to be enabled by default.

This issue can be spotted when opening elinks and navigating through
Menu -> Setup -> Option Manager -> Connections -> SSL -> Verify
Certificates. Click 'Info' button to find the default value of the
option (cert_verify), which is zero (disabled).

Tested on Debian Stretch, with latest today's updates.
--- End Message ---
--- Begin Message ---
Source: elinks
Source-Version: 0.13~20190125-1

We believe that the bug you reported is fixed in the latest version of
elinks, 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 856...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated elinks 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: Sat, 26 Jan 2019 02:53:52 +0100
Source: elinks
Architecture: source
Version: 0.13~20190125-1
Distribution: experimental
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 740981 757631 797931 797934 797968 856852 866015 891575 917406
Changes:
 elinks (0.13~20190125-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #891575, #797931, #797934, #757631,
 #866015, #797968, #740981, #856852)
   * Add git-buildpackage conf file
   * Refreshed patches & removed patches that were includes upstream.
 Removed patches:
 08-drop-deprecated-gnutls-functions.diff
 08_524696_fix_imdb_urls.diff
 09-Switch-to-use-lua-5.1.diff
 11-fix-compat-with-gnutls36.patch
   * Add libgcrypt20-dev to build deps
   * Re-added 14_debug_disable_Werror.diff to enable development versions debug
 support
   * Added 16_POST_BUFFER_SIZE.diff patch which to enable  uploading large files
 over https:// connections.
   * Add ascii-replacement-utf8-console.diff patch to print ASCII replacement
 for characters not found in current codepage in utf8 mode
   * Enable LZMA support
   * Enable BitTorrent
   * Enable NNTP Support
   * Enable Unicode combining characters support
   * Enable EX mode support
   * Enable SpiderMonkey support
   * Enable terminfo support
   * Build documentation
   * Build with libev
   * Bumped to compat level 12.
 No need to have dh-autoreconf, autotools-dev from build deps
 Also no need to explicitly call the respective sequences in rules
   * Remove old upstream gpg key.
   * Remove whitespaces
   * Renamed elinks.config to elinks.conf, old name confused build scrips
   * debian/rules: Override dh_installexamples to exclude .gitignore
   * Add typos.diff patch to fix spelling mistakes
   * debian/control:
 + Replace Conflicts with Breaks+Replaces
 + Update standards version to 4.3.0
 + New maintainer (Closes: #917406)
 + Add Vcs-* fields
   * Add upstream metadata
   * Switch to DEP-5 copyright format
   * Disable pristine-tar, since we are getting the release from upstream git
Checksums-Sha1:
 31dfa7b9392b6a51c14f3aac843f424faaa1818a 2340 elinks_0.13~20190125-1.dsc
 8ce05dc4aa86056e00ad4b4c8900b88966e02b82 1768440 
elinks_0.13~20190125.orig.tar.xz
 9e424e8b0e8954ef768fe4025f62e2e09375e0e3 23044 
elinks_0.13~20190125-1.debian.tar.xz
 9216b6f327a31103886df8add7071e19fc1c3727 6496 
elinks_0.13~20190125-1_source.buildinfo
Checksums-Sha256:
 fedc16fc62d261f0767562a4a48045e684015ea82053956c2df6b86d919bf8ac 2340 
elinks_0.13~20190125-1.dsc
 18d7f5bc46664d8cc131f2c57545d2668277515eb6ccc677d3580e1fcd18efa9 1768440 
elinks_0.13~20190125.orig.tar.xz
 

Bug#740981: marked as done (elinks: doesn't check if hostname matches certificate's CN/SAN (CWE-297))

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:46:06 +
with message-id 
and subject line Bug#740981: fixed in elinks 0.13~20190125-1
has caused the Debian Bug report #740981,
regarding elinks: doesn't check if hostname matches certificate's CN/SAN 
(CWE-297)
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.)


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

Package: elinks
Version: 0.12~pre6-4
Tags: security

elinks doesn't verify that the server hostname matches a domain name in 
the subject's Common Name or subjectAltName field of the certificate.


Steps to reproduce:

1) Add fake host to /etc/hosts:
5.153.231.4 www.debian.moo

2) Enable certificate validation:
Setup > Options manager > Connections > SSL > Verify certificates

3) Visit https://www.debian.moo/. The browser happily displays the page, 
even though the certificate is valid only for "debian.org" and 
"www.debian.org" domains.



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

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages elinks depends on:
ii  elinks-data   0.12~pre6-4
ii  libbz2-1.01.0.6-5
ii  libc6 2.18-4
ii  libcomerr21.42.9-3
ii  libexpat1 2.1.0-4
ii  libfsplib00.11-2
ii  libgnutls26   2.12.23-13
ii  libgpm2   1.20.4-6.1
ii  libgssapi-krb5-2  1.12+dfsg-2
ii  libidn11  1.28-1
ii  libk5crypto3  1.12+dfsg-2
ii  libkrb5-3 1.12+dfsg-2
ii  libperl5.18   5.18.2-2+b1
ii  libtre5   0.8.0-3
ii  zlib1g1:1.2.8.dfsg-1

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: elinks
Source-Version: 0.13~20190125-1

We believe that the bug you reported is fixed in the latest version of
elinks, 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 740...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated elinks 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: Sat, 26 Jan 2019 02:53:52 +0100
Source: elinks
Architecture: source
Version: 0.13~20190125-1
Distribution: experimental
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Closes: 740981 757631 797931 797934 797968 856852 866015 891575 917406
Changes:
 elinks (0.13~20190125-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #891575, #797931, #797934, #757631,
 #866015, #797968, #740981, #856852)
   * Add git-buildpackage conf file
   * Refreshed patches & removed patches that were includes upstream.
 Removed patches:
 08-drop-deprecated-gnutls-functions.diff
 08_524696_fix_imdb_urls.diff
 09-Switch-to-use-lua-5.1.diff
 11-fix-compat-with-gnutls36.patch
   * Add libgcrypt20-dev to build deps
   * Re-added 14_debug_disable_Werror.diff to enable development versions debug
 support
   * Added 16_POST_BUFFER_SIZE.diff patch which to enable  uploading large files
 over https:// connections.
   * Add ascii-replacement-utf8-console.diff patch to print ASCII replacement
 for characters not found in current codepage in utf8 mode
   * Enable LZMA support
   * Enable BitTorrent
   * Enable NNTP Support
   * Enable Unicode combining characters support
   * Enable EX mode support
   * Enable SpiderMonkey support
   * Enable terminfo support
   * Build documentation
   * Build with libev
   * Bumped to compat level 12.
 No need to have dh-autoreconf, autotools-dev from build deps
 Also no need to explicitly call the respective sequences in rules
   * Remove old upstream gpg key.
   * Remove whitespaces
   * Renamed elinks.config to elinks.conf, old name confused build scrips
   * debian/rules: Override dh_installexamples to exclude .gitignore
   * Add typos.diff patch to fix spelling mistakes
   * debian/control:
 + 

Bug#913548: marked as done (spamassassin: running /etc/cron.daily/spamassassin gives: Unescaped left brace in regex is deprecated here)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 15:33:30 +1300
with message-id <87bm41se85@silverfish.pri>
and subject line Re: Bug#913548: spamassassin: running 
/etc/cron.daily/spamassassin gives: Unescaped left brace in regex is deprecated 
here
has caused the Debian Bug report #913548,
regarding spamassassin: running /etc/cron.daily/spamassassin gives: Unescaped 
left brace in regex is deprecated here
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.)


-- 
913548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spamassassin
Version: 3.4.2-1
Severity: important

Hi,

running /etc/cron.daily/spamassassin gives:
Unescaped left brace in regex is deprecated here (and will be fatal in Perl 
5.32), passed through in regex; marked by <-- HERE in m/ ( {<-- HERE } (?: / \* 
)? | \* ) / at (eval 109) line 830.


-- 
   Elimar

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

Kernel: Linux 4.14.71-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages spamassassin depends on:
ii  adduser 3.118
ii  curl7.62.0-1
ii  init-system-helpers 1.55
ii  libhtml-parser-perl 3.72-3+b3
ii  libhttp-date-perl   6.02-1
ii  libmail-dkim-perl   0.53-1
ii  libnet-dns-perl 1.17-1
ii  libnetaddr-ip-perl  4.079+dfsg-1+b3
ii  libsocket6-perl 0.29-1+b1
ii  libsys-hostname-long-perl   1.5-1
ii  libwww-perl 6.36-1
ii  lsb-base9.20170808
ii  perl [libarchive-tar-perl]  5.28.0-3
ii  w3m 0.5.3-36+b1

Versions of packages spamassassin recommends:
ii  gnupg  2.2.10-3
ii  libio-socket-inet6-perl2.72-2
ii  libmail-spf-perl   2.9.0-4
ii  perl [libsys-syslog-perl]  5.28.0-3
pn  sa-compile 
ii  spamc  3.4.2-1

Versions of packages spamassassin suggests:
ii  libdbi-perl   1.642-1+b1
pn  libencode-detect-perl 
pn  libgeo-ip-perl
ii  libio-socket-ssl-perl 2.060-3
pn  libnet-patricia-perl  
ii  perl [libcompress-zlib-perl]  5.28.0-3
ii  pyzor 1:1.0.0-3
ii  razor 1:2.85-4.2+b5

-- Configuration Files:
/etc/default/spamassassin changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:2.11.0-4

This should be fixed now.

Thanks
-- 
Brian May --- End Message ---


Bug#919637: marked as done (RFS: elinks/0.13~20190125-1 [ITA])

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 03:05:51 +0100
with message-id <20190128020551.4vuxh33trtc72...@angband.pl>
and subject line Re: Bug#919637: RFS: elinks/0.13~20190114-1 [ITA]
has caused the Debian Bug report #919637,
regarding RFS: elinks/0.13~20190125-1 [ITA]
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.)


-- 
919637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Hello,

 I am adopting elinks. I have worked on the fork that Moritz has 
 mentioned: https://github.com/rkd77/felinks
 I have emailed previous upstream maintainers,asking them if they are 
 still maintaining elinks. Two emails bounced back, and I still got no 
 reply from the others.
 Anyways, this upload is targetting experimental, as I have enabled 
 several features like Bittorrent and Javascript.

This upload fixes the following bugs
#740981 (normal): elinks: doesn't check if hostname matches certificate's 
CN/SAN (CWE-297)
#757631 (normal): elinks: HTML5 source element display missing
#797931 (normal): elinks: Does not support SSL rehandshakes
#797934 (wishlist): elinks: Support for SSL authentication using client certs
#797968 (wishlist): elinks: Please add support for TLS SNI
#856852 (normal): cert_verify is disabled by default
#866015 (important): elinks: SSL error with some websites
#879539 (minor): elinks: contains code related to gnutls pgp supprt
#891575 (important): elinks: CVE-2012-6709
#917406 (normal): ITA: elinks -- advanced text-mode WWW browser

Last changelog entry is:
elinks (0.13~20190114-1) experimental; urgency=medium

  * New upstream release (Closes: #891575, #797931, #797934, #757631,
#866015, #797968, #740981, #865852)
  * Add git-buildpackage conf file
  * Refreshed patches & removed patches that were includes upstream.
Removed patches:
08-drop-deprecated-gnutls-functions.diff (Closes: #879539)
08_524696_fix_imdb_urls.diff
09-Switch-to-use-lua-5.1.diff
  * Add libgcrypt20-dev to build deps
  * Re-added 14_debug_disable_Werror.diff to enable development versions debug
support
  * Added 16_POST_BUFFER_SIZE.diff patch which to enable  uploading large files
over https:// connections.
  * Add ascii-replacement-utf8-console.diff patch to print ASCII replacement
for characters not found in current codepage in utf8 mode
  * Enable LZMA support
  * Enable BitTorrent
  * Enable NNTP Support
  * Enable Unicode combining characters support
  * Enable EX mode support
  * Enable SpiderMonkey support
  * Enable terminfo support
  * Build documentation
  * Build with libev
  * Bumped to compat level 12.
No need to have dh-autoreconf, autotools-dev from build deps
Also no need to explicitly call the respective sequences in rules
  * Remove old upstream gpg key.
  * Remove whitespaces
  * Renamed elinks.config to elinks.conf, old name confused build scrips
  * debian/rules: Override dh_installexamples to exclude .gitignore
  * Add typos.diff patch to fix spelling mistakes
  * debian/control:
+ Replace Conflicts with Breaks+Replaces
+ Update standards version to 4.3.0
+ New maintainer (Closes: #917406)
+ Add Vcs-* fields
  * Add upstream metadata
  * Switch to DEP-5 copyright format
  * Disable pristine-tar, since we are getting the release from upstream git


There is one lintian warning:
W: elinks-data: manpage-has-errors-from-man usr/share/man/man5/elinks.conf.5.gz 
1166: warning [p 14, 7.0i]: can't break line

The package is on: g...@salsa.debian.org:aelmahmoudy-guest/elinks.git , 
felinks branch

To access further information about this package, please visit the following 
URL:
https://mentors.debian.net/package/elinks

Alternatively, one can download the package with dget using this command:
  dget -x 
https://mentors.debian.net/debian/pool/main/e/elinks/elinks_0.13~20190114-1.dsc

-- 
‎أحمد المحمودي (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: PGP signature
--- End Message ---
--- Begin Message ---
On Sat, Jan 26, 2019 at 04:29:26AM +0100, أحمد المحمودي wrote:
> On Mon, Jan 21, 2019 at 03:37:24PM +0100, Adam Borowski wrote:
> > Alas, it still FTBFSes:
> > /<>/doc/manual.xml:3993: element link: validity error : IDREF 
> > attribute linkend references an unknown ID "CONFIG-SCRIPTING-SPIDERMONKEY"

> Fixed upstream. I have re-uploaded to mentors.

✓

-- 

Bug#919950: marked as done (Please drop compatibility hack for liblzma.so.2 (last present in squeeze))

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 01:52:05 +
with message-id 
and subject line Bug#919950: fixed in xz-utils 5.2.4-1
has caused the Debian Bug report #919950,
regarding Please drop compatibility hack for liblzma.so.2 (last present in 
squeeze)
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.)


-- 
919950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblzma5
Version: 5.2.2-1.3
Severity: normal

liblzma5 currently contains a compatibility hack for liblzma.so.2, which
is the only thing pulling libdl into liblzma. liblzma.so.2 hasn't been
in Debian since Squeeze, released in 2011; wheezy, released in 2013, has
liblzma5. Please consider dropping the compatibility hack, which will
also mean liblzma will no longer pull in libdl.

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

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

Versions of packages liblzma5 depends on:
ii  libc6  2.28-5

liblzma5 recommends no packages.

liblzma5 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xz-utils
Source-Version: 5.2.4-1

We believe that the bug you reported is fixed in the latest version of
xz-utils, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated xz-utils 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: Sun, 27 Jan 2019 17:09:34 -0800
Source: xz-utils
Binary: liblzma-dev liblzma-doc liblzma5 liblzma5-dbgsym xz-utils 
xz-utils-dbgsym xzdec xzdec-dbgsym
Architecture: source amd64 all
Version: 5.2.4-1
Distribution: unstable
Urgency: low
Maintainer: Jonathan Nieder 
Changed-By: Jonathan Nieder 
Description:
 liblzma-dev - XZ-format compression library - development files
 liblzma-doc - XZ-format compression library - API documentation
 liblzma5   - XZ-format compression library
 xz-utils   - XZ-format compression utilities
 xzdec  - XZ-format compression utilities - tiny decompressors
Closes: 685203 826382 851615 919950
Changes:
 xz-utils (5.2.4-1) unstable; urgency=low
 .
   * New upstream release.  Closes: #851615.
   * Standards-Version: 4.3.0 (checked).
   * Use an XZ compressed tarball for upstream source.
   * Add upstream signing key and verify tarball at "uscan" time.
   * Drop patches; all were applied or otherwise fixed upstream.
   * Update copyright file.
   * debian/control:
 - Use a stable repo.or.cz URL for packaging repo.
   Closes: #826382.  Thanks to Rolf Leggewie.
 - Use https for upstream homepage URL.
 - No longer Build-Depends: freebsd-glue on kfreebsd.
   * get-orig-source: Use https for upstream Git repository.
   * liblzma:
 - Remove compatibility tricks that permit sharing a process with
   liblzma.so.2.  This means liblzma.a no longer depends on libdl
   at run time.
   Closes: #919950.  Thanks to Josh Triplett.
 - Breaks: liblzma2 versions without symbol versioning.
 - Priority: optional.
   * xz-utils:
 - Lower priority of xz-utils to standard.  Closes: #685203.
 - README.Debian: Remove notes about differences from upstream.
 - Remove old NEWS.Debian.
Checksums-Sha1:
 a98271e4291bed8df795ce04d9dc8e4ce959462d 2518 xz-utils_5.2.4-1.dsc
 1d3a6910c28d40df0134f4a49e5570e8249120c5 1053868 xz-utils_5.2.4.orig.tar.xz
 59ccbfb2405abe510999afef4b374cad30c09275 879 xz-utils_5.2.4.orig.tar.xz.asc
 667c14fd9409ca54c397b07d2d70140d6297393f 135296 xz-utils_5.2.4-1.debian.tar.xz
 79df1077e27a9f9b43e8d139386cff5182265ec5 210268 liblzma-dev_5.2.4-1_amd64.deb
 6a3525c688a02eecfbdc3df7373be6a2ea72c587 353676 liblzma-doc_5.2.4-1_all.deb
 23df406b535fe7b98a41f9997108f27675a732e8 239804 
liblzma5-dbgsym_5.2.4-1_amd64.deb
 17621fc94a3ca08e4ff5e6df4b3e7639b5e47c82 152504 

Bug#920444: marked as done (RFS: zapping/0.10~cvs6-16 [QA] [RC])

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:51:30 +0100
with message-id <20190128015130.4niqierq6uqgp...@angband.pl>
and subject line Re: Bug#920444: RFS: zapping/0.10~cvs6-16 [QA] [RC]
has caused the Debian Bug report #920444,
regarding RFS: zapping/0.10~cvs6-16 [QA] [RC]
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.)


-- 
920444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for a QA upload of the package "zapping".

 * Package name: zapping
   Version : 0.10~cvs6-16
   Upstream Author : Iñaki García Etxebarria 
 Michael H. Schimek 
 * URL : http://zapping.sourceforge.net/
 * License : GPL-2
   Section : gnome

It builds this binary package:

zapping- television viewer for the GNOME environment

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/z/zapping/zapping_0.10~cvs6-16.dsc

Or use the Git repository at:

  https://salsa.debian.org/debian/zapping

Changes since the last upload:

  * QA upload.
  * debian/patches/24-GConf-to-GSettings.patch: Assign each GSettings
instance to its own unique variable; otherwise things get really messy
when plugins are loaded (Closes: #919473).
  * debian/patches/27-zsfb-manpage.patch: New; build and install
zapping_setup_fb's manpage conditionally based on the same
AM_CONDITIONAL that is used for the binary.
  * debian/patches/series: Update.
  * debian/rules: Pass --disable-v4l --disable-bktr on GNU/Hurd; remove
hurd-specific CPPFLAGS.
(override_dh_auto_install): Conditionally move zapping_setup_fb to
/usr/bin as it's only built on GNU/Linux architectures.
  * debian/control (Build-Depends): Remove freebsd-glue; that was a really
stupid idea that I should be ashamed of.  And I am.
(Depends): Add gsettings-desktop-schemas -- the code loads one schema
from this package which will be a hard error if it is not installed.
(Standards-Version): Bump to 4.3.0; no changes needed.
  * debian/copyright: Update copyright years, add Jeremy Bicha.
--- End Message ---
--- Begin Message ---
On Fri, Jan 25, 2019 at 05:23:36PM +0200, Yavor Doganov wrote:
>  * Package name: zapping
>Version : 0.10~cvs6-16

> Changes since the last upload:
> 
>   * QA upload.
>   * debian/patches/24-GConf-to-GSettings.patch: Assign each GSettings
> instance to its own unique variable; otherwise things get really messy
> when plugins are loaded (Closes: #919473).
>   * debian/patches/27-zsfb-manpage.patch: New; build and install
> zapping_setup_fb's manpage conditionally based on the same
> AM_CONDITIONAL that is used for the binary.
>   * debian/patches/series: Update.
>   * debian/rules: Pass --disable-v4l --disable-bktr on GNU/Hurd; remove
> hurd-specific CPPFLAGS.
> (override_dh_auto_install): Conditionally move zapping_setup_fb to
> /usr/bin as it's only built on GNU/Linux architectures.
>   * debian/control (Build-Depends): Remove freebsd-glue; that was a really
> stupid idea that I should be ashamed of.  And I am.
> (Depends): Add gsettings-desktop-schemas -- the code loads one schema
> from this package which will be a hard error if it is not installed.
> (Standards-Version): Bump to 4.3.0; no changes needed.
>   * debian/copyright: Update copyright years, add Jeremy Bicha.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄--- End Message ---


Bug#685203: marked as done (xz-utils is "Priority: required" but not pseudo-essential)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 01:52:05 +
with message-id 
and subject line Bug#685203: fixed in xz-utils 5.2.4-1
has caused the Debian Bug report #685203,
regarding xz-utils is "Priority: required" but not pseudo-essential
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.)


-- 
685203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xz-utils
Version: 5.1.1alpha+20120614-1
Severity: minor
Justification: policy §2.5
Tags: patch

Hi,

xz-utils has "Priority: required" but no pseudo-essential package
depends on it:

$ grep-dctrl -sPackage -Fpriority required \
  -a -FDepends,Pre-Depends 'xz-utils' \
  http://bugs.debian.org/452393
[2] http://thread.gmane.org/gmane.linux.debian.devel.release/55821
From: Jonathan Nieder 
Date: Sat, 23 Jun 2012 17:44:04 -0500
Subject: debian/control: xz-utils is not pseudo-essential any more

Since dpkg 1.16.4~6 (libdpkg: Add liblzma compression support,
2012-06-07), the xz command is no longer needed in a minimal Debian
system.

Based on its list of reverse-dependencies, it is even safe to lower
the priority to optional.  Let's make it "standard", since it is not
part of the traditional Unix toolset but is a useful component even in
reasonably small character-mode systems.
---
 debian/changelog |1 +
 debian/control   |1 +
 2 files changed, 2 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index a69f889..56563e1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,6 @@
 xz-utils (5.1.1alpha+20120614-1.1) unstable; urgency=low
 
+  * Lower priority of xz-utils to standard.
   * xz-utils/README.Debian: Document differences from upstream.
 
  -- Jonathan Nieder   Fri, 17 Aug 2012 19:57:24 -0700
diff --git a/debian/control b/debian/control
index 986f0c1..281931e 100644
--- a/debian/control
+++ b/debian/control
@@ -29,6 +29,7 @@ Description: XZ-format compression library
  format, use the p7zip package instead.)
 
 Package: xz-utils
+Priority: standard
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Multi-Arch: foreign
-- 
1.7.9.6 (Apple Git-31.1)

--- End Message ---
--- Begin Message ---
Source: xz-utils
Source-Version: 5.2.4-1

We believe that the bug you reported is fixed in the latest version of
xz-utils, 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 685...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated xz-utils 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: Sun, 27 Jan 2019 17:09:34 -0800
Source: xz-utils
Binary: liblzma-dev liblzma-doc liblzma5 liblzma5-dbgsym xz-utils 
xz-utils-dbgsym xzdec xzdec-dbgsym
Architecture: source amd64 all
Version: 5.2.4-1
Distribution: unstable
Urgency: low
Maintainer: Jonathan Nieder 
Changed-By: Jonathan Nieder 
Description:
 liblzma-dev - XZ-format compression library - development files
 liblzma-doc - XZ-format compression library - API documentation
 liblzma5   - XZ-format compression library
 xz-utils   - XZ-format compression utilities
 xzdec  - XZ-format compression utilities - tiny decompressors
Closes: 685203 826382 851615 919950
Changes:
 xz-utils (5.2.4-1) unstable; urgency=low
 .
   * New upstream release.  Closes: #851615.
   * Standards-Version: 4.3.0 (checked).
   * Use an XZ compressed tarball for upstream source.
   * Add upstream signing key and verify tarball at "uscan" time.
   * Drop patches; all were applied or otherwise fixed upstream.
   * Update copyright file.
   * debian/control:
 - Use a stable repo.or.cz URL for packaging repo.
   Closes: #826382.  Thanks to Rolf Leggewie.
 - Use https for upstream homepage URL.
 - No longer Build-Depends: freebsd-glue on kfreebsd.
   * get-orig-source: Use https for upstream Git repository.
   * liblzma:
 - Remove compatibility tricks that permit sharing a process with
   liblzma.so.2.  This means liblzma.a no longer depends on libdl
   at run time.
   Closes: #919950.  Thanks to Josh Triplett.
 - Breaks: liblzma2 versions without symbol 

Bug#826382: marked as done (xz-utils: git packaging repo not updated)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 01:52:05 +
with message-id 
and subject line Bug#826382: fixed in xz-utils 5.2.4-1
has caused the Debian Bug report #826382,
regarding xz-utils: git packaging repo not updated
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.)


-- 
826382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xz-utils
Version: v4.999.9beta+20100527-1
Severity: normal

Dear Maintainer,

the git packaging repo hasn't been updated for quite a while. It
would be nice if you did so.

Regards

Rolf


PS: Even more important is to upload upstream 5.2.2 -> #731634
--- End Message ---
--- Begin Message ---
Source: xz-utils
Source-Version: 5.2.4-1

We believe that the bug you reported is fixed in the latest version of
xz-utils, 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 826...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated xz-utils 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: Sun, 27 Jan 2019 17:09:34 -0800
Source: xz-utils
Binary: liblzma-dev liblzma-doc liblzma5 liblzma5-dbgsym xz-utils 
xz-utils-dbgsym xzdec xzdec-dbgsym
Architecture: source amd64 all
Version: 5.2.4-1
Distribution: unstable
Urgency: low
Maintainer: Jonathan Nieder 
Changed-By: Jonathan Nieder 
Description:
 liblzma-dev - XZ-format compression library - development files
 liblzma-doc - XZ-format compression library - API documentation
 liblzma5   - XZ-format compression library
 xz-utils   - XZ-format compression utilities
 xzdec  - XZ-format compression utilities - tiny decompressors
Closes: 685203 826382 851615 919950
Changes:
 xz-utils (5.2.4-1) unstable; urgency=low
 .
   * New upstream release.  Closes: #851615.
   * Standards-Version: 4.3.0 (checked).
   * Use an XZ compressed tarball for upstream source.
   * Add upstream signing key and verify tarball at "uscan" time.
   * Drop patches; all were applied or otherwise fixed upstream.
   * Update copyright file.
   * debian/control:
 - Use a stable repo.or.cz URL for packaging repo.
   Closes: #826382.  Thanks to Rolf Leggewie.
 - Use https for upstream homepage URL.
 - No longer Build-Depends: freebsd-glue on kfreebsd.
   * get-orig-source: Use https for upstream Git repository.
   * liblzma:
 - Remove compatibility tricks that permit sharing a process with
   liblzma.so.2.  This means liblzma.a no longer depends on libdl
   at run time.
   Closes: #919950.  Thanks to Josh Triplett.
 - Breaks: liblzma2 versions without symbol versioning.
 - Priority: optional.
   * xz-utils:
 - Lower priority of xz-utils to standard.  Closes: #685203.
 - README.Debian: Remove notes about differences from upstream.
 - Remove old NEWS.Debian.
Checksums-Sha1:
 a98271e4291bed8df795ce04d9dc8e4ce959462d 2518 xz-utils_5.2.4-1.dsc
 1d3a6910c28d40df0134f4a49e5570e8249120c5 1053868 xz-utils_5.2.4.orig.tar.xz
 59ccbfb2405abe510999afef4b374cad30c09275 879 xz-utils_5.2.4.orig.tar.xz.asc
 667c14fd9409ca54c397b07d2d70140d6297393f 135296 xz-utils_5.2.4-1.debian.tar.xz
 79df1077e27a9f9b43e8d139386cff5182265ec5 210268 liblzma-dev_5.2.4-1_amd64.deb
 6a3525c688a02eecfbdc3df7373be6a2ea72c587 353676 liblzma-doc_5.2.4-1_all.deb
 23df406b535fe7b98a41f9997108f27675a732e8 239804 
liblzma5-dbgsym_5.2.4-1_amd64.deb
 17621fc94a3ca08e4ff5e6df4b3e7639b5e47c82 152504 liblzma5_5.2.4-1_amd64.deb
 04d00b3bd8bfbf63b188d5222b7c662aa5b0f627 94456 
xz-utils-dbgsym_5.2.4-1_amd64.deb
 6e2f6caa27609368d9e602a826c76c66bc59ad02 7382 xz-utils_5.2.4-1_amd64.buildinfo
 65ccb1d7b319e3f894a42afd9f4d7f7ea7766843 183060 xz-utils_5.2.4-1_amd64.deb
 28f7c021c587eafb486dbfa24a5c3597da9a224c 114948 xzdec-dbgsym_5.2.4-1_amd64.deb
 fedfd3a00a279b81106109b7b88a4596ebcd5c94 116652 xzdec_5.2.4-1_amd64.deb
Checksums-Sha256:
 b1572c4efb3c8ebf6f0e044b70e1e0451c919a99d3f80be03b624a54dd7ea593 2518 
xz-utils_5.2.4-1.dsc
 9717ae363760dedf573dad241420c5fea86256b65bc21d2cf71b2b12f0544f4b 1053868 
xz-utils_5.2.4.orig.tar.xz
 

Bug#851615: marked as done (xz-utils: please upgrade to 5.2.3)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 01:52:05 +
with message-id 
and subject line Bug#851615: fixed in xz-utils 5.2.4-1
has caused the Debian Bug report #851615,
regarding xz-utils: please upgrade to 5.2.3
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.)


-- 
851615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xz-utils
Version: 5.2.2-1.2
Severity: wishlist

Please upgrade to 5.2.3 for Stretch. One visible change is the usage of
sched_getaffinity() which is preferred over all online CPUs especially on
bigger NUMA boxes where affinity mask is often limited to a node.

Sebastian
--- End Message ---
--- Begin Message ---
Source: xz-utils
Source-Version: 5.2.4-1

We believe that the bug you reported is fixed in the latest version of
xz-utils, 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 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Nieder  (supplier of updated xz-utils 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: Sun, 27 Jan 2019 17:09:34 -0800
Source: xz-utils
Binary: liblzma-dev liblzma-doc liblzma5 liblzma5-dbgsym xz-utils 
xz-utils-dbgsym xzdec xzdec-dbgsym
Architecture: source amd64 all
Version: 5.2.4-1
Distribution: unstable
Urgency: low
Maintainer: Jonathan Nieder 
Changed-By: Jonathan Nieder 
Description:
 liblzma-dev - XZ-format compression library - development files
 liblzma-doc - XZ-format compression library - API documentation
 liblzma5   - XZ-format compression library
 xz-utils   - XZ-format compression utilities
 xzdec  - XZ-format compression utilities - tiny decompressors
Closes: 685203 826382 851615 919950
Changes:
 xz-utils (5.2.4-1) unstable; urgency=low
 .
   * New upstream release.  Closes: #851615.
   * Standards-Version: 4.3.0 (checked).
   * Use an XZ compressed tarball for upstream source.
   * Add upstream signing key and verify tarball at "uscan" time.
   * Drop patches; all were applied or otherwise fixed upstream.
   * Update copyright file.
   * debian/control:
 - Use a stable repo.or.cz URL for packaging repo.
   Closes: #826382.  Thanks to Rolf Leggewie.
 - Use https for upstream homepage URL.
 - No longer Build-Depends: freebsd-glue on kfreebsd.
   * get-orig-source: Use https for upstream Git repository.
   * liblzma:
 - Remove compatibility tricks that permit sharing a process with
   liblzma.so.2.  This means liblzma.a no longer depends on libdl
   at run time.
   Closes: #919950.  Thanks to Josh Triplett.
 - Breaks: liblzma2 versions without symbol versioning.
 - Priority: optional.
   * xz-utils:
 - Lower priority of xz-utils to standard.  Closes: #685203.
 - README.Debian: Remove notes about differences from upstream.
 - Remove old NEWS.Debian.
Checksums-Sha1:
 a98271e4291bed8df795ce04d9dc8e4ce959462d 2518 xz-utils_5.2.4-1.dsc
 1d3a6910c28d40df0134f4a49e5570e8249120c5 1053868 xz-utils_5.2.4.orig.tar.xz
 59ccbfb2405abe510999afef4b374cad30c09275 879 xz-utils_5.2.4.orig.tar.xz.asc
 667c14fd9409ca54c397b07d2d70140d6297393f 135296 xz-utils_5.2.4-1.debian.tar.xz
 79df1077e27a9f9b43e8d139386cff5182265ec5 210268 liblzma-dev_5.2.4-1_amd64.deb
 6a3525c688a02eecfbdc3df7373be6a2ea72c587 353676 liblzma-doc_5.2.4-1_all.deb
 23df406b535fe7b98a41f9997108f27675a732e8 239804 
liblzma5-dbgsym_5.2.4-1_amd64.deb
 17621fc94a3ca08e4ff5e6df4b3e7639b5e47c82 152504 liblzma5_5.2.4-1_amd64.deb
 04d00b3bd8bfbf63b188d5222b7c662aa5b0f627 94456 
xz-utils-dbgsym_5.2.4-1_amd64.deb
 6e2f6caa27609368d9e602a826c76c66bc59ad02 7382 xz-utils_5.2.4-1_amd64.buildinfo
 65ccb1d7b319e3f894a42afd9f4d7f7ea7766843 183060 xz-utils_5.2.4-1_amd64.deb
 28f7c021c587eafb486dbfa24a5c3597da9a224c 114948 xzdec-dbgsym_5.2.4-1_amd64.deb
 fedfd3a00a279b81106109b7b88a4596ebcd5c94 116652 xzdec_5.2.4-1_amd64.deb
Checksums-Sha256:
 b1572c4efb3c8ebf6f0e044b70e1e0451c919a99d3f80be03b624a54dd7ea593 2518 
xz-utils_5.2.4-1.dsc
 9717ae363760dedf573dad241420c5fea86256b65bc21d2cf71b2b12f0544f4b 1053868 
xz-utils_5.2.4.orig.tar.xz
 

Bug#920487: marked as done (RFS: wxmaxima/19.01.2-1)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:45:17 +0100
with message-id <20190128014517.fhgwpoasyhcbg...@angband.pl>
and subject line Re: Bug#920487: RFS: wxmaxima/19.01.2-1
has caused the Debian Bug report #920487,
regarding RFS: wxmaxima/19.01.2-1
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.)


-- 
920487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: wxmaxima
   Version : 19.01.2-1
   Upstream Author : Gunter Königsmann 
 * URL : http://wxmaxima-developers.github.io/wxmaxima/
 * License : GPL 2+
   Section : math

It builds those binary packages:

wxmaxima   - GUI for the computer algebra system Maxima

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/w/wxmaxima/wxmaxima_19.01.2-1.dsc

More information about wxmaxima can be obtained from https://www.example.com.

Changes since the last upload:

 * The newest upstream version which only contains bug fixes - but contains 
many bug fixes for the display code.


Regards,
   Gunter Königsmann

--- End Message ---
--- Begin Message ---
On Sat, Jan 26, 2019 at 07:48:14AM +0100, Gunter Königsmann wrote:
>  * Package name: wxmaxima
>Version : 19.01.2-1

> Changes since the last upload:
> 
>  * The newest upstream version which only contains bug fixes - but contains 
> many bug fixes for the display code.

+wxmaxima (19.01.2-1) unstable; urgency=medium
+
+  * A new upstream version that mainly corrects cell heights.
+  * Updated debian/compat and the respective dependency in debian/control
+  * Re-exported the signing key in order to silence a lintian warning
+ -- Gunter Königsmann   Tue, 13 Jan 2019 13:10:36 +0100

Jan 13 was a Sunday not Tuesday, our tools complain about this.  I've
changed the weekday, and uploaded.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄--- End Message ---


Bug#631768: marked as done (gnomint saved window size after using the quit button is out of range)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 01:34:17 +
with message-id 
and subject line Bug#631768: fixed in gnomint 1.3.0-1
has caused the Debian Bug report #631768,
regarding gnomint saved window size after using the quit button is out of range
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.)


-- 
631768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnomint
Version: 1.2.1-2
Severity: normal

The first time gnomint is used, all works as expected.

Then after using the "Quit" entry in the Certificates menu, and restarting,
a smallish (probably 320x320) window appears which expands to a size almost
filling the screen, which then crashes and dies with the error message


  The program 'gnomint' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 214 error_code 11 request_code 53 minor_code 0)

Investigation reveals that when using the Quit menu entry, gnomint
writes an entry to the ${HOME}.gconf/apps/gnomint/%gconf.xml
with a ridiculously large set of values for the window size.

  
  

(148488120,147732584)

  

Editing the values here does not change the behavior of gnomint crashing,
but if the gconf-editor is started and the key for apps/gnomint/size
is changed from the above value to something sensible greater than 320x320
then gnomint can be launched.

Exiting via the "Quit"  menu entry continues to cause the wrong size
value to be saved and therefore should not be used.

This bug was previously reported on Sun, 27 Dec 2009 23:17:58 -0500



but was merely dismissed by the package maintainer without
thorough investigation with the comment

   "I guess that the problem you were experiencing temporary and
probably not related to gnomint itself, hence i'm closing the bug."



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.39-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnomint depends on:
ii  gconf2  2.32.3-2 GNOME configuration database syste
ii  libatk1.0-0 2.0.0-1  The ATK accessibility toolkit
ii  libc6   2.13-7   Embedded GNU C Library: Shared lib
ii  libcairo2   1.10.2-2ubuntu2  The Cairo 2D vector graphics libra
ii  libfontconfig1  2.8.0-2.1ubuntu3 generic font configuration library
ii  libfreetype62.4.4-1  FreeType 2 font engine, shared lib
ii  libgconf2-4 2.32.3-2 GNOME configuration database syste
ii  libgcrypt11 1.4.6-5  LGPL Crypto library - runtime libr
ii  libgdk-pixbuf2.0-0  2.23.3-3 GDK Pixbuf library
ii  libglib2.0-02.28.6-1 The GLib library of C routines
ii  libgnutls26 2.10.5-1+b1  the GNU TLS library - runtime libr
ii  libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface
ii  libpango1.0-0   1.28.3-6 Layout and rendering of internatio
ii  libreadline66.2-2GNU readline and history libraries
ii  libsqlite3-03.7.6.3-1SQLite 3 shared library

gnomint recommends no packages.

gnomint suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: gnomint
Source-Version: 1.3.0-1

We believe that the bug you reported is fixed in the latest version of
gnomint, 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 631...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated gnomint 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: Sat, 26 Jan 2019 22:16:06 +0200
Source: gnomint
Architecture: source
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: 

Bug#920654: marked as done (RFS: liboauth/1.0.3-3 [QA])

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:34:20 +0100
with message-id <20190128013420.qtfths24y3qlf...@angband.pl>
and subject line Re: Bug#920654: RFS: liboauth/1.0.3-3 [QA]
has caused the Debian Bug report #920654,
regarding RFS: liboauth/1.0.3-3 [QA]
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.)


-- 
920654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: liboauth
   Version : 1.0.3-3
   Upstream Author : Robin Gareus 
 * URL : http://liboauth.sourceforge.net/
 * License : Expat
   Section : libs

  It builds these binary packages:

liboauth-dev - C library implementing OAuth Core 1.0a API (development 
files)
liboauth0  - C library implementing OAuth Core 1.0a API (runtime)

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

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


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

dget -ux 
https://mentors.debian.net/debian/pool/main/libo/liboauth/liboauth_1.0.3-3.dsc

  Changes since the last upload:

  * QA upload.
  * Add debian/not-installed to suppress dh_missing warnings.
  * Add 06_null_ptr_deref.patch, cherry-picked from upstream to avoid
possible null pointer dereference.
  * Drop 02_xmalloc_dont_exit.patch, since fixing the shlib-calls-exit
lintian warning by introducing a possible null pointer dereference is
incorrect. Use an override to suppress it instead.
  * Update debian/gbp.conf: change debian branch to debian/master.


  Regards,
   Carlos Maddela
--- End Message ---
--- Begin Message ---
On Mon, Jan 28, 2019 at 09:54:56AM +1100, Carlos Maddela wrote:
>  * Package name: liboauth
>Version : 1.0.3-3

>   Changes since the last upload:
> 
>   * QA upload.
>   * Add debian/not-installed to suppress dh_missing warnings.
>   * Add 06_null_ptr_deref.patch, cherry-picked from upstream to avoid
> possible null pointer dereference.
>   * Drop 02_xmalloc_dont_exit.patch, since fixing the shlib-calls-exit
> lintian warning by introducing a possible null pointer dereference is
> incorrect. Use an override to suppress it instead.
>   * Update debian/gbp.conf: change debian branch to debian/master.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄--- End Message ---


Bug#885817: marked as done (gnomint: Depends on gconf)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 01:34:17 +
with message-id 
and subject line Bug#885817: fixed in gnomint 1.3.0-1
has caused the Debian Bug report #885817,
regarding gnomint: Depends on gconf
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.)


-- 
885817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnomint
Version: 1.2.1-7
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

Your package depends or build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnomint
Source-Version: 1.3.0-1

We believe that the bug you reported is fixed in the latest version of
gnomint, 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 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated gnomint 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: Sat, 26 Jan 2019 22:16:06 +0200
Source: gnomint
Architecture: source
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Yavor Doganov 
Closes: 631768 855200 885817
Changes:
 gnomint (1.3.0-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream release.
   * debian/compat: Set to 11.
   * debian/control: Run wrap-and-sort -ast.
 (Build-Depends): Bump debhelper requirement to match the compat level.
 Remove autotools-dev and libgconf2-dev.
 (Recommends): Add gconf2 for the sake of data migration.
 (Standards-Version): Claim compliance with 4.3.0 as of this release.
   * debian/rules: Enable all hardening.  Remove --with autotools_dev.
 (override_dh_auto_install): Remove gconf schemas stuff.
   * debian/patches/682432.patch: Refresh.
   * debian/patches/02-cflags.patch: Remove configure hunk; refresh and
 remove -Werror.  Fix typo in the patch description.
   * debian/patches/01-ldd.patch:
   * debian/patches/10_gnutlsv3.diff: Delete, fixed upstream.
   * debian/patches/fix-autoreconf.patch: New, fix autoreconf failure.
   * debian/patches/gsettings-port.patch: New, migrate from GConf to
 GSettings (Closes: #885817).  I believe the switch to GSettings also
 closes: #631768 which was probably due to the fact that GConf does not
 apply changes atomically.
   * debian/patches/export-private-key-crash.patch: New, fix crash when
 exporting the private key (Closes: #855200).  Thanks to Karl E.
 Jorgensen for the report.
   * debian/patches/desktop-file.patch: New, fix some lintian complaints.
   * debian/patches/spelling-errors.patch: New, self-explanatory.
   * debian/patches/series: Update.
   * debian/watch: New file.
   * debian/pixmaps/gnomint.xpm: Delete.
   * debian/gnomint.menu: Likewise.
   * debian/gnomint.install: Likewise.
   * debian/copyright: Declare format.
   * debian/source/options: Delete as per lintian's advice.
Checksums-Sha1:
 4c3263e8fa05e92f62fa27fc83ba34f656121be3 1796 gnomint_1.3.0-1.dsc
 8abce2963b698dcd452a1ee38fd312b2d033009c 757968 gnomint_1.3.0.orig.tar.gz
 24b2896f92768904199ed5f513886d529f4c9b39 9780 gnomint_1.3.0-1.debian.tar.xz
 8d2edef2e0dd5a8c5034f70b7173d35de3409067 5826 gnomint_1.3.0-1_source.buildinfo
Checksums-Sha256:
 0543253f159187ec7aee3cc9a2d9cc38e9264baa1c39dca2c4cdd1f76fe61d22 1796 
gnomint_1.3.0-1.dsc
 85b404d458f22c1b1337c0063f659cdf3da4fa1d02baf0c50efad9e897194834 757968 
gnomint_1.3.0.orig.tar.gz
 ebad38271c0ca5dc6f0258340bb1fd94f036c861e0837d8680c60bcad0175858 9780 
gnomint_1.3.0-1.debian.tar.xz
 cfb0e0f9ff0b8025d399237e4b1a8788968054f5c2b613d763db88ca4d794140 5826 
gnomint_1.3.0-1_source.buildinfo
Files:
 8d2b83c2d7205e4eefcabe79957fbb9b 1796 gnome optional gnomint_1.3.0-1.dsc
 32d6fa9be8c47325fa5b337a99c7e006 757968 

Bug#855200: marked as done (gnomint: segfault when exporting private keys)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 01:34:17 +
with message-id 
and subject line Bug#855200: fixed in gnomint 1.3.0-1
has caused the Debian Bug report #855200,
regarding gnomint: segfault when exporting private keys
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.)


-- 
855200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnomint
Version: 1.2.1-7
Severity: important

Dear Maintainer,

When exporting private keys from gnomint, the export appars to work
ok, but is immediately followed by a segfault.  This happens on both
version 1.2.1-7+b2 and version 1.2.1-7

This doesn't happen when exporting the public parts.

I managed to build gnomint 1.2.1-7 [1] from the debian source ("managed" -
it was easy) , which also produced the gnomint-dbgsym package which
allowed me to examine the resulting core dump. It gave me this backtrace:

Core was generated by `gnomint'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fbe7c4bd445 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
[Current thread is 1 (Thread 0x7fbe7ce73a80 (LWP 25490))]
(gdb) bt
#0  0x7fbe7c4bd445 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#1  0x7fbe7c4b032c in gtk_tree_model_get_valist () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#2  0x7fbe7c4b0629 in gtk_tree_model_get () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#3  0x5589191c2a4b in __ca_export_private_pkcs8 (iter=0x5589, 
type=type@entry=0) at ca.c:950
#4  0x5589191c34ea in ca_on_extractprivatekey1_activate 
(menuitem=, user_data=) at ca.c:1192
#5  0x7fbe7be3df75 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x7fbe7be4ff82 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x7fbe7be58bcc in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x7fbe7be58faf in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x7fbe7c4ec62e in gtk_widget_activate () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#10 0x7fbe7c3e74dd in gtk_menu_shell_activate_item () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#11 0x7fbe7c3e7846 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#12 0x7fbe7c3d57bc in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x7fbe7be3df75 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x7fbe7be5037d in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x7fbe7be5866f in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x7fbe7be58faf in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x7fbe7c4ed8ac in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#18 0x7fbe7c3d3f84 in gtk_propagate_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#19 0x7fbe7c3d433b in gtk_main_do_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#20 0x7fbe79f45cbc in ?? () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#21 0x7fbe7bb647f7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fbe7bb64a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fbe7bb64d82 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fbe7c3d33b7 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#25 0x5589191b828a in main (argc=, argv=) at 
main.c:201


[1] "apt-get source" was unwilling give the source for 1.2.1-7+b2 !?
It would only give me version 1.2.1-7. But the same problem
exists there too.


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

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

Versions of packages gnomint depends on:
ii  gconf-service   3.2.6-4
ii  gconf2  3.2.6-4
ii  libc6   2.24-9
ii  libgconf-2-43.2.6-4
ii  libgcrypt20 1.7.6-1
ii  libgdk-pixbuf2.0-0  2.36.4-1
ii  libglib2.0-02.50.2-2
ii  libgnutls30 3.5.8-3
ii  libgtk2.0-0 2.24.31-2
ii  libreadline77.0-2
ii  libsqlite3-03.16.2-2

gnomint recommends no packages.

gnomint suggests no packages.

-- no 

Bug#920660: marked as done (RFS: rmlint/2.8.0-3)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:31:08 +0100
with message-id <20190128013108.zhmohvfsmekzt...@angband.pl>
and subject line Re: Bug#920660: RFS: rmlint/2.8.0-3
has caused the Debian Bug report #920660,
regarding RFS: rmlint/2.8.0-3
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.)


-- 
920660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: rmlint
   Version : 2.8.0-3
   Upstream Author : Christopher Pahl 
 * URL : https://rmlint.readthedocs.io/
 * License : GPL-3+
   Section : utils

  It builds these binary packages:

 rmlint - Extremely fast tool to remove filesystem lint
 rmlint-doc - HTML documentation for rmlint
 rmlint-gui - GTK+ frontend to rmlint

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

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


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

dget -ux 
https://mentors.debian.net/debian/pool/main/r/rmlint/rmlint_2.8.0-3.dsc

  Changes since the last upload:

  * Re-enable SSE4.2 optimisations without causing SIGILL faults.
  * Fix changelog details in debian/upstream/metadata.
  * Update debian/gbp.conf to conform with DEP14 conventions.
  * Suppress maintainer-script-supports-ancient-package-version
lintian warnings.
  * Update sed rule to substitute local copy of MathJax script.


  Regards,
   Carlos Maddela
--- End Message ---
--- Begin Message ---
On Mon, Jan 28, 2019 at 12:07:28PM +1100, Carlos Maddela wrote:
>  * Package name: rmlint
>Version : 2.8.0-3

>   Changes since the last upload:
> 
>   * Re-enable SSE4.2 optimisations without causing SIGILL faults.
>   * Fix changelog details in debian/upstream/metadata.
>   * Update debian/gbp.conf to conform with DEP14 conventions.
>   * Suppress maintainer-script-supports-ancient-package-version
> lintian warnings.
>   * Update sed rule to substitute local copy of MathJax script.

Tested on a non-SSE4.2 machine.  No explosions.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄--- End Message ---


Bug#907826: marked as done (RFS: gnomint/1.3.0-1 [QA])

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 02:12:44 +0100
with message-id <20190128011244.5qtqna6qn4teb...@angband.pl>
and subject line Re: Bug#907826: RFS: gnomint/1.3.0-1 [QA]
has caused the Debian Bug report #907826,
regarding RFS: gnomint/1.3.0-1 [QA]
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.)


-- 
907826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important

Dear mentors,

I'm looking for a sponsor for a QA upload of "gnomint".

 * Package name: gnomint
   Version : 1.3.0-1
   Upstream Author : David Marín Carreño 
 * URL : https://gnomint.sf.net
 * License : GPL-3+
   Section : gnome

It builds this binary package:

gnomint- X.509 Certification Authority management tool for GNOME

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gnomint/gnomint_1.3.0-1.dsc

Changes since the last upload:

  * QA upload.
  * New upstream release.
  * debian/compat: Set to 11.
  * debian/control: Run wrap-and-sort -ast.
(Build-Depends): Bump debhelper requirement to match the compat level.
Remove autotools-dev and libgconf2-dev.
(Standards-Version): Claim compliance with 4.2.1 as of this release.
  * debian/rules: Enable all hardening.  Remove --with autotools_dev.
(override_dh_auto_install): Remove gconf schemas stuff.
  * debian/patches/682432.patch: Refresh.
  * debian/patches/02-cflags.patch: Remove configure hunk; refresh and
remove -Werror.  Fix typo in the patch description.
  * debian/patches/01-ldd.patch:
  * debian/patches/10_gnutlsv3.diff: Delete, fixed upstream.
  * debian/patches/fix-autoreconf.patch: New, fix autoreconf failure.
  * debian/patches/gsettings-port.patch: New, migrate from GConf to
GSettings (Closes: #885817).  I believe the switch to GSettings also
closes: #631768 which was probably due to the fact that GConf does not
apply changes atomically.
  * debian/patches/export-private-key-crash.patch: New, fix crash when
exporting the private key (Closes: #855200).  Thanks to Karl E.
Jorgensen for the report.
  * debian/patches/desktop-file.patch: New, fix some lintian complaints.
  * debian/patches/spelling-errors.patch: New, self-explanatory.
  * debian/patches/series: Update.
  * debian/watch: New file.
  * debian/pixmaps/gnomint.xpm:
  * debian/gnomint.menu:
  * debian/gnomint.install: Delete.
  * debian/copyright: Declare format.
--- End Message ---
--- Begin Message ---
On Sat, Jan 26, 2019 at 10:58:19PM +0200, Yavor Doganov wrote:
> Control: reopen -1
> 
> This bug has been closed because the package was automatically removed
> from mentors.d.n (20 weeks without upload).

Thanks for the ping.


> On Sun, Sep 02, 2018 at 07:41:18PM +0300, Yavor Doganov wrote:
> I reuploaded the package with three tiny changes:
> 
> - Bumped Standards-Version to 4.3.0;
> - Deleted debian/source/options (custom compression settings);
> - Refreshed changelog timestamp.

Looks good to me.  I did not test the functionality, and the review was
pretty cursory, but I see no likely issues.

✓

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄--- End Message ---


Bug#920471: marked as done (RFS: fathom/1.0+git.20190120.0439ca-1)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 01:59:20 +0100
with message-id <20190128005920.lcrfx23b3yosk...@angband.pl>
and subject line Re: Bug#920471: RFS: fathom/1.0+git.20190120.0439ca-1
has caused the Debian Bug report #920471,
regarding RFS: fathom/1.0+git.20190120.0439ca-1
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.)


-- 
920471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "fathom":

* Package name: fathom
  Version : 1.0+git.20190120.0439ca-1
  Upstream Author : Jon Dart
* URL : https://github.com/jdart1/Fathom
* License : MIT
  Section : libs

It builds those binary packages:

 fathom - Command-line for probing Syzygy tablebases
 libfathom-dev - Library for probing Syzygy tablebases (development files)
 libfathom1 - Library for probing Syzygy tablebases

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/f/fathom/fathom_1.0+git.20190120.0439ca-1.dsc

Package development is on the following repo:

https://salsa.debian.org/josgalo-guest/fathom

Changes since the last upload:

fathom (1.0+git.20190120.0439ca-1) unstable; urgency=medium

  * debian/control:
- Use debhelper compat version 12.
- Change maintainer's e-mail and upstream homepage.
  * debian/copyright:
- Update url source, copyright notices and my e-mail.
  * debian/rules:
- Add -I option to find headers.
  * debian/watch:
- Change upstream git repo.
  Use Jon Dart's fork. It has some bug fixes and enhancements.

 -- Jose G. López   Fri, 25 Jan 2019 20:39:28 +0100

Using Jon Dart's fork as it has some bug fixes and enhancements.
It has a fix for compiling on 32 bits archs.

Hope this version fix these building errors:
https://buildd.debian.org/status/package.php?p=fathom

Thanks and regards,


pgpHIxGs5ONOH.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Fri, Jan 25, 2019 at 11:50:28PM +0100, Jose G. López wrote:
> * Package name: fathom
>   Version : 1.0+git.20190120.0439ca-1

> fathom (1.0+git.20190120.0439ca-1) unstable; urgency=medium
> 
>   * debian/control:
> - Use debhelper compat version 12.
> - Change maintainer's e-mail and upstream homepage.
>   * debian/copyright:
> - Update url source, copyright notices and my e-mail.
>   * debian/rules:
> - Add -I option to find headers.
>   * debian/watch:
> - Change upstream git repo.
>   Use Jon Dart's fork. It has some bug fixes and enhancements.
> 
>  -- Jose G. López   Fri, 25 Jan 2019 20:39:28 +0100

✓

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄--- End Message ---


Bug#845624: marked as done (lxqt: Touchpad features)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 00:20:56 +
with message-id 
and subject line Bug#845624: fixed in lxqt-config 0.14.0-1
has caused the Debian Bug report #845624,
regarding lxqt: Touchpad features
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.)


-- 
845624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lxqt
Version: 7
Severity: normal

Hello Dear Maintainer!

It is not bug report. It is request to adding feature for touchpades. Please,
add touchpad management in "LXQt settings".
Primary, need logic for disabling touchpad when usb || bt mouse connected.



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

Kernel: Linux 4.8.8-desktop-1000hz (SMP w/4 CPU cores)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lxqt depends on:
ii  lxqt-about0.11.0-2
ii  lxqt-admin0.11.0-2
ii  lxqt-config   0.11.0-2
ii  lxqt-core 7
ii  lxqt-globalkeys   0.11.0-3
ii  lxqt-notificationd0.11.0-2
ii  lxqt-openssh-askpass  0.11.0-2
ii  lxqt-policykit0.11.0-4
ii  lxqt-powermanagement  0.11.0-2
ii  lxqt-qtplugin 0.11.0-3+b1
ii  lxqt-runner   0.11.0-2

Versions of packages lxqt recommends:
ii  ark4:16.08.3-1
ii  audacious  3.7.2-1
ii  chromium [www-browser] 53.0.2785.143-1+exp1
pn  cmst   
ii  firefox-esr [www-browser]  45.5.0esr-1
ii  gksu   2.0.2-9
ii  gucharmap  1:9.0.2-1
ii  konqueror [www-browser]4:16.08.3-1
ii  lximage-qt 0.5.0-4
ii  lxqt-sudo  0.11.0-2
ii  lynx [www-browser] 2.8.9dev11-1
ii  network-manager1.4.2-2
ii  pavucontrol3.0-3+b2
ii  qlipper1:5.0.0-1
ii  qpdfview   0.4.14-1
ii  qps1.10.16-29-g7e679db-1
ii  qterminal  0.7.0-2
ii  sddm [x-display-manager]   0.13.0-1
ii  smplayer   16.11.0~ds0-1
ii  smtube 15.5.10-1
ii  w3m [www-browser]  0.5.3-33
ii  xarchiver  1:0.5.4-5

Versions of packages lxqt suggests:
pn  calibre   
pn  claws-mail
pn  compton   
pn  compton-conf  
ii  hexchat   2.12.0-2+b1
pn  juffed
pn  nomacs
pn  obconf-qt 
ii  openbox   3.6.1-3
pn  qtpass
pn  screengrab | shutter  
pn  vokoscreen
pn  zim   
--- End Message ---
--- Begin Message ---
Source: lxqt-config
Source-Version: 0.14.0-1

We believe that the bug you reported is fixed in the latest version of
lxqt-config, 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 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alf Gaida  (supplier of updated lxqt-config 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: Sun, 27 Jan 2019 17:15:29 +0100
Source: lxqt-config
Binary: lxqt-config lxqt-config-l10n
Architecture: source
Version: 0.14.0-1
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team 
Changed-By: Alf Gaida 
Description:
 lxqt-config - LXQt system settings center
 lxqt-config-l10n - Language package for lxqt-config
Closes: 845624
Changes:
 lxqt-config (0.14.0-1) unstable; urgency=medium
 .
   * Cherry-picking new upstream version 0.14.0.
   * Bumped Standards to 4.3.0, no changes needed
   * Dropped d/compat, use debhelper-compat = 12, no changes needed
   * Fixed years in d/copyright
   * Bumped minimum version liblxqt0-dev (>= 0.14.0~)
   * Added build dependency libxi-dev
   * Added build dependency xserver-xorg-input-libinput-dev
   * Removed obsolete PULL_TRANSLATIONS= OFF from dh_auto_configure
   * Added l10n-package, moved from lxqt-l10n
   * Added 

Bug#900421: marked as done (improve "wiki account creation delayed" message)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Mon, 28 Jan 2019 00:10:24 +
with message-id <20190128001024.z5cafmajiptgv...@tack.einval.com>
and subject line Re: Bug#900421: improve "wiki account creation delayed" message
has caused the Debian Bug report #900421,
regarding improve "wiki account creation delayed" message
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.)


-- 
900421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: wiki.debian.org
severity: wishlist
x-debbugs-cc: debian-backports.lists.debian.org

Dear wiki admins,

On Wed, May 30, 2018 at 04:24:20PM +0200, Geert Stappers wrote:
> On Wed, May 30, 2018 at 01:57:26PM +, Christian Heutger wrote:
> > I now uploaded to https://www.heutger.net/backports/
> > and tried to create a wiki account, but got " Account creation failed:
> > To prevent spam, this wiki requires additional information from some
> > people. Please contact w...@debian.org and describe what you want to
> > do in the wiki...", so I try to get that sorted out now.

I've experienced this several many times, that people are confused by
the message, despite it says what it says. Thus I suggest to make it
even clearer.

How about: 

"Account creation *delayed*: to prevent spam, this wiki requires additional
information from some people. Please contact w...@debian.org and describe
what you want to do in the wiki. To repeat: please mail us if you need
an account."

(I replaced "failed" with "delayed" and add the last sentence.)


-- 
cheers,
Holger


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sun, Jan 27, 2019 at 04:01:29PM -0800, Tassia Camoes Araujo wrote:
>Hi Steve,
>
>On 2019-01-27 15:56, Steve McIntyre wrote:
>>
>> Updated to say
>> 
>>   "Automatic account creation disabled to stop spammers signing
>>up. Please contact $admin_private and describe what you want to do in
>>the wiki."
>> 
>> How does that sound?
>
>Great news, I think this new message solves the issue.
>Thanks again!

Cool, no problem. Closing this bug then.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...--- End Message ---


Bug#762918: marked as done (Please convert all scripts to not use bash)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 15:46:15 -0800
with message-id <20190127234615.ga103...@google.com>
and subject line Re: Please convert all scripts to not use bash
has caused the Debian Bug report #762918,
regarding Please convert all scripts to not use bash
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.)


-- 
762918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: xz-utils
Version: 5.1.1alpha+20120614-2
Severity: grave

Please convert all scripts (xzdiff, xzless, ...) to use /bin/sh as shell
and not /bin/bash. Most of them (as I checked) do not use any special
bash syntax anyway so there is no need to use bash.

I made this a grave bug as it is security relevant due the current bash
bugs and against the debian policy to use /bin/sh if possible.

- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.15.10 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to 
de_DE)
Shell: /bin/sh linked to /bin/dash

Versions of packages xz-utils depends on:
ii  libc6 2.19-11
ii  liblzma5  5.1.1alpha+20120614-2

xz-utils recommends no packages.

xz-utils suggests no packages.

- -- no debconf information

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJUJT0eAAoJEKZ8CrGAGfasOQkL/3+GmsUyz05FfCth5fUojLXI
3BerfHYf2OP2a6oIWUIRbWva6AD7mHXNqY4P4/862zy6csJ+nQg6KjiZ4le+zUVz
hG3WubKxdcFZfv9loCCznT6b+VvedpV8kP0xDsleusnSl0Ud4ZIgvtyS1Fkt6AT3
Em3VIrN++LCH6Uq5o9lj5EbXMPd0GQkv5xx2fW9gjUykR3iYPOagUrZ63Fi/wP2F
P1IIB8WmUDXRQEhr7oGquhrCZvPjEGDgC8vloAoAYwuNvTUfoeDQ3N597koaoMiz
AbRtw16LzZyCuWDbXA9DL7Uq2bBPKWpA5EBWLjE/+IBU1Ms5Vh4Ag1JiRZPRxN7o
19Jec+mOspiyd1v6TY66+4wv3tOMOZkDEgFru0cn57XQzi+vjXqe2/ulg3JW3j1h
qtZfBbZTXB1n1cWeJZ5FFGsZbYVr5mIZOXOLQHoMKTXv4NbgBKilgiJu+6oTOe3j
3km5DyBZnGWaJ9HKlDz6CoMSXJiIaE2dLlNeOxE+Pg==
=YYRl
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 5.2.2-1.3

Hi Klaus,

In September, 2014, Klaus Ethgen wrote:

> Please convert all scripts (xzdiff, xzless, ...) to use /bin/sh as shell
> and not /bin/bash. Most of them (as I checked) do not use any special
> bash syntax anyway so there is no need to use bash.

This was a packaging bug --- the intent was to use an arbitrary POSIX
shell (hence /bin/sh) all along.  Fixed by Ximin Luo in 5.2.2-1.3
(thanks!).

Thanks for reporting, and sorry for the slow reply.--- End Message ---


Bug#919971: marked as done (node-rollup-pluginutils: autopkgtestsuite failure)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:53:50 +
with message-id 
and subject line Bug#919971: fixed in node-rollup-pluginutils 2.3.3-4
has caused the Debian Bug report #919971,
regarding node-rollup-pluginutils: autopkgtestsuite 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.)


-- 
919971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-rollup-pluginutils
Version: 2.3.3-2
Severity: serious
Tags: patch

Hello, looks like the latest upload fails its autopkgtestsuite, since
some days/weeks.

See e.g.:
https://ci.debian.net/data/autopkgtest/unstable/amd64/n/node-rollup-pluginutils/1618356/log.gz

(Reading database ... 22971 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [07:49:14]: test upstreamtestsuite: [---
find test/ -name '*.js' -and -not -name 'createFilter.test.js' -exec mocha {} \;
internal/modules/cjs/loader.js:583
    throw err;
    ^

Error: Cannot find module '..'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object. 
(/tmp/autopkgtest-lxc.nqmg3_9p/downtmp/build.9cL/src/test/addExtension.test.js:2:22)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at /usr/lib/nodejs/mocha/lib/mocha.js:231:27
    at Array.forEach ()
    at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:228:14)
    at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:536:10)
    at Object. (/usr/lib/nodejs/mocha/bin/_mocha:573:18)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
internal/modules/cjs/loader.js:583
    throw err;
    ^


I'm not sure which is the best approach to fix this issue, but at least
this approach works:

--- node-rollup-pluginutils-2.3.3/debian/tests/upstreamtestsuite    2018-12-31 
02:23:05.0 +0100
+++ node-rollup-pluginutils-2.3.3/debian/tests/upstreamtestsuite    2019-01-20 
22:46:52.0 +0100
@@ -1,2 +1,7 @@
 #!/bin/sh
-make -f debian/rules test_package
+sed -i test/dataToEsm.test.js -e "s/( '..' )/('rollup-pluginutils')/g"
+sed -i test/attachScopes.test.js -e "s/( '..' )/('rollup-pluginutils')/g"
+sed -i test/addExtension.test.js -e "s/( '..' )/('rollup-pluginutils')/g"
+sed -i test/makeLegalIdentifier.test.js -e "s/( '..' 
)/('rollup-pluginutils')/g"
+sed -i test/createFilter.test.js -e "s/( '..' )/('rollup-pluginutils')/g"
+make -f debian/rules test_package

This is something that basically reverts commit 
b33024e405af90183a6e6a65ab3163f177932e5e

Thanks for having a look,

Gianfranco

--- End Message ---
--- Begin Message ---
Source: node-rollup-pluginutils
Source-Version: 2.3.3-4

We believe that the bug you reported is fixed in the latest version of
node-rollup-pluginutils, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated node-rollup-pluginutils 
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: Sun, 27 Jan 2019 19:41:28 +0100
Source: node-rollup-pluginutils
Binary: 

Bug#835377: marked as done (godoc requires explicit GOROOT)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:06:27 +
with message-id <4f86cdb9-76f7-202d-e2ea-45027a110...@debian.org>
and subject line Closing bug after 2 years
has caused the Debian Bug report #835377,
regarding godoc requires explicit GOROOT
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.)


-- 
835377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-golang-x-tools
Version: 1:0.0~git20160315.0.f42ec61-2
Severity: normal

The general recommendation is to not set GOROOT, because the go tools
know what it should be with a default install (see [1] and [2] and
numerous discussions on golang-nuts mailing list).

However, godoc does not use the implicit GOROOT (the one shown by go
env) and requires setting it explicitly to get expected behavior (e.g.
providing documentation for standard library packages).

...Marvin

[1] https://golang.org/doc/install
[2] http://dave.cheney.net/2013/06/14/you-dont-need-to-set-goroot-really

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

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

Versions of packages golang-golang-x-tools depends on:
ii  golang-golang-x-tools-dev  1:0.0~git20160315.0.f42ec61-2
ii  libc6  2.23-4

golang-golang-x-tools recommends no packages.

golang-golang-x-tools suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
There was no response to request for more information after 2 years.
Closing now.
-- 
Martín Ferrari (Tincho)--- End Message ---


Bug#228112: marked as done (indent: Adjustment of '*' in function declaration)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:04:21 +
with message-id 
and subject line Bug#228112: fixed in indent 2.2.12-1
has caused the Debian Bug report #228112,
regarding indent: Adjustment of '*' in function declaration
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.)


-- 
228112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=228112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: indent
Version: 2.2.9-5
Severity: wishlist


It would good to have an option to adjust '*' in the parameterlist
of functions. Possible results of adjustment:
"function(type *variable)"
"function(type * variable)"
"function(type* variable)"
or don't touch.
This could be done easily, as the meaning of '*' can be easily
decided in a function declaration.

Thanks,
 Miklos Danko, M.D.
mailto:dan...@gizi.dote.hu   (Hungary)


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux chewing 2.4.23 #1 Tue Jan 6 11:13:44 CET 2004 i686
Locale: LANG=C, LC_CTYPE=hu_HU

Versions of packages indent depends on:
ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries an

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: indent
Source-Version: 2.2.12-1

We believe that the bug you reported is fixed in the latest version of
indent, 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 228...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated indent 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: Sun, 27 Jan 2019 22:35:20 +0100
Source: indent
Architecture: source
Version: 2.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Closes: 228112 349065 487517 657461 726105 865677 916199
Changes:
 indent (2.2.12-1) unstable; urgency=low
 .
   * New upstream release. Closes: #916199.
 This is now maintained upstream by Andrej Shadura.
   * Drop all debian/patches/*, not required anymore.
   * Should fix '*' in function declaration. Closes: #228112.
   * Should fix double const after C++ function declaration. Closes: #349065.
   * Should improve support for gettext macros. Closes: #487517.
   * New option --fix-nested-comments. Closes: #657461.
   * Should not change !! to ! ! anymore when using -linux. Closes: #726105.
   * Should now cross-build. Closes: #865677.
   * Rules-Requires-Root: no.
Checksums-Sha1:
 36783e19c275da879687c9f2d8844c4d57402f64 1390 indent_2.2.12-1.dsc
 eecb3d7e78516d846af70e7bc86aabac9b92399c 620280 indent_2.2.12.orig.tar.xz
 d280f8b35975b8df52cd391411559234b5b97de7 5948 indent_2.2.12-1.debian.tar.xz
 9ae2b38a123edf27551aa324e0c184acab82ea84 4896 indent_2.2.12-1_source.buildinfo
Checksums-Sha256:
 e802796b98203d047d819685801bd970b20a6525836b35c5a9fd119eb7cf176d 1390 
indent_2.2.12-1.dsc
 b745a5dfc68f86a483d7f96dc1cda7aafd1e78ecba3c7d8ad304709e91e1defb 620280 
indent_2.2.12.orig.tar.xz
 d3ac4770ff8a0de2497a44c2a2d3e57521efb748620793bf531499565c50c5ea 5948 
indent_2.2.12-1.debian.tar.xz
 d62fde0178001f6517549001f78abba0c64d9a4c2bede1056b123610c9ed529e 4896 
indent_2.2.12-1_source.buildinfo
Files:
 235cbcac6f3c8e67d8c2ddf55ee33a3e 1390 devel optional indent_2.2.12-1.dsc
 9cba859a8b1958baa2e3dce1dadb37db 620280 devel optional 
indent_2.2.12.orig.tar.xz
 85039d044a9c085d5a506ff9ad66dd74 5948 devel optional 
indent_2.2.12-1.debian.tar.xz
 aa435f822003c88ec252181c36d9a3af 4896 devel optional 
indent_2.2.12-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAlxOKC4ACgkQQc5/C58b
izL00wf/Zm/3/RhTtw5rZ6s+9YDbDRoqBmbY2v1a06rWF0+rFRLHpGm1mKgwKwOf
/VNSkobY+7a/SNda/rzWgHdDT+ekcAXh4VBc3UiG51BNOl9RTjauupDgLnccEVUt
mepPmLP2btWupN1mSAaHy1HIySV3miQbQYFMLo9/QlcO3eVu7ZPpFP5jy76iLqLT
pUYIDuw/4MCoUcAun//CF/KHshpONhCi1nx5Pa9rFsEidtlH1QIPalQUmvgvbnpQ
kqVLrcPR9TnpCPIniySTrfeAu53I3LSUkAgFtH9P2QHIQgMRCJSwEfCox3ZROaEL
x0lVS45qFVrvIqoPBXjVU3c1yXBVBQ==
=lz9b
-END PGP SIGNATURE End Message ---


Bug#507173: marked as done (indent: adds extra const keywords to C++ programs)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:04:21 +
with message-id 
and subject line Bug#349065: fixed in indent 2.2.12-1
has caused the Debian Bug report #349065,
regarding indent: adds extra const keywords to C++ programs
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.)


-- 
349065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=349065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: indent
Version: 2.2.10-1
Severity: normal

Steps to reproduce:
1) cat > svg.cc <--- End Message ---
--- Begin Message ---
Source: indent
Source-Version: 2.2.12-1

We believe that the bug you reported is fixed in the latest version of
indent, 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 349...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated indent 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: Sun, 27 Jan 2019 22:35:20 +0100
Source: indent
Architecture: source
Version: 2.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Closes: 228112 349065 487517 657461 726105 865677 916199
Changes:
 indent (2.2.12-1) unstable; urgency=low
 .
   * New upstream release. Closes: #916199.
 This is now maintained upstream by Andrej Shadura.
   * Drop all debian/patches/*, not required anymore.
   * Should fix '*' in function declaration. Closes: #228112.
   * Should fix double const after C++ function declaration. Closes: #349065.
   * Should improve support for gettext macros. Closes: #487517.
   * New option --fix-nested-comments. Closes: #657461.
   * Should not change !! to ! ! anymore when using -linux. Closes: #726105.
   * Should now cross-build. Closes: #865677.
   * Rules-Requires-Root: no.
Checksums-Sha1:
 36783e19c275da879687c9f2d8844c4d57402f64 1390 indent_2.2.12-1.dsc
 eecb3d7e78516d846af70e7bc86aabac9b92399c 620280 indent_2.2.12.orig.tar.xz
 d280f8b35975b8df52cd391411559234b5b97de7 5948 indent_2.2.12-1.debian.tar.xz
 9ae2b38a123edf27551aa324e0c184acab82ea84 4896 indent_2.2.12-1_source.buildinfo
Checksums-Sha256:
 e802796b98203d047d819685801bd970b20a6525836b35c5a9fd119eb7cf176d 1390 
indent_2.2.12-1.dsc
 b745a5dfc68f86a483d7f96dc1cda7aafd1e78ecba3c7d8ad304709e91e1defb 620280 
indent_2.2.12.orig.tar.xz
 d3ac4770ff8a0de2497a44c2a2d3e57521efb748620793bf531499565c50c5ea 5948 
indent_2.2.12-1.debian.tar.xz
 d62fde0178001f6517549001f78abba0c64d9a4c2bede1056b123610c9ed529e 4896 
indent_2.2.12-1_source.buildinfo
Files:
 235cbcac6f3c8e67d8c2ddf55ee33a3e 1390 devel optional indent_2.2.12-1.dsc
 9cba859a8b1958baa2e3dce1dadb37db 620280 devel optional 
indent_2.2.12.orig.tar.xz
 85039d044a9c085d5a506ff9ad66dd74 5948 devel optional 
indent_2.2.12-1.debian.tar.xz
 aa435f822003c88ec252181c36d9a3af 4896 devel optional 
indent_2.2.12-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAlxOKC4ACgkQQc5/C58b
izL00wf/Zm/3/RhTtw5rZ6s+9YDbDRoqBmbY2v1a06rWF0+rFRLHpGm1mKgwKwOf
/VNSkobY+7a/SNda/rzWgHdDT+ekcAXh4VBc3UiG51BNOl9RTjauupDgLnccEVUt
mepPmLP2btWupN1mSAaHy1HIySV3miQbQYFMLo9/QlcO3eVu7ZPpFP5jy76iLqLT
pUYIDuw/4MCoUcAun//CF/KHshpONhCi1nx5Pa9rFsEidtlH1QIPalQUmvgvbnpQ
kqVLrcPR9TnpCPIniySTrfeAu53I3LSUkAgFtH9P2QHIQgMRCJSwEfCox3ZROaEL
x0lVS45qFVrvIqoPBXjVU3c1yXBVBQ==
=lz9b
-END PGP SIGNATURE End Message ---


Bug#349065: marked as done ([Bug+Patch] double const after C++ Function declaration)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:04:21 +
with message-id 
and subject line Bug#349065: fixed in indent 2.2.12-1
has caused the Debian Bug report #349065,
regarding [Bug+Patch] double const after C++ Function declaration
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.)


-- 
349065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=349065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: indent
Version: 2.2.9-6


Hello,

Debian Bug System CCed as I use Debian, but I can reproduce the Problem on
cygwin, too.

see the Following problem:
saturn:~$ indent  --version
GNU indent: 2.2.9
saturn:~$ cat test.cpp
#include 
#include 
#include "test.hpp"


const int &
 test::test () const
 {
 }
saturn:~$ indent -o /dev/stdout test.cpp
#include 
#include 
#include "test.hpp"


const int &
test::test () const const
{
}


Notice the double const after test in the Output.
After applying the Attached Patch the Output looks Sytactically correct --
but the formation is still not as expected -- but can be easily fixed by
the editor:

saturn:~/indent-2.2.9/src$ ./indent  -o /dev/stdout  ../../test.cpp
#include 
#include 
#include "test.hpp"


const int &
test::test ()
 const
 {
 }


I have include a little bit more environment to include the comment -- is
it still correct? I have run the regression TEST with this change and no
difference, perhaps you can include my example Program into this Testsuite
Perhaps include some other Programs to further test this part of the code?

Best Regards,
  Thorsten Wilmer


diff -r -U12 indent-2.2.9-org/src/indent.c indent-2.2.9/src/indent.c
--- indent-2.2.9-org/src/indent.c   2002-10-28 21:00:56.0 +0100
+++ indent-2.2.9/src/indent.c   2006-01-20 20:36:32.0 +0100
@@ -1426,25 +1427,25 @@
 exit_values_ty * file_exit_value)
 {
 /* handle C++ const function declarations like
  * const MediaDomainList PVR::get_itsMediaDomainList() const
  * {
  * return itsMediaDomainList;
  * }
  * by ignoring "const" just after a parameter list */

 if ((parser_state_tos->last_token == rparen) &&
 parser_state_tos->in_parameter_declaration &&
 parser_state_tos->saw_double_colon &&
-!strncmp (token, "const", 5))
+! (strncmp (token, "const", 5)==0))
 {
 char   * t_ptr;
 set_buf_break (bb_const_qualifier, paren_target);
 *e_code++ = ' ';

 for (t_ptr = token; t_ptr < token_end; ++t_ptr)
 {
 check_code_size();
 *e_code++ = *t_ptr;
 }

 *e_code = '\0'; /* null terminate code sect */




--- End Message ---
--- Begin Message ---
Source: indent
Source-Version: 2.2.12-1

We believe that the bug you reported is fixed in the latest version of
indent, 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 349...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated indent 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: Sun, 27 Jan 2019 22:35:20 +0100
Source: indent
Architecture: source
Version: 2.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Closes: 228112 349065 487517 657461 726105 865677 916199
Changes:
 indent (2.2.12-1) unstable; urgency=low
 .
   * New upstream release. Closes: #916199.
 This is now maintained upstream by Andrej Shadura.
   * Drop all debian/patches/*, not required anymore.
   * Should fix '*' in function declaration. Closes: #228112.
   * Should fix double const after C++ function declaration. Closes: #349065.
   * Should improve support for gettext macros. Closes: #487517.
   * New option --fix-nested-comments. Closes: #657461.
   * Should not change !! to ! ! anymore when using -linux. Closes: #726105.
   * Should now cross-build. Closes: #865677.
   * Rules-Requires-Root: no.
Checksums-Sha1:
 36783e19c275da879687c9f2d8844c4d57402f64 1390 indent_2.2.12-1.dsc
 eecb3d7e78516d846af70e7bc86aabac9b92399c 620280 indent_2.2.12.orig.tar.xz
 d280f8b35975b8df52cd391411559234b5b97de7 5948 

Bug#657461: marked as done (add --fix-nested-comments option)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:04:21 +
with message-id 
and subject line Bug#657461: fixed in indent 2.2.12-1
has caused the Debian Bug report #657461,
regarding add --fix-nested-comments option
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.)


-- 
657461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: indent
Version: 2.2.11-1
Severity: wishlist
Tags: patch upstream

The patch attached to add an option to fix nested comments by replacing
'/*' with ' *'.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-rc7-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages indent depends on:
ii  dpkg  1.16.1.2  
ii  install-info  4.13a.dfsg.1-4
ii  libc6 2.13-7

indent recommends no packages.

indent suggests no packages.

-- no debconf information
Description: add an option to fix nested comments
 Added -fnc/--fix-nested comment option which tries to fix nested comments
 by replacing '/*' inside comments by a space followed by '*'. By default,
 this option is turned off.
Author: Andrew O. Shadura 
Last-Update: 2012-01-26

--- a/src/comments.c
+++ b/src/comments.c
@@ -59,6 +59,9 @@
  * `format_col1_comments'   ("fc1"):  Format comments which
  * begin in column 1.
  *
+ * `fix_nested_comments'("fnc"):  Fix comments which
+ * have nested opening sequences
+ *
  * `unindent_displace'  ("d"):  The hanging indentation for
  * comments which do not appear to the right of code.
  *
@@ -190,6 +193,15 @@
 /* We have reached the end of the comment, and it's all on
  * this line. */
 
+ if (settings.fix_nested_comments)
+ {
+if ((*buf_ptr == '*') && (*(buf_ptr - 1) == '/'))
+{
+   *(e_com - 1) = ' ';
+   *e_com = '*';
+}
+ }
+
  if ((*buf_ptr == '*') && (*(buf_ptr + 1) == '/'))
  {
 if (buf_ptr == buf_end)
--- a/src/args.c
+++ b/src/args.c
@@ -158,6 +158,7 @@
 static int exp_eei  = 0;
 static int exp_fc1  = 0;
 static int exp_fca  = 0;
+static int exp_fnc  = 0;
 static int exp_gnu  = 0;
 static int exp_hnl  = 0;
 static int exp_i= 0;
@@ -314,6 +315,7 @@
 {"hnl", PRO_BOOL,true,   ON, 
_newlines,  _hnl},
 {"h",   PRO_FUNCTION,   0, ONOFF_NA, (int *) 
usage,  _version},
 {"gnu", PRO_SETTINGS,   0, ONOFF_NA, 
GNU_SETTINGS_STRING,_gnu},
+{"fnc", PRO_BOOL,   false,   ON, 
_nested_comments,  _fnc},
 {"fca", PRO_BOOL,true,   ON, 
_comments,  _fca},
 {"fc1", PRO_BOOL,true,   ON, 
_col1_comments, _fc1},
 {"eei", PRO_BOOL,   false,   ON, 
_expression_indent,  _eei},
@@ -433,6 +435,7 @@
 {"h",   PRO_FUNCTION,   0, ONOFF_NA, (int *) 
usage,  _version},
 /* This is now the default. */
 {"gnu", PRO_SETTINGS,   0, ONOFF_NA, 
GNU_SETTINGS_STRING,_gnu},
+{"fnc", PRO_BOOL,   false,   ON, 
_nested_comments,  _fnc},
 {"fca", PRO_BOOL,   false,   ON, 
_comments,  _fca},
 {"fc1", PRO_BOOL,   false,   ON, 
_col1_comments, _fc1},
 {"eei", PRO_BOOL,   false,   ON, 
_expression_indent,  _eei},
@@ -548,6 +551,7 @@
 {"honour-newlines", "hnl"},
 {"help","h"},
 {"gnu-style",   "gnu"},
+{"fix-nested-comments", "fnc"},
 {"format-first-column-comments","fc1"},
 {"format-all-comments", "fca"},
 {"extra-expression-indentation","eei"},
--- a/src/indent.h
+++ b/src/indent.h
@@ -268,6 +268,7 @@
 int lineup_to_parens;/*!<  if 

Bug#726105: marked as done (indent: Incorrectly changes `!!` to `! !` when run with `-linux`)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:04:21 +
with message-id 
and subject line Bug#726105: fixed in indent 2.2.12-1
has caused the Debian Bug report #726105,
regarding indent: Incorrectly changes `!!` to `! !` when run with `-linux`
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.)


-- 
726105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: indent
Version: 2.2.11-4
Severity: normal
Tags: upstream

Dear Debian folks,


`indent -linux` changes `!!var` to `! !var`, which is incorrect [1].

but no space after unary operators:
&  *  +  -  ~  !  sizeof  typeof  alignof  __attribute__  
defined


Thanks,

Paul


PS: Upstream development seems to have ceased, as there are no replies
to messages to , so I guess it won’t be fixed soon
and I should probably look for an alternative to GNU Indent.


[1] 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/CodingStyle?id=b57a0505e750b3d7b2d39e9823b276d8ca1a08fe#n211

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.10-3-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages indent depends on:
ii  libc6  2.17-93

indent recommends no packages.

indent suggests no packages.

-- no debconf information


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: indent
Source-Version: 2.2.12-1

We believe that the bug you reported is fixed in the latest version of
indent, 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 726...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated indent 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: Sun, 27 Jan 2019 22:35:20 +0100
Source: indent
Architecture: source
Version: 2.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Closes: 228112 349065 487517 657461 726105 865677 916199
Changes:
 indent (2.2.12-1) unstable; urgency=low
 .
   * New upstream release. Closes: #916199.
 This is now maintained upstream by Andrej Shadura.
   * Drop all debian/patches/*, not required anymore.
   * Should fix '*' in function declaration. Closes: #228112.
   * Should fix double const after C++ function declaration. Closes: #349065.
   * Should improve support for gettext macros. Closes: #487517.
   * New option --fix-nested-comments. Closes: #657461.
   * Should not change !! to ! ! anymore when using -linux. Closes: #726105.
   * Should now cross-build. Closes: #865677.
   * Rules-Requires-Root: no.
Checksums-Sha1:
 36783e19c275da879687c9f2d8844c4d57402f64 1390 indent_2.2.12-1.dsc
 eecb3d7e78516d846af70e7bc86aabac9b92399c 620280 indent_2.2.12.orig.tar.xz
 d280f8b35975b8df52cd391411559234b5b97de7 5948 indent_2.2.12-1.debian.tar.xz
 9ae2b38a123edf27551aa324e0c184acab82ea84 4896 indent_2.2.12-1_source.buildinfo
Checksums-Sha256:
 e802796b98203d047d819685801bd970b20a6525836b35c5a9fd119eb7cf176d 1390 
indent_2.2.12-1.dsc
 b745a5dfc68f86a483d7f96dc1cda7aafd1e78ecba3c7d8ad304709e91e1defb 620280 
indent_2.2.12.orig.tar.xz
 d3ac4770ff8a0de2497a44c2a2d3e57521efb748620793bf531499565c50c5ea 5948 
indent_2.2.12-1.debian.tar.xz
 d62fde0178001f6517549001f78abba0c64d9a4c2bede1056b123610c9ed529e 4896 
indent_2.2.12-1_source.buildinfo
Files:
 235cbcac6f3c8e67d8c2ddf55ee33a3e 1390 devel optional indent_2.2.12-1.dsc
 9cba859a8b1958baa2e3dce1dadb37db 620280 devel optional 
indent_2.2.12.orig.tar.xz
 85039d044a9c085d5a506ff9ad66dd74 5948 devel optional 
indent_2.2.12-1.debian.tar.xz
 aa435f822003c88ec252181c36d9a3af 4896 devel optional 
indent_2.2.12-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAlxOKC4ACgkQQc5/C58b
izL00wf/Zm/3/RhTtw5rZ6s+9YDbDRoqBmbY2v1a06rWF0+rFRLHpGm1mKgwKwOf

Bug#865677: marked as done (indent FTCBFS: compiles build tool texinfo2man with the host architecture compiler)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:04:21 +
with message-id 
and subject line Bug#865677: fixed in indent 2.2.12-1
has caused the Debian Bug report #865677,
regarding indent FTCBFS: compiles build tool texinfo2man with the host 
architecture compiler
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.)


-- 
865677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: indent
Version: 2.2.11-5
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

indent almost cross compiles. It just fails executing texinfo2man, which
is a built tool. Unfortunately, it uses the host architecture compiler
for building texinfo2html. The attached patch fixes that. Please
consider applying it.

Helmut
diff --minimal -Nru indent-2.2.11/debian/changelog 
indent-2.2.11/debian/changelog
--- indent-2.2.11/debian/changelog  2017-01-10 17:50:20.0 +0100
+++ indent-2.2.11/debian/changelog  2017-06-23 18:32:56.0 +0200
@@ -1,3 +1,12 @@
+indent (2.2.11-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Closes: #-1.
+ + 05-cross.patch.
+ + autoreconf.
+
+ -- Helmut Grohne   Fri, 23 Jun 2017 18:32:56 +0200
+
 indent (2.2.11-5) unstable; urgency=medium
 
   * Drop 99-config-guess-config-sub, no longer needed when using dh
diff --minimal -Nru indent-2.2.11/debian/control indent-2.2.11/debian/control
--- indent-2.2.11/debian/control2017-01-10 16:00:00.0 +0100
+++ indent-2.2.11/debian/control2017-06-23 18:32:56.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Santiago Vila 
 Standards-Version: 3.9.8
-Build-Depends: gettext, texi2html, texinfo, debhelper (>=9)
+Build-Depends: gettext, texi2html, texinfo, debhelper (>=9), autoconf-archive, 
dh-autoreconf
 
 Package: indent
 Architecture: any
diff --minimal -Nru indent-2.2.11/debian/patches/05-cross.patch 
indent-2.2.11/debian/patches/05-cross.patch
--- indent-2.2.11/debian/patches/05-cross.patch 1970-01-01 01:00:00.0 
+0100
+++ indent-2.2.11/debian/patches/05-cross.patch 2017-06-23 18:32:54.0 
+0200
@@ -0,0 +1,39 @@
+From: Helmut Grohne 
+Subject: use the build architecture compiler for build tools
+
+Index: indent-2.2.11/man/Makefile.am
+===
+--- indent-2.2.11.orig/man/Makefile.am
 indent-2.2.11/man/Makefile.am
+@@ -1,15 +1,16 @@
+ mandir = @mandir@
+ 
+-bin_PROGRAMS = texinfo2man
+-texinfo2man_SOURCES = texinfo2man.c
+ man_MANS = @PACKAGE@.1
+ 
+-EXTRA_DIST = $(man_MANS) @pack...@.1.in
++EXTRA_DIST = texinfo2man.c $(man_MANS) @pack...@.1.in
+ 
+ # --- Maintainer's Section
+ 
+ MAINTAINERCLEANFILES = @PACKAGE@.1 Makefile.in texinfo2man 
+ 
++texinfo2man: texinfo2man.c
++  $(CC_FOR_BUILD) -o $@ ${srcdir}/texinfo2man.c
++
+ @PACKAGE@.1: ${srcdir}/@pack...@.1.in  ${srcdir}/../doc/@PACKAGE@.texinfo 
texinfo2man  Makefile.am
+   ./texinfo2man ${srcdir}/@pack...@.1.in 
${srcdir}/../doc/@PACKAGE@.texinfo > $@
+ 
+Index: indent-2.2.11/configure.ac
+===
+--- indent-2.2.11.orig/configure.ac
 indent-2.2.11/configure.ac
+@@ -11,6 +11,7 @@
+ AC_PROG_CC
+ AC_PROG_CPP
+ AC_PROG_INSTALL
++AX_CC_FOR_BUILD
+ 
+ AC_AIX
+ AC_MINIX
diff --minimal -Nru indent-2.2.11/debian/patches/series 
indent-2.2.11/debian/patches/series
--- indent-2.2.11/debian/patches/series 2017-01-10 16:00:00.0 +0100
+++ indent-2.2.11/debian/patches/series 2017-06-23 18:28:37.0 +0200
@@ -2,3 +2,4 @@
 02-use-lc-all-for-setlocale.patch
 03-manpage-in-section-1-not-in-section-1l.patch
 04-option-dj-does-not-take-a-parameter.patch
+05-cross.patch
diff --minimal -Nru indent-2.2.11/debian/rules indent-2.2.11/debian/rules
--- indent-2.2.11/debian/rules  2017-01-10 16:00:00.0 +0100
+++ indent-2.2.11/debian/rules  2017-06-23 18:32:56.0 +0200
@@ -1,6 +1,6 @@
 #!/usr/bin/make -f
 %:
-   dh $@
+   dh $@ --with=autoreconf
 
 package = indent
 
--- End Message ---
--- Begin Message ---
Source: indent
Source-Version: 2.2.12-1

We believe that the bug you reported is fixed in the latest version of
indent, 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 865...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance 

Bug#916199: marked as done (indent: Please package indent 2.2.12)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:04:21 +
with message-id 
and subject line Bug#916199: fixed in indent 2.2.12-1
has caused the Debian Bug report #916199,
regarding indent: Please package indent 2.2.12
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.)


-- 
916199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: indent
Version: 2.2.11-5
Severity: normal

Indent 2.2.12 has been released three months ago, it would be great if
you updated it in Debian just in time for the next Debian release.

-- 
Cheers,
  Andrej
--- End Message ---
--- Begin Message ---
Source: indent
Source-Version: 2.2.12-1

We believe that the bug you reported is fixed in the latest version of
indent, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated indent 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: Sun, 27 Jan 2019 22:35:20 +0100
Source: indent
Architecture: source
Version: 2.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Closes: 228112 349065 487517 657461 726105 865677 916199
Changes:
 indent (2.2.12-1) unstable; urgency=low
 .
   * New upstream release. Closes: #916199.
 This is now maintained upstream by Andrej Shadura.
   * Drop all debian/patches/*, not required anymore.
   * Should fix '*' in function declaration. Closes: #228112.
   * Should fix double const after C++ function declaration. Closes: #349065.
   * Should improve support for gettext macros. Closes: #487517.
   * New option --fix-nested-comments. Closes: #657461.
   * Should not change !! to ! ! anymore when using -linux. Closes: #726105.
   * Should now cross-build. Closes: #865677.
   * Rules-Requires-Root: no.
Checksums-Sha1:
 36783e19c275da879687c9f2d8844c4d57402f64 1390 indent_2.2.12-1.dsc
 eecb3d7e78516d846af70e7bc86aabac9b92399c 620280 indent_2.2.12.orig.tar.xz
 d280f8b35975b8df52cd391411559234b5b97de7 5948 indent_2.2.12-1.debian.tar.xz
 9ae2b38a123edf27551aa324e0c184acab82ea84 4896 indent_2.2.12-1_source.buildinfo
Checksums-Sha256:
 e802796b98203d047d819685801bd970b20a6525836b35c5a9fd119eb7cf176d 1390 
indent_2.2.12-1.dsc
 b745a5dfc68f86a483d7f96dc1cda7aafd1e78ecba3c7d8ad304709e91e1defb 620280 
indent_2.2.12.orig.tar.xz
 d3ac4770ff8a0de2497a44c2a2d3e57521efb748620793bf531499565c50c5ea 5948 
indent_2.2.12-1.debian.tar.xz
 d62fde0178001f6517549001f78abba0c64d9a4c2bede1056b123610c9ed529e 4896 
indent_2.2.12-1_source.buildinfo
Files:
 235cbcac6f3c8e67d8c2ddf55ee33a3e 1390 devel optional indent_2.2.12-1.dsc
 9cba859a8b1958baa2e3dce1dadb37db 620280 devel optional 
indent_2.2.12.orig.tar.xz
 85039d044a9c085d5a506ff9ad66dd74 5948 devel optional 
indent_2.2.12-1.debian.tar.xz
 aa435f822003c88ec252181c36d9a3af 4896 devel optional 
indent_2.2.12-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAlxOKC4ACgkQQc5/C58b
izL00wf/Zm/3/RhTtw5rZ6s+9YDbDRoqBmbY2v1a06rWF0+rFRLHpGm1mKgwKwOf
/VNSkobY+7a/SNda/rzWgHdDT+ekcAXh4VBc3UiG51BNOl9RTjauupDgLnccEVUt
mepPmLP2btWupN1mSAaHy1HIySV3miQbQYFMLo9/QlcO3eVu7ZPpFP5jy76iLqLT
pUYIDuw/4MCoUcAun//CF/KHshpONhCi1nx5Pa9rFsEidtlH1QIPalQUmvgvbnpQ
kqVLrcPR9TnpCPIniySTrfeAu53I3LSUkAgFtH9P2QHIQgMRCJSwEfCox3ZROaEL
x0lVS45qFVrvIqoPBXjVU3c1yXBVBQ==
=lz9b
-END PGP SIGNATURE End Message ---


Bug#487517: marked as done (indent: [rfe] better support for gettext macros)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 22:04:21 +
with message-id 
and subject line Bug#487517: fixed in indent 2.2.12-1
has caused the Debian Bug report #487517,
regarding indent: [rfe] better support for gettext macros
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.)


-- 
487517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: indent
Version: 2.2.9-7
Severity: wishlist
Tags: l10n

Hi,

At the GRASS GIS project (grass.osgeo.org) we are preparing to re-indent 
our c. 1M SLOC codebase. Trials have shown that indent sometimes does 
not do well with the _("") gettext macros used for i18n of messages.
For example,

indent produces:
 G_fatal_error
(_
 ("Can't get projection info of current location

better would be to break lines like:
 G_fatal_error(
_("Can't get projection info 



CLI rules used:
$ indent -bad -bap -bbb -br -bli0 -bls -cli0 -ncs -fc1 -hnl -i4 \
-nbbo -nbc -nbfda -nbfde -ncdb -ncdw -nce -nfca -npcs -nprs \
-npsl -nsc -nsob -saf -sai -saw -sbi0 -ss -ts8 -ut main.c

Example code which upon indent'ing shows the behaviour:
  http://trac.osgeo.org/grass/browser/grass/trunk/raster/r.sun/main.c

refs:
  http://thread.gmane.org/gmane.comp.gis.grass.devel/26820/focus=27382
  http://trac.osgeo.org/grass/browser/grass/trunk/SUBMITTING#L229



thanks,
Hamish


--- End Message ---
--- Begin Message ---
Source: indent
Source-Version: 2.2.12-1

We believe that the bug you reported is fixed in the latest version of
indent, 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 487...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated indent 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: Sun, 27 Jan 2019 22:35:20 +0100
Source: indent
Architecture: source
Version: 2.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Closes: 228112 349065 487517 657461 726105 865677 916199
Changes:
 indent (2.2.12-1) unstable; urgency=low
 .
   * New upstream release. Closes: #916199.
 This is now maintained upstream by Andrej Shadura.
   * Drop all debian/patches/*, not required anymore.
   * Should fix '*' in function declaration. Closes: #228112.
   * Should fix double const after C++ function declaration. Closes: #349065.
   * Should improve support for gettext macros. Closes: #487517.
   * New option --fix-nested-comments. Closes: #657461.
   * Should not change !! to ! ! anymore when using -linux. Closes: #726105.
   * Should now cross-build. Closes: #865677.
   * Rules-Requires-Root: no.
Checksums-Sha1:
 36783e19c275da879687c9f2d8844c4d57402f64 1390 indent_2.2.12-1.dsc
 eecb3d7e78516d846af70e7bc86aabac9b92399c 620280 indent_2.2.12.orig.tar.xz
 d280f8b35975b8df52cd391411559234b5b97de7 5948 indent_2.2.12-1.debian.tar.xz
 9ae2b38a123edf27551aa324e0c184acab82ea84 4896 indent_2.2.12-1_source.buildinfo
Checksums-Sha256:
 e802796b98203d047d819685801bd970b20a6525836b35c5a9fd119eb7cf176d 1390 
indent_2.2.12-1.dsc
 b745a5dfc68f86a483d7f96dc1cda7aafd1e78ecba3c7d8ad304709e91e1defb 620280 
indent_2.2.12.orig.tar.xz
 d3ac4770ff8a0de2497a44c2a2d3e57521efb748620793bf531499565c50c5ea 5948 
indent_2.2.12-1.debian.tar.xz
 d62fde0178001f6517549001f78abba0c64d9a4c2bede1056b123610c9ed529e 4896 
indent_2.2.12-1_source.buildinfo
Files:
 235cbcac6f3c8e67d8c2ddf55ee33a3e 1390 devel optional indent_2.2.12-1.dsc
 9cba859a8b1958baa2e3dce1dadb37db 620280 devel optional 
indent_2.2.12.orig.tar.xz
 85039d044a9c085d5a506ff9ad66dd74 5948 devel optional 
indent_2.2.12-1.debian.tar.xz
 aa435f822003c88ec252181c36d9a3af 4896 devel optional 
indent_2.2.12-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAlxOKC4ACgkQQc5/C58b
izL00wf/Zm/3/RhTtw5rZ6s+9YDbDRoqBmbY2v1a06rWF0+rFRLHpGm1mKgwKwOf
/VNSkobY+7a/SNda/rzWgHdDT+ekcAXh4VBc3UiG51BNOl9RTjauupDgLnccEVUt
mepPmLP2btWupN1mSAaHy1HIySV3miQbQYFMLo9/QlcO3eVu7ZPpFP5jy76iLqLT
pUYIDuw/4MCoUcAun//CF/KHshpONhCi1nx5Pa9rFsEidtlH1QIPalQUmvgvbnpQ

Bug#920606: marked as done (transifex-client: Depends: python3-six (= 1.11.0) but 1.12.0-1 is to be installed)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 21:35:18 +
with message-id 
and subject line Bug#920606: fixed in transifex-client 0.13.5-2
has caused the Debian Bug report #920606,
regarding transifex-client: Depends: python3-six (= 1.11.0) but 1.12.0-1 is to 
be installed
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.)


-- 
920606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: transifex-client
Version: 0.13.5-1
Severity: serious

The following packages have unmet dependencies:
 transifex-client : Depends: python3-six (= 1.11.0) but 1.12.0-1 is to be 
installed
--- End Message ---
--- Begin Message ---
Source: transifex-client
Source-Version: 0.13.5-2

We believe that the bug you reported is fixed in the latest version of
transifex-client, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated transifex-client 
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: Sun, 27 Jan 2019 20:58:59 +
Source: transifex-client
Binary: transifex-client
Architecture: source all
Version: 0.13.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Hans-Christoph Steiner 
Description:
 transifex-client - Command line interface for Transifex
Closes: 920606
Changes:
 transifex-client (0.13.5-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
 .
   [ Hans-Christoph Steiner ]
   * Standards-Version: 4.3.0: remove get-orig-source
   * add autopkgtest smoke test
   * patch to allow using Debian's python3-six version (Closes: #920606)
Checksums-Sha1:
 1a769da8440c9f270cfff250dd3def4b13537464 1857 transifex-client_0.13.5-2.dsc
 d89dd4466309b369f2fd692866dccb1c9fcc52df 4832 
transifex-client_0.13.5-2.debian.tar.xz
 9c7ca9ee4d2049dd5ceab4e5b8dde9499220b107 166820 
transifex-client_0.13.5-2_all.deb
 925891969091d90171b97e4a10b426b9637db314 6515 
transifex-client_0.13.5-2_amd64.buildinfo
Checksums-Sha256:
 faeb06ae9d795228e48f9ff1e2acaa0ad096b830bf1cdc0b87db76ecf8157c7d 1857 
transifex-client_0.13.5-2.dsc
 4d0d8704a4e509498ad30c8d86906347b90eb30c5572305e19a078292ae000ae 4832 
transifex-client_0.13.5-2.debian.tar.xz
 b1c4d6ce36b45f86cbb591c11b4fce542b5550e2a56f07cb3a1d361a10332b99 166820 
transifex-client_0.13.5-2_all.deb
 b7413f43a0cb83ab37596c53e77a799db2dee97bfdb54fc944c591e0a22e964a 6515 
transifex-client_0.13.5-2_amd64.buildinfo
Files:
 afd4ffdf7808d23a1f4295e0b35db077 1857 devel optional 
transifex-client_0.13.5-2.dsc
 8985c33d1349047609adba31543fc9c1 4832 devel optional 
transifex-client_0.13.5-2.debian.tar.xz
 7b5a848d85daf4baaf87e49479f1c350 166820 devel optional 
transifex-client_0.13.5-2_all.deb
 998a40e613772cc23f5d40e49e0dda4e 6515 devel optional 
transifex-client_0.13.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPG for Android - https://guardianproject.info/code/gnupg/

iQEcBAEBCAAGBQJcTh12AAoJED4XeBe6G5v6PLcH/iN55NIv6jpCdCQ8YKpk261x
UCMBt0jz74nxUUUHB1Yw5xmYlPPLEe6q9ka9unwbnPOQlTi+25UV2P4PoWoDsMnx
68fgY51m3Z1vypkffxbR8i9+d48LH/XW83o0m0/R4ewQjNq1jyT9Hiwf3NpY17nD
IoLQ9fQZPNQwzWTx5vN0G31rPv/q9Y99cQVbBYYRr1rxooxGlgtg5RZbSQaDeNIZ
kJhVMND7uL0FmvTYAFntyhiirtHIu6hf7Apd+G1CtDXS4K+s/MjlC6vZ0xsfhAdW
2WQjk82OefONtsq/J+eWXVbrLL+HnSAaiTYw8a4KUCzN6JJGiXcDdFZEF7c9s1g=
=sGAq
-END PGP SIGNATURE End Message ---


Bug#759173: marked as done (ocamlgraph: [INTL:pt] Updated Portuguese translation of manpage)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 21:20:13 +
with message-id 
and subject line Bug#759173: fixed in ocamlgraph 1.8.8-1.1
has caused the Debian Bug report #759173,
regarding ocamlgraph: [INTL:pt] Updated Portuguese translation of manpage
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.)


-- 
759173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ocamlgraph
Version: 1.8.5-1
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for ocamlgraph's manpage.
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro


ocamlgraph_1.8.5-1_ocamlgraph-man.pt.po.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: ocamlgraph
Source-Version: 1.8.8-1.1

We believe that the bug you reported is fixed in the latest version of
ocamlgraph, 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 759...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Helge Kreutzmann  (supplier of updated ocamlgraph 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: Sun, 23 Dec 2018 07:42:45 +0100
Source: ocamlgraph
Architecture: source
Version: 1.8.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Helge Kreutzmann 
Closes: 759173 866145
Changes:
 ocamlgraph (1.8.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add German man page translation. Closes: #866145.
   * Add Portuguese man page translation. Closes: #759173.
   * Add infrastructure to actually build and install all manpages, including
 the english one. Taken from package camomile.
Checksums-Sha1:
 8b7323acc31bd972dc1713e725cc804b028a232f 2167 ocamlgraph_1.8.8-1.1.dsc
 1f18dcd96b25e211e3910b2b4447062fc8019c65 13804 
ocamlgraph_1.8.8-1.1.debian.tar.xz
 8489ba36f7d89d42a7574874969914529d36e0ae 6737 
ocamlgraph_1.8.8-1.1_amd64.buildinfo
Checksums-Sha256:
 afb2cb0abeab2ddab37924c529568d6e6450af4a04b4fad8c34dbd4d4be444c0 2167 
ocamlgraph_1.8.8-1.1.dsc
 fcc00a1faa6ad64c5350d2ae5ab030d835918b706512fdd18b4d920599da7229 13804 
ocamlgraph_1.8.8-1.1.debian.tar.xz
 1a1c123ef57607980349bda88f9edbaa6af7fc3119e2db23a58e0ca6ffe6566c 6737 
ocamlgraph_1.8.8-1.1_amd64.buildinfo
Files:
 e8b5af55c01577894d70b23b7d7f245a 2167 libdevel optional 
ocamlgraph_1.8.8-1.1.dsc
 a146f3844ba47d0fdb154ceac820f8cc 13804 libdevel optional 
ocamlgraph_1.8.8-1.1.debian.tar.xz
 2e472a8b0e61aec9f85060c4ee1ad4dc 6737 libdevel optional 
ocamlgraph_1.8.8-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxOGpUACgkQEwLx8Dbr
6xksTA//eGptSZRDmV1ArhUnfyvyXx7xOI4Bp0kZVuMH1Y14eKkoRZIdaQuGYYpU
pTiliNy3dmSsMYg3AYCQBi/HXTNWNcLXyj/Jz2fmBnuCS1EdYUQrq/3KyL8mUwcW
2MJYX35mv8AASE3Lb+OjdHVRs64gpjDwmizNLfiCkpFvxcoF0zRhbKtLUO98K3X4
k4lSzokwM2+UE8ZlJ6n2LrSnqUBffkSvMEZmbtp8j24VS3PuN83Ple9khbWEO0t9
5ePx50XyOuXf5Ceqofu+ObdBA82fhyJkJQLwK0HpUjhcxRXn76/TyolKJNdmrIcE
X23YKokota+DnB8IxaH5UQLUU8Py4I3IFr3hWxrpUtIYYacZVsDYsfPrhBI1qI9u
9ywPjHzF2SxJ+AFTfxluSqIpwNhZNIMpWJcO5j3q6tm2HMdvUVaD+W9wCkWi13J8
NJhu/wzO4F7X4F3EVh7Cc7y1t/7ceUDiGNeN5rMpyGCcnDFwoLCYoK6anNWYsxsh
5wxkPlcgzdYSheXxIWaAIjZUZBthPXcsIG3LSFwa5SwZDIo8Vv5OzE06g/Dnz4K0
LhVoVoJihuRJOIMTfqrXYQCgF2NMp6rqbXj5ifxw3V6LI3eIoh5G2UYGZ53U3AOK
B5x+ehzsvAy8dggEmu37oxR/AwMdFOfeI2UB3Y2qiz8x5IKJdbo=
=LSYJ
-END PGP SIGNATURE End Message ---


Bug#866145: marked as done (ocamlgraph: [INTL:de] Initial German po4a translation)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 21:20:13 +
with message-id 
and subject line Bug#866145: fixed in ocamlgraph 1.8.8-1.1
has caused the Debian Bug report #866145,
regarding ocamlgraph: [INTL:de] Initial German po4a translation
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.)


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

Package: ocamlgraph
Version: 1.8.6-1
Severity: wishlist
Tags: l10n patch



Hi,

please find attached the initial German po4a translation.

Kind regards,
Chris


de.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ocamlgraph
Source-Version: 1.8.8-1.1

We believe that the bug you reported is fixed in the latest version of
ocamlgraph, 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 866...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Helge Kreutzmann  (supplier of updated ocamlgraph 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: Sun, 23 Dec 2018 07:42:45 +0100
Source: ocamlgraph
Architecture: source
Version: 1.8.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Helge Kreutzmann 
Closes: 759173 866145
Changes:
 ocamlgraph (1.8.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add German man page translation. Closes: #866145.
   * Add Portuguese man page translation. Closes: #759173.
   * Add infrastructure to actually build and install all manpages, including
 the english one. Taken from package camomile.
Checksums-Sha1:
 8b7323acc31bd972dc1713e725cc804b028a232f 2167 ocamlgraph_1.8.8-1.1.dsc
 1f18dcd96b25e211e3910b2b4447062fc8019c65 13804 
ocamlgraph_1.8.8-1.1.debian.tar.xz
 8489ba36f7d89d42a7574874969914529d36e0ae 6737 
ocamlgraph_1.8.8-1.1_amd64.buildinfo
Checksums-Sha256:
 afb2cb0abeab2ddab37924c529568d6e6450af4a04b4fad8c34dbd4d4be444c0 2167 
ocamlgraph_1.8.8-1.1.dsc
 fcc00a1faa6ad64c5350d2ae5ab030d835918b706512fdd18b4d920599da7229 13804 
ocamlgraph_1.8.8-1.1.debian.tar.xz
 1a1c123ef57607980349bda88f9edbaa6af7fc3119e2db23a58e0ca6ffe6566c 6737 
ocamlgraph_1.8.8-1.1_amd64.buildinfo
Files:
 e8b5af55c01577894d70b23b7d7f245a 2167 libdevel optional 
ocamlgraph_1.8.8-1.1.dsc
 a146f3844ba47d0fdb154ceac820f8cc 13804 libdevel optional 
ocamlgraph_1.8.8-1.1.debian.tar.xz
 2e472a8b0e61aec9f85060c4ee1ad4dc 6737 libdevel optional 
ocamlgraph_1.8.8-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxOGpUACgkQEwLx8Dbr
6xksTA//eGptSZRDmV1ArhUnfyvyXx7xOI4Bp0kZVuMH1Y14eKkoRZIdaQuGYYpU
pTiliNy3dmSsMYg3AYCQBi/HXTNWNcLXyj/Jz2fmBnuCS1EdYUQrq/3KyL8mUwcW
2MJYX35mv8AASE3Lb+OjdHVRs64gpjDwmizNLfiCkpFvxcoF0zRhbKtLUO98K3X4
k4lSzokwM2+UE8ZlJ6n2LrSnqUBffkSvMEZmbtp8j24VS3PuN83Ple9khbWEO0t9
5ePx50XyOuXf5Ceqofu+ObdBA82fhyJkJQLwK0HpUjhcxRXn76/TyolKJNdmrIcE
X23YKokota+DnB8IxaH5UQLUU8Py4I3IFr3hWxrpUtIYYacZVsDYsfPrhBI1qI9u
9ywPjHzF2SxJ+AFTfxluSqIpwNhZNIMpWJcO5j3q6tm2HMdvUVaD+W9wCkWi13J8
NJhu/wzO4F7X4F3EVh7Cc7y1t/7ceUDiGNeN5rMpyGCcnDFwoLCYoK6anNWYsxsh
5wxkPlcgzdYSheXxIWaAIjZUZBthPXcsIG3LSFwa5SwZDIo8Vv5OzE06g/Dnz4K0
LhVoVoJihuRJOIMTfqrXYQCgF2NMp6rqbXj5ifxw3V6LI3eIoh5G2UYGZ53U3AOK
B5x+ehzsvAy8dggEmu37oxR/AwMdFOfeI2UB3Y2qiz8x5IKJdbo=
=LSYJ
-END PGP SIGNATURE End Message ---


Bug#492932: marked as done (Clarify contents in description)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 21:19:09 +
with message-id 
and subject line Bug#492932: fixed in context-nonfree 2007.03.22-1.1
has caused the Debian Bug report #492932,
regarding Clarify contents in description
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.)


-- 
492932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: context-nonfree
Version: 2007.03.22-1
Severity: wishlist

Hi!

context-nonfree's description is as follows:

`The ConTeXt distribution contains some fonts that are not considered free from
Debian perspective, which are included here.'

I would add a sentence, something like:

`Currently it only contains the Hoekwater "koeieletters" font.'


Cheerio


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

Kernel: Linux 2.6.25-odysseus (PREEMPT)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


--- End Message ---
--- Begin Message ---
Source: context-nonfree
Source-Version: 2007.03.22-1.1

We believe that the bug you reported is fixed in the latest version of
context-nonfree, 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 492...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated context-nonfree 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: Sun, 27 Jan 2019 15:42:10 -0500
Source: context-nonfree
Binary: context-nonfree
Architecture: source all
Version: 2007.03.22-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX maintainers 
Changed-By: Boyuan Yang 
Description:
 context-nonfree - Non-free items from the ConTeXt distribution
Closes: 492932
Changes:
 context-nonfree (2007.03.22-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for Debian Buster.
 + Solves no-strong-digests-in-dsc. (lintian)
   * debian/control:
 + Clarify contents in description. (Closes: #492932)
 + Add binary package dependency on ${misc:Depends}. (lintian)
 + Declare compliance with debian-policy 4.3.0. (lintian)
 + Bump debhelper compat to v12. (lintian)
   * debian/compat: Removed in favour of using debhelper-compat.
   * debian/source/format: Use "3.0 (quilt)" format. (lintian)
   * debian/context-nonfree.lintian-overrides: Add override for
 non-free fonts (license-problem-font-adobe-copyrighted-fragment).
   * debian/rules:
 + Update and use debhelper dh syntax.
 + Move manual install instructions into debian/*.install files.
 + Use "dh_missing --fail-missing".
Checksums-Sha1:
 6a741d942555c1c661edde6ba21ee393781be945 1899 
context-nonfree_2007.03.22-1.1.dsc
 1bf3c4c54b4fa70f9976a7a091d3ee09d9d535a3 679951 
context-nonfree_2007.03.22.orig.tar.gz
 fe1692e06dccc00a6c5477d52c2ac12e3122ac77 1872 
context-nonfree_2007.03.22-1.1.debian.tar.xz
 8635b02fddbc2107071ae24473eaea27f96dcde3 672660 
context-nonfree_2007.03.22-1.1_all.deb
 e9f1c5eb7231df9b1fae1c265dec86e2a989058e 5434 
context-nonfree_2007.03.22-1.1_amd64.buildinfo
Checksums-Sha256:
 ea65874630d92983a66b78542a9d58e6615516fb03eb1c0e56169b28be1c48a4 1899 
context-nonfree_2007.03.22-1.1.dsc
 a856a21f978d351a5b918cb99a4807af085ab8f5af43f2ecea7b4bd4b67a2aa9 679951 
context-nonfree_2007.03.22.orig.tar.gz
 53c1b1c2cb962683e97423c90c333a9d3bf0f9dab31dd20082cac9458506ecdf 1872 
context-nonfree_2007.03.22-1.1.debian.tar.xz
 9bbb3827e8f0f19d65126a1207ab53892ef9d33ff7a6d46324c3fe20e3e18c2a 672660 
context-nonfree_2007.03.22-1.1_all.deb
 923fab461ec8ee445e6002e1befd1c37b40a7d63aabdd50bb831eb371e0a 5434 
context-nonfree_2007.03.22-1.1_amd64.buildinfo
Files:
 dce41f1fbc9f53c09e04623823d5ce08 1899 non-free/tex optional 
context-nonfree_2007.03.22-1.1.dsc
 8624700528c428940cb3db2db98f3f28 679951 non-free/tex optional 
context-nonfree_2007.03.22.orig.tar.gz
 41a1c5af0c65425a2f7ce499c89af89e 1872 non-free/tex optional 
context-nonfree_2007.03.22-1.1.debian.tar.xz
 f3e6c430e730f303d1edf8d0b3b1c57e 672660 non-free/tex optional 
context-nonfree_2007.03.22-1.1_all.deb
 

Bug#778384: marked as done (fookebox: [INTL:it] Italian translation of debconf messages)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 21:04:08 +
with message-id 
and subject line Bug#778384: fixed in fookebox 0.7.2-3
has caused the Debian Bug report #778384,
regarding fookebox: [INTL:it] Italian translation of debconf messages
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.)


-- 
778384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fookebox
Severity: wishlist
Tags: l10n patch

Hi.

Please find attached the Italian translation of fookebox debconf messages
proofread by the Italian localization team.

Please include it in your next upload.

Thanks,
Beatrice
# Italian translation of fookebox debconf messages
# Copyright (C) 2014 fookebox package's copyright holder
# This file is distributed under the same license as the fookebox package.
# Beatrice Torracca , 2015.
msgid ""
msgstr ""
"Project-Id-Version: fookebox\n"
"Report-Msgid-Bugs-To: fooke...@packages.debian.org\n"
"POT-Creation-Date: 2014-11-02 06:06+0100\n"
"PO-Revision-Date: 2015-01-23 08:34+0200\n"
"Last-Translator: Beatrice Torracca \n"
"Language-Team: Italian \n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Virtaal 0.7.1\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Remove old fookebox database?"
msgstr "Rimuovere il vecchio database di fookebox?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Previous versions of fookebox used a database to store schedule information. "
"This database is no longer used and can be safely removed."
msgstr ""
"Le versioni precedenti di fookebox usavano un database per memorizzare le "
"informazioni sulla pianificazione. Questo database non è più usato e può "
"essere rimosso senza problemi."
--- End Message ---
--- Begin Message ---
Source: fookebox
Source-Version: 0.7.2-3

We believe that the bug you reported is fixed in the latest version of
fookebox, 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 778...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Helge Kreutzmann  (supplier of updated fookebox 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: Sat, 26 Jan 2019 14:55:14 +0100
Source: fookebox
Architecture: source
Version: 0.7.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Helge Kreutzmann 
Closes: 778384
Changes:
 fookebox (0.7.2-3) unstable; urgency=medium
 .
   * QA upload
   * Add Italian Debconf translation. Thanks Beatrice Torracca. Closes: #778384
Checksums-Sha1:
 5040502ba6e452075ce350e093610afacfb46c5a 1782 fookebox_0.7.2-3.dsc
 b9abaa118b5d164ac42b62bf1d3e8f6ffedbdad8 35972 fookebox_0.7.2-3.debian.tar.xz
 b0c437645e52207a3678df8a1c5b832a6dab0053 6168 fookebox_0.7.2-3_amd64.buildinfo
Checksums-Sha256:
 aad8ce93a8b0aed615808d763142f0c7b0a41a1c7c4e4b85225a26e28f668457 1782 
fookebox_0.7.2-3.dsc
 abad21a8ff6904a6509389e348cfe2366e831577fd829b8266f79da68a6c188f 35972 
fookebox_0.7.2-3.debian.tar.xz
 90ee7a0a7ff5bd98048e54ca497419529a6a90aa2712bd088a22d0df6f25b024 6168 
fookebox_0.7.2-3_amd64.buildinfo
Files:
 47f6feb800729a558b2c03f73dd8f9f6 1782 web optional fookebox_0.7.2-3.dsc
 91fb741d98b2216ddb54b7f75814bb02 35972 web optional 
fookebox_0.7.2-3.debian.tar.xz
 0533393c52d21f322e43279df89a9082 6168 web optional 
fookebox_0.7.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxOGI4ACgkQEwLx8Dbr
6xn73A//dpPuDdjclDc2ca4Mx7dJwX/JbXDpsSkP5szdt5lXyhPnif4iizLEk9t9
VCrVncQQDwd0ahYi7ysPIp7rdVdtZIsWE0ztJPOZ2vRxH0BEmJPXPn/nNfw8tLcw
VOsdYoNrSR/eJkBCUE05UyooUQLEWs/G99aWXxm+N/UgGGIZxnSnKCUF6ElsiXV0
wegJ0SLRPiOXnbXgHYJLLVWP0z84V2ZEvgbjTrPnx57D8QvyaZHrFk1ayKR+iLm6
VAglgnzXv3+qbSiI8boS1kOrF01VAKcrh3hhTiMuBFqTBlgkbFUXokPwboWSeBs4
TKGEkAvnYwbVyO86oPH/bT+7hKOxIihlMXpUKVNDHLwbxVz0e1A/LQRf/7jkG4Bm
k1X6x2ttJQBZXXGdqtLyvndX8mgVUv3EwRbTn+PmUWJ+s0mUK2eM4wVLhnofKQTv
vHg9uow23W4Dh71ZkEsFaowOO3Og+R75fVZtwHXjcktCV1LaQlIfd9vVF0m5dzW0
vEPsxmYMv8ODZLg67sv4MUjAFDBVDQ0933CM23gEBX4ku50clA1b8cmnhUnDbKtG

Bug#866436: marked as done (keysync: depends on obsolete python-imaging (replace with python3-pil or python-pil))

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 20:43:32 +
with message-id 
and subject line Bug#866436: fixed in keysync 0.2.2-2
has caused the Debian Bug report #866436,
regarding keysync: depends on obsolete python-imaging (replace with python3-pil 
or python-pil)
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.)


-- 
866436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:keysync
Version: 0.2.2-1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Source: keysync
Source-Version: 0.2.2-2

We believe that the bug you reported is fixed in the latest version of
keysync, 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 866...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated keysync 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: Sun, 27 Jan 2019 19:34:52 +
Source: keysync
Binary: keysync
Architecture: source all
Version: 0.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Hans-Christoph Steiner 
Changed-By: Hans-Christoph Steiner 
Description:
 keysync- Syncs OTR identities between the different chat programs
Closes: 820370 866436
Changes:
 keysync (0.2.2-2) unstable; urgency=medium
 .
   * Standards-Version: 4.3.0 no changes
   * switch imaging to pil (Closes: #866436)
   * switch to Section: utils (Closes: #820370)
   * W: dh_python2:479: Please add dh-python package to Build-Depends
   * update Vcs tags to point to salsa.debian.org
Checksums-Sha1:
 f80451d391e862ede59170fb324469748c0359c9 1689 keysync_0.2.2-2.dsc
 02b15af519b367ec3a5c0bd1d4b3cfa0fc0b6501 112532 keysync_0.2.2-2.debian.tar.xz
 6098912088895833d83d94f918ebff435e304614 789640 keysync_0.2.2-2_all.deb
 793accfb647acb7366383de0edac0f9104c0e9a6 6321 keysync_0.2.2-2_amd64.buildinfo
Checksums-Sha256:
 590d0f2991a95d8b440ecb2a705b318fb69b848069d67e5a733c613341333e7f 1689 
keysync_0.2.2-2.dsc
 a20238ed66362a17f6964f1e0a27233d14644492d2c2791deec9524cfc1f093c 112532 
keysync_0.2.2-2.debian.tar.xz
 70e9df69c7f0966111b6cf19e44f915a119aad9f3d75721c7874c5efa76cecda 789640 
keysync_0.2.2-2_all.deb
 e6cae4ee78d2a25564b0e16fa861e49173a327a84825da056bf251856d7af9ad 6321 
keysync_0.2.2-2_amd64.buildinfo
Files:
 f61979cfb67bf973a01dafbd4304b3ad 1689 utils optional keysync_0.2.2-2.dsc
 30963d7431f42f10118996661fce6c25 112532 utils optional 
keysync_0.2.2-2.debian.tar.xz
 88ae0bafd2f2eed93da42c50b5a85500 789640 utils optional keysync_0.2.2-2_all.deb
 d207dbca6b1c2e6d2362fdb999339e65 6321 utils optional 
keysync_0.2.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPG for Android - https://guardianproject.info/code/gnupg/

iQEcBAEBCAAGBQJcTg75AAoJED4XeBe6G5v6aMUH/jATUxkDSdh4k3nfkaR+u/Wc
gMm/dGnb3yT0bXS/EHtBf1zSNx7VtiCHZbpCyZQ5CyW1DigPDrimFr03ymnDGaV9
87mvtJSss0CmFqnsGMsoDn8xzxeca46Y8qYDhdC4g7zARrserBFgxwrWR4ykLb0q
jhPCFyANCeOLc4wSru/BTxJEnnhLzSE7tDUkS2g9+Q/dYD1SXXx8qCa0AHSN8zfL
OegLAwmLYjrgp3ReUdgx3vOkv++AzEcK4FsMngBHk8G7eK4K6V1JTadp2+qZSCVi
WtPI1cscik48PQrbCY/gRy+nm3B5hymux/Qu23UgELYcqoA27NkGirKAt5dE2fc=
=x0C2
-END PGP SIGNATURE End Message ---


Bug#820370: marked as done (keysync: Section should not be “python”)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 20:43:32 +
with message-id 
and subject line Bug#820370: fixed in keysync 0.2.2-2
has caused the Debian Bug report #820370,
regarding keysync: Section should not be “python”
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.)


-- 
820370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: keysync
Version: 0.2.2-1
Severity: minor

Dear Maintainer,

The section “python” is for packages that install the Python
programming language or libraries. Its packages are primarily of
interest only to Python programmers.

The package ‘keysync’ installs primarily an application, of interest
regardless of the programming language. It should not be in the
“python” section.

By the section descriptions, this package may belong in section “net”.

Please set the field “Section” appropriately on this package.


Since the package is already in Debian with a different section, you
will also need to submit a request to override the existing section
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#override-file>.

Then mark this bug report as blocked by that new one.

-- 
 \ “Pinky, are you pondering what I'm pondering?” “Uh, I think so, |
  `\  Brain, but balancing a family and a career ... ooh, it's all |
_o__) too much for me.” —_Pinky and The Brain_ |
Ben Finney 
--- End Message ---
--- Begin Message ---
Source: keysync
Source-Version: 0.2.2-2

We believe that the bug you reported is fixed in the latest version of
keysync, 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 820...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated keysync 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: Sun, 27 Jan 2019 19:34:52 +
Source: keysync
Binary: keysync
Architecture: source all
Version: 0.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Hans-Christoph Steiner 
Changed-By: Hans-Christoph Steiner 
Description:
 keysync- Syncs OTR identities between the different chat programs
Closes: 820370 866436
Changes:
 keysync (0.2.2-2) unstable; urgency=medium
 .
   * Standards-Version: 4.3.0 no changes
   * switch imaging to pil (Closes: #866436)
   * switch to Section: utils (Closes: #820370)
   * W: dh_python2:479: Please add dh-python package to Build-Depends
   * update Vcs tags to point to salsa.debian.org
Checksums-Sha1:
 f80451d391e862ede59170fb324469748c0359c9 1689 keysync_0.2.2-2.dsc
 02b15af519b367ec3a5c0bd1d4b3cfa0fc0b6501 112532 keysync_0.2.2-2.debian.tar.xz
 6098912088895833d83d94f918ebff435e304614 789640 keysync_0.2.2-2_all.deb
 793accfb647acb7366383de0edac0f9104c0e9a6 6321 keysync_0.2.2-2_amd64.buildinfo
Checksums-Sha256:
 590d0f2991a95d8b440ecb2a705b318fb69b848069d67e5a733c613341333e7f 1689 
keysync_0.2.2-2.dsc
 a20238ed66362a17f6964f1e0a27233d14644492d2c2791deec9524cfc1f093c 112532 
keysync_0.2.2-2.debian.tar.xz
 70e9df69c7f0966111b6cf19e44f915a119aad9f3d75721c7874c5efa76cecda 789640 
keysync_0.2.2-2_all.deb
 e6cae4ee78d2a25564b0e16fa861e49173a327a84825da056bf251856d7af9ad 6321 
keysync_0.2.2-2_amd64.buildinfo
Files:
 f61979cfb67bf973a01dafbd4304b3ad 1689 utils optional keysync_0.2.2-2.dsc
 30963d7431f42f10118996661fce6c25 112532 utils optional 
keysync_0.2.2-2.debian.tar.xz
 88ae0bafd2f2eed93da42c50b5a85500 789640 utils optional keysync_0.2.2-2_all.deb
 d207dbca6b1c2e6d2362fdb999339e65 6321 utils optional 
keysync_0.2.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPG for Android - https://guardianproject.info/code/gnupg/

iQEcBAEBCAAGBQJcTg75AAoJED4XeBe6G5v6aMUH/jATUxkDSdh4k3nfkaR+u/Wc
gMm/dGnb3yT0bXS/EHtBf1zSNx7VtiCHZbpCyZQ5CyW1DigPDrimFr03ymnDGaV9
87mvtJSss0CmFqnsGMsoDn8xzxeca46Y8qYDhdC4g7zARrserBFgxwrWR4ykLb0q
jhPCFyANCeOLc4wSru/BTxJEnnhLzSE7tDUkS2g9+Q/dYD1SXXx8qCa0AHSN8zfL
OegLAwmLYjrgp3ReUdgx3vOkv++AzEcK4FsMngBHk8G7eK4K6V1JTadp2+qZSCVi
WtPI1cscik48PQrbCY/gRy+nm3B5hymux/Qu23UgELYcqoA27NkGirKAt5dE2fc=
=x0C2
-END PGP SIGNATURE End Message ---


Processed (with 2 errors): Second attempt to merge bugs

2019-01-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unblock 807848 by 818115
Failed to set blocking bugs of 807848: Not altering archived bugs; see 
unarchive.

> close 818115
Bug #818115 [src:sphinx] turn python-sphinx into an arch:any package
Marked Bug as done
> merge 818115 915856
Bug #818115 {Done: Dmitry Shachnev } [src:sphinx] turn 
python-sphinx into an arch:any package
Unable to merge bugs because:
blocks of #915856 is '' not '807848'
Failed to merge 818115: Did not alter merged bugs.

> thanks
Stopping processing here.

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



Processed: closing 919324

2019-01-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 919324 1.2.0.9000-1
Bug #919324 [r-cran-readxl] CVE-2018-20450 CVE-2018-20452
Marked as fixed in versions r-cran-readxl/1.2.0.9000-1.
Bug #919324 [r-cran-readxl] CVE-2018-20450 CVE-2018-20452
Marked Bug as done
> thanks
Stopping processing here.

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



Processed (with 1 error): Re: Bug#915856: sphinx: Failed cross building with Build-Depends on python3-sphinx

2019-01-27 Thread Debian Bug Tracking System
Processing control commands:

> reassign 818115 src:sphinx 1.4.9-2
Bug #818115 [python-sphinx] turn python-sphinx into an arch:any package
Bug reassigned from package 'python-sphinx' to 'src:sphinx'.
No longer marked as found in versions sphinx/1.3.6-2.
Ignoring request to alter fixed versions of bug #818115 to the same values 
previously set
Bug #818115 [src:sphinx] turn python-sphinx into an arch:any package
Marked as found in versions sphinx/1.4.9-2.
> merge 818115 -1
Bug #818115 [src:sphinx] turn python-sphinx into an arch:any package
Unable to merge bugs because:
blocks of #915856 is '' not '807848'
Failed to merge 818115: Did not alter merged bugs.

> close -1
Bug #915856 [src:sphinx] sphinx: Failed cross building with Build-Depends on 
python3-sphinx
Marked Bug as done

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



Bug#752938: marked as done (swig2.0: drop the unused default-jdk build dependency)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 19:51:14 +
with message-id 
and subject line Bug#752938: fixed in swig 3.0.12-2
has caused the Debian Bug report #752938,
regarding swig2.0: drop the unused default-jdk build dependency
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.)


-- 
752938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swig2.0
Version: 2.0.12-1
Severity: wishlist
Tags: patch

Hi,

First of all, thanks for taking care of SWIG in Debian!

I came across it as part of my work on this year's "Bootstrappable
Debian" Google Summer of Code project.  The goal of the project is to
figure out ways to modify packages, possibly using the new build
profiles mechanism, in order to resolve circular build dependencies as
described on the http://bootstrap.debian.net/amd64/ pages.  SWIG came up
because it's present in the "Feedback Arc Set" listed there, and because
the version-specific pages linked to from
http://bootstrap.debian.net/source/swig2.0.html suggested that it might
be advisable to remove the build dependency on default-jdk, since that
would solve several dependency loops in one fell swoop.

To my great surprise, when I tried building the swig2.0 packages with
B-D: default-jdk removed and "with_java" set to something else in the
rules file, it turned out that SWIG builds just fine, and that there are
absolutely no differences, none at all, in the generated binary
packages.  As it happens, the SWIG configure script checks for Java, but
then nothing ever uses the values, nothing builds anything Java-related,
nothing even writes the values to installed files.

So what do you think about the attached trivial patch that, perhaps
temporarily, drops the Java build dependency and disables the Java
checks during the build?  Of course, if in the future SWIG decides to
actually use Java, we may have to revisit this - but for the present it
would help bootstrapping Debian on new architectures by easily removing
a build dependency loop without any adverse effects at all.

Thanks again for your work on SWIG and Debian in general!

G'luck,
Peter

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

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org p.penc...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
From 94ccf803abb3a299d1ca3181b388e65bd2b12f37 Mon Sep 17 00:00:00 2001
From: Peter Pentchev 
Date: Sat, 28 Jun 2014 01:55:34 +0300
Subject: [PATCH] Remove the unused default-jdk build dependency.

The SWIG build does not ever use the Java compiler that the configure
script checks for.  The checks are there, the various Makefile.in files
set the variables to the values obtained by the configure script, but
nothing ever uses them.

This fixes a circular build dependency as noted in the version-specific
pages linked to from http://bootstrap.debian.net/source/swig2.0.html
---
 debian/control | 1 -
 debian/rules   | 2 +-
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 2e97484..3a96284 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,6 @@ Build-Depends: dpkg-dev (>= 1.16.1~),
bison,
debhelper (>= 7.0),
dh-autoreconf,
-   default-jdk [!hppa !mips !mipsel !alpha !arm !hurd-i386],
guile-2.0-dev,
libchicken-dev [!m68k !mips !mipsel],
libperl-dev,
diff --git a/debian/rules b/debian/rules
index 02f0d21..5f53c97 100755
--- a/debian/rules
+++ b/debian/rules
@@ -29,7 +29,7 @@ CONFIGURE_ARGS := \
 
 DEB_TARGET_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH)
 
-with_java := yes
+with_java := not used during the build at all
 no_java_archs := hppa hurd-i386 mips mipsel netbsd-i386
 ifneq ($(DEB_TARGET_ARCH),i386)
   ifeq ($(DEB_TARGET_ARCH), $(findstring $(DEB_TARGET_ARCH),$(no_java_archs)))
-- 
2.0.0



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: swig
Source-Version: 3.0.12-2

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

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

Bug#795694: marked as done (git-dpm: Lots of warnings about GREP_OPTIONS)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 19:49:28 +
with message-id 
and subject line Bug#795694: fixed in git-dpm 0.9.2-1
has caused the Debian Bug report #795694,
regarding git-dpm: Lots of warnings about GREP_OPTIONS
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.)


-- 
795694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-dpm
Version: 0.9.1-1
Severity: normal

I recently noticed that git-dpm on my laptop was producing quite a lot of:

grep: warning: GREP_OPTIONS is deprecated; please use an alias or script

This appears to be as a result of #411931 being fixed in grep as of 2.21-1.

git-dpm seems to be using this for:
export GREP_OPTIONS=--color=never

I suppose to override any local user version. Perhaps you could achieve the
same goal while remaining compatible with old and new grep by just clearing the
variable rather than setting it?

Cheers,
Ian.

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

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

Versions of packages git-dpm depends on:
ii  dpkg-dev  1.18.1
ii  git   1:2.5.0-1

Versions of packages git-dpm recommends:
ii  bzip2   1.0.6-8
ii  devscripts  2.15.8
ii  sensible-utils  0.0.9
ii  xz-utils5.1.1alpha+20120614-2.1

Versions of packages git-dpm suggests:
ii  pristine-tar  1.33
ii  sharutils 1:4.15.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: git-dpm
Source-Version: 0.9.2-1

We believe that the bug you reported is fixed in the latest version of
git-dpm, 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 795...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bernhard R. Link  (supplier of updated git-dpm 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: Sun, 27 Jan 2019 18:24:52 +0100
Source: git-dpm
Binary: git-dpm
Architecture: source all
Version: 0.9.2-1
Distribution: unstable
Urgency: medium
Maintainer: Bernhard R. Link 
Changed-By: Bernhard R. Link 
Description:
 git-dpm- git Debian package manager
Closes: 795694
Changes:
 git-dpm (0.9.2-1) unstable; urgency=medium
 .
   * new bugfix version
   - don't set GREP_OPTIONS (Closes: 795694)
   * bump Standards-Version
   * switch to debhelper 12
Checksums-Sha1:
 dc53c7a932d51b6921cee8652e5e1b5866ee14bb 1700 git-dpm_0.9.2-1.dsc
 aeb1899b83f69df63419cceaace68fb70cd439ea 151126 git-dpm_0.9.2.orig.tar.gz
 a9b754e97b3246af973d525b02e73ee503aabf30 3284 git-dpm_0.9.2-1.debian.tar.xz
 fe4704005ecee3d9399ca1702735fe9f91755a51 219484 git-dpm_0.9.2-1_all.deb
 bad42031fc501b683600a63bae29477bc55dc945 6973 git-dpm_0.9.2-1_amd64.buildinfo
Checksums-Sha256:
 03dd4a78e5a3b319e2460d40bca96de8b7e648477d0f40223812ae06f39d8466 1700 
git-dpm_0.9.2-1.dsc
 23635637f94cca788cd5546ce746b237f7b0d27cd3bac191dbfa1d54ff851846 151126 
git-dpm_0.9.2.orig.tar.gz
 92ab9deb28f6019ada905d63e712d66f1fb9b5c84be921fe559f22969672bd32 3284 
git-dpm_0.9.2-1.debian.tar.xz
 67ab37e9a847fd1358a810d68b35782b2bd34d05c2d36734541917ff55e6fcd2 219484 
git-dpm_0.9.2-1_all.deb
 64ba0b354fc5e5afa002a4244ebfdb7bc21ba6555c2ce43831b6ffb768e166aa 6973 
git-dpm_0.9.2-1_amd64.buildinfo
Files:
 3b661b74e53fd1a8cb5978c56b2ec78f 1700 vcs optional git-dpm_0.9.2-1.dsc
 80424e3b927c743b8a5260f3939887d4 151126 vcs optional git-dpm_0.9.2.orig.tar.gz
 e3bc836dd789eed6ca9c930f4a76c903 3284 vcs optional 
git-dpm_0.9.2-1.debian.tar.xz
 4c29afc9b23ae5ed3446a16eb8e4940e 219484 vcs optional git-dpm_0.9.2-1_all.deb
 72a1294476c7099563c9a40c4f5c4a9f 6973 vcs optional 
git-dpm_0.9.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEER2LYZQQfdf9pay9D6ZZIQUY/gV8FAlxOBh8SHGJybGlua0Bk
ZWJpYW4ub3JnAAoJEOmWSEFGP4FfeXsP/3Q5JnSBuwQU5e/d8X07YoRSWkn0Xgp9

Bug#920548: marked as done (golang-1.12: CVE-2019-6486)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 19:50:07 +
with message-id 
and subject line Bug#920548: fixed in golang-1.12 1.12~beta2-2
has caused the Debian Bug report #920548,
regarding golang-1.12: CVE-2019-6486
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.)


-- 
920548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-1.12
Version: 1.12~beta2-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/golang/go/issues/29903

Hi,

The following vulnerability was published for golang-1.12, which was
already fixed for the released version 1.11.5 and 1.10.8 upstream.

CVE-2019-6486[0]:
| Go before 1.10.8 and 1.11.x before 1.11.5 mishandles P-521 and P-384
| elliptic curves, which allows attackers to cause a denial of service
| (CPU consumption) or possibly conduct ECDH private key recovery
| attacks.

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-2019-6486
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6486
[1] https://github.com/golang/go/issues/29903

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: golang-1.12
Source-Version: 1.12~beta2-2

We believe that the bug you reported is fixed in the latest version of
golang-1.12, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated golang-1.12 
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: Sun, 27 Jan 2019 20:05:59 +0100
Source: golang-1.12
Architecture: source
Version: 1.12~beta2-2
Distribution: unstable
Urgency: medium
Maintainer: Go Compiler Team 
Changed-By: Dr. Tobias Quathamer 
Closes: 920548
Changes:
 golang-1.12 (1.12~beta2-2) unstable; urgency=medium
 .
   * Refresh patch Reproducible BUILD_PATH_PREFIX_MAP.
 Thanks to Michael Stapelberg!
   * Add patch to fix CVE-2019-6486. (Closes: #920548)
Checksums-Sha1:
 f7ee221e2c5ec216f82d516952d957e35d39fab5 2611 golang-1.12_1.12~beta2-2.dsc
 a08edb3d89002aee229007948d44d0e6328393bc 29832 
golang-1.12_1.12~beta2-2.debian.tar.xz
 9c570ec90b9b0338264a3a8dbc59640fd63f3afa 6494 
golang-1.12_1.12~beta2-2_amd64.buildinfo
Checksums-Sha256:
 ac07dfcf8611b0380c2d3b9f5428cfc57bd02f872415de9cd9935ce021d09315 2611 
golang-1.12_1.12~beta2-2.dsc
 c8ff699bb540de782998690fe794d1d7ea2134b863030e8ff53634286ba70144 29832 
golang-1.12_1.12~beta2-2.debian.tar.xz
 233e7c738452f6ae5f935c4e8cb10eba83a50b63877f93236ed513601467518a 6494 
golang-1.12_1.12~beta2-2_amd64.buildinfo
Files:
 f2cf4915830e4b3db407a07fb88efeb4 2611 devel optional 
golang-1.12_1.12~beta2-2.dsc
 07efc8e8120b611aa4eeb01b73b2ec6c 29832 devel optional 
golang-1.12_1.12~beta2-2.debian.tar.xz
 2a696920cec8a351f096d043781dfa26 6494 devel optional 
golang-1.12_1.12~beta2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxOBk4ACgkQEwLx8Dbr
6xmzJBAAk+2ihr0j4Hq7aHFxM6Lqm+YHnqo+omz+DtETvvl3BEBs4cmF87F5eElU
woUCAvvsW4XsEHxpVqbgrNSDBAZJXhO0dXoqmmGcEqKR1fjYLwBbUPkKOZeBx8Xd
tbuAfIqNowXiwzo+eFYxLmz92cOUMbQU2MFncoiEQokWFMEA2JVatRpZ+CUSVZSL
biDgkWRdQoUjInKVsaFnXKtlvhNLIWSkYASxA7hJwtYoH+PV6ksdNwrUuMJw8+SD
zEfRuWuPmSXJKnJORIXz+T5iKsBVVAZR3g2rkydiVdaUyjRmxoitv9R1ueEF872P
/CcrfiNBlNr7DSTj0L7Lh5hGlH3LOnaG7rYq2MTeV3QzCxI4/upicRaqO51lU+4X
POts9Bn9VLhHVES9LKb4t0IVLC4reATnz23NE+mniLSdK5/nmP+QiIkZCUQSf9w5
BNPiFgaTcXasiNEx54r4IO8rcsZrV6uo+5o9gbkLhds9aHdzKnSKwDrZT5Z2rO+w
lGnramVvPttKvSAfNDKIxwbYlq4WbT9fUJ/tnAeq/JgL18/wLmUkYOZroGEslzxZ
UYTD4G/MInIOP1mSduv3iYwzTVcdP/09woThcmQzlUiZvnyF4hzoHK5JJOa5aCND
0aoGb+wpgeUcacNuuKg7aYBHSxiWgK4pCumxt+E88dvEI8rTPHM=
=58OR
-END PGP SIGNATURE End Message ---


Bug#920636: marked as done (dialogues illegible on HIDPI display)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 19:11:29 +
with message-id <20190127191128.ga9...@laptop-t.office.oeko.net>
and subject line Re: Bug#920636: Acknowledgement (dialogues illegible on HIDPI 
display)
has caused the Debian Bug report #920636,
regarding dialogues illegible on HIDPI display
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.)


-- 
920636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagemagick
Version: 8:6.9.10.23+dfsg-2
Severity: normal




-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
compare:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
convert:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
composite:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
conjure:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
display:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
identify:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
import:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
mogrify:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
montage:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
stream:  ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org

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

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

Versions of packages imagemagick depends on:
ii  imagemagick-6.q16  8:6.9.10.23+dfsg-2

imagemagick recommends no packages.

imagemagick suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

Hi,

this bug report was sent due to fat fingers, and should be disregarded.

Cheers,
Toni--- End Message ---


Bug#920409: marked as done (splitpatch: please make the build reproducible)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 19:19:41 +
with message-id 
and subject line Bug#920409: fixed in splitpatch 1.0+20170926+git322ebca-2
has caused the Debian Bug report #920409,
regarding splitpatch: please make the build reproducible
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.)


-- 
920409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: splitpatch
Version: 1.0+20170926+git322ebca-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 splitpatch could not be built reproducibly.

This is because the embedded pod2man.mk uses the current build
date.

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   2019-01-25 08:42:48.543410438 
+0100
@@ -0,0 +1,21 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2019-01-25
+
+--- splitpatch-1.0+20170926+git322ebca.orig/man/pod2man.mk
 splitpatch-1.0+20170926+git322ebca/man/pod2man.mk
+@@ -36,7 +36,13 @@ RELEASE ?= $(PACKAGE)
+ 
+ # Optional variables to set
+ MANSECT   ?= 1
+-PODCENTER ?= $$(date "+%Y-%m-%d")
++
++DATE_FMT = %Y-%m-%d
++ifdef SOURCE_DATE_EPOCH
++PODCENTER ?= $$(shell date -u -d "@$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 
2>/dev/null || date -u -r "$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 2>/dev/null || 
date -u "+$(DATE_FMT)")
++else
++PODCENTER ?= $$(date "$(DATE_FMT)")
++endif
+ 
+ # Directories
+ MANSRC=
--- a/debian/patches/series 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/series 2019-01-25 08:42:47.423403838 +0100
@@ -0,0 +1 @@
+reproducible-build.patch
--- End Message ---
--- Begin Message ---
Source: splitpatch
Source-Version: 1.0+20170926+git322ebca-2

We believe that the bug you reported is fixed in the latest version of
splitpatch, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated splitpatch 
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: Sun, 27 Jan 2019 16:40:59 -0200
Source: splitpatch
Architecture: source
Version: 1.0+20170926+git322ebca-2
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho 
Changed-By: Joao Eriberto Mota Filho 
Closes: 920409
Changes:
 splitpatch (1.0+20170926+git322ebca-2) unstable; urgency=medium
 .
   * debian/patches/10_reproducible-build.patch: added to fix a unreproducible
 condition. Thanks to Chris Lamb . (Closes: #920409)
Checksums-Sha1:
 a3edbb48ecb4b8ec3cf4cbec27979752d71653a0 2022 
splitpatch_1.0+20170926+git322ebca-2.dsc
 819ea1b0381826b7acf06fb67a8f0a3ff1f1b6cb 6712 
splitpatch_1.0+20170926+git322ebca-2.debian.tar.xz
 f124a023eeb0b9e846faa497f9d2f19aeb1e820b 5014 
splitpatch_1.0+20170926+git322ebca-2_source.buildinfo
Checksums-Sha256:
 79d1840a7dba468e2c1ea73bfa138cf683c11b02eba1e342bca044c6604f4cd6 2022 
splitpatch_1.0+20170926+git322ebca-2.dsc
 2b9684932c08d9c6aac065e5a6351191265d0519375d39f3cebcdce09245820c 6712 
splitpatch_1.0+20170926+git322ebca-2.debian.tar.xz
 56fbf26725c4da458a0a67d299bf1d74d1abb4a9f6d271ab81dc0ded7d5ab1ed 5014 
splitpatch_1.0+20170926+git322ebca-2_source.buildinfo
Files:
 f6f060d502b2ba8223621e19b96f48f7 2022 text optional 
splitpatch_1.0+20170926+git322ebca-2.dsc
 89839e68eae617a175160e447f1a2029 6712 text optional 
splitpatch_1.0+20170926+git322ebca-2.debian.tar.xz
 f671e5870005efc79e681ce4fcfc19e6 5014 text optional 
splitpatch_1.0+20170926+git322ebca-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlxN/zEACgkQ3mO5xwTr
6e/rixAAqInaq3ZPUlYBaK8Iw2WHYD8chRTUpW98yHMW8/ws9/IjhQbMbCkGtb6P

Bug#911867: marked as done (RFS: frr/6.0.2-1 [ITP])

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 20:04:18 +0100
with message-id <20190127190418.gl881...@eidolon.nox.tf>
and subject line close / upload sponsored
has caused the Debian Bug report #911867,
regarding RFS: frr/6.0.2-1 [ITP]
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.)


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

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: frr
   Version : 6.0.1-1
   Upstream Author : FRRouting-dev 
 * URL : https://frrouting.org/
 * License : GPLv2 and LGPLv2.1
   Section : net

This replaces the "quagga" package, which FRRouting is a fork of.

It builds those binary packages:

  frr   - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon forked from Quagga
  frr-dbg- BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (debug symbols)
  frr-doc- BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (documentation)
  frr-pythontools - BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (Python 
Tools)
  frr-rpki-rtrlib - FRRouting RTRlib RPKI support
  frr-snmp   - FRRouting SNMP support

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

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


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

  dget -x https://mentors.debian.net/debian/pool/main/f/frr/frr_6.0.1-1.dsc

More information about frr can be obtained from https://frrouting.org

Changes since the last upload is not applicable since this is the first
upload.

I expect there still is feedback that I need to address in regards to
the Debian packaging on this and I will likely be uploading further
revisions in the coming days.


Regards,
 David Lamparter
--- End Message ---
--- Begin Message ---
Closing this as Vincent Bernat has sponsored the initial upload.
Thanks a lot!

-David--- End Message ---


Bug#891722: marked as done (sqwebmail-de FTBFS: applying patches fails)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 18:51:15 +
with message-id 
and subject line Bug#891722: fixed in sqwebmail-de 6.0.0-1
has caused the Debian Bug report #891722,
regarding sqwebmail-de FTBFS: applying patches fails
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.)


-- 
891722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqwebmail-de
Version: 5.5.1-3
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/sqwebmail-de-5.5.1'
mkdir htmltree
cp -a /usr/lib/courier/sqwebmail/html/en-us/ htmltree
rm htmltree/en-us/ISPELLDICT
echo -n default > htmltree/en-us/ISPELLDICT
# patch files - except TIMEZONELIST
filterdiff -x */TIMEZONELIST < `ls *diff ` | (cd htmltree/en-us; patch -p1 )
patching file ISPELLDICT
patching file LANGUAGE
patching file LANGUAGE_PREF
patching file LOCALE
patching file abooklist.html
patching file acl.html
patching file attachments.html
patching file autoresponder.html
patching file calendarlogin.inc.html
patching file empty.html
patching file eventacl.html
patching file eventdaily.html
patching file eventdelete.html
patching file eventmonthly.html
patching file eventnotifydelete.txt
patching file eventnotifynew.txt
patching file eventnotifysubject.txt
patching file eventshow.html
patching file eventweekly.html
patching file expired.html
patching file filter.html
patching file folder.html
patching file folders.html
patching file gpg.html
Hunk #3 FAILED at 80.
Hunk #4 FAILED at 127.
Hunk #5 succeeded at 123 (offset -16 lines).
Hunk #6 succeeded at 132 (offset -16 lines).
Hunk #7 succeeded at 153 (offset -16 lines).
Hunk #8 FAILED at 181.
Hunk #9 succeeded at 183 (offset -16 lines).
Hunk #10 succeeded at 191 (offset -16 lines).
3 out of 10 hunks FAILED -- saving rejects to file gpg.html.rej
patching file gpgcreate.html
patching file gpgerr.html
patching file index.html
Hunk #2 succeeded at 18 with fuzz 2.
patching file invalid.html
patching file keyimport.html
patching file ldaplist.html
patching file ldapsearch.html
patching file login.html
patching file loginform.inc.html
patching file navbar.inc.html
patching file navbar2.inc.html
patching file navbar3.inc.html
patching file newevent.html
patching file newmsg.html
patching file preferences.html
patching file print.html
patching file printnocookie.html
patching file printredirect.html
patching file quickadd.html
patching file readmsg.html
patching file redirect.html
patching file spellchk.html
make[1]: *** [debian/rules:20: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: sqwebmail-de
Source-Version: 6.0.0-1

We believe that the bug you reported is fixed in the latest version of
sqwebmail-de, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Willi Mann  (supplier of updated sqwebmail-de 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: Sun, 27 Jan 2019 19:24:46 +0100
Source: sqwebmail-de
Binary: sqwebmail-de
Architecture: source
Version: 6.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Willi Mann 
Changed-By: Willi Mann 
Description:
 sqwebmail-de - German translations for the SqWebMail webmail service
Closes: 891722
Changes:
 sqwebmail-de (6.0.0-1) unstable; urgency=medium
 .
   * New "upstream" tarball (Updated translation for sqwebmail 6.0.0
 (courier 1.0.5))
 - fix build against latest courier-mta package, closes: #891722)
   * Depend on latest sqwebmail in debian (6.0.0+1.0.5)
   * Update Standards-Version (3.9.6 -> 4.3.0)
   * Update VCS-* fields
   * d/rules: also exclude ISPELLDICT from patching
Checksums-Sha1:
 a1ec34f24ea9ec6e6df7417137b9b1965d734fcd 1899 sqwebmail-de_6.0.0-1.dsc
 be341017cbd5038674f99d17ef6276daebbf218f 29853 sqwebmail-de_6.0.0.orig.tar.gz
 ba2615ad5afc97faf030bfd3f2ca84ebc1e010f3 3984 
sqwebmail-de_6.0.0-1.debian.tar.xz
 9d330d6d0bd9a1b8746cc2c9f8ddfc72500fa8a0 6306 

Bug#920400: marked as done (linssid FTCBFS: upstream linssid-app.pro hard codes build architecture compiler)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 18:05:36 +
with message-id 
and subject line Bug#920400: fixed in linssid 3.6-3
has caused the Debian Bug report #920400,
regarding linssid FTCBFS: upstream linssid-app.pro hard codes build 
architecture compiler
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.)


-- 
920400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linssid
Version: 3.6-2
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

linssid fails to cross build from source, because
linssid/linssid-app.pro hard codes the build architecture compiler for
no good reason. After removing the relevant assignments and thus relying
on qmake/debhelper to figure out, linssid cross builds successfully.
Please consider applying the attached patch.

Helmut
--- linssid-3.6.orig/linssid-app/linssid-app.pro
+++ linssid-3.6/linssid-app/linssid-app.pro
@@ -15,8 +15,6 @@
 MOC_DIR = 
 RCC_DIR = 
 UI_DIR = 
-QMAKE_CC = gcc
-QMAKE_CXX = g++
 DEFINES += 
 INCLUDEPATH += /usr/include/boost
 INCLUDEPATH += /usr/include/qt5
--- End Message ---
--- Begin Message ---
Source: linssid
Source-Version: 3.6-3

We believe that the bug you reported is fixed in the latest version of
linssid, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated linssid 
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: Sun, 27 Jan 2019 14:53:18 -0200
Source: linssid
Architecture: source
Version: 3.6-3
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho 
Changed-By: Joao Eriberto Mota Filho 
Closes: 920400
Changes:
 linssid (3.6-3) unstable; urgency=medium
 .
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 12.
   * debian/control: bumped Standards-Version to 4.3.0.
   * debian/copyright: updated packaging copyright years.
   * debian/patches/20_fix-FTCBFS-build-arch-compiler.patch: created to fix a
 FTCBFS. Thanks to Helmut Grohne . (Closes: #920400)
Checksums-Sha1:
 d346db48d9fbb9a985a0720f7421ffd9bb6c0461 1951 linssid_3.6-3.dsc
 637bd819fbb981d4db1c97e4edc9e5be2116a5f8 6000 linssid_3.6-3.debian.tar.xz
 158bf3f7b92cc49e59452bd9038b13b19d419ffa 9699 linssid_3.6-3_source.buildinfo
Checksums-Sha256:
 cd2a77ece4f4f6202f32fe0934fee45e7cfe3fa229918ab35b0079addd930fde 1951 
linssid_3.6-3.dsc
 93fe622db67b674821d5505146772d4290f6b6a0fbd6326a5a4ed4d0c3f52239 6000 
linssid_3.6-3.debian.tar.xz
 1eec973ebe89c2a317d49f04ab4cbd49f9766b0e073f7fea85a9b5319280c03c 9699 
linssid_3.6-3_source.buildinfo
Files:
 2975516e043994728418f5cc2fef6b86 1951 net optional linssid_3.6-3.dsc
 71e8aaca38c9abbfd546d4c02e21a546 6000 net optional linssid_3.6-3.debian.tar.xz
 3858f859cbb61f91d6a9bda61ae78acd 9699 net optional 
linssid_3.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlxN76QACgkQ3mO5xwTr
6e93/A//TqZfRx2SUldpKXb3hb226+edJGMg86u+jZ+3jhVY40AU1ADIUtomI0yO
4j7gq1ICh9TB9q30LpI+gu0+x7rCj0tBgAEvEgQ2GjfQ8PTJnrcretLHF9rNyR2X
zzDS7j1tcpkMbtR5HLLron6sv6bbuVysfrqNx2CN6HNvOk53gQd3sxx/Qynpkdci
ziVF165k+Lxp62c9JpPlxQg33WbxFfbyW8W5Qvis+HsEUt3AP/4dyw7bB6Yz/U5S
2OaxS51hBXyAh1qOXhWDwbfxXdfQ2i37sWTfgIOZ4xH8+bm47H5J0hoztuCRuNFN
JTrX199X6GPqjDgsX+wGELuI7d7yn1fsG6PtpRJaxPqrRkRygsB5kh1/KvrZo3Zu
aGCmP5TbST4L4skkQkafsrIPua11/IXEY2GIov16BgAKf7wt2vEjsNejKPLD/wwd
RjM7ztHXHXPF2Oe6fjSrksys7wgeCQTPU8TKOTQ932oIt8aSmFY0rI1GlOdu4GQp
yMLfiCRFv/fFVXdmlFkPa7ADiAuVDyK/MeTJuRN2F2yKfQYAXYuz+tMQYo6uZGFw
kEYmLbHv+NcS21asKA38fnKy9ujooxVlge/O1izV/cG4110iLld37Nlhl+vhGrb4
TnXHM2Nc6xaUE54qGSIUFroxeBqkBYKzcvrbajBmfw7g2C0gnIk=
=7uDj
-END PGP SIGNATURE End Message ---


Bug#920244: marked as done (cdimage.debian.org: Please add LXQt and Standard builds for live Buster images)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 18:05:26 +
with message-id <20190127180514.7j5f7yhudp4pn...@tack.einval.com>
and subject line Re: Bug#920244: cdimage.debian.org: Please add LXQt and 
Standard builds for live Buster images
has caused the Debian Bug report #920244,
regarding cdimage.debian.org: Please add LXQt and Standard builds for live 
Buster images
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.)


-- 
920244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cdimage.debian.org
Severity: wishlist
Tags: patch

Debian Images Team,

Now that live-tasks includes live-task-lxqt and live-task-standard,
please add LXQt and Standard builds for live Buster images.

This would fix Bug #876428 - No 'standard' image of Debian-Live:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876428

Untested patch for live-setup/available/run-30live-wrapper is attached.

Thank you!
Daniel Lewart
--- a/available/run-30live-wrapper  2019-01-12 03:58:15.0 -0600
+++ b/available/run-30live-wrapper  2019-01-23 00:00:00.0 -0600
@@ -30,9 +30,12 @@
 
 if [ "$BUILDS"x = ""x ] ; then
 case "$CODENAME" in
-   stretch|buster)
+   stretch)
BUILDS="cinnamon gnome kde lxde mate xfce"
;;
+   buster)
+   BUILDS="cinnamon gnome kde lxde lxqt mate standard xfce"
+   ;;
*)
log "  ABORTING: Don't know what to build for \"$CODENAME\""
exit 1
--- End Message ---
--- Begin Message ---
On Wed, Jan 23, 2019 at 12:45:09AM -0600, Daniel Lewart wrote:
>Package: cdimage.debian.org
>Severity: wishlist
>Tags: patch
>
>Debian Images Team,
>
>Now that live-tasks includes live-task-lxqt and live-task-standard,
>please add LXQt and Standard builds for live Buster images.
>
>This would fix Bug #876428 - No 'standard' image of Debian-Live:
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876428
>
>Untested patch for live-setup/available/run-30live-wrapper is attached.

Thanks for the patch. It looks sane enough, so I've just applied it
now. For results, check back tomorrow with the next weekly build. :-)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"... the premise [is] that privacy is about hiding a wrong. It's not.
 Privacy is an inherent human right, and a requirement for maintaining
 the human condition with dignity and respect."
  -- Bruce Schneier--- End Message ---


Bug#920512: marked as done (syslog-ng: FTBFS with dpkg-buildpackage -A)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 18:06:21 +
with message-id 
and subject line Bug#920512: fixed in syslog-ng 3.19.1-2
has caused the Debian Bug report #920512,
regarding syslog-ng: FTBFS with dpkg-buildpackage -A
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.)


-- 
920512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syslog-ng
Version: 3.19.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

syslog-ng/experimental FTBFS during the binary-indep-only build, i.e. if
built with dpkg-buildpackage -A:

 debian/rules build-indep
make: 'build-indep' is up to date.
 fakeroot debian/rules binary-indep
dh binary-indep --with autoreconf,systemd,python2
   debian/rules build-indep
make[1]: Entering directory '/build/syslog-ng-3.19.1'
make[1]: 'build-indep' is up to date.
make[1]: Leaving directory '/build/syslog-ng-3.19.1'
   dh_testroot -i
   dh_prep -i
   dh_installdirs -i
   debian/rules override_dh_auto_install
make[1]: Entering directory '/build/syslog-ng-3.19.1'
dh_auto_install -- \
pkgconfigdir=/usr/lib/x86_64-linux-gnu/pkgconfig \
PYSETUP_OPTIONS="--install-layout=deb \
--root=/build/syslog-ng-3.19.1/debian/tmp/"
find . -name \*.la | xargs --no-run-if-empty rm
make[1]: Leaving directory '/build/syslog-ng-3.19.1'
   dh_install -i
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/default-network-drivers/*" (tried in ., 
debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/default-network-drivers/*
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/ewmm/*" (tried in ., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/ewmm/*
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/graylog2/*" (tried in ., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/graylog2/*
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/loadbalancer/*" (tried in ., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/loadbalancer/*
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/osquery/*" (tried in ., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/osquery/*
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/windowseventlog/*" (tried in ., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/windowseventlog/*
dh_install: missing files, aborting
make: *** [debian/rules:205: binary-indep] Error 25


The 'build-indep' target seems to be a no-op, not creating the stuff
needed by the subsequent install target.


cheers,

Andreas


syslog-ng_3.19.1-1_indep.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: syslog-ng
Source-Version: 3.19.1-2

We believe that the bug you reported is fixed in the latest version of
syslog-ng, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated syslog-ng 
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: Sat, 26 Jan 2019 13:57:58 +
Source: syslog-ng
Architecture: source
Version: 3.19.1-2
Distribution: unstable
Urgency: medium
Maintainer: syslog-ng maintainers 

Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 920512
Changes:
 syslog-ng (3.19.1-2) unstable; urgency=medium
 .
   * Install SCL files from source (closes: #920512).
   * Make syslog-ng-mod-pacctformat linux-any.
Checksums-Sha1:
 e90e7973e014e599d84736c64b50456002b2c5d2 4536 syslog-ng_3.19.1-2.dsc
 9bca6308ea5820ee88149c62d8f6e06f0b3bc323 42472 syslog-ng_3.19.1-2.debian.tar.xz
 de75cba6bc607198438904fe1b338fba1b0c6c74 18283 
syslog-ng_3.19.1-2_amd64.buildinfo
Checksums-Sha256:
 1ad67aba482ed5e0517b9acb6ed2b1c109026866e5a4a493992ae82f672cc70c 4536 
syslog-ng_3.19.1-2.dsc

Bug#919775: marked as done (apparmor: AppArmor denies new mesa-related paths)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 18:04:28 +
with message-id 
and subject line Bug#919775: fixed in apparmor 2.13.2-4
has caused the Debian Bug report #919775,
regarding apparmor: AppArmor denies new mesa-related paths
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.)


-- 
919775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apparmor
Version: 2.13.2-3
Severity: normal
Tags: upstream patch

Dear Maintainer,

After recent Mesa updates on Sid, new denies are produced by some
applicaitons:

```
type=AVC msg=audit(1547905564.212:523): apparmor="DENIED"
operation="open" profile="supertuxkart" name="/usr/share/drirc.d/"
pid=15740 comm="supertuxkart" requested_mask="r" denied_mask="r"
fsuid=1000 ouid=0
```

```
type=AVC msg=audit(1547905896.307:548): apparmor="DENIED"
operation="open" profile="supertuxkart"
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=15963 c
omm="supertuxkart" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

```

MR is prepared:
https://gitlab.com/apparmor/apparmor/merge_requests/308

I hope this gets into Buster. I guess these kind of fixes are allowd until
final freeze, or even later?



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

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

Versions of packages apparmor depends on:
ii  debconf [debconf-2.0]  1.5.70
ii  libc6  2.28-5
ii  lsb-base   10.2018112800
ii  python33.7.2-1

apparmor recommends no packages.

Versions of packages apparmor suggests:
ii  apparmor-profiles-extra  1.24
ii  apparmor-utils   2.13.2-3

-- Configuration Files:
/etc/apparmor.d/abstractions/audio changed [not included]
/etc/apparmor.d/abstractions/fonts changed [not included]
/etc/apparmor.d/abstractions/kde changed [not included]
/etc/apparmor.d/abstractions/mesa changed [not included]
/etc/apparmor.d/abstractions/ubuntu-email changed [not included]
/etc/apparmor.d/tunables/kernelvars changed [not included]
/etc/apparmor.d/tunables/securityfs changed [not included]
/etc/apparmor.d/tunables/sys changed [not included]

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: apparmor
Source-Version: 2.13.2-4

We believe that the bug you reported is fixed in the latest version of
apparmor, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated apparmor 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: Sun, 27 Jan 2019 17:07:34 +
Source: apparmor
Architecture: source
Version: 2.13.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian AppArmor Team 
Changed-By: intrigeri 
Closes: 919705 919775
Changes:
 apparmor (2.13.2-4) unstable; urgency=medium
 .
   * Move libapparmor.so unversioned symlink to /lib/ (Closes: 
#919705).
   * New patches, cherry-picked from upstream:
 - Make tunables/share play well with aliases.
 - Fix access to /usr/share/drirc.d.conf (Closes: #919775).
 - Fix access to the default paths used by dehydrated in Debian.
 - Support new font configuration paths.
 - Support libvirt named profile.
 - Fix access to /etc/alsa/conf.d/.
   * autopkgtests: test compiling more profiles shipped by other packages.
   * Patch the dnsmasq profile to fix ptrace and signal communication
 with libvirtd.
Checksums-Sha1:
 f0cc1f6cfb733467f6cc2870ef7f18d16cfdbff4 3258 apparmor_2.13.2-4.dsc
 36dfe22c9e0ae31142882543b52e831ed926a739 95876 apparmor_2.13.2-4.debian.tar.xz
 94e6495972c00b7c59677195da4ed88bffd3dd86 12631 
apparmor_2.13.2-4_amd64.buildinfo
Checksums-Sha256:
 

Bug#919705: marked as done (move libapparmor.so to /lib/)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 18:04:28 +
with message-id 
and subject line Bug#919705: fixed in apparmor 2.13.2-4
has caused the Debian Bug report #919705,
regarding move libapparmor.so to /lib/
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.)


-- 
919705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapparmor-dev
Version: 2.13.2-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:libvirt

I tried cross building libvirt. It still has a few issues, but one of
the issues is that it fails to find libapparmor (not immediately
visible). In the end, I was able to reduce the libvirt's check to the
following command:

echo 'main(){return aa_change_profile();}' | $CC -x c - -o /dev/null -lapparmor

If $CC is a native compiler, it just works. If $CC is a cross compiler
(e.g. for arm64), you get an error:

/usr/lib/gcc-cross/aarch64-linux-gnu/8/../../../../aarch64-linux-gnu/bin/ld: 
/lib/aarch64-linux-gnu/libapparmor.a(kernel.o): in function 
`aa_query_label@@APPARMOR_2.9':
(.text+0x1248): undefined reference to `pthread_once'

What you can see here is that for some reason gcc is preferring the
static library over the dynamic one. So I started looking and compared
$CC -print-search-dirs. Indeed, for native toolchains /usr/lib/
comes before /lib/. For Debian's cross toolchains, this order
is reversed for some reason. I'm not sure whether that's a bug in the
cross toolchains. However, it causes gcc to prefer the static library
over the dynamic one.

I've concluded that regardless of whether this is a bug in gcc, it is a
bug in libapparmor-dev. I think that putting static and dynamic
libraries in different directories is a recipe for breakage. You really
should put them in the same directory. That can be either /lib/
or /usr/lib/. Implementing the former is easier so that's what
my patch does. Would you be so kind and fix this on the apparmor side?

Helmut
diff --minimal -Nru apparmor-2.13.2/debian/changelog 
apparmor-2.13.2/debian/changelog
--- apparmor-2.13.2/debian/changelog2019-01-01 19:03:54.0 +0100
+++ apparmor-2.13.2/debian/changelog2019-01-18 19:48:04.0 +0100
@@ -1,3 +1,10 @@
+apparmor (2.13.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move libapparmor.so to /lib/. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 18 Jan 2019 19:48:04 +0100
+
 apparmor (2.13.2-3) unstable; urgency=medium
 
   * Update upstream MR!252 backport to fix initscript (Closes: #917874)
diff --minimal -Nru apparmor-2.13.2/debian/rules apparmor-2.13.2/debian/rules
--- apparmor-2.13.2/debian/rules2019-01-01 19:03:54.0 +0100
+++ apparmor-2.13.2/debian/rules2019-01-18 19:48:01.0 +0100
@@ -176,7 +176,7 @@
# Create unversioned link in /usr to the shared library
MY_DSO=$$(basename $$(readlink 
$(CURDIR)/debian/tmp/lib/$(DEB_HOST_MULTIARCH)/libapparmor.so)); \
ln -sf /lib/$(DEB_HOST_MULTIARCH)/$${MY_DSO} \
-   $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libapparmor.so
+   $(CURDIR)/debian/tmp/lib/$(DEB_HOST_MULTIARCH)/libapparmor.so
 
 override_dh_installinit:
dh_installinit --no-start --no-restart-on-upgrade --error-handler=true
--- End Message ---
--- Begin Message ---
Source: apparmor
Source-Version: 2.13.2-4

We believe that the bug you reported is fixed in the latest version of
apparmor, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated apparmor 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: Sun, 27 Jan 2019 17:07:34 +
Source: apparmor
Architecture: source
Version: 2.13.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian AppArmor Team 
Changed-By: intrigeri 
Closes: 919705 919775
Changes:
 apparmor (2.13.2-4) unstable; urgency=medium
 .
   * Move libapparmor.so unversioned symlink to /lib/ (Closes: 
#919705).
   * New patches, cherry-picked from upstream:
 - Make tunables/share play well 

Bug#920026: marked as done (python-greenlet-dev: ships header in /usr/include/python3.7/)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 17:17:32 +
with message-id 
and subject line Bug#920026: fixed in python-greenlet 0.4.15-2
has caused the Debian Bug report #920026,
regarding python-greenlet-dev: ships header in /usr/include/python3.7/
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.)


-- 
920026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-greenlet-dev
Version: 0.4.15-1
Severity: serious

Hi,

your package ships the header file(s):

  /usr/include/python3.7/greenlet/greenlet.h

but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpacking order /usr/include/python3.7 being a directory in some
cases, separating the headers into two independent trees.

These header files must be shipped in /usr/include/python3.7m/ instead.
Please talk to the python maintainers to find a proper solution for
handling the packaging of python header files in a future-proof way.


Andreas
--- End Message ---
--- Begin Message ---
Source: python-greenlet
Source-Version: 0.4.15-2

We believe that the bug you reported is fixed in the latest version of
python-greenlet, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated python-greenlet 
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: Sun, 27 Jan 2019 15:29:31 +
Source: python-greenlet
Architecture: source
Version: 0.4.15-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 920026
Changes:
 python-greenlet (0.4.15-2) unstable; urgency=medium
 .
   * Correct Python 3 header installation directory (closes: #920026).
   * Mark python-greenlet-doc as Multi-Arch foreign.
   * Update Standards-Version to 4.3.0 .
Checksums-Sha1:
 430a9123df2e02b66a1bb279693ca4f185c9ce07 2304 python-greenlet_0.4.15-2.dsc
 5114e2411dea096ddd169b2727cc16af5b8f7cce 7144 
python-greenlet_0.4.15-2.debian.tar.xz
 c6817d5d6e6c499d47e94255d59d93562b56abe6 11265 
python-greenlet_0.4.15-2_amd64.buildinfo
Checksums-Sha256:
 28dc856e74f12ddb84921ed40c190074a6ae83ba0c8ef781e969336a83431eb3 2304 
python-greenlet_0.4.15-2.dsc
 8cab9e1149a59cb7e313ad6a5546d02ca385845bd24c163956383b62c1b4e6e2 7144 
python-greenlet_0.4.15-2.debian.tar.xz
 82d99727ae45df9d7cbf6a5f4de1adb9bd1f37de3359ab9436a899c558382354 11265 
python-greenlet_0.4.15-2_amd64.buildinfo
Files:
 f7b3d6ce86c23793287612f41c5cb4d7 2304 python optional 
python-greenlet_0.4.15-2.dsc
 8f47041eccd13bd2e0b7a2abf08af06a 7144 python optional 
python-greenlet_0.4.15-2.debian.tar.xz
 5e946d331c56857e33c8fc65758d0f44 11265 python optional 
python-greenlet_0.4.15-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlxN4aUACgkQ3OMQ54ZM
yL+1qRAAiz4r9pGcDZMbzqc37NNfCqrijrYftUIZhh8ndt0DiIwKuSgf4ozJx0Td
PGtlRXqjoeByiitPRbT5+Th0y6CvwnEqQCIPs0M6wWUkVg7aXlqUwtGdh3Z3H9zH
YEFuMNxQiipKXuC4iw6BpSz6mqxe9GYc5SQoItmHhbaLxNmcgzuLjfJRmseyoOHq
bnG+53eN3hx2UocmNVUIhOZ7RF9DsGsRZ2X/t4yx6lL0fjH734zWlvc2mTToYJUH
Tb4BHeEK6l1nm1OUUapFbwZMjx+ilELWFLzLFblC8DOZg3qQCOp6uVZrbvju91Os
Ry62Wxkd6dGnAl/cN7whN1xhKjecdQR9EMz8VbNdlfyIxaR5Lqpp/rDQOyFVaKU0
qpJ0FHm04jMTSTqk8Gzim8oQcXkdxCxzqHEqeFmGwJNa0c2wdWpZ2rPahEJJlpkT
ujx7JoPENWyrmY9o8old5YDvvRDlODlh26c7rkZNUCUhAkai0ud/K5bvPv1frAuD
5a/YBGJlPD6Tzb4V9xiA7qmzEWC0t4XzL7mkk6mjDpXeydlwPFe+H2hPni+8/K+b
lheutLND78Xfe4lJwsXiD1EtXENZxKuiZR4uQpeSPjpjvA0nelIJ+lM/BV+GrA+9
9/zsTa6ETXYnkiXqF8NitOJ77TqtehUpSphF23hswcoPzuggEzM=
=SomY
-END PGP SIGNATURE End Message ---


Bug#908890: marked as done (developers-reference: As alioth is gone, replace references to Salsa)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:48 +
with message-id 
and subject line Bug#908890: fixed in developers-reference 3.4.22
has caused the Debian Bug report #908890,
regarding developers-reference: As alioth is gone, replace references to Salsa
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.)


-- 
908890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:developers-reference
Severity: normal
Tags: patch

I found during the translation to German that there are a few references
to alioth, but at this service is no longer, those references needs
updating.

MR: https://salsa.debian.org/debian/developers-reference/merge_requests/6

Please note that this MR needs reviewing, language and contentwise.
For example I'm not sure if section 4.12 should be deleted completly or
(like in the MR) described as past service…

Cheers,
-- 
tobi

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

Kernel: Linux 4.17.0-3-amd64 (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)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 3.4.22

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated developers-reference 
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: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Holger Levsen 
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
Changes:
 developers-reference (3.4.22) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
 doc section on Debian website). Closes: #690750, #912724.
 .
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
 .
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
 .
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
 .
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
 .
   [ Holger Levsen ]
   * comment.ent:
 - add url-openpgp-best-practices-fr and use that in fr.po.
 - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
   as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
 Closes: #907915
   * d/control:
 - upgrade to use debhelper-compat(=11), drop d/compat.
 - add "Rules-Requires-Root: no" to support building as non-root.
 - remove Build-Depends on dpkg-dev as it's part of build-essential and the
   required version is present in wheezy.
 - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
   docbook-xsl and dblatex.
 - bump standards version to 4.3.0, no changes needed.
 - sort and wrap Build-Depends-Indep.
 - add myself to uploaders.
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces.
Checksums-Sha1:
 c0e7c80183ab122fe6c6f62d544fd990bd74dfa1 2398 developers-reference_3.4.22.dsc
 46bd729ef368aeeb432370c201731d4ba36e899e 671308 
developers-reference_3.4.22.tar.xz
 4567e7518eff2cbd7639ef772ed00d7b92eae5cf 5199 
developers-reference_3.4.22_source.buildinfo

Bug#907915: marked as done (developers-reference: language in manual)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:48 +
with message-id 
and subject line Bug#907915: fixed in developers-reference 3.4.22
has caused the Debian Bug report #907915,
regarding developers-reference: language in manual
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.)


-- 
907915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: developers-reference
Version: 3.4.20
Severity: wishlist

With Debian presenting itself as a distribution suitable for children
in educational environments, please consider removing the "f-bombs" in
this package.  As a fundamental document in Debian, it is something
that should be acceptable for school children to read so adding an
"offensive" tag to the package will not be enough to remedy the
situation.

There are three such occurrences:

* Section 5.13.2.1 Out-of-date: please find another term for
"architectures that don't keep up", and modify the update_out.py
mentioned in that section accordingly.

* 5.13.2.4 Influence of packaging in testing: same comment; please use
another term for such architectures.

* 6.3.4 Common errors in changelog entries: please remove the fsck
joke by finding a different example for "too many acronyms"--or just
make up an example to replace that one.

It would be nice to make these changes before the buster freeze if
possible, so a cleaned-up version gets into stable as soon as
possible.

Thank you,


Paul Hardy
--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 3.4.22

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 907...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated developers-reference 
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: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Holger Levsen 
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
Changes:
 developers-reference (3.4.22) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
 doc section on Debian website). Closes: #690750, #912724.
 .
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
 .
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
 .
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
 .
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
 .
   [ Holger Levsen ]
   * comment.ent:
 - add url-openpgp-best-practices-fr and use that in fr.po.
 - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
   as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
 Closes: #907915
   * d/control:
 - upgrade to use debhelper-compat(=11), drop d/compat.
 - add "Rules-Requires-Root: no" to support building as non-root.
 - remove Build-Depends on dpkg-dev as it's part of build-essential and the
   required version is present in wheezy.
 - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
   docbook-xsl and dblatex.
 - bump standards version to 4.3.0, no changes needed.
 - sort and wrap Build-Depends-Indep.
 - add myself to uploaders.
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces.
Checksums-Sha1:
 c0e7c80183ab122fe6c6f62d544fd990bd74dfa1 2398 developers-reference_3.4.22.dsc
 46bd729ef368aeeb432370c201731d4ba36e899e 671308 
developers-reference_3.4.22.tar.xz

Bug#818850: marked as done (developers-reference: two chapters regarding the 'default' field)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:48 +
with message-id 
and subject line Bug#818850: fixed in developers-reference 3.4.22
has caused the Debian Bug report #818850,
regarding developers-reference: two chapters regarding the 'default' field
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.)


-- 
818850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: developers-reference


In the developers-reference from git today, there are two chapters 
regarding the 'default' field, that is 6.5.4.4 and 6.5.4.5.
See 
https://www.debian.org/doc/manuals/developers-reference/ch06.en.html#s6.5.4.4
and
https://www.debian.org/doc/manuals/developers-reference/ch06.en.html#s6.5.4.5
(these links are from the unstable version 3.4.17 though).

These two chapters should be merged into one chapter.


Greetings
Holger


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 3.4.22

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated developers-reference 
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: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Holger Levsen 
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
Changes:
 developers-reference (3.4.22) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
 doc section on Debian website). Closes: #690750, #912724.
 .
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
 .
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
 .
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
 .
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
 .
   [ Holger Levsen ]
   * comment.ent:
 - add url-openpgp-best-practices-fr and use that in fr.po.
 - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
   as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
 Closes: #907915
   * d/control:
 - upgrade to use debhelper-compat(=11), drop d/compat.
 - add "Rules-Requires-Root: no" to support building as non-root.
 - remove Build-Depends on dpkg-dev as it's part of build-essential and the
   required version is present in wheezy.
 - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
   docbook-xsl and dblatex.
 - bump standards version to 4.3.0, no changes needed.
 - sort and wrap Build-Depends-Indep.
 - add myself to uploaders.
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces.
Checksums-Sha1:
 c0e7c80183ab122fe6c6f62d544fd990bd74dfa1 2398 developers-reference_3.4.22.dsc
 46bd729ef368aeeb432370c201731d4ba36e899e 671308 
developers-reference_3.4.22.tar.xz
 4567e7518eff2cbd7639ef772ed00d7b92eae5cf 5199 
developers-reference_3.4.22_source.buildinfo
Checksums-Sha256:
 32caa0599339f67467497cc069befd74e4d95a9d7d21509b5e6cf02fcfa68b24 2398 
developers-reference_3.4.22.dsc
 bc598c8f7a072198a49dfd11c760b7417cd4f72050fef749be517c1daa47 671308 

Bug#908291: marked as done (developers-reference, section 5.11.4: Add a note on versioning scheme when reverting an NMU)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:48 +
with message-id 
and subject line Bug#908291: fixed in developers-reference 3.4.22
has caused the Debian Bug report #908291,
regarding developers-reference, section 5.11.4: Add a note on versioning scheme 
when reverting an NMU
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.)


-- 
908291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: developers-reference
Severity: wishlist
Tags: patch

Dear Maintainer,

The Developer's reference explains a lot about NMUs and corresponding version
scheme but it does not explain the naming convention to use when you have to
revert an NMU that brings a new upstream version.
Lintian has a check about it (https://lintian.debian.org/tags/epoch-changed-
but-upstream-version-did-not-go-backwards.html), so it seems the format is
wildly accepted.
So maybe a not about it here would be a good thing.

I took the liberty to provide a patch via a MR:
https://salsa.debian.org/debian/developers-reference/merge_requests/4

Let me know if adding that paragraph would be ok and if the wording is correct.
I'm not sure on how to handle the po files. Let me know if I can help on that
too.

Thanks
Joseph
--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 3.4.22

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated developers-reference 
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: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Holger Levsen 
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
Changes:
 developers-reference (3.4.22) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
 doc section on Debian website). Closes: #690750, #912724.
 .
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
 .
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
 .
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
 .
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
 .
   [ Holger Levsen ]
   * comment.ent:
 - add url-openpgp-best-practices-fr and use that in fr.po.
 - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
   as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
 Closes: #907915
   * d/control:
 - upgrade to use debhelper-compat(=11), drop d/compat.
 - add "Rules-Requires-Root: no" to support building as non-root.
 - remove Build-Depends on dpkg-dev as it's part of build-essential and the
   required version is present in wheezy.
 - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
   docbook-xsl and dblatex.
 - bump standards version to 4.3.0, no changes needed.
 - sort and wrap Build-Depends-Indep.
 - add myself to uploaders.
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces.
Checksums-Sha1:
 c0e7c80183ab122fe6c6f62d544fd990bd74dfa1 2398 developers-reference_3.4.22.dsc
 46bd729ef368aeeb432370c201731d4ba36e899e 671308 
developers-reference_3.4.22.tar.xz
 4567e7518eff2cbd7639ef772ed00d7b92eae5cf 5199 
developers-reference_3.4.22_source.buildinfo
Checksums-Sha256:
 32caa0599339f67467497cc069befd74e4d95a9d7d21509b5e6cf02fcfa68b24 2398 

Bug#690750: marked as done (developers-reference: no link to English manual)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:48 +
with message-id 
and subject line Bug#690750: fixed in developers-reference 3.4.22
has caused the Debian Bug report #690750,
regarding developers-reference: no link to English manual
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.)


-- 
690750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: developers-reference
Version: 3.4.9
Severity: minor
tags: l10n
Control: user debian-de...@debian.or.jp
Control: usertags -1 debianjp

Hi,

 Now it's index.html says "This page is also available in French, German
 and Japanese." and link to each language. However, this line is same in
 each language.

 So, non-English manuals doesn't have a link to original English manual.
 As a comment in index.dbx,
> 

 Yes, it should be fixed (as severity: minor).

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane
--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 3.4.22

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 690...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated developers-reference 
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: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Holger Levsen 
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
Changes:
 developers-reference (3.4.22) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
 doc section on Debian website). Closes: #690750, #912724.
 .
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
 .
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
 .
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
 .
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
 .
   [ Holger Levsen ]
   * comment.ent:
 - add url-openpgp-best-practices-fr and use that in fr.po.
 - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
   as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
 Closes: #907915
   * d/control:
 - upgrade to use debhelper-compat(=11), drop d/compat.
 - add "Rules-Requires-Root: no" to support building as non-root.
 - remove Build-Depends on dpkg-dev as it's part of build-essential and the
   required version is present in wheezy.
 - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
   docbook-xsl and dblatex.
 - bump standards version to 4.3.0, no changes needed.
 - sort and wrap Build-Depends-Indep.
 - add myself to uploaders.
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces.
Checksums-Sha1:
 c0e7c80183ab122fe6c6f62d544fd990bd74dfa1 2398 developers-reference_3.4.22.dsc
 46bd729ef368aeeb432370c201731d4ba36e899e 671308 
developers-reference_3.4.22.tar.xz
 4567e7518eff2cbd7639ef772ed00d7b92eae5cf 5199 
developers-reference_3.4.22_source.buildinfo
Checksums-Sha256:
 32caa0599339f67467497cc069befd74e4d95a9d7d21509b5e6cf02fcfa68b24 2398 
developers-reference_3.4.22.dsc
 bc598c8f7a072198a49dfd11c760b7417cd4f72050fef749be517c1daa47 671308 
developers-reference_3.4.22.tar.xz
 da255d205bdbc6b2a80dcf09764753620e38a06b541265658d4f5cddc54ba5df 5199 
developers-reference_3.4.22_source.buildinfo
Files:
 3bbedc689e80798d21bd75fd2c6eddd6 2398 doc optional 

Bug#915310: marked as done (developer-reference: broken link to anonscm.debian.org)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:49 +
with message-id 
and subject line Bug#915310: fixed in developers-reference 3.4.22
has caused the Debian Bug report #915310,
regarding developer-reference: broken link to anonscm.debian.org
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.)


-- 
915310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: developer-reference
Version: 3.4.18

We have a broken link in current master branch.  It also impacts stretch (hence 
my selection of version).

developers-reference (master=)$ git grep anonscm.debian.org
common.ent:https://anonscm.debian.org/cgit/mirror/packages-arch-specific.git/tree/Packages-arch-specific;>
--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 3.4.22

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated developers-reference 
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: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Holger Levsen 
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
Changes:
 developers-reference (3.4.22) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
 doc section on Debian website). Closes: #690750, #912724.
 .
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
 .
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
 .
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
 .
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
 .
   [ Holger Levsen ]
   * comment.ent:
 - add url-openpgp-best-practices-fr and use that in fr.po.
 - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
   as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
 Closes: #907915
   * d/control:
 - upgrade to use debhelper-compat(=11), drop d/compat.
 - add "Rules-Requires-Root: no" to support building as non-root.
 - remove Build-Depends on dpkg-dev as it's part of build-essential and the
   required version is present in wheezy.
 - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
   docbook-xsl and dblatex.
 - bump standards version to 4.3.0, no changes needed.
 - sort and wrap Build-Depends-Indep.
 - add myself to uploaders.
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces.
Checksums-Sha1:
 c0e7c80183ab122fe6c6f62d544fd990bd74dfa1 2398 developers-reference_3.4.22.dsc
 46bd729ef368aeeb432370c201731d4ba36e899e 671308 
developers-reference_3.4.22.tar.xz
 4567e7518eff2cbd7639ef772ed00d7b92eae5cf 5199 
developers-reference_3.4.22_source.buildinfo
Checksums-Sha256:
 32caa0599339f67467497cc069befd74e4d95a9d7d21509b5e6cf02fcfa68b24 2398 
developers-reference_3.4.22.dsc
 bc598c8f7a072198a49dfd11c760b7417cd4f72050fef749be517c1daa47 671308 
developers-reference_3.4.22.tar.xz
 da255d205bdbc6b2a80dcf09764753620e38a06b541265658d4f5cddc54ba5df 5199 
developers-reference_3.4.22_source.buildinfo
Files:
 3bbedc689e80798d21bd75fd2c6eddd6 2398 doc optional 
developers-reference_3.4.22.dsc
 469ca9a880dacf560a109425d4f895cc 671308 doc optional 
developers-reference_3.4.22.tar.xz
 a758cc466bbfa35c5d0f08f2b59bd085 5199 doc optional 
developers-reference_3.4.22_source.buildinfo

-BEGIN 

Bug#907665: marked as done (developers-reference: Section 6.7.9 about dbg packages outdated)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:48 +
with message-id 
and subject line Bug#907665: fixed in developers-reference 3.4.22
has caused the Debian Bug report #907665,
regarding developers-reference: Section 6.7.9 about dbg packages outdated
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.)


-- 
907665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: developers-reference
Severity: normal
Tags: patch

As we now have Automatic Debug Symbol package, I think most of the
section could be deleted and replaced to the references on the Wiki.

The attached patch does that…

-- 
tobi

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

Kernel: Linux 4.17.0-3-amd64 (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)
LSM: AppArmor: enabled
diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk
index 6f05ece..6a85f23 100644
--- a/best-pkging-practices.dbk
+++ b/best-pkging-practices.dbk
@@ -1795,58 +1795,32 @@ it in its official location).
 
 
 Best practices for debug packages
+
 
-A debug package is a package with a name ending in -dbg, that contains
-additional information that gdb can use.  Since Debian 
binaries are stripped by
-default, debugging information, including function names and line numbers, is
-otherwise not available when running gdb on Debian 
binaries.  Debug packages
-allow users who need this additional debugging information to install it,
-without bloating a regular system with the information.
-
-
-It is up to a package's maintainer whether to create a debug package or not.
-Maintainers are encouraged to create debug packages for library packages, since
-this can aid in debugging many programs linked to a library.  In general, debug
-packages do not need to be added for all programs; doing so would bloat the
-archive.  But if a maintainer finds that users often need a debugging version
-of a program, it can be worthwhile to make a debug package for it.  Programs
-that are core infrastructure, such as Apache and the X server are also good
-candidates for debug packages.
-
-
-Some debug packages may contain an entire special debugging build of a library
-or other binary, but most of them can save space and build time by instead
-containing separated debugging symbols that gdb can find 
and load on the fly
-when debugging a program or library.  The convention in Debian is to keep these
-symbols in 
/usr/lib/debug/path, where
-path is the path to the executable or library.  For
-example, debugging symbols for /usr/bin/foo go in
-/usr/lib/debug/usr/bin/foo, and debugging symbols for
-/usr/lib/libfoo.so.1 go in
-/usr/lib/debug/usr/lib/libfoo.so.1.
-
-
-The debugging symbols can be extracted from an object file using 
-objcopy --only-keep-debug.  Then the object file can be 
stripped,
-and objcopy --add-gnu-debuglink used to specify the path
-to the debugging symbol file. 
- objcopy 1
- explains in detail how this works.
-
-
-The dh_strip command in debhelper supports creating debug
-packages, and can take care of using objcopy to separate
-out the debugging symbols for you.  If your package uses debhelper, all you
-need to do is call dh_strip --dbg-package=libfoo-dbg, and
-add an entry to debian/control for the debug package.
+A debug package is a package that contains additional information that
+gdb can use.  Since Debian binaries are stripped by
+default, debugging information, including function names and line
+numbers, is otherwise not available when running gdb
+on Debian binaries.  Debug packages allow users who need this additional
+debugging information to install it, without bloating a regular system
+with the information.
 
+
 
-Note that the debug package should depend on the package that it provides
-debugging symbols for, and this dependency should be versioned.  For example:
+Previously is was up to a package's maintainer whether to create a debug
+package or not. You can still find those manually generated debug
+packages, whose package names generally ended with -dbg.
+
+However, since end of 2015 manually generating dbg packages are
+depreciated and has been replaced largely by automatic debug symbol
+generation, which will generate packages with names ending with -dbgsym.
+
+If you want to migrate your 

Bug#905930: marked as done (www.debian.org: Duplication of text in webpage https://www.debian.org/doc/manuals/developers-reference/ch04.en.html 4.6.5 "Debian 10, will be called buster and Debian 10 wi

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:48 +
with message-id 
and subject line Bug#905930: fixed in developers-reference 3.4.22
has caused the Debian Bug report #905930,
regarding www.debian.org: Duplication of text in webpage 
https://www.debian.org/doc/manuals/developers-reference/ch04.en.html 4.6.5 
"Debian 10, will be called buster and Debian 10 will be called buster."
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.)


-- 
905930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: www.debian.org
Severity: minor

Dear Maintainer,

   * What led up to the situation?
   I am trying to apply to be a non-uploading DD, and I was reading up on the 
approriate documentation.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 N/A
   * What was the outcome of this action?
   No effect, just trying to help.
   * What outcome did you expect instead?
   Corrected during general clean ups as happen.

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

Kernel: Linux 4.17.12-x86_64-linode112 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 3.4.22

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated developers-reference 
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: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Holger Levsen 
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
Changes:
 developers-reference (3.4.22) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
 doc section on Debian website). Closes: #690750, #912724.
 .
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
 .
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
 .
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
 .
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
 .
   [ Holger Levsen ]
   * comment.ent:
 - add url-openpgp-best-practices-fr and use that in fr.po.
 - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
   as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
 Closes: #907915
   * d/control:
 - upgrade to use debhelper-compat(=11), drop d/compat.
 - add "Rules-Requires-Root: no" to support building as non-root.
 - remove Build-Depends on dpkg-dev as it's part of build-essential and the
   required version is present in wheezy.
 - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
   docbook-xsl and dblatex.
 - bump standards version to 4.3.0, no changes needed.
 - sort and wrap Build-Depends-Indep.
 - add myself to uploaders.
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces.
Checksums-Sha1:
 c0e7c80183ab122fe6c6f62d544fd990bd74dfa1 2398 developers-reference_3.4.22.dsc
 46bd729ef368aeeb432370c201731d4ba36e899e 671308 
developers-reference_3.4.22.tar.xz
 

Bug#912724: marked as done (www.debian.org: wrong links to translations of "Debian Developer's Reference")

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:51:49 +
with message-id 
and subject line Bug#912724: fixed in developers-reference 3.4.22
has caused the Debian Bug report #912724,
regarding www.debian.org: wrong links to translations of "Debian Developer's 
Reference"
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.)


-- 
912724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: www.debian.org
Severity: normal
Tags: l10n

Dear Maintainer,

Debian Developer's Reference on the Debian's website [reference]
contains wrong links to translations of the documantation. That is,
French translation is linked as index.fr.en.html (where it should be
index.fr.html) and so on. The same problem holds for translations,
that is French translation [reference-fr] links to Italian as
index.it.fr.html (where it should be index.it.html).

[reference-en] 
https://www.debian.org/doc/manuals/developers-reference/index.en.html

[reference-fr] 
https://www.debian.org/doc/manuals/developers-reference/index.fr.html

I guess the problem is with the content negotiation, since there's no
such problems both in the source code of the documentation and in the
documentation provided in the package developers-reference (and its
translations). It may be possible that content negotiation breaks some
other links to translated documentation in the same way.

With regards,
Lev

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 3.4.22

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated developers-reference 
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: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Holger Levsen 
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
Changes:
 developers-reference (3.4.22) unstable; urgency=medium
 .
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
 doc section on Debian website). Closes: #690750, #912724.
 .
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
 .
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
 .
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
 .
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
 .
   [ Holger Levsen ]
   * comment.ent:
 - add url-openpgp-best-practices-fr and use that in fr.po.
 - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
   as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
 Closes: #907915
   * d/control:
 - upgrade to use debhelper-compat(=11), drop d/compat.
 - add "Rules-Requires-Root: no" to support building as non-root.
 - remove Build-Depends on dpkg-dev as it's part of build-essential and the
   required version is present in wheezy.
 - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
   

Bug#841289: marked as done ([drm/i915] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [2507], reason: Engine(s) hung, action: reset)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 17:21:24 +0100
with message-id 
and subject line Re: Bug#841289: [drm/i915] GPU HANG: ecode 9:0:0xfffe, in 
Xorg [2507], reason: Engine(s) hung, action: reset
has caused the Debian Bug report #841289,
regarding [drm/i915] GPU HANG: ecode 9:0:0xfffe, in Xorg [2507], reason: 
Engine(s) hung, action: reset
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.)


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

Hello,

recently, something on my system related to drm/i915 broke. Since no
xserver/drm packages have been upgraded, I strongly suspect the latest
linux kernel upgrade to be the culprit.

Since several days, the X server on my Lenovo Thinkpad T460 sometimes
freezes, apparently when gnome locks and turns of the screen after some
time of inactivity. This renders the system completely unusable, it
seems to not react at all anymore. Also changing to a text consoly
(tty) doesn't work.

Below you find a copy of the relevant syslog entries. Unfortunately,
since the system is rendered unusable, I'm not able to save the crash
details from /sys/class/drm/card0/error. After reboot, it obviously is
empty again.

Please tell me if I can do anything more to debug this bug. It's very
annoying as it sometimes implies loosing things that you just worked on.

Unfortunately, I don't know another way to reproduce the bug apart from
waiting for the automatic screen lock. Then you have to be (un)lucky
because it doesn't freeze every time.

Cheers,
 jonas

(Assumed) relevant logs from /var/log/syslog:

[...]
Oct 12 21:43:01 calvin2 kernel: [11219.762878] [drm] RC6 on
Oct 12 21:43:25 calvin2 kernel: [11243.760753] [drm] RC6 on
Oct 12 21:43:54 calvin2 kernel: [11272.758240] [drm] RC6 on
Oct 12 21:44:23 calvin2 kernel: [11301.754923] [drm] RC6 on
Oct 12 21:44:40 calvin2 kernel: [11318.753426] [drm] stuck on render ring
Oct 12 21:44:40 calvin2 kernel: [11318.754593] [drm] GPU HANG: ecode 
9:0:0xfffe, in Xorg [2507], reas
on: Engine(s) hung, action: reset
Oct 12 21:44:40 calvin2 kernel: [11318.754599] [drm] GPU hangs can indicate a 
bug anywhere in the entire 
gfx stack, including userspace.
Oct 12 21:44:40 calvin2 kernel: [11318.754603] [drm] Please file a _new_ bug 
report on bugs.freedesktop.o
rg against DRI -> DRM/Intel
Oct 12 21:44:40 calvin2 kernel: [11318.754607] [drm] drm/i915 developers can 
then reassign to the right c
omponent if it's not a kernel issue.
Oct 12 21:44:40 calvin2 kernel: [11318.754610] [drm] The gpu crash dump is 
required to analyze gpu hangs,
 so please always attach it.
Oct 12 21:44:40 calvin2 kernel: [11318.754614] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
Oct 12 21:44:40 calvin2 kernel: [11318.756979] drm/i915: Resetting chip after 
gpu hang
Oct 12 21:44:41 calvin2 kernel: [11319.761430] [drm] RC6 on
Oct 12 21:44:50 calvin2 kernel: [11328.752757] [drm] stuck on render ring
Oct 12 21:44:50 calvin2 kernel: [11328.753891] [drm] GPU HANG: ecode 
9:0:0xfffe, in Xorg [2507], reason: Engine(s) hung, action: reset
Oct 12 21:44:50 calvin2 kernel: [11328.756633] drm/i915: Resetting chip after 
gpu hang
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
EDID vendor "LGD", prod id 1188
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Printing DDC gathered Modelines:
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Modeline "1920x1080"x0.0  138.70  1920 1968 2000 2080  1080 1083 1088  
+hsync -vsync (66.7 kHz eP)
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
EDID vendor "LGD", prod id 1188
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Printing DDC gathered Modelines:
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Modeline "1920x1080"x0.0  138.70  1920 1968 2000 2080  1080 1083 1088  
+hsync -vsync (66.7 kHz eP)
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
EDID vendor "LGD", prod id 1188
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Printing DDC gathered Modelines:
Oct 12 21:44:51 calvin2 /usr/lib/gdm3/gdm-x-session[2505]: (II) modeset(0): 
Modeline "1920x1080"x0.0  138.70  1920 1968 2000 2080  1080 1083 1088  
+hsync -vsync (66.7 kHz eP)
Oct 12 21:44:51 calvin2 kernel: [11329.760399] [drm] RC6 on
Oct 12 21:44:51 calvin2 

Bug#912587: marked as done (firejail AppArmor profile blocks Chromium's usage of ptrace => large amounts of denial logged)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:40:23 +
with message-id 
and subject line Bug#912587: fixed in firejail 0.9.58-1
has caused the Debian Bug report #912587,
regarding firejail AppArmor profile blocks Chromium's usage of ptrace => large 
amounts of denial logged
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.)


-- 
912587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apparmor
Severity: important

Dear Maintainer,
when apparmor is installed, it emits an incredible amount of
logs on dmesg, causing actual important stuff from the kernel
to be missed.

By incredible amount I mean that it fills completely the ring
buffer with crap.

Should it even be logging on dmesg?

Imagine dmesg, only filled of this:
[299560.719237] audit: type=1400 audit(1541071734.314:10526): apparmor="DENIED" 
operation="ptrace" profile="firejail-default" pid=13691 comm="TaskSchedulerSi" 
requested_mask="read" denied_mask="read" peer="firejail-default"
[299560.719241] audit: type=1400 audit(1541071734.314:10527): apparmor="DENIED" 
operation="ptrace" profile="firejail-default" pid=13691 comm="TaskSchedulerSi" 
requested_mask="readby" denied_mask="readby" peer="firejail-default"
[299560.921678] audit: type=1400 audit(1541071734.518:10528): apparmor="DENIED" 
operation="ptrace" profile="firejail-default" pid=13691 comm="TaskSchedulerSi" 
requested_mask="read" denied_mask="read" peer="firejail-default"

For now my solution is to remove apparmor, but it gets sometimes pulled in 
again by other things.

Best

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to it_IT.UTF-8), LANGUAGE=it (charmap=UTF-8) (ignored: LC_ALL set to 
it_IT.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: firejail
Source-Version: 0.9.58-1

We believe that the bug you reported is fixed in the latest version of
firejail, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated firejail 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: Sun, 27 Jan 2019 17:09:49 +0100
Source: firejail
Architecture: source
Version: 0.9.58-1
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 912587 916920
Changes:
 firejail (0.9.58-1) unstable; urgency=medium
 .
   * New upstream release.
   * Mark github-desktop.profile as moved conffile.
   * Allow ptrace read/readby requests in AppArmor profile.
 Thanks to Salvo Tomaselli for the report and intrigeri for help with
 AppArmor. (Closes: #912587)
   * Restrict networking feature by default in firejail.config, as a new
 network namespace can circumvent packet filter of default namespace.
 Thanks to Alain Ducharme for the report. (Closes: #916920)
Checksums-Sha1:
 f145c06ff7c47a08300f4fc77187f22bf2a314a5 2456 firejail_0.9.58-1.dsc
 707a723328c1f70eef4a6be8e7ebd4ed62383e1c 337708 firejail_0.9.58.orig.tar.xz
 8bcdc81eea3ccbef06b0a1026da64f832d7a8bb2 488 firejail_0.9.58.orig.tar.xz.asc
 344c060cb5e66b814a2a0d0c790edcc13b5847a8 11340 firejail_0.9.58-1.debian.tar.xz
 20240d9fe6617349a16a24b5612f1e249a5fc647 5483 
firejail_0.9.58-1_source.buildinfo
Checksums-Sha256:
 8c7c054aaf3c2a0b315b004ab70d693b632d6360fa46972fb07b87c7f3c3a123 2456 
firejail_0.9.58-1.dsc
 2f6fcb58e2544d647b4ec28275ffd5e94f677dfd2ead9acaa17efe6e8567bf7b 337708 
firejail_0.9.58.orig.tar.xz
 113529da4e4760eaece11b60774a5348261ff57dfc337c5a8ac6a74d7d904fb2 488 
firejail_0.9.58.orig.tar.xz.asc
 2edb01d4c2899bb66a76e8d9eb7841a9ff0ac44b3fe07e11ae438e843687a598 11340 
firejail_0.9.58-1.debian.tar.xz
 beb9d8e5cc73e84d1384342c5e547607b7d3a83e6de13237481ea12bf5b1c579 5483 
firejail_0.9.58-1_source.buildinfo
Files:
 

Bug#916920: marked as done (firejail: Firejail allows regular users to bypass root system settings)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:40:23 +
with message-id 
and subject line Bug#916920: fixed in firejail 0.9.58-1
has caused the Debian Bug report #916920,
regarding firejail: Firejail allows regular users to bypass root system settings
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.)


-- 
916920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firejail
Version: 0.9.56-2
Severity: normal

Dear Maintainer,

Firejail being a setuid executable provides regular users root powers to bypass
system settings.
I think it's a problem for an official Debian package to automatically
grant regular users that much power without root having actively granted it
(root might not fully appreciate the powers granted to regular users simply
by installing this enhanced security package).
Perhaps Firejail could be installed by default without the SUID bit set, and
leave it up to root to actively decide if they want to turn it on.
Or, perhaps default /etc/firejail/firejail.config should be set much more
conservatively initially, things like: restricted-network yes

Example:
root sets up system firewall (simple example here, block all outbound):
# nft add table ip filter
# nft add chain ip filter OUTPUT "{ type filter hook output priority 0; policy 
drop; }"
regular user tries:
$ wget http://www.google.com # fails, as expected due to firewall rules
$ firejail --net=enp6s0 --noprofile wget http://www.google.com # works!
regular user is able to bypass all system firewall rules

Thank you

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

Kernel: Linux 4.18.0-3-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firejail depends on:
ii  libapparmor1  2.13.1-3+b1
ii  libc6 2.28-2

Versions of packages firejail recommends:
ii  firejail-profiles  0.9.56-2
ii  iproute2   4.18.0-2
ii  iptables   1.8.2-2+b1
ii  xauth  1:1.0.10-1
ii  xserver-xephyr 2:1.20.3-1

firejail suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: firejail
Source-Version: 0.9.58-1

We believe that the bug you reported is fixed in the latest version of
firejail, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated firejail 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: Sun, 27 Jan 2019 17:09:49 +0100
Source: firejail
Architecture: source
Version: 0.9.58-1
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 912587 916920
Changes:
 firejail (0.9.58-1) unstable; urgency=medium
 .
   * New upstream release.
   * Mark github-desktop.profile as moved conffile.
   * Allow ptrace read/readby requests in AppArmor profile.
 Thanks to Salvo Tomaselli for the report and intrigeri for help with
 AppArmor. (Closes: #912587)
   * Restrict networking feature by default in firejail.config, as a new
 network namespace can circumvent packet filter of default namespace.
 Thanks to Alain Ducharme for the report. (Closes: #916920)
Checksums-Sha1:
 f145c06ff7c47a08300f4fc77187f22bf2a314a5 2456 firejail_0.9.58-1.dsc
 707a723328c1f70eef4a6be8e7ebd4ed62383e1c 337708 firejail_0.9.58.orig.tar.xz
 8bcdc81eea3ccbef06b0a1026da64f832d7a8bb2 488 firejail_0.9.58.orig.tar.xz.asc
 344c060cb5e66b814a2a0d0c790edcc13b5847a8 11340 firejail_0.9.58-1.debian.tar.xz
 20240d9fe6617349a16a24b5612f1e249a5fc647 5483 
firejail_0.9.58-1_source.buildinfo
Checksums-Sha256:
 8c7c054aaf3c2a0b315b004ab70d693b632d6360fa46972fb07b87c7f3c3a123 2456 
firejail_0.9.58-1.dsc
 2f6fcb58e2544d647b4ec28275ffd5e94f677dfd2ead9acaa17efe6e8567bf7b 337708 
firejail_0.9.58.orig.tar.xz
 

Bug#920617: marked as done (gnome-settings-daemon: Please upgrade gnome-settings-daemon-common too.)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 11:07:41 -0500
with message-id 

and subject line Re: Bug#920617: gnome-settings-daemon: Please upgrade 
gnome-settings-daemon-common too.
has caused the Debian Bug report #920617,
regarding gnome-settings-daemon: Please upgrade gnome-settings-daemon-common 
too.
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.)


-- 
920617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-settings-daemon
Version: 3.30.2-1
Severity: normal

Dear Maintainer,

gnome-settings-daemon won’t upgrade because it needs the same version of gnome-
settings-daemon-common.

 gnome-settings-daemon : Depends: gnome-settings-daemon-common (= 3.30.2-2) but
3.30.2-1 is installed



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

Kernel: Linux 4.17.0-3-686-pae (SMP w/3 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-settings-daemon depends on:
ii  gnome-settings-daemon-common  3.30.2-1
ii  gsettings-desktop-schemas 3.28.1-1
ii  libasound21.1.7-2
ii  libc6 2.28-5
ii  libcairo2 1.16.0-2
ii  libcanberra-gtk3-00.30-7
ii  libcanberra0  0.30-7
ii  libcolord21.4.3-4
ii  libcups2  2.2.10-3
ii  libfontconfig12.13.1-2
ii  libgdk-pixbuf2.0-02.38.0+dfsg-7
ii  libgeoclue-2-02.5.2-1
ii  libgeocode-glib0  3.26.0-2
ii  libglib2.0-0  2.58.2-4
ii  libgnome-desktop-3-17 3.30.2-4
ii  libgtk-3-03.24.4-1
ii  libgudev-1.0-0232-2
ii  libgweather-3-15  3.28.2-2
ii  liblcms2-22.9-3
ii  libnm01.14.4-4
ii  libnotify40.7.7-4
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.41-1
ii  libpam-systemd240-4
ii  libpango-1.0-01.42.4-6
ii  libpangocairo-1.0-0   1.42.4-6
ii  libpolkit-gobject-1-0 0.105-25
ii  libpulse-mainloop-glib0   12.2-3
ii  libpulse0 12.2-3
ii  libupower-glib3   0.99.9-3
ii  libwacom2 0.31-1
ii  libwayland-client01.16.0-1
ii  libx11-6  2:1.6.7-1
ii  libxext6  2:1.3.3-1+b2
ii  libxi62:1.7.9-1

Versions of packages gnome-settings-daemon recommends:
ii  iio-sensor-proxy  2.4-2
ii  pulseaudio12.2-3

gnome-settings-daemon suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
We believe this bootstrapping problem is caused by dak being too quick
to remove arch:all packages. gnome-settings-daemon often doesn't build
on the arch:all autobuilder as soon as it builds on other
architectures.

The workaround is for a developer to build the arch:all package
locally and upload it. Here's what I use for my sbuild:

sbuild -d unstable -A --no-arch-any --extra-repository='deb
http://deb.debian.org/debian testing main'

and then I upload the resulting _all.changes file.

Since I've done that for this build of gnome-settings-daemon (it may
take some time to be published) and the underlying bug does not appear
to be in gnome-settings-daemon itself, I am closing this bug. Thank
you for letting us know.


Jeremy Bicha--- End Message ---


Bug#919736: marked as done (tj3: FTBFS (failing tests))

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:08:14 +
with message-id 
and subject line Bug#919736: fixed in tj3 3.6.0-6
has caused the Debian Bug report #919736,
regarding tj3: FTBFS (failing tests)
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.)


-- 
919736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tj3
Version: 3.6.0-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_ruby --build
   dh_ruby --build
localehelper LANG=en_US.UTF-8 rake manual
mkdir -p manual/html
rake vim
rake help2man 
mkdir -p man
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
rake spec
/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*_spec.rb
Run options: exclude {:ruby=>#}
..F.F...

Failures:

  1) TaskJuggler::StatusSheetTest TaskJuggler::StatusSheetSender should have 
matching status sheets in body and attachment
 Failure/Error: bodySheet.should == attachedSheet

   expected: "statussheet boss 2011-03-16-00:00-+ - 
2011-03-23-00:00-+ {\r\n\r\n  # Task: T1\r\n  task t1 ...   #   # Work: 
100%Remaining: 5.0d (10.0d) \r\n#   author r2\r\n# }\r\n  
}\r\n\r\n}\r\n"
got: "statussheet boss 2011-03-16-00:00-+ - 
2011-03-23-00:00-+ {\n\n  # Task: T1\n  task t1 {\n   ...:00-+\n#   
# Work: 100%Remaining: 5.0d (10.0d) \n#   author r2\n# }\n  
}\n\n}\n" (using ==)
 # ./spec/StatusSheets_spec.rb:234:in `block (4 levels) in 
'
 # ./spec/StatusSheets_spec.rb:231:in `each'
 # ./spec/StatusSheets_spec.rb:231:in `block (3 levels) in 
'

  2) TaskJuggler::TimeSheets TaskJuggler::TimeSheetSender should have matching 
timesheets in body and attachment
 Failure/Error: bodySheet.should == attachedSheet

   expected: "timesheet r1 2011-03-14-00:00-+ - 2011-03-21-00:00-+ 
{\r\n\r\n  # Vacation time: 0.0%\r\n\r\...details\r\n  #   ->8-\r\n  # 
}\r\n\r\n  # You have no future assignments for this project!\r\n}\r\n"
got: "timesheet r1 2011-03-14-00:00-+ - 2011-03-21-00:00-+ 
{\n\n  # Vacation time: 0.0%\n\n  # Tas...  Some more details\n  #   ->8-\n  # 
}\n\n  # You have no future assignments for this project!\n}\n" (using ==)
 # ./spec/TimeSheets_spec.rb:220:in `block (4 levels) in 
'
 # ./spec/TimeSheets_spec.rb:217:in `each'
 # ./spec/TimeSheets_spec.rb:217:in `block (3 levels) in 
'

Finished in 24.83 seconds (files took 0.84252 seconds to load)
68 examples, 2 failures

Failed examples:

rspec ./spec/StatusSheets_spec.rb:230 # TaskJuggler::StatusSheetTest 
TaskJuggler::StatusSheetSender should have matching status sheets in body and 
attachment
rspec ./spec/TimeSheets_spec.rb:216 # TaskJuggler::TimeSheets 
TaskJuggler::TimeSheetSender should have matching timesheets in body and 
attachment

/usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*_spec.rb failed
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: tj3
Source-Version: 3.6.0-6

We believe that the bug you reported is fixed in the latest version of
tj3, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug 

Bug#875954: marked as done (courier-mta: /usr/sbin/sendmail has wrong permissions)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 16:40:09 +0100
with message-id 
and subject line Re: courier-mta: /usr/sbin/sendmail has wrong permissions
has caused the Debian Bug report #875954,
regarding courier-mta: /usr/sbin/sendmail has wrong permissions
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.)


-- 
875954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-mta
Version: 0.76.3-5
Severity: important

sendmail gets installed with setgid but has to be installed with setuid.



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (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 courier-mta depends on:
pn  courier-authlib
pn  courier-base   
ii  debconf [debconf-2.0]  1.5.61
ii  init-system-helpers1.48
ii  libc6  2.24-11+deb9u1
pn  libcourier-unicode1
ii  libgcc11:6.3.0-18
ii  libgdbm3   1.8.3-14
ii  libidn11   1.33-1
pn  libnet-cidr-perl   
ii  libperl5.245.24.1-3+deb9u1
ii  libstdc++6 6.3.0-18
ii  sysvinit-utils 2.88dsf-59.9

courier-mta recommends no packages.

Versions of packages courier-mta suggests:
ii  claws-mail [mail-reader]  3.14.1-3+b1
pn  courier-doc   
pn  courier-filter-perl   
pn  couriergrey   
--- End Message ---
--- Begin Message ---
Hi,

given the lack of feedback since 2017-09-19, I'm now going to close this
issue.

Kind Regards

Markus Wanner



signature.asc
Description: OpenPGP digital signature
--- End Message ---


Processed: is in NEW

2019-01-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 917561
Bug #917561 [sponsorship-requests] RFS: opencpn/4.8.8+dfsg.1-1 [ITP] -- 
Chartplotter and Marine Navigation software
Marked Bug as done
>
End of message, stopping processing here.

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



Bug#867681: marked as done (software-properties-gtk: trusted.gpg file created by this package produces gpg error for 'apt-get update')

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 15:35:35 +
with message-id 
and subject line Bug#867681: fixed in software-properties 0.96.24.32.7-1
has caused the Debian Bug report #867681,
regarding software-properties-gtk: trusted.gpg file created by this package 
produces gpg error for 'apt-get update'
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.)


-- 
867681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: software-properties-gtk
Version: 0.96.20.2-1
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?

>> Adding other repos and keys via gui.

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

>> Deleted /etc/apt/trusted.gpg file and all
contents of /var/lib/apt/lists directory.

   * What was the outcome of this action?

>>'app-get update' didn't give any errors.

   * What outcome did you expect instead?

>> Same as the above mentioned.

Note: Got the temporary fix from
https://readlist.com/lists/lists.debian.org/debian-user/77/388466.html

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



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

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

Versions of packages software-properties-gtk depends on:
ii  gir1.2-gtk-3.0   3.22.11-1
ii  python3  3.5.3-1
ii  python3-gi   3.22.0-2
ii  python3-software-properties  0.96.20.2-1
ii  software-properties-common   0.96.20.2-1

software-properties-gtk recommends no packages.

Versions of packages software-properties-gtk suggests:
ii  gnome-software  3.22.5-1
--- End Message ---
--- Begin Message ---
Source: software-properties
Source-Version: 0.96.24.32.7-1

We believe that the bug you reported is fixed in the latest version of
software-properties, 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 867...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated software-properties 
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: Sat, 26 Jan 2019 22:52:33 +0100
Source: software-properties
Binary: python3-software-properties software-properties-common 
software-properties-gtk software-properties-kde
Architecture: source
Version: 0.96.24.32.7-1
Distribution: experimental
Urgency: medium
Maintainer: Julian Andres Klode 
Changed-By: Julian Andres Klode 
Description:
 python3-software-properties - manage the repositories that you install 
software from
 software-properties-common - manage the repositories that you install software 
from (common)
 software-properties-gtk - manage the repositories that you install software 
from (gtk)
 software-properties-kde - manage the repositories that you install software 
from (qt)
Closes: 867681
Changes:
 software-properties (0.96.24.32.7-1) experimental; urgency=medium
 .
   * Merge with Ubuntu 18.04 LTS; remaining changes:
 - Do not use dh-translations (and now dh-migrations as well)
 - Occasional indentation changes in debian/
 - Drop aptdaemon, qapt, and ubuntu-drivers
 - Updated debian/copyright
 - Various patches
   * Amongst other things, this fixes apt-key management (Closes: #867681)
   * {Build-},Depend on gpg, gpg-agent
 .
 software-properties (0.96.24.32.7) bionic; urgency=medium
 .
   * SoftwarePropertiesGtk.py: when checking a package's depends for DKMS also
 pass on an AttributeError (LP: #1807373)
 .
 software-properties (0.96.24.32.6) bionic; urgency=medium
 .
   * cloudarchive: Enable support for the Stein Ubuntu Cloud Archive on
 18.04 (LP: #1805436).
 .
 software-properties (0.96.24.32.5) bionic; 

Bug#898881: marked as done (conntrack-tools FTCBFS: does not pass --host to ./configure)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 15:34:11 +
with message-id 
and subject line Bug#898881: fixed in conntrack-tools 1:1.4.5-2
has caused the Debian Bug report #898881,
regarding conntrack-tools FTCBFS: does not pass --host to ./configure
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.)


-- 
898881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: conntrack-tools
Version: 1:1.4.5-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

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

Helmut
diff --minimal -Nru conntrack-tools-1.4.5/debian/changelog 
conntrack-tools-1.4.5/debian/changelog
--- conntrack-tools-1.4.5/debian/changelog  2018-05-01 12:59:52.0 
+0200
+++ conntrack-tools-1.4.5/debian/changelog  2018-05-17 06:03:41.0 
+0200
@@ -1,3 +1,11 @@
+conntrack-tools (1:1.4.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes:
+#-1)
+
+ -- Helmut Grohne   Thu, 17 May 2018 06:03:41 +0200
+
 conntrack-tools (1:1.4.5-1) unstable; urgency=medium
 
   * [9fa49d0] d/control: point VCS-* to salsa.debian.org
diff --minimal -Nru conntrack-tools-1.4.5/debian/rules 
conntrack-tools-1.4.5/debian/rules
--- conntrack-tools-1.4.5/debian/rules  2018-05-01 12:51:37.0 +0200
+++ conntrack-tools-1.4.5/debian/rules  2018-05-17 06:03:41.0 +0200
@@ -7,7 +7,7 @@
dh $@
 
 override_dh_auto_configure:
-   ./configure --prefix=/usr --disable-silent-rules --enable-systemd
+   dh_auto_configure -- --libdir='$${prefix}/lib' --enable-systemd
 
 override_dh_strip:
dh_strip --dbgsym-migration='conntrack-tools-dbg (<< 
1:1.4.4+snapshot20161117-1)'
--- End Message ---
--- Begin Message ---
Source: conntrack-tools
Source-Version: 1:1.4.5-2

We believe that the bug you reported is fixed in the latest version of
conntrack-tools, 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 898...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arturo Borrero Gonzalez  (supplier of updated 
conntrack-tools 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: Sun, 27 Jan 2019 12:40:28 +0100
Source: conntrack-tools
Architecture: source
Version: 1:1.4.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Arturo Borrero Gonzalez 
Closes: 898881 916138
Changes:
 conntrack-tools (1:1.4.5-2) unstable; urgency=medium
 .
   * [5ce3c64] d/conntrackd.manpages: add file
   * [a099cb5] d/rules: simplify dh_auto_configure call (Closes: #898881)
   * [2315dfd] d/patches: add upstream_conntrackd.conf.8.patch (Closes: #916138)
   * [40fd6d5] src:conntrack-tools: bump standards-version to 4.3.0
   * [6478616] d/control: suggests nftables
   * [dbe1816] d/changelog: cleanup trailing whitespaces
   * [5d22f2d] d/rules: drop dh_strip override for dbgsym migration
Checksums-Sha1:
 d2e35cdf561a8c7cedf8b2122d02b868240a5e0b 2491 conntrack-tools_1.4.5-2.dsc
 106b54ce847e6e9724dfc143acf71251c83afddb 10216 
conntrack-tools_1.4.5-2.debian.tar.xz
 71677f2ab6551bdb598af5ca051b7b094265ef11 6888 
conntrack-tools_1.4.5-2_amd64.buildinfo
Checksums-Sha256:
 b0780b36c48a24a9da4a19ee47ed18ff9577318323174b54360128fc8638b4a2 2491 
conntrack-tools_1.4.5-2.dsc
 1e48dca8f237f1d288531f4d94ab72cdba04d08f37d1d2ab5ef3bc1e986f6c99 10216 
conntrack-tools_1.4.5-2.debian.tar.xz
 c69491e1988fd8ef7942a6f59ad693bd658d18cc680b90c56588f73810164b1c 6888 
conntrack-tools_1.4.5-2_amd64.buildinfo
Files:
 2804fb48bdfd4368e3dd0df137040bb2 2491 net optional conntrack-tools_1.4.5-2.dsc
 9bd95ea8c8c35213a669846082d0a836 10216 net optional 
conntrack-tools_1.4.5-2.debian.tar.xz
 a13c6767960c03da43c729b374d3a9e7 6888 net optional 
conntrack-tools_1.4.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-


Bug#916138: marked as done (conntrackd: State Accept/Ignore isn't working, always get symbol '}': syntax error. Even "SYNC EXAMPLE 2" from manpage fails.)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 15:34:11 +
with message-id 
and subject line Bug#916138: fixed in conntrack-tools 1:1.4.5-2
has caused the Debian Bug report #916138,
regarding conntrackd: State Accept/Ignore isn't working, always get symbol '}': 
syntax error. Even "SYNC EXAMPLE 2" from manpage fails.
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.)


-- 
916138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: conntrackd
Version: 1:1.4.4+snapshot20161117-5
Severity: normal

Dear Maintainer,

the block

State Accept {
    ESTABLISHED CLOSED TIME_WAIT CLOSE_WAIT
}

is not working and throw a syntax error.

Even the examples in all manuals have this problem.

If I move the block upwards under "filter from userspace/kernelspace" the syntax
error line number get smaller.

[ERROR] parsing config file in line (48), symbol '}': syntax error

If I uncomment the block, the config work.

Thank you in advance, Eike


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

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

Versions of packages conntrackd depends on:
ii  init-system-helpers  1.48
ii  libc6    2.24-11+deb9u3
ii  libmnl0  1.0.4-2
ii  libnetfilter-conntrack3  1.0.6-2
ii  libnetfilter-cthelper0   1.0.0-1
ii  libnetfilter-queue1  1.0.2-2
ii  libnfnetlink0    1.0.1-3
ii  libsystemd0  232-25+deb9u6

conntrackd recommends no packages.

conntrackd suggests no packages.

-- Configuration Files:
/etc/conntrackd/conntrackd.conf changed:
   Sync {
    Mode NOTRACK {
 DisableInternalCache on
 DisableExternalCache on
    }
    TCP {
 IPv4_address 192.168.2.100
 IPv4_Destination_Address 192.168.2.101
 Port 3780
 Interface eth2
 SndSocketBuffer 1249280
 RcvSocketBuffer 1249280
 Checksum on
    }
    Options {
 TCPWindowTracking Off
 ExpectationSync On
    }
   }
   General {
    Systemd on
    HashSize 32768
    HashLimit 131072
    LogFile on
    Syslog offconntrackd: State Accept/Ignore isn't working, always get
symbol '}': syntax error. Also "SYNC EXAMPLE 2" from manpage fails.
    LockFile /var/lock/conntrack.lock
    UNIX {
 Path /var/run/conntrackd.ctl
    }
    NetlinkBufferSize 2097152
    NetlinkBufferSizeMaxGrowth 8388608
    NetlinkOverrunResync On
    NetlinkEventsReliable Off
    EventIterationLimit 100
    Filter From Userspace {
 Protocol Accept {
  TCP
  SCTP
  DCCP
 }
 Address Ignore {
  IPv4_address 127.0.0.1
  IPv4_address 192.168.0.0/16
  IPv6_address ::1
 }
 State Accept {
  ESTABLISHED CLOSED TIME_WAIT CLOSE_WAIT
 }
    }
   }


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: conntrack-tools
Source-Version: 1:1.4.5-2

We believe that the bug you reported is fixed in the latest version of
conntrack-tools, 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 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arturo Borrero Gonzalez  (supplier of updated 
conntrack-tools 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: Sun, 27 Jan 2019 12:40:28 +0100
Source: conntrack-tools
Architecture: source
Version: 1:1.4.5-2
Distribution: unstable
Urgency: medium
Maintainer: 

Bug#920558: marked as done (RFS: liboauth/1.0.3-2 [QA])

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 15:28:58 +
with message-id <20190127152858.a7lbb2cj7iv47...@master.debian.org>
and subject line removed from mentors
has caused the Debian Bug report #920558,
regarding RFS: liboauth/1.0.3-2 [QA]
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.)


-- 
920558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: liboauth
   Version : 1.0.3-2
   Upstream Author : Robin Gareus 
 * URL : http://liboauth.sourceforge.net/
 * License : Expat
   Section : libs

  It builds these binary packages:

 liboauth-dev - C library implementing OAuth Core 1.0a API (development files)
 liboauth0  - C library implementing OAuth Core 1.0a API (runtime)

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

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


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

dget -ux 
https://mentors.debian.net/debian/pool/main/libo/liboauth/liboauth_1.0.3-2.dsc

  My changes have also been temporarily pushed to
  https://salsa.debian.org/e7appew-guest/liboauth.git.

  Changes since the last upload:

  * QA upload.
  * Update debian/gbp.conf to conform with DEP14 conventions.
  * Update VCS details.
  * Simplify LFS build rules.
  * Build verbosely.
  * Update Lintian override to use debian-watch-does-not-check-gpg-signature
tag.
  * Build with Debhelper compat level 12.
  * Set "Rules-Requires-Root: no".
  * Add Build-Depends-Package details to symbols file.
  * Update debian/copyright.
  * Add machine-readable upstream metadata.
  * Update debian/watch.
  * Replace 03_man_page_typos.patch with 03_fix_typos.patch to fix more
typos detected.
  * Indicate that the patches that I have personally authored have
been forwarded upstream.
  * Indicate compliance with Debian Policy 4.3.0.


  Regards,
   Carlos Maddela
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4720--- End Message ---


Bug#890190: marked as done ([compiz-plugins-default] Plugin "wall" doesn't honor edge-delay)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 15:06:19 +
with message-id 
and subject line Bug#890190: fixed in compiz 2:0.8.16.1-6
has caused the Debian Bug report #890190,
regarding [compiz-plugins-default] Plugin "wall" doesn't honor edge-delay
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.)


-- 
890190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: compiz-plugins-default
Version: 1:0.9.13.0+16.10.20160818.2-5.1
Severity: important

--- Please enter the report below this line. ---
According to e.g., https://www.mail-archive.com/compiz@lists.launchpad.
net/msg11314.html, the plugin "wall" has a hidden option "nodelay". It
disables the plugin's ability to use the general option "edge delay" to
wait before the edge flip is started.

The first problem is that the default setting is "true", i.e., don't
delay. The user can adjust in CCSM --> General --> General Options -->
Edge Trigger Delay, but will get frustrated as it is ignored by Compiz.

Some users could try to search the internet for solutions. Several
forum posts suggest to edit /usr/share/compiz/wall.xml and change all
instances of true to false.

The second problem is that with the current version this workaround
doesn't even work any more. See e.g., https://bugs.launchpad.net/ubuntu
/+source/compiz/+bug/771463?comments=all.

So please:
 - fix the behavior of the "wall" plugin
 - set the default of nodelay to false

--- System information. ---
Architecture: 
Kernel:   Linux 4.14.0-3-amd64

Debian Release: buster/sid
  500 unstablewww.deb-multimedia.org 
  500 unstablehttp.at.debian.org 
  500 testing www.deb-multimedia.org 
  500 testing http.at.debian.org 
  500 stable  http.at.debian.org 
1 experimentalhttp.at.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-
compiz-core  (= 1:0.9.13.0+16.10.20160818.2-5.1) | 
1:0.9.13.0+16.10.20160818.2-5.1
libdecoration0   (= 1:0.9.13.0+16.10.20160818.2-5.1) | 
1:0.9.13.0+16.10.20160818.2-5.1
libc6  (>= 2.14) | 
libcairo2 (>= 1.2.4) | 
libgcc1   (>= 1:3.0) | 
libgl1-mesa-glx  | 
 OR libgl1   | 
libglib2.0-0 (>= 2.16.0) | 
libglibmm-2.4-1v5(>= 2.50.0) | 
libice6 (>= 1:1.0.0) | 
libpng16-16 (>= 1.6.2-1) | 
libsigc++-2.0-0v5 (>= 2.2.0) | 
libsm6   | 
libstartup-notification0(>= 0.2) | 
libstdc++6  (>= 5.2) | 
libx11-6 | 
libx11-xcb1  | 
libxcb1  | 
libxcomposite1  (>= 1:0.3-1) | 
libxcursor1   (>> 1.1.2) | 
libxdamage1   (>= 1:1.1) | 
libxext6(>= 2:1.3.0) | 
libxfixes3  (>= 1:4.0.1) | 
libxi6   | 
libxinerama1 | 
libxml2   (>= 2.7.4) | 
libxrandr2  (>= 4.3) | 
libxrender1  | 
libxslt1.1   (>= 1.1.25) | 


Package's Recommends field is empty.

Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Source: compiz
Source-Version: 2:0.8.16.1-6

We believe that the bug you reported is fixed in the latest version of
compiz, 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 

Bug#914804: marked as done (pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lcuda)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 13:52:33 +
with message-id 
and subject line Bug#914804: fixed in pycuda 2018.1.1-3
has caused the Debian Bug report #914804,
regarding pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lcuda
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.)


-- 
914804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycuda
Version: 2018.1.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

I tried to manually binNMU pycuda for boost1.67, but it failed with

[...]
x86_64-linux-gnu-g++ -pthread -shared -Wl,-Bsymbolic-functions -Wl,-z,relro 
-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-A8UpPM/python2.7-2.7.15=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now -g -O2 -fdebug-prefix-map=/build/pycuda-2018.1.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 build/temp.linux-amd64-2.7/src/cpp/cuda.o 
build/temp.linux-amd64-2.7/src/cpp/bitlog.o 
build/temp.linux-amd64-2.7/src/wrapper/wrap_cudadrv.o 
build/temp.linux-amd64-2.7/src/wrapper/mempool.o 
build/temp.linux-amd64-2.7/src/wrapper/wrap_cudagl.o 
build/temp.linux-amd64-2.7/src/wrapper/wrap_curand.o -L/usr/lib/stubs 
-L/usr/lib64/stubs -L/usr/lib/stubs -L/usr/lib64/stubs -lboost_python-py27 
-lboost_thread -lcuda -lcurand -o 
/build/pycuda-2018.1.1/.pybuild/cpython2_2.7/build/pycuda/_driver.so
/usr/bin/ld: cannot find -lboost_python-py27
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-g++' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:26: binary-arch] Error 25


(there may have been earlier errors, I unfortunately do not have
the full log, only the last screen)


Andreas
--- End Message ---
--- Begin Message ---
Source: pycuda
Source-Version: 2018.1.1-3

We believe that the bug you reported is fixed in the latest version of
pycuda, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tomasz Rybak  (supplier of updated pycuda 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: Sun, 27 Jan 2019 14:23:34 +0100
Source: pycuda
Binary: python-pycuda python-pycuda-dbg python-pycuda-doc python3-pycuda 
python3-pycuda-dbg
Architecture: source amd64 all
Version: 2018.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Tomasz Rybak 
Description:
 python-pycuda - Python module to access Nvidia‘s CUDA parallel computation API
 python-pycuda-dbg - Python module to access Nvidia‘s CUDA API (debug 
extensions)
 python-pycuda-doc - module to access Nvidia‘s CUDA computation API 
(documentation)
 python3-pycuda - Python 3 module to access Nvidia‘s CUDA parallel computation 
API
 python3-pycuda-dbg - Python 3 module to access Nvidia‘s CUDA API (debug 
extensions)
Closes: 914804
Changes:
 pycuda (2018.1.1-3) unstable; urgency=medium
 .
   * Rebuild with CUDA 9.2 (Closes: #914804)
   * Update debian/watch to new version and to use substitution variables.
Checksums-Sha1:
 940f1ad3fac607b9b16127e3ace16bbc90e4c9d9 2715 pycuda_2018.1.1-3.dsc
 53a88c7b0efafe411527a5f9c9b6efd9eb863978 10912 pycuda_2018.1.1-3.debian.tar.xz
 e92b8c9ea86bf896069e8fa981dc8062cf07e917 13243 
pycuda_2018.1.1-3_amd64.buildinfo
 fd68414036a1e270cfee02cfdb3a8c3483267be9 6102308 
python-pycuda-dbg_2018.1.1-3_amd64.deb
 ae932020cc541f9ac73bde13723772c56864cda2 125184 
python-pycuda-doc_2018.1.1-3_all.deb
 4ef4adcc6e4220efe21307798bdcff45e7722abd 315604 
python-pycuda_2018.1.1-3_amd64.deb
 b3562e777a6aea5e0d60cb901bbeb50cb8716dd1 6130904 
python3-pycuda-dbg_2018.1.1-3_amd64.deb
 194237d7d664b504399f5e9beb56da0152f10de1 314760 
python3-pycuda_2018.1.1-3_amd64.deb
Checksums-Sha256:
 

Bug#920597: marked as done (docker.io: Unable to start daemon: "containerd" executable file not found in PATH)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 13:51:00 +
with message-id 
and subject line Bug#920597: fixed in docker.io 18.09.1+dfsg1-3
has caused the Debian Bug report #920597,
regarding docker.io: Unable to start daemon: "containerd" executable file not 
found in PATH
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.)


-- 
920597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 18.09.1+dfsg1-2
Severity: serious
X-Debbugs-CC: arnaud.rebill...@collabora.com

Docker daemon is unable to start:


Failed to start containerd: exec: "containerd": executable file not found in 
$PATH



signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: docker.io
Source-Version: 18.09.1+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
docker.io, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated docker.io 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: Sun, 27 Jan 2019 23:43:53 +1100
Source: docker.io
Binary: docker-doc docker.io docker.io-dbgsym golang-docker-dev 
golang-github-docker-docker-dev vim-syntax-docker
Architecture: source all amd64
Version: 18.09.1+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 docker-doc - Linux container runtime -- documentation
 docker.io  - Linux container runtime
 golang-docker-dev - Transitional package for golang-github-docker-docker-dev
 golang-github-docker-docker-dev - reusable Go packages included with Docker
 vim-syntax-docker - Docker container engine - Vim highlighting syntax files
Closes: 920597
Changes:
 docker.io (18.09.1+dfsg1-3) unstable; urgency=medium
 .
   * New patch to fix name of the "containerd" executable (Closes: #920597).
Checksums-Sha1:
 b1dc1e4c48927bb1022144b7f6d6e445332ddcbb 8933 docker.io_18.09.1+dfsg1-3.dsc
 0a700dd150381f14af84a36d0df7ad2aaa643a03 40520 
docker.io_18.09.1+dfsg1-3.debian.tar.xz
 21f6cd26d8a937d17cd7b9a68059abf969fa9439 974648 
docker-doc_18.09.1+dfsg1-3_all.deb
 b6d7b184c764742e4e81a8220611f459a903ced3 7122520 
docker.io-dbgsym_18.09.1+dfsg1-3_amd64.deb
 50b3b8222cf352a671d4ff44cabf106e66ad90e7 25559 
docker.io_18.09.1+dfsg1-3_amd64.buildinfo
 73a32d5c8f186332a5930a4137f844b239eb7739 53525024 
docker.io_18.09.1+dfsg1-3_amd64.deb
 0cded981b8dba6407fb97b869bb5fb2d2f310d51 20096 
golang-docker-dev_18.09.1+dfsg1-3_all.deb
 a000c0474a0d8539ec3e24c2b678c571fc4f5a0a 532492 
golang-github-docker-docker-dev_18.09.1+dfsg1-3_all.deb
 71b04234abc70fd631e2916ece1942eb03510af9 21260 
vim-syntax-docker_18.09.1+dfsg1-3_all.deb
Checksums-Sha256:
 5cda0d271e10f5e5c89f04cd6e82ed2bde6ce0edf179f85048f68b7f1c88a236 8933 
docker.io_18.09.1+dfsg1-3.dsc
 34cebd557e4658e480f12284a059b99a27ca526c51b1c04fcd522978a50c06b4 40520 
docker.io_18.09.1+dfsg1-3.debian.tar.xz
 ca5ba01157d1747092566c03e174e1d7c3c2b44eee854fae5dfa1e4699a6394b 974648 
docker-doc_18.09.1+dfsg1-3_all.deb
 ac17e9dbde21490de928d2b11c6d5060a825644ec040a48ab96f4537e3b6e903 7122520 
docker.io-dbgsym_18.09.1+dfsg1-3_amd64.deb
 038ab8a198f83130cc838ff6c81df37fb87d6226edb4be176f3ae768c82c4d8d 25559 
docker.io_18.09.1+dfsg1-3_amd64.buildinfo
 9c4744d0ecca3c90339cf3eccc59603b7c4931106bbf811ba75c7829818aacfa 53525024 
docker.io_18.09.1+dfsg1-3_amd64.deb
 d48403317fe92d41e88feb1a316fc49fc06ec5e674b575c12236846d9923af38 20096 
golang-docker-dev_18.09.1+dfsg1-3_all.deb
 1b50f8c4e44c36d96b722a4434875d0c9812e955dd9f1a89a4fd7b3c630fbf7d 532492 
golang-github-docker-docker-dev_18.09.1+dfsg1-3_all.deb
 8b6a844b10faaa56aeaa0af40bd97121f099e8bf734f44e6938b5cf8348591b3 21260 
vim-syntax-docker_18.09.1+dfsg1-3_all.deb
Files:
 a5db07b642e61c20a274eb5ac22bd05b 8933 admin optional 
docker.io_18.09.1+dfsg1-3.dsc
 36ae6429627843e7742a64c4bdf9ea5d 40520 admin optional 
docker.io_18.09.1+dfsg1-3.debian.tar.xz
 5804d8d995a2a1305e4c3fc7359e9e33 974648 doc optional 

Bug#916256: marked as done (gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 23:55:54 +1100
with message-id <4197763.WzzgV0LaB0@deblab>
and subject line Re: [pkg-go] Bug#916256: Bug#916256: Bug#916256: gitlab-runner 
fails when it tries to pull docker image gitlab-runner-helper:11.2.0
has caused the Debian Bug report #916256,
regarding gitlab-runner fails when it tries to pull docker image 
gitlab-runner-helper:11.2.0
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.)


-- 
916256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab-runner
Version: 11.2.0+dfsg-2
Severity: important

Dear Maintainer,

Summary
---
gitlab-runner executes docker for the first time it tries to download docker
image gitlab-runner-helper:11.2.0
but it fails because repository does not exists with this tag name.

Related links:
* https://hub.docker.com/r/gitlab/gitlab-runner-helper/tags/

Expected behavior
-
gitlab-runner should be able to find the right tag name of gitlab-runner-
helper.

Error
-
ERRO[] Docker executor: prebuilt image helpers will be loaded from
/var/lib/gitlab-runner.
Running with gitlab-runner 11.2.0 (11.2.0)
Using Docker executor with image registry.gitlab.com/:latest ...
Pulling docker image gitlab-runner-helper:11.2.0 ...
ERROR: Job failed: Error response from daemon: pull access denied for gitlab-
runner-helper, repository does not exist or may require 'docker login'
(executor_docker.go:166:1s)
FATAL: Error response from daemon: pull access denied for gitlab-runner-helper,
repository does not exist or may require 'docker login'
(executor_docker.go:166:1s)

Command
---
$ gitlab-runner exec docker --docker-volumes $PWD/builds:/builds build

Workaround
--
Download gitlab-runner-helper 11.2.0 version using x86_64-6d9dd510 tag and
rename it locally.
$ docker run --rm -it gitlab/gitlab-runner-helper:x86_64-6d9dd510
$ docker tag  gitlab/gitlab-runner-helper:x86_64-6d9dd510 gitlab-runner-
helper:11.2.0
Now you can execute:
$ gitlab-runner exec docker --docker-volumes $PWD/builds:/builds build



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

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

Versions of packages gitlab-runner depends on:
ii  adduser  3.118
ii  ca-certificates  20170717
ii  git  1:2.19.2-1
ii  libc62.27-8
ii  lsb-base 10.2018112800

Versions of packages gitlab-runner recommends:
ii  cdebootstrap  0.7.7+b1
ii  xz-utils  5.2.2-1.3

Versions of packages gitlab-runner suggests:
ii  docker.io  18.06.1+dfsg1-2

-- Configuration Files:
/etc/gitlab-runner/config.toml [Errno 13] Permission denied: 
'/etc/gitlab-runner/config.toml'

-- no debconf information
--- End Message ---
--- Begin Message ---
On Friday, 25 January 2019 4:56:33 PM AEDT Dean Hamstead wrote:
> That said, this error would occur if the kubernetes cluster is external
> to the debian machine that runs the runner? (which is my scenario) as
> that docker instance running on the kubernetes node would not have that
> 'local' image?

Yes, gitlab-runner package produces helper image during post-install stage 
and when necessary it is imported into local store for Docker to use.

This would work only when Docker is running by the time when gitlab-runner is 
installed because the latter uses "docker build" command to generate helper 
image.


> by manually setting the helper_image to something in the gitlab/ space -
> things work for me

Thank you for reporting workaround. It might be useful to some.


> They are ubuntu it seems but they are entirely encapsulated as part of
> the service.

I'm going to close this bug since it is not even about a Debian package which 
is probably has been installed improperly... There is nothing I could do 
about the package to help with this problem.

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

-- 
Regards,
 Dmitry Smirnov.

---

Sometimes the first duty of intelligent men is the restatement of the
obvious.
-- George Orwell


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


Bug#919918: marked as done (scikit-learn FTBFS on armel/armhf/arm64/ppc64el/s390x: test failures)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 12:50:32 +
with message-id 
and subject line Bug#919918: fixed in scikit-learn 0.20.2+dfsg-2
has caused the Debian Bug report #919918,
regarding scikit-learn FTBFS on armel/armhf/arm64/ppc64el/s390x: test failures
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.)


-- 
919918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-learn
Version: 0.20.1+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=scikit-learn=sid

There are several, potentially unrelated, test failures
on various architectures.
--- End Message ---
--- Begin Message ---
Source: scikit-learn
Source-Version: 0.20.2+dfsg-2

We believe that the bug you reported is fixed in the latest version of
scikit-learn, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated scikit-learn 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: Sun, 27 Jan 2019 11:41:13 +0100
Source: scikit-learn
Binary: python-sklearn python-sklearn-lib python3-sklearn python3-sklearn-lib 
python-sklearn-doc
Architecture: source
Version: 0.20.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Ole Streicher 
Description:
 python-sklearn - Python modules for machine learning and data mining - Python 2
 python-sklearn-doc - documentation and examples for scikit-learn
 python-sklearn-lib - low-level implementations and bindings for scikit-learn
 python3-sklearn - Python modules for machine learning and data mining - Python 
3
 python3-sklearn-lib - low-level implementations and bindings for scikit-learn 
- Python
Closes: 919918
Changes:
 scikit-learn (0.20.2+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Skip tests that fail on non-intel platforms. Closes: #919918
Checksums-Sha1:
 b455bc66cb0e152f713eb1d78752ac5871ad0200 3346 scikit-learn_0.20.2+dfsg-2.dsc
 a72db918b69b20a7eae44de6867f18eb29d12cdf 21020 
scikit-learn_0.20.2+dfsg-2.debian.tar.xz
Checksums-Sha256:
 6ffa71e735fb7d9cd3e534f28dde936d1c2e2c07b2288c93fdd15a296c29510b 3346 
scikit-learn_0.20.2+dfsg-2.dsc
 4f427fa4ec6e75e6d02da4bf18e6c9874ad28c120fa6eac8dae02af09582d7ab 21020 
scikit-learn_0.20.2+dfsg-2.debian.tar.xz
Files:
 0f0a673aeda88555b8017da735e7b54f 3346 python optional 
scikit-learn_0.20.2+dfsg-2.dsc
 f7ae6a65a9f1291650c735928f8f243d 21020 python optional 
scikit-learn_0.20.2+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAlxNpZEACgkQcRWv0HcQ
3PdzQg/5AcmrfAnRvbeCMqBm1stzxW3tQcnD6pCpViffzzh1ZD+ZuNw6HkNm0nhb
97to7OnrFAQuOlu9/KjLsNzccEEtc1CfvB9A45n3BpviQCTaRhmOq+V/whmbnqvt
eWlj9REhcNoBdVIT9Qfww1ZX16eLp3SerHJxBsrRo2G1VJqdsmNKjS/oqehLMIYd
r56QD/39ICwzrs0hCdvCKgYNUle0W/2I5ff4inWmK9Glpbr9oHiHdxCXHOE9FGan
3ms4gqaIwjKkqBai1MhWIyY834w0O7viLJtqmbwhoCdLz/DRLzJYX45T64oBrD5A
0I9lWM47USQMYf0LWwJPrIS3QqhpxDS8YCexvHjycZQTQktW35CT0iwLcFbMHIdw
aFEfIWP3LDPJ6R3yogcW2ITuHtBACFjXbYCdCFEfffxsgXPdQ4bxoiwpsSfhVtQm
lgGlTPpJBEHxt9kCleFDgmx/9EWZjDO3jGhGk9sT+xcPWueYQGwM1bBpaxM9ovPM
yRA14nuHoz2k8Z/5pLUSTJNUS3N7Jt1DzpcY4gGezzsT7OxdAvzZcEW1uFuniHHc
SE20m7UwrZENOk0yFGCP2Fti9zHQmXmw/LsnXcSa36dq99kHfUDyGxTJOUOTjAB/
DMseSll2Gl7dqs8WKFKZOwS/JbFjJUejZGk/wfWZOmr7ujW7hrU=
=997f
-END PGP SIGNATURE End Message ---


Processed: Re: stretch-backports: needs newer python3-urllib3

2019-01-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 920160
Bug #920160 [netdata] stretch-backports: needs newer python3-urllib3
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#919535: marked as done (surf: AppArmor profile forbids access to publicsuffix data)

2019-01-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Jan 2019 12:21:46 +
with message-id 
and subject line Bug#919535: fixed in surf 2.0+git20181009-4
has caused the Debian Bug report #919535,
regarding surf: AppArmor profile forbids access to publicsuffix data
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.)


-- 
919535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: surf
Version: 2.0+git20181009-2.1
Severity: normal
Tags: patch

Dear Maintainer,

surf is not able to access the following two files due to its apparmor
profile:

[ 5565.325749] audit: type=1400 audit(1547681461.606:127): apparmor="DENIED" 
operation="open" profile="/usr/bin/surf" 
name="/usr/share/publicsuffix/public_suffix_list.dafsa" pid=29897 
comm="WebKitNetworkPr" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 5565.328420] audit: type=1400 audit(1547681461.610:128): apparmor="DENIED" 
operation="open" profile="/usr/bin/surf" 
name="/usr/share/publicsuffix/public_suffix_list.dat" pid=29897 
comm="WebKitNetworkPr" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

I have included a patch.

Regards,
Leo
-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armhf (armv7l)

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

Versions of packages surf depends on:
ii  libc6 2.28-5
ii  libgcr-base-3-1   3.28.0-4
ii  libgcr-ui-3-1 3.28.0-4
ii  libglib2.0-0  2.58.2-3
ii  libgtk-3-03.24.2-3
ii  libwebkit2gtk-4.0-37  2.22.5-1
ii  libx11-6  2:1.6.7-1

Versions of packages surf recommends:
ii  curl 7.62.0-1
ii  suckless-tools   44-1
ii  x11-utils7.7+4
ii  xterm [x-terminal-emulator]  342-1

Versions of packages surf suggests:
ii  apparmor  2.13.2-3

-- Configuration Files:
/etc/apparmor.d/usr.bin.surf changed [not included]

-- no debconf information
>From 092793cac1b5dd01a62f910497c95b51d28dc674 Mon Sep 17 00:00:00 2001
From: Leo Singer 
Date: Wed, 16 Jan 2019 23:40:11 +
Subject: [PATCH] Tell apparmor to allow access to publicsuffix data

---
 debian/changelog| 7 +++
 debian/usr.bin.surf | 1 +
 2 files changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 7e6f003..c002849 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+surf (2.0+git20181009-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Tell apparmor to allow read access to publicsuffix data.
+
+ -- Leo Singer   Wed, 16 Jan 2019 23:39:11 +
+
 surf (2.0+git20181009-3) unstable; urgency=medium
 
   * Fix path pattern for usrmerged paths in AppArmor profile.
diff --git a/debian/usr.bin.surf b/debian/usr.bin.surf
index f204a83..3a9b2d6 100644
--- a/debian/usr.bin.surf
+++ b/debian/usr.bin.surf
@@ -31,6 +31,7 @@
   /usr/lib/@{multiarch}/webkit2gtk-4.0/WebKit*Process ix,
   /{dev,run}/shm/WK2SharedMemory.* rw,
   /var/tmp/WebKit-Media-* rw,
+  /usr/share/publicsuffix/public_suffix_list.{dat,dafsa} r,
   owner @{HOME}/.local/share/webkitgtk/ w,
   owner @{HOME}/.local/share/webkitgtk/** rw,
   owner @{HOME}/.cache/webkitgtk/ w,
-- 
2.20.1

--- End Message ---
--- Begin Message ---
Source: surf
Source-Version: 2.0+git20181009-4

We believe that the bug you reported is fixed in the latest version of
surf, 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 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated surf 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: Sun, 27 Jan 2019 12:52:31 +0100
Source: surf
Architecture: source
Version: 2.0+git20181009-4
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 919534 919535 919536
Changes:
 surf (2.0+git20181009-4) unstable; urgency=medium
 .
   [ Leo Singer ]
   * AppArmor: allow 

  1   2   >