Bug#865797: marked as done (signond FTBFS: symbol changes)

[Debian Bug Tracking System]

Your message dated Mon, 07 May 2018 04:49:45 +
with message-id 
and subject line Bug#865797: fixed in signond 8.59-2
has caused the Debian Bug report #865797,
regarding signond FTBFS: symbol changes
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.)


-- 
865797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: signond
Version: 8.59-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes signond FTBFS:

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

...
   dh_makeshlibs -O-Bbuild/qt5 -O--parallel
dpkg-gensymbols: warning: debian/libsignon-qt5-1/DEBIAN/symbols doesn't match 
completely debian/libsignon-qt5-1.symbols
--- debian/libsignon-qt5-1.symbols (libsignon-qt5-1_8.59-1_amd64)
+++ dpkg-gensymbolsMvafsq   2018-07-26 21:09:03.368772123 -1200
@@ -56,8 +56,8 @@
  _ZN6SignOn12IdentityInfoD1Ev@Base 8.57+20150423
  _ZN6SignOn12IdentityInfoD2Ev@Base 8.57+20150423
  _ZN6SignOn12IdentityInfoaSERKS0_@Base 8.57+20150423
- (optional=inline)_ZN6SignOn5ErrorC1EiRK7QString@Base 8.57+20150423
- (optional=inline)_ZN6SignOn5ErrorC2EiRK7QString@Base 8.57+20150423
+#MISSING: 8.59-1# (optional=inline)_ZN6SignOn5ErrorC1EiRK7QString@Base 
8.57+20150423
+#MISSING: 8.59-1# (optional=inline)_ZN6SignOn5ErrorC2EiRK7QString@Base 
8.57+20150423
  _ZN6SignOn5ErrorD0Ev@Base 8.57+20150423
  _ZN6SignOn5ErrorD1Ev@Base 8.57+20150423
  _ZN6SignOn5ErrorD2Ev@Base 8.57+20150423
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libsignon-plugins-common1/DEBIAN/symbols 
doesn't match completely debian/libsignon-plugins-common1.symbols
--- debian/libsignon-plugins-common1.symbols 
(libsignon-plugins-common1_8.59-1_amd64)
+++ dpkg-gensymbolsVmmzQ3   2018-07-26 21:09:03.756772123 -1200
@@ -1,9 +1,9 @@
 libsignon-plugins-common.so.1 libsignon-plugins-common1 #MINVER#
  (optional=templinst|arch=mips64el 
mipsel)_Z17qRegisterMetaTypeI13QDBusArgumentEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS3_Xaasr12QMetaTypeId2IS3_E7DefinedntsrS8_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
  _Z23expandDBusArgumentValueRK8QVariantPb@Base 8.57+20150423
- 
(optional=templinst|arch=amd64)_Z27qRegisterNormalizedMetaTypeI13QDBusArgumentEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6CreateEPKv@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6DeleteEPv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst|arch=amd64)_Z27qRegisterNormalizedMetaTypeI13QDBusArgumentEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6CreateEPKv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6DeleteEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE8DestructEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE9ConstructEPvPKv@Base
 8.57+20150423
  (optional=templinst)_ZN4QMapI7QString8QVariantE13detach_helperEv@Base 
8.57+20150423
@@ -30,6 +30,8 @@
  
(optional=templinst)_ZN7QVectorI10QByteArrayE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptionEE@Base
 8.57+20150423
  (optional=templinst)_ZN7QVectorI10QByteArrayE6appendERKS0_@Base 8.57+20150423
  (optional=templinst)_ZN8QMapNodeI7QString8QVariantE14destroySubTreeEv@Base 
8.57+20150423
+ _ZN9QtPrivate16StreamStateSaverD1Ev@Base 8.59-1
+ _ZN9QtPrivate16StreamStateSaverD2Ev@Base 8.59-1
  _ZNK6SignOn13BlobIOHandler10metaObjectEv@Base 8.57+20150423
  
(optional=templinst)_ZNK8QMapNodeI7QString8QVariantE4copyEP8QMapDataIS0_S1_E@Base
 8.57+20150423
  _ZTVN6SignOn13BlobIOHandlerE@Base 8.57+20150423
@@ -37,16 +39,16 @@
  
(optional=templinst)_ZrsI7QString8QVariantER11QDataStreamS3_R4QMapIT_T0_E@Base 
8.57+20150423
 libsignon-plugins.so.1 libsignon-plugins-common1 #MINVER#
  

Bug#898060: linux-image-4.9.0-6-amd64: q

[yunchih]

Hi, maintainers:

I just rebooted the problematic NFS server, but
the problem soon appeared again!  In other words,
some NFS clients are hanging and server is filled
with the error message:

# dmesg | tail -2
[ 6180.718237] RPC request reserved 84 but used 272
[ 6180.732857] RPC request reserved 84 but used 272
# dmesg | grep RPC | wc -l
2519
# uname -a
Linux home 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1 (2018-04-29) x86_64 GNU/Linux

Please help!

Bug#895495: marked as done (libkf5eventviews FTBFS: symbol disappeared)

[Debian Bug Tracking System]

Your message dated Mon, 07 May 2018 03:34:54 +
with message-id 
and subject line Bug#895495: fixed in libkf5eventviews 4:17.12.3-2
has caused the Debian Bug report #895495,
regarding libkf5eventviews FTBFS: symbol disappeared
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.)


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

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

dh_makeshlibs '-Xusr/lib/libkdeinit5_*'  
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5eventviews5/DEBIAN/symbols doesn't match 
completely debian/libkf5eventviews5.symbols
--- debian/libkf5eventviews5.symbols (libkf5eventviews5_4:17.12.3-1_amd64)
+++ dpkg-gensymbolshYHHUq   2018-04-11 11:02:48.544501361 -1200
@@ -598,7 +598,7 @@
  _ZN10EventViews9MonthViewD0Ev@Base 4:17.12.2
  _ZN10EventViews9MonthViewD1Ev@Base 4:17.12.2
  _ZN10EventViews9MonthViewD2Ev@Base 4:17.12.2
- _ZN10QByteArray7reserveEi@Base 4:17.12.2
+#MISSING: 4:17.12.3-1# _ZN10QByteArray7reserveEi@Base 4:17.12.2
  
(optional=templinst)_ZN12KConfigGroup10writeEntryI10QByteArrayEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base
 4:17.12.2
  
(optional=templinst)_ZN12KConfigGroup10writeEntryIiEEvPKcRK5QListIT_E6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base
 4:17.12.2
  
(optional=templinst)_ZN12KConfigGroup10writeEntryIiEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base
 4:17.12.2
dh_makeshlibs: failing due to earlier errors
make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: 
pre_binary_dh_makeshlibs] Error 2


Why did kmime export a function from QByteArray?
--- End Message ---
--- Begin Message ---
Source: libkf5eventviews
Source-Version: 4:17.12.3-2

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated libkf5eventviews 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, 07 May 2018 05:11:30 +0200
Source: libkf5eventviews
Binary: libkf5eventviews-data libkf5eventviews-dev libkf5eventviews5
Architecture: source
Version: 4:17.12.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 libkf5eventviews-data - KDE PIM event handling - data files
 libkf5eventviews-dev - KDE PIM event handling - devel files
 libkf5eventviews5 - KDE PIM event handling - library
Closes: 895495
Changes:
 libkf5eventviews (4:17.12.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Update symbols files from logs of buildds. (Closes: #895495)
   * Bump Standards-Version to 4.1.4, no changes required.
   * Remove the unused files for autopkgtests.
   * Add Build-Depends-Package in symbols file.
   * Remove unused ${shlibs:Depends} substvar from libkf5eventviews-dev.
Checksums-Sha1:
 93fd8a90d6e02000e48fbbc84ca0e656db2be13e 3043 libkf5eventviews_17.12.3-2.dsc
 9b30a7dff083c25045e53f70dc5a3e1c61d660b9 15928 
libkf5eventviews_17.12.3-2.debian.tar.xz
 339c07e732ef93f58c6638c3852158489d0384ed 15603 
libkf5eventviews_17.12.3-2_source.buildinfo
Checksums-Sha256:
 836882c0c2861b3e842af1a8bc2bff5c3c538620b2295049059eaf945328ebe4 3043 
libkf5eventviews_17.12.3-2.dsc
 51a1a032826165a861f762b2f04dd2b81217ff6b506414710177b9bcebf98aea 15928 
libkf5eventviews_17.12.3-2.debian.tar.xz
 dc3fc93cc39a53176f702f48e935294ea0bbcbcf6798c80498f05ed3a15ea1f9 15603 
libkf5eventviews_17.12.3-2_source.buildinfo
Files:
 6cf4050fef7c9eb3dbb84963e0912545 3043 libs optional 
libkf5eventviews_17.12.3-2.dsc
 54c43f5087182e742aff5f94dbc21cd3 15928 libs optional 
libkf5eventviews_17.12.3-2.debian.tar.xz
 bb0a5ef40421dfd480ca663830111331 15603 libs optional 

Processed: tagging 897554

[Debian Bug Tracking System]

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

> tags 897554 + pending
Bug #897554 [src:maint-guide] maint-guide: FTBFS: dh_install: missing files, 
aborting
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: "this weekend"

[Debian Bug Tracking System]

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

> forwarded 897583 https://github.com/ivan-m/graphviz/issues/26
Bug #897583 [src:haskell-graphviz] haskell-graphviz: FTBFS: unsatisfiable 
build-dependency: libghc-fgl-dev (< 5.6) but 5.6.0.0-2 is to be installed
Set Bug forwarded-to-address to 'https://github.com/ivan-m/graphviz/issues/26'.
> quit
Stopping processing here.

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

Bug#897554: maint-guide: FTBFS: dh_install: missing files, aborting

[Boyuan Yang]

在 2018年5月7日星期一 CST 上午12:44:19，Osamu Aoki 写道：
> Hi Boyuan Yang,
> 
> On Wed, May 02, 2018 at 10:59:48PM +0200, Lucas Nussbaum wrote:
> > Source: maint-guide
> > Version: 1.2.40
> > Severity: serious
> > Tags: buster sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20180502 qa-ftbfs
> > Justification: FTBFS on amd64
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> > 
> > Relevant part (hopefully):
> > >  fakeroot debian/rules binary
> > > 
> > > dh  binary
> > > 
> > >dh_testroot
> > >dh_prep
> > >dh_auto_install
> > >dh_install
> > > 
> > > dh_install: Cannot find (any matches for) "tmp/maint-guide.zh-cn.pdf"
> > > (tried in ., debian/tmp)
> > > 
> > > dh_install: maint-guide-zh-cn missing files: tmp/maint-guide.zh-cn.pdf
> > > dh_install: Cannot find (any matches for) "tmp/maint-guide.zh-tw.pdf"
> > > (tried in ., debian/tmp)
> > > 
> > > dh_install: maint-guide-zh-tw missing files: tmp/maint-guide.zh-tw.pdf
> > > dh_install: missing files, aborting
> > > make: *** [debian/rules:35: binary] Error 25
> > 
> > The full build log is available from:
> >http://aws-logs.debian.net/2018/05/02/maint-guide_1.2.40_unstable.log
> > 
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> > 
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
> 
> Can you look into this problem?  Is this tool chain problem or missiong
> dependency package?
> 
> I thought you enabled zh-* build since tool chain is now ready...
> 
> Regards,
> 
> Osamu

I didn't touch maint-guide recently; I was previously fixing the build problem 
of debian-reference.

There were several mails regarding zh-* problem in maint-guide (written by 
others), mainly about backquote character (`). I didn't follow them but those 
mails seem to have pointed out the cause of the build failure. Will dig into 
it later.

--
Regards,
Boyuan Yang

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

Bug#898088: arc4random_buf() may block for a long time

[Ben Hutchings]

On Mon, 2018-05-07 at 01:04 +0100, Ben Hutchings wrote:
[...]
> But the fix for this means that getrandom() and arc4random_buf() may
> block until a minute or even longer after boot.  Since
> gnome-session-binary calls arc4random_buf() via
> IceGenerateMagicCookie(), fixing the kernel causes a "blank screen"
> regression for some systems.
[...]

See bug #897632 for an example.

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
  - John Lennon


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

Bug#898088: arc4random_buf() may block for a long time

[Ben Hutchings]

Source: libbsd
Version: 0.8.7-1
Severity: serious
Tags: upstream

The manual page for arc4random_buf() says "High quality 32-bit
pseudo-random numbers are generated very quickly."  This promise is
false, and it can never be true in general!

On recent Linux kernel versions arc4random_buf() uses the getrandom()
system call where available.  getrandom() is documented to block
(or return an error, depending on the flags parameter) when
the kernel's RNG does not have enough entropy available.  It was
recently found that the RNG was unblocking getrandom() too early
(CVE-2018-1108).

But the fix for this means that getrandom() and arc4random_buf() may
block until a minute or even longer after boot.  Since
gnome-session-binary calls arc4random_buf() via
IceGenerateMagicCookie(), fixing the kernel causes a "blank screen"
regression for some systems.

I don't know quite how we're going to solve this, but at the very
least the manual page for arc4random_buf() must clarify whether it
is intended to provide high quality, or non-blocking, behaviour.

Ben.

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

Kernel: Linux 4.16.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#898080: marked as done (mpv: Segfault on any file)

[Debian Bug Tracking System]

Your message dated Sun, 06 May 2018 22:35:16 +
with message-id 
and subject line Bug#898080: fixed in mpv 0.28.2-1
has caused the Debian Bug report #898080,
regarding mpv: Segfault on any 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.)


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

Dear Maintainer,

Upon upgrading to mpv 0.28, mpv segfaults on any file I open. After downgrading 
to 0.27, this was no longer an issue. I can provide strace output if desired.

Sincerely,

Chiraag

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

Kernel: Linux 4.16.5-chiraag (SMP w/8 CPU cores; PREEMPT)
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 mpv depends on:
ii  libarchive13  3.2.2-3.1
ii  libasound21.1.6-1
ii  libass9   1:0.14.0-1
ii  libavcodec58  7:4.0-1+b1
ii  libavdevice58 7:4.0-1+b1
ii  libavfilter7  7:4.0-1+b1
ii  libavformat58 7:4.0-1+b1
ii  libavutil56   7:4.0-1+b1
ii  libc6 2.27-3
ii  libcaca0  0.99.beta19-2+b3
ii  libcdio-cdda2 10.2+0.94+2-2+b1
ii  libcdio-paranoia2 10.2+0.94+2-2+b1
ii  libcdio17 1.0.0-2+b1
ii  libdrm2   2.4.91-2
ii  libdvdnav46.0.0-1
ii  libdvdread4   6.0.0-1
ii  libegl1   1.0.0+git20180308-2
ii  libgbm1   18.0.2-2
ii  libgl11.0.0+git20180308-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  liblcms2-22.9-1
ii  liblua5.2-0   5.2.4-1.1+b2
ii  libpulse0 11.1-5
ii  librubberband21.8.1-7
ii  libsdl2-2.0-0 2.0.8+dfsg1-1
ii  libsmbclient  2:4.8.1+dfsg-1
ii  libsndio6.1   1.1.0-3
ii  libswresample37:4.0-1+b1
ii  libswscale5   7:4.0-1+b1
ii  libuchardet0  0.0.6-2
ii  libva-drm22.1.0-3
ii  libva-x11-2   2.1.0-3
ii  libva22.1.0-3
ii  libvdpau1 1.1.1-8
ii  libvulkan11.1.73+dfsg-1
ii  libx11-6  2:1.6.5-1
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.3-1+b3
ii  libxrandr22:1.5.1-1
ii  libxss1   1:1.2.2-1+b2
ii  libxv12:1.0.11-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages mpv recommends:
ii  xdg-utils   1.1.2-2
ii  youtube-dl  2018.04.25-1

mpv suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mpv
Source-Version: 0.28.2-1

We believe that the bug you reported is fixed in the latest version of
mpv, 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.
James Cowgill  (supplier of updated mpv 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, 06 May 2018 23:20:25 +0100
Source: mpv
Binary: mpv libmpv1 libmpv-dev
Architecture: source
Version: 0.28.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 libmpv-dev - video player based 

Bug#890410: marked as done (mpv: fix for CVE-2018-6360 overlooks subtitles)

[Debian Bug Tracking System]

Your message dated Sun, 06 May 2018 22:35:16 +
with message-id 
and subject line Bug#890410: fixed in mpv 0.28.2-1
has caused the Debian Bug report #890410,
regarding mpv: fix for CVE-2018-6360 overlooks subtitles
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.)


-- 
890410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mpv
Version: 0.23.0-1
Severity: grave
Tags: security upstream

Yet another bug relating to the fix for CVE-2018-6360...

This time the bug is not a regression, but a mistake upstream made when
writing the original patch. Upstream overlooked the handling of subtitle
URLs which were not protected.

Upstream has released 0.27.2 and 0.28.2 to fix these. I think the bug
affects 0.23 as well (but I have not yet checked).

Possibly this warrants a new CVE number.

Upstream commit:
https://github.com/mpv-player/mpv/commit/3e71eb8676de53a05f51b987d294e7d2fa0a5bc1

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mpv
Source-Version: 0.28.2-1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated mpv 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, 06 May 2018 23:20:25 +0100
Source: mpv
Binary: mpv libmpv1 libmpv-dev
Architecture: source
Version: 0.28.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 libmpv-dev - video player based on MPlayer/mplayer2 (client library dev files)
 libmpv1- video player based on MPlayer/mplayer2 (client library)
 mpv- video player based on MPlayer/mplayer2
Closes: 890410 898080
Changes:
 mpv (0.28.2-1) experimental; urgency=medium
 .
   * New upstream bugfix release.
 - Also whitelist subtitle URLs in youtube-dl hook. (Closes: #890410)
 .
   * debian/rules:
 - Build-Depend on ffmpeg 4.0. (Closes: #898080)
   * debian/patches:
 - Drop patch for CVE-2018-6360 - fixed upstream.
 - Fix typo in 06_ffmpeg-abi.patch description.
Checksums-Sha1:
 4e4c110e40faff869cd8d937ed4ffb36cbd40da2 2851 mpv_0.28.2-1.dsc
 2dfc6a68ee5d99ff510e417d60ff939ddf9ec08f 2982558 mpv_0.28.2.orig.tar.gz
 c8bfcda069e64b63ec10c437e2c228afcb433900 104364 mpv_0.28.2-1.debian.tar.xz
 d6c41695b9f0bb7149bdab47a605b7393f26c6bd 8520 mpv_0.28.2-1_source.buildinfo
Checksums-Sha256:
 79df9099b6fb2f7e5cd2fd7eca03f683c28442bb6adb714c831f8c2c5526 2851 
mpv_0.28.2-1.dsc
 aada14e025317b5b3e8e58ffaf7902e8b6e4ec347a93d25a7c10d3579426d795 2982558 
mpv_0.28.2.orig.tar.gz
 9ea30ec54aa40deb4647d2e51c683120a0255bef0cd280eca1269d6034317b44 104364 
mpv_0.28.2-1.debian.tar.xz
 c48e8c7e9f051e4e2faa35c7a5fd89b09067a3435deb3b66edfec51165af8a78 8520 
mpv_0.28.2-1_source.buildinfo
Files:
 0e97c47b82f649dfea1b420ecf392af1 2851 video optional mpv_0.28.2-1.dsc
 b6538dec29a2a69574f4e3a3d688fb8b 2982558 video optional mpv_0.28.2.orig.tar.gz
 c9f681d927167362d21722584f24eba4 104364 video optional 
mpv_0.28.2-1.debian.tar.xz
 6ddd9a1cd858a25ae1fe9e51132e4cf2 8520 video optional 
mpv_0.28.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAlrvgQcUHGpjb3dnaWxs
QGRlYmlhbi5vcmcACgkQx/FnbeotAe9RwxAAk/NiIMGXWnBvw91YGcIaiWQIwped
xrXJXJte7vPj1m+LI7bPRUh6EIFMB5qDGpHsyRdvqqO+y/T6/PhNl99/HYPNtiDP
uMx0FBxaCSOabwRDUO9s2hUJmxo2uRyWDigFJAvjFpK1N28AZMbKDRM1ICOJfHtX
tEVWPnM09wy4EiLT0dlLfMqqAI6ynqhYSOw/xnG+dBXNdIseoTPlQTj9bm12duQ+
K84z/Swrdje7G4FwKo/UglSGm4QMWRoTYY4nxLTMQD/YeGCVFnKKXjGbPjmW/aTq
DmgkDbzCqgc+U77+utpCw4IfM75KEWJZVpb69U0Z17IFA/UGcYhUxi9vNoi2STfy
AaJZHhyiS7W96XG5ls0e9mJN2TScO/QcGili3gTbDKDkbN9fNLjm+0QHqf9KS9sr
dGhHIZbOuaGvxl3i1xPcOwTZTYzBr6KOHClNVHMYGmIcoJGmuKXwbAmlG0SZKnuz
DtUzJ+0LPD2rX9OF+zDtI5LXOQCe9Bb1QT2ORUowJ7a7U+RkliOJCcaI6LGfuycK

Bug#898086: libequinox-osgi-java: Does not install symlinks into /usr/lib/eclipse/plugins

[Nick Morrott]

Source: libequinox-osgi-java
Version: 3.9.1-1
Severity: grave
Justification: renders package unusable
Control: affects eclipse

Dear Maintainer,

The separation of the libequinox-osgi-java binary package from the eclipse
source appears to break fresh installations of eclipse.

On a fresh installation of eclipse on buster/sid (using a supported JDK
version), it is apparent that eclipse is unable to locate
/usr/lib/eclipse/plugins/org.eclipse.osgi_3.8.1.dist.jar (configured in
/usr/lib/eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info).

On stretch (3.8.1-10), the relevant symlinks between
/usr/lib/eclipse/plugins and
/usr/share/java are present.

On buster/sid, no symlink is created to /usr/lib/eclipse/plugins,
which causes eclipse to immediately crash.

Manually installing the following symlink resolves the issue:

cd /usr/lib/eclipse/plugins
ln -s ../../../share/java/org.eclipse.osgi-3.9.1.jar
org.eclipse.osgi_3.8.1.dist.jar



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

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

Processed: Bug #898080 in mpv marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #898080 [mpv] mpv: Segfault on any file
Added tag(s) pending.

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

Bug#898080: Bug #898080 in mpv marked as pending

[jcowgill]

Control: tag -1 pending

Hello,

Bug #898080 in mpv reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/mpv/commit/5800733948408fc34d24f4704928bbd537c1eb2b


Build-depend on ffmpeg 4.0

Closes: #898080



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/898080

Processed: Bug#898080: mpv: Segfault on any file

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #898080 [mpv] mpv: Segfault on any file
Severity set to 'grave' from 'important'

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

Bug#892539: pdftk: Depends on GCJ which is going away

[Emilio Pozuelo Monfort]

On Mon, 2 Apr 2018 19:12:01 +0200 Emilio Pozuelo Monfort  
wrote:
> On Wed, 21 Mar 2018 15:12:30 +0100 Petter Reinholdtsen  
> wrote:
> > I use pdftk regularly, and really hope we can manage to keep it in
> > Debian.
> > 
> > Is there a plan for adressing this before gcj is removed?
> 
> There's a fork that doesn't require GCJ as Adrian pointed out, you could help
> package that.

I did some work on this, there's a source and deb package prepared in

  https://people.debian.org/~pochu/pdftk/

This is based on upstream commit 121337af4464f3cb6b9acb3b2095d43d1453e05b.

Once installed, you can run pdftk as:

  java -jar /usr/share/pdftk/pdftk.jar

A wrapper script could be created and put into /usr/bin, or perhaps
there's a better way. I'm not very familiar with Java packages.

There's a problem though. If you run a more complex command it will
fail to find the dependencies. It's probably missing CLASSPATH, or
perhaps a dependency in the jar manifest file. Again, I'm not
familiar with this to know how to fix it:

  $ java -jar /usr/share/pdftk/pdftk.jar mypdf.pdf burst
  Unhandled Java Exception in create_output():
  java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringEscapeUtils
at report.OutputXmlString(Unknown Source)
at report.OutputPdfName(Unknown Source)
at report.ReportInfo(Unknown Source)
at report.ReportOnPdf(Unknown Source)
at TK_Session.create_output(Unknown Source)
at pdftk.main(Unknown Source)
  Caused by: java.lang.ClassNotFoundException: 
org.apache.commons.lang3.StringEscapeUtils
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
... 6 more

Feel free to take this here, I won't do any more work on this package.
I will be removing pdftk from testing soon though, in order to finish
this GCJ removal transition. So if you or anyone cares about this
package, you may want to get it into shape and test this port and
upload it.

Cheers,
Emilio

Bug#897546: marked as done (nbdkit: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Sun, 06 May 2018 20:58:03 +
with message-id 
and subject line Bug#897546: fixed in nbdkit 1.2.2-2
has caused the Debian Bug report #897546,
regarding nbdkit: FTBFS: dh_install: missing files, aborting
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.)


-- 
897546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nbdkit
Version: 1.2.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install -X.la --fail-missing
> dh_install: Please use dh_missing --list-missing/--fail-missing instead
> dh_install: This feature will be removed in compat 12.
> dh_install: Cannot find (any matches for) 
> "/usr/lib/*-*/nbdkit/plugins/nbdkit-ruby-plugin.so" (tried in ., debian/tmp)
> 
> dh_install: nbdkit-plugin-ruby missing files: 
> /usr/lib/*-*/nbdkit/plugins/nbdkit-ruby-plugin.so
> dh_install: Cannot find (any matches for) 
> "/usr/share/man/man3/nbdkit-ruby-plugin.3" (tried in ., debian/tmp)
> 
> dh_install: nbdkit-plugin-ruby missing files: 
> /usr/share/man/man3/nbdkit-ruby-plugin.3
> dh_install: missing files, aborting
> make[1]: *** [debian/rules:30: override_dh_install] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/nbdkit_1.2.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: nbdkit
Source-Version: 1.2.2-2

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated nbdkit 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, 06 May 2018 22:05:26 +0200
Source: nbdkit
Binary: nbdkit nbdkit-plugin-dev nbdkit-plugin-perl nbdkit-plugin-python 
nbdkit-plugin-libvirt nbdkit-plugin-guestfs nbdkit-plugin-ruby
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description:
 nbdkit - toolkit for creating NBD servers
 nbdkit-plugin-dev - development files for nbdkit
 nbdkit-plugin-guestfs - libguestfs plugin for nbdkit
 nbdkit-plugin-libvirt - libvirt plugin for nbdkit
 nbdkit-plugin-perl - Perl plugin for nbdkit
 nbdkit-plugin-python - Python plugin for nbdkit
 nbdkit-plugin-ruby - Ruby plugin for nbdkit
Closes: 897546
Changes:
 nbdkit (1.2.2-2) unstable; urgency=medium
 .
   * Add ruby build-dependency (Closes: #897546)
Checksums-Sha1:
 2bf03e1201b9f5b78e7382c68b94beb30bbf682e 2753 nbdkit_1.2.2-2.dsc
 f46ae2925b337492a9170447b3b78480984ec0ad 4824 nbdkit_1.2.2-2.debian.tar.xz
 52ded65b2d82de3ccd18fe6e1e778d81f9a3f815 16923 nbdkit_1.2.2-2_source.buildinfo
Checksums-Sha256:
 eb4cc0f0c5ee5fda8d2062d84f52a906f1e1ad5e81568e1bbe7e308c34031eca 2753 
nbdkit_1.2.2-2.dsc
 89a19651b4947e167df852846e6efe91d4f348a39f0d6d50cf8e45e92c19bded 4824 
nbdkit_1.2.2-2.debian.tar.xz
 37c23108bc21f8e716c8e35387fda3c90816129b4412999b9fc1fe781715db2a 16923 
nbdkit_1.2.2-2_source.buildinfo
Files:
 7444895899334a48a632cd2f4e474d16 2753 admin optional nbdkit_1.2.2-2.dsc
 0bfa14e7969cc0805e364745aec2dc26 4824 admin optional 
nbdkit_1.2.2-2.debian.tar.xz
 665491498b4ebe8689e3cacf33e2e417 16923 admin optional 
nbdkit_1.2.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlrvYDwACgkQdbcQY1wh

Bug#897114: marked as done (ifrit FTBFS with cmake 3.11.1)

[Debian Bug Tracking System]

Your message dated Sun, 06 May 2018 20:55:12 +
with message-id 
and subject line Bug#897114: fixed in ifrit 4.1.2-6
has caused the Debian Bug report #897114,
regarding ifrit FTBFS with cmake 3.11.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.)


-- 
897114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ifrit
Version: 4.1.2-5
Severity: serious
Tags: buster sid

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

...
 fakeroot debian/rules binary
dh binary --buildsystem=cmake --sourcedirectory=build
   dh_update_autotools_config -O--buildsystem=cmake -O--sourcedirectory=build
   dh_auto_configure -O--buildsystem=cmake -O--sourcedirectory=build
cd obj-x86_64-linux-gnu && cmake ../build -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-- The C compiler identification is GNU 7.3.0
-- The CXX compiler identification is GNU 7.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- The imported target "vtkRenderingPythonTkWidgets" references the file
   "/usr/lib/x86_64-linux-gnu/libvtkRenderingPythonTkWidgets.so"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/cmake/vtk-6.3/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtk" references the file
   "/usr/bin/vtk"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/cmake/vtk-6.3/VTKTargets.cmake"
but not all the files it references.

CMake Error at /usr/share/cmake-3.11/Modules/FindQt.cmake:166 (message):
  Multiple versions of Qt found please set DESIRED_QT_VERSION
Call Stack (most recent call first):
  CMakeLists.txt:174 (INCLUDE)


-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version 
"2.7.15rc1") 
CMake Error: Error required internal CMake variable not set, cmake may not be 
built correctly.
Missing variable is:
QT_MOC_EXECUTABLE
-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: ifrit
Source-Version: 4.1.2-6

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated ifrit 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, 06 May 2018 22:10:35 +0200
Source: ifrit
Binary: ifrit
Architecture: source
Version: 4.1.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 ifrit  - powerful tool for visualizing 3-dimensional data sets
Closes: 897114
Changes:
 ifrit (4.1.2-6) unstable; urgency=medium
 .
   [ Adam Borowski ]
   * QA upload.
   * R³.
   * Move the VCS to Salsa.
   * Don't handle noopt and nostrip, already done by dpkg-buildflags.
 .
   [ Peter Michael Green ]
   * Set DESIRED_QT_VERSION to 4 through a new override_dh_auto_configure target
 + Note: the package has a target called 

Bug#897095: marked as done (bagel FTBFS: cannot find -lmpi)

[Debian Bug Tracking System]

Your message dated Sun, 06 May 2018 20:49:55 +
with message-id 
and subject line Bug#897095: fixed in bagel 1.1.1-1
has caused the Debian Bug report #897095,
regarding bagel FTBFS: cannot find -lmpi
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.)


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

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

...
dh_auto_configure --\
--datadir=/usr/share/bagel  \
--libdir=/usr/lib/bagel \
--enable-static \
--disable-shared\
--with-boost\
--with-libxc=yes\
--with-mpi=openmpi  \
--disable-scalapack \
--enable-smith
...
configure: error: in `/build/1st/bagel-1.1.0':
configure: error: C compiler cannot create executables
...
configure:3525: checking whether the C compiler works
configure:3547: gcc -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c 
-lblas -llapack -lpthread -lmpi >&5
/usr/bin/x86_64-linux-gnu-ld: cannot find -lmpi
collect2: error: ld returned 1 exit status



Seems to be related to the recent MPI changes.

My first question would be whether --with-mpi=openmpi is correct
when the build dependency is on libmpich-dev.
--- End Message ---
--- Begin Message ---
Source: bagel
Source-Version: 1.1.1-1

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated bagel 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, 06 May 2018 22:26:51 +0200
Source: bagel
Binary: bagel
Architecture: source
Version: 1.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Description:
 bagel  - Computational Chemistry Package
Closes: 897095
Changes:
 bagel (1.1.1-1) unstable; urgency=medium
 .
   * New upstream point release.
   * debian/patches/add_missing_includes.patch: New patch.
   * debian/rules (LIBS): Removed -lmpi (Closes: 897095).
Checksums-Sha1:
 667dffab577f9da41da2e3c0b6ed9745b3ecf8b8 2062 bagel_1.1.1-1.dsc
 8bca6e0f0bafbb16d0a554250f587c4c88e10ada 41468601 bagel_1.1.1.orig.tar.gz
 8e3918c469476fa681f22ef856405588834d68b8 5764 bagel_1.1.1-1.debian.tar.xz
 553f3784c17b3a0de52c9c826c66163084cf0933 8030 bagel_1.1.1-1_source.buildinfo
Checksums-Sha256:
 fc914b40c19f92970f45f99ed0ed62a44d97165607970b620b6b322fab51f58a 2062 
bagel_1.1.1-1.dsc
 60d46496c25d18698acf67f39ca7150d0c6daf49944a8e47cf0c10a0e31d245f 41468601 
bagel_1.1.1.orig.tar.gz
 2cfb7399fafb9ef7cade2b104daee73aed79b7c927d3b3db4c98724994d2 5764 
bagel_1.1.1-1.debian.tar.xz
 6be76add5f1a96194b144bc2f862bab0826d5783f3f4d1e7a4febc86ec59c969 8030 
bagel_1.1.1-1_source.buildinfo
Files:
 60b150bc01aaae8d37d86e077bcb73a8 2062 science optional bagel_1.1.1-1.dsc
 1f535cf7eda690d5b3aee7012e515daf 41468601 science optional 
bagel_1.1.1.orig.tar.gz
 5541cbf5c68247b70e046a7f2c25d5e6 5764 science optional 
bagel_1.1.1-1.debian.tar.xz
 6a3c0450847eef5c477ca541c0da164f 8030 science optional 
bagel_1.1.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAlrvZSMACgkQ3GhqJ7Q0
gbDmzQ//Zmq8xAja55mV+rdvCsJkS6/lollBVkrfIVce4dW54yoTobi3L6xlhv8f
TWxbI2T3pL3ekR2Lsiqv6bSHm+1HA/T7jMBv0P42uQ17nv61KNJd6JOjomhxDDDU
4xcUalwIYLaLrHMR6MB7mQo1vdEt/C45uiR/dyZ1V5pdTT9WvGE19gJUau+wvZzL
Yo5k/KoHzbmyHsNM7MNfEGTHqqIAfbUeXwFBdTsbrxQw49BswyadW/2Ubrp6GV8J
vqTPB9748VhekLbbJNGk9fZZl7giJJ4Q1m6CkpzW6Y/FBO4360xYwYRWJOXcQECF
B6qBacU/Aj/67Etf9oaD2BDzakkYs3VnVx7r+ryRtJ2HXk0X7UgerLZKh2iEmAg2
S4TSFTozxMIou7rrR5uPr0kOr+Ur/v0HCIyDKEsPUIOJ93IrwmNp0bc62csVGG9u

Processed: tagging 894736

[Debian Bug Tracking System]

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

> tags 894736 + upstream fixed-upstream
Bug #894736 {Done: Andrea Capriotti } [vim-syntastic] 
Checker config files allow arbitrary code execution scenarios
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: bug 894736 is forwarded to https://github.com/vim-syntastic/syntastic/issues/2170

[Debian Bug Tracking System]

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

> forwarded 894736 https://github.com/vim-syntastic/syntastic/issues/2170
Bug #894736 {Done: Andrea Capriotti } [vim-syntastic] 
Checker config files allow arbitrary code execution scenarios
Set Bug forwarded-to-address to 
'https://github.com/vim-syntastic/syntastic/issues/2170'.
> thanks
Stopping processing here.

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

Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

[Sven Joachim]

On 2018-05-02 22:54 +0200, Lucas Nussbaum wrote:

> Source: tudu
> Version: 0.10.2-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20180502 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
>> make[1]: Entering directory '/<>'
>> rm -f configure Makefile */Makefile
>> acr
>> acr: ./configure script created successfully.
>> acr: all done.
>> dh_auto_configure
>>  ./configure --build=x86_64-linux-gnu --prefix=/usr
>> --includedir=\${prefix}/include --mandir=\${prefix}/share/man
>> --infodir=\${prefix}/share/info --sysconfdir=/etc
>> --localstatedir=/var --disable-silent-rules
>> --libdir=\${prefix}/lib/x86_64-linux-gnu
>> --libexecdir=\${prefix}/lib/x86_64-linux-gnu
>> --disable-maintainer-mode --disable-dependency-tracking
>> checking for cpp... ERROR:  cannot parse sources

It seems to me this is a bug in acr 1.6.1-1.  The configure script
generated by it is clearly broken, and the same tudu version built
successfully with acr 1.2-1 back in June 2017.  Maybe the acr
maintainer can find out what went wrong here.

>> WARNING: Unknown flag '--disable-silent-rules'.
>> 
>> 
>> WARNING: Unknown flag '--disable-maintainer-mode'.
>> 
>> 
>> WARNING: Unknown flag '--disable-dependency-tracking'.
>> 
>> checking build system type... x86_64-linux-gnu
>> checking host system type... x86_64-unknown-linux-gnu
>> checking target system type... x86_64-unknown-linux-gnu
>> checking for working directories... current
>> using prefix '/usr'
>> checking for c++ compiler... g++
>> checking for xcurses.h... no
>> checking for ncursesw/curses.h... yes
>> checking for ncurses/curses.h... no
>> checking for ncurses.h... yes
>> checking for curses.h... yes
>> checking for libncursesw ... yes
>> checking for libncurses ... yes
>> checking for libcurses ... yes
>> checking for WIDEC_CURSES... ./configure: 394: ./configure: 
>> echo#define_XOPEN_SOURCE_EXTENDED: not found
>> ./configure: 394: ./configure: echo#include: not found
>> ./configure: 394: ./configure: echointmain(){addwstr(L"");}: not found
>> ./configure: 394: ./configure: cannot create /dev/null2: Permission denied
>> ./configure: 394: ./configure: eval$CXX-g: not found
>> ./configure: 394: ./configure: rmtest.c: not found
>> no
>> 
>> ERROR: There is no wide character support on curses!
>> 
>> dh_auto_configure: ./configure --build=x86_64-linux-gnu
>> --prefix=/usr --includedir=\${prefix}/include
>> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
>> --sysconfdir=/etc --localstatedir=/var --disable-silent-rules
>> --libdir=\${prefix}/lib/x86_64-linux-gnu
>> --libexecdir=\${prefix}/lib/x86_64-linux-gnu
>> --disable-maintainer-mode --disable-dependency-tracking returned
>> exit code 1
>> make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 2

Cheers,
   Sven

Bug#894797: marked as done (node-foreground-child: FTBFS)

[Debian Bug Tracking System]

Your message dated Sun, 06 May 2018 19:35:36 +
with message-id 
and subject line Bug#894797: fixed in node-foreground-child 1.5.6-5
has caused the Debian Bug report #894797,
regarding node-foreground-child: FTBFS
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.)


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

Source: node-foreground-child
Version: 1.5.6-4
Severity: serious

Some recent change in unstable makes node-foreground-child FTBFS:

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

  ...
# Subtest: test/immortal-child.js
not ok 1 - should match pattern provided
  ---
  found:
out: ''
err: ''
code: null
signal: SIGINT
  pattern:
out: >-
  /^(child alive\n)*child SIGINT received\n(child 
alive\n)*child exit null

  SIGTERM\n$/
err: /^parent \d+\nchild \d+\n$/
code: null
signal: SIGTERM
  at:
line: 37
column: 7
file: test/immortal-child.js
type: ChildProcess
  stack: |
ChildProcess. (test/immortal-child.js:37:7)
  source: |
t.match(actual, expect)
  ...
1..1
# failed 1 test
# time=224.905ms
--- End Message ---
--- Begin Message ---
Source: node-foreground-child
Source-Version: 1.5.6-5

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated node-foreground-child 
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, 06 May 2018 21:12:32 +0200
Source: node-foreground-child
Binary: node-foreground-child
Architecture: source
Version: 1.5.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bastien Roucariès 
Description:
 node-foreground-child - helper running a child process as a foreground process
Closes: 894797
Changes:
 node-foreground-child (1.5.6-5) unstable; urgency=medium
 .
   * Increase timeout to 300s
 thanks to Graham Inggs (Closes: #894797).
   * Bump compat and policy (no changes)
Checksums-Sha1:
 71f2149fa4dacd06f4fde29f1d60c680c343f04d 2207 node-foreground-child_1.5.6-5.dsc
 939dcc2674713e8a95c9bf882cb7b4bccfab01e1 3524 
node-foreground-child_1.5.6-5.debian.tar.xz
 6d89f58b05b4c3aacf88ab493d69f0574870abe4 7414 
node-foreground-child_1.5.6-5_source.buildinfo
Checksums-Sha256:
 f1f13c2df51ed4b08566eaec6b3e88255f0404ce0d5f98947e229a6ac4c60130 2207 
node-foreground-child_1.5.6-5.dsc
 f08309cfadb81d81d2be05428f8f67dd93825115bcb4e568836998d1d5094b99 3524 
node-foreground-child_1.5.6-5.debian.tar.xz
 b66a5171daf6366add95429321fba2913a24eb3b6aaf37415004fc7f44f4faf2 7414 
node-foreground-child_1.5.6-5_source.buildinfo
Files:
 6f2ae98b6ada48b1f45220798040ab55 2207 web optional 
node-foreground-child_1.5.6-5.dsc
 de27fd0e160480723ecc7c297446d816 3524 web optional 
node-foreground-child_1.5.6-5.debian.tar.xz
 b43803963795bc430cd0526f8c9d9051 7414 web optional 
node-foreground-child_1.5.6-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAlrvVWEACgkQADoaLapB
CF8NEhAArFbkF7NspUh+sVIpkJRghWVyoIeHl1Kvq0yLBLNervKQtXRM/dhb1eiO
Kl5M7g65inO02/ygVuJoQBfvfahmwWGlFv6NANPr8UfnrTWiRW44ihZorJ2aFNRa
YQRqPy5ZMXez+QwXDY6S0jF2SaX0dbI9xi/zg8Xy3OhKp1akMXnrSMXMnGQBPehU
silQaiBlKdre1+X9ScCUI7ZyMd6AO9GgJFo+IUmmplYrejRjhDAm/oTTQwjRkJA3
yCcQ1CD8IWrVOF3x/PKJqAqlO85P41aVi7EEo68Ac7WW7O2bs48EtuZ0OuWiMsa2
nOPZoEP17etfKT8bl8QOtvvneTHQpVPulfocwt1nbSj8YdNLsTclPdbIboOT1I4X
feVmeI5NiI3E076SD84FruTJEUwKtJ1VPvobooFjfUWB7LhR2lE4kMXqFvRbMLyb
MGCL6soS+Ibnvun0+Lp7sbIlTI50eR+JqphwtlY+uYm013o7FdY8xG0WK+0rPa1S
3HQCUYboDPh+xxX5fsQI6e9AchYT63SlzXXxxtGFbpDzK1MnMcHjHzQSBmEuwgrA

Bug#896305: marked as done (python-laditools: laditools fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 06 May 2018 19:34:37 +
with message-id 
and subject line Bug#896305: fixed in laditools 1.1.0-3
has caused the Debian Bug report #896305,
regarding python-laditools: laditools fails to 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.)


-- 
896305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-laditools
Version: 1.1.0-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-laditools importing the module laditools
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/laditools/__init__.py", line 25, in 

from .config import LadiConfiguration
  File "/usr/lib/python2.7/dist-packages/laditools/config.py", line 22, in 

from xdg import BaseDirectory as basedir
ImportError: No module named xdg

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: laditools
Source-Version: 1.1.0-3

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

Debian distribution maintenance software
pp.
Ross Gammon  (supplier of updated laditools 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, 06 May 2018 20:28:15 +0200
Source: laditools
Binary: laditools python-laditools
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Ross Gammon 
Description:
 laditools  - Linux Audio Desktop Integration Tools
 python-laditools - Python module to control and monitor the LADI system
Closes: 896305
Changes:
 laditools (1.1.0-3) unstable; urgency=medium
 .
   [ Ross Gammon ]
   * Patches forwarded upstream
   * Add python-xdg dependency (Closes: #896305)
   * Fix "fail to build twice" by more aggressive cleaning
   * Use Debian email address
   * Add lintian override for missing-build-dependency-for-dh-addon
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
Checksums-Sha1:
 dfc32b521994b77d310e78cc6a8811a92557a484 2084 laditools_1.1.0-3.dsc
 33a3f416de7f0c0815b5beaed65851267a03fd6a 6008 laditools_1.1.0-3.debian.tar.xz
 43b5359650106f6893cb83429b189dfe3279b62a 11246 
laditools_1.1.0-3_amd64.buildinfo
Checksums-Sha256:
 ff644f92f49718323f847073a1a64ef9d3660c7897d3442a33925bb55376d798 2084 
laditools_1.1.0-3.dsc
 b00616d69df99f3a4311b130b8b9b221276cac91883e60d3a12638daa5780c9c 6008 
laditools_1.1.0-3.debian.tar.xz
 e14b3977dc20b392534bceba735a0fdc5e2d09f1d3761376cf46c87468ec6f99 11246 
laditools_1.1.0-3_amd64.buildinfo
Files:
 6b2b2a983774bd243d2ea48de33784ae 2084 sound optional laditools_1.1.0-3.dsc
 f61d9cb3dc09444baf938eca448628c5 6008 sound optional 
laditools_1.1.0-3.debian.tar.xz
 27385618897f147f6b8c23b125ea8bb8 11246 sound optional 
laditools_1.1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJa71MGAAoJEHM+a/k86PbZwekQAKLpDAZHVWnRLoyo6B6KIID8
EmLoalIc1s75XINqTnrfg6cV7Zyp/Zrn7j/ac52suLdrVyUxc2B3uNLZX1y0AST4
/bvzYLFSmZqqLWcBGtkteSOn+7cjYiorMSuX4TXIOFBwZeyyjjIzJDFv57oGPzf8
zQ2yKEdD8jG6Uql/zfxQ5nROAKG2ybB7evWoBLUUMa+ZNa7i7Aj0Ucqvz3/geT5S
4bh1uNHsWzS1IVrA16xeCjMA7wHC/Np5IHG8T5cpxAhvh3NuT4Letgmbiul1+Y90
SuLiKkFBYyG6eTJpQW0EDdHNZ48RuH6RVHXk6YBmLbhYqWMxsyqd8pCvglCxXfq+

Bug#891928: marked as done (CVE-2018-1048: ALLOW_ENCODED_SLASH option not taken into account in the AjpRequestParser)

[Debian Bug Tracking System]

Your message dated Sun, 6 May 2018 21:38:09 +0200
with message-id <91171867-7d8b-c53d-14c9-223822ec9...@debian.org>
and subject line Re: CVE-2018-1048: ALLOW_ENCODED_SLASH option not taken into 
account in the AjpRequestParser
has caused the Debian Bug report #891928,
regarding CVE-2018-1048: ALLOW_ENCODED_SLASH option not taken into account in 
the AjpRequestParser
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.)


-- 
891928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: undertow
Version: 1.4.8-1+deb9u1
Severity: grave
Tags: security
Forwarded: https://issues.jboss.org/browse/UNDERTOW-1245

It was found that the AJP connector in undertow, as shipped in Jboss
EAP 7.1.0.GA, does not use the ALLOW_ENCODED_SLASH option and thus
allow the the slash / anti-slash characters encoded in the url which
may lead to path traversal and result in the information disclosure of
arbitrary local files.

Upstream bug:

https://issues.jboss.org/browse/UNDERTOW-1245

This was apparently fixed in 1.4.22.
--- End Message ---
--- Begin Message ---
I am going to close this bug report because CVE-2018-1048 will not be
fixed in Stretch. As discussed with the security team the package will
be removed instead.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885880 [deluge-gtk] deluge: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Bug#892741: llvmlite: FTBFS on mips64el - testsuite segfaults

[Daniel Stender]

On 05/06/2018 08:56 PM, Adrian Bunk wrote:
> Control: severity -1 serious
> 
> On Sat, May 05, 2018 at 05:58:21PM +0200, Daniel Stender wrote:
>> Control: severity -1 important
>>
>> I'm lowering the severity of this bug report now to unblock the migration to 
>> testing.
> 
> The failed mips64el build does block testing migration in any case:
> https://tracker.debian.org/pkg/llvmlite

#898002

> The easiest way forward might be going from 5.0 to 6.0?

#898004
 
>> DS
> 
> cu
> Adrian

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885510 [src:ntfs-config] ntfs-config: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885518 [src:lptools] lptools: Recommends unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885526 [src:spice-gtk] spice-gtk: Drop unneeded Build-Depends on 
unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885506 [src:yorick-yao] yorick-yao: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885496 [src:xpn] xpn: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885508 [src:obmenu] obmenu: Depends on unmaintained python-glade2
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885492 [src:utf8-migration-tool] utf8-migration-tool: Depends on 
unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885487 [src:tictactoe-ng] tictactoe-ng: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885479 [src:simple-image-reducer] : Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885505 [src:yorick-spydr] yorick-spydr: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885481 [smartpm] smartpm: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885495 [src:xmms2tray] xmms2tray: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885491 [src:ttb] ttb: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885494 [src:virtualbricks] virtualbricks: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885485 [src:tegaki-recognize] tegaki-recognize: Depends on unmaintained 
pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885477 [src:reinteract] reinteract: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885474 [src:pythontracer] pythontracer: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885471 [src:tegaki-pygtk] tegaki-pygtk: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885473 [python-zbarpygtk] python-zbarpygtk: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885379 [src:liblarch] liblarch: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885311 [src:keepnote] keepnote: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885470 [src:sqlkit] sqlkit: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885359 [src:oboinus] oboinus: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885307 [src:ibus-sunpinyin] ibus-sunpinyin: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885351 [src:mcomix] mcomix: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885373 [src:python-gtkglext1] python-gtkglext1: Depends on unmaintained 
pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885368 [src:pyscrabble] pyscrabble: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885378 [src:kiwi] kiwi: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885362 [src:prelude-notify] prelude-notify: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885369 [src:pythoncad] pythoncad: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885363 [pwrkap-gui] pwrkap-gui: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885364 [pybootchartgui] pybootchartgui: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885365 [src:pybridge] pybridge: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885366 [src:pyneighborhood] pyneighborhood: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885309 [src:jack-mixer] jack-mixer: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885302 [src:gtklick] gtklick: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885357 [src:nicotine] nicotine: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885305 [src:hijra] hijra: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885301 [src:gtk-recordmydesktop] gtk-recordmydesktop: Depends on 
unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885360 [pam-dbus-notify] pam-dbus-notify: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885298 [src:gquilt] gquilt: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885312 [src:key-mon] key-mon: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885313 [src:lottanzb] lottanzb: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885356 [src:ndisgtk] ndisgtk: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885353 [src:mirage] mirage: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885361 [src:pondus] pondus: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885352 [src:magicor] magicor: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885354 [src:musiclibrarian] musiclibrarian: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885308 [src:idjc] idjc: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885280 [src:fslint] fslint: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885285 [src:geda-xgsch2pcb] geda-xgsch2pcb: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885282 [src:gameclock] gameclock: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885299 [src:griffith] griffith: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885270 [src:d-rats] d-rats: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885291 [src:globs] globs: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885268 [src:comix] comix: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885275 [src:disk-manager] disk-manager: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885303 [src:gwakeonlan] gwakeonlan: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885273 [src:diffuse] diffuse: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885276 [src:driconf] driconf: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885258 [src:apoo] apoo: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885257 [src:agtl] agtl: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885254 [bluewho] bluewho: Depends on deprecated pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885300 [src:gtg] gtg: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885274 [src:directoryassistant] directoryassistant: Depends on 
unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885281 [src:furiusisomount] furiusisomount: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885256 [src:activity-log-manager] activity-log-manager: Depends on 
unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885290 [src:geximon] geximon: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885136 [4digits] 4digits: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885262 [src:buxon] buxon: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885279 [src:ffrenzy] ffrenzy: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885277 [src:emma] emma: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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

Bug#885135: pygtk will be part of buster

[Adrian Bunk]

Control: severity -1 important

pygtk will be part of buster, see #895248 for background.

Note that pygtk is Python 2 only, and Python 2 is expected to be
removed from unstable after the release of buster.
It is therefore still advisable to port these packages away
from pygtk.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: pygtk will be part of buster

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #885284 [src:gbirthday] gbirthday: Depends on unmaintained pygtk
Severity set to 'important' from 'serious'

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