Bug#924158: marked as done (lirc shoud byte-compile its Python modules in postinst)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2019 02:40:21 +
with message-id 
and subject line Bug#924158: fixed in lirc 0.10.1-5.1
has caused the Debian Bug report #924158,
regarding lirc shoud byte-compile its Python modules in postinst
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.)


-- 
924158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lirc
Version: 0.10.1-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

Per the Debian Python policy [0], lirc should be automatically byte-compiling
its installed Python modules.

I'm not sure why it's not done automatically by dh-python in your package,
though I expect the right maintscript is injected in a phase that you overrode.


Best,

  nicoo


[0]: 
https://www.debian.org/doc/packaging-manuals/python-policy/module_packages.html#byte_compilation

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlyEStsRHG5pY29vQGRl
Ymlhbi5vcmcACgkQ5vmO4pLV7MtDwg//Scj2c7jQ+cMzq+9my0VVrLnV6ZfAG1Pf
nID5/eveTb7+zH4LMx3av91/l9B2kkM3TfLR3rDIJqQNniV0OUf6AnkwAqiiK1Yn
ghrLQ9RfcI0b4tVIMC6TYYHHcfv7V1mjLe46wEOEbcL369Sy7HK9lvQoId3QFpVc
07GiiCwvA47ctW7HW2j/l62//2ULpDIfKYohgH/AyCfbwv1qvEoWvB2bxTVIKnfE
HskyzMaMwDPd3Md4W3leiiYj4//n3PEUCH4ucvXbAO7B0pe7UmHdgchPY/7V30iH
BnlGcfiBlAXduk0j203hp8sLSBOkFTh7kMJZCh3UxrUYVXrNWHEdgal9rYxTPjjz
dtB/EaeWLbd8O5481JQv5gnYhkQTeUayVDJDWQZFyZYndtA5ZcVhOuBjHflK/aLG
ZHH2u+VbsGg/i4LyIT6d3gOykaDYUqJXHtNjb+BZBWFelkuHuBS3Tmg3HM01vtdJ
c9YEvOnY3QaLBzA+6dV4NfW0lAkzDBsifknWqo8Ch+3y1trdzuC+Mid61aJ7Rvu7
MAHSVNa/E3IgfFtIUkjQ4npW6S8YvoPrlY+eyJv4TvsUFrL5h9Yt+j/WYX8Nmne/
GFZq9PUZc8YcMKTEAToHOIa/wPmehddH3tn6vYiaFsjVFQSbqmf2zRPq9t7FvvGD
OldzCUP8o1U=
=My4/
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: lirc
Source-Version: 0.10.1-5.1

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

Debian distribution maintenance software
pp.
Nicolas Braud-Santoni  (supplier of updated lirc 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: Tue, 12 Mar 2019 01:33:40 +0100
Source: lirc
Architecture: source
Version: 0.10.1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team 
Changed-By: Nicolas Braud-Santoni 
Closes: 919843 924158
Changes:
 lirc (0.10.1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   * debian/rules
 + Remove rdfind-based dedup (Closes: #919843)
   Using dh_installdocs --link-docs was investigated, and rejected due to
   - limited benefits;
   - interactions between lirc-docs shipping files under 
/usr/share/doc/lirc,
 but liblirc0 being the obvious candidate due to dependencies.
 .
 + Do not install conffiles in a dummy location
   dpkg will, by default, not overwrite users' conffiles,
   so shipping them in a different location is superfluous.
 .
   * Removed liblircclient{0,-dev}
 They were obsolete transitional packages that predated the stretch release.
 .
   * Rename debian/post{inst,rm} to lirc.post{inst,rm}
   * debian/lirc.{postinst,prerm}: Recompile and remove Python bytecode as 
needed
 Closes: #924158
 .
   * debian/control: Fix relationships on liblirc{,client}-dev.
 This should be Breaks+Replaces, not Conflict+Replaces.
 Using the former should ensure that upgrading from stretch works smoothly.
 .
   * debian/changelog: Fix spelling in v0.10.1-4

Bug#919843: marked as done (lirc-doc: broken symlinks: /usr/share/doc/lirc/lirc.org/* -> /build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/*)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2019 02:40:21 +
with message-id 
and subject line Bug#919843: fixed in lirc 0.10.1-5.1
has caused the Debian Bug report #919843,
regarding lirc-doc: broken symlinks: /usr/share/doc/lirc/lirc.org/* -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/*
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.)


-- 
919843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lirc-doc
Version: 0.10.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m24.4s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/lirc/plugindocs/var -> /var/lib/lirc/plugins (lirc-doc)
  /usr/share/doc/lirc/plugindocs/lirc.css -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/html/lirc.css 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/marb18.jpg -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/images/marb18.jpg 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/lirc.gif -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/images/lirc.gif 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/favicon.ico -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/favicon.ico
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/diode.gif -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/images/diode.gif 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/images/atwf83.jpg -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/images/atwf83.jpg 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/html/table.html -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/html/table.html 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/html/plugins-index.html -> 
/var/lib/lirc/plugins/index.html (lirc-doc)
  /usr/share/doc/lirc/lirc.org/html/lirc.css -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/html/lirc.css 
(lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/variables_4.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_5.js
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/groups_4.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_13.js
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/functions_12.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_15.js
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/defines_a.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_16.js
 (lirc-doc)
  /usr/share/doc/lirc/lirc.org/api-docs/html/search/classes_e.js -> 
/build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/lirc.org/api-docs/html/search/all_14.js
 (lirc-doc)


The targets are absolute build-time paths ...


cheers,

Andreas


lirc-doc_0.10.1-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lirc
Source-Version: 0.10.1-5.1

We believe that the bug you reported is fixed in the latest version of
lirc, 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.
Nicolas Braud-Santoni  (supplier of updated lirc 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: Tue, 12 Mar 2019 01:33:40 +0100
Source: lirc
Architecture: source
Version: 0.10.1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team 
Changed-By: Nicolas Braud-Santoni 
Closes: 919843 924158
Changes:
 lirc (0.10.1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   * debian/rules
 + Remove rdfind-based dedup (Closes: #919843)
   Using dh_installdocs --link-docs was investigated, and rejected due to
   - limited benefits;
   - interactions between lirc-docs shipping files under 
/usr/share/doc/lirc,
 but liblirc0 being the obvious candidate due to 

Processed: closing 915119

[Debian Bug Tracking System]

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

> close 915119 2.7.5-1
Bug #915119 [libdnssec6] libdnssec6: Does not link against pthread but uses its 
symbols
There is no source info for the package 'libdnssec6' at version '2.7.5-1' with 
architecture ''
Unable to make a source version for version '2.7.5-1'
Marked as fixed in versions 2.7.5-1.
Bug #915119 [libdnssec6] libdnssec6: Does not link against pthread but uses its 
symbols
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#924501: marked as done (lintian: spurious maintainer-script-supports-ancient-package-version)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 23:04:30 +
with message-id 
and subject line Bug#924501: fixed in lintian 2.11.0
has caused the Debian Bug report #924501,
regarding lintian: spurious maintainer-script-supports-ancient-package-version
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.)


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

Hi,

I'm getting 
  X: lam4-dev: maintainer-script-supports-ancient-package-version preinst:4 
7.1.4-3 (2012-04-09 < 2015-04-26)
in a not-yet-uploaded NMU 7.1.4-3.2 for src:lam.

== 8< debian/lam4-dev.preinst =
#!/bin/sh
set -e

if dpkg --compare-versions "$2" lt-nl "7.1.4-3.2~"
then
update-alternatives --remove mpi /usr/include/lam
fi

# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.

#DEBHELPER#
== >8 ==


Andreas
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.11.0

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lintian 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, 18 Mar 2019 22:20:48 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.11.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 924082 924116 924417 924501
Changes:
 lintian (2.11.0) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * Support dh-sequence-{gir,gnome,python3} etc. virtual packages as
 satisfying various build-dependencies. (Closes: #924082)
   * Don't detect non-maintainer upload (NMU) versions when checking for
 maintainer scripts that support "ancient" package versions.
 (Closes: #924501)
   * Correct false-positives in when checking for dh-runit packages that
 lack a "Breaks" substvar by ensuring that the binary package actually
 uses runit. (Closes: #924116)
   * Update the long description of the
 new-package-should-not-package-python2-module tag to justify further
 why a changelog entry is more appropriate than an override.
   * Remove errant "#" from the long description of
 inconsistent-appstream-metadata-license.
 .
   [ Felix Lechner ]
   * Deprecate static labs; all labs are temporary from now on.
   * In autopkgtests, allow output to stderr to shorten waiting period.
   * Fix the rules-requires-root-implicitly test on stretch.
   * For stretch-backports, also Build-Depend on the "XS" version of the
 Text::CSV Perl module in addition to the pure Perl version.
 .
   [ Stewart Ferguson ]
   * Allow *.pth files in Python directories to avoid false-positives for
 unknown-file-in-python-module-directory. (Closes: #924417)
 .
   [ Paul Wise ]
   * Add/fix several spelling corrections.
Checksums-Sha1:
 b9f25645ad0bbc2fc8f467d0b112626dcd87db63 3853 lintian_2.11.0.dsc
 43287ac82e6aed639187807c8a6680c8090d63c7 1717584 lintian_2.11.0.tar.xz
 298a911932e6b76a47fc1ce07d1e2b2eaeb44c9a 1187308 lintian_2.11.0_all.deb
 1beeba8b7e0dc5bb9f5e2229029e7c69106d24d8 18119 lintian_2.11.0_amd64.buildinfo
Checksums-Sha256:
 8f2c72cbc8d8f5747f36026075c5e9cd06e6d85d254e268a4cb60a16364506a4 3853 
lintian_2.11.0.dsc
 4fc134fe7ac3fee9bdb32b069b841de196f1b081811d993e069bf073d2af1efe 1717584 
lintian_2.11.0.tar.xz
 1350fdc89992dc834d45a704eeddfef4818e1c58ed424e5feafd35d0c79d0e57 1187308 
lintian_2.11.0_all.deb
 8cd3c483d4ecb2da2803a95dfb799db1b92aa53feb7f973e671b742ae9e1c121 18119 
lintian_2.11.0_amd64.buildinfo
Files:
 edc20194d72b8961527920f3a24876b3 3853 devel optional lintian_2.11.0.dsc
 3ca0f7959afe8d6c48f525d7ebbcfed6 1717584 devel optional lintian_2.11.0.tar.xz
 1e9e71223285f3fc797d063326c83989 1187308 devel optional lintian_2.11.0_all.deb
 ff41d0cecb6e30373c5fc8ff985ca174 18119 devel optional 
lintian_2.11.0_amd64.buildinfo

Bug#924082: marked as done (lintian: missing-build-dependency triggered for dh-sequence)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 23:04:30 +
with message-id 
and subject line Bug#924082: fixed in lintian 2.11.0
has caused the Debian Bug report #924082,
regarding lintian: missing-build-dependency triggered for dh-sequence
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.)


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

debhelper 12 supports a new special dh-sequence- build-depends feature
[1]. For instance, a Build-Depends on dh-sequence-gnome (a virtual
package provided by gnome-pkg-tools) will automatically pass the
'--with gnome' option to dh without needing that to be specified in
debian/rules.

The lintian tags need to be updated for this. For instance, here's the
lintian errors I got with totem 3.32.0-1 targeted at experimental. The
final error "missing-build-dependency gnome-pkg-tools" triggered an
auto-reject.


E: totem source: missing-build-dependency-for-dh_-command dh_python3
=> dh-python
E: totem source: missing-build-dependency-for-dh_-command
dh_girepository => gobject-introspection
E: totem source: missing-build-dependency gnome-pkg-tools


So if you find the dh_python3 helper is being used, a Build-Depends on
dh-sequence-python3 should satisfy the requirement.

If you can, I'm requesting that this issue be fixed for Buster since a
growing number of packages will be using dh-sequence.

[1] https://manpages.debian.org/unstable/dh#OPTIONS

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.11.0

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lintian 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, 18 Mar 2019 22:20:48 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.11.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 924082 924116 924417 924501
Changes:
 lintian (2.11.0) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * Support dh-sequence-{gir,gnome,python3} etc. virtual packages as
 satisfying various build-dependencies. (Closes: #924082)
   * Don't detect non-maintainer upload (NMU) versions when checking for
 maintainer scripts that support "ancient" package versions.
 (Closes: #924501)
   * Correct false-positives in when checking for dh-runit packages that
 lack a "Breaks" substvar by ensuring that the binary package actually
 uses runit. (Closes: #924116)
   * Update the long description of the
 new-package-should-not-package-python2-module tag to justify further
 why a changelog entry is more appropriate than an override.
   * Remove errant "#" from the long description of
 inconsistent-appstream-metadata-license.
 .
   [ Felix Lechner ]
   * Deprecate static labs; all labs are temporary from now on.
   * In autopkgtests, allow output to stderr to shorten waiting period.
   * Fix the rules-requires-root-implicitly test on stretch.
   * For stretch-backports, also Build-Depend on the "XS" version of the
 Text::CSV Perl module in addition to the pure Perl version.
 .
   [ Stewart Ferguson ]
   * Allow *.pth files in Python directories to avoid false-positives for
 unknown-file-in-python-module-directory. (Closes: #924417)
 .
   [ Paul Wise ]
   * Add/fix several spelling corrections.
Checksums-Sha1:
 b9f25645ad0bbc2fc8f467d0b112626dcd87db63 3853 lintian_2.11.0.dsc
 43287ac82e6aed639187807c8a6680c8090d63c7 1717584 lintian_2.11.0.tar.xz
 298a911932e6b76a47fc1ce07d1e2b2eaeb44c9a 1187308 lintian_2.11.0_all.deb
 1beeba8b7e0dc5bb9f5e2229029e7c69106d24d8 18119 lintian_2.11.0_amd64.buildinfo
Checksums-Sha256:
 8f2c72cbc8d8f5747f36026075c5e9cd06e6d85d254e268a4cb60a16364506a4 3853 
lintian_2.11.0.dsc
 4fc134fe7ac3fee9bdb32b069b841de196f1b081811d993e069bf073d2af1efe 1717584 

Bug#924417: marked as done (lintian: Allow *.pth files in python dist-packages)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 23:04:30 +
with message-id 
and subject line Bug#924417: fixed in lintian 2.11.0
has caused the Debian Bug report #924417,
regarding lintian: Allow *.pth files in python dist-packages
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.)


-- 
924417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.9.1
Severity: normal
Tags: patch

Dear Maintainer,

/usr/lib/python*/dist-packages/*.pth files currently trigger lintian error
tag:

unknown-file-in-python-module-directory

*.pth should not be unknown. They are well-documented by the Python
specification[1] and this location is exactly where they belong.

Legitimate uses of this file exist in the archive.  python-
testing.mysqld[2] and python-input-pad[3] override this tag with the phrase
"false positive". The vast majority (>150) of others including python-
matplotlib and python-gobject-2 simply ignore this lintian error as they
deploy pth files[4].

There few important cases of this lintian error being raised including:
- debdry deploying 'control'
- python-cf deploying 'delme.nc'
- python-django-ranged-response deploying 'db.sqlite3'
- python3-csvkit deploying 'stdin_out.csv'

One could argue that the use of *.pth files should be discouraged.
Installing a package which deploys a *.pth can change the global python
environment. In this case a new tag (perhaps with lower severity) would be
more appropriate which warns the packager to carefully check the file's
contents and consider removing it. A more relevant tag describing the
position is less likely to be ignored than a general error which says this
Python-specification-compliant file is 'unknown'. A new tag would be more
appropriate than changing this tag because there are legitimate and
important instances of the existing tag as-is.

Best Regards,

Stewart Ferguson

[1] https://docs.python.org/3/library/site.html
[2] 
https://sources.debian.org/src/python-testing.mysqld/1.4.0-3/debian/python3-testing.mysqld.lintian-overrides/
[3] 
https://sources.debian.org/src/input-pad/1.0.3-3/debian/python-input-pad.lintian-overrides/
[4] 
https://lintian.debian.org/tags/unknown-file-in-python-module-directory.html

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
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

Versions of packages lintian depends on:
ii  binutils   2.31.1-15
ii  bzip2  1.0.6-9
ii  diffstat   1.62-1
ii  dpkg   1.19.5
ii  dpkg-dev   1.19.5
ii  file   1:5.35-2
ii  gettext0.19.8.1-9
ii  gpg2.2.12-1
ii  intltool-debian0.35.0+20060710.5
ii  libapt-pkg-perl0.1.34+b1
ii  libarchive-zip-perl1.64-1
ii  libcapture-tiny-perl   0.48-1
ii  libcgi-pm-perl 4.40-1
ii  libclass-accessor-perl 0.51-1
ii  libclone-perl  0.41-1+b1
pn  libdigest-sha-perl 
ii  libdpkg-perl   1.19.5
ii  libemail-valid-perl1.202-1
ii  libfile-basedir-perl   0.08-1
ii  libio-async-perl   0.72-1
ii  libipc-run-perl20180523.0-1
ii  liblist-moreutils-perl 0.416-1+b4
ii  libparse-debianchangelog-perl  1.2.0-13
ii  libpath-tiny-perl  0.108-1
ii  libtext-levenshtein-perl   0.13-1
ii  libtimedate-perl   2.3000-2
ii  libtry-tiny-perl   0.30-1
ii  liburi-perl1.76-1
ii  libxml-simple-perl 2.25-1
ii  libyaml-libyaml-perl   0.76+repack-1
ii  man-db 2.8.5-2
ii  patchutils 0.3.4-2
ii  perl   5.28.1-4
ii  t1utils1.41-3
ii  xz-utils   5.2.4-1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b5

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libhtml-parser-perl3.72-3+b3
ii  libtext-template-perl  1.54-1

-- no debconf information
From 

Bug#924116: marked as done (lintian: false positive of package-uses-dh-runit-...)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 23:04:30 +
with message-id 
and subject line Bug#924116: fixed in lintian 2.11.0
has caused the Debian Bug report #924116,
regarding lintian: false positive of package-uses-dh-runit-...
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.)


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

Package: lintian
Version: 2.7.0
Severity: wishlist

Dear Maintainer,

Lintian produces false positive
'package-uses-dh-runit-but-lacks-breaks-substvar' in following scenario:

 * source package builds bin:foo and bin:bar.
 * bin:foo uses functionality of dh_runit (test -f debian/foo.runit),
   but bar does not (! test -f debian/bar.runit)
 * Accordingly, Package stanza in `debian/control' for `foo' have
   'runit:Breaks'; stanza for `bar' do not.
 * Lintian compains about `bar'.

This behaviour is due my not-so-well-thought #920299. Can you please
report binary package `foo' only if `test -f debian/foo.runit', but no
Breaks: ${runit:Breaks} in stanza for `foo'?


pgpOeWMCk99jp.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.11.0

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lintian 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, 18 Mar 2019 22:20:48 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.11.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Description:
 lintian- Debian package checker
Closes: 924082 924116 924417 924501
Changes:
 lintian (2.11.0) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * Support dh-sequence-{gir,gnome,python3} etc. virtual packages as
 satisfying various build-dependencies. (Closes: #924082)
   * Don't detect non-maintainer upload (NMU) versions when checking for
 maintainer scripts that support "ancient" package versions.
 (Closes: #924501)
   * Correct false-positives in when checking for dh-runit packages that
 lack a "Breaks" substvar by ensuring that the binary package actually
 uses runit. (Closes: #924116)
   * Update the long description of the
 new-package-should-not-package-python2-module tag to justify further
 why a changelog entry is more appropriate than an override.
   * Remove errant "#" from the long description of
 inconsistent-appstream-metadata-license.
 .
   [ Felix Lechner ]
   * Deprecate static labs; all labs are temporary from now on.
   * In autopkgtests, allow output to stderr to shorten waiting period.
   * Fix the rules-requires-root-implicitly test on stretch.
   * For stretch-backports, also Build-Depend on the "XS" version of the
 Text::CSV Perl module in addition to the pure Perl version.
 .
   [ Stewart Ferguson ]
   * Allow *.pth files in Python directories to avoid false-positives for
 unknown-file-in-python-module-directory. (Closes: #924417)
 .
   [ Paul Wise ]
   * Add/fix several spelling corrections.
Checksums-Sha1:
 b9f25645ad0bbc2fc8f467d0b112626dcd87db63 3853 lintian_2.11.0.dsc
 43287ac82e6aed639187807c8a6680c8090d63c7 1717584 lintian_2.11.0.tar.xz
 298a911932e6b76a47fc1ce07d1e2b2eaeb44c9a 1187308 lintian_2.11.0_all.deb
 1beeba8b7e0dc5bb9f5e2229029e7c69106d24d8 18119 lintian_2.11.0_amd64.buildinfo
Checksums-Sha256:
 8f2c72cbc8d8f5747f36026075c5e9cd06e6d85d254e268a4cb60a16364506a4 3853 
lintian_2.11.0.dsc
 4fc134fe7ac3fee9bdb32b069b841de196f1b081811d993e069bf073d2af1efe 1717584 
lintian_2.11.0.tar.xz
 1350fdc89992dc834d45a704eeddfef4818e1c58ed424e5feafd35d0c79d0e57 1187308 
lintian_2.11.0_all.deb
 8cd3c483d4ecb2da2803a95dfb799db1b92aa53feb7f973e671b742ae9e1c121 18119 
lintian_2.11.0_amd64.buildinfo
Files:
 edc20194d72b8961527920f3a24876b3 3853 devel optional lintian_2.11.0.dsc
 3ca0f7959afe8d6c48f525d7ebbcfed6 1717584 devel optional lintian_2.11.0.tar.xz
 

Bug#924620: marked as done (misbehaving guest can corrupt firmware image)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 22:20:07 +
with message-id 
and subject line Bug#924620: fixed in edk2 0~20190309.89910a39-1
has caused the Debian Bug report #924620,
regarding misbehaving guest can corrupt firmware image
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.)


-- 
924620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-efi-aarch64
Version: 0~20181115.85588389-2
Severity: important

Buggy EFI apps[1] can corrupt the firmware flash volume by dereferencing
NULL pointers because we map the NOR flash at 0x0. Upstream has merged
patches to make these inadvertent accesses fault instead.

[1] For examples, see:
  https://bugs.launchpad.net/bugs/1811722
  https://bugs.launchpad.net/bugs/1811901
[2] 51bb05c795 ArmVirtPkg/QemuVirtMemInfoLib: trim the MMIO region mapping
5e27deed43 ArmVirtPkg/NorFlashQemuLib: disregard our primary FV
aa1097921d ArmPkg/ArmMmuLib ARM: handle unmapped sections when updating 
permissions
36a87fec68 ArmPkg/ArmMmuLib ARM: handle unmapped section in 
GetMemoryRegion()

Ubuntu version of this bug: https://bugs.launchpad.net/bugs/1812093

-- 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.20.0-trunk-amd64 (SMP w/2 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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: edk2
Source-Version: 0~20190309.89910a39-1

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

Debian distribution maintenance software
pp.
dann frazier  (supplier of updated edk2 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, 18 Mar 2019 15:38:21 -0600
Source: edk2
Architecture: source
Version: 0~20190309.89910a39-1
Distribution: experimental
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: dann frazier 
Closes: 924615 924620
Changes:
 edk2 (0~20190309.89910a39-1) experimental; urgency=medium
 .
   * New upstream release, based on edk2-stable201903 tag.
 - Fixes for CVE-2018-12178, CVE-2018-12180 and CVE-2018-12181
   Closes: #924615.
 - qemu-efi-*: Avoid silent corruption of firmware flash image
   by buggy EFI apps. Closes: #924620, LP: #1812093.
 - d/binary-check.blacklist: Drop binaries removed upstream.
 - d/binary-check.whitelist: Add new files detected as binary
   that were hand-verified to be source.
 - Bump openssl up to 1.1.0j.
 - qemu-efi-{arm,aarch64}: Drop -DINTEL_BDS from build flags.
   It became the default some time ago and was removed.
 - ovmf: Stop cargo-culting the inclusion and build of external
   EdkShell source. This is now no longer supported by upstream,
   and is a no-op because it was replaced by the internal UEFI
   shell back 2013 (9bef3cdc "OvmfPkg: Build and use the UEFI shell
   by default").
 - qemu-efi-{arm,aarch64}: Don't explicitly build ShellPkg,
   ArmVirtPkg has been doing it since 2015 (da1ce6f8
   "ArmVirtualizationPkg: build UEFI shell from source").
 - Don't explicitly build FatPkg, OvmfPkg & ArmVirtPkg have
   included it since 2016 (aa47e529 "OvmfPkg: Convert to using
   FatPkg in the EDK II tree"), (42e3d9eb "ArmVirtPkg: Convert to
   build FatPkg from source").
 - d/p/no-missing-braces.diff: Forward port.
 - d/p/no-stack-protector-all-archs.diff: Forward port.
Checksums-Sha1:
 388a7224c852916e1912763ec739fde6ebe9b4cd 2338 edk2_0~20190309.89910a39-1.dsc
 e6d4ff6e0567a0bb81927c535e375a4a51a378bc 23339972 
edk2_0~20190309.89910a39.orig.tar.xz
 0701dc3c4f0cd50625fde26bb039a85cde58a355 15228 
edk2_0~20190309.89910a39-1.debian.tar.xz
 

Bug#924615: marked as done (CVE-2018-12178 CVE-2018-12180 CVE-2018-12181)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 22:20:07 +
with message-id 
and subject line Bug#924615: fixed in edk2 0~20190309.89910a39-1
has caused the Debian Bug report #924615,
regarding CVE-2018-12178 CVE-2018-12180 CVE-2018-12181
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.)


-- 
924615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: edk2
Severity: grave
Tags: security

Please see
https://security-tracker.debian.org/tracker/CVE-2018-12178
https://security-tracker.debian.org/tracker/CVE-2018-12180
https://security-tracker.debian.org/tracker/CVE-2018-12181

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: edk2
Source-Version: 0~20190309.89910a39-1

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

Debian distribution maintenance software
pp.
dann frazier  (supplier of updated edk2 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, 18 Mar 2019 15:38:21 -0600
Source: edk2
Architecture: source
Version: 0~20190309.89910a39-1
Distribution: experimental
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: dann frazier 
Closes: 924615 924620
Changes:
 edk2 (0~20190309.89910a39-1) experimental; urgency=medium
 .
   * New upstream release, based on edk2-stable201903 tag.
 - Fixes for CVE-2018-12178, CVE-2018-12180 and CVE-2018-12181
   Closes: #924615.
 - qemu-efi-*: Avoid silent corruption of firmware flash image
   by buggy EFI apps. Closes: #924620, LP: #1812093.
 - d/binary-check.blacklist: Drop binaries removed upstream.
 - d/binary-check.whitelist: Add new files detected as binary
   that were hand-verified to be source.
 - Bump openssl up to 1.1.0j.
 - qemu-efi-{arm,aarch64}: Drop -DINTEL_BDS from build flags.
   It became the default some time ago and was removed.
 - ovmf: Stop cargo-culting the inclusion and build of external
   EdkShell source. This is now no longer supported by upstream,
   and is a no-op because it was replaced by the internal UEFI
   shell back 2013 (9bef3cdc "OvmfPkg: Build and use the UEFI shell
   by default").
 - qemu-efi-{arm,aarch64}: Don't explicitly build ShellPkg,
   ArmVirtPkg has been doing it since 2015 (da1ce6f8
   "ArmVirtualizationPkg: build UEFI shell from source").
 - Don't explicitly build FatPkg, OvmfPkg & ArmVirtPkg have
   included it since 2016 (aa47e529 "OvmfPkg: Convert to using
   FatPkg in the EDK II tree"), (42e3d9eb "ArmVirtPkg: Convert to
   build FatPkg from source").
 - d/p/no-missing-braces.diff: Forward port.
 - d/p/no-stack-protector-all-archs.diff: Forward port.
Checksums-Sha1:
 388a7224c852916e1912763ec739fde6ebe9b4cd 2338 edk2_0~20190309.89910a39-1.dsc
 e6d4ff6e0567a0bb81927c535e375a4a51a378bc 23339972 
edk2_0~20190309.89910a39.orig.tar.xz
 0701dc3c4f0cd50625fde26bb039a85cde58a355 15228 
edk2_0~20190309.89910a39-1.debian.tar.xz
 1ab531b384695054025cfce7a882a841b5429a42 7456 
edk2_0~20190309.89910a39-1_source.buildinfo
Checksums-Sha256:
 d99370ce9ee37146e81716658ef5e5a955d4e5fe8020c731972e6a12aff311e2 2338 
edk2_0~20190309.89910a39-1.dsc
 62e1a2062b595b559f66b52a71c99c0aa43f099a7ff81fe023d6f197eb7455e5 23339972 
edk2_0~20190309.89910a39.orig.tar.xz
 380e37cb6ade8feaec62f694e68ff53fac41a59fadcf98839e96c82f8f988522 15228 
edk2_0~20190309.89910a39-1.debian.tar.xz
 dde54a9526e0df785a3c62ca6265956408207967424e326f303f5c543c376b2f 7456 
edk2_0~20190309.89910a39-1_source.buildinfo
Files:
 e5c741088cba2ff031f4ebef8960831e 2338 misc optional 
edk2_0~20190309.89910a39-1.dsc
 41ff12588d839a58b80283dedc866c4a 23339972 misc optional 
edk2_0~20190309.89910a39.orig.tar.xz
 341a1fbb571a6d42d9d33c3751dadb26 15228 misc optional 
edk2_0~20190309.89910a39-1.debian.tar.xz
 eca5e225c19e87f43347546e83c829a0 7456 misc optional 
edk2_0~20190309.89910a39-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEECfR9vy0y7twkQ+vuG/g8XlT8hkAFAlyQFMMRHGRhbm5mQGRl

Processed: RFS: xhk/1.1-1 [ITP] -- Xlib Half Keyboard/Half-QWERTY, one handed keyboard

[Debian Bug Tracking System]

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

> close 917629
Bug #917629 [sponsorship-requests] RFS: xhk/1.1-1 [ITP] -- Xlib Half 
Keyboard/Half-QWERTY, one handed keyboard
Marked Bug as done
> stop
Stopping processing here.

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

Bug#924909: marked as done (texlive-fonts-extra: dpkg install texlive-fonts-extra_2018.20190227-1_all.deb hangs)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2019 07:00:05 +0900
with message-id <20190318220005.gb28...@burischnitzel.preining.info>
and subject line Re: Bug#924909: texlive-fonts-extra: dpkg install 
texlive-fonts-extra_2018.20190227-1_all.deb hangs
has caused the Debian Bug report #924909,
regarding texlive-fonts-extra: dpkg install 
texlive-fonts-extra_2018.20190227-1_all.deb hangs
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.)


-- 
924909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-fonts-extra
Version: 2018.20190131-1
Severity: normal

Quick report: an apt-get upgrade hangs when installing
texlive-fonts-extra_2018.20190227-1_all.deb. Neede tp kill process.

Running 
dpkg -i /var/cache/apt/archives/texlive-fonts-extra_2018.20190227-1_all.deb
directly also hangs in same way. Actually it looks like a crash:-
Running with
dpkg -i -D10 /var/cache/apt/archives/texlive-fonts-extra_2018.20190227-1_all.deb

The process runs for many minutes and then appears to crash (the screen
also blanks and has to be restored).
The last messages are:
-
D10: path_remove_tree '/usr/share/texlive/texmf-dist/tex/plain/ly1.dpkg-tmp'
D10: path_remove_tree 
'/usr/share/texlive/texmf-dist/tex/plain/ly1/texnansi.tex.dpkg-tmp'
D10: path_remove_tree 
'/usr/share/texlive/texmf-dist/tex/plain/semaphor.dpkg-tmp'
D10: path_remove_tree 
'/usr/share/texlive/texmf-dist/tex/plain/semaphor/semaf.tex.dpkg-tmp'
D10: path_remove_tree '/var.dpkg-tmp'
D10: path_remove_tree '/var/lib.dpkg-tmp'
D10: path_remove_tree '/var/lib/tex-common.dpkg-tmp'
D10: path_remove_tree '/var/lib/tex-common/fontmap-cfg.dpkg-tmp'
D10: path_remove_tree '/var/lib/tex-common/fontmap-cfg/texlive.dpkg-tmp'
D10: path_remove_tree 
'/var/lib/tex-common/fontmap-cfg/texlive/texlive-fonts-extra.cfg.dpkg-tmp'
D10: path_remove_tree '/var/lib/dpkg/tmp.ci'
D10: path_remove_tree running rm -rf '/var/lib/dpkg/tmp.ci'
D10: path_remove_tree '/var/lib/dpkg/reassemble.deb'
dpkg: dependency problems prevent configuration of texlive-fonts-extra:
 texlive-fonts-extra depends on texlive-base (>= 2018.20190227); however:
  Package texlive-base is not configured yet.

dpkg: error processing package texlive-fonts-extra (--install):
 dependency problems - leaving unconfigured
Processing triggers for tex-common (6.11) ...
Running mktexlsr. This may take some time... done.
texlive-base is not ready, delaying updmap-sys call
update-language: texlive-base not installed and configured, doing nothing!
texlive-base is not ready, skipping fmtutil --all call
Errors were encountered while processing:
 texlive-fonts-extra



##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 1245 Mar 11 14:29 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Feb 28 14:28 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Mar  2 02:27 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Mar  2 02:27 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Mar 11 14:28 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Mar  2 02:27 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Mar  2 02:27 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2968 Mar 11 14:28 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 May 30  2014 mktex.cnf
-rw-r--r-- 1 root root 475 Mar 11 14:28 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-fonts-extra depends on:
it  tex-common6.11
iu  texlive-base  2018.20190227-2

Versions of packages texlive-fonts-extra 

Bug#924916: marked as done (RM: python-django-openstack-auth -- RoM; provided by python3-django-horizon)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:46:07 +
with message-id 
and subject line Bug#924919: Removed package(s) from unstable
has caused the Debian Bug report #924916,
regarding RM: python-django-openstack-auth -- RoM; provided by 
python3-django-horizon
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.)


-- 
924916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-openstack-auth
Version: 3.5.0-2
Severity: serious

Hi Thomas,

can this package be removed? If so, please reassign to ftp.debian.org
(and lover the severity to normal).

I'm again investigating openstack-dashboard related upgrade failures.
This may be #905183 returning, never being fixed, or a different
problem.

Having python-django-openstack-auth and python3-django-openstack-auth
available as both real packages (from src:python-django-openstack-auth)
and virtual packages (Provides/Conflicts/Replaces by
python3-django-horizon) does not make things easier for apt in this
case.
And I doubt that providing a python2 module from a python3 package is a
good idea ...

There are no rdepends left that depend on these packages.
So maybe consider dropping the Provides and Replaces (but keep the
Conflicts) in python3-django-horizon as well.


Thanks

Andreas
--- End Message ---
--- Begin Message ---
Version: 3.5.0-2+rm

Dear submitter,

as the package python-django-openstack-auth has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924919

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924943: marked as done (RM: pyspatialite -- ROM; Obsolete, no longer required for qgis)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:46:39 +
with message-id 
and subject line Bug#924943: Removed package(s) from unstable
has caused the Debian Bug report #924943,
regarding RM: pyspatialite -- ROM; Obsolete, no longer required for qgis
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.)


-- 
924943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Control: block -1 by 924908

Please remove pyspatialite from Debian. Now that qgis 3.4.x is in
unstable, it is no longer required nor used by any other package.

It is also obsolete upstream. Users should use the sqlite bindings for
Python and load the spatialite extension.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pyspatialite |   3.0.1-11 | source
pyspatialite |   3.0.1-13 | source
python-pyspatialite |   3.0.1-11 | kfreebsd-i386
python-pyspatialite |   3.0.1-13 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, mips, mips64el, mipsel, ppc64el, s390x

--- Reason ---
ROM; Obsolete, no longer required for qgis
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924943

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924919: marked as done (RM: python-django-openstack-auth -- ROM; Included in Horizon, deprecated)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:46:01 +
with message-id 
and subject line Bug#924919: Removed package(s) from unstable
has caused the Debian Bug report #924919,
regarding RM: python-django-openstack-auth -- ROM; Included in Horizon, 
deprecated
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.)


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


Dear FTP masters,

django-openstack-auth is now integrated in django-horizon, and therefore,
should be completely removed from Debian.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-django-openstack-auth |3.5.0-2 | source, all
python3-django-openstack-auth |3.5.0-2 | all

--- Reason ---
ROM; Included in Horizon, deprecated
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924919

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924746: marked as done (RM: emacs25-non-dfsg -- RoQA; superseded by src:emacs-non-dfsg)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:44:35 +
with message-id 
and subject line Bug#924746: Removed package(s) from unstable
has caused the Debian Bug report #924746,
regarding RM: emacs25-non-dfsg -- RoQA; superseded by src:emacs-non-dfsg
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.)


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

For the unversioned emacs packages, the new source package for non-free
bits is emacs-non-dfsg, which covers emacs 26.


Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

emacs25-common-non-dfsg |   25.2+1-1 | all
emacs25-non-dfsg |   25.2+1-1 | source

--- Reason ---
RoQA; superseded by src:emacs-non-dfsg
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924746

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924908: marked as done (RM: qgis [armhf] -- ROM; FTBFS on armhf)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:37 +
with message-id 
and subject line Bug#924908: Removed package(s) from unstable
has caused the Debian Bug report #924908,
regarding RM: qgis [armhf] -- ROM; FTBFS on armhf
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.)


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

Please remove qgis from armhf, it FTBFS due to a segfault.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libqgis-3d3.4.5 | 3.4.5+dfsg-1 | armhf
libqgis-analysis3.4.5 | 3.4.5+dfsg-1 | armhf
libqgis-app3.4.5 | 3.4.5+dfsg-1 | armhf
libqgis-core3.4.5 | 3.4.5+dfsg-1 | armhf
libqgis-customwidgets | 3.4.5+dfsg-1 | armhf
libqgis-dev | 3.4.5+dfsg-1 | armhf
libqgis-gui3.4.5 | 3.4.5+dfsg-1 | armhf
libqgis-native3.4.5 | 3.4.5+dfsg-1 | armhf
libqgis-server3.4.5 | 3.4.5+dfsg-1 | armhf
libqgisgrass7-3.4.5 | 3.4.5+dfsg-1 | armhf
libqgispython3.4.5 | 3.4.5+dfsg-1 | armhf
python3-qgis | 3.4.5+dfsg-1 | armhf
  qgis | 3.4.5+dfsg-1 | armhf
qgis-plugin-grass | 3.4.5+dfsg-1 | armhf
qgis-provider-grass | 3.4.5+dfsg-1 | armhf
qgis-providers | 3.4.5+dfsg-1 | armhf
qgis-server | 3.4.5+dfsg-1 | armhf

--- Reason ---
ROM; FTBFS on armhf
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924908

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#921746: marked as done (Should witty be removed?)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #921746,
regarding Should witty be removed?
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.)


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

Should witty be removed from the archive?

- No maintainer upload since 2016
- Remove from testing since 16 months
- Multiple RC bugs (3) and other legacy issues (QT4)
- Marginal popcon

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#884540: marked as done (libwt40: Clicking on any button raises a Wt internal error popup)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #884540,
regarding libwt40: Clicking on any button raises a Wt internal error popup
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.)


-- 
884540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwt40
Version: 3.3.6+dfsg-1.1
Severity: important

Dear Maintainer,

Clicking on any button raiseso a 'Wt internal error' popup.
It seems there is a version mismatch between the jquery source shipped with 
stretch and libwt40.
This issue requires users to compile and install wt-3.3.6 from source to make 
the applications work again.

Regards,

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

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

Versions of packages libwt40 depends on:
ii  libboost-date-time1.62.0   1.62.0+dfsg-4
ii  libboost-filesystem1.62.0  1.62.0+dfsg-4
ii  libboost-random1.62.0      1.62.0+dfsg-4
ii  libboost-regex1.62.0       1.62.0+dfsg-4
ii  libboost-system1.62.0      1.62.0+dfsg-4
ii  libboost-thread1.62.0      1.62.0+dfsg-4
ii  libc6                      2.24-11+deb9u1
ii  libgcc1                    1:6.3.0-18
ii  libgl1-mesa-glx [libgl1]   13.0.6-1+b2
ii  libglew2.0                 2.0.0-3+b1
ii  libglib2.0-0               2.50.3-2
ii  libgraphicsmagick-q16-3    1.3.25-8
ii  libhpdf-2.2.1              2.2.1-1.1+b1
ii  libpango-1.0-0             1.40.5-1
ii  libpangoft2-1.0-0          1.40.5-1
ii  libssl1.1                  1.1.0f-3+deb9u1
ii  libstdc++6                 6.3.0-18
ii  libwt-common               3.3.6+dfsg-1.1
ii  libx11-6                   2:1.6.4-3

Versions of packages libwt40 recommends:
ii  libwthttp40  3.3.6+dfsg-1.1
ii  tinymce      3.4.8+dfsg0-1

libwt40 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#869327: marked as done (Updating the emacs25-non-dfsg Uploaders list)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:44:40 +
with message-id 
and subject line Bug#924746: Removed package(s) from unstable
has caused the Debian Bug report #869327,
regarding Updating the emacs25-non-dfsg Uploaders list
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.)


-- 
869327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs25-non-dfsg
Version: 25.2+1-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Jerome Marant  has retired, so can't work on
the emacs25-non-dfsg package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
Version: 25.2+1-1+rm

Dear submitter,

as the package emacs25-non-dfsg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924746

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924770: marked as done (RM: witty -- RoQA; unmaintained, RC-buggy, dropped from testing since 1.5 years, RC-buggy)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:05 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #924770,
regarding RM: witty -- RoQA; unmaintained, RC-buggy, dropped from testing since 
1.5 years, RC-buggy
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.)


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

Please remove witty:

- No maintainer upload since 2016
- Removed from testing since 18 months
- Multiple RC bugs (4) and other legacy issues (QT4)
- Marginal popcon

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libwt-common | 3.3.6+dfsg-1.1 | all
 libwt-dbg | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
 libwt-dbg | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
 libwt-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
 libwt-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
 libwt-doc | 3.3.6+dfsg-1.1 | all
   libwt40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
   libwt40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwtdbo-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbo-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwtdbo40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbo40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwtdbofirebird-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbofirebird-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libwtdbofirebird40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbofirebird40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libwtdbomysql-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbomysql-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libwtdbomysql40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbomysql40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libwtdbopostgres-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbopostgres-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libwtdbopostgres40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbopostgres40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libwtdbosqlite-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbosqlite-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libwtdbosqlite40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtdbosqlite40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
libwtext-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtext-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwtext40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtext40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwtfcgi-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtfcgi-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwtfcgi40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwtfcgi40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwthttp-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwthttp-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwthttp40 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwthttp40 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwttest-dev | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwttest-dev | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
libwttest10 | 3.3.6+dfsg-1.1 | kfreebsd-amd64, kfreebsd-i386
libwttest10 | 3.3.6+dfsg-1.1+b1 | amd64, arm64, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
 witty | 3.3.6+dfsg-1.1 | source, all
 witty-dbg | 3.3.6+dfsg-1.1 | all
 witty-dev | 3.3.6+dfsg-1.1 | all
 witty-doc | 3.3.6+dfsg-1.1 | all

Bug#871286: marked as done (libwt40: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #871286,
regarding libwt40: requires rebuild against GCC 7 and symbols/shlibs bump
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.)


-- 
871286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwt40
Version: 3.3.6+dfsg-1.1
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string, std::allocator >[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string, std::allocator >()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#905008: marked as done (emacs25-common-non-dfsg: should be replaced by emacs-common-non-dfsg)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:44:40 +
with message-id 
and subject line Bug#924746: Removed package(s) from unstable
has caused the Debian Bug report #905008,
regarding emacs25-common-non-dfsg: should be replaced by emacs-common-non-dfsg
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.)


-- 
905008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-common-non-dfsg
Version: 25.2+1-1
Severity: normal

emacs-gtk has:

  Suggests: emacs-common-non-dfsg

which cannot be satisfied as emacs-common-non-dfsg does not exist.
I assume that emacs25-common-non-dfsg should be renamed to
emacs-common-non-dfsg.

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

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

Versions of packages emacs25-common-non-dfsg depends on:
ii  dpkg  1.19.0.5+b1
ii  install-info  6.5.0.dfsg.1-4

emacs25-common-non-dfsg recommends no packages.

emacs25-common-non-dfsg suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-1+rm

Dear submitter,

as the package emacs25-non-dfsg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924746

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#865395: marked as done (witty-examples: error in building examples)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #865395,
regarding witty-examples: error in building examples
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.)


-- 
865395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: witty-examples
Version: 3.3.6+dfsg-1.1
Severity: normal
Tags: patch

Dear Maintainer,

need to edit the default CMakeLists.txt file as described below to build 
hello.wt example


   * What led up to the situation? 
installed libhpdf-dev (which probably should be a prerequesite or a recommends 
with the package)

tried to compile the examples as described in the README 
(http://metadata.ftp-master.debian.org/changelogs/main/w/witty/witty_3.3.6+dfsg-1.1_README.Debian)
after typing:
cmake -DWT_SOURCE_DIR=/usr/lib/Wt -DEXAMPLES_CONNECTOR="wt;wthttp" 
-DCMAKE_BUILD_TYPE=Release /usr/lib/Wt/examples

make
the system failed:
[  0%] Linking CXX executable hello.wt
/usr/bin/ld: cannot find -llibhpdf
collect2: error: ld returned 1 exit status
hello/CMakeFiles/hello.wt.dir/build.make:94: recipe for target 'hello/hello.wt' 
failed

   * What exactly did you do (or not do) that was effective (or ineffective)?
edited /usr/lib/Wt/examples/CMakeLists.txt and changed line 43 from:
debug libhpdfd optimized libhpdf
to:
debug hpdfd optimized hpdf

   * What was the outcome of this action?
successful build:
[100%] Built target hello.wt


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

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

Versions of packages witty-examples depends on:
ii  libboost-filesystem1.62.0 1.62.0+dfsg-4
ii  libboost-program-options-dev  1.62.0.1
ii  libboost-system1.62.0 1.62.0+dfsg-4
ii  libboost-thread1.62.0 1.62.0+dfsg-4
ii  libc6 2.24-12
ii  libgcc1   1:7.1.0-7
ii  libhpdf-2.2.1 2.2.1-1.1+b1
ii  libqt4-dev4:4.8.7+dfsg-11
ii  libqtcore44:4.8.7+dfsg-11
ii  libstdc++67.1.0-7
ii  libwt40   3.3.6+dfsg-1.1
ii  libwtdbo403.3.6+dfsg-1.1
ii  libwtdbosqlite40  3.3.6+dfsg-1.1
ii  libwtext403.3.6+dfsg-1.1
ii  libwthttp40   3.3.6+dfsg-1.1

witty-examples recommends no packages.

Versions of packages witty-examples suggests:
ii  libwt-dev [witty-dev] 3.3.6+dfsg-1.1
ii  libwt-doc 3.3.6+dfsg-1.1
ii  libwtdbo-dev [witty-dev]  3.3.6+dfsg-1.1
ii  libwtdbo40 [witty-dev]3.3.6+dfsg-1.1
ii  libwtdbofirebird-dev [witty-dev]  3.3.6+dfsg-1.1
ii  libwtdbofirebird40 [witty-dev]3.3.6+dfsg-1.1
ii  libwtdbopostgres-dev [witty-dev]  3.3.6+dfsg-1.1
ii  libwtdbopostgres40 [witty-dev]3.3.6+dfsg-1.1
ii  libwtdbosqlite-dev [witty-dev]3.3.6+dfsg-1.1
ii  libwtdbosqlite40 [witty-dev]  3.3.6+dfsg-1.1
ii  libwtext-dev [witty-dev]  3.3.6+dfsg-1.1
ii  libwthttp-dev [witty-dev] 3.3.6+dfsg-1.1
ii  witty-dev 3.3.6+dfsg-1.1

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#904508: marked as done (libwt-common: broken symlink: /usr/share/Wt/resources/tiny_mce -> ../../tinymce/www)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #904508,
regarding libwt-common: broken symlink: /usr/share/Wt/resources/tiny_mce -> 
../../tinymce/www
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.)


-- 
904508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwt-common
Version: 3.3.6+dfsg-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m48.0s ERROR: FAIL: Broken symlinks:
  /usr/share/Wt/resources/tiny_mce -> ../../tinymce/www


Is libwt-common missing A Depends/Recommends/Suggests: tinymce ?

Feel free to downgrade the severity if the lack of tinymce does
not break functionality.


cheers,

Andreas


libwt-common_3.3.6+dfsg-1.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#893711: marked as done (please provide an HTML version of the documentation)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:44:40 +
with message-id 
and subject line Bug#924746: Removed package(s) from unstable
has caused the Debian Bug report #893711,
regarding please provide an HTML version of the documentation
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.)


-- 
893711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:emacs25-non-dfsg
Version: 25.2+1-1
Severity: wishlist

Dear Maintainer,

Please provide an HTML version of the Emacs documentation (keeping in mind that
HTML is the preferred documentation format in Debian, per policy 12.4).

You will have to decide whether shipping documents in a single page or in
multiple pages (upstream has both for the manual on its website¹). I tend to
favor the single page format, since that facilitates text searching within the
browser.

Cheers,

¹ https://www.gnu.org/software/emacs/manual/emacs.html

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 25.2+1-1+rm

Dear submitter,

as the package emacs25-non-dfsg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924746

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#875230: marked as done ([witty] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #875230,
regarding [witty] Future Qt4 removal from 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.)


-- 
875230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: witty
Version: 3.3.6+dfsg-1.1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#765173: marked as done ([libsrtp0] package not multiarch-aware)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #765173,
regarding [libsrtp0] package not multiarch-aware
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.)


-- 
765173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsrtp0
Version: 1.4.5~20130609~dfsg-1
Severity: important

--- Please enter the report below this line. ---

Package is missing multiarch support. This is needed by chromium:i386 on 
amd64.

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.3mq

Debian Release: jessie/sid
  900 testing www.deb-multimedia.org 
  900 testing security.debian.org 
  900 testing repos.fds-team.de 
  900 testing ftp.icm.edu.pl 
  800 stable  security.debian.org 
  800 stable  ftp.icm.edu.pl 
  700 unstablewww.deb-multimedia.org 
  700 unstableftp.icm.edu.pl 
  600 experimentalftp.icm.edu.pl 
  500 stable  deb.opera.com 
  500 proposed-updates ftp.icm.edu.pl 
  500 debian  packages.linuxmint.com 

--- Package information. ---
Depends  (Version) | Installed
==-+-===
libc6(>= 2.14) | 


Package's Recommends field is empty.

Suggests(Version) | Installed
=-+-===
srtp-utils| 
--- End Message ---
--- Begin Message ---
Version: 1.4.5~20130609~dfsg-2+rm

Dear submitter,

as the package srtp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924558: marked as done (RM: ruby-rails-assets-clipboard -- ROM; no longer required for gitlab, no reverse dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:42:33 +
with message-id 
and subject line Bug#924558: Removed package(s) from unstable
has caused the Debian Bug report #924558,
regarding RM: ruby-rails-assets-clipboard -- ROM; no longer required for 
gitlab, no reverse dependencies
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.)


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

This was originally packaged as a dependency of gitlab, which no longer
 require it (switched to node-clipboard in NEW).
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libjs-clipboard |1.4.2-1 | all
ruby-rails-assets-clipboard |1.4.2-1 | source, all

--- Reason ---
ROM; no longer required for gitlab, no reverse dependencies
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924558

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924209: marked as done (python-nbsphinx0.3-doc: broken symlink: /usr/share/doc/python-nbsphinx/rst -> html/_sources)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:44:12 +
with message-id 
and subject line Bug#924741: Removed package(s) from unstable
has caused the Debian Bug report #924209,
regarding python-nbsphinx0.3-doc: broken symlink: 
/usr/share/doc/python-nbsphinx/rst -> html/_sources
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.)


-- 
924209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-nbsphinx0.3-doc
Version: 0.4.1+zero.3.5+ds-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m21.0s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/python-nbsphinx/rst -> html/_sources (python-nbsphinx0.3-doc)

This symlink clashes with the python-nbsphinx-doc package,
you probably wanted to create
  /usr/share/doc/python-nbsphinx0.3/rst -> html/_sources
instead.^^^


cheers,

Andreas


python-nbsphinx0.3-doc_0.4.1+zero.3.5+ds-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.4.1+zero.3.5+ds-1+rm

Dear submitter,

as the package nbsphinx0.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924741

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#668567: marked as done (package includes conflicting config.h in /usr/include/srtp)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #668567,
regarding package includes conflicting config.h in /usr/include/srtp
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.)


-- 
668567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsrtp0-dev
Version: 1.4.4~dfsg-6

The package installs a copy of config.h to /usr/include/srtp

This config.h redefines a number of things that are standard across any
autotools project, e.g. PACKAGE_NAME

If someone is building another package (e.g. resiprocate) that depends
on srtp, then the defines in config.h from srtp may clash with those
from resiprocate/config.h

Sample error:

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DUSE_CARES -Wall
-Wno-deprecated -DRESIP_OSTYPE_LINUX -DRESIP_ARCH_X86_64
-DRESIP_LARCH_IA64 -D_REENTRANT -DRESIP_TOOLCHAIN_GNU -MT Flow.lo -MD
-MP -MF .deps/Flow.Tpo -c Flow.cxx  -fPIC -DPIC -o .libs/Flow.o
In file included from ../reTurn/client/TurnAsyncTlsSocket.hxx:3,
 from Flow.hxx:13,
 from Flow.cxx:10:
../config.h:69:1: warning: "PACKAGE_NAME" redefined


--- End Message ---
--- Begin Message ---
Version: 1.4.5~20130609~dfsg-2+rm

Dear submitter,

as the package srtp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#910292: marked as done (Do not release srtp 1.x with Buster)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #910292,
regarding Do not release srtp 1.x with 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.)


-- 
910292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hi,

on behalf of Jonas I'm filing a transition bug to track removal of the old
libsrtp0 from Debian.

src:srtp has built libsrtp0 and libsrtp0-dev. It is several years out of date.
The successor is src:libsrtp2 building libsrtp2-1 and libsrtp2-dev. Most rdeps
have already migrated. We'd like to avoid releasing libsrtp0 with Buster if
possible.

There has been an incomplete attempt to update libsrtp 1.x in experimental a
few years ago (building libsrtp1). This has never gained traction and has been
superseded by libsrtp2. The only accidental rdep inside experimental is waiting
for the buildds to catch up, then I'll request removal from experimental as
well.

Thanks,
Bernhard

Ben file:

title = "srtp";
is_affected = .depends ~ "libsrtp0" | .depends ~ "libsrtp0-dev" | .depends ~ 
"libsrtp2-1" | .depends ~ "libsrtp2-dev";
is_good = .depends ~ "libsrtp2-1" | .depends ~ "libsrtp2-dev";
is_bad = .depends ~ "libsrtp0" | .depends ~ "libsrtp0-dev";
--- End Message ---
--- Begin Message ---
Version: 1.4.5~20130609~dfsg-2+rm

Dear submitter,

as the package srtp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#804545: marked as done (patch jessie version for use with Chromium)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #804545,
regarding patch jessie version for use with Chromium
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.)


-- 
804545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsrtp0
Version: 1.4.5~20130609~dfsg-1.1
Severity: important
Tags: security

As described in #770659, Chromium is having problems with the standard
version of libsrtp0 on jessie.

Chromium upstream uses a bundled and patched version of libsrtp0. 
Chromium packages uploaded to jessie as security updates are not built
with the bundled version from upstream though.

There is a patch[2] for libsrtp0 that could be adapted for a stable update.

Users have been disabling the sandbox in Chromium to work around this
issue, hence the security tag has been used.

1.
http://anonscm.debian.org/cgit/pkg-chromium/pkg-chromium.git/tree/debian/rules#n61
2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770659#124
--- End Message ---
--- Begin Message ---
Version: 1.4.5~20130609~dfsg-2+rm

Dear submitter,

as the package srtp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#835834: marked as done (ruby-compass: please make the build reproducible)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:44 +
with message-id 
and subject line Bug#924565: Removed package(s) from unstable
has caused the Debian Bug report #835834,
regarding ruby-compass: 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.)


-- 
835834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-compass
Version: 1.0.3~dfsg-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], I noticed
that ruby-compass could not be built reproducibly.

Patch attached.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/2004_reproducible-build.patch  1970-01-01 
01:00:00.0 +0100
--- b/debian/patches/2004_reproducible-build.patch  2016-08-28 
18:26:54.511593100 +0100
@@ -0,0 +1,20 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-28
+
+--- ruby-compass-1.0.3~dfsg.orig/cli/lib/compass/commands/print_version.rb
 ruby-compass-1.0.3~dfsg/cli/lib/compass/commands/print_version.rb
+@@ -56,7 +56,12 @@ Options:
+   if name = ::Compass.version[:name]
+ lines.last << " (#{name})"
+   end
+-  lines << "Copyright (c) 2008-#{Time.now.year} Chris Eppstein"
++  if ENV['SOURCE_DATE_EPOCH'].nil?
++now = Time.now
++  else
++now = Time.at(ENV['SOURCE_DATE_EPOCH'].to_i).gmtime
++  end
++  lines << "Copyright (c) 2008-#{now.year} Chris Eppstein"
+   lines << "Released under the MIT License."
+   lines << "Compass is charityware."
+   lines << "Please make a tax deductable donation for a worthy cause: 
http://umdf.org/compass;
--- a/debian/patches/series 2016-08-28 18:18:38.966324108 +0100
--- b/debian/patches/series 2016-08-28 18:26:53.407581357 +0100
@@ -3,3 +3,4 @@
 2001_avoid_git_in_gemspec.patch
 2002-frameworks-below-usr-share.patch
 2003_disable_rb-fsevent.patch
+2004_reproducible-build.patch
--- End Message ---
--- Begin Message ---
Version: 1.0.5~dfsg-5+rm

Dear submitter,

as the package ruby-compass has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924565

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#812917: marked as done (please multiarchify the package)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #812917,
regarding please multiarchify the package
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.)


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

Package: src:srtp
Version: 1.4.5~20130609~dfsg-1.1
Tags: patch
User: d...@debian.org
Usertags: multiarch

patch at
http://launchpadlibrarian.net/235405282/srtp_1.4.5~20130609~dfsg-1.1_1.4.5~20130609~dfsg-1.1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Version: 1.4.5~20130609~dfsg-2+rm

Dear submitter,

as the package srtp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924741: marked as done (RM: nbsphinx0.3 -- RoQA; superseded by nbsphinx (0.4.2+ds-1))

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:44:08 +
with message-id 
and subject line Bug#924741: Removed package(s) from unstable
has caused the Debian Bug report #924741,
regarding RM: nbsphinx0.3 -- RoQA; superseded by nbsphinx (0.4.2+ds-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.)


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

nbsphinx (0.4.2+ds-1) restored python2 support and builds
python-nbsphinx, again. So this package which was meant to retain an old
version supporting python2 is no longer needed

nbsphinx0.3 | 0.4.1+zero.3.5+ds-1 | source
python-nbsphinx0.3-doc | 0.4.1+zero.3.5+ds-1 | all


Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

nbsphinx0.3 | 0.4.1+zero.3.5+ds-1 | source
python-nbsphinx0.3-doc | 0.4.1+zero.3.5+ds-1 | all

--- Reason ---
RoQA; superseded by nbsphinx (0.4.2+ds-1)
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924741

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924564: marked as done (RM: srtp -- ROM; obsolete and replaced by libsrtp2)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:42:59 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #924564,
regarding RM: srtp -- ROM; obsolete and replaced by libsrtp2
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Hi ftpmasters,

Please drop source package srtp from unstable: It is obsolete and
replaced by libsrtp2, and should no longer have any reverse dependencies
(other than a non-crucial fallback-build-dependency of janus).


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlyKUX8ACgkQLHwxRsGg
ASEnmQ/+O2PKfdLIhqQYrnXwtLrpcmmJc1NIhNi9KXB0CuC6FV9uTHpvUlcERU7h
z2CaGr6yPOiohJUXh9cf4opmT5AolQD9Lwicfn1et4HTauvVB3U5iSrj6mnRC4mF
YwlR4OkSET62MsM+b2vzV1b3eJ6qeCt0fS/C8XImwc6OK4AnOo8Ow9Kt366lbx1r
2jbxjiRvpTsCNRXYSZZ0lrQz90si3crQHZVgmQezwvJNmemrEZ8VNYRdP3LbTYrs
f9QyHaBaOCj7UqqScKBIcywsWv7ZY7Eyq45gObUljQVVol1eJoO0WPgRI+nPN+3e
oylNt3FgWSL8xEerphAUBJwD8AP3jEyPf//QF3sbX0NhhtodBZuJL7GWUI4ETXsh
ZK7F/NhQjDzbwOqSVWROwkNdjavsze+fc9Ero0BglWsFJDTWMmTrNKILliXEB1Ca
49DNiMCvvp7PUe40H/pnPwIafLGrz+2iExmy8dESlK2PZB0Sr1C564+Xo8A4pfw+
NctG2yeunSW3jDaG5wIym6zkuf8AOXqNes5Bnm03uYOvE3h2Ji1yfgts3Tlix/Vs
D2ZeWkj0e9psymJe05nJGAGuub2J+eSThA1vdN0OGoP/q/yJvlXId0Tmy1exMbdh
A+EVXFDWYSNo4emA0A+4hfVPLvg7nBqYSorSL0QXGT+6fZrEiP0=
=NTuS
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  libsrtp0 | 1.4.5~20130609~dfsg-1 | hurd-i386
  libsrtp0 | 1.4.5~20130609~dfsg-2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
libsrtp0-dev | 1.4.5~20130609~dfsg-1 | hurd-i386
libsrtp0-dev | 1.4.5~20130609~dfsg-2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
  srtp | 1.4.5~20130609~dfsg-1 | source
  srtp | 1.4.5~20130609~dfsg-2 | source
 srtp-docs | 1.4.5~20130609~dfsg-1 | all
 srtp-docs | 1.4.5~20130609~dfsg-2 | all
srtp-utils | 1.4.5~20130609~dfsg-1 | hurd-i386
srtp-utils | 1.4.5~20130609~dfsg-2 | amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x

--- Reason ---
ROM; obsolete and replaced by libsrtp2
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924564

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#850677: marked as done (emacs25-common-non-dfsg: The dir file of the info system in /usr/share/info is empty)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:44:40 +
with message-id 
and subject line Bug#924746: Removed package(s) from unstable
has caused the Debian Bug report #850677,
regarding emacs25-common-non-dfsg: The dir file of the info system in 
/usr/share/info is empty
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.)


-- 
850677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-common-non-dfsg
Version: 25.1+1-1
Severity: normal

Dear Maintainer,

   I have upgrade my emacs from v24 to v25. Emacs 24 has a correct dir file
   but emacs25 has an empty one. Everything else seems OK. All info files
   are available and their alternatives are correct. the only problem
   is the content of that 'dir' file.


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

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

Versions of packages emacs25-common-non-dfsg depends on:
ii  dpkg  1.18.18

emacs25-common-non-dfsg recommends no packages.

emacs25-common-non-dfsg suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-1+rm

Dear submitter,

as the package emacs25-non-dfsg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924746

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#863218: marked as done (witty: WChart does not work with this version of libharu)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #863218,
regarding witty: WChart does not work with this version of libharu
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.)


-- 
863218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: witty: WChart does not work with this version of libharu
Package: witty
Version: 3.3.6+dfsg-1.1
Severity: important

Dear Maintainer,

Using WChart with the current Debian packages (or just running the Chart
example) does not work, as witty tries to use UTF-8, which our version
of Libharu does not support [0]. Libharu from experimental could work,
but I haven't tested this yet.

Steps to reproduce:
Install witty-examples
cd /usr/lib/Wt/examples/charts
./charts

Open a browser for localhost:8080

Instead of an example with charts, you get an empty page. Stdout shows
(amongst other things) [error] "Wt: fatal error: WPdfImage error:
error_no=102B, detail_no=0". Other examples work fine.


[0]: 
https://www.mail-archive.com/search?l=witty-inter...@lists.sourceforge.net=subject:%22%5C%5BWt%5C-interest%5C%5D+WPdfImage+error+102b%22=newest=1
or
http://witty-interest.narkive.com/1FcaBlfE/wt-interest-wpdfimage-error-102b


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

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

Versions of packages witty depends on:
ii  libwt40 3.3.6+dfsg-1.1
ii  libwtdbo40  3.3.6+dfsg-1.1
ii  libwtdbofirebird40  3.3.6+dfsg-1.1
ii  libwtdbopostgres40  3.3.6+dfsg-1.1
ii  libwtdbosqlite403.3.6+dfsg-1.1
ii  libwtext40  3.3.6+dfsg-1.1
ii  libwthttp40 3.3.6+dfsg-1.1
ii  witty-examples  3.3.6+dfsg-1.1

witty recommends no packages.

witty suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924565: marked as done (RM: ruby-compass -- ROM; dead upstream, conceptually replaced by ruby-sass and sassc)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:40 +
with message-id 
and subject line Bug#924565: Removed package(s) from unstable
has caused the Debian Bug report #924565,
regarding RM: ruby-compass -- ROM; dead upstream, conceptually replaced by 
ruby-sass and sassc
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi ftpmasters,

Please drop ruby-compass from unstable.

Project id dead upstream, and its concept is nowagays largely covered by
ruby-sass and sassc (and several other implementations of SASS/SCSS.

 - Jonas


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlyKUbkACgkQLHwxRsGg
ASHK4g/+NtTulSIeBRnJpPJIyq5GhNIFrC0JNNahZRsyWUrz4lKLT63ji9YzOKo9
73+qojduEJg45iZ9tyK2fR7ojPr9WrTtc14qC8SLFs3V92c0gd1s4eBEmsDf5gF+
TOzH3S+scHdY6BmCQLAm4sug07ubCUQIee2SZxWVOfrDl0cVp+FExhcYgjR0HRbh
ihTDXav9C6NIsmaFrL6of1YP0FrU0fxpHUh8x6vaNIQs/nejVGzoRBHfTef0n6zd
1KdOKOGGnn0pHg8XrXUhqGlOyNQuUXV/N0JQnAK910pf/h6KWh/iOlsTdoC9Frh1
lhgyzgPuPyzSjnP16nvip4oyEttOLrPbk2S3fcF/0vaxvFIxyJu7suFYH6g9wPKV
wE+BEcNWz3yusBQF911mms3pMbzT1NOW3G9VPOJiU2v+1bFiJUQlTVHuaJnpXTQ0
3RhgJDGX1eZNxExdKE3le3wFv9mLgLH+tc87cu5OMTn5mtO4xTd+NtSd0uoLK1+z
w6lz5BrTl0ePjTGh6Mekf4tbcPcCu70A5uzxTZqAnBBaRY4uWakCw+XvMJzOFLLh
mAY990pLqyIvnJXcDfjudlaPil7qrhm7+qt23dMOQ3+wgkFDAC8dgm4E5WahvctC
an5f3a3u93ksLD2r5HTRosoWVN2aeghlMjwcsKXgZlb4jQEvQx8=
=vTRv
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

ruby-compass | 1.0.3~dfsg-5 | source, all
ruby-compass-core | 1.0.3~dfsg-5 | all
ruby-compass-import-once | 1.0.5~dfsg-5 | all

--- Reason ---
ROM; dead upstream, conceptually replaced by ruby-sass and sassc
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924565

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#720978: marked as done (libwt-dev: Provide a system-wide cmake config file (file exists, just needs proper installation))

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #720978,
regarding libwt-dev: Provide a system-wide cmake config file (file exists, just 
needs proper installation)
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.)


-- 
720978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwt-dev
Version: 3.3.0-1
Severity: wishlist

Hi Pau!

I'm exploring Wt to do some development and I found that there is no
WtConfig.cmake file present system-wide so CMake can find it.

At the same time, I found that the examples install 
/usr/lib/Wt/cmake/FindWt.cmake.

Saving that file as /usr/lib/cmake/WtConfig.cmake is enough to let any CMake
project find Wt and set up the correct variables.

Would it be possible to do this?

Kinds regards, Lisandro.

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
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 libwt-dev depends on:
ii  libboost-date-time-dev   1.49.0.1
ii  libboost-dev 1.49.0.1
ii  libboost-filesystem-dev  1.49.0.1
ii  libboost-regex-dev   1.49.0.1
ii  libboost-signals-dev 1.49.0.1
ii  libboost-thread-dev  1.49.0.1
ii  libfcgi-dev  2.4.0-8.1
ii  libssl-dev   1.0.1e-3
ii  libwt35  3.3.0-1

Versions of packages libwt-dev recommends:
ii  libwthttp-dev  3.3.0-1

libwt-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#778563: marked as done (differing header files)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:45:16 +
with message-id 
and subject line Bug#924770: Removed package(s) from unstable
has caused the Debian Bug report #778563,
regarding differing header files
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.)


-- 
778563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: witty
Version: 3.3.3+dfsg-4.1
User: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on Debian's “reproducible builds” effort [1], we have
noticed that witty doesn't build reproducibly [2].

There is a difference in the header file /usr/include/Wt/WConfig.h.
Depending on the build, some macros are defined or not:

On one build it had the following content:

#define WT_STATIC
#define WTDBO_STATIC
#define WTDBOPOSTGRES_STATIC
#define WTDBOSQLITE3_STATIC
#define WTDBOFIREBIRD_STATIC
#define WTDBOMYSQL_STATIC
#define WTHTTP_STATIC
#define WT_EXT_STATIC
#define WT_EXT_STATIC

While on another build it contained the following lines:

/* #undef WT_STATIC */
/* #undef WTDBO_STATIC */
/* #undef WTDBOPOSTGRES_STATIC */
/* #undef WTDBOSQLITE3_STATIC */
/* #undef WTDBOFIREBIRD_STATIC */
/* #undef WTDBOMYSQL_STATIC */
/* #undef WTHTTP_STATIC */
/* #undef WT_EXT_STATIC */
/* #undef WT_EXT_STATIC */

The build environments differed in user/group, hostname, time,
locale, but the toolchain was the same.  The generated header
should always be identical with the same toolchain.

Regards,
 Reiner


[1]: https://wiki.debian.org/ReproducibleBuilds
[2]: https://reproducible.debian.net/witty




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 3.3.6+dfsg-1.1+rm

Dear submitter,

as the package witty has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924770

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#830926: marked as done (Tests fail when testing installed package)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:42:38 +
with message-id 
and subject line Bug#924558: Removed package(s) from unstable
has caused the Debian Bug report #830926,
regarding Tests fail when testing installed package
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.)


-- 
830926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rails-assets-clipboard
Version: 1.4.2-1
Severity: important
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your package tests fail when testing the installed package:

[..]
  create  tmp/cache/assets
  create  vendor/assets/javascripts
  create  vendor/assets/javascripts/.keep
  create  vendor/assets/stylesheets
  create  vendor/assets/stylesheets/.keep
 run  bundle install --local
Could not find gem 'sqlite3' in any of the gem sources listed in your Gemfile or
available on this machine.
 run  bundle exec spring binstub --all
bundler: command not found: spring
Install missing gem executables with `bundle install`
+ cd foo
+ echo gem 'rails-assets-clipboard'
+ echo //= require clipboard
+ bundle install --local
Could not find gem 'sqlite3' in any of the gem sources listed in your Gemfile or
available on this machine.
adt-run [19:39:04]: test smoke-test: ---]
adt-run [19:39:04]: test smoke-test:  - - - - - - - - - - results - - - - - - - 
- - -
smoke-test   FAIL non-zero exit status 7
adt-run [19:39:04]:  summary
smoke-test   FAIL non-zero exit status 7

See 
https://ci.debian.net/data/packages/unstable/amd64/r/ruby-rails-assets-clipboard/20160710_193632.autopkgtest.log.gz
 for details.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Version: 1.4.2-1+rm

Dear submitter,

as the package ruby-rails-assets-clipboard has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924558

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#890619: marked as done (New upstream version)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:42:38 +
with message-id 
and subject line Bug#924558: Removed package(s) from unstable
has caused the Debian Bug report #890619,
regarding New upstream version
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.)


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

Package: ruby-rails-assets-clipboard
Severity: wishlist

Hi

I'm in the process of preparing webodm for Debian which requires 
libjs-clipbard >= 1.7.1


It would be nice if you could update the package in sid.

Regards
Simon
--- End Message ---
--- Begin Message ---
Version: 1.4.2-1+rm

Dear submitter,

as the package ruby-rails-assets-clipboard has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924558

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#628559: marked as done (srtp: Please do not build documentation package (arch:all) when dpkg-buildpackage -B is invoked)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #628559,
regarding srtp: Please do not build documentation package (arch:all) when 
dpkg-buildpackage -B is invoked
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.)


-- 
628559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: srtp
Version: 1.4.4~dfsg-7
Severity: normal

Please do not unconditionally build documenttion package (arch:all) 
when it is not requested. This would save both machine and human time.

Use case 1) Autobuilders call dpkg-buildpackage -B, no need to waste
their time with dragging and installing useless build-depends 
Use case 2) Developer debugging the code is hardly interested in
pulling and installing useless build-depends, as well as building the
srtp-docs (arch:all) package every now and then.

These should go to Build-Depends-Indep:
doxygen-latex | doxygen, doxygen-latex | texlive-latex-recommended, 
texlive-fonts-recommended

Moving them to -Indep led to the following error:

make[2]: Entering directory /home/deb/debian/srtp-1.4.4~dfsg/doc'
sed 's/LIBSRTPVERSION/1.4.4/' header.template > header.tex
doxygen
make[2]: doxygen: Command not found
make[2]: *** [libsrtpdoc] Error 127
make[2]: Leaving directory /home/deb/debian/srtp-1.4.4~dfsg/doc'
make[1]: *** [libsrtpdoc] Error 2
make[1]: Leaving directory /home/deb/debian/srtp-1.4.4~dfsg'
make: *** [build/srtp-docs] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

It is probably not a good idea to have alternatives listed in build
dependencies, this makes things less reproducible.

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

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


--- End Message ---
--- Begin Message ---
Version: 1.4.5~20130609~dfsg-2+rm

Dear submitter,

as the package srtp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#876608: marked as done (ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:44 +
with message-id 
and subject line Bug#924565: Removed package(s) from unstable
has caused the Debian Bug report #876608,
regarding ruby-compass (build) depends on ruby-sass (< 3.5), but 3.5.1-2 is in 
unstable
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.)


-- 
876608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-compass
Version: 1.0.3~dfsg-5
Severity: serious

ruby-compass depends ond build depends on ruby-sass (< 3.5),
but 3.5.1-2 is in unstable.
--- End Message ---
--- Begin Message ---
Version: 1.0.5~dfsg-5+rm

Dear submitter,

as the package ruby-compass has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924565

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#764778: marked as done (libsrtp0: Symbol conflict with SSL library)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #764778,
regarding libsrtp0: Symbol conflict with SSL library
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.)


-- 
764778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsrtp0
Version: 1.4.5~20130609~dfsg-1
Severity: important
Tags: upstream patch

Hi,

libsrtp defines the following SHA1 functions:

sha1
sha1_init
sha1_update
sha1_final
sha1_core

The first three of these names conflict with symbols exported by polarssl.
This is preventing applications from linking against both libraries, which
for example the current version of Linphone (3.7) needs to do for secure
communication.

Please consider the attached patch which renames the SHA1 functions. This
should not cause a problem for programs using libsrtp because the functions
are only used internally within the library.

Upstream bug: https://github.com/cisco/libsrtp/issues/28
Red Hat bug: https://bugzilla.redhat.com/show_bug.cgi?id=956340

Many thanks,
Si Padmore.

-- System Information:
Debian Release: 7.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Description: Rename sha1 symbols that conflict with polarssl
 The names of the functions defined in crypto/hash/sha1.c conflict with
 some library functions exported by polarssl. This patch renames the
 functions in libsrtp.
 The functions are only used internally in libsrtp so this change should
 not cause a problem for programs using this library.
Author: Si Padmore 
Last-Update: 2014-10-10

--- srtp-1.4.5~20130609~dfsg.orig/crypto/include/sha1.h
+++ srtp-1.4.5~20130609~dfsg/crypto/include/sha1.h
@@ -58,43 +58,43 @@ typedef struct {
 } sha1_ctx_t;
 
 /*
- * sha1(, msg, len, output) hashes the len octets starting at msg
+ * srtp_sha1(, msg, len, output) hashes the len octets starting at msg
  * into the SHA1 context, then writes the result to the 20 octets at
  * output
  * 
  */
 
 void
-sha1(const uint8_t *message,  int octets_in_msg, uint32_t output[5]);
+srtp_sha1(const uint8_t *message,  int octets_in_msg, uint32_t output[5]);
 
 /*
- * sha1_init() initializes the SHA1 context ctx
+ * srtp_sha1_init() initializes the SHA1 context ctx
  * 
- * sha1_update(, msg, len) hashes the len octets starting at msg
+ * srtp_sha1_update(, msg, len) hashes the len octets starting at msg
  * into the SHA1 context
  * 
- * sha1_final(, output) performs the final processing of the SHA1
+ * srtp_sha1_final(, output) performs the final processing of the SHA1
  * context and writes the result to the 20 octets at output
  *
  */
 
 void
-sha1_init(sha1_ctx_t *ctx);
+srtp_sha1_init(sha1_ctx_t *ctx);
 
 void
-sha1_update(sha1_ctx_t *ctx, const uint8_t *M, int octets_in_msg);
+srtp_sha1_update(sha1_ctx_t *ctx, const uint8_t *M, int octets_in_msg);
 
 void
-sha1_final(sha1_ctx_t *ctx, uint32_t output[5]);
+srtp_sha1_final(sha1_ctx_t *ctx, uint32_t output[5]);
 
 /*
- * The sha1_core function is INTERNAL to SHA-1, but it is declared
+ * The srtp_sha1_core function is INTERNAL to SHA-1, but it is declared
  * here because it is also used by the cipher SEAL 3.0 in its key
  * setup algorithm.  
  */
 
 /*
- *  sha1_core(M, H) computes the core sha1 compression function, where M is
+ *  srtp_sha1_core(M, H) computes the core sha1 compression function, where M is
  *  the next part of the message and H is the intermediate state {H0,
  *  H1, ...}
  *
@@ -103,6 +103,6 @@ sha1_final(sha1_ctx_t *ctx, uint32_t out
  */
 
 void
-sha1_core(const uint32_t M[16], uint32_t hash_value[5]);
+srtp_sha1_core(const uint32_t M[16], uint32_t hash_value[5]);
  
 #endif /* SHA1_H */
--- srtp-1.4.5~20130609~dfsg.orig/crypto/hash/hmac.c
+++ srtp-1.4.5~20130609~dfsg/crypto/hash/hmac.c
@@ -137,10 +137,10 @@ hmac_init(hmac_ctx_t *state, const uint8
   debug_print(mod_hmac, "ipad: %s", octet_string_hex_string(ipad, 64));
   
   /* initialize sha1 context */
-  sha1_init(>init_ctx);
+  srtp_sha1_init(>init_ctx);
 
   /* hash ipad ^ key */
-  sha1_update(>init_ctx, ipad, 64);
+  srtp_sha1_update(>init_ctx, ipad, 64);
   memcpy(>ctx, >init_ctx, sizeof(sha1_ctx_t)); 
 
   return err_status_ok;
@@ -161,7 +161,7 @@ hmac_update(hmac_ctx_t *state, const uin
 	  octet_string_hex_string(message, msg_octets));
   
   /* hash message into sha1 context */
-  sha1_update(>ctx, message, msg_octets);
+  srtp_sha1_update(>ctx, message, msg_octets);
 
   return err_status_ok;
 }

Bug#723862: marked as done (srtp build failure on HURD (was: Roll call for porters of architectures in sid and testing))

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #723862,
regarding srtp build failure on HURD (was: Roll call for porters of 
architectures in sid and testing)
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.)


-- 
723862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: srtp
Version: 1.4.5~20130609~dfsg-1


On 20/09/13 17:05, Tzafrir Cohen wrote:
> On Thu, Sep 19, 2013 at 10:41:48PM +0200, Daniel Pocock wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>>
>>
>>
>> I'm particularly keen to see communication packages working on as many
>> architectures as possible because otherwise two-way communications
>> opportunities are missed if some users are excluded.
>>
>> In short, I'm not formally volunteering, but if people have trouble
>> with any VoIP or communications packages on any of the ports, please
>> hassle me, I'll try to help.
>>
>> I'm also very happy to accept feedback and patches from porters when
>> wearing my upstream developer hat, so if people have trouble with any
>> of my packages on ports, please contact me.
> SRTP fails to build on HURD:
> https://buildd.debian.org/status/package.php?p=srtp=sid
>

I noticed that - initially I simply adapted my packages not to support
SRTP on HURD although I did get help from upstream to make it work on
SPARC.  With WebRTC requiring SRTP this probably needs to be fixed though.

Have you looked over the issue already?

The config.h bug in srtp is potentially more annoying

The HURD failure is in a test case
--- End Message ---
--- Begin Message ---
Version: 1.4.5~20130609~dfsg-2+rm

Dear submitter,

as the package srtp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#922091: marked as done (RM: srtp -- ROM; obsolete)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #922091,
regarding RM: srtp -- ROM; obsolete
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi ftpmasters,

Source package srtp is obsolete: It is replaced by libsrtp2.

Please remove srtp from unstable.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxh+HUACgkQLHwxRsGg
ASE3AQ//a3N7mZBt8pN9gIKGjxtatYt651kT3lH27pslUXHGJGlcudSpTVsB+C8Z
MlYINJdQ9dXdD4OJU1j/PEuUD3i1224RsWUIiV2XudmignyO7U7AcG5ESaKaVVQQ
ApBaxMauhY/N3DHZGXer3TRH5m0F0PfVxet5bw6NicFC+9QPK734sI5R4gZPn37d
gST1HyoIItzUK+/YzYG8wTMRvYR454ZLOYudhjKKp3YyU9VFJUFJJEbXqWnY9yLv
Wz27u2mty05lNYQX1T07xdH8vs2VykzGjyuMMfRarnWnMyrjSz3lh8vb+OVuMONE
fYJgUffUWISjbaNUXoSWm9LN568naSSbHR6pqFWyC0f+94JPe0I1gz27SGLpWarb
3TWVjrgJ8p86z5n1u9kuQVC2+eycA6J6er8w9nOi3+XC4vmG43C1pqbsXpQOUr2J
yF002pNtdPGVpmXxcLStOgvMVYV5iDvsqA1Q9eJ0nO8cMbDyhD5YomNqEz/CZQF3
UUqldw+SR2eMMxQyUTEYePmQOgTOA7qe0xFlVBAfjTVHBFff+ZvYGgSDoDEFeq8t
y0uz9GMQn6aJjobkakjYlJr7HtPp0PheBFNRNnRMm3rRyYy15+57BJgXDG0aXkNs
srEytLDYkddzSJ8PPsgIFOmOseTiR3JBLhoup5HGvJGcYBAnOsE=
=GpK+
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 1.4.5~20130609~dfsg-2+rm

Dear submitter,

as the package srtp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924564

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#883093: marked as done (srtp: FTBFS with alternatives to doxygen-latex installed)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:43:10 +
with message-id 
and subject line Bug#924564: Removed package(s) from unstable
has caused the Debian Bug report #883093,
regarding srtp: FTBFS with alternatives to doxygen-latex 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.)


-- 
883093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: srtp
Version: 1.4.5~20130609~dfsg-2
Severity: serious

>From my pbuilder build log, using a partial mirror such that doxygen-latex
was uninstallable but the Build-Depends alternatives doxygen and
texlive-latx-recommended were:

...
touch debian/stamp-makefile-check
[ -f debian/stamp-make-docs ] || /usr/bin/make -C . libsrtpdoc
make[1]: Entering directory '/build/srtp-1.4.5~20130609~dfsg'
/usr/bin/make -C doc
make[2]: Entering directory '/build/srtp-1.4.5~20130609~dfsg/doc'
sed 's/LIBSRTPVERSION/1.4.5/' header.template > header.tex
doxygen -u
warning: Tag `DETAILS_AT_TOP' at line 199 of file `Doxyfile' has become
obsolete.
 This tag has been removed.
warning: Tag `HTML_ALIGN_MEMBERS' at line 523 of file `Doxyfile' has become
obsolete.
 This tag has been removed.
warning: Tag `XML_SCHEMA' at line 745 of file `Doxyfile' has become
obsolete.
 This tag has been removed.
warning: Tag `XML_DTD' at line 751 of file `Doxyfile' has become obsolete.
 This tag has been removed.
warning: Tag `MAX_DOT_GRAPH_WIDTH' at line 978 of file `Doxyfile' has
become obsolete.
 This tag has been removed.
warning: Tag `MAX_DOT_GRAPH_HEIGHT' at line 986 of file `Doxyfile' has
become obsolete.
 This tag has been removed.
warning: Tag `CGI_NAME' at line 1013 of file `Doxyfile' has become obsolete.
 This tag has been removed.
warning: Tag `CGI_URL' at line 1019 of file `Doxyfile' has become obsolete.
 This tag has been removed.
warning: Tag `DOC_URL' at line 1025 of file `Doxyfile' has become obsolete.
 This tag has been removed.
warning: Tag `DOC_ABSPATH' at line 1031 of file `Doxyfile' has become
obsolete.
 This tag has been removed.
warning: Tag `BIN_ABSPATH' at line 1036 of file `Doxyfile' has become
obsolete.
 This tag has been removed.
warning: Tag `EXT_DOC_PATHS' at line 1042 of file `Doxyfile' has become
obsolete.
 This tag has been removed.


Configuration file `Doxyfile' updated.

doxygen
/build/srtp-1.4.5~20130609~dfsg/crypto/include/err.h:146: warning: Compound
debug_module_t is not documented.
/build/srtp-1.4.5~20130609~dfsg/include/srtp.h:735: warning: argument 'p'
of command @param is not found in the argument list of
crypto_policy_set_from_profile_for_rtcp(crypto_policy_t *policy,
srtp_profile_t profile)
/build/srtp-1.4.5~20130609~dfsg/include/srtp.h:756: warning: The following
parameters of crypto_policy_set_from_profile_for_rtcp(crypto_policy_t
*policy, srtp_profile_t profile) are not documented:
  parameter 'policy'
  parameter 'profile'
/build/srtp-1.4.5~20130609~dfsg/include/srtp.h:707: warning: argument 'p'
of command @param is not found in the argument list of
crypto_policy_set_from_profile_for_rtp(crypto_policy_t *policy,
srtp_profile_t profile)
/build/srtp-1.4.5~20130609~dfsg/include/srtp.h:728: warning: The following
parameters of crypto_policy_set_from_profile_for_rtp(crypto_policy_t
*policy, srtp_profile_t profile) are not documented:
  parameter 'policy'
  parameter 'profile'
:3: warning: explicit link request to 'defines' could not be resolved
:3: warning: explicit link request to 'defines' could not be resolved
/build/srtp-1.4.5~20130609~dfsg/crypto/include/crypto_types.h:76: warning:
explicit link request to 'defines' could not be resolved
/build/srtp-1.4.5~20130609~dfsg/crypto/include/crypto_types.h:75: warning:
explicit link request to 'defines' could not be resolved
/build/srtp-1.4.5~20130609~dfsg/crypto/include/crypto_types.h:155: warning:
explicit link request to 'defines' could not be resolved
/build/srtp-1.4.5~20130609~dfsg/crypto/include/crypto_types.h:154: warning:
explicit link request to 'defines' could not be resolved
/build/srtp-1.4.5~20130609~dfsg/crypto/include/err.h:68: warning: Member
err_status_t (enumeration) of group Error is not documented.
/build/srtp-1.4.5~20130609~dfsg/doc/intro.txt:385: warning: Found unknown
command `\t'
/build/srtp-1.4.5~20130609~dfsg/crypto/include/crypto_types.h:76: warning:
explicit link request to 'defines' could not be resolved
/build/srtp-1.4.5~20130609~dfsg/crypto/include/crypto_types.h:155: warning:
explicit link request to 'defines' 

Bug#751876: marked as done (esajpip fails to build on kFreeBSD)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:40:15 +
with message-id 
and subject line Bug#924385: Removed package(s) from unstable
has caused the Debian Bug report #751876,
regarding esajpip fails to build on kFreeBSD
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.)


-- 
751876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: esajpip
Version: 0.1~bzr33-1
Severity: wishlist

On Fri, May 23, 2014 at 10:32 PM, JP  wrote:
>> The build failure are due to the fact that `prctl` is for linux only.
>> It does not work on FreeBSD, so I need to tweak the build system to
>> conditionnally turn PLATFORM_LINUX:
>>
>> https://buildd.debian.org/status/fetch.php?pkg=esajpip=kfreebsd-amd64=0.1~bzr33-1=1400275362
>
> The prctl call is used to ensure that, when the parent process dies,
> the child process dies as well, do you know how this is carried out in
> a non-linux platform? Maybe a more platform-independent solution would
> be the one (second one) indicated here
> http://stackoverflow.com/questions/284325/how-to-make-child-process-die-after-parent-exits.

I think BSD people are using setproctitle() instead. See:
http://avignu.tuxfamily.org/index.php?post/2014/05/27/Quel-est-l-%C3%A9quivalent-de-prctl-()-pour-les-BSD-avec-le-langage-Vala
--- End Message ---
--- Begin Message ---
Version: 0.1~bzr33-4+rm

Dear submitter,

as the package esajpip has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/924385

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924555: marked as done (RM: fis-gtm-6.3-005 -- RoQA; NBS; superseded by fis-gtm-6.3-007)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:41:31 +
with message-id 
and subject line Bug#924555: Removed package(s) from unstable
has caused the Debian Bug report #924555,
regarding RM: fis-gtm-6.3-005 -- RoQA; NBS; superseded by fis-gtm-6.3-007
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.)


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

fis-gtm does not get decrufted automatically due to the dependency of
the arch:all fis-gtm package on the cruft arch:x86 fis-gtm-X.Y-ABC
package.


Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

fis-gtm-6.3-005 |  6.3-005-2 | amd64, i386

--- Reason ---
RoQA; NBS; superseded by fis-gtm-6.3-007
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924555

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924249: marked as done (RM: fusiondirectory-plugin-kolab2 fusiondirectory-plugin-kolab2-schema -- RoQA; NBS; cruft)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:38:39 +
with message-id 
and subject line Bug#924249: Removed package(s) from unstable
has caused the Debian Bug report #924249,
regarding RM: fusiondirectory-plugin-kolab2 
fusiondirectory-plugin-kolab2-schema -- RoQA; NBS; cruft
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.)


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

Hi,

these packages are no longer built by fusiondirectory 1.2.3-2.

anbe@coccia:~$ dak rm -Rn -b fusiondirectory-plugin-kolab2
fusiondirectory-plugin-kolab2-schema
Will remove the following packages from unstable:

fusiondirectory-plugin-kolab2 |   1.0.19-1 | all
fusiondirectory-plugin-kolab2-schema |   1.0.19-1 | all

Maintainer: FusionDirectory packages maintainers group


--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.

Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

fusiondirectory-plugin-kolab2 |   1.0.19-1 | all
fusiondirectory-plugin-kolab2-schema |   1.0.19-1 | all

--- Reason ---
RoQA; NBS; cruft
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924249

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924469: marked as done (RM: python-fabulous-doc python3-fabulous-doc -- ROM; NBS; Leftover package after docs are back in main package)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:40:50 +
with message-id 
and subject line Bug#924469: Removed package(s) from unstable
has caused the Debian Bug report #924469,
regarding RM: python-fabulous-doc python3-fabulous-doc -- ROM; NBS; Leftover 
package after docs are back in main package
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.)


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

Dear ftpmaster

Please remove python-fabulous-doc (0.3.0+dfsg1-2) from unstable, since the docs 
are now shipped along with they python3 only package python3-fabulous.

thanks,

-Jonathan
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-fabulous-doc | 0.3.0+dfsg1-2 | all
python3-fabulous-doc | 0.3.0+dfsg1-4 | all

--- Reason ---
ROM; NBS; Leftover package after docs are back in main package
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924469

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924385: marked as done (RM: esajpip -- ROM; RC buggy, unmaintained)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:40:11 +
with message-id 
and subject line Bug#924385: Removed package(s) from unstable
has caused the Debian Bug report #924385,
regarding RM: esajpip -- ROM; RC buggy, unmaintained
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.)


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

esajpip has FTBFS in the past without any activity from the maintainer
(me) for about a month (#921780). I've actually lost interest in this
package and given that it has a very low popcon, I do not believe it
is of any use for Debian user.

So I think it should be removed from Debian.

Thanks
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   esajpip | 0.1~bzr33-4 | source
   esajpip | 0.1~bzr33-4+b1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
esajpip-doc | 0.1~bzr33-4 | all

--- Reason ---
ROM; RC buggy, unmaintained
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924385

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924141: marked as done (RM: python-flask-api -- RoQA; NBS; only build for python3)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:37:10 +
with message-id 
and subject line Bug#924141: Removed package(s) from unstable
has caused the Debian Bug report #924141,
regarding RM: python-flask-api -- RoQA; NBS; only build for python3
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.)


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

Hi,

please decruft flask-api and remove the no longer built python2 package.


Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-flask-api | 0.6.4+dfsg-1 | all

--- Reason ---
RoQA; NBS; only build for python3
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924141

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924244: marked as done (RM: neutron-fwaas-l3-agent -- RoQA; NBS; obsolete arch:all package)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:37:58 +
with message-id 
and subject line Bug#924244: Removed package(s) from unstable
has caused the Debian Bug report #924244,
regarding RM: neutron-fwaas-l3-agent -- RoQA; NBS; obsolete arch:all package
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.)


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

neutron-fwaas-l3-agent was a transitional package and is no
longer built by src:neutron-fwaas.

anbe@coccia:~$ dak rm -Rn -b neutron-fwaas-l3-agent
Will remove the following packages from unstable:

neutron-fwaas-l3-agent | 1:13.0.1-4 | all

Maintainer: Debian OpenStack 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

neutron-fwaas-l3-agent | 1:13.0.1-4 | all

--- Reason ---
RoQA; NBS; obsolete arch:all package
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924244

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#872469: marked as done (emacs25: use HTML5/XML RELAX NG schema, not XHTML 1.1)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #872469,
regarding emacs25: use HTML5/XML RELAX NG schema, not XHTML 1.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.)


-- 
872469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs24-common
Version: 24.1+1-4

The XHTML RELAX NG schema currently packaged with Emacs 24.1 in
Debian doesn't support XHTML5.  For instance, nXML doesn't seem
to recognize ‘aside’ as a valid element in the example XHTML5
document MIME'd.

I was able to find the schema with XHTML5 support at [1, 2],
and, in order to force nXML use it instead of the one shipped,
created a schemas.xml file (in the directory that holds the
example document) based on the contents of Emacs' own
etc/schema/schemas.xml, with only the following edit:

   
   
-  
+  
+  
   
   

(I've unpacked the schema snapshot [2] into the same directory
as well.)

Unfortunately, this schema uses the following datatype library
declaration [3], which Emacs doesn't seem to support:

datatypes w = "http://whattf.org/datatype-draft;

Thus, I've also had to provide the following “stub” code:

(defun rng-html5-compile (name params)
  "A stub for the http://whattf.org/datatype-draft datatype library."
  '(t identity))

(put (intern "http://whattf.org/datatype-draft;)
 'rng-dt-compile
 'rng-html5-compile)

Finally, it made Emacs recognize the ‘aside’ element introduced
in XHTML5.

Hopefully, someone could implement proper support for [3].
Either way, my suggestion would be to switch to the RELAX NG
XHTML schema that supports XHTML5 [1].

TIA.

[1] http://syntax.whattf.org/
[2] http://bitbucket.org/validator/syntax/get/ed90a83ab0fd.tar.bz2 
[3] http://hsivonen.iki.fi/html5-datatypes/

-- 
FSF associate member #7257  http://sf-day.org/


binnDVsffxttT.bin
Description: application/xhtml
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#876763: marked as done (mishandled tty destroys login shell, emacs inside git-rebase -i &)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #876763,
regarding mishandled tty destroys login shell, emacs inside git-rebase -i &
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.)


-- 
876763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-bin-common, git
Version: 25.1+1-4, 1:2.11.0-3+deb9u1

Steps to reproduce:

 * Install git and emacs on Debian stretch
 * unset DISPLAY
 * export EDITOR=emacs
 * run git-rebase -i something &

Expected behaviour:

 [1]+ Stopped git rebase -i something &

Observed behaviour:

 Terminal window will vanish (or, shell session is unceremoniously
 terminated).

Got a typescript where I straced my interactive shell, by running the
repro inside

  rm -f typescript; script -c 'strace -ot bash'

My shell gets

  read(0, 0x7ffe9df3e58f, 1)  = -1 EIO (Input/output error)

Either git or emacs has obviously done something wrong with the
terminal.

If EDITOR=vi or EDITOR=ed, it works as expected.
OTOH, plain   emacs &   also works as expected.

Thanks for your attention,
Ian.



typescript
Description: transcript from script(1)
execve("/bin/bash", ["bash"], [/* 51 vars */]) = 0
brk(NULL)   = 0x1037000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f019792b000
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=147702, ...}) = 0
mmap(NULL, 147702, PROT_READ, MAP_PRIVATE, 5, 0) = 0x7f0197906000
close(5)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0", O_RDONLY|O_CLOEXEC) = 5
read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\16\0\0\0\0\0\0"..., 
832) = 832
fstat(5, {st_mode=S_IFREG|S_ISUID|0644, st_size=30712, ...}) = 0
mmap(NULL, 2126896, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f0197503000
mprotect(0x7f0197509000, 2097152, PROT_NONE) = 0
mmap(0x7f0197709000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x6000) = 0x7f0197709000
close(5)= 0
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libtinfo.so.5", O_RDONLY|O_CLOEXEC) = 5
read(5, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\315\0\0\0\0\0\0"..., 832) = 
832
fstat(5, {st_mode=S_IFREG|0644, st_size=170776, ...}) = 0
mmap(NULL, 2267936, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f01972d9000
mprotect(0x7f01972fe000, 2097152, PROT_NONE) = 0
mmap(0x7f01974fe000, 20480, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x25000) = 0x7f01974fe000
close(5)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 5
read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\r\0\0\0\0\0\0"..., 
832) = 832
fstat(5, {st_mode=S_IFREG|0644, st_size=14640, ...}) = 0
mmap(NULL, 2109680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f01970d5000
mprotect(0x7f01970d8000, 2093056, PROT_NONE) = 0
mmap(0x7f01972d7000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x2000) = 0x7f01972d7000
close(5)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 5
read(5, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\3\2\0\0\0\0\0"..., 
832) = 832
fstat(5, {st_mode=S_IFREG|0755, st_size=1689360, ...}) = 0
mmap(NULL, 3795360, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f0196d36000
mprotect(0x7f0196ecb000, 2097152, PROT_NONE) = 0
mmap(0x7f01970cb000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x195000) = 0x7f01970cb000
mmap(0x7f01970d1000, 14752, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f01970d1000
close(5)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 5
read(5, 

Bug#873013: marked as done (emacs25-el: ert.el hard-truncates backtrace making debugging hard or impossible)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #873013,
regarding emacs25-el: ert.el hard-truncates backtrace making debugging hard or 
impossible
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.)


-- 
873013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-el
Version: 25.2+1-5
Severity: normal

Hi Rob,

In src:emacs25, L2374 of lisp/emacs-lisp/ert.el trucates the backtrace with
  (setq truncate-lines t)

Would it be possible to either set this to -1, use visual-line-mode instead, or 
make this configurable?  A truncated backtrace makes debugging painful.

Thank you,
Nicholas
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924019: marked as done (RM: libkres9, libkres-dev [arm64] -- ROM; no binaries for src:knot-resolver on arm64)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:36:26 +
with message-id 
and subject line Bug#924019: Removed package(s) from unstable
has caused the Debian Bug report #924019,
regarding RM: libkres9, libkres-dev [arm64] -- ROM; no binaries for 
src:knot-resolver on arm64
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.)


-- 
924019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Control: affects -1 src:knot-resolver libkres9 libkres-dev

NOTE: this is just a request for removal of the libkres9 and libkres-dev
binary packages on arm64.  please do *not* remove the knot-resolver
source package, or the knot-resolver binary package on any architecture!
I believe the libkres9 and libkres-dev packages on other architectures
will be automatically removed because of the successful build of
src:knot-resolver on those platforms.

As noted in #923970, even though the libkres9 itself can function on its
own, libkres-dev isn't functional for building anything, and nothing
builds against libkres-dev besides knot-resolver itself, so
src:knot-resolver (as of 3.2.1-2) drops both of these binary packages
and ships the shared object directly in the knot-resolver binary
package.

As noted in a previous RM bug (#908755), the knot-resolver binary fails
on arm64 because of a bad interaction between that platform and the
package's use of the embedded LUA interpreter.

So src:knot-resolver has nothing to ship on the arm64 platform, which is
why these two binary packages need to be removed on that platform.

Thanks for your work on debian!

Regards,

--dkg


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libkres-dev |3.2.1-1 | arm64
  libkres9 |3.2.1-1 | arm64

--- Reason ---
ROM; no binaries for src:knot-resolver on arm64
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/924019

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#871485: marked as done (emacs25-common: Please remove the DocBook RNC schema as it breaks validation)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #871485,
regarding emacs25-common: Please remove the DocBook RNC schema as it breaks 
validation
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.)


-- 
871485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-common
Version: 25.2+1-5
Severity: normal

emacs25-common contains the DocBook 4.2 schema, which is old. There
are newer 4.x schemas, and now even 5.x, which is largely incompatible
with 4.x. Updating the schema wouldn't be sufficient as several
schemas need to coexist. Such schemas should normally be provided by
separate packages (e.g. docbook-xml for 4.x and docbook5-xml for 5.x).
Only correct location rules need to be added, but this may need
cooperation from the docbook*-xml packages.

Note: This bug is similar to

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

against emacs24-common (initially filed in 2005!!!). The issue is much
more important now that DocBook 5 is available.

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

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

Versions of packages emacs25-common depends on:
ii  emacsen-common  2.0.8
ii  install-info6.4.90.dfsg.1-1+b1

Versions of packages emacs25-common recommends:
ii  emacs25-el  25.2+1-5

Versions of packages emacs25-common suggests:
ii  emacs25-common-non-dfsg  25.2+1-1
ii  ncurses-term 6.0+20170715-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#875678: marked as done (emacs25-common: Lisp error when loading js2-mode)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #875678,
regarding emacs25-common: Lisp error when loading js2-mode
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.)


-- 
875678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-common
Version: 25.2+1-6
Severity: normal
File: /usr/share/emacs/25.2/lisp/progmodes/js.elc

Dear Maintainer,

I'm getting a strange lisp error when opening a desktop session which
contains a JS file. The error message is:

Debugger entered--Lisp error: (void-variable sgml-name-re)
  (concat "\\|/>")
  (defconst js--jsx-end-tag-re (concat "\\|/>") 
("/usr/share/emacs/25.2/lisp/progmodes/js.elc" . 55920))
  require(js)
  
byte-code("\301\302!\210\301\303!\210\301\304!\210\301\305!\210\306\307\"\203de.debian.org
 with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from )
id 1h5zuK-00022V-Hc; Mon, 18 Mar 2019 21:34:56 +
Received: from fasolo.debian.org ([138.16.160.17])
from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP 
CA,CN=fasolo.debian.org,EMAIL=hostmas...@fasolo.debian.org (verified)
by mailly.debian.org with esmtps 
(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from )
id 1h5zuE-0003CJ-KY; Mon, 18 Mar 2019 21:34:50 +
Received: from kitterman by fasolo.debian.org with local (Exim 4.89)
(envelope-from )
id 1h5zuB-000F1w-0V; Mon, 18 Mar 2019 21:34:47 +
From: Debian FTP Masters 
To: 
335052-d...@bugs.debian.org,335712-d...@bugs.debian.org,405684-d...@bugs.debian.org,422236-d...@bugs.debian.org,549485-d...@bugs.debian.org,586223-d...@bugs.debian.org,622870-d...@bugs.debian.org,622872-d...@bugs.debian.org,623233-d...@bugs.debian.org,677365-d...@bugs.debian.org,734325-d...@bugs.debian.org,734417-d...@bugs.debian.org,755051-d...@bugs.debian.org,767111-d...@bugs.debian.org,767121-d...@bugs.debian.org,769188-d...@bugs.debian.org,842880-d...@bugs.debian.org,850263-d...@bugs.debian.org,855212-d...@bugs.debian.org,862050-d...@bugs.debian.org,869674-d...@bugs.debian.org,870459-d...@bugs.debian.org,871485-d...@bugs.debian.org,872469-d...@bugs.debian.org,873013-d...@bugs.debian.org,875678-d...@bugs.debian.org,876763-d...@bugs.debian.org,879021-d...@bugs.debian.org,890299-d...@bugs.debian.org,893175-d...@bugs.debian.org,905767-d...@bugs.debian.org,
X-DAK: dak rm
Cc: emac...@packages.debian.org
X-Filler: 42
X-Debian: DAK
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Subject: Bug#916759: Removed package(s) from unstable
Message-Id: 
Date: Mon, 18 Mar 2019 21:34:47 +
X-CrossAssassin-Score: 26

Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#862050: marked as done (New upstream bugfix release 25.2 available)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #862050,
regarding New upstream bugfix release 25.2 available
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.)


-- 
862050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs25
Version: 25.1+1-4

Emacs 25.2 was released on April 22nd:

[https://lists.gnu.org/archive/html/info-gnu/2017-04/msg9.html]

It would be nice to have it available on unstable.

-d
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#913789: marked as done (RM: leafpad -- RoQA; abandoned upstream, rc-buggy)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:13 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #913765,
regarding RM: leafpad -- RoQA; abandoned upstream, rc-buggy
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.)


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

Package: wnpp
Severity: serious
Tags: O

This needs love or it will die. Needs to be updated to use gtk3, has at 
least one bug that may cause data loss without warning. Is anyone going 
to take this on, or is there a better simple text editor that we should 
all move to and let this one go?
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   leafpad | 0.8.18.1-5 | source, amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x

--- Reason ---
RoQA; abandoned upstream, rc-buggy
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 913...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/913765

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#913765: marked as done (RM: leafpad -- RoQA; abandoned upstream, rc-buggy)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #913789,
regarding RM: leafpad -- RoQA; abandoned upstream, rc-buggy
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.)


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

Package: leafpad

Version: 0.8.18.1

Severity: serious

Tags: O

This needs love or it will die. Needs to be updated to use gtk3, has at 
least one bug that may cause data loss without warning. Is anyone going 
to take this on, or is there a better simple text editor that we should 
all move to and let this one go?
--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#913789: marked as done (RM: leafpad -- RoQA; abandoned upstream, rc-buggy)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #913789,
regarding RM: leafpad -- RoQA; abandoned upstream, rc-buggy
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.)


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

Package: wnpp
Severity: serious
Tags: O

This needs love or it will die. Needs to be updated to use gtk3, has at 
least one bug that may cause data loss without warning. Is anyone going 
to take this on, or is there a better simple text editor that we should 
all move to and let this one go?
--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#905767: marked as done (emacs25: FTBFS due to test failures on arm64 in a binNMU against new version of libmagick)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #905767,
regarding emacs25: FTBFS due to test failures on arm64 in a binNMU against new 
version of libmagick
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.)


-- 
905767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25
Version: 25.2+1-6+b3
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

The latest binNMU of emacs25 on arm64 FTBFS due to the following test failure:

"""
[...]
   passed  35/37  eieio-test-35-named-object
   passed  36/37  eieio-test-36-build-class-alist
Test eieio-test-37-obsolete-name-in-constructor backtrace:
  #[nil "\304\305\306!\307D\310\311\312\216\313 \"\211)\204\31
  ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
  ert-run-test([cl-struct-ert-test eieio-test-37-obsolete-name-in-cons
  ert-run-or-rerun-test([cl-struct-ert--stats (not (tag :expensive-tes
  ert-run-tests((not (tag :expensive-test)) #[385 "\306\307\"\203G\2
  ert-run-tests-batch((not (tag :expensive-test)))
  ert-run-tests-batch-and-exit((not (tag :expensive-test)))
  eval((ert-run-tests-batch-and-exit (quote (not (tag :expensive-test)
  command-line-1(("-L" ":/<>/emacs25-25.2+1/debian/b
  command-line()
  normal-top-level()
Test eieio-test-37-obsolete-name-in-constructor condition:
(ert-test-failed
 ((should
   (equal
(eieio--testing "toto")
'...))
  :form
  (equal
   [eieio-class-tag--eieio--testing]
   ("toto" 2))
  :value nil :explanation
  (different-types
   [eieio-class-tag--eieio--testing]
   ("toto" 2
   FAILED  37/37  eieio-test-37-obsolete-name-in-constructor

Ran 37 tests, 36 results as expected, 1 unexpected (2018-07-18 08:49:03+)

1 unexpected results:
   FAILED  eieio-test-37-obsolete-name-in-constructor

ERROR: eieio-tests.log
"""

Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#870459: marked as done (emacs25-el: org-cycle-agenda-files does not cycle agenda files)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #870459,
regarding emacs25-el: org-cycle-agenda-files does not cycle agenda files
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.)


-- 
870459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-el
Version: 25.1+1-4
Severity: normal
Tags: upstream

Dear Maintainer,

org version 8.2.10 (the one packaged in Stretch's emacs25-el) has a broken 
org-cycle-agenda-files.

# Steps to reproduce:
(setq org-agenda-files '("~/foo.org" "~/bar.org"))

Execute (org-cycle-agenda-files). This will set current buffer to foo.org, as 
expected.
Execute (org-cycle-agenda-files) again.

## Expected behaviour
Current buffer should switch to the next agenda file: bar.org

## Actual behaviour
Current buffer remains on foo.org

# Workarounds

(a) Install the separate 'org-mode' package[0], which does not have this bug
(b) Use the function on https://emacs.stackexchange.com/a/30116/16560 . This 
works for me,
but my emacs-fu isn't strong enough to know whether it's reasonable code.

Regards,
Tom Fitzhenry

0. https://packages.debian.org/stretch/org-mode


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

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

Versions of packages emacs25-el depends on:
ii  emacs25-common  25.1+1-4

emacs25-el recommends no packages.

emacs25-el suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#890908: marked as done (leafpad: Couldn't Register with accessibility bus... error message)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #890908,
regarding leafpad: Couldn't Register with accessibility bus... error 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.)


-- 
890908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leafpad
Version: 0.8.18.1-5
Severity: minor

Dear Maintainer,

snippet from lxterminal:

jon@lin02server:/etc/exim4$ gksudo leafpad passwd.client &
[1] 7983
jon@lin02server:/etc/exim4$ Xlib:  extension "RANDR" missing on display ":1.0".

** (gksudo:7983): WARNING **: Couldn't register with accessibility bus: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.

This error message appears upon exit. Have no idea what it means or how to fix 
it.
It does not appear to effect the edited file; so it is just noise in the 
terminal.

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

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

Versions of packages leafpad depends on:
ii  libc62.24-11+deb9u1
ii  libcairo21.14.8-1
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1

leafpad recommends no packages.

Versions of packages leafpad suggests:
pn  evince-gtk  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#890299: marked as done (emacs25: Various problems with Kannada fonts)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #890299,
regarding emacs25: Various problems with Kannada fonts
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.)


-- 
890299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs25
Version: 25.2+1-6
Severity: normal

Dear Maintainer,

I've had a couple of issues with a couple of Kannada fonts.

The first is Noto Sans Kannada (from fonts-noto-hinted). When I have the font 
installed, it is the default for rendering Kannada characters. However, certain 
characters (such as ಚು and ಕು) rendered in the font cause Emacs to completely 
crash with a segfault (I will add the exact output of the crash in a follow-up 
email).

The second is Gubbi (from fonts-gubbi). This problem is hard to explain to 
someone who doesn't know Kannada, so I will attach pictures in to demonstrate.

At least one font which works perfectly well (as far as I'm aware) is Lohit 
Kannada (from fonts-lohit-knda).

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

Kernel: Linux 4.14.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.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 ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#879021: marked as done (FTBFS: file-notify-test07-backup FAILED)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #879021,
regarding FTBFS: file-notify-test07-backup FAILED
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.)


-- 
879021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs25
Version: 25.2+1-6
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

The latest build of emacs25 for the non-release architectures hppa,
ppc64, sparc64, and x32 failed per the below excerpt from (e.g.)
https://buildd.debian.org/status/fetch.php?pkg=emacs25=hppa=25.2%2B1-6=1505856214=0
The other logs
https://buildd.debian.org/status/fetch.php?pkg=emacs25=ppc64=25.2%2B1-6=1505305017=0
https://buildd.debian.org/status/fetch.php?pkg=emacs25=sparc64=25.2%2B1-6=1507856553=0
https://buildd.debian.org/status/fetch.php?pkg=emacs25=x32=25.2%2B1-6=1505309747=0
exhibit identical symptoms, but I'm including all four links FTR.

Could you please take a look?

Thanks!



Test file-notify-test07-backup backtrace:
  #[0 "\306\307\310C\307C\3111( \312\313\314\315\316$\317\"\32
  ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
  ert-run-test([cl-struct-ert-test file-notify-test07-backup "Check th
  ert-run-or-rerun-test([cl-struct-ert--stats (not (tag :expensive-tes
  ert-run-tests((not (tag :expensive-test)) #[385 "\306\307\"\203G \2
  ert-run-tests-batch((not (tag :expensive-test)))
  ert-run-tests-batch-and-exit((not (tag :expensive-test)))
  eval((ert-run-tests-batch-and-exit (quote (not (tag :expensive-test)
  command-line-1(("-L" ":/<>/emacs25-25.2+1/debian/b
  command-line()
  normal-top-level()
Test file-notify-test07-backup condition:
(ert-test-failed
 ((should
   (file-notify--test-with-events-check events))
  :form
  (file-notify--test-with-events-check
   ((renamed created changed)))
  :value nil :explanation "Received events `(changed)' do not match 
expected events `(renamed created changed)'"))
   FAILED  7/7  file-notify-test07-backup

Ran 7 tests, 6 results as expected, 1 unexpected (2017-09-19 21:17:38+)

1 unexpected results:
   FAILED  file-notify-test07-backup

ERROR: file-notify-tests.log
[...]
SUMMARY OF TEST RESULTS
---
Files examined: 98
Ran 1630 tests, 1575 results as expected, 1 unexpected, 54 skipped
1 files contained unexpected results:
  file-notify-tests.log
Makefile:155: recipe for target 'check-doit' failed
make[4]: *** [check-doit] Error 1

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#913765: marked as done (RM: leafpad -- RoQA; abandoned upstream, rc-buggy)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:13 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #913765,
regarding RM: leafpad -- RoQA; abandoned upstream, rc-buggy
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.)


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

Package: leafpad

Version: 0.8.18.1

Severity: serious

Tags: O

This needs love or it will die. Needs to be updated to use gtk3, has at 
least one bug that may cause data loss without warning. Is anyone going 
to take this on, or is there a better simple text editor that we should 
all move to and let this one go?
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   leafpad | 0.8.18.1-5 | source, amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x

--- Reason ---
RoQA; abandoned upstream, rc-buggy
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 913...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/913765

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#893175: marked as done (EDE: Can't re-open a project after closing and re-opening emacs)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #893175,
regarding EDE: Can't re-open a project after closing and re-opening emacs
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.)


-- 
893175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-common
Version: 25.2+1-6
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

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

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

*** End of the template - remove these template lines ***
You can create and build a project using EDE, and it seems like a useful tool.
However, if you close emacs after creating/building a project, and later try to
go to the directory containing that project with dired (with "(global-ede-mode
t)" im my ~/.emacs), an attempt to open a source file in that directory gives
an error:

> eieio-persistent-validate/fix-slot-value: Corrupt object on disk

Furthermore, trying to build the project (using "C-c . C") gives an error as
well:

> ede-invoke-method: Cannot invoke project-compile-project for hello

("hello" is, of course, the name of the project).

EDE works well when you first build a project, but, unfortunately, you can't
modify it later at this time.



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

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

Versions of packages emacs25-common depends on:
ii  emacsen-common  2.0.8
ii  install-info6.5.0.dfsg.1-2

Versions of packages emacs25-common recommends:
ii  emacs25-el  25.2+1-6

Versions of packages emacs25-common suggests:
ii  emacs25-common-non-dfsg  25.2+1-1
ii  ncurses-term 6.1-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAlqsul0OHHJqbXhAcmpt
eC5uZXQACgkQEvfoZbXi52Gxbg//cfuXmaMF+KSpzQEZ+mu1QxUTDHEwZ1eM8dOk
uT0Y2M84+X4wm9+/f0B+aV+ovgbGJnGPKb+hj+bXUaVu3IA7P+0jIRlRYo4KrS0Y
jDvIYPeYGUmq28t6zgzsSC8CjyZubNzeJiFEeJBLz8g0cCPFZMa4GS/B1aiQJXyc
DYUgLOd9cvqkilqkyWsQtJTTyL6Yp3fiANg4o2RVZVwHLq6W8NDJIigz3V/LcUg0
Hvshso4NM16Fj44/JbcvZUtnFPC+z2UGclUsiHDibfkE/PW+CejTFRmA0YkBXrEC
rVCYy9ZwSxZjafHu5lemDc4igF9BkihcVox6sEnReTG5xzAwVkj9DztK5b6iIMpB
cPm8JUB3LYAU7qbFfcrPSyCv2o+fyNnVJB0/gbfH7M8WS/+cSBTQu6P4yX0KDabk
20/ddmTgO2QDDQGXr4Th0zTToLoVtH7N1O4xJrttgG19E4SVFOsURYEdrtiv4Dtk
7+RZ043IB+ehMbvLt7KS77t4ZDydR69H6k44BHSLsWZsSVaJEYA4vSdBZsOqBAv7
m8H1T7BaAALGNhDV1NmQK8raOAJ8QoQbjv6DXGdZzGVH5z9NPMRdS4aifVO8qXeb
RgyZzRi8czghfY14Q7UTVfAlp0LhnzNJU3qypsES2TBPQg+pNMP99j6B56iniiox
DOxBY54=
=qrg2
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#916759: marked as done (RM: emacs25 -- RoQA; superseded by src:emacs)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:21 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #916759,
regarding RM: emacs25 -- RoQA; superseded by src:emacs
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.)


-- 
916759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs25
Version: 25.2+1-6
Severity: normal

Hi,

src:emacs25 seems to be a cruft package that should be removed from
unstable. If you agree, please reassign this bug to ftp.debian.org

anbe@coccia:~$ dak rm -Rn  emacs25
Will remove the following packages from unstable:

   emacs25 |   25.2+1-2 | source
   emacs25 |   25.2+1-6 | source
emacs25-bin-common |   25.2+1-2 | hurd-i386
emacs25-bin-common | 25.2+1-6+b2 | arm64, kfreebsd-amd64, kfreebsd-i386
emacs25-bin-common | 25.2+1-6+b3 | amd64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
emacs25-common |   25.2+1-2 | all
emacs25-common |   25.2+1-6 | all
emacs25-dbg |   25.2+1-2 | hurd-i386
emacs25-dbg | 25.2+1-6+b2 | arm64, kfreebsd-amd64, kfreebsd-i386
emacs25-dbg | 25.2+1-6+b3 | amd64, armel, armhf, i386, mips, mips64el, mipsel, 
ppc64el, s390x
emacs25-el |   25.2+1-2 | all
emacs25-el |   25.2+1-6 | all
emacs25-lucid-dbg |   25.2+1-2 | hurd-i386
emacs25-lucid-dbg | 25.2+1-6+b2 | arm64, kfreebsd-amd64, kfreebsd-i386
emacs25-lucid-dbg | 25.2+1-6+b3 | amd64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
emacs25-nox-dbg |   25.2+1-2 | hurd-i386
emacs25-nox-dbg | 25.2+1-6+b2 | arm64, kfreebsd-amd64, kfreebsd-i386
emacs25-nox-dbg | 25.2+1-6+b3 | amd64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x

Please take a look at the bugs filed against emacs25-common and 
emacs25-el and reassign them to the corresponding packages from
src:emacs if they are still relevant.
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=emacs25


Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   emacs25 |   25.2+1-2 | source
   emacs25 |   25.2+1-6 | source
emacs25-bin-common |   25.2+1-2 | hurd-i386
emacs25-bin-common | 25.2+1-6+b2 | arm64, kfreebsd-amd64, kfreebsd-i386
emacs25-bin-common | 25.2+1-6+b3 | amd64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
emacs25-common |   25.2+1-2 | all
emacs25-common |   25.2+1-6 | all
emacs25-dbg |   25.2+1-2 | hurd-i386
emacs25-dbg | 25.2+1-6+b2 | arm64, kfreebsd-amd64, kfreebsd-i386
emacs25-dbg | 25.2+1-6+b3 | amd64, armel, armhf, i386, mips, mips64el, mipsel, 
ppc64el, s390x
emacs25-el |   25.2+1-2 | all
emacs25-el |   25.2+1-6 | all
emacs25-lucid-dbg |   25.2+1-2 | hurd-i386
emacs25-lucid-dbg | 25.2+1-6+b2 | arm64, kfreebsd-amd64, kfreebsd-i386
emacs25-lucid-dbg | 25.2+1-6+b3 | amd64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
emacs25-nox-dbg |   25.2+1-2 | hurd-i386
emacs25-nox-dbg | 25.2+1-6+b2 | arm64, kfreebsd-amd64, kfreebsd-i386
emacs25-nox-dbg | 25.2+1-6+b3 | amd64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; superseded by src:emacs
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 916...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/916759

This message was generated automatically; if you believe that there is
a problem with it please contact the archive 

Bug#913838: marked as done (leafpad: find/replace with ß character produces unexpected data loss without error)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #913838,
regarding leafpad: find/replace with ß character produces unexpected data loss 
without error
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.)


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

Package: leafpad
Version: 0.8.18.1-5
Severity: grave

given: Wie heißen Sie?
action: find/replace S with X
want: Wie heißen Xie?
got: Wie heiXen Xie?

given: Wie heißen Sie?
action: find/replace en with XX
want: Wie heißXX Sie?
got: Wie heißeXXSie?

given: Wie heißen Sie?
action: find/replace " " with |
want: Wie|heißen|Sie?
got: Wie|heißen |ie?



-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (100, 'bionic-backports')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-39-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages leafpad depends on:
ii  libc6    2.27-3ubuntu1
ii  libcairo2    1.15.10-2
ii  libglib2.0-0 2.56.3-0ubuntu0.18.04.1
ii  libgtk2.0-0  2.24.32-1ubuntu1
ii  libpango-1.0-0   1.40.14-1ubuntu0.1
ii  libpangocairo-1.0-0  1.40.14-1ubuntu0.1

leafpad recommends no packages.

Versions of packages leafpad suggests:
pn  evince-gtk  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#924494: marked as done (chrony fails to start when seccomp enabled on armel)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:16 +
with message-id 
and subject line Bug#924494: fixed in chrony 3.4-4
has caused the Debian Bug report #924494,
regarding chrony fails to start when seccomp enabled on armel
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.)


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

Dear Maintainer,

chrony on armel does not start due to seccomp not allowing all required
system calls.

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

Kernel: Linux 4.19.0-2-marvell
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages chrony depends on:
ii  adduser  3.118
ii  init-system-helpers  1.56+nmu1
ii  iproute2 4.20.0-2
ii  libc62.28-8
ii  libcap2  1:2.25-2
ii  libedit2 3.1-20181209-1
ii  libnettle6   3.4.1-1
ii  libseccomp2  2.3.3-4
ii  lsb-base 10.2018112800
ii  ucf  3.0038+nmu1

chrony recommends no packages.

Versions of packages chrony suggests:
pn  dnsutils 
pn  networkd-dispatcher  

-- no debconf information
--- chrony-3.4.orig/sys_linux.c
+++ chrony-3.4/sys_linux.c
@@ -504,8 +504,8 @@ SYS_Linux_EnableSystemCallFilter(int lev
 SCMP_SYS(stat64), SCMP_SYS(statfs), SCMP_SYS(statfs64), SCMP_SYS(unlink),
 /* Socket */
 SCMP_SYS(bind), SCMP_SYS(connect), SCMP_SYS(getsockname), 
SCMP_SYS(getsockopt),
-SCMP_SYS(recvfrom), SCMP_SYS(recvmmsg), SCMP_SYS(recvmsg),
+SCMP_SYS(recvfrom), SCMP_SYS(recvmmsg), SCMP_SYS(recvmsg),SCMP_SYS(recv),
-SCMP_SYS(sendmmsg), SCMP_SYS(sendmsg), SCMP_SYS(sendto),
+SCMP_SYS(sendmmsg), SCMP_SYS(sendmsg), SCMP_SYS(sendto),SCMP_SYS(send),
 /* TODO: check socketcall arguments */
 SCMP_SYS(socketcall),
 /* General I/O */
--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 3.4-4

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

Debian distribution maintenance software
pp.
Vincent Blut  (supplier of updated chrony 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, 18 Mar 2019 19:35:34 +0100
Source: chrony
Architecture: source
Version: 3.4-4
Distribution: unstable
Urgency: medium
Maintainer: Vincent Blut 
Changed-By: Vincent Blut 
Closes: 924494
Changes:
 chrony (3.4-4) unstable; urgency=medium
 .
   * debian/patches/*:
 - Add allow-further-syscalls-in-seccomp-filter.patch. Supplementing the
 seccomp filter whitelist with those syscalls is a prerequisite, notably for
 the arm64 architecture.
 .
   [ Leigh Brown ]
   * debian/patches/*:
 - Add allow-recv-send-in-seccomp-filter.patch. Necessary on armel and
 ppc64el. Other architectures might also be affected. (Closes: #924494)
Checksums-Sha1:
 bf188d39a69cfd27d3136268dc641eeb14965bfd 2156 chrony_3.4-4.dsc
 2eb87d6b655bfb42b45168401b33d6b2d849408e 32212 chrony_3.4-4.debian.tar.xz
Checksums-Sha256:
 5ee6f1736feb2c9081dadd9ac693f4b44941a04b23c206a19ae6802a69b9 2156 
chrony_3.4-4.dsc
 3674e8caa8e02f915a5a401a0b69ceba09284e58b30d65806c50aa508b13e48c 32212 
chrony_3.4-4.debian.tar.xz
Files:
 b9ae2006cba52b998daa66b1490c2891 2156 net optional chrony_3.4-4.dsc
 601cb088c18060ce403702be0eb53edd 32212 net optional chrony_3.4-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlyP/6kACgkQnFyZ6wW9
dQoSuAf+I8FUWpaI9nYr6aozEgYStQXgjjS/EyHHVc1f9CBV+d5aVhhMcVnTSGH+
OBq6Jgu8kGP2/Rke5OctkvpIpymynmg8saqiV4Nep1dEQwQulcPiFP0NZN4m4CWZ
tw8glaR+T/oaivAn9eXcLtpsp73TSW7Ur4mdK6u8m4VkAXmbblZwA145nqgfH09q
9tHgdQ1oV9cJ1b2iOcqDCMdhw6vyIwR38sk76ypMQeubKvOz94hrbKTifwy61H8o
CbOo9sfGq99utmbCX7KUHNTZZZ6E7iHDuNKyaBWu/YeO2REv9XavH27flcnw2fAK
WMJX5bJup5ud3WpCS5GtswcQA5xP4A==

Bug#890416: marked as done (Leafpad over ssh erases file content upon saving)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #890416,
regarding Leafpad over ssh erases file content upon saving
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.)


-- 
890416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leafpad
Version: 0.8.18.1-5
Severity: important

Dear Maintainer,

I am using Leafpad to view / edit files on remote computers. If I log in
via a terminal using ssh -X [...], I observe no issue with the the program.
However, when logging in using "Caja" file browser for the Mate DE (via ssh
protocol), and editing a file with Leafpad, hitting the save button erases
(!) the file content, leaving me with an empty file. The issue seems to be
Leafpad-specific: I have tried out other text editors with GUI: Vim, Pluma,
and Kate, they do not seem to produce this effect, and also, nothing
irregular happens when using the editor locally. The remote computer hosts
a similarly configured Debian system.

Based on these, I wanted to notify you, although I am not exactly sure how
to exclude completely the possibility that it is a bug in Caja.

Thank you for looking into this.

All the bests,
Árpád


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

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

Versions of packages leafpad depends on:
ii  libc62.25-3
ii  libcairo21.15.8-2
ii  libglib2.0-0 2.54.1-1
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.12-1
ii  libpangocairo-1.0-0  1.40.12-1

leafpad recommends no packages.

Versions of packages leafpad suggests:
pn  evince-gtk  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#855212: marked as done (emacs25-common: nxml-mode regards XML as valid though it contains an invalid character)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #855212,
regarding emacs25-common: nxml-mode regards XML as valid though it contains an 
invalid character
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.)


-- 
855212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-common
Version: 25.1+1-3
Severity: normal

Consider the file generated by:

  printf '\n\f\n'

i.e. a file that contains a ^L character.

nXML regards this file as valid XML, while the ^L character is invalid
in XML 1.0: https://www.w3.org/TR/2006/REC-xml-20060816/#charsets

As a comparison, xmllint complains:

file.xml:2: parser error : PCDATA invalid Char value 12

  
  ^

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

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

Versions of packages emacs25-common depends on:
ii  dpkg1.18.22
ii  emacsen-common  2.0.8
ii  install-info6.3.0.dfsg.1-1+b1

Versions of packages emacs25-common recommends:
ii  emacs25-el  25.1+1-3

Versions of packages emacs25-common suggests:
ii  emacs25-common-non-dfsg  25.1+1-1
ii  ncurses-term 6.0+20161126-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#850263: marked as done (emacs25: incorrect fallback font breaks box drawing with some default fonts such as 6x13 (regression))

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #850263,
regarding emacs25: incorrect fallback font breaks box drawing with some default 
fonts such as 6x13 (regression)
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.)


-- 
850263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs25-common
Version: 25.1+1-3
Severity: important

Font selection in Emacs 25 is incorrect and breaks box drawing.

See attached box-drawing.txt file (excerpt from
),
and PNG screenshots of what I obtain with Emacs 24 (correct) and
Emacs 25 (incorrect). This makes various files unreadable or look
ugly.

This is reproducible with "emacs25 -q", but not "emacs25 -Q" (but
the latter doesn't honor X resources).

FYI, I have in my X resources:

Emacs*font: 6x13

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

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

Versions of packages emacs25-common depends on:
ii  dpkg1.18.18
ii  emacsen-common  2.0.8
ii  install-info6.3.0.dfsg.1-1+b1

Versions of packages emacs25-common recommends:
ii  emacs25-el  25.1+1-3

Versions of packages emacs25-common suggests:
ii  emacs25-common-non-dfsg  25.1+1-1
ii  ncurses-term 6.0+20161126-1

-- no debconf information
Box drawing alignment tests:  █
  ▉
  ╔══╦══╗  ┌──┬──┐  ╭──┬──╮  ╭──┬──╮  ┏━━┳━━┓  ┎┒┏┑   ╷  ╻ ┏┯┓ ┌┰┐▊ ╱╲╱╲╳╳╳
  ║┌─╨─┐║  │╔═╧═╗│  │╒═╪═╕│  │╓─╁─╖│  ┃┌─╂─┐┃  ┗╃╄┙  ╶┼╴╺╋╸┠┼┨ ┝╋┥▋ ╲╱╲╱╳╳╳
  ║│╲ ╱│║  │║   ║│  ││ │ ││  │║ ┃ ║│  ┃│ ╿ │┃  ┍╅╆┓   ╵  ╹ ┗┷┛ └┸┘▌ ╱╲╱╲╳╳╳
  ╠╡ ╳ ╞╣  ├╢   ╟┤  ├┼─┼─┼┤  ├╫─╂─╫┤  ┣┿╾┼╼┿┫  ┕┛┖┚ ┌┄┄┐ ╎ ┏┅┅┓ ┋ ▍ ╲╱╲╱╳╳╳
  ║│╱ ╲│║  │║   ║│  ││ │ ││  │║ ┃ ║│  ┃│ ╽ │┃  ░░▒▒▓▓██ ┊  ┆ ╎ ╏  ┇ ┋ ▎
  ║└─╥─┘║  │╚═╤═╝│  │╘═╪═╛│  │╙─╀─╜│  ┃└─╂─┘┃  ░░▒▒▓▓██ ┊  ┆ ╎ ╏  ┇ ┋ ▏
  ╚══╩══╝  └──┴──┘  ╰──┴──╯  ╰──┴──╯  ┗━━┻━━┛  ▗▄▖▛▀▜   └╌╌┘ ╎ ┗╍╍┛ ┋  ▁▂▃▄▅▆▇█
   ▝▀▘▙▄▟
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#869674: marked as done ([src:emacs25] Please include systemd user file)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #869674,
regarding [src:emacs25] Please include systemd user 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.)


-- 
869674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:emacs25
Version: 25.2+1-1
Severity: wishlist

Could you please include from emacs26 the service file: 
http://git.savannah.gnu.org/cgit/emacs.git/tree/etc/emacs.service

And copy it to /usr/lib/systemd/user/emacs25.service ?

It will help to run emacs25 --daemon


Bastien

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#845397: marked as done (Leafpad: mishandling of error cases in the saving function can lead to silent data loss)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #845397,
regarding Leafpad: mishandling of error cases in the saving function can lead 
to silent data loss
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.)


-- 
845397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leafpad
Version: 0.8.18.1-5

X-Debbugs-CC: bladeboy200...@gmail.com
Severity: critical

Some mishandling of error return code in the saving function of
leafpad can lead to data loss.


When a file ($FILE) is saved in leafpad, it calls the functions
file_save_real(file.c:180):
 - The content on the GtkTextBuffer is transformed in a gchar*,
 - Then the file $FILE is opened (file.c:220) in write mode (which
truncate $FILE content)
 - The gchar* is written to $FILE (file.c:226) but not necessary yet flushed
   (on my computer there is an autoflush only if more than 4k of data),
 - Leafpad calls the function gtk_text_buffer_set_modified()
(file.c:232) for the UI layer
 - Then the $FILE is closed (file.c:233) which causes the unflushed
content to be finally written to disk.
 - Sadly the result of that fclose() (file.c:233) is not checked at all.

---

1) first problem, the "truncating side-effect"

The call to gtk_text_buffer_set_modified() (file.c:232) triggers a
"modified-changed" signal.
There is a callback (view.c:354) that links that "modified-changed"
signal to cb_modified_changed.
 -> the function cb_modified_changed(view.c:218) calls (view.c:224)
the function get_file_basename()
  -> the function get_file_basename(file.c:42) calls (file.c:66) the
function check_file_writable()
   -> the function check_file_writable(file.c:31) :
 - calls (file.c:35) the function fopen() on the same $FILE in
APPEND mode to check if it's writable
 - and (file.c:36) that second handle on $FILE is closed

Because in the file_save_real(file.c:180), gtk_text_buffer_set_modified()
is called before the fclose() somehow 2 handles on $FILE exists at the
same time,
the second handle being closed before the first.

On a local filesystem (ext4) it usually behave somehow without errors:
when the file is fclosed any unflushed content is then written on disk.

Here is the strace when trying to save 2 bytes in /tmp/file.txt (an
ext filesystem)

file.c:220:file_save_real()  | open("/tmp/file.txt",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 13
file.c:035:check_file_writable() | open("/tmp/file.txt",
O_WRONLY|O_CREAT|O_APPEND, 0666) = 14
file.c:036:check_file_writable() | close(14)= 0
file.c:233:file_save_real()  | *write(13, "X!", 2)   = 2* 
file.c:233:file_save_real()  | close(13)= 0

Until here it seems fine,
but that can have a dramatic side-effect when used with gvfs over
sftp, a bug happens!
( see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680418
and https://bugs.launchpad.net/ubuntu/+source/leafpad/+bug/708829 )

gfvs+sftp don't like having concurrently 2 file pointers on the same file,
and trying to write data on the oldest, after having closed the
youngest ... fails and the file end up truncated.

After having mounted the sftp://localhost/tmp/file.txt via gvfs, the same strace

file.c:220:file_save_real()  |
open("/run/user/1000/gvfs/sftp:host=localhost,user=me/tmp/file.txt",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 13
file.c:035:check_file_writable() |
open("/run/user/1000/gvfs/sftp:host=localhost,user=me/tmp/file.txt",
O_WRONLY|O_CREAT|O_APPEND, 0666) = 14
file.c:036:check_file_writable() | close(14)= 0
file.c:233:file_save_real()  | *write(13, "X!", 2)   = -1
EOPNOTSUPP (Operation not supported)  *
file.c:233:file_save_real()  | close(13)= 0

Solution proposed:
As previously proposed in 2012 (and by Max Rockatanski
 in 2016) on bug=680418,
the call to fclose() should be done before the call to
gtk_text_buffer_set_modified().

The data should also probably be fflushed and fsynced just after the 
fwrite.

---

2) second problem, the silent (No space left on device)

The result of fclose() (file.c:233) being not checked at all,
if there is not enough space on disk to write data when flushing, the
remaining data is currently silently lost.
For example try creating a ram drive of 4kb:
mkdir -p /tmp/tmpfs4k && mount -o size=4k -t tmpfs none /tmp/tmpfs4k

Then try to write 4097 bytes into /tmp/tmpfs4k/test (with a strace) :

Bug#842880: marked as done (emacs25: Does not enable dynamic modules)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #842880,
regarding emacs25: Does not enable dynamic modules
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.)


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

Dear Maintainer,

Please consider building with the --with-modules flag to enable the dynamic 
module
feature added in 25.1.



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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#767121: marked as done (nxml-mode: non-working indentation after yank)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #767121,
regarding nxml-mode: non-working indentation after yank
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.)


-- 
767121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs24-common
Version: 24.4+1-4
Severity: normal
Forwarded: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18872

Consider the following XML file:

--






--

1. Open it with "emacs -Q".
2. Go to line 6 () and type C-y. One gets:

--





--

where [] is the cursor.

5. Type TAB. This should have put the cursor just below the 'b'
for indentation, but this does nothing.

6. If one types DEL then RET, one doesn't get an indentation either.

7. If one types DEL then RET again, one gets the indentation!

This is a regression. I've reported this bug upstream:

  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18872

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

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

Versions of packages emacs24-common depends on:
ii  dpkg1.17.21
ii  emacsen-common  2.0.8
ii  install-info5.2.0.dfsg.1-5

emacs24-common recommends no packages.

Versions of packages emacs24-common suggests:
ii  emacs24-common-non-dfsg  24.4+1-2
ii  emacs24-el   24.4+1-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#769188: marked as done (nxml-mode: C-c C-i sometimes says "Not in a start-tag")

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #769188,
regarding nxml-mode: C-c C-i sometimes says "Not in a start-tag"
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.)


-- 
769188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs24
Version: 24.4+1-4
Severity: normal
Forwarded: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19024

C-c C-i sometimes gives the error:

  nxml-balanced-close-start-tag: Not in a start-tag

To reproduce, open the following file with "emacs -Q":








Put the cursor at the end of the comment line, then type:

  C-j < b C-c C-i

Note that if the file is saved and reopened between C-j and <,
this bug does not occur.

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

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

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.4+1-4
ii  gconf-service  3.2.6-3
ii  libacl12.2.52-2
ii  libasound2 1.0.28-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-13
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libdbus-1-31.8.8-2
ii  libfontconfig1 2.11.0-6.1
ii  libfreetype6   2.5.2-2
ii  libgconf-2-4   3.2.6-3
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libgif44.1.6-11
ii  libglib2.0-0   2.42.0-2
ii  libgnutls-deb0-28  3.3.8-3
ii  libgomp1   4.9.2-1
ii  libgpm21.20.4-6.1
ii  libgtk-3-0 3.14.4-2
ii  libice62:1.0.9-1
ii  libjpeg62-turbo1:1.3.1-10
ii  libm17n-0  1.6.4-3
ii  libmagickcore-6.q16-2  8:6.8.9.9-2
ii  libmagickwand-6.q16-2  8:6.8.9.9-2
ii  libotf00.9.13-2
ii  libpango-1.0-0 1.36.8-2
ii  libpangocairo-1.0-01.36.8-2
ii  libpng12-0 1.2.50-2+b1
ii  librsvg2-2 2.40.5-1
ii  libselinux12.3-2
ii  libsm6 2:1.2.2-1
ii  libtiff5   4.0.3-10+b3
ii  libtinfo5  5.9+20140913-1
ii  libx11-6   2:1.6.2-3
ii  libxft22.3.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.1+dfsg1-3
ii  libxpm41:3.5.11-1
ii  libxrandr2 2:1.4.2-1+b1
ii  libxrender11:0.9.8-1+b1
ii  zlib1g 1:1.2.8.dfsg-2

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
ii  emacs24-common-non-dfsg  24.4+1-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#776027: marked as done (leafpad drops words in printed document)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #776027,
regarding leafpad drops words in printed document
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.)


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

Dear Maintainer,

I have a text file that does not print properly from leafpad. Some words are 
missing.
There's no need to actually print it, it's visible in the Print Preview window 
already.
The file contains non-ascii (Czech) characters.

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I copied the text from 
http://josefstepanek.cz/3220/navod-proclivaci-vymenovaci-posta-praha-120.html 
to leafpad.
Then I printed it.

This worked flawlessly with LibreOffice.

   * What was the outcome of this action?

Incomplete paper document.
E.g. the beginning of paragraph starting with '6.' is missing in the printed 
one.
It looks like each deletion is 56-62 characters long.
There are 5 such deletions in the attached document. 

   * What outcome did you expect instead?

Complete document



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

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

Versions of packages leafpad depends on:
ii  libc62.19-13
ii  libcairo21.14.0-2.1
ii  libglib2.0-0 2.42.1-1
ii  libgtk2.0-0  2.24.25-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3

leafpad recommends no packages.

Versions of packages leafpad suggests:
pn  evince-gtk  

-- no debconf information
Mám připraveno. Co dál?

Proclívací (vyměňovací) pošta Praha 120 sídlí na adrese Plzeňská 139/290, Praha 
5-Košíře (mapa »). Nejbližší tramvajová zastávka je Klamovka (nedaleko ní je 
také stejnojmenná autobusová zastávka).

Po:   8:00 – 17:00
Út:   8:00 – 15:30
St:   8:00 – 17:00
Čt:   8:00 – 15:30
Pá:   8:00 – 15:30

Po malém můstku vejdete do budovy, dáte se prosklenými dveřmi vpravo a potom 
opět vpravo – po schodech do 3. patra (které je, bráno relativně, vlastně 
druhé, protože vchod do budovy ústí v prvním).

1. Výdejna – přepážka: Pak se dáte (zavřenými) dveřmi vpravo, předložíte 
papíry, které vám přišly v obálce poštou. Na základě nich vám pracovnice najde 
složku a pošle vás chodbou naproti a vpravo – k celníkům.

2. Celnice – přepážka: Tam je dveří sice několik, ale ty správné (obvykle 
také zavřené) snadno odhalíte díky světelné tabuli. Vejdete dovnitř a vydáte se 
k jedné z přepážek. Chvíli počkáte, než si opíší potřebné údaje. Zeptají se, co 
je obsahem zásilky, požádají o kopii objednávky či fakturu (tam je pro ně 
klíčové uvedení celkové ceny) a o podpis. Vystaví účet za DPH (případně i clo) 
a pošlou vás k pokladně.

3. Celnice – pokladna: Pokladna je naštěstí ve stejné místnosti. Předložíte 
papír, který jste před chvílí obdrželi, zaplatíte a dostanete doklad o 
zaplacení.

4. Celnice – přepážka: S dokladem se vrátíte na přepážku, kde na jeho 
základě dostanete zpátky složku.

5. Výdejna – přepážka: Se složkou a dokladem o zaplacení se vrátíte do 
výdejny. Musíte ještě jednou k přepážce, kde požádají o občanku, podpis a 
vystaví vám fakturu za administrativu (obvykle 99,- Kč za vyhotovení souhrnné 
deklarace). Zaplatíte a pak už vás konečně pošlou k výdeji.

6. Výdejna – výdej: Vezmou si od vás složku, jdou hledat do skladu a za 
chvíli přinesou vytouženou zásilku.--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman 

Bug#734325: marked as done (emacs25-common: cperl mode freeze when editing a regexp)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #734325,
regarding emacs25-common: cperl mode freeze when editing a regexp
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.)


-- 
734325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs24-common
Version: 24.3+1-2
Severity: normal

Open a file in cperl mode containing the following line:

  /(\d{4})(?: +){2}/;

e.g.: "emacs -Q file" then M-x cperl-mode 

Put the cursor over the second opening brace, and type 
several times to delete what is before "{2}". When one types
 at this point:

  /(\d{4})(?:{2}/;
 ^cursor

Emacs freezes. One can type C-g to interrupt.

One can also reproduce the bug by typing: /(\d{4})(?{2
Emacs freezes before the "2" appears.

This bug is also present with Emacs 23.

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

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

Versions of packages emacs24-common depends on:
ii  dpkg1.17.5
ii  emacsen-common  2.0.5
ii  install-info5.2.0.dfsg.1-2

emacs24-common recommends no packages.

Versions of packages emacs24-common suggests:
ii  emacs24-common-non-dfsg  24.3+1-1
ii  emacs24-el   24.3+1-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#677365: marked as done (emacs25-common: in LaTeX mode, font-lock / bracket matching on \url behaves incorrectly)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #677365,
regarding emacs25-common: in LaTeX mode, font-lock / bracket matching on \url 
behaves incorrectly
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.)


-- 
677365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs23-common
Version: 23.4+1-3
Severity: minor

The "%" character is sometimes use in URL's, thus in \url as a real
character, but LaTeX thinks that's beginning a comment: % and the
following characters in the line is colorized as a comment, and }
isn't seen as a closing bracket. Example:

  \url{http://localhost/#foo%20bar}

/usr/share/texlive/texmf-dist/tex/latex/url/url.sty says:

% A form of \verb that allows linebreaks at certain characters or
% combinations of characters, accepts reconfiguration, and can usually
% be used in the argument to another command.  It is intended for email
% addresses, hypertext links, directories/paths, etc., which normally
% have no spaces.  The font may be selected using the \urlstyle command,
% and new url-like commands can be defined using \urldef.
%
% Usage:Conditions:
% \url{ }   If the argument contains any "%" or "^^", or ends with
%   "\", it can't be used in the argument to another command.
%   The argument must not contain unbalanced braces.
% \url|  |  ...where "|" is any character not used in the argument and not
%   "{" or a space.  The same restrictions as above except that the
%   argument may contain unbalanced braces.
[...]

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

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

Versions of packages emacs23-common depends on:
ii  dpkg1.16.4.2
ii  emacsen-common  2.0.3
ii  install-info4.13a.dfsg.1-10

emacs23-common recommends no packages.

Versions of packages emacs23-common suggests:
ii  emacs23-common-non-dfsg  23.4+1-1
ii  emacs23-el   23.4+1-3

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#643013: marked as done (leafpad aborts citing segmentation fault)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #643013,
regarding leafpad aborts citing segmentation fault
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.)


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

Hi all,
 I updated to the new leafpad today. I was checking some
changelogs using leafpad before the update. When I tried the same with
the new version it resulted into a segmentation fault.

$ zcat changelog.gz | leafpad
Segmentation fault

Can somebody look into this. There is no leafpad-dbg hence cannot use
gdb to debug it.

$ aptitude search leafpad
i   leafpad - GTK+ based simple text editor

If a debug build can be provided then would run it in gdb and perhaps
be able to give more info.

Thanx in advance.

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

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

Versions of packages leafpad depends on:
ii  libatk1.0-0 2.0.1-2
ii  libc6   2.13-21
ii  libcairo2   1.10.2-6.1
ii  libfontconfig1  2.8.0-3
ii  libfreetype62.4.6-2
ii  libgdk-pixbuf2.0-0  2.24.0-1
ii  libglib2.0-02.28.6-1
ii  libgtk2.0-0 2.24.6-1
ii  libpango1.0-0   1.28.4-3

leafpad recommends no packages.

Versions of packages leafpad suggests:
pn  evince-gtk  

-- no debconf information

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17


--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#755051: marked as done (emacs25-common: C/l mode: parentheses matching in comment is broken by apostrophe character)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #755051,
regarding emacs25-common: C/l mode: parentheses matching in comment is broken 
by apostrophe character
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.)


-- 
755051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs24-common
Version: 24.3+1-4
Severity: normal

In C/l mode (provided by cc-mode.el), parentheses matching in a
comment is broken by the apostrophe character: open a new file
file.c and type:

/* (it's) */

then put the cursor after the closing parenthesis and type C-M-p.
An error message

  forward-list: Scan error: "Unbalanced parentheses", 9, 1

appears and the cursor isn't moved.

There's no such problem if the apostrophe is removed.

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

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

Versions of packages emacs24-common depends on:
ii  dpkg1.17.10
ii  emacsen-common  2.0.8
ii  install-info5.2.0.dfsg.1-4

emacs24-common recommends no packages.

Versions of packages emacs24-common suggests:
ii  emacs24-common-non-dfsg  24.3+1-1
ii  emacs24-el   24.3+1-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#764059: marked as done (leafpad: Migrate word and line count statistics patch from 0.8.7le)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #764059,
regarding leafpad: Migrate word and line count statistics patch from 0.8.7le
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.)


-- 
764059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leafpad
Version: 0.8.18.1-4
Severity: wishlist

Hi!

A "limited edition" version of Leafpad 0.8.17 was made in 2009. It contained
a patch to display word and line counts. This was never included in the main
versions, however. Can these patches be migrated into the current version of
Leafpad? The version of Leafpad with word and line counts can be found on
the Leafpad website: http://tarot.freeshell.org/leafpad/

Thanks,

Riley Baird
--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#734417: marked as done (nxml-mode: spelling doesn't work in XML comments)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #734417,
regarding nxml-mode: spelling doesn't work in XML comments
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.)


-- 
734417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs24-common
Version: 24.3+1-2
Severity: normal

$ cat sp-test.xml

$ emacs -Q sp-test.xml

which loads the file in nXML mode. If I select "zzz" and do an
ispell-region, a mistake is detected. But if I select the whole
line and do an ispell-region, the mistake isn't detected.

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

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

Versions of packages emacs24-common depends on:
ii  dpkg1.17.5
ii  emacsen-common  2.0.5
ii  install-info5.2.0.dfsg.1-2

emacs24-common recommends no packages.

Versions of packages emacs24-common suggests:
ii  emacs24-common-non-dfsg  24.3+1-1
ii  emacs24-el   24.3+1-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#767111: marked as done (nxml-mode: DTD edition breaks the file structure)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #767111,
regarding nxml-mode: DTD edition breaks the file structure
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.)


-- 
767111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs24-common
Version: 24.4+1-4
Severity: normal
Forwarded: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18871

Consider the following XML file:

--



]>




--

1. Open it with "emacs -Q".
2. Go to line 2 and type C-SPC.
3. Go to line 6 and type C-w to delete the DTD.

The highlighting gets completely wrong. And if I delete the closing
tag  (with C-k) and type C-c C-f, I get the error:

  No matching start-tag

In more complex files, slightly editing the DTD gives the same behavior.

This is a regression. I've reported this bug upstream:

  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18871

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

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

Versions of packages emacs24-common depends on:
ii  dpkg1.17.21
ii  emacsen-common  2.0.8
ii  install-info5.2.0.dfsg.1-5

emacs24-common recommends no packages.

Versions of packages emacs24-common suggests:
ii  emacs24-common-non-dfsg  24.4+1-2
ii  emacs24-el   24.4+1-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#335712: marked as done (Emacs shell-script-mode highlighting (coloring) bugs for pdksh and zsh minor modes)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #335712,
regarding Emacs shell-script-mode highlighting (coloring) bugs for pdksh and 
zsh minor modes
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.)


-- 
335712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=335712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs21-el
Version: 21.4a-3
Severity: minor

Consider the following file

#!/bin/zsh
if [[ x == x ]] then
  echo OK
fi
if [[ x == x ]]; then
  echo OK
fi

opened in Shell-script[zsh] mode. The first "then" is not colored
(but the second one is).

Moreover, in the condition "x == x", the first x is colored (this
is incorrect, IMHO), while the second one isn't (OK).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.4-20051012
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages emacs21-el depends on:
ii  emacs21-common21.4a-3The GNU Emacs editor's shared, arc

emacs21-el recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#623233: marked as done (emacs25-common: use Autoconf mode instead of m4 for acinclude.m4, aclocal.m4 and acsite.m4)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #623233,
regarding emacs25-common: use Autoconf mode instead of m4 for acinclude.m4, 
aclocal.m4 and acsite.m4
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.)


-- 
623233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs23-common
Version: 23.3+1-1
Severity: wishlist

By default, the m4 mode is used for the acinclude.m4, aclocal.m4 and
acsite.m4 files. It would be better to use the more specific Autoconf
mode for these files (like configure.ac).

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

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

Versions of packages emacs23-common depends on:
ii  dpkg  1.16.0.2   Debian package management system
ii  emacsen-common1.4.22 Common facilities for all emacsen
ii  install-info  4.13a.dfsg.1-6 Manage installed documentation in 

emacs23-common recommends no packages.

Versions of packages emacs23-common suggests:
ii  emacs23-common-non-dfsg   23.3+1-1   GNU Emacs shared, architecture ind
ii  emacs23-el23.3+1-1   GNU Emacs LISP (.el) files

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#405684: marked as done (emacs25-common: CPerl mode indentation bug)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #405684,
regarding emacs25-common: CPerl mode indentation bug
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.)


-- 
405684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-snapshot-el
Version: 1:20070101-1
Severity: normal

With the following Perl script loaded in CPerl mode ("emacs -q" then
M-x cperl-mode), when I type [Tab] on the "sub bar" line, this line
is indented instead of remaining at the same place.


#!/usr/bin/env perl

sub foo
  {
  }

sub bar
  {
  }


In fact, the problem appears more often when one types "sub bar", then
[Enter], then "{". One gets:

sub bar
{

instead of

sub bar
  {

-- Package-specific info:
-- Emacs odds and ends:
Loading 00debian-vars...
Loading /etc/emacs/site-start.d/20apel.el (source)...
Loading /etc/emacs-snapshot/site-start.d/35elib-startup.el (source)...
Loading 42hyperlatex...
Loading /etc/emacs/site-start.d/50a2ps.el (source)...
Loading a2ps-print...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /etc/emacs/site-start.d/50cedet-common.el (source)...
Loading /etc/emacs/site-start.d/50coq.el (source)...
Loading /etc/emacs/site-start.d/50cscope.el (source)...
Loading /etc/emacs/site-start.d/50css-mode.el (source)...
Loading /etc/emacs/site-start.d/50cxref-emacs.el (source)...
Loading cxref...
Loading /etc/emacs/site-start.d/50devscripts-el.el (source)...
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
Skipping dictionaries-common setup for emacs-snapshot
Loading /etc/emacs/site-start.d/50dictionary-el.el (source)...
Loading dictionary-init...
Loading /etc/emacs/site-start.d/50dpkg-dev-el.el (source)...
Loading /etc/emacs/site-start.d/50edict-el.el (source)...
Loading /etc/emacs/site-start.d/50eieio.el (source)...
Loading /etc/emacs/site-start.d/50elserv.el (source)...
Loading /etc/emacs/site-start.d/50emacs-goodies-el.el (source)...
Loading /etc/emacs/site-start.d/50emacs-jabber.el (source)...
Loading /etc/emacs/site-start.d/50flim.el (source)...
Loading /etc/emacs/site-start.d/50ftnchek.el (source)...
Loading /etc/emacs/site-start.d/50gettext.el (source)...
Loading /etc/emacs/site-start.d/50gnuplot-mode.el (source)...
Loading /etc/emacs/site-start.d/50gtk-doc-tools.el (source)...
Loading /etc/emacs/site-start.d/50latex-cjk-common.el (source)...
Loading cjk-enc...
Loading /etc/emacs/site-start.d/50muse-el.el (source)...
Loading /usr/share/emacs-snapshot/site-lisp/muse-el/muse-autoloads.el 
(source)...
Loading /etc/emacs/site-start.d/50octave.el (source)...
Loading /etc/emacs/site-start.d/50octave2.1-emacsen.el (source)...
Loading /etc/emacs/site-start.d/50psvn.el (source)...
Loading /etc/emacs/site-start.d/50rnc-mode.el (source)...
Loading /etc/emacs/site-start.d/50vc-svn.el (source)...
Loading /etc/emacs/site-start.d/50yorick-auto.el (source)...
Loading /etc/emacs/site-start.d/51debian-el.el (source)...
Loading /etc/emacs/site-start.d/51planner-el.el (source)...
Loading /usr/share/emacs-snapshot/site-lisp/planner-el/planner-autoloads.el 
(source)...
Loading /etc/emacs-snapshot/site-start.d/60nxml-mode.el (source)...
Loading /usr/share/emacs/site-lisp/nxml-mode/rng-auto.el (source)...
Version is: GNU Emacs 22.0.92.1 (i486-pc-linux-gnu, GTK+ Version 2.8.20)
 of 2007-01-01 on pacem, modified by Debian
System load-path: (/usr/share/emacs-snapshot/site-lisp/rnc-mode 
/usr/share/emacs-snapshot/site-lisp/latex-cjk-common 
/usr/share/emacs-snapshot/site-lisp/gtk-doc-tools 
/usr/share/emacs-snapshot/site-lisp/eieio /usr/share/emacs/site-lisp/eieio/ 
/usr/share/emacs-snapshot/site-lisp/edict-el 
/usr/share/emacs-snapshot/site-lisp/css-mode 
/usr/share/emacs/site-lisp/css-mode /usr/share/emacs-snapshot/site-lisp/coq 
/usr/share/emacs-snapshot/site-lisp/cedet-common 
/usr/share/emacs/site-lisp/cedet-common/ 
/usr/share/emacs-snapshot/site-lisp/a2ps 
/usr/share/emacs-snapshot/site-lisp/elib/ 
/usr/share/emacs-snapshot/site-lisp/nxml-mode 
/usr/share/emacs/site-lisp/nxml-mode 
/usr/share/emacs-snapshot/site-lisp/planner-el 
/usr/share/emacs-snapshot/site-lisp/debian-el 
/usr/share/emacs-snapshot/site-lisp/muse-el/contrib 
/usr/share/emacs-snapshot/site-lisp/muse-el 
/usr/share/emacs-snapshot/site-lisp/flim 
/usr/share/emacs-snapshot/site-lisp/emacs-jabber 
/usr/share/emacs-snapshot/site-lisp/emacs-goodies-el 

Bug#422236: marked as done (emacs25-common: Tar mode should use the ISO8601 format to display the timestamps (or support TIME_STYLE or locales))

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #422236,
regarding emacs25-common: Tar mode should use the ISO8601 format to display the 
timestamps (or support TIME_STYLE or locales)
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.)


-- 
422236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-snapshot
Version: 1:20070302-1
Severity: wishlist

When tar-mode-show-date is set to t (to get the timestamps), the Tar
mode displays them in a non-standard format. It should use the ISO8601
format (this is what GNU tar (version 1.16.1) does). Other formats
(e.g. one corresponding to the locales) could be used via an option;
in particular, the support of the TIME_STYLE environment variable
(see coreutils manual) would be a good idea.

-- Package-specific info:
-- Emacs odds and ends:
Loading 00debian-vars...
Loading /etc/emacs/site-start.d/20apel.el (source)...
Loading /etc/emacs-snapshot/site-start.d/35elib-startup.el (source)...
Loading 42hyperlatex...
Loading /etc/emacs/site-start.d/50a2ps.el (source)...
Loading a2ps-print...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /etc/emacs/site-start.d/50cedet-common.el (source)...
Loading /etc/emacs/site-start.d/50coq.el (source)...
Loading /etc/emacs/site-start.d/50cscope.el (source)...
Loading /etc/emacs/site-start.d/50css-mode.el (source)...
Loading /etc/emacs/site-start.d/50cxref-emacs.el (source)...
Loading cxref...
Loading /etc/emacs/site-start.d/50devscripts-el.el (source)...
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
Skipping dictionaries-common setup for emacs-snapshot
Loading /etc/emacs/site-start.d/50dictionary-el.el (source)...
Loading dictionary-init...
Loading /etc/emacs/site-start.d/50dpkg-dev-el.el (source)...
Loading /etc/emacs/site-start.d/50edict-el.el (source)...
Loading /etc/emacs/site-start.d/50eieio.el (source)...
Loading /etc/emacs/site-start.d/50elserv.el (source)...
Loading /etc/emacs/site-start.d/50emacs-goodies-el.el (source)...
Loading /etc/emacs/site-start.d/50emacs-jabber.el (source)...
Loading /etc/emacs/site-start.d/50flim.el (source)...
Loading /etc/emacs/site-start.d/50ftnchek.el (source)...
Loading /etc/emacs/site-start.d/50gettext.el (source)...
Loading /etc/emacs/site-start.d/50gnuplot-mode.el (source)...
Loading /etc/emacs/site-start.d/50gtk-doc-tools.el (source)...
Loading /etc/emacs/site-start.d/50latex-cjk-common.el (source)...
Loading cjk-enc...
Loading /etc/emacs/site-start.d/50muse-el.el (source)...
Loading /usr/share/emacs-snapshot/site-lisp/muse-el/muse-autoloads.el 
(source)...
Loading /etc/emacs/site-start.d/50octave.el (source)...
Loading /etc/emacs/site-start.d/50octave2.1-emacsen.el (source)...
Loading /etc/emacs/site-start.d/50psvn.el (source)...
Loading /etc/emacs/site-start.d/50rnc-mode.el (source)...
Loading /etc/emacs/site-start.d/50vc-svn.el (source)...
Loading /etc/emacs/site-start.d/50yorick-auto.el (source)...
Loading /etc/emacs/site-start.d/51debian-el.el (source)...
Loading /etc/emacs/site-start.d/51planner-el.el (source)...
Loading /usr/share/emacs-snapshot/site-lisp/planner-el/planner-autoloads.el 
(source)...
Loading /etc/emacs-snapshot/site-start.d/60nxml-mode.el (source)...
Loading /usr/share/emacs/site-lisp/nxml-mode/rng-auto.el (source)...
Version is: GNU Emacs 22.0.95.1 (i486-pc-linux-gnu, GTK+ Version 2.8.20)
 of 2007-03-02 on pacem, modified by Debian
System load-path: (/usr/share/emacs-snapshot/site-lisp/rnc-mode 
/usr/share/emacs-snapshot/site-lisp/latex-cjk-common 
/usr/share/emacs-snapshot/site-lisp/gtk-doc-tools 
/usr/share/emacs-snapshot/site-lisp/eieio /usr/share/emacs/site-lisp/eieio/ 
/usr/share/emacs-snapshot/site-lisp/edict-el 
/usr/share/emacs-snapshot/site-lisp/css-mode 
/usr/share/emacs/site-lisp/css-mode /usr/share/emacs-snapshot/site-lisp/coq 
/usr/share/emacs-snapshot/site-lisp/cedet-common 
/usr/share/emacs/site-lisp/cedet-common/ 
/usr/share/emacs-snapshot/site-lisp/a2ps 
/usr/share/emacs-snapshot/site-lisp/elib/ 
/usr/share/emacs-snapshot/site-lisp/nxml-mode 
/usr/share/emacs/site-lisp/nxml-mode 
/usr/share/emacs-snapshot/site-lisp/planner-el 
/usr/share/emacs-snapshot/site-lisp/debian-el 
/usr/share/emacs-snapshot/site-lisp/muse-el/contrib 
/usr/share/emacs-snapshot/site-lisp/muse-el 
/usr/share/emacs-snapshot/site-lisp/flim 
/usr/share/emacs-snapshot/site-lisp/emacs-jabber 
/usr/share/emacs-snapshot/site-lisp/emacs-goodies-el 

Bug#549485: marked as done (emacs25-common: description of -fn in emacs(1) man page is not up-to-date)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #549485,
regarding emacs25-common: description of -fn in emacs(1) man page is not 
up-to-date
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.)


-- 
549485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs23-common
Version: 23.1+1-4
Severity: normal

The emacs (emacs23) man page says:

  -fn font, --font font
   Set the Emacs window's font to that specified  by  font.
   You   will   find   the   various   X   fonts   in   the
   /usr/lib/X11/fonts directory.  Note that Emacs will only
   accept fixed width fonts.  Under the X11 Release 4 font-
   naming conventions, any font with the value "m"  or  "c"
   in  the eleventh field of the font name is a fixed width
   font.  Furthermore, fonts whose name  are  of  the  form
   widthxheight  are  generally fixed width, as is the font
   fixed.  See xlsfonts(1) for more information.

At least the path /usr/lib/X11/fonts is wrong (according to strace).

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

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages emacs23-common depends on:
ii  dpkg  1.15.4 Debian package management system
ii  emacsen-common1.4.19 Common facilities for all emacsen

emacs23-common recommends no packages.

Versions of packages emacs23-common suggests:
ii  emacs23-common-non-dfsg   23.1+1-1   GNU Emacs shared, architecture ind
ii  emacs23-el23.1+1-4   GNU Emacs LISP (.el) files

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#622872: marked as done (emacs25-common: m4-mode.el highlighting of "dnl foo#bar" is incorrect)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:34:47 +
with message-id 
and subject line Bug#916759: Removed package(s) from unstable
has caused the Debian Bug report #622872,
regarding emacs25-common: m4-mode.el highlighting of "dnl foo#bar" is incorrect
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.)


-- 
622872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs23-el
Version: 23.3+1-1
Severity: minor

On

dnl foo bar
dnl foo#bar
dnl foo bar

the highlighting of "dnl foo#bar" appears differently, which is
incorrect: as dnl takes the precedence over comments (#), the
3 lines should be highlighted in the same way.

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

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

Versions of packages emacs23-el depends on:
ii  emacs23-common23.3+1-1   The GNU Emacs editor's shared, arc

emacs23-el recommends no packages.

emacs23-el suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 25.2+1-6+rm

Dear submitter,

as the package emacs25 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916759

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#592391: marked as done (leafpad: Drag and drop does not open file)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #592391,
regarding leafpad: Drag and drop does not open 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.)


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


When I drag a file from a nautilus window and drop it in leafpad's text view,
the file is not opened, but rather the file's URL is inserted into the text
view. Looking at the source code and based on my recollection of some earlier
version, leafpad should open the dragged file; and that's what I'd expect
anyway.

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

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages leafpad depends on:
ii  libatk1.0-0   1.30.0-1   The ATK accessibility toolkit
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libcairo2 1.8.10-4   The Cairo 2D vector graphics libra
ii  libfontconfig12.8.0-2.1  generic font configuration library
ii  libfreetype6  2.4.0-2FreeType 2 font engine, shared lib
ii  libglib2.0-0  2.24.1-1   The GLib library of C routines
ii  libgtk2.0-0   2.20.1-1   The GTK+ graphical user interface 
ii  libpango1.0-0 1.28.1-1   Layout and rendering of internatio

leafpad recommends no packages.

Versions of packages leafpad suggests:
pn  evince-gtk (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.8.18.1-5+rm

Dear submitter,

as the package leafpad has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/913765

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#563813: marked as done ([PATCH] leafpad: Update old FSF addresses in code)

[Debian Bug Tracking System]

Your message dated Mon, 18 Mar 2019 21:33:26 +
with message-id 
and subject line Bug#913765: Removed package(s) from unstable
has caused the Debian Bug report #563813,
regarding [PATCH] leafpad: Update old FSF addresses in code
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.)


-- 
563813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leafpad
Version: 0.8.17-2
Severity: wishlist


The following patch updates old FSF addresses to URL (recommended by
FSF in latest GPL).

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

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

Versions of packages leafpad depends on:
ii  libatk1.0-0   1.28.0-1   The ATK accessibility toolkit
ii  libc6 2.10.2-2   GNU C Library: Shared libraries
ii  libcairo2 1.8.8-2The Cairo 2D vector graphics libra
ii  libfontconfig12.6.0-4.2  generic font configuration library
ii  libfreetype6  2.3.11-1   FreeType 2 font engine, shared lib
ii  libglib2.0-0  2.22.3-1   The GLib library of C routines
ii  libgtk2.0-0   2.18.3-1   The GTK+ graphical user interface 
ii  libpango1.0-0 1.26.2-1   Layout and rendering of internatio

leafpad recommends no packages.

Versions of packages leafpad suggests:
pn  evince-gtk (no description available)

-- no debconf information
>From 2f432f6b751d97a850262d8247b3753f8cc91aa0 Mon Sep 17 00:00:00 2001
From: Jari Aalto 
Date: Tue, 5 Jan 2010 16:39:37 +0200
Subject: [PATCH] update FSF address

Signed-off-by: Jari Aalto 
---
 src/about.c |3 +--
 src/about.h |3 +--
 src/callback.c  |3 +--
 src/callback.h  |3 +--
 src/dialog.c|3 +--
 src/dialog.h|3 +--
 src/dnd.c   |3 +--
 src/dnd.h   |3 +--
 src/emacs.c |3 +--
 src/emacs.h |3 +--
 src/encoding.c  |3 +--
 src/encoding.h  |3 +--
 src/file.c  |3 +--
 src/file.h  |3 +--
 src/font.c  |3 +--
 src/font.h  |3 +--
 src/gnomeprint.c|3 +--
 src/gnomeprint.h|3 +--
 src/gtkprint.c  |3 +--
 src/gtkprint.h  |3 +--
 src/gtksourceiter.c |5 ++---
 src/gtksourceiter.h |5 ++---
 src/hlight.c|3 +--
 src/hlight.h|3 +--
 src/i18n.h  |3 +--
 src/indent.c|3 +--
 src/indent.h|3 +--
 src/leafpad.h   |3 +--
 src/linenum.c   |3 +--
 src/linenum.h   |3 +--
 src/main.c  |3 +--
 src/menu.c  |3 +--
 src/menu.h  |3 +--
 src/search.c|3 +--
 src/search.h|3 +--
 src/selector.c  |3 +--
 src/selector.h  |3 +--
 src/undo.c  |3 +--
 src/undo.h  |3 +--
 src/utils.c |3 +--
 src/utils.h |3 +--
 src/view.c  |3 +--
 src/view.h  |3 +--
 src/window.c|3 +--
 src/window.h|3 +--
 45 files changed, 47 insertions(+), 92 deletions(-)

diff --git a/src/about.c b/src/about.c
index 90eca8b..7585362 100644
--- a/src/about.c
+++ b/src/about.c
@@ -13,8 +13,7 @@
  *  GNU General Public License for more details.
  *  
  *  You should have received a copy of the GNU General Public License
- *  along with this program; if not, write to the Free Software
- *  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ *  along with this program. If not, see .
  */
 
 #include 
diff --git a/src/about.h b/src/about.h
index 30e0f3e..dfeac55 100644
--- a/src/about.h
+++ b/src/about.h
@@ -13,8 +13,7 @@
  *  GNU General Public License for more details.
  *  
  *  You should have received a copy of the GNU General Public License
- *  along with this program; if not, write to the Free Software
- *  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ *  along with this program. If not, see .
  */
 
 #ifndef _ABOUT_H
diff --git a/src/callback.c b/src/callback.c
index 8ea0104..95c9f5f 100644
--- a/src/callback.c
+++ b/src/callback.c
@@ -13,8 +13,7 @@
  *  GNU General Public License for more details.
  *  
  *  You