Bug#890276: marked as done (RFS: wine/3.0-1~bpo9+1)
Your message dated Tue, 13 Feb 2018 09:15:22 +0100 with message-id <20180213081522.2tvozroydjeir...@angband.pl> and subject line Re: Bug#890276: RFS: wine/3.0-1~bpo9+1 has caused the Debian Bug report #890276, regarding RFS: wine/3.0-1~bpo9+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.) -- 890276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "wine" * Package name: wine Version : 3.0-1~bpo9+1 Upstream Author : see AUTHORS file * URL : winehq.org * License : LGPL-2.1+ Section : otherosfs It builds those binary packages: fonts-wine - Windows API implementation - fonts libwine- Windows API implementation - library libwine-dev - Windows API implementation - development files wine - Windows API implementation - standard suite wine-binfmt - Windows API implementation - binfmt support wine32 - Windows API implementation - 32-bit binary loader wine32-preloader - Windows API implementation - prelinked 32-bit binary loader wine32-tools - Windows API implementation - 32-bit developer tools wine64 - Windows API implementation - 64-bit binary loader wine64-preloader - Windows API implementation - prelinked 64-bit binary loader wine64-tools - Windows API implementation - 64-bit developer tools To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wine Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wine/wine_3.0-1~bpo9+1.dsc or from our git repository, branch stretch-backports commit dc601b2480c66f577d2d38f1ecf1c2017ad0d175 Changes since the last upload: * Rebuild for stretch-backports. * Make versioned dependency on debhelper backports safe. I'm a member of pkg-wine and DM with upload rights for this package. I still need a sponsor this time, because this is the first upload to stretch-backports and therefore has to go through backports-new. My usual sponsor (in bcc) from pkg-wine intended to upload this (http://lists.alioth.debian.org/pipermail/pkg-wine-party/2018-January/007014.html), but has gone mia since. A private mail from a few days ago is also still unanswered, yet (I hope you're well!). Therefore I'm asking here in the hope to speed up things. To build this package you need debhelper and unicode-data from stretch-backports. AFAIK uploading to backports-new requires at least an binary-indep build (not only source). Thanks and greets jre signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Mon, Feb 12, 2018 at 09:49:49PM +0100, Jens Reyer wrote: > * Package name: wine >Version : 3.0-1~bpo9+1 > Changes since the last upload: > > * Rebuild for stretch-backports. > * Make versioned dependency on debhelper backports safe. > > > > I'm a member of pkg-wine and DM with upload rights for this package. I > still need a sponsor this time, because this is the first upload to > stretch-backports and therefore has to go through backports-new. > > My usual sponsor (in bcc) from pkg-wine intended to upload this > (http://lists.alioth.debian.org/pipermail/pkg-wine-party/2018-January/007014.html), > but has gone mia since. A private mail from a few days ago is also > still unanswered, yet (I hope you're well!). Therefore I'm asking here > in the hope to speed up things. > > To build this package you need debhelper and unicode-data from > stretch-backports. AFAIK uploading to backports-new requires at least > an binary-indep build (not only source). For the sake of others who upload a backport-relying-on-backports, the incantation is: sbuild --build-dep-resolver=aptitude -s -d stretch-backports -c stretch-amd64-sbuild wine_3.0-1~bpo9+1.dsc Looks good to me, uploaded. Thanks for the booze! Meow. -- ⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration ⣾⠁⢰⠒⠀⣿⡁ camps is back. What about KL Warschau (operating until 1956)? ⢿⡄⠘⠷⠚⠋⠀ Zgoda? Łambinowice? Most ex-German KLs? If those were "soviet ⠈⠳⣄ puppets", Bereza Kartuska? Sikorski's camps in UK (thanks Brits!)?--- End Message ---
Bug#887426: marked as done (ITP: minidb -- A simple SQLite3-based store for Python objects)
Your message dated Tue, 13 Feb 2018 09:00:11 + with message-id and subject line Bug#887426: fixed in minidb 2.0.2-1 has caused the Debian Bug report #887426, regarding ITP: minidb -- A simple SQLite3-based store for Python objects 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.) -- 887426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: ITP I intend to pacakge minidb as it's a dependency to existing package urlwatch which needs an updrade. Source is available here: https://github.com/thp/minidb Licence: ISC https://github.com/thp/minidb/blob/master/LICENSE The package is currently maintained as a pip (and pip3) install: https://pypi.python.org/pypi/minidb Maxime Werlen --- End Message --- --- Begin Message --- Source: minidb Source-Version: 2.0.2-1 We believe that the bug you reported is fixed in the latest version of minidb, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maxime Werlen (supplier of updated minidb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Feb 2018 06:34:26 +0100 Source: minidb Binary: python3-minidb Architecture: source all Version: 2.0.2-1 Distribution: unstable Urgency: low Maintainer: Maxime Werlen Changed-By: Maxime Werlen Description: python3-minidb - simple SQLite3-based store for Python objects Closes: 887426 Changes: minidb (2.0.2-1) unstable; urgency=low . * Initial release. (Closes: #887426) Checksums-Sha1: 586791089c8db661787be86e0a14de6f954b8d46 1919 minidb_2.0.2-1.dsc 439bbef23bcb6ad477ca0fa9d52f94c7f1060b06 16078 minidb_2.0.2.orig.tar.gz 194554afef45e2f14ebf88412f8fae0600f6754b 1964 minidb_2.0.2-1.debian.tar.xz 32e5e51adac1476a8d1c665934a0eed3d23ca563 6455 minidb_2.0.2-1_amd64.buildinfo e1a2b089c0696bb9d893db652e93a29f0d217a36 14348 python3-minidb_2.0.2-1_all.deb Checksums-Sha256: 744c6b7d31b90b82fd59ffbac9cded0a66a5744757a212a4f1e451fa46ec549f 1919 minidb_2.0.2-1.dsc 40a1992281dbfb63a90616db328c1babc3aabadd8844fdd676369e8df09d3b9f 16078 minidb_2.0.2.orig.tar.gz a4346d07da12ff51c3b54362946daf6acbd2dcec10e714226b389c967ffef39b 1964 minidb_2.0.2-1.debian.tar.xz b322b9694fff576ae2ec35d025e82e4f0693d9e499c1e8bd83949c804c1e7933 6455 minidb_2.0.2-1_amd64.buildinfo b4768d012db6f181511eec7f618dc5a5f2cfae9e2f734f00a6912ebe80c6b3d2 14348 python3-minidb_2.0.2-1_all.deb Files: 2e7787fe7b5c7f89414f8c25c4ac165c 1919 python optional minidb_2.0.2-1.dsc 1aa7b7afa9c51507a595895d162ad12f 16078 python optional minidb_2.0.2.orig.tar.gz 6dfd87a1fa6e090289ef44922afd4496 1964 python optional minidb_2.0.2-1.debian.tar.xz 75a6ceedb615f7b2fa7756eb9b415f6f 6455 python optional minidb_2.0.2-1_amd64.buildinfo 3025e669ebf1946e1ba41f91fcb12fc9 14348 python optional python3-minidb_2.0.2-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAlqCbiQACgkQMRa6Xp/6 aaN8uw/9Gj7wOzrqVm8g4BeT3lvS/3G3M3P0vj4XNNx6PKuCqmpMLUvHl7AloaUN ojb/mOhW4YowICjaPuCQ3443f6L37Zt9rsDRhOvOZDH3O8hI6+yreUh47H0lgJvE bs5IzdGHbplMOFd/3EIX27hra73tVfdzctuQqnzHVIY9CY/qQbz5DOwil7nRl5vu jI3GzmTIzvPzTBoHCl/G1jF9nU5LPhhOuT52BQOtSOGqgybOt2LJj+VTKNTeRUBh erfmI5lJpkQZelLAbfH1ulkt++B3yC6p9dYjTzYsV51RX6X02kTtuKE840Nh2kPC 4hU1VAkUCFEFWhXp4jZQjJcJcnTAu7kNvzvQRq5BFKCqeY60v9G21YIfwFs0r9rg FmNCdzhg1RfIOy/7pQxyOGfJ5m+33+CDxzm5R1FULea0OGPQSo1DFH2s069zR0du /oWN258qU8C8spFbIOvsbH3TP0bf4DCwlK/4MCKEq1/uVl7qmWQliPafoMS63Xqr FCRLLmiRLiNVbGv8PvlkGbnxNAIkpRg3/QxrJTG5AuYi8s6gv4kOXy0hIFIpJSFb GSnw5DYgCgrVv+AOWI4cqeuLZgNlUolkk5H6GTJVM7khno+Q6tkMFAYfw6qryeDv yCwVQfGV2WVc7Ce3WFyjxx9EGEjZpYpDkD7+GSP5lhM6ymgU0bk= =+9jn -END PGP SIGNATURE End Message ---
Bug#890273: marked as done (ITP: python-os-service-types -- lib for consuming OpenStack sevice-types-authority data)
Your message dated Tue, 13 Feb 2018 09:00:12 + with message-id and subject line Bug#890273: fixed in python-os-service-types 1.1.0-1 has caused the Debian Bug report #890273, regarding ITP: python-os-service-types -- lib for consuming OpenStack sevice-types-authority data to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 890273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: python-os-service-types Version : 1.1.0 Upstream Author : OpenStack Foundation * URL : https://github.com/openstack/os-service-types * License : Apache-2.0 Programming Lang: Python Description : lib for consuming OpenStack sevice-types-authority data This package provides a Python library for consuming OpenStack sevice-types-authority data . The OpenStack Service Types Authority contains information about official OpenStack services and their historical service-type aliases. . The data is in JSON and the latest data should always be used. This simple library exists to allow for easy consumption of the data, along with a built-in version of the data to use in case network access is for some reason not possible and local caching of the fetched data. Note: this is a new dependency for openstacksdk, itself needed by many OpenStack API clients. --- End Message --- --- Begin Message --- Source: python-os-service-types Source-Version: 1.1.0-1 We believe that the bug you reported is fixed in the latest version of python-os-service-types, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-os-service-types 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, 12 Feb 2018 21:12:22 +0100 Source: python-os-service-types Binary: python-os-service-types python-os-service-types-doc python3-os-service-types Architecture: source all Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack Changed-By: Thomas Goirand Description: python-os-service-types - lib for consuming OpenStack sevice-types-authority data - Python python-os-service-types-doc - lib for consuming OpenStack sevice-types-authority data - doc python3-os-service-types - lib for consuming OpenStack sevice-types-authority data - Python Closes: 890273 Changes: python-os-service-types (1.1.0-1) unstable; urgency=medium . * Initial release. (Closes: #890273) Checksums-Sha1: e2c3dcf613358e70215f32e2638f8fcde41f45a5 2752 python-os-service-types_1.1.0-1.dsc 538b7dba6b23a0557bc7348382f300bd0d1aa2bc 18120 python-os-service-types_1.1.0.orig.tar.xz 6ec673f17dc1761b5a859713646edf28e5d21d06 2452 python-os-service-types_1.1.0-1.debian.tar.xz 37b4722337b772e82fbdad19406e4e5666b17c69 916100 python-os-service-types-doc_1.1.0-1_all.deb 6a8edc6620f9338f792bdff4af5f67223b326900 8544 python-os-service-types_1.1.0-1_all.deb 5a2ff87b004350cf3b855b00039afb6617cb0eb9 12002 python-os-service-types_1.1.0-1_amd64.buildinfo a0cb29cc2e130098d1e92372683de43e43f5be1e 8632 python3-os-service-types_1.1.0-1_all.deb Checksums-Sha256: e1119dbac1691d637cf24ba340c030476cdc9cd17a1810341b5b8605f47af27b 2752 python-os-service-types_1.1.0-1.dsc b368f28eaa7187e60efb4688f898518106861af69d27f54236e42e552cc1a5b9 18120 python-os-service-types_1.1.0.orig.tar.xz 0e4345c9d80996a0bc0b2c498209ade9455a90ad7f5f0392d6f39c4f5c5c3918 2452 python-os-service-types_1.1.0-1.debian.tar.xz 43d80ee04afcc5724882795bdd0067b9be5b7f664ea6a36ea5262627faf4ef2e 916100 python-os-service-types-doc_1.1.0-1_all.deb e2233b741affb3a34bc4bca89c94293410568b66b3014e468a195e0a9d050801 8544 python-os-service-types_1.1.0-1_all.deb f37e7c7f046df54ddca84fea2a922494a3cdb119281d42d90fc4c11f2b5a99f2 12002 python-os-service-types_1.1.0-1_amd64.buildinfo 4ae4e6b1c38f2da36e5d056d9bf38ce4cd30154f25c2b26ad2ec118794bb7415 8632 python3-os-service-types_1.1.0-1_all.deb Files: 61b43215a544c5f281bb7c1d903535aa 2752 python o
Bug#883315: marked as done (Some minor glitches)
Your message dated Tue, 13 Feb 2018 09:00:11 +
with message-id
and subject line Bug#883315: fixed in live-tasks 0.2
has caused the Debian Bug report #883315,
regarding Some minor glitches
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.)
--
883315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: live-tasks
Severity: normal
Tags: patch
Hi,
the attached patch fixes some minor glitches - not that important, but please
release 0.2 and re-tag.
Thanks Alf
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.3-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index 651f198..50902d5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+live-tasks (0.2) unstable; urgency=medium
+
+ * Adds support for the LXQt desktop environment
+ * Bumped Standards to 4.1.1, no changes needed
+ * Fixed VCS pathes - s/vmdebootstrap/debian-live
+ * Use secure pathes in copyright
+ * Bumped dh and compat to 10
+ * Fixed notation in live tasks, it is LXQt
+ * Fixed year in copyright
+
+ -- Alf Gaida Sat, 02 Dec 2017 10:33:12 +0100
+
live-tasks (0.1) unstable; urgency=medium
* Initial release. (Closes: #835817)
diff --git a/debian/compat b/debian/compat
index ec63514..f599e28 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-9
+10
diff --git a/debian/control b/debian/control
index 187909e..9d3bef6 100644
--- a/debian/control
+++ b/debian/control
@@ -3,10 +3,10 @@ Maintainer: Live Systems Maintainers
Uploaders: Ana Custura
Section: metapackages
Priority: optional
-Build-Depends: debhelper (>= 9)
-Standards-Version: 3.9.8
-Vcs-Browser: https://anonscm.debian.org/cgit/vmdebootstrap/live-tasks.git
-Vcs-Git: https://anonscm.debian.org/git/vmdebootstrap/live-tasks.git
+Build-Depends: debhelper (>= 10)
+Standards-Version: 4.1.1
+Vcs-Browser: https://anonscm.debian.org/cgit/debian-live/live-tasks.git
+Vcs-Git: https://anonscm.debian.org/git/debian-live/live-tasks.git
Package: live-task-base
Architecture: all
@@ -28,9 +28,9 @@ Depends: ${misc:Depends},
Recommends: less,
dkms,
time,
-firmware-linux-free,
+firmware-linux-free,
inetutils-ping,
-netutils,
+netutils,
file,
dbus,
openssh-client,
@@ -330,9 +330,9 @@ Depends: ${misc:Depends},
task-lxqt-desktop
Recommends: live-task-localisation,
live-task-localisation-desktop
-Description: Live environment support for Lxqt
+Description: Live environment support for LXQt
This metapackage installs packages and documentation to support the Debian
- live Lxqt environment.
+ live LXQt environment.
Package: live-task-cinnamon
Architecture: all
diff --git a/debian/copyright b/debian/copyright
index f1ab529..600282d 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,9 +1,9 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: live-tasks
-Source: http://anonscm.debian.org/cgit/debian-live/live-tasks.git
+Source: https://anonscm.debian.org/cgit/debian-live/live-tasks.git
Files: *
-Copyright: 2016 Ana Custura
+Copyright: 2016-2017 Ana Custura
License: BSD-2-clause
License: BSD-2-clause
--- End Message ---
--- Begin Message ---
Source: live-tasks
Source-Version: 0.2
We believe that the bug you reported is fixed in the latest version of
live-tasks, 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 883...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ana Custura (supplier of updated live-tasks 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
Bug#871845: marked as done (cglib: Please update the Uploaders list)
Your message dated Tue, 13 Feb 2018 09:04:33 + with message-id and subject line Bug#871845: fixed in cglib 3.2.6-1 has caused the Debian Bug report #871845, regarding cglib: Please update the 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.) -- 871845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cglib Severity: minor Tags: pending User: nomad...@debian.org Usertags: cleanup As title says. I haven't been involved in the maintenance of this package since several years ago. I intend to keep an eye on this package for the current oldstable and stable release lifecycles. However, it's very unlikely I'll be involved in its current development cycle (buster). I removed myself from uploaders list and prepared a tentative QA upload but I didn't upload it to the archive since the resulting package would be in violation of Debian Policy (§3.3 and §5.6.3). I'd appreciate if somebody else can step in as maintainer. Cheers, Miguel. -- System Information: Debian Release: 8.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=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) -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: cglib Source-Version: 3.2.6-1 We believe that the bug you reported is fixed in the latest version of cglib, 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 871...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated cglib 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, 13 Feb 2018 00:00:32 +0100 Source: cglib Binary: libcglib-java libcglib-nodep-java libcglib-java-doc Architecture: source Version: 3.2.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libcglib-java - Code generation library for Java libcglib-java-doc - Code generation library for Java (documentation) libcglib-nodep-java - Code generation library for Java (without dependencies) Closes: 871845 Changes: cglib (3.2.6-1) unstable; urgency=medium . * Team upload. . [ Miguel Landaeta ] * Remove myself from uploaders list. (Closes: #871845) * Update copyright info. . [ Emmanuel Bourg ] * New upstream release - Depend on libasm-java (>= 6.0) - Refreshed the patches * Standards-Version updated to 4.1.3 * Switch to debhelper level 11 Checksums-Sha1: ea8da9ffe0a3656dae97d68e99310d569794c0d0 2193 cglib_3.2.6-1.dsc a7c211f37ff900f5e220706465d371d5219856d7 110848 cglib_3.2.6.orig.tar.xz 0c249c406c80ef35bab86e65b1a344ba368ac756 6020 cglib_3.2.6-1.debian.tar.xz f13e4d18ab5a06f8dfca63bcfcf538b45f5adbd0 15193 cglib_3.2.6-1_source.buildinfo Checksums-Sha256: 1e1bb11b3af5b823e5ac4152f1eea1a0045299610424c9b2ff4b15d2d1fa7edb 2193 cglib_3.2.6-1.dsc 291e2aeb34ebcbc819a27bbc3141cf1e0a59b580424a4af1101be01759124db0 110848 cglib_3.2.6.orig.tar.xz 780a3ad1c4c584c104073f0265598a2f466b568a105a47c1e33f5a300ed7b50c 6020 cglib_3.2.6-1.debian.tar.xz 7fbeb340f1650f6eb72bb346c1504577f88b7bd85a7fa49f39cd0575ce6c189c 15193 cglib_3.2.6-1_source.buildinfo Files: 3c2a6d79418f3f7e08e1d9470971cb5c 2193 java optional cglib_3.2.6-1.dsc 3270bc641be5504bf1acdf590bc5dea0 110848 java optional cglib_3.2.6.orig.tar.xz 609d76822628d660bf9ff32737009c1c 6020 java optional cglib_3.2.6-1.debian.tar.xz f4190e577bbe50a5d54ad594f420c8c5 15193 java optional cglib_3.2.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlqCHyESHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs4X4QALdFid2R9IKfymEFdvFevfemvaiUk+4C jHDI/4r//s6nYNHne
Bug#887087: marked as done (ftconfig.h:113:26: warning: "__SIZEOF_LONG__4" is not defined, evaluates to 0 [-Wundef])
Your message dated Tue, 13 Feb 2018 09:05:16 + with message-id and subject line Bug#887087: fixed in freetype 2.8.1-2 has caused the Debian Bug report #887087, regarding ftconfig.h:113:26: warning: "__SIZEOF_LONG__4" is not defined, evaluates to 0 [-Wundef] 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.) -- 887087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfreetype6-dev Version: 2.8.1-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I simply updated/full-upgraded and eventually recompiled one of my own projects, which previously produced no compiler errors or warnings (with -Wall -Wextra -Wpedantic on latest g++). * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? The new outcome is that I am spammed by multiple sets of warnings like this: In file included from /usr/include/freetype2/freetype/freetype.h:33:0, from /usr/include/cairo/cairo-ft.h:47, from /usr/include/cairomm-1.0/cairomm/enums.h:23, from /usr/include/cairomm-1.0/cairomm/surface.h:37, from /usr/include/cairomm-1.0/cairomm/context.h:24, from /usr/include/pangomm-1.4/pangomm/context.h:42, from /usr/include/gtkmm-3.0/gtkmm/widget.h:31, from /usr/include/gtkmm-3.0/gtkmm/container.h:28, from /usr/include/gtkmm-3.0/gtkmm/bin.h:27, from /usr/include/gtkmm-3.0/gtkmm/window.h:30, from /usr/include/gtkmm-3.0/gtkmm/dialog.h:29, from /usr/include/gtkmm-3.0/gtkmm/aboutdialog.h:32, from /home/daniel/src/[project]/src/gui/About.hpp:4, from /home/daniel/src/[project]/src/gui.cpp:9: /usr/include/freetype2/freetype/config/ftconfig.h:113:26: warning: "__SIZEOF_LONG__4" is not defined, evaluates to 0 [-Wundef] #define FT_SIZEOF_LONG (__SIZEOF_LONG__4 / FT_CHAR_BIT) ^ /usr/include/freetype2/freetype/config/ftconfig.h:293:5: note: in expansion of macro ‘FT_SIZEOF_LONG’ #if FT_SIZEOF_LONG == __SIZEOF_LONG__ ^~ /usr/include/freetype2/freetype/config/ftconfig.h:113:26: warning: "__SIZEOF_LONG__4" is not defined, evaluates to 0 [-Wundef] #define FT_SIZEOF_LONG (__SIZEOF_LONG__4 / FT_CHAR_BIT) ^ /usr/include/freetype2/freetype/config/ftconfig.h:302:9: note: in expansion of macro ‘FT_SIZEOF_LONG’ #elif ( FT_SIZEOF_LONG == __SIZEOF_LONG__ ) && \ * What outcome did you expect instead? I expected simply to be able to continue compiling my project with no errors or warnings, especially not ones about a macro that looks like it might eventually end up somewhere where its having the wrong value could create security risks. :) Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libfreetype6-dev depends on: ii libc6-dev [libc-dev] 2.26-3 ii libfreetype6 2.8.1-1 ii libpng-dev 1.6.34-1 ii zlib1g-dev [libz-dev] 1:1.2.8.dfsg-5 libfreetype6-dev recommends no packages. libfreetype6-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: freetype Source-Version: 2.8.1-2 We believe that the bug you reported is fixed in the latest version of freetype, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated freetype 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, 1
Bug#890302: marked as done (RFS: libt3widget/0.6.1-1)
Your message dated Tue, 13 Feb 2018 10:32:52 +0100 with message-id <20180213093252.7c4ul7s755wca...@angband.pl> and subject line Re: Bug#890302: RFS: libt3widget/0.6.1-1 has caused the Debian Bug report #890302, regarding RFS: libt3widget/0.6.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.) -- 890302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libt3widget" * Package name: libt3widget Version : 0.6.1-1 Upstream Author : Gertjan Halkes * URL : https://os.ghalkes.nl/t3/libt3widget.html * License : GPLv3 Section : libs It builds those binary packages: libt3widget-dev - Development files for libt3widget libt3widget1 - C++ terminal dialog toolkit To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libt3widget Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libt/libt3widget/libt3widget_0.6.1-1.dsc Changes since the last upload: * New upstream release. The upstream release fixes the broken keybindings for F8 and Shift-F8. Regards, Gertjan Halkes --- End Message --- --- Begin Message --- On Tue, Feb 13, 2018 at 09:36:08AM +0100, Gertjan Halkes wrote: > * Package name: libt3widget > Version : 0.6.1-1 > Changes since the last upload: > > * New upstream release. > > The upstream release fixes the broken keybindings for F8 and Shift-F8. ✓ -- ⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration ⣾⠁⢰⠒⠀⣿⡁ camps is back. What about KL Warschau (operating until 1956)? ⢿⡄⠘⠷⠚⠋⠀ Zgoda? Łambinowice? Most ex-German KLs? If those were "soviet ⠈⠳⣄ puppets", Bereza Kartuska? Sikorski's camps in UK (thanks Brits!)?--- End Message ---
Bug#889270: marked as done (advancecomp: CVE-2018-1056: heap buffer overflow while running advzip)
Your message dated Tue, 13 Feb 2018 09:34:28 + with message-id and subject line Bug#889270: fixed in advancecomp 2.1-1 has caused the Debian Bug report #889270, regarding advancecomp: CVE-2018-1056: heap buffer overflow while running advzip 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.) -- 889270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: advancecomp Version: 2.0-1 Severity: important Tags: security heap buffer overflow running advzip with "-l poc" option Running 'advzip -l poc' with the attached file raises heap buffer overflow which may allow a remote attacker to cause unspecified impact including denial-of-service attack I expected the program to terminate without segfault, but the program crashes as follow june@june:~/temp/report/advzip/00030552$ ../../binary/advancecomp-2.0/advzip -l ./poc = ==9858==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6060effd at pc 0x76e9af7f bp 0x7fffd6c0 sp 0x7fffce70 READ of size 2020 at 0x6060effd thread T0 #0 0x76e9af7e (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x5cf7e) #1 0x55579c2a in zip_entry::load_cent(unsigned char const*, unsigned int&) /home/june/temp/report/binary/advancecomp-2.0/zip.cc:722 #2 0x5557b56f in zip::open() /home/june/temp/report/binary/advancecomp-2.0/zip.cc:867 #3 0x5556e7a6 in list_single(std::__cxx11::basic_string, std::allocator > const&, bool) /home/june/temp/report/binary/advancecomp-2.0/rezip.cc:122 #4 0x5556f8b2 in list_all(int, char**, bool) /home/june/temp/report/binary/advancecomp-2.0/rezip.cc:261 #5 0x5557214c in process(int, char**) /home/june/temp/report/binary/advancecomp-2.0/rezip.cc:613 #6 0x55572446 in main /home/june/temp/report/binary/advancecomp-2.0/rezip.cc:623 #7 0x760082b0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202b0) #8 0x5556daf9 in _start (/home/june/temp/report/binary/advancecomp-2.0/advzip+0x19af9) 0x6060effd is located 0 bytes to the right of 61-byte region [0x6060efc0,0x6060effd) allocated by thread T0 here: #0 0x76effd28 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28) #1 0x55583a4a in data_alloc(unsigned int) /home/june/temp/report/binary/advancecomp-2.0/data.cc:51 #2 0x55573af2 in cent_read(_IO_FILE*, unsigned int, unsigned char*&, unsigned int&) /home/june/temp/report/binary/advancecomp-2.0/zip.cc:113 #3 0x5557b3c5 in zip::open() /home/june/temp/report/binary/advancecomp-2.0/zip.cc:847 #4 0x5556e7a6 in list_single(std::__cxx11::basic_string, std::allocator > const&, bool) /home/june/temp/report/binary/advancecomp-2.0/rezip.cc:122 #5 0x5556f8b2 in list_all(int, char**, bool) /home/june/temp/report/binary/advancecomp-2.0/rezip.cc:261 #6 0x5557214c in process(int, char**) /home/june/temp/report/binary/advancecomp-2.0/rezip.cc:613 #7 0x55572446 in main /home/june/temp/report/binary/advancecomp-2.0/rezip.cc:623 #8 0x760082b0 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202b0) SUMMARY: AddressSanitizer: heap-buffer-overflow (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x5cf7e) Shadow bytes around the buggy address: 0x0c0c7fff9da0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9db0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9dd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9de0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa =>0x0c0c7fff9df0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00[05] 0x0c0c7fff9e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9e10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9e20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9e30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c0c7fff9e40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user:
Bug#882593: marked as done (ITP: texhyphj -- Support for TeX hyphenation patterns in Java)
Your message dated Tue, 13 Feb 2018 10:00:28 + with message-id and subject line Bug#882593: fixed in texhyphj 1.2+dfsg-1 has caused the Debian Bug report #882593, regarding ITP: texhyphj -- Support for TeX hyphenation patterns in Java 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.) -- 882593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Sebastian Humenda * Package name: texhyphj Version : 1.2 Upstream Author : Joel Håkansson * URL : https://github.com/joeha480/texhyphj * License : LGPL-2.1 Programming Lang: Java Description : Support for TeX hyphenation patterns in Java This Java library allows the re-use of hyphenation patterns, as used by LaTeX. . This project continues the work by David Tolpin. Specifically, adding UTF-8 support for pattern files while maintaining the original functionality. It is a dependency of dotify-cli, which I am trying to package. Upstream is alive. --- End Message --- --- Begin Message --- Source: texhyphj Source-Version: 1.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of texhyphj, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Humenda (supplier of updated texhyphj package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 03 Dec 2017 12:23:07 +0100 Source: texhyphj Binary: libtexhyphj-java Architecture: source all Version: 1.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Sebastian Humenda Changed-By: Sebastian Humenda Description: libtexhyphj-java - Support for TeX hyphenation patterns in Java Closes: 882593 Changes: texhyphj (1.2+dfsg-1) unstable; urgency=medium . * Initial release. (Closes: #882593) Checksums-Sha1: b24302540fcd5ae7dec64553f0abf5eada4f8a76 1829 texhyphj_1.2+dfsg-1.dsc 32a2f9f2056e2722f70537cef270557996b60c5e 74748 texhyphj_1.2+dfsg.orig.tar.xz 0579a0496452a766862f027c8303442816e0f0f0 6624 texhyphj_1.2+dfsg-1.debian.tar.xz 8f07493e84dbca67e10c3ee9b6abae12edf17f09 53936 libtexhyphj-java_1.2+dfsg-1_all.deb e8a595398c2a743d75af7918d6a990a01c84f025 11407 texhyphj_1.2+dfsg-1_amd64.buildinfo Checksums-Sha256: e01a79b5495c34af03d443da466eed460c1057b70145f3d450a61467f2a1c765 1829 texhyphj_1.2+dfsg-1.dsc 33e06d40c8c5bce8c3f54f9160dda86be97e2740bde93b41ca979d088b9ba40f 74748 texhyphj_1.2+dfsg.orig.tar.xz f98e38f2b7c4072bf8b701817b505d54a9f0b8a1a59c9e1aabc72cd1c5b4a76c 6624 texhyphj_1.2+dfsg-1.debian.tar.xz fa6c8ec6b4548115c6319c4438a9116b0be097a49d71bd312599c65bfc5a2c83 53936 libtexhyphj-java_1.2+dfsg-1_all.deb d08e294f9b8e78ee8cf0ac8814c66ea2064e01cba8568c3a0164a91817fd0490 11407 texhyphj_1.2+dfsg-1_amd64.buildinfo Files: d5b829f223c9a0c9eda065822bf884ea 1829 java optional texhyphj_1.2+dfsg-1.dsc 1ff880269b0346f763f0b14899380b74 74748 java optional texhyphj_1.2+dfsg.orig.tar.xz 341bb62d045f8662823c34f392c8364a 6624 java optional texhyphj_1.2+dfsg-1.debian.tar.xz bb914f93cdb6acbc9b6725708f7528e4 53936 java optional libtexhyphj-java_1.2+dfsg-1_all.deb 2933f161bc61ee3f317e69de367070f0 11407 java optional texhyphj_1.2+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErr90SPq5RTpFUjkOsKUb9YyRecUFAloj3yAACgkQsKUb9YyR ecXuRhAAld9nC5HPPqGlomEbMRPvLrSVBzkRapZPvs+IsVLz49dl7dgzlFkKJp8k A36SmdlX/7cOtx8sGxQsWNohlnAoXU4PdJK2TqVn5zt4KwTExNbmKapSTcI2c5UC /h0B1WWnORtG1jDKiz+Rh/rdeoOo+RmZc2LdRTyvuFDLddw2OiVhAb6yVjgvDZov 3yLeC/nmgVYRqwxdJz+hGONeEKTASSzVWbu6uxZ6XntE5B25xD/Voh8OgqfOX4e2 eX84DMlhn9CCFNjBYguuB6vbqz5Olc3w5a0JIRIl24ZAXhwf5OuOg3/5Rnh5zRxF Dwf/T9MJGikSPnEghr/hMxp5ZZyFTsbvp/ILEv//+7Ut6Rmln8Dlto9DLRpMrwtu Bg83grgh4kC2ijYPuXmiaLMZcQp/P0byvwKxmkqktjfVRepv5qNbVSluX8Cct8yi A3xudAyxgoadH7NOA1vTphqU5uvYoeRX72k0KpwMYZ3XR5pnnoIsv8CerhpU4pB0 LIS7CaNTRtJCtjoH5IPaGNe0n2Kp/DfbrKe41FhX9GP3rIhZuMuqJSt0ecuO2MGN hJ88Li93JJn3JLYk+sh3aGCgnLR9VKWOHTJ7deRvRSrpNZoMkUUs3m+KB+765eW0 BytB4noTVKNM7VBKyIiXPXIFEbm7b3nCdLjyrpMD3Atjhfw+uKg= =xAaw -END PGP SIGNATURE End Messag
Bug#787150: marked as done (ITP: mediastreamer2 -- Voice and video streaming engine for telephony)
Your message dated Tue, 13 Feb 2018 10:00:27 + with message-id and subject line Bug#787150: fixed in mediastreamer2 1:2.16.1-2 has caused the Debian Bug report #787150, regarding ITP: mediastreamer2 -- Voice and video streaming engine for telephony 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.) -- 787150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Felix Lechner * Package name: mediastreamer2 Version : 2.11.2 Upstream Author : Simon Morlat * URL : http://www.linphone.org/technical-corner/mediastreamer2/downloads * License : GPL-2+, GPL-3+, LGPL-2.1, Apache, BSD-3-clause, BSD-2-clause Programming Lang: C Description : Voice and video streaming engine for telephony Mediastreamer2 is a powerful and lightweight streaming engine specially designed for voice/video telephony applications.The library is part of Linphone. . Like ortp, the library was previously shipped and versioned together with Linphone. The two libraries are being separated. Their versioning will require a new epoch. --- End Message --- --- Begin Message --- Source: mediastreamer2 Source-Version: 1:2.16.1-2 We believe that the bug you reported is fixed in the latest version of mediastreamer2, 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 787...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dr. Tobias Quathamer (supplier of updated mediastreamer2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 18 Nov 2017 12:13:07 +0100 Source: mediastreamer2 Binary: libmediastreamer-base10 libmediastreamer-dev libmediastreamer-voip10 Architecture: source amd64 Version: 1:2.16.1-2 Distribution: experimental Urgency: medium Maintainer: Debian VoIP Team Changed-By: Dr. Tobias Quathamer Description: libmediastreamer-base10 - Voice and video streaming engine for telephony (base) libmediastreamer-dev - Development files for the mediastreamer2 library libmediastreamer-voip10 - Voice and video streaming engine for telephony (voip) Closes: 787150 Changes: mediastreamer2 (1:2.16.1-2) experimental; urgency=medium . * Team upload. * Use DEB_LDFLAGS_MAINT_APPEND instead of DEB_LDFLAGS_APPEND . mediastreamer2 (1:2.16.1-1) experimental; urgency=medium . * Team upload. . [ Felix Lechner ] * Initial release separate from linphone (Closes: #787150) . [ Johannes 'josch' Schauer ] * New upstream version 2.15.1 - Update build dependencies - Switch from autotools to CMake (upstream deprecated autotools) - debian/patches/fix-spelling-errors.patch: fix more spelling mistakes * debian/control: drop *-dbg packages in favour of automatically generated *-dbgsym packages * debian/compat: Bump debhelper compatibility level to 10 * debian/control: bump Standards-Version (no changes required) * debian/rules: Use hardening=+all * Remove debian/libmediastreamer-voip9.lintian-overrides because there is no embedded library anymore * Unify libmediastreamer-base-dev and libmediastreamer-voip-dev into libmediastreamer-dev. linphone is the only user of the package and there is no reason to split them. . [ Dr. Tobias Quathamer ] * New upstream version 2.16.1 - Refresh patches - Add libxml2-dev to Build-Depends - Create the needed gitversion.h file * Use HTTPS URLs * Bump library .so name from 9 to 10 * Remove unneeded script mkdeb.sh * Update Standards-Version to 4.1.1 * Remove unneeded lintian override for source package * Add new library symbols * Add -Wl,--as-needed to DEB_LDFLAGS_APPEND Checksums-Sha1: d7addbd3be2cf9eb39da0ce5e1ccdb68a37efc00 2936 mediastreamer2_2.16.1-2.dsc 095a81fb16479b59056f14f5a68e7ee39850e492 18895219 mediastreamer2_2.16.1.orig.tar.gz 5e9d89963380cdd1251ea23a30f460d2a6ae4331 15768 mediastreamer2_2.16.1-2.debian.tar.xz 5f05eef88406db1b4144fd73b4ce32f0c3724dd7 92840 libmediastreamer-base10-dbgsym_2.16.1-2_amd64.deb 42624a5fd436d213b108af879e54b9b151f24993 39628
Bug#883175: marked as done (ITP: pdbg -- PowerPC FSI Debugger)
Your message dated Tue, 13 Feb 2018 10:00:28 + with message-id and subject line Bug#883175: fixed in pdbg 1.0-1 has caused the Debian Bug report #883175, regarding ITP: pdbg -- PowerPC FSI Debugger 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.) -- 883175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist pdbg is a simple application to allow debugging of the host POWER processors from the BMC. It works in a similar way to JTAG programmers for embedded system development in that it allows you to access GPRs, SPRs and system memory. License: Apache-2.0 Copyright: 2016 International Business Machines Corporation and others. URL: https://github.com/open-power/pdbg pgpiWuuH56JHc.pgp Description: PGP signature pgpci8NUMfSQD.pgp Description: PGP signature --- End Message --- --- Begin Message --- Source: pdbg Source-Version: 1.0-1 We believe that the bug you reported is fixed in the latest version of pdbg, 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 883...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Frédéric Bonnard (supplier of updated pdbg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 Oct 2017 13:55:13 + Source: pdbg Binary: pdbg libpdbg0 Architecture: source ppc64el Version: 1.0-1 Distribution: unstable Urgency: medium Maintainer: Frédéric Bonnard Changed-By: Frédéric Bonnard Description: libpdbg0 - PowerPC FSI Debugger runtime libraries pdbg - PowerPC FSI Debugger Closes: 883175 Changes: pdbg (1.0-1) unstable; urgency=medium . * Initial release. (Closes: #883175) Checksums-Sha1: b5d2245eac5b8d4f5991c27128f618f0bed1f06f 1793 pdbg_1.0-1.dsc 83ae103b3e063b1ce5ddb5fd6c693a19169e1b3a 92799 pdbg_1.0.orig.tar.gz 28adfbbd3073a97ca4b0f798e485e38dff629a1f 8356 pdbg_1.0-1.debian.tar.xz c6ddcccdf383fe2b9dd97d3e0516380a1ddeffa1 71052 libpdbg0-dbgsym_1.0-1_ppc64el.deb f27471729ee6ad67eb1d5958b0316cd5d6e8dde1 28112 libpdbg0_1.0-1_ppc64el.deb 0e1ec9a3f9a4c9a15bdea0c016f6f04234a4849e 22352 pdbg-dbgsym_1.0-1_ppc64el.deb e35c23c64a909db621e2b2f519d1d9130c004bff 7169 pdbg_1.0-1_ppc64el.buildinfo a9edc594c78553afdca67c2864b58a600265572c 17388 pdbg_1.0-1_ppc64el.deb Checksums-Sha256: 0fe8773949df2b68703e12361cf60954636bfb6224c696f7cd8dc5795acd7031 1793 pdbg_1.0-1.dsc 1722ae084058fae83ee83cef2fd6f7dee9743f1dffa569fbfa9f9ec0321f22b7 92799 pdbg_1.0.orig.tar.gz 847768f47f661fd2a75f78d1996abb87456ea21afb291308544a016c03e04988 8356 pdbg_1.0-1.debian.tar.xz f4a389e5a8d9266b578c37c1571fac8789e8e82a11c70e5026de7ff39ddeee04 71052 libpdbg0-dbgsym_1.0-1_ppc64el.deb 8ea265e5db85d0d121d47724126da8a62927bd7b9e94fcf61d549ff43ae89b76 28112 libpdbg0_1.0-1_ppc64el.deb fea0122db59325629584db7e55cb6bc5cd6be85b5b2d5c92312db3c5a3ccd756 22352 pdbg-dbgsym_1.0-1_ppc64el.deb 8e9c8c34e3e555155d41ab9d1a724986d470c28a51a67a12f21726c3db4a5aa9 7169 pdbg_1.0-1_ppc64el.buildinfo ffb459d3ada1ccbd32149ef2ec3ff6733ac2e651f0989c6a55dc93f07b9b47ba 17388 pdbg_1.0-1_ppc64el.deb Files: 8907c598601417c72f95d7bb39149913 1793 misc optional pdbg_1.0-1.dsc aaa2906f108c548b85d60a25e3b55a02 92799 misc optional pdbg_1.0.orig.tar.gz 9cf522fd52694f516120eb5a6fcead54 8356 misc optional pdbg_1.0-1.debian.tar.xz 32b201b478ddd4dcb78512a196072c40 71052 debug optional libpdbg0-dbgsym_1.0-1_ppc64el.deb 27b998b9afbbd74feae37b1dddbf6716 28112 libs optional libpdbg0_1.0-1_ppc64el.deb b7650cc98b0088a4405354d51248dcaa 22352 debug optional pdbg-dbgsym_1.0-1_ppc64el.deb 2e21821fbd6b89651d67da53110397dd 7169 misc optional pdbg_1.0-1_ppc64el.buildinfo d78fbeb5e711d0ac654310bc2dc71d25 17388 misc optional pdbg_1.0-1_ppc64el.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEh9vVdWFVIC7DiF6Ta3SY/LmzWKwFAlogJmcACgkQa3SY/Lmz WKzjYA//Xtm2JJ7jhzIsdO/UDUkIQDm0qvkU+5AZbsW4CnxN6CNYoKS9Jw1CBJpD L7WTF+/40Fkdq8DCH0jEf9FqcRnbWw5dIdecCq83RhbSxcYUT/+cEihWLm+g3KYL kd227QXzNM6IpU7pCJ+VtSBNNSx45aGWynkFhCRl20qU2uT60kUA6HAF77LZyfHv Hv+j+Mnm6oa0ivGjPJgCso9yqpw5zAPW4nwlTZiCJ6TQiC+CMmYp6VsKDMmcc7yt OHU58JccArewnObZfQ9j8s5J+E0sI62ZZkER8
Bug#886917: marked as done (tracker.debian.org: fails to linkify CVE identifiers)
Your message dated Tue, 13 Feb 2018 10:20:51 + with message-id <5a82bc03c1a42_5292af4411a50d020...@godard.mail> and subject line Bug #886917 in tracker.debian.org fixed has caused the Debian Bug report #886917, regarding tracker.debian.org: fails to linkify CVE identifiers 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.) -- 886917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tracker.debian.org I'm looking at https://tracker.debian.org/news/899725 (upload of src:linux/3.2.96-3 to wheezy-security). The CVEs there are not likified into security-tracker.d.o URLs. Once fixed, if possible, please rebuild the affected pages (ISTR the news are stored in the database already with the HTML markup). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Hello, Bug #886917 in tracker.debian.org reported by you has been fixed in the Git repository. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/qa/distro-tracker/commit/68c7b738662b3738038f05f66779ed9ac0c86281 Fix CVE linkify regexp to match CVE numbers in parentheses (Closes: #886917) (this message was generated automatically) -- Greetings--- End Message ---
Bug#887660: marked as done (RFS: minidb/2.0.2-1 [ITP])
Your message dated Tue, 13 Feb 2018 10:34:00 + with message-id and subject line closing RFS: minidb/2.0.2-1 [ITP] has caused the Debian Bug report #887660, regarding RFS: minidb/2.0.2-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 887660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "minidb" * Package name: minidb Version : 2.0.2-1 Upstream Author : Thomas Perl * URL : http://thp.io/2010/minidb/ * License : ISC Section : libs It builds those binary packages: minidb - simple SQLite3-based store for Python objects To access further information about this package, please visit the following URL: https://mentors.debian.net/package/minidb Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/minidb/minidb_2.0.2-1.dsc More information about minidb can be obtained from https://github.com/thp/minidb. Minidb is used by another existing package I'm updating : urlwatch. I'm looking for a sponsor for this two packages. See https://mentors.debian.net/package/urlwatch Changes since the last upload: minidb (2.0.2-1) unstable; urgency=low * Initial release (Closes: #887426) -- Maxime Werlen Tue, 16 Jan 2018 21:16:58 +0100 Regards, Maxime Werlen --- End Message --- --- Begin Message --- Package minidb has been removed from mentors.--- End Message ---
Bug#887481: marked as done (RFS: freetype/2.8.1-1.1 [NMU])
Your message dated Tue, 13 Feb 2018 10:33:32 + with message-id and subject line RFS: freetype/2.8.1-1.1 [NMU] has caused the Debian Bug report #887481, regarding RFS: freetype/2.8.1-1.1 [NMU] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 887481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for an NMU of the package "freetype". * Package name: freetype Version : 2.8.1-1.1 Upstream Author : The FreeType Project * URL : https://www.freetype.org/ * License : FreeType License / GPLv2 Section : libs It builds the following binary packages: * freetype2-demos - FreeType 2 demonstration programs * libfreetype6 - FreeType 2 font engine, shared library files * libfreetype6-dev - FreeType 2 font engine, development files * libfreetype6-udeb - FreeType 2 font engine for the debian-installer (udeb) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/freetype Alternatively, download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/f/freetype/freetype_2.8.1-1.1.dsc More information about hello can be obtained from https://www.freetype.org Changes since the last upload: * Non-maintainer upload. * debian/rules: - Update a 'sed' expression to prevent it replacing all occurrences of SIZEOF_LONG in ftconfig.h (Closes: #887087). Regards, Hugh McMaster --- End Message --- --- Begin Message --- Freetype 2.8.1-2 has now reached Sid/Unstable. This version includes the patch from my NMU. So this RFS is no longer needed. Closing.--- End Message ---
Bug#878227: marked as done (please drop transitional packages bibledit and bibledit-data)
Your message dated Tue, 13 Feb 2018 10:48:40 + with message-id and subject line Transitional packages has caused the Debian Bug report #878227, regarding please drop transitional packages bibledit and bibledit-data to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 878227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bibledit,bibledit-data Version: 4.9-1 Severity: normal user: qa.debian@packages.debian.org usertags: transitional Please drop the transitional packages bibledit and bibledit-data for buster, as they have been released with wheezy, jessie and stretch already. Thanks for maintaining bibledit-gtk! -- cheers, Holger signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Hi, The package this bug report refers to no longer exists in Debian unstable. It has been removed very recently. For more information about its removal, see this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869133 So since the package no longer exists, I am closing the bug report, as no longer applicable. Thank you for your contribution to Debian! --- End Message ---
Bug#884023: marked as done (bibledit: Installs same file as bibledit-gtk)
Your message dated Tue, 13 Feb 2018 10:52:09 + with message-id and subject line Duplicate no longer there has caused the Debian Bug report #884023, regarding bibledit: Installs same file as bibledit-gtk 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.) -- 884023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bibledit Version: 5.0.331-1 Severity: serious Both bibledit-gtk and bibledit ship the same file: /usr/share/pixmaps/bibledit.xpm See § 7.6.1 of Debian Policy which recommends that you use Breaks/Replaces here. https://www.debian.org/doc/debian-policy/#document-ch-relationships Also, I highly recommend that you add a transitional package so that people using bibledit-gtk will be upgraded to bibledit. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Package "bibledit-gtk" no longer exists, now, in Debian unstable. It has been removed very recently. For more information about its removal, see this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869133 So, since package "bibledit-gtk" is no longer in the Debian archives, the installation of the identical file is no longer relevant. I am closing this bug report as no longer applicable. --- End Message ---
Bug#863050: marked as done (Please update to newer version)
Your message dated Tue, 13 Feb 2018 11:00:16 + with message-id and subject line Bug#863050: fixed in python-jpype 0.6.2+dfsg-1 has caused the Debian Bug report #863050, regarding Please update to newer 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.) -- 863050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-jpype Version: 0.5.4.2-3+b1 The newest version of Jpype in Debian is currently 0.5.4.2, which is from 2011. The latest upstream version is 0.6.2, which is from 2017. Some Python packages (e.g. JayDeBeApi) require a newer version of Jpype than the one in Debian. There's also Python 3 support since 2015. I notice that the watch file points to Sourceforge. Jpype has moved to Github [1] some time ago. Please update the watch and the package so that we can enjoy Jpype's new features and bug fixes straight from Debian. [1] https://github.com/originell/jpype --- End Message --- --- Begin Message --- Source: python-jpype Source-Version: 0.6.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of python-jpype, 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 863...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated python-jpype package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 11 Feb 2018 18:42:08 +0900 Source: python-jpype Binary: python-jpype python3-jpype Architecture: source amd64 Version: 0.6.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: TANIGUCHI Takaki Description: python-jpype - Binding the worlds of Java and Python (for Python 2) python3-jpype - Binding the worlds of Java and Python (for Python 3) Closes: 863050 867199 Changes: python-jpype (0.6.2+dfsg-1) unstable; urgency=medium . [ Ondřej Nový ] * Fixed VCS URL (https) . [ TANIGUCHI Takaki ] * debian/watch: Set new location. * New upstream version 0.6.2+dfsg (Closes: #863050) * debian/rules: + call dh_numpy + disable test * Remove test/sample/big.xml from upstream. (Closes: #867199) * debian/control: - Add dh-python to B-D. - Change Priority from extra to optional - Migrate Vcs-* to salsa.debian.org. * debian/watch: Add dversionmangle * Bump Standards-Version to 4.1.3 * debian/compat: 11 Checksums-Sha1: de9b9f6f2989fc8cd84aa432c5d7262b643111fe 2125 python-jpype_0.6.2+dfsg-1.dsc 4b7d2947ae66e7daecd6821c63231f5fdff13fba 145765 python-jpype_0.6.2+dfsg.orig.tar.gz 787e6649e4e19ed182cfbae7e591ee24082ec62d 2756 python-jpype_0.6.2+dfsg-1.debian.tar.xz 0ff57f005d63d95435039829b01301582606a9c3 2045676 python-jpype-dbgsym_0.6.2+dfsg-1_amd64.deb 501c8b29151d83e8ed86510d2efcd6b932dcdc09 13786 python-jpype_0.6.2+dfsg-1_amd64.buildinfo 6e2c9fd91675319bda9671a4c6da0936b152864f 181940 python-jpype_0.6.2+dfsg-1_amd64.deb 6c5ddaf8843fcb4b2b9c61c422f7f131e2663c99 2057992 python3-jpype-dbgsym_0.6.2+dfsg-1_amd64.deb 8948cde93619419c6bf134c6083ba766e5729ff0 162116 python3-jpype_0.6.2+dfsg-1_amd64.deb Checksums-Sha256: 1eba8972c99559fc1d99742f0a6f38bd946e77279b8ff5061a3c66d0f7873bef 2125 python-jpype_0.6.2+dfsg-1.dsc 9029998e5fc0cf0d326cb25e3772e890c187b749a12a0117f0ebf657ba205bd3 145765 python-jpype_0.6.2+dfsg.orig.tar.gz 20a222ab26b8b5cd96f7e8a951f9693cee16008517c67de6e591cadefb6336f9 2756 python-jpype_0.6.2+dfsg-1.debian.tar.xz 5904404304614bc1f4f2b3fa71fdd464fc5c9ec6f1705aa90fd921c695b4b7e2 2045676 python-jpype-dbgsym_0.6.2+dfsg-1_amd64.deb 4b5612a4fd2e069cad37754bb20c4f65e3c217def4b3fae61860a27a0917c561 13786 python-jpype_0.6.2+dfsg-1_amd64.buildinfo a2229e11c5ecb864e0842842787eb40c2bd1d095bc9e47379200b3964433461f 181940 python-jpype_0.6.2+dfsg-1_amd64.deb be1dad4f6971d6ad70d3c20aaf0d086201b639be446bf6e0e24886076d47de1a 2057992 python3-jpype-dbgsym_0.6.2+dfsg-1_amd64.deb f171f0f36306481d42d2b39a3d9afebe1bf14aa6e1c60d7376d0bd2935d83e8d 162116 python3-jpype_0.6.2+dfsg-1_amd64.deb Files: 17803258b5ee77f9391e9bd4831d5482 2125 python optional python-jpype_0.6.2+df
Bug#877480: marked as done (ITP: kopano-webapp-plugin-files -- Kopano WebApp files plugin)
Your message dated Tue, 13 Feb 2018 11:00:14 + with message-id and subject line Bug#877480: fixed in kopano-webapp-plugin-files 2.1.0+dfsg1-1 has caused the Debian Bug report #877480, regarding ITP: kopano-webapp-plugin-files -- Kopano WebApp files plugin 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.) -- 877480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Carsten Schoenert * Package name: kopano-webapp-plugin-files Version : 2.1.0-beta1 Upstream Author : Kopano * URL : https://kopano.com/ https://stash.kopano.io/projects/KWA/repos/files/browse * License : AGPL-3, BSD-3, Expat, LGPL-3 Programming Lang: PHP, JS Description : Kopano WebApp files plugin This package is a plugin for kopano-webapp, a web interface for the Kopano Collaboration Platform. . File management integration plugin for the kopano-webapp, allows a user to browse, save and attach files from a file share backend. Supported backends are FTP and WebDav (for example Owncloud or NextCloud). This package is a additional plugin for kopano-webapp which is currently waiting for review in NEW. It will be maintained by Giraffe Maintainers Regards Carsten --- End Message --- --- Begin Message --- Source: kopano-webapp-plugin-files Source-Version: 2.1.0+dfsg1-1 We believe that the bug you reported is fixed in the latest version of kopano-webapp-plugin-files, 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 877...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carsten Schoenert (supplier of updated kopano-webapp-plugin-files package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Dec 2017 17:23:21 +0100 Source: kopano-webapp-plugin-files Binary: kopano-webapp-files Architecture: source all Version: 2.1.0+dfsg1-1 Distribution: experimental Urgency: medium Maintainer: Giraffe Maintainers Changed-By: Carsten Schoenert Description: kopano-webapp-files - Kopano WebApp files plugin Closes: 877480 Changes: kopano-webapp-plugin-files (2.1.0+dfsg1-1) experimental; urgency=medium . * initial packaging (Closes: #877480) . * [318d017] debian/* basic debianization * [a4d2eb3] debian/copyright: update info about PHP composer files * [8357c3d] d/README.source: adding some source related information * [b52fb07] New upstream version 2.1.0+dfsg1 * [0f4de28] rebuild patch queue from patch-queue branch * [6927743] debian/control: increase Standards-Version to 4.1.2 * [e8d98aa] remove Lintian override for k-w-p-f Checksums-Sha1: e26d074bbf9171aa43ead82f9287d21860e8ee95 2133 kopano-webapp-plugin-files_2.1.0+dfsg1-1.dsc 4cb8178ffb61e34b3bef9d309adfe43f59f89e13 1774708 kopano-webapp-plugin-files_2.1.0+dfsg1.orig.tar.xz eda2f04da89a3d6eebeb9eb9134a5c6ba565706c 4801864 kopano-webapp-plugin-files_2.1.0+dfsg1-1.debian.tar.xz b982d0257a9a9d1e760b12970dac6bae9627fe0d 1749720 kopano-webapp-files_2.1.0+dfsg1-1_all.deb ca42f64cbbfcf7ef63fc132da4208b858110caf3 11507 kopano-webapp-plugin-files_2.1.0+dfsg1-1_amd64.buildinfo Checksums-Sha256: 8738fd447e7ada7cf005872b3a3e169524b29b56a2e9d742c0f0e89597d9158c 2133 kopano-webapp-plugin-files_2.1.0+dfsg1-1.dsc 30b072cc813d20c2b946c69c0787c1ef260b1aeac2a23d1f96302641b29e795f 1774708 kopano-webapp-plugin-files_2.1.0+dfsg1.orig.tar.xz 010e7958294f946f5b9ddd2677b31543477c9bd9dc3168c24a6f2b07d7cebe8f 4801864 kopano-webapp-plugin-files_2.1.0+dfsg1-1.debian.tar.xz fd275f209473ff67c2cb251c1a4af5d1b79d931474c8690065c963e848c6e5d7 1749720 kopano-webapp-files_2.1.0+dfsg1-1_all.deb a0d98631c93fb08ec6a9c2ad0f9a1fa2132914a9a5d23e5f16faaf6fede0 11507 kopano-webapp-plugin-files_2.1.0+dfsg1-1_amd64.buildinfo Files: 2844af41a287ca4888bcda04299a94ab 2133 web optional kopano-webapp-plugin-files_2.1.0+dfsg1-1.dsc b80ad45fa0b7f83dc32c4f19ca298496 1774708 web optional kopano-webapp-plugin-files_2.1.0+dfsg1.orig.tar.xz e4fc7a838bafc09165dccbde743fbf2d 4801864 web optional kopano-webapp-plugin-files_2.1.0+dfsg1-1.
Bug#867199: marked as done (src:python-jpype: Non-free file (possible) in source test/sample/big.xml)
Your message dated Tue, 13 Feb 2018 11:00:16 + with message-id and subject line Bug#867199: fixed in python-jpype 0.6.2+dfsg-1 has caused the Debian Bug report #867199, regarding src:python-jpype: Non-free file (possible) in source test/sample/big.xml 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.) -- 867199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-jpype Version: 0.5.4.2-2 Severity: serious Justification: Policy 2.3 Unfortunately, I just rejected your package from New because it contains a file with no clear license that is not documented in debian/copyright. The same problem exists with the current packages in Debian. test/sample/big.xml: It's not clear that this is free (and thus suitable for distribution in Debian Main even in source form). If the file has a free license, please document that, if not repack the tarball to remove it. Scott K --- End Message --- --- Begin Message --- Source: python-jpype Source-Version: 0.6.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of python-jpype, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 867...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. TANIGUCHI Takaki (supplier of updated python-jpype package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 11 Feb 2018 18:42:08 +0900 Source: python-jpype Binary: python-jpype python3-jpype Architecture: source amd64 Version: 0.6.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: TANIGUCHI Takaki Description: python-jpype - Binding the worlds of Java and Python (for Python 2) python3-jpype - Binding the worlds of Java and Python (for Python 3) Closes: 863050 867199 Changes: python-jpype (0.6.2+dfsg-1) unstable; urgency=medium . [ Ondřej Nový ] * Fixed VCS URL (https) . [ TANIGUCHI Takaki ] * debian/watch: Set new location. * New upstream version 0.6.2+dfsg (Closes: #863050) * debian/rules: + call dh_numpy + disable test * Remove test/sample/big.xml from upstream. (Closes: #867199) * debian/control: - Add dh-python to B-D. - Change Priority from extra to optional - Migrate Vcs-* to salsa.debian.org. * debian/watch: Add dversionmangle * Bump Standards-Version to 4.1.3 * debian/compat: 11 Checksums-Sha1: de9b9f6f2989fc8cd84aa432c5d7262b643111fe 2125 python-jpype_0.6.2+dfsg-1.dsc 4b7d2947ae66e7daecd6821c63231f5fdff13fba 145765 python-jpype_0.6.2+dfsg.orig.tar.gz 787e6649e4e19ed182cfbae7e591ee24082ec62d 2756 python-jpype_0.6.2+dfsg-1.debian.tar.xz 0ff57f005d63d95435039829b01301582606a9c3 2045676 python-jpype-dbgsym_0.6.2+dfsg-1_amd64.deb 501c8b29151d83e8ed86510d2efcd6b932dcdc09 13786 python-jpype_0.6.2+dfsg-1_amd64.buildinfo 6e2c9fd91675319bda9671a4c6da0936b152864f 181940 python-jpype_0.6.2+dfsg-1_amd64.deb 6c5ddaf8843fcb4b2b9c61c422f7f131e2663c99 2057992 python3-jpype-dbgsym_0.6.2+dfsg-1_amd64.deb 8948cde93619419c6bf134c6083ba766e5729ff0 162116 python3-jpype_0.6.2+dfsg-1_amd64.deb Checksums-Sha256: 1eba8972c99559fc1d99742f0a6f38bd946e77279b8ff5061a3c66d0f7873bef 2125 python-jpype_0.6.2+dfsg-1.dsc 9029998e5fc0cf0d326cb25e3772e890c187b749a12a0117f0ebf657ba205bd3 145765 python-jpype_0.6.2+dfsg.orig.tar.gz 20a222ab26b8b5cd96f7e8a951f9693cee16008517c67de6e591cadefb6336f9 2756 python-jpype_0.6.2+dfsg-1.debian.tar.xz 5904404304614bc1f4f2b3fa71fdd464fc5c9ec6f1705aa90fd921c695b4b7e2 2045676 python-jpype-dbgsym_0.6.2+dfsg-1_amd64.deb 4b5612a4fd2e069cad37754bb20c4f65e3c217def4b3fae61860a27a0917c561 13786 python-jpype_0.6.2+dfsg-1_amd64.buildinfo a2229e11c5ecb864e0842842787eb40c2bd1d095bc9e47379200b3964433461f 181940 python-jpype_0.6.2+dfsg-1_amd64.deb be1dad4f6971d6ad70d3c20aaf0d086201b639be446bf6e0e24886076d47de1a 2057992 python3-jpype-dbgsym_0.6.2+dfsg-1_amd64.deb f171f0f36306481d42d2b39a3d9afebe1bf14aa6e1c60d7376d0bd2935d83e8d 162116 python3-jpype_0.6.2+dfsg-1_amd64.deb Files: 17803258b5ee77f9391e9bd4831d5482 2125 python optional python-jpype_0.6.2+df
Bug#889417: marked as done (Updating the httpcomponents-core Uploaders list)
Your message dated Tue, 13 Feb 2018 11:35:34 + with message-id and subject line Bug#889417: fixed in httpcomponents-core 4.4.9-1 has caused the Debian Bug report #889417, regarding Updating the httpcomponents-core 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.) -- 889417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: httpcomponents-core Version: 4.3.3-1 4.4.8-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Damien Raude-Morvan has not been working on the httpcomponents-core package for quite some time. 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 --- Source: httpcomponents-core Source-Version: 4.4.9-1 We believe that the bug you reported is fixed in the latest version of httpcomponents-core, 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 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated httpcomponents-core 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, 13 Feb 2018 12:12:07 +0100 Source: httpcomponents-core Binary: libhttpcore-java Architecture: source Version: 4.4.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libhttpcore-java - set of low level HTTP transport components for Java Closes: 889417 Changes: httpcomponents-core (4.4.9-1) unstable; urgency=medium . * New upstream release * Removed Damien Raude-Morvan from the uploaders (Closes: #889417) * Standards-Version updated to 4.1.3 * Switch to debhelper level 11 Checksums-Sha1: a0a8a712f0ac8c30652fbb59c13e8ec40004448f 2206 httpcomponents-core_4.4.9-1.dsc 2536db1e4322ac1ec40cb2614dd8e60f8fa0d3c7 342928 httpcomponents-core_4.4.9.orig.tar.xz 951c6a5cd6c1724d275caff58f585173294656ce 4928 httpcomponents-core_4.4.9-1.debian.tar.xz 825f1dab55a8cf443323112fdab696661d07d4ee 15654 httpcomponents-core_4.4.9-1_source.buildinfo Checksums-Sha256: 78e54313d3e63aa15916265ed3aa5b922c008a1a9a3a10b6a0a5399939ed96a0 2206 httpcomponents-core_4.4.9-1.dsc 2db89aabd2ff42d78bd61ff33393d32c116ecbce2ee2a97c7bc5523992ca3be3 342928 httpcomponents-core_4.4.9.orig.tar.xz cfa9c567385de36725b79533ed31b5172dd4be93e942269b49a246ce77b5a727 4928 httpcomponents-core_4.4.9-1.debian.tar.xz 42e70a4be41b83859b57a6276ed408bb5bfd0afb7c9f56a00e8f2e36f5235512 15654 httpcomponents-core_4.4.9-1_source.buildinfo Files: ff3d0becf427d06e5fadaddc718c50eb 2206 java optional httpcomponents-core_4.4.9-1.dsc 606a45d23eddb576f4f3725a3b1bd07d 342928 java optional httpcomponents-core_4.4.9.orig.tar.xz 4df2a49de3c7dca48ffbbdeba1530d8d 4928 java optional httpcomponents-core_4.4.9-1.debian.tar.xz 1dc579ce35392d2867d1c7d0cef13762 15654 java optional httpcomponents-core_4.4.9-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlqCyB8SHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs9FcP/jDLjVoA+FVo6yi+EgRgT6gYo+bl91Q1 tnTFRQqYA+n11SNYcuA/gR4A+UziRY4lirN9ECDvvZtjCxE/pRntd8zSMSyTsXc7 9YdOtTqG+xfaRYkL6UsxCuh9dP6DW3whfQQNsP27pt7KXrlgF3et8m87F1QuFBvb 7G8p3tmpRgUbmfzpkbeCzvfMlT7orpK2gsG+tZUpXWMMDw82oRE40oZiWhuNr9aQ OkY1ZN83VzTE0mAcare+veysRmCcDhCmURKii1z3uF4/+I0sHeGWfePnu9MKi9FA RM1uSVlNQo25L9gQf4ve1gAQ0GDWlxaSEcDsK4N3bRh8OHVPTqabdlL8mIyRMExL qcGagGgYVWixLbHoVvalrVl0nSmVCq04Kb2AXTYp+H7KOaSmZ4hQzCqY/yIfTLl2 +90fHETllrvdPRs3JojrM2iKRJ8UFekFNhxKC2KDUpuCf92sfhLedpwZrtd/6EuN HgDAMKlOSOuvG3QMBKEbsJ85O/2VA73haRcMbjaALXYmpjYP/1DBtxdYHVPhevVx Y+pN17Ph4DOSKm3+vSBwG1+jYGq9c2fOOJ00wcDBsdWPzYIYe0U4gxG5hkGBLcYq nab5Q/79XDUl/wMPfZ2fmg+aLi2SFS4glpyPs3+LbfeJnIv/fM9ddleEJtzP+0PT QvnYuddOVxlM =glJz -END PGP SIGNATURE End Message ---
Bug#889869: marked as done (bash: crash in qemu-user: bash: xmalloc: ... cannot allocate XX bytes (0 bytes allocated))
Your message dated Tue, 13 Feb 2018 11:34:17 + with message-id and subject line Bug#889869: fixed in bash 4.4.18-1.1 has caused the Debian Bug report #889869, regarding bash: crash in qemu-user: bash: xmalloc: ... cannot allocate XX bytes (0 bytes allocated) 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.) -- 889869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bash Version: 4.4.18-1 Severity: important Hi! I'm afraid that running bash in any qemu-user chroot/container crashes with: bash: xmalloc: .././locale.c:81: cannot allocate 2 bytes (0 bytes allocated) or bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes allocated) Happens for any target arch I tried. This makes bash non-installable (as its postinst is written in bash), and obviously makes the emulated system pretty much broken. Alas, gdb can't run binfmt-ed processes; a workaround apparently exists but it's anything but simple. Meow! -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.2+ (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages bash depends on: ii base-files 10.1 ii debianutils 4.8.4 ii libc62.26-6 ii libtinfo56.0+20171125-1 Versions of packages bash recommends: ii bash-completion 1:2.1-4.3 Versions of packages bash suggests: pn bash-doc -- no debconf information --- End Message --- --- Begin Message --- Source: bash Source-Version: 4.4.18-1.1 We believe that the bug you reported is fixed in the latest version of bash, 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 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated bash 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, 13 Feb 2018 11:17:39 +0100 Source: bash Binary: bash bash-static bash-builtins bash-doc Architecture: source Version: 4.4.18-1.1 Distribution: unstable Urgency: high Maintainer: Matthias Klose Changed-By: Raphaël Hertzog Description: bash - GNU Bourne Again SHell bash-builtins - Bash loadable builtins - headers & examples bash-doc - Documentation and examples for the GNU Bourne Again SHell bash-static - GNU Bourne Again SHell (static version) Closes: 889869 Changes: bash (4.4.18-1.1) unstable; urgency=high . * Non-maintainer upload. * Build again with -no-pie as dropping it broke bash when run under qemu-user (with the same symptoms as #842037). Closes: #889869 Re-opens: #865599 Checksums-Sha1: f3debf265b5e26c131bd676ce77744e5b89a8a78 1994 bash_4.4.18-1.1.dsc 7b22f86c829e96d531c035ad559921f51ca584ac 57760 bash_4.4.18-1.1.debian.tar.xz 290b877649ad807f6298ef5038f3a42a25041b49 5535 bash_4.4.18-1.1_source.buildinfo Checksums-Sha256: 7b81cdbff262db9bb6bd304bd849c84e54f3ab7aa707afbb6e93ed223db8d739 1994 bash_4.4.18-1.1.dsc bb2b62332aa5912e4070c44f840c3aa8236c773eba89a52367e70b95e0a717c7 57760 bash_4.4.18-1.1.debian.tar.xz c3d1ce54a936e47875d7e1cf8c944149bfbc107830732e68b2becd99ffbfbf35 5535 bash_4.4.18-1.1_source.buildinfo Files: d46dcd3de4500eba8852b7f67a6dff84 1994 base required bash_4.4.18-1.1.dsc 98f593337355e156457d9b6b68f78421 57760 base required bash_4.4.18-1.1.debian.tar.xz 4e70416153afa5fafba073b25bb9fcf5 5535 base required bash_4.4.18-1.1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Raphael Hertzog iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAlqCxe0ACgkQA4gdq+vC mrlqjwf/ezagK5gaKLqvGU4Wny9j1DqseLFCrDnhwkHaD6TpLGGgXiP2IsaRRC8/ F9AJN4QPbHjS3cjfjU3D6O7Pfyy828hVfPmL/Sh5+Ke5mlEsblDXtXJ77LQq2sW6 5Cfh70cUj/+7p8c0RZ6suOqkgD/8R7tEqDwRrOdpokoIhA/weqb6WDNyyQJPPyoB ToMB+KXtTSjTV5fZQmzulkf/j5UIyde/4cdSvo+daekgAz+TOAPGxXJqDW87OrMT uVTyaGs+ScGBDsZcGKGS+5xk0seASx7A5ZwyZ3su4iUegWZj0X2bgNlE0DfdCB
Bug#890088: marked as done (nlopt: Build-depend on dh-octave instead of octave-pkg-dev)
Your message dated Tue, 13 Feb 2018 11:52:22 + with message-id and subject line Bug#890088: fixed in nlopt 2.4.2+dfsg-4 has caused the Debian Bug report #890088, regarding nlopt: Build-depend on dh-octave instead of octave-pkg-dev 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.) -- 890088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nlopt Version: 2.4.2+dfsg-3 Severity: normal Tags: patch The octave-pkg-dev has been superseded by dh-octave and will be soon deprecated. Please, find attached to this bug report a patch for updating the nlopt source package, accordingly. Rafael Laboissière -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (550, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-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) diff --git a/debian/control b/debian/control index 63f3a2e..913b4e9 100644 --- a/debian/control +++ b/debian/control @@ -4,7 +4,7 @@ Priority: optional Maintainer: Debian Science Maintainers Uploaders: Sergey B Kirpichev , Christophe Trophime Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1~), - autotools-dev, libtool, automake, g++ (>= 4.2), octave-pkg-dev (>= 1.0.1), + autotools-dev, libtool, automake, g++ (>= 4.2), dh-octave, python-all-dev (>= 2.6.6-3~), python-numpy, guile-2.0, guile-2.0-dev Standards-Version: 4.0.0 X-Python-Version: >= 2.6 diff --git a/debian/rules b/debian/rules index c25c58e..377f0b2 100755 --- a/debian/rules +++ b/debian/rules @@ -72,6 +72,7 @@ override_dh_shlibdeps: dh_shlibdeps -- \ debian/python-nlopt/usr/lib/python*/dist-packages/*.so* \ -Tdebian/python-nlopt.substvars + dh_octave_substvar override_dh_auto_install: for v in $(PYVERS); do \ --- End Message --- --- Begin Message --- Source: nlopt Source-Version: 2.4.2+dfsg-4 We believe that the bug you reported is fixed in the latest version of nlopt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated nlopt 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: Tue, 13 Feb 2018 12:25:27 +0100 Source: nlopt Binary: libnlopt0 libnlopt-dev python-nlopt octave-nlopt libnlopt-guile0 Architecture: source Version: 2.4.2+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Sébastien Villemot Description: libnlopt-dev - nonlinear optimization library -- development package libnlopt-guile0 - nonlinear optimization library -- Guile bindings libnlopt0 - nonlinear optimization library octave-nlopt - nonlinear optimization library -- GNU Octave package python-nlopt - nonlinear optimization library -- Python bindings Closes: 890088 Changes: nlopt (2.4.2+dfsg-4) unstable; urgency=medium . * Team upload. . [ Rafael Laboissiere ] * Build-depend on dh-octave instead of octave-pkg-dev (Closes: #890088) . [ Sébastien Villemot ] * Update Vcs-* fields for salsa. * Bump to debhelper compat level 11, simplify debian/rules. * Add Testsuite: autopkgtest-pkg-python. Checksums-Sha1: a486e780d104c9390be269cc6d0c264ed91d0194 2354 nlopt_2.4.2+dfsg-4.dsc d9edea5e5a37b6122034bf88a73cf93e17d6ae0f 12064 nlopt_2.4.2+dfsg-4.debian.tar.xz bfe0dd43e87cd0b506c30fdd5ddb33bc67e3b2d1 18281 nlopt_2.4.2+dfsg-4_amd64.buildinfo Checksums-Sha256: c05067e35ec893eb5ba7dc00ba5357a4560a3251f9b72d9172cd2d57f8abcd55 2354 nlopt_2.4.2+dfsg-4.dsc fba956cdabe053e7ad1049f01e1a1249c10fc6cb2eb6e25f6376bd5e2ab0186e 12064 nlopt_2.4.2+dfsg-4.debian.tar.xz 27e96b92078724f6440aea7b6e0adedc70f95176447ca412e71fec6626c3e9ae 18281 nlopt_2.4.2+dfsg-4_amd64.buildinfo Files: 82a7311cbf645e97fed4639a97d516da 2354 math optional nlopt_2.4.2+dfsg-4.dsc 0d0de7342ed04b20f1705e80
Bug#888083: marked as done (mblaze: poorly formatted list in package description)
Your message dated Tue, 13 Feb 2018 12:22:16 +
with message-id
and subject line Bug#888083: fixed in mblaze 0.3.1-1
has caused the Debian Bug report #888083,
regarding mblaze: poorly formatted list in package description
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
888083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mblaze
Version: 0.2-1
Severity: minor
The mblaze package description looks terrible in aptitude (and
probablypackages.d.o) because it doesn't do list formatting correctly.
The correct way to do list formatting is two spaces, then an asterisk
and then a space and then the text.
Examples below:
$ aptitude show mblaze | sed -n -e '/^Description/{ :a; p;' -e 'n; /^ /ba; }; '
Description: UNIX utilities to deal with Maildir
The mblaze message system is a set of Unix utilities to deal with mail kept in
Maildir folders. It is a classic command line MUA and has no features for
receiving or transferring mail; you are expected to fetch your mail using
fdm(1), getmail(1) offlineimap(1), procmail(1), or similar , and send it using
dma(8), msmtp(1), sendmail(8), as provided by OpenSMTPD, Postfix, or similar.
mblaze expects your mail to reside in Maildir folders.
Its design is roughly inspired by MH, the RAND Message Handling System, but it
is a complete implementation from scratch. mblaze operates directly on Maildir
folders and doesn't use its own caches or databases. There is no setup needed
for many uses.
mblaze consists of these Unix tools that each do one job: maddr(1) extract
addresses from mail magrep(1)find mails matching a pattern mcom(1)
compose and send mail mdeliver(1) deliver messages or import mailboxes
mdirs(1) find Maildir folders mexport(1) export Maildir folders as
mailboxes mflag(1) change flags (marks) of mail mflow(1) reflow
format=flowed plain text mails mfwd(1) forward mail mgenmid(1) generate
Message-IDs mhdr(1) extract mail headers minc(1) incorporate new mail
mless(1) conveniently read mail in less(1) mlist(1) list and filter
mail messages mmime(1) create MIME messages mmkdir(1)create new Maildir
mpick(1) advanced mail filter mrep(1) reply to mail mscan(1)
generate one-line summaries of mail msed(1) manipulate mail headers
mseq(1) manipulate mail sequences mshow(1) render mail and extract
attachments msort(1) sort mail mthread(1) arrange mail into discussions
$ aptitude show apt | sed -n -e '/^Description/{ :a; p;' -e 'n; /^ /ba; }; '
Description: commandline package manager
This package provides commandline tools for searching and managing as well as
querying information about packages as a low-level access to all features of
the libapt-pkg library.
These include:
* apt-get for retrieval of packages and information about them from
authenticated sources and for installation, upgrade and removal of packages
together with their dependencies
* apt-cache for querying available information about installed as well as
installable packages
* apt-cdrom to use removable media as a source for packages
* apt-config as an interface to the configuration settings
* apt-key as an interface to manage authentication keys
$ apt-cache show mblaze | sed -n -e '/^Description/{ :a; p;' -e 'n; /^ /ba; }; '
Description-en: UNIX utilities to deal with Maildir
The mblaze message system is a set of Unix utilities to deal with mail kept in
Maildir folders. It is a classic command line MUA and has no features for
receiving or transferring mail; you are expected to fetch your mail using
fdm(1), getmail(1) offlineimap(1), procmail(1), or similar , and send it using
dma(8), msmtp(1), sendmail(8), as provided by OpenSMTPD, Postfix, or similar.
mblaze expects your mail to reside in Maildir folders.
.
Its design is roughly inspired by MH, the RAND Message Handling System, but it
is a complete implementation from scratch. mblaze operates directly on Maildir
folders and doesn't use its own caches or databases. There is no setup needed
for many uses.
.
mblaze consists of these Unix tools that each do one job:
maddr(1) extract addresses from mail
magrep(1)find mails matching a pattern
mcom(1) compose and send mail
mdeliver(1) deliver messages or import mailboxes
mdirs(1) find Maildir folders
mexport(1) export Maildir folders as mailboxes
mflag(1) change flags (marks) of mail
mflow(1) reflow format=flowed plain text mails
mfwd(1)
Bug#887988: marked as done (mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev)
Your message dated Tue, 13 Feb 2018 12:22:16 + with message-id and subject line Bug#887988: fixed in mblaze 0.3.1-1 has caused the Debian Bug report #887988, regarding mblaze: File conflict at /usr/bin/msort, /usr/bin/mprev 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.) -- 887988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mblaze,msort Version: mblaze/0.2-1 msort/8.53-2.1+b2 Severity: serious Hi, when installing mblaze on a system where msort is already installed, it fails to install with a file conflict as follows: Unpacking mblaze (0.2-1) ... dpkg: error processing archive /var/cache/apt/archives/mblaze_0.2-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/msort', which is also in package msort 8.53-2.1+b2 Errors were encountered while processing: /var/cache/apt/archives/mblaze_0.2-1_amd64.deb (Please note that dpkg aborts on the first file conflict and there's a chance that e.g. man pages also have a file conflict.) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: mblaze Source-Version: 0.3.1-1 We believe that the bug you reported is fixed in the latest version of mblaze, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Braud-Santoni (supplier of updated mblaze 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: Wed, 31 Jan 2018 18:58:56 +0100 Source: mblaze Binary: mblaze Architecture: source amd64 Version: 0.3.1-1 Distribution: unstable Urgency: medium Maintainer: Nicolas Braud-Santoni Changed-By: Nicolas Braud-Santoni Description: mblaze - UNIX utilities to deal with Maildir Closes: 887988 888083 888398 Changes: mblaze (0.3.1-1) unstable; urgency=medium . * New upstream version (2018-01-30) * New tools mbnc, mflow, mraw, mrecode * Numerous bug fixes * Improved documentation and UTF-8 parsing * mcolor, mless now support $NO_COLOR * blaze822.h ensures PATH_MAX is defined (Closes: 888398) . * Update Lintian overrides * Add debian-watch-could-verify-download We use signed Git tags from upstream, not signed tarballs * Add hardening-no-fortify-functions due to a false negative . * Update debian/copyright * Refer to the CC0-1.0 license file under /usr/share/common-licenses * Use a HTTPS URI for the DEP5 format . * Update debian/control * Conflict with msort, mpdtoys (Closes: 887988) * Fix the formatting in Description (Closes: 888083) * Declare compliance with policy 4.1.3 No change required. * Switch to debhelper 11 . * Install upstream's changelog Checksums-Sha1: 2a491280645752e8b81475699f7c545bc3e19bbe 1869 mblaze_0.3.1-1.dsc 7c65b3ef19b1c968eb7f241ba3511edf8b5bcb0f 83742 mblaze_0.3.1.orig.tar.gz 24a7e8a5cc5f104b62757b5be6658469ea45e552 6672 mblaze_0.3.1-1.debian.tar.xz d1d0e96b680a7cc36541a9ead69c6f1926972835 483684 mblaze-dbgsym_0.3.1-1_amd64.deb 08420567372634c20910c3db34049344b9f58bb5 5592 mblaze_0.3.1-1_amd64.buildinfo d2a34d1c5ca02d8fd5dc477651100d306f3a2787 117992 mblaze_0.3.1-1_amd64.deb Checksums-Sha256: 3c413785a3a5d158adc073ef57b5292308c6617f55f6c6c11de953ff6bb45962 1869 mblaze_0.3.1-1.dsc ae5947173c3887138576ed79f42cb021883c657f8124c69f47aa9c232275ab82 83742 mblaze_0.3.1.orig.tar.gz 0d54642d0b7fc44e7307a0b8b7388f0cdef412b5b54ab67f0670a79a6d0bd82e 6672 mblaze_0.3.1-1.debian.tar.xz 511ec98a271a75ec82979366bfb12b32d689f0c2d2a5119726bda77f3d5797f4 483684 mblaze-dbgsym_0.3.1-1_amd64.deb 7aa5aff6fdad023dccd8f015ddd1
Bug#890085: marked as done (vlfeat: Build-depend on dh-octave instead of octave-pkg-dev)
Your message dated Tue, 13 Feb 2018 12:23:18 +
with message-id
and subject line Bug#890085: fixed in vlfeat 0.9.20+dfsg0-2
has caused the Debian Bug report #890085,
regarding vlfeat: Build-depend on dh-octave instead of octave-pkg-dev
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.)
--
890085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vlfeat
Version: 0.9.20+dfsg0-1
Severity: normal
Tags: patch
The octave-pkg-dev has been superseded by dh-octave and will be soon
deprecated. Please, find attached to this bug report a patch for
updating the libgdf source package, accordingly.
Rafael Laboissière
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (550, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-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)
diff --git a/debian/control b/debian/control
index 0303e2f..c6d44d3 100644
--- a/debian/control
+++ b/debian/control
@@ -1,7 +1,7 @@
Source: vlfeat
Section: science
Priority: optional
-Build-Depends: debhelper (>= 9), dh-exec, liboctave-dev, octave-pkg-dev (>= 1.0.0),
+Build-Depends: debhelper (>= 9), dh-exec, liboctave-dev, dh-octave,
transfig, ghostscript, librsvg2-bin, texlive-latex-base, imagemagick,
python2.7, doxygen, rsync, groff
Maintainer: Debian Science Maintainers
diff --git a/debian/rules b/debian/rules
index 66d428e..48df993 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,7 +20,7 @@ override_dh_auto_install: $(addprefix install/,data $(wildcard toolbox/*))
ln -fs libvl.so.$(VERSION) libvl.so.$(API_VERSION)
override_dh_gencontrol:
- dh_gencontrol -- -V"octave:Depends=octave(>=`octave-config --print VERSION`)"
+ dh_octave_substvar
override_dh_strip: strip_mex
dh_strip --dbg-package=libvlfeat$(API_VERSION)-dbg
--- End Message ---
--- Begin Message ---
Source: vlfeat
Source-Version: 0.9.20+dfsg0-2
We believe that the bug you reported is fixed in the latest version of
vlfeat, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 890...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sébastien Villemot (supplier of updated vlfeat 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: Tue, 13 Feb 2018 12:48:31 +0100
Source: vlfeat
Binary: libvlfeat1 libvlfeat-dev libvlfeat1-dbg libvlfeat-doc octave-vlfeat
Architecture: source
Version: 0.9.20+dfsg0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Sébastien Villemot
Description:
libvlfeat-dev - Computer vision library focussing on visual features and
clusteri
libvlfeat-doc - Computer vision library focussing on visual features and
clusteri
libvlfeat1 - Computer vision library focussing on visual features and clusteri
libvlfeat1-dbg - Computer vision library focussing on visual features and
clusteri
octave-vlfeat - Computer vision library focussing on visual features and
clusteri
Closes: 890085
Changes:
vlfeat (0.9.20+dfsg0-2) unstable; urgency=medium
.
* Team upload.
* Build-depend on dh-octave instead of octave-pkg-dev.
Thanks to Rafael Laboissière (Closes: #890085)
* Update Vcs-* fields for salsa.
* Bump packages from priority extra to optional.
* Also missing files to clean rule: *.o, VERSION, toolbox/{mex,noprefix}.
Checksums-Sha1:
9eb3f6490fc0fea2a991bbc006fd983c17399427 2322 vlfeat_0.9.20+dfsg0-2.dsc
e3a212a3d21b54a315be4eafcc157ed7fba65325 10900
vlfeat_0.9.20+dfsg0-2.debian.tar.xz
b5e9636ee764a1c36bf1ebeae3bd5320b23ebdb8 19779
vlfeat_0.9.20+dfsg0-2_amd64.buildinfo
Checksums-Sha256:
63df87f42c875d2c9651614ad5b04832aac1b8dfadd460abbcd65a08a4b13e71 2322
vlfeat_0.9.20+dfsg0-2.dsc
46ff25919200609baaff4245c148f941af9b30ed93ed170ceb83b0dd61e3be6a 10900
vlfeat_0.9.20+dfsg0-2.debian.tar.xz
0e1
Bug#888398: marked as done (mblaze: FTBFS on hurd-i386: PATH_MAX undeclared)
Your message dated Tue, 13 Feb 2018 12:22:16 + with message-id and subject line Bug#888398: fixed in mblaze 0.3.1-1 has caused the Debian Bug report #888398, regarding mblaze: FTBFS on hurd-i386: PATH_MAX undeclared 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.) -- 888398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mblaze Version: 0.2-1 Severity: important Tags: upstream Justification: fails to build from source User: debian-h...@lists.debian.org Usertags: hurd The build of mblaze for hurd-i386 (admittedly not a release architecture) failed with multiple errors of the form seq.c:21:19: error: 'PATH_MAX' undeclared (first use in this function); did you mean 'INT8_MAX'? as detailed in [1]. The Hurd notoriously has no static PATH_MAX. Best practice is dynamically accommodating whatever you actually encounter, since fixed-size buffers generally run the risk of either wasting memory or yielding truncation (or, worse, buffer overflows). However, if that's infeasible, you can also look up _PC_PATH_MAX via pathconf or even supply a fallback constant (traditionally 4096). Could you please take a look? Thanks! [1] https://buildd.debian.org/status/fetch.php?pkg=mblaze&arch=hurd-i386&ver=0.2-1&stamp=1516620274&raw=0 -- 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 --- Source: mblaze Source-Version: 0.3.1-1 We believe that the bug you reported is fixed in the latest version of mblaze, 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 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Braud-Santoni (supplier of updated mblaze 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: Wed, 31 Jan 2018 18:58:56 +0100 Source: mblaze Binary: mblaze Architecture: source amd64 Version: 0.3.1-1 Distribution: unstable Urgency: medium Maintainer: Nicolas Braud-Santoni Changed-By: Nicolas Braud-Santoni Description: mblaze - UNIX utilities to deal with Maildir Closes: 887988 888083 888398 Changes: mblaze (0.3.1-1) unstable; urgency=medium . * New upstream version (2018-01-30) * New tools mbnc, mflow, mraw, mrecode * Numerous bug fixes * Improved documentation and UTF-8 parsing * mcolor, mless now support $NO_COLOR * blaze822.h ensures PATH_MAX is defined (Closes: 888398) . * Update Lintian overrides * Add debian-watch-could-verify-download We use signed Git tags from upstream, not signed tarballs * Add hardening-no-fortify-functions due to a false negative . * Update debian/copyright * Refer to the CC0-1.0 license file under /usr/share/common-licenses * Use a HTTPS URI for the DEP5 format . * Update debian/control * Conflict with msort, mpdtoys (Closes: 887988) * Fix the formatting in Description (Closes: 888083) * Declare compliance with policy 4.1.3 No change required. * Switch to debhelper 11 . * Install upstream's changelog Checksums-Sha1: 2a491280645752e8b81475699f7c545bc3e19bbe 1869 mblaze_0.3.1-1.dsc 7c65b3ef19b1c968eb7f241ba3511edf8b5bcb0f 83742 mblaze_0.3.1.orig.tar.gz 24a7e8a5cc5f104b62757b5be6658469ea45e552 6672 mblaze_0.3.1-1.debian.tar.xz d1d0e96b680a7cc36541a9ead69c6f1926972835 483684 mblaze-dbgsym_0.3.1-1_amd64.deb 08420567372634c20910c3db34049344b9f58bb5 5592 mblaze_0.3.1-1_amd64.buildinfo d2a34d1c5ca02d8fd5dc477651100d306f3a2787 117992 mblaze_0.3.1-1_amd64.deb Checksums-Sha256: 3c413785a3a5d158adc073ef57b5292308c6617f55f6c6c11de953ff6bb45962 1869 mblaze_0.3.1-1.dsc ae5947173c3887138576ed79f42cb021883c657f8124c69f47aa9c232275ab82 83742 mblaze_0.3.1.orig.tar.gz 0d54642d0b7fc44e7307a0b8b7388f0cdef412b5b54ab67f0670a79a6d0bd82e 6672 mblaze_0.3.1-1.debian.tar.xz 511ec98a271a75ec82979366bfb12b32d689f0c2d2a5119726bda77f3d5797f4 483684 mblaze-dbgsym_0.3.1-1_amd64.deb 7aa5aff6fdad023dccd8f015ddd1e26b2c1d81464ddfe066978e692f5d6d3ecf 5592 mblaze_0.3.1-1_amd64.buildinfo 801
Bug#889818: marked as done (prometheus-mongodb-exporter: FTBFS on 32-bit architectures - constant 9007199254740992 overflows int)
Your message dated Tue, 13 Feb 2018 13:12:21 + with message-id <0aa8c22c-a33e-7088-c1df-c5ec879b5...@debian.org> and subject line #886432 was fixed in 2016.08.01-5 has caused the Debian Bug report #886432, regarding prometheus-mongodb-exporter: FTBFS on 32-bit architectures - constant 9007199254740992 overflows int 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.) -- 886432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prometheus-mongodb-exporter Version: 1.0.0-1 Severity: serious Tags: sid buster Hi, prometheus-mongodb-exporter FTBFS on mips in a recent rebuild, but since I can reproduce this failure on i386 as well, presumably it fails on all 32-bit architectures. The error is: > github.com/golang/glog > gopkg.in/mgo.v2/internal/json > gopkg.in/mgo.v2/bson > # gopkg.in/mgo.v2/bson > src/gopkg.in/mgo.v2/bson/json.go:320:7: constant 9007199254740992 overflows > int > gopkg.in/mgo.v2/internal/scram > github.com/beorn7/perks/quantile > github.com/golang/protobuf/proto > github.com/prometheus/client_model/go > github.com/matttproud/golang_protobuf_extensions/pbutil > github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg > github.com/prometheus/common/model > github.com/prometheus/common/expfmt > github.com/prometheus/procfs/xfs > github.com/prometheus/procfs > github.com/prometheus/client_golang/prometheus > dh_auto_build: cd build && go install > -gcflags=\"-trimpath=/<>/build/src\" > -asmflags=\"-trimpath=/<>/build/src\" -v -p 1 > github.com/dcu/mongodb_exporter github.com/dcu/mongodb_exporter/collector > github.com/dcu/mongodb_exporter/shared returned exit code 2 Thanks, James signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 2016.08.01-5 This was fixed in the above version amd the givebacks of prometheus-mongodb-exporter and snapd built. Thanks, James signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#886432: marked as done (snapd FTBFS on 32bit: json.go:320:7: constant 9007199254740992 overflows int)
Your message dated Tue, 13 Feb 2018 13:12:21 + with message-id <0aa8c22c-a33e-7088-c1df-c5ec879b5...@debian.org> and subject line #886432 was fixed in 2016.08.01-5 has caused the Debian Bug report #886432, regarding snapd FTBFS on 32bit: json.go:320:7: constant 9007199254740992 overflows int 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.) -- 886432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snapd Version: 2.30-1 Severity: serious https://buildd.debian.org/status/package.php?p=snapd&suite=sid ... # gopkg.in/mgo.v2/bson src/gopkg.in/mgo.v2/bson/json.go:320:7: constant 9007199254740992 overflows int --- End Message --- --- Begin Message --- Version: 2016.08.01-5 This was fixed in the above version amd the givebacks of prometheus-mongodb-exporter and snapd built. Thanks, James signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#889819: marked as done (prometheus-mongodb-exporter FTBFS on 32bit: constant 9007199254740992 overflows int)
Your message dated Tue, 13 Feb 2018 13:12:21 + with message-id <0aa8c22c-a33e-7088-c1df-c5ec879b5...@debian.org> and subject line #886432 was fixed in 2016.08.01-5 has caused the Debian Bug report #886432, regarding prometheus-mongodb-exporter FTBFS on 32bit: constant 9007199254740992 overflows int 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.) -- 886432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prometheus-mongodb-exporter Version: 1.0.0-1 Severity: serious Tags: buster sid Some recent change in unstable makes prometheus-mongodb-exporter FTBFS on 32bit: https://tests.reproducible-builds.org/debian/history/prometheus-mongodb-exporter.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/prometheus-mongodb-exporter.html https://buildd.debian.org/status/package.php?p=prometheus-mongodb-exporter&suite=sid ... dh_auto_build -a -O--buildsystem=golang -O--builddir=build cd build && go install -gcflags=\"-trimpath=/<>/build/src\" -asmflags=\"-trimpath=/<>/build/src\" -v -p 1 github.com/dcu/mongodb_exporter github.com/dcu/mongodb_exporter/collector github.com/dcu/mongodb_exporter/shared github.com/golang/glog gopkg.in/mgo.v2/internal/json gopkg.in/mgo.v2/bson # gopkg.in/mgo.v2/bson src/gopkg.in/mgo.v2/bson/json.go:320:7: constant 9007199254740992 overflows int gopkg.in/mgo.v2/internal/scram github.com/beorn7/perks/quantile github.com/golang/protobuf/proto github.com/prometheus/client_model/go github.com/matttproud/golang_protobuf_extensions/pbutil github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg github.com/prometheus/common/model github.com/prometheus/common/expfmt github.com/prometheus/procfs/xfs github.com/prometheus/procfs github.com/prometheus/client_golang/prometheus dh_auto_build: cd build && go install -gcflags=\"-trimpath=/<>/build/src\" -asmflags=\"-trimpath=/<>/build/src\" -v -p 1 github.com/dcu/mongodb_exporter github.com/dcu/mongodb_exporter/collector github.com/dcu/mongodb_exporter/shared returned exit code 2 debian/rules:14: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 --- End Message --- --- Begin Message --- Version: 2016.08.01-5 This was fixed in the above version amd the givebacks of prometheus-mongodb-exporter and snapd built. Thanks, James signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#889826: marked as done (ITP: vmdb2 -- create disk images with Debian installed)
Your message dated Tue, 13 Feb 2018 14:11:25 +0100 with message-id <20180213131125.gh4...@rosa.stappers.it> and subject line [notificati...@github.com: Re: [larswirzenius/vmdb2] mv debian/ Debian/ (#29)] has caused the Debian Bug report #889826, regarding ITP: vmdb2 -- create disk images with Debian 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.) -- 889826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Lars Wirzenius * Package name: vmdb2 Version : 0.9 Upstream Author : Lars Wirzenius * URL : https://github.com/larswirzenius/vmdb2 * License : GPL3+ Programming Lang: Python Description : create disk images with Debian installed vmdb2 creates disk images with Debian installed. Conceptually it's like vmdebootstrap, except that the output is a disk image instead of a directory tree. Such images can be used for virtual machines, as well as real hardware. . vmdb2 is a successor of vmdebootstrap and intends to replace it. It's intentionally not backwards compatible with vmdebootstrap, however. --- End Message --- --- Begin Message --- - Forwarded message from Lars Wirzenius - Date: Mon, 12 Feb 2018 18:56:40 + (UTC) From: Lars Wirzenius To: larswirzenius/vmdb2 Cc: stappersg , Author Subject: Re: [larswirzenius/vmdb2] mv debian/ Debian/ (#29) Thanks, but I'm going to decline this. That directory in this repository _is_ the official Debian packaging. I seem to have forgotten to close the ITP. vmdb2 is already in unstable. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/larswirzenius/vmdb2/pull/29#issuecomment-365025360 - End forwarded message - Yes, there is https://packages.debian.org/sid/vmdb2 So now closing is ITP bugreport. Cheers Geert Stappers -- Leven en laten leven--- End Message ---
Bug#842512: marked as done (explain how this integrates with various unattended-upgrade solutions)
Your message dated Tue, 13 Feb 2018 13:36:41 +
with message-id
and subject line Bug#842512: fixed in needrestart 2.11+git20180213-1
has caused the Debian Bug report #842512,
regarding explain how this integrates with various unattended-upgrade solutions
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.)
--
842512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: needrestart
Version: 2.9-1~bpo8+1
Severity: wishlist
It is unclear to me whether installing this package alongside a
properly configured "unattended-upgrade" package will do the right
thing (that is, automatically restart services).
I am unsure because the default config (needrestart.conf) has the
following entry, which I assume to be the default:
# Restart services (l)ist only, (i)nteractive or (a)utomatically.
#$nrconf{restart} = 'i';
It *looks* like things work, because on the server where I have both
setup, running needrestart by hand tells me everything is fine. Is it
that "a" is the default, or that needrestart can tell there's no
terminal, or what?
It would be great if this is documented better (i looked, without
luck, in the manpage and readme files).
Thanks!
-- Package-specific info:
needrestart output:
Your outdated processes:
chromium[13772]
checkrestart output:
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable'), (1, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages needrestart depends on:
ii dpkg 1.17.27
ii gettext-base 0.19.3-2
ii libintl-perl 1.23-1+deb8u1
ii libmodule-find-perl0.12-1
ii libmodule-scandeps-perl1.16-1
ii libproc-processtable-perl 0.51-1
ii libsort-naturally-perl 1.03-1
ii libterm-readkey-perl 2.32-1+b1
ii perl 5.20.2-3+deb8u6
ii xz-utils 5.1.1alpha+20120614-2+b3
needrestart recommends no packages.
Versions of packages needrestart suggests:
ii libnotify-bin 0.7.6-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: needrestart
Source-Version: 2.11+git20180213-1
We believe that the bug you reported is fixed in the latest version of
needrestart, 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 842...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100
Source: needrestart
Binary: needrestart
Architecture: source all
Version: 2.11+git20180213-1
Distribution: experimental
Urgency: medium
Maintainer: Patrick Matthäi
Changed-By: Patrick Matthäi
Description:
needrestart - check which daemons need to be restarted after library upgrades
Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677
Changes:
needrestart (2.11+git20180213-1) experimental; urgency=medium
.
* New upstream git snapshot.
- Possible to override the configured restart mode using the
NEEDRESTART_MODE environment variable.
Closes: #866105
- Check for pending Intel microcode updates.
Closes: #886445
- Ignore special filename mappings used by recent versions of KDE
plasmashell.
Closes: #879091
- Fix handling of library mappings if target does not exist.
Closes: #878700
- Add missing unnamed device major numbers (fix for OpenVZ).
Closes: #876452
- Do not call GetTerminalSize() if STDOUT is not a TTY.
Closes: #859387
- Fix switch from interactive to list mode if debconf is run
noninteractive.
Closes: #876459
- Add documentation on restart mode if run non-interactive.
Closes: #842512
- Fix typo in man page.
Closes: #885448
- Drop merged patch 0
Bug#878700: marked as done (needrestart: False positive with AppImage)
Your message dated Tue, 13 Feb 2018 13:36:41 + with message-id and subject line Bug#878700: fixed in needrestart 2.11+git20180213-1 has caused the Debian Bug report #878700, regarding needrestart: False positive with AppImage 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.) -- 878700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: needrestart Version: 2.11-3 Severity: normal Dear Maintainer, It appears that AppImage packages mount their filesystem under /tmp/, and needrestart may find that there are open binaries or libraries there but be unable to find them. Sorry, I'm not sure how to word this ... The symptom I see is that I'm asked to restart xfce4-session every time I run needrestart, and it appears to be the NextCloud Appimage that's triggering it. >From sudo needrestart -v: [main] #8534 uses obsolete /tmp/.mount_Nextcl4R40GR/usr/bin/nextcloud I can show more of that output if needed (but would try for a minimal case) -- Package-specific info: needrestart output: Your outdated processes: AppRun[8534] checkrestart output: -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ.utf8, LC_CTYPE=en_NZ.utf8 (charmap=UTF-8), LANGUAGE=en_NZ:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages needrestart depends on: ii dpkg 1.18.24 ii gettext-base 0.19.8.1-2 ii libintl-perl 1.26-2 ii libmodule-find-perl0.13-1 ii libmodule-scandeps-perl1.23-1 ii libproc-processtable-perl 0.53-2 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.37-1 ii perl 5.24.1-3+deb9u2 ii xz-utils 5.2.2-1.2+b1 Versions of packages needrestart recommends: ii libpam-systemd 232-25+deb9u1 Versions of packages needrestart suggests: ii libnotify-bin 0.7.7-2 -- no debconf information --- End Message --- --- Begin Message --- Source: needrestart Source-Version: 2.11+git20180213-1 We believe that the bug you reported is fixed in the latest version of needrestart, 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 878...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100 Source: needrestart Binary: needrestart Architecture: source all Version: 2.11+git20180213-1 Distribution: experimental Urgency: medium Maintainer: Patrick Matthäi Changed-By: Patrick Matthäi Description: needrestart - check which daemons need to be restarted after library upgrades Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677 Changes: needrestart (2.11+git20180213-1) experimental; urgency=medium . * New upstream git snapshot. - Possible to override the configured restart mode using the NEEDRESTART_MODE environment variable. Closes: #866105 - Check for pending Intel microcode updates. Closes: #886445 - Ignore special filename mappings used by recent versions of KDE plasmashell. Closes: #879091 - Fix handling of library mappings if target does not exist. Closes: #878700 - Add missing unnamed device major numbers (fix for OpenVZ). Closes: #876452 - Do not call GetTerminalSize() if STDOUT is not a TTY. Closes: #859387 - Fix switch from interactive to list mode if debconf is run noninteractive. Closes: #876459 - Add documentation on restart mode if run non-interactive. Closes: #842512 - Fix typo in man page. Closes: #885448 - Drop merged patch 03-perl-warning. - Drop merged patch 04-ignore-systemd-services. - Drop merged patch 02-install-restart-d. * Add dependency on binutils. Closes: #887677
Bug#859387: marked as done (NeedRestart::UI assumes STDOUT is a terminal)
Your message dated Tue, 13 Feb 2018 13:36:41 + with message-id and subject line Bug#859387: fixed in needrestart 2.11+git20180213-1 has caused the Debian Bug report #859387, regarding NeedRestart::UI assumes STDOUT is a terminal 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.) -- 859387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: needrestart Version: 2.11-2 Severity: normal File: /usr/share/perl5/NeedRestart/UI.pm Usertags: terminal I switched to unattended-upgrades and now needrestart prints lots of the following lines, it appears that it prints one for each message it prints. I would recommend checking if the $fd or STDOUT is a terminal before calling GetTerminalSize. When not writing to a terminal, I think needrestart should not wrap any messages. Unable to get Terminal Size. The TIOCGWINSZ ioctl didn't work. The COLUMNS and LINES environment variables didn't work. The resize program didn't work. The stty program didn't work. at /usr/share/perl5/NeedRestart/UI.pm line 50. -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 'testing- proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages needrestart depends on: ii dpkg 1.18.23 ii gettext-base 0.19.8.1-2 ii libintl-perl 1.26-2 ii libmodule-find-perl0.13-1 ii libmodule-scandeps-perl1.23-1 ii libproc-processtable-perl 0.53-2 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.37-1 ii perl 5.24.1-2 ii xz-utils 5.2.2-1.2+b1 Versions of packages needrestart recommends: ii libpam-systemd 232-19 Versions of packages needrestart suggests: ii libnotify-bin0.7.7-1+b1 ii needrestart-session 0.3-4.1 -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: needrestart Source-Version: 2.11+git20180213-1 We believe that the bug you reported is fixed in the latest version of needrestart, 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 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100 Source: needrestart Binary: needrestart Architecture: source all Version: 2.11+git20180213-1 Distribution: experimental Urgency: medium Maintainer: Patrick Matthäi Changed-By: Patrick Matthäi Description: needrestart - check which daemons need to be restarted after library upgrades Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677 Changes: needrestart (2.11+git20180213-1) experimental; urgency=medium . * New upstream git snapshot. - Possible to override the configured restart mode using the NEEDRESTART_MODE environment variable. Closes: #866105 - Check for pending Intel microcode updates. Closes: #886445 - Ignore special filename mappings used by recent versions of KDE plasmashell. Closes: #879091 - Fix handling of library mappings if target does not exist. Closes: #878700 - Add missing unnamed device major numbers (fix for OpenVZ). Closes: #876452 - Do not call GetTerminalSize() if STDOUT is not a TTY. Closes: #859387 - Fix switch from interactive to list mode if debconf is run noninteractive. Closes: #876459 - Add documentation on restart mode if run non-interactive. Closes: #842512 - Fix typo in man page.
Bug#876452: marked as done (needrestart: Unnamed block devices (like for OpenVZ's simfs) not being detected properly)
Your message dated Tue, 13 Feb 2018 13:36:41 +
with message-id
and subject line Bug#876452: fixed in needrestart 2.11+git20180213-1
has caused the Debian Bug report #876452,
regarding needrestart: Unnamed block devices (like for OpenVZ's simfs) not
being detected properly
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.)
--
876452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: needrestart
Version: 2.11-3
Severity: important
Tags: patch upstream
Dear Maintainer,
needrestart does not work properly on some OpenVZ containers - it always claims
that everything needs to be restarted. There was a bug report about that in the
upstream:
https://github.com/liske/needrestart/issues/28
but the solution given there (already included in Debian) does not cover all
cases. As written in the kernel docs
(https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/devices.txt),
unnamed device major number is not always 0, it can also be 144, 145 and 146.
I've made a simple patch to handle that.
Regards,
Piotr
-- System Information:
Debian Release: 9.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32.bsd54g54 (SMP w/24 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: sysvinit (via /sbin/init)
Versions of packages needrestart depends on:
ii dpkg 1.18.24
ii gettext-base 0.19.8.1-2
ii libintl-perl 1.26-2
ii libmodule-find-perl0.13-1
ii libmodule-scandeps-perl1.23-1
ii libproc-processtable-perl 0.53-2
ii libsort-naturally-perl 1.03-1
ii libterm-readkey-perl 2.37-1
ii perl 5.24.1-3+deb9u1
ii xz-utils 5.2.2-1.2+b1
Versions of packages needrestart recommends:
ii sysvinit-core 2.88dsf-59.9
Versions of packages needrestart suggests:
pn needrestart-session | libnotify-bin
-- no debconf information
--- needrestart-2.11.orig/needrestart
+++ needrestart-2.11/needrestart
@@ -472,9 +472,9 @@ if(defined($opt_l)) {
# Don't compare device numbers on anon filesystems
# w/o a backing device (like OpenVZ's simfs).
+ my $major = (($sdev >> 8) & 0xfff) | (($sdev >> 32) &
~0xfff);
$mdev = "00:00"
- if $sdev >> 8) & 0xfff) |
-(($sdev >> 32) & ~0xfff)) == 0);
+ if ($major == 0 || $major == 144 || $major == 145
|| $major == 146);
# compare maps content vs. on-disk
unless($minode eq $sinode && ((grep {$mdev eq $_}
@sdevs) ||
--- End Message ---
--- Begin Message ---
Source: needrestart
Source-Version: 2.11+git20180213-1
We believe that the bug you reported is fixed in the latest version of
needrestart, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100
Source: needrestart
Binary: needrestart
Architecture: source all
Version: 2.11+git20180213-1
Distribution: experimental
Urgency: medium
Maintainer: Patrick Matthäi
Changed-By: Patrick Matthäi
Description:
needrestart - check which daemons need to be restarted after library upgrades
Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677
Changes:
needrestart (2.11+git20180213-1) experimental; urgency=medium
.
* New upstream git snapshot.
- Possible to override the configured restart mode using the
NEEDRESTART_MODE environment variable.
Closes: #866105
- Check for pending Intel microcode updates.
Closes: #886445
- Ignore special filename mappings used by recent versions of KDE
plasmashell.
Closes:
Bug#887677: marked as done (needrestart: Missing dependency on binutils (for strings))
Your message dated Tue, 13 Feb 2018 13:36:41 + with message-id and subject line Bug#887677: fixed in needrestart 2.11+git20180213-1 has caused the Debian Bug report #887677, regarding needrestart: Missing dependency on binutils (for strings) 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.) -- 887677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: needrestart Version: 2.11-3 Severity: normal Dear Maintainer, While trying to detect kernel status with needrestart -kv, the following message appears: /usr/lib/needrestart/vmlinuz-get-version: 23: /usr/lib/needrestart/vmlinuz-get-version: strings: not found It looks like needrestart attempts to invoke `strings' from the binutils package, but it is not marked as a dependency so may be missing. (While raised against 2.11-3, the dependency is still missing in 2.11-4 according to p.d.o.) -- Package-specific info: needrestart output: Failed to retrieve available kernel versions. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.9.76-v7+ (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages needrestart depends on: ii dpkg 1.18.24 ii gettext-base 0.19.8.1-2 ii libintl-perl 1.26-2 ii libmodule-find-perl0.13-1 ii libmodule-scandeps-perl1.23-1 ii libproc-processtable-perl 0.53-2 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.37-1 ii perl 5.24.1-3+deb9u2 ii xz-utils 5.2.2-1.2+b1 Versions of packages needrestart recommends: pn libpam-systemd | sysvinit-core Versions of packages needrestart suggests: pn needrestart-session | libnotify-bin -- no debconf information --- End Message --- --- Begin Message --- Source: needrestart Source-Version: 2.11+git20180213-1 We believe that the bug you reported is fixed in the latest version of needrestart, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100 Source: needrestart Binary: needrestart Architecture: source all Version: 2.11+git20180213-1 Distribution: experimental Urgency: medium Maintainer: Patrick Matthäi Changed-By: Patrick Matthäi Description: needrestart - check which daemons need to be restarted after library upgrades Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677 Changes: needrestart (2.11+git20180213-1) experimental; urgency=medium . * New upstream git snapshot. - Possible to override the configured restart mode using the NEEDRESTART_MODE environment variable. Closes: #866105 - Check for pending Intel microcode updates. Closes: #886445 - Ignore special filename mappings used by recent versions of KDE plasmashell. Closes: #879091 - Fix handling of library mappings if target does not exist. Closes: #878700 - Add missing unnamed device major numbers (fix for OpenVZ). Closes: #876452 - Do not call GetTerminalSize() if STDOUT is not a TTY. Closes: #859387 - Fix switch from interactive to list mode if debconf is run noninteractive. Closes: #876459 - Add documentation on restart mode if run non-interactive. Closes: #842512 - Fix typo in man page. Closes: #885448 - Drop merged patch 03-perl-warning. - Drop merged patch 04-ignore-systemd-services. - Drop merged patch 02-install-restart-d. * Add dependency on binutils. Closes: #887677
Bug#879091: marked as done (needrestart: false positive with recent evolution/gnome-shell: /tmp/#8929645)
Your message dated Tue, 13 Feb 2018 13:36:41 + with message-id and subject line Bug#879091: fixed in needrestart 2.11+git20180213-1 has caused the Debian Bug report #879091, regarding needrestart: false positive with recent evolution/gnome-shell: /tmp/#8929645 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.) -- 879091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: needrestart Version: 2.11-4 Severity: normal There seems to be a false positive with evolution 3.26.1-1 and gnome-shell 3.22.3-3 and temporary files like /tmp/#8929645: $ needrestart -v [main] eval /etc/needrestart/needrestart.conf [main] needrestart v2.11 [main] running in user mode [Core] Using UI 'NeedRestart::UI::stdio'... [main] detected systemd ... [main] #2789 uses deleted /tmp/#8929645 [main] #10548 uses deleted /tmp/#8930322 Your outdated processes: evolution[2789], gnome-shell[10548] $ lsof -p 2789 | grep /tmp evolution 2789 pabs DEL REG 253,18929645 /tmp/#8929645 $ lsof -p 10548 | grep /tmp gnome-she 10548 pabs DEL REG 253,1 8930322 /tmp/#8930322 -- Package-specific info: needrestart output: Your outdated processes: evolution[2789], gnome-shell[10548] checkrestart output: -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'),user/1000/ (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages needrestart depends on: ii dpkg 1.18.24 ii gettext-base 0.19.8.1-4 ii libintl-perl 1.26-2 ii libmodule-find-perl0.13-1 ii libmodule-scandeps-perl1.24-1 ii libproc-processtable-perl 0.53-2+b2 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.37-1+b2 ii perl 5.26.0-8 ii xz-utils 5.2.2-1.3 Versions of packages needrestart recommends: ii libpam-systemd 235-2 Versions of packages needrestart suggests: ii libnotify-bin0.7.7-2 ii needrestart-session 0.3-5 -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: needrestart Source-Version: 2.11+git20180213-1 We believe that the bug you reported is fixed in the latest version of needrestart, 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 879...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100 Source: needrestart Binary: needrestart Architecture: source all Version: 2.11+git20180213-1 Distribution: experimental Urgency: medium Maintainer: Patrick Matthäi Changed-By: Patrick Matthäi Description: needrestart - check which daemons need to be restarted after library upgrades Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677 Changes: needrestart (2.11+git20180213-1) experimental; urgency=medium . * New upstream git snapshot. - Possible to override the configured restart mode using the NEEDRESTART_MODE environment variable. Closes: #866105 - Check for pending Intel microcode updates. Closes: #886445 - Ignore special filename mappings used by recent versions of KDE plasmashell. Closes: #879091 - Fix handling of library mappings if target does not exist. Closes: #878700 - Add missing unnamed device major numbers (fix for OpenVZ). Closes: #876452 - Do not call GetTerminalSize() if STDOUT is not a TTY.
Bug#886445: marked as done (needrestart: detect need to reboot due to Intel microcode updates)
Your message dated Tue, 13 Feb 2018 13:36:41 + with message-id and subject line Bug#886445: fixed in needrestart 2.11+git20180213-1 has caused the Debian Bug report #886445, regarding needrestart: detect need to reboot due to Intel microcode updates 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.) -- 886445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: needrestart Version: 2.11-4 Severity: wishlist Please detect the need to reboot to apply Intel microcode updates. When iucode_tool is installed, please check if /boot/initrd.img* contain the same microcode rev for the current CPU signature as the Linux kernel is listing in /proc/cpuinfo as the microcode version. First, get the processor signature (also available in next step): $ /usr/sbin/iucode_tool -Sv /usr/sbin/iucode_tool: system has processor(s) with signature 0x00020655 Second, match the processor signature against the 'sig' field of the selected microcodes in all the initrds and extract the 'rev' field of that microcode. $ /usr/sbin/iucode_tool -tr -Sl /boot/initrd.img-4.14.0-2-amd64 /usr/sbin/iucode_tool: system has processor(s) with signature 0x00020655 microcode bundle 1: /boot/initrd.img-4.14.0-2-amd64 selected microcodes: 001/001: sig 0x00020652, pf_mask 0x12, 2015-06-30, rev 0x000f, size 8192 001/002: sig 0x00020655, pf_mask 0x92, 2015-06-30, rev 0x0005, size 3072 Third, match the extracted rev field against the microcode field in the Linux /proc/cpuinfo file. $ grep micro /proc/cpuinfo microcode : 0x5 microcode : 0x5 microcode : 0x5 microcode : 0x5 When running as root, the microcode versions are also in /sys: $ head /sys/devices/system/cpu/*/microcode/version head: cannot open '/sys/devices/system/cpu/cpu0/microcode/version' for reading: Permission denied head: cannot open '/sys/devices/system/cpu/cpu1/microcode/version' for reading: Permission denied head: cannot open '/sys/devices/system/cpu/cpu2/microcode/version' for reading: Permission denied head: cannot open '/sys/devices/system/cpu/cpu3/microcode/version' for reading: Permission denied $ sudo head /sys/devices/system/cpu/*/microcode/version ==> /sys/devices/system/cpu/cpu0/microcode/version <== 0x5 ==> /sys/devices/system/cpu/cpu1/microcode/version <== 0x5 ==> /sys/devices/system/cpu/cpu2/microcode/version <== 0x5 ==> /sys/devices/system/cpu/cpu3/microcode/version <== 0x5 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: needrestart Source-Version: 2.11+git20180213-1 We believe that the bug you reported is fixed in the latest version of needrestart, 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 886...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100 Source: needrestart Binary: needrestart Architecture: source all Version: 2.11+git20180213-1 Distribution: experimental Urgency: medium Maintainer: Patrick Matthäi Changed-By: Patrick Matthäi Description: needrestart - check which daemons need to be restarted after library upgrades Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677 Changes: needrestart (2.11+git20180213-1) experimental; urgency=medium . * New upstream git snapshot. - Possible to override the configured restart mode using the NEEDRESTART_MODE environment variable. Closes: #866105 - Check for pending Intel microcode updates. Closes: #886445 - Ignore special filename mappings used by recent versions of KDE plasmashell. Closes: #879091 - Fix handling of library mappings if target does not exist. Closes: #878700 - Add missing unnamed device major numbers (fix for OpenVZ). Closes: #876452 - Do not call GetTerminalSize() if STDOUT is not a TTY. Closes: #859387 - Fix switch from inte
Bug#866105: marked as done (needrestart: please have a mechanism to invoke needrestart from apt with -r a)
Your message dated Tue, 13 Feb 2018 13:36:41 + with message-id and subject line Bug#866105: fixed in needrestart 2.11+git20180213-1 has caused the Debian Bug report #866105, regarding needrestart: please have a mechanism to invoke needrestart from apt with -r a to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 866105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: needrestart Version: 2.11-3 Severity: wishlist Dear Maintainer, during automated processes, such as puppet runs or automated upgrades, it is sometimes acceptable to restart daemons without asking. In this case, I would like to have my system return to the normal way of operation after the automated processing. It would, therefore, be not a good idea to actually modify /etc/apt/apt.conf.d/99needrestart because one would need to re-edit the file to its original state. Would it be possible to have /usr/lib/needrestart/apt-pinvoke source a (normally not existing) /etc/needrestart.conf where one could put the options in? or even an /etc/needrestart.d where one could drop a file and remove it afterwards? In the mean time, I have added an 98needrestart which calls apt-pinvoke -r a, but this of course means that needrestart runs twice - once noninteractively, doing the necessary restarts, and a second time interactively with (hopefully) nothing to do. Is this intended/acceptable use? Greetings Marc -- Package-specific info: needrestart output: checkrestart output: -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.6-zgws1 (SMP w/4 CPU cores) Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages needrestart depends on: ii dpkg 1.18.24 ii gettext-base 0.19.8.1-2 ii libintl-perl 1.26-2 ii libmodule-find-perl0.13-1 ii libmodule-scandeps-perl1.23-1 ii libproc-processtable-perl 0.53-2 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.37-1 ii perl 5.24.1-3 ii xz-utils 5.2.2-1.2+b1 Versions of packages needrestart recommends: ii libpam-systemd 232-25 Versions of packages needrestart suggests: pn needrestart-session | libnotify-bin -- no debconf information --- End Message --- --- Begin Message --- Source: needrestart Source-Version: 2.11+git20180213-1 We believe that the bug you reported is fixed in the latest version of needrestart, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100 Source: needrestart Binary: needrestart Architecture: source all Version: 2.11+git20180213-1 Distribution: experimental Urgency: medium Maintainer: Patrick Matthäi Changed-By: Patrick Matthäi Description: needrestart - check which daemons need to be restarted after library upgrades Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677 Changes: needrestart (2.11+git20180213-1) experimental; urgency=medium . * New upstream git snapshot. - Possible to override the configured restart mode using the NEEDRESTART_MODE environment variable. Closes: #866105 - Check for pending Intel microcode updates. Closes: #886445 - Ignore special filename mappings used by recent versions of KDE plasmashell. Closes: #879091 - Fix handling of library mappings if target does not exist. Closes: #878700 - Add missing unnamed device major numbers (fix for OpenVZ). Closes: #876452 - Do not call GetTerminalSize() if STDOUT is not a TTY. Closes: #859387 - Fix switch from interactive to list mode if debconf is run noninte
Bug#876459: marked as done (needrestart: Non-interactive mode not being detected properly)
Your message dated Tue, 13 Feb 2018 13:36:41 +
with message-id
and subject line Bug#876459: fixed in needrestart 2.11+git20180213-1
has caused the Debian Bug report #876459,
regarding needrestart: Non-interactive mode not being detected properly
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.)
--
876459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: needrestart
Version: 2.11-3
Severity: important
Tags: upstream patch
Dear Maintainer,
the problem described in the archived bug #803249 still exists in 2.11-3
(Debian 9.1). When needrestart is run without a tty AND with
DEBIAN_FRONTEND=noninteractive, it still tries to work interactively rather
than fall back to "list only" mode. In some cases it causes unwanted restarts.
The easiest way to reproduce it is to run needrestart from cron, redirecting
the output to a file.
I attach a patch that may work, but I'm not sure, as I know Perl only a little
and don't know other implementation details. In my case it is working as
expected.
The problem is rather serious. I use Ansible for automation and once I run it
to install something on an OpenVZ host. After installation by apt-get,
needrestart started to restart VZ containers, including the one from which
Ansible was run. I ended up with all the containers stopped!
Regards,
Piotr
-- System Information:
Debian Release: 9.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32.bsd54g54 (SMP w/24 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: sysvinit (via /sbin/init)
Versions of packages needrestart depends on:
ii dpkg 1.18.24
ii gettext-base 0.19.8.1-2
ii libintl-perl 1.26-2
ii libmodule-find-perl0.13-1
ii libmodule-scandeps-perl1.23-1
ii libproc-processtable-perl 0.53-2
ii libsort-naturally-perl 1.03-1
ii libterm-readkey-perl 2.37-1
ii perl 5.24.1-3+deb9u1
ii xz-utils 5.2.2-1.2+b1
Versions of packages needrestart recommends:
ii sysvinit-core 2.88dsf-59.9
Versions of packages needrestart suggests:
pn needrestart-session | libnotify-bin
-- no debconf information
--- needrestart-2.11.orig/needrestart
+++ needrestart-2.11/needrestart
@@ -181,7 +181,7 @@ $nrconf{ui} = qq(NeedRestart::UI::stdio)
die "Hook directory '$nrconf{hook_d}' is invalid!\n" unless(-d $nrconf{hook_d}
|| $opt_b);
$opt_r = $nrconf{restart} unless(defined($opt_r));
die "ERROR: Unknown restart option '$opt_r'!\n" unless($opt_r =~ /^(l|i|a)$/);
-$is_tty++ if($opt_r eq 'i' && exists($ENV{DEBIAN_FRONTEND}) &&
$ENV{DEBIAN_FRONTEND} eq 'noninteractive');
+$is_tty = 0 if($opt_r eq 'i' && exists($ENV{DEBIAN_FRONTEND}) &&
$ENV{DEBIAN_FRONTEND} eq 'noninteractive');
$opt_r = 'l' if(!$is_tty && $opt_r eq 'i');
$opt_m = $nrconf{ui_mode} unless(defined($opt_m));
--- End Message ---
--- Begin Message ---
Source: needrestart
Source-Version: 2.11+git20180213-1
We believe that the bug you reported is fixed in the latest version of
needrestart, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100
Source: needrestart
Binary: needrestart
Architecture: source all
Version: 2.11+git20180213-1
Distribution: experimental
Urgency: medium
Maintainer: Patrick Matthäi
Changed-By: Patrick Matthäi
Description:
needrestart - check which daemons need to be restarted after library upgrades
Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677
Changes:
needrestart (2.11+git20180213-1) experimental; urgency=medium
.
* New upstream git snapshot.
- Possible to override the configured restart mode using the
NEEDRESTART_MODE environment variable.
Bug#885448: marked as done (needrestart manual: typo: (a)dvaned -> (a)dvanced)
Your message dated Tue, 13 Feb 2018 13:36:41 + with message-id and subject line Bug#885448: fixed in needrestart 2.11+git20180213-1 has caused the Debian Bug report #885448, regarding needrestart manual: typo: (a)dvaned -> (a)dvanced 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.) -- 885448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: needrestart Version: 2.11-4 Severity: minor File: /usr/share/man/man1/needrestart.1.gz There is a typo in the manual page, this line: a (a)dvaned mode Should be changed to this line: a (a)dvanced mode -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages needrestart depends on: ii dpkg 1.19.0.4 ii gettext-base 0.19.8.1-4 ii libintl-perl 1.26-2 ii libmodule-find-perl0.13-1 ii libmodule-scandeps-perl1.24-1 ii libproc-processtable-perl 0.53-2+b2 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.37-1+b2 ii perl 5.26.1-3 ii xz-utils 5.2.2-1.3 Versions of packages needrestart recommends: ii libpam-systemd 236-1 Versions of packages needrestart suggests: ii libnotify-bin0.7.7-3 ii needrestart-session 0.3-5 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: needrestart Source-Version: 2.11+git20180213-1 We believe that the bug you reported is fixed in the latest version of needrestart, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi (supplier of updated needrestart 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: Tue, 13 Feb 2018 14:10:34 +0100 Source: needrestart Binary: needrestart Architecture: source all Version: 2.11+git20180213-1 Distribution: experimental Urgency: medium Maintainer: Patrick Matthäi Changed-By: Patrick Matthäi Description: needrestart - check which daemons need to be restarted after library upgrades Closes: 842512 859387 866105 876452 876459 878700 879091 885448 886445 887677 Changes: needrestart (2.11+git20180213-1) experimental; urgency=medium . * New upstream git snapshot. - Possible to override the configured restart mode using the NEEDRESTART_MODE environment variable. Closes: #866105 - Check for pending Intel microcode updates. Closes: #886445 - Ignore special filename mappings used by recent versions of KDE plasmashell. Closes: #879091 - Fix handling of library mappings if target does not exist. Closes: #878700 - Add missing unnamed device major numbers (fix for OpenVZ). Closes: #876452 - Do not call GetTerminalSize() if STDOUT is not a TTY. Closes: #859387 - Fix switch from interactive to list mode if debconf is run noninteractive. Closes: #876459 - Add documentation on restart mode if run non-interactive. Closes: #842512 - Fix typo in man page. Closes: #885448 - Drop merged patch 03-perl-warning. - Drop merged patch 04-ignore-systemd-services. - Drop merged patch 02-install-restart-d. * Add dependency on binutils. Closes: #887677 * Bump debian/compat to level 11. * Bump Standards-Version to 4.1.3 (no changes required). Checksums-Sha1: f81922f08e0ea0f2e34061f8806d81c9386a8dac 1850 needrestart_2.11+git20180213-1.dsc 9ed0f6c7fd7a1a556d2371e532c08c4d
Bug#888000: marked as done (Port from deprecated libnm-glib bindings to libnm)
Your message dated Tue, 13 Feb 2018 15:05:52 +
with message-id
and subject line Bug#888000: fixed in gnome-shell-extension-disconnect-wifi 17-1
has caused the Debian Bug report #888000,
regarding Port from deprecated libnm-glib bindings to libnm
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.)
--
888000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-disconnect-wifi
Version: 3.22.14-1
Severity: serious
Tags: patch
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: libnm
Hi,
the libnm-glib/libnm-util libraries have been deprecated upstream in
favour of libnm (along with their corresponding gir bindings)
Your package uses the old Gir bindings:
disconnect-w...@kgshank.net/extension.js:const NetworkManager =
imports.gi.NetworkManager;
disconnect-w...@kgshank.net/extension.js:const NMClient = imports.gi.NMClient;
disconnect-w...@kgshank.net/extension.js: if (device.get_device_type() !=
NetworkManager.DeviceType.WIFI) {
disconnect-w...@kgshank.net/extension.js: if (device.get_device_type() !=
NetworkManager.DeviceType.WIFI) {
disconnect-w...@kgshank.net/extension.js: = newstate >
NetworkManager.DeviceState.DISCONNECTED;
disconnect-w...@kgshank.net/extension.js:= (newstate ==
NetworkManager.DeviceState.DISCONNECTED)
disconnect-w...@kgshank.net/extension.js: if (device.get_device_type() !=
NetworkManager.DeviceType.WIFI) {
Fortunately, this has already been fixed upstream at
https://github.com/kgshank/gse-disconnect-wifi/commit/5584d98989d25a9c37810896f5e113b4c13b2bdc
https://github.com/kgshank/gse-disconnect-wifi/commit/1e15074bafdee7a20db57b78143d50d1793946f1
https://github.com/kgshank/gse-disconnect-wifi/commit/2f7fcf6a3846fc90eb1d0597415a090d3c3af1ae
Please cherry-pick those patches to make your extension compatible with
newer versions of gnome-shell.
In version 3.26.2-4, I switched gnome-shell over to libnm, which means
your extension is currently non-functional anymore in sid/buster (thus the RC
severity).
Regards,
Michael
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-disconnect-wifi
Source-Version: 17-1
We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-disconnect-wifi, 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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan Carter (supplier of updated
gnome-shell-extension-disconnect-wifi 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, 13 Feb 2018 15:18:30 +0200
Source: gnome-shell-extension-disconnect-wifi
Binary: gnome-shell-extension-disconnect-wifi
Architecture: source all
Version: 17-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter
Changed-By: Jonathan Carter
Description:
gnome-shell-extension-disconnect-wifi - disconnect wifi extension for GNOME
shell
Closes: 888000
Changes:
gnome-shell-extension-disconnect-wifi (17-1) unstable; urgency=medium
.
* New upstream release
- Drop deprecated libnm-glib bindings (Closes: #888000)
* Move VCS to salsa.debian.org
* Update standards version to 4.1.3
* Update compat to level 11
* Update watch file to version 4
* Update copyright years
Checksums-Sha1:
0103feb14f01068c030e83421e98af54a14e1df7 2149
gnome-shell-extension-disconnect-wifi_17-1.dsc
b36fb7d701fa2e1f409f560c2d13162552424ec5 18899
gnome-shell-extension-disconnect-wifi_17.orig.tar.gz
e264c8a7de90dd64870f748389901a4ef6af3f72 1864
gnome-shell-extension-disconnect-wifi_17-1.debian.tar.xz
3c6b7eb56f0201e79680cc04fe39715dbce2e3c6 7312
g
Bug#887189: marked as done (golang-github-docker-docker-dev should depend on e2fsprogs explicitly)
Your message dated Tue, 13 Feb 2018 16:24:06 +0100 with message-id <20180213152406.2hrvnbnn5yg7a...@fatal.se> and subject line Re: Bug#887189: golang-github-docker-docker-dev should depend on e2fsprogs explicitly has caused the Debian Bug report #887189, regarding golang-github-docker-docker-dev should depend on e2fsprogs explicitly 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.) -- 887189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: golang-github-docker-docker-dev Version: 1.13.1~ds2-3 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting there all packages that use e2fsprogs must be identified and gain a dependency on it as e2fsprogs currently is essential. golang-github-docker-docker-dev was identified as potentially needing such a dependency, because it mentions tool names from e2fsprogs in the following files: /usr/share/gocode/src/github.com/docker/docker/pkg/fsutils/fsutils_linux_test.go contains mkfs.ext4. According to file it is a ASCII text /usr/share/gocode/src/github.com/docker/docker/pkg/mount/mountinfo_linux_test.go contains debugfs. According to file it is a ASCII text Please investigate whether these cases are actually uses of a tool from e2fsprogs. Care has been taken to shrink the number of candidates as much as possible, but a few false positives will remain. After doing so, do one of the following: * Add e2fsprogs to Depends. * Add e2fsprogs to Recommends. * Close this bug explaining why e2fsprogs is not used by this package. Once e2fsprogs drops the "Essential: yes" flag, this bug will be upgraded to RC severity. Please note that lintian will warn about such a dependency before lintian 2.5.56. Thanks for your help Helmut --- End Message --- --- Begin Message --- Hello Tianon, On Mon, Feb 12, 2018 at 09:47:03AM -0800, Tianon Gravi wrote: > I agree that this bug as filed doesn't make much sense, but it does > point to one that does make sense IMO, which would be adding the two > packages mentioned (e2fsprogs and xfsprogs) to Suggests over in > docker.io instead (since there are configurations of Docker where it'd > be appropriate and necessary to have those packages installed). Thanks for your feedback. Since we seem to be in agreement I'll close this bug report (via bcc) and for the record copy #887222 which is the bug report where docker.io dependencies are discussed. Lets continue the discussion in that bug report if needed. Regards, Andreas Henriksson--- End Message ---
Bug#888720: marked as done (squid3: CVE-2018-1000027: SQUID-2018:2 Denial of Service issue in HTTP Message processing)
Your message dated Tue, 13 Feb 2018 16:06:23 +
with message-id
and subject line Bug#888720: fixed in squid3 3.5.27-1
has caused the Debian Bug report #888720,
regarding squid3: CVE-2018-127: SQUID-2018:2 Denial of Service issue in
HTTP Message processing
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.)
--
888720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squid3
Version: 3.5.23-5
Severity: important
Tags: security upstream
Hi,
the following vulnerability was published for squid3.
CVE-2018-127[0]:
SQUID-2018:2 Denial of Service issue in HTTP Message processing
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2018-127
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-127
[1] http://www.squid-cache.org/Advisories/SQUID-2018_2.txt
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: squid3
Source-Version: 3.5.27-1
We believe that the bug you reported is fixed in the latest version of
squid3, 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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luigi Gangitano (supplier of updated squid3 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, 13 Feb 2018 15:31:24 +0100
Source: squid3
Binary: squid3 squid squid-dbg squid-common squidclient squid-cgi squid-purge
Architecture: source amd64 all
Version: 3.5.27-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano
Changed-By: Luigi Gangitano
Description:
squid - Full featured Web Proxy cache (HTTP proxy)
squid-cgi - Full featured Web Proxy cache (HTTP proxy) - control CGI
squid-common - Full featured Web Proxy cache (HTTP proxy) - common files
squid-dbg - Full featured Web Proxy cache (HTTP proxy) - Debug symbols
squid-purge - Full featured Web Proxy cache (HTTP proxy) - control utility
squid3 - Transitional package
squidclient - Full featured Web Proxy cache (HTTP proxy) - control utility
Closes: 888719 888720
Changes:
squid3 (3.5.27-1) unstable; urgency=high
.
[ Amos Jeffries ]
* New Upstream Release
.
* debian/{control,rules}
- Add temporary dependency on gcc-6 and g++-6 to workaround FTBFS in
unstable
.
* debian/patches/
- Fix security issue SQUID-2018:1 (CVE-2016-124) (Closes: #888719)
- Fix security issue SQUID-2018:2 (CVE-2016-127) (Closes: #888720)
.
[ Luigi Gangitano ]
* debian/control
- Changed priority to optional for squid3 and squid-dbg
- Removed unneeded Build-Dep on autotools-dev
.
* debian/rules
- Include dpkg-architecture Makefile instead of invoking the binary at
build time
.
* debian/squid.postinst
- Remove recursive chown calls
Checksums-Sha1:
34db42142759bb0c060862eeaece8b2095b0d122 2559 squid3_3.5.27-1.dsc
0cebb9b7ca832994a1b2b440a5ae653a74bc3084 4837850 squid3_3.5.27.orig.tar.gz
98e0fe8f1687296b7946b549268d6b6ede4fb2f9 27300 squid3_3.5.27-1.debian.tar.xz
c38ec122c0fb9056dee19673c30bd39fb4608811 166484 squid-cgi_3.5.27-1_amd64.deb
efdd25466c276b6733bb23d7822e37e590ff129b 285548 squid-common_3.5.27-1_all.deb
f5a15abf17252df634ebe751fdaf90e874a824c6 21590720 squid-dbg_3.5.27-1_amd64.deb
93a516ef257a1bacd5b0670a85ea79d0e7c0aedd 158900 squid-purge_3.5.27-1_amd64.deb
69e172f1eec670b447e497a9d92b64bafa278e06 139844 squid3_3.5.27-1_all.deb
8c257d412ec0e8926c4041a608be275b6af75610 8746 squid3_3.5.27-1_amd64.buildinfo
112b4475d25a7f4c05bf7c22da2860ef88239829 2324000 squid_3.5.27-1_amd64.deb
254d20c9f5cbab072c79703a88663feb2ddfd33f 170564 squidclient_3.5.27-1_amd64.deb
Checksums-Sha256:
73d74d807328e10ca9ec42646360934d3252937d99fcdff02f27d804aad19294 2559
squid3_3.5.27-1.dsc
f6a5f1272000b1c6365652b35f950fd77d091c14076d61812aecac4e90c73b39 4837850
squid3_3.5.27.orig.tar.gz
d0276eccafa6eb5cf435bbe4128baa60d53997b58145
Bug#888719: marked as done (squid3: CVE-2018-1000024: SQUID-2018:1 Denial of Service issue in ESI Response processing)
Your message dated Tue, 13 Feb 2018 16:06:23 +
with message-id
and subject line Bug#888719: fixed in squid3 3.5.27-1
has caused the Debian Bug report #888719,
regarding squid3: CVE-2018-124: SQUID-2018:1 Denial of Service issue in ESI
Response processing
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.)
--
888719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squid3
Version: 3.5.23-5
Severity: important
Tags: security upstream
Hi,
the following vulnerability was published for squid3.
CVE-2018-124[0]:
SQUID-2018:1 Denial of Service issue in ESI Response processing
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2018-124
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-124
[1] http://www.squid-cache.org/Advisories/SQUID-2018_1.txt
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: squid3
Source-Version: 3.5.27-1
We believe that the bug you reported is fixed in the latest version of
squid3, 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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luigi Gangitano (supplier of updated squid3 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, 13 Feb 2018 15:31:24 +0100
Source: squid3
Binary: squid3 squid squid-dbg squid-common squidclient squid-cgi squid-purge
Architecture: source amd64 all
Version: 3.5.27-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano
Changed-By: Luigi Gangitano
Description:
squid - Full featured Web Proxy cache (HTTP proxy)
squid-cgi - Full featured Web Proxy cache (HTTP proxy) - control CGI
squid-common - Full featured Web Proxy cache (HTTP proxy) - common files
squid-dbg - Full featured Web Proxy cache (HTTP proxy) - Debug symbols
squid-purge - Full featured Web Proxy cache (HTTP proxy) - control utility
squid3 - Transitional package
squidclient - Full featured Web Proxy cache (HTTP proxy) - control utility
Closes: 888719 888720
Changes:
squid3 (3.5.27-1) unstable; urgency=high
.
[ Amos Jeffries ]
* New Upstream Release
.
* debian/{control,rules}
- Add temporary dependency on gcc-6 and g++-6 to workaround FTBFS in
unstable
.
* debian/patches/
- Fix security issue SQUID-2018:1 (CVE-2016-124) (Closes: #888719)
- Fix security issue SQUID-2018:2 (CVE-2016-127) (Closes: #888720)
.
[ Luigi Gangitano ]
* debian/control
- Changed priority to optional for squid3 and squid-dbg
- Removed unneeded Build-Dep on autotools-dev
.
* debian/rules
- Include dpkg-architecture Makefile instead of invoking the binary at
build time
.
* debian/squid.postinst
- Remove recursive chown calls
Checksums-Sha1:
34db42142759bb0c060862eeaece8b2095b0d122 2559 squid3_3.5.27-1.dsc
0cebb9b7ca832994a1b2b440a5ae653a74bc3084 4837850 squid3_3.5.27.orig.tar.gz
98e0fe8f1687296b7946b549268d6b6ede4fb2f9 27300 squid3_3.5.27-1.debian.tar.xz
c38ec122c0fb9056dee19673c30bd39fb4608811 166484 squid-cgi_3.5.27-1_amd64.deb
efdd25466c276b6733bb23d7822e37e590ff129b 285548 squid-common_3.5.27-1_all.deb
f5a15abf17252df634ebe751fdaf90e874a824c6 21590720 squid-dbg_3.5.27-1_amd64.deb
93a516ef257a1bacd5b0670a85ea79d0e7c0aedd 158900 squid-purge_3.5.27-1_amd64.deb
69e172f1eec670b447e497a9d92b64bafa278e06 139844 squid3_3.5.27-1_all.deb
8c257d412ec0e8926c4041a608be275b6af75610 8746 squid3_3.5.27-1_amd64.buildinfo
112b4475d25a7f4c05bf7c22da2860ef88239829 2324000 squid_3.5.27-1_amd64.deb
254d20c9f5cbab072c79703a88663feb2ddfd33f 170564 squidclient_3.5.27-1_amd64.deb
Checksums-Sha256:
73d74d807328e10ca9ec42646360934d3252937d99fcdff02f27d804aad19294 2559
squid3_3.5.27-1.dsc
f6a5f1272000b1c6365652b35f950fd77d091c14076d61812aecac4e90c73b39 4837850
squid3_3.5.27.orig.tar.gz
d0276eccafa6eb5cf435bbe4128baa60d53997b58145
Bug#890160: marked as done (ocrfeeder: Please switch to python-gobject-2/python-gi)
Your message dated Tue, 13 Feb 2018 16:06:03 + with message-id and subject line Bug#890160: fixed in ocrfeeder 0.8.1-4 has caused the Debian Bug report #890160, regarding ocrfeeder: Please switch to python-gobject-2/python-gi 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.) -- 890160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocrfeeder Version: 0.8.1-3 Severity: important Tags: buster sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: pygobject-trans-rm Dear Maintainer, Your package ocrfeeder depends against the python-gobject transitional package. We would like to drop this transitional package for buster. Could you please switch to either python-gobject-2 (if your package is using the old python binding for GObject) or to python-gi (if your package is using the new gobject-introspection one). Please don't hesitate to contact me if you have any questions. Kind Regards, Laurent Bigonville --- End Message --- --- Begin Message --- Source: ocrfeeder Source-Version: 0.8.1-4 We believe that the bug you reported is fixed in the latest version of ocrfeeder, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Garcia (supplier of updated ocrfeeder 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: Tue, 13 Feb 2018 17:48:08 +0200 Source: ocrfeeder Binary: ocrfeeder Architecture: source Version: 0.8.1-4 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Alberto Garcia Description: ocrfeeder - Document layout analysis and optical character recognition system Closes: 890160 Changes: ocrfeeder (0.8.1-4) unstable; urgency=medium . * Don't require python-gobject (Closes: #890160). - debian/control: remove the build dependency. - skip-python-gobject.patch: remove the check during configure. * debian/copyright: - Update copyright years. - Use HTTPS for the format URL. Checksums-Sha1: c83a4f03d3a149640a21ba2bd8d3c0e19f34de5e 2267 ocrfeeder_0.8.1-4.dsc c3dcd210c73de7ec239e4d8b78eddc240542dc37 5984 ocrfeeder_0.8.1-4.debian.tar.xz c1e5aedec72cdd3547bd3af4e50a9e5316f3fbc5 12447 ocrfeeder_0.8.1-4_source.buildinfo Checksums-Sha256: 16b61e304eee6025562c99faa2a628187ecac187b398f94d9ed3cee868eb6811 2267 ocrfeeder_0.8.1-4.dsc 32d642673ab5a24b93079138ca8faf43c6d9080b401f78ecd45ca23c31a43134 5984 ocrfeeder_0.8.1-4.debian.tar.xz d811a58caae28e5d55bfe83962baf6affc587354026f5afc42061f549be269b7 12447 ocrfeeder_0.8.1-4_source.buildinfo Files: 1b5a553f9849a3c8c69f0f58df8670fc 2267 graphics optional ocrfeeder_0.8.1-4.dsc ed4293a4d0f17e2017ecec853a5f4ef6 5984 graphics optional ocrfeeder_0.8.1-4.debian.tar.xz 7c70cd3f720104350d161ddc52ffad7b 12447 graphics optional ocrfeeder_0.8.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEG4Kq8pR5Ln9Vhk8+vjIZrz7UE0EFAlqDCQUACgkQvjIZrz7U E0Et+hAAvA4E000gz6m/FPVYNCNtRbAR/zmPsOrWe5BqLb28To0Mhw/nRZtfy7Pe wicxa6lJrjAeNbaK2rf/lQfeUB4V7JGQPG7vyHRcRdTfEIkBo1jJqUDwYg8yoCxy b5JwYwpUCBnSujLqajb7je43oET0kGBzYm8AO246M+9CWjLyeYu5n0QdcJFTV4hH 3BBg+SmwVvI2XT4ssVkQbIRXggdeAErc7hXEkdz4RPGpuNqFHhtUbn+p4v4Rc3Mk KVCr0epMkHTpu+nCxyLYbLPkLWUv9u1qhM6AyjUG4DWjNj9GTvY6qkaVgQHfDAQu eX6Kf2lPHX/WJrIoQlPJFs7KLvzrzBKE2qjz/38mtRV4GwmqlLrN62F108IrwbAs BbDZQZk1XRZzJg/xbZn2DMnrxzL2ZowJYjAFd9vqFicBn1W1r3XObs4zGfX76z48 UeAU6c/h+gOxbHyYwJyrjAXK4rFaUd9M6Sajlq/fj6v4rMGxiQ9umf/zTJ9u8zhN WwQ0Ik/KIkP9up+W7FajtMQ5+a11s9ZQxEVbQoxJGKLmVqpodeYRLp5YkcuktDuc uJKAfCOBS26w46xcGC9stJ9EWPL0ZWSUzrlN5JW5N4oHSYx7azfhJUTQrIcBxP1J uczjw/koRMz+rbcUZk9gC3Glebx/vUir2xojl5CbBmoaxoi9UxE= =N7UQ -END PGP SIGNATURE End Message ---
Bug#889356: marked as done (Updating the httpcomponents-client Uploaders list)
Your message dated Tue, 13 Feb 2018 16:50:23 + with message-id and subject line Bug#889356: fixed in httpcomponents-client 4.5.5-1 has caused the Debian Bug report #889356, regarding Updating the httpcomponents-client 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.) -- 889356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: httpcomponents-client Version: 4.3.5-2 4.5.3-1 4.5.4-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Damien Raude-Morvan has not been working on the httpcomponents-client package for quite some time. 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 --- Source: httpcomponents-client Source-Version: 4.5.5-1 We believe that the bug you reported is fixed in the latest version of httpcomponents-client, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated httpcomponents-client package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Feb 2018 17:26:39 +0100 Source: httpcomponents-client Binary: libhttpclient-java libhttpmime-java Architecture: source Version: 4.5.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libhttpclient-java - HTTP/1.1 compliant HTTP agent implementation libhttpmime-java - HTTP/1.1 compliant HTTP agent implementation - MIME extension Closes: 889356 Changes: httpcomponents-client (4.5.5-1) unstable; urgency=medium . * Team upload. * New upstream release * Removed Damien Raude-Morvan from the uploaders (Closes: #889356) * Switch to debhelper level 11 Checksums-Sha1: 0758a64d041f1fbf2713d10cc634c32842df001b 2480 httpcomponents-client_4.5.5-1.dsc 89f8a0cc88a6133db172b6f5944ac3fa8e7439a0 586204 httpcomponents-client_4.5.5.orig.tar.xz 27ffe941a1d0ec3a90e15305585e84d58c572a01 10216 httpcomponents-client_4.5.5-1.debian.tar.xz e58a54281956539acea69df3dd736a7c7fc07b8d 15463 httpcomponents-client_4.5.5-1_source.buildinfo Checksums-Sha256: 0921b001f337bf7a18f71bb02186f4c0372eb64fd068376b87c7856d9315c366 2480 httpcomponents-client_4.5.5-1.dsc 76a5e38102591d28e1938fee1aa773cecc28799839f5c5f92484cdab7712b139 586204 httpcomponents-client_4.5.5.orig.tar.xz c3cfbff942c5134b406cbd9fe936d60e3c70f3f5e3a29941e9f3ef0d0c241013 10216 httpcomponents-client_4.5.5-1.debian.tar.xz 4f582eb42051b94878177db2cca04755f7829737a78aca9d9e0dbd1f67394ef5 15463 httpcomponents-client_4.5.5-1_source.buildinfo Files: af5f485d0937fc147e5c55d6a3813be5 2480 java optional httpcomponents-client_4.5.5-1.dsc 446a9da9875f8573772e481015d5395a 586204 java optional httpcomponents-client_4.5.5.orig.tar.xz af1128bf9983baf2679f70730e46fac2 10216 java optional httpcomponents-client_4.5.5-1.debian.tar.xz bb219b40ccbd9781b5b75d23bc9b9a37 15463 java optional httpcomponents-client_4.5.5-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlqDEdYSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsuqEP/0NYmTR1E9zxcHpi2ceTTF6M+s5q5b0W nvgqWA3HTSjgJ9MTGwy1bcmkK+nJEiQPy+BdsoRK2U3fLpKR8NJ/zz+cn9OtoGiH aCLV/8qBbcYeCMxnXHagoVskJAvrCTpzf0ERyMdz4BI3Hw/6wTgAGtCQ+Xscz70T 9AMgUCPMddG852xeqdwe2DtmBGvn2nxahNnmNCqgZlwwtJohCEaV1P39zXVwPwm3 s6d5tWe/FcvX7qKrytrLP1mzmDbDvBW2NrUpgkIn4A1z/+oMONkUc2NsNm4UOxJ5 NmD2Ga39zt+3jJt95t/5v+KYpaEowI2rulJiskMIqYCr4WPFz/7m/aRLbAjXWydu uPf1egfdQxOu64MzI+DJAFyF2eLkp5QEoTK2s5PUz7QP+wNR2EgQlfPyYjE8U2wL VWjC4nzE0KMvB6XOTKL1LARfsWbNKmksOc7Hoxa8xhiFqURbYOc9AefaFlJXv+5L Cg301Eq9tvnkyAeqvqTgLUf8TWZv0wNkvfWt0VbbOAyYzLDMxTRobbQYPwe+825H jTPvybbJ/LdTb7mGabEmAzVO2CTZbmZt7S5Pc0ps4mr+XLQdVkVsFSafzIX3KTB6 TgX2oBpibOLBoOUcUXW1vaPIAoNbbL8s8bosAhDSuhvdtHsHdwrImI11XtoE/1nn vss4KhafgDWs =Rnh9 -END PGP SIGNATURE End Messag
Bug#887952: marked as done (Revert to Arch:all)
Your message dated Tue, 13 Feb 2018 16:50:15 + with message-id and subject line Bug#887952: fixed in golang-github-jacobsa-crypto 0.0~git2016.0.293ce0c+dfsg1-9 has caused the Debian Bug report #887952, regarding Revert to Arch:all 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.) -- 887952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: golang-github-jacobsa-crypto Version: 0.0_git2016.0.293ce0c+dfsg1-5 Severity: serious For a brief time, the package is being marked Arch:any to produce detailed logs. We would like to support additional release architectures, but the package is Golang source (and autopkgtest did not run on the affected architectures). The package should be marked Arch:all before being allowed into testing. --- End Message --- --- Begin Message --- Source: golang-github-jacobsa-crypto Source-Version: 0.0~git2016.0.293ce0c+dfsg1-9 We believe that the bug you reported is fixed in the latest version of golang-github-jacobsa-crypto, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felix Lechner (supplier of updated golang-github-jacobsa-crypto 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, 13 Feb 2018 08:28:43 -0800 Source: golang-github-jacobsa-crypto Binary: golang-github-jacobsa-crypto-dev Architecture: source Version: 0.0~git2016.0.293ce0c+dfsg1-9 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Felix Lechner Description: golang-github-jacobsa-crypto-dev - Some Go cryptography routines that are not included in the Go sta Closes: 887952 Changes: golang-github-jacobsa-crypto (0.0~git2016.0.293ce0c+dfsg1-9) unstable; urgency=medium . * Fixed pointer size detection in autopkgtest * Marked package Arch:all (Closes: #887952) * Removed unused lintian override Checksums-Sha1: ba07b5fe2fc9ac03f3700911848c3433746ada9d 2759 golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9.dsc 9abaed2ed8fe6809d1c02efc28b5f2100be775da 4472 golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9.debian.tar.xz 4c8231c13374e1d62794ca14d4c94b676c271055 6236 golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9_source.buildinfo Checksums-Sha256: 63f86d1f6fa76063fb0d130cc85e5caaaf22e0e48404b58219ae77c088abca33 2759 golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9.dsc 458dbd9060d46140c5533484c40af7c055d551878f2f28c439da9c4b0a2a947f 4472 golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9.debian.tar.xz b5ad642723fe5bcf3b348be112104feb56f0fccbd2dfb5a7740b4430c62bb56d 6236 golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9_source.buildinfo Files: 28b51b84223c78cd58e5284a153ccf70 2759 devel optional golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9.dsc fa4203b6c968e252ad8135448c762553 4472 devel optional golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9.debian.tar.xz df570c5190797e1fc48f36b76eb70986 6236 devel optional golang-github-jacobsa-crypto_0.0~git2016.0.293ce0c+dfsg1-9_source.buildinfo -BEGIN PGP SIGNATURE- iQKvBAEBCgCZFiEE8E0cIgLi+g0BiFTarFipTxFhjuAFAlqDElxfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYw NEQxQzIyMDJFMkZBMEQwMTg4NTREQUFDNThBOTRGMTE2MThFRTAbHGZlbGl4Lmxl Y2huZXJAbGVhc2UtdXAuY29tAAoJEKxYqU8RYY7gLtkP/3eaIK86qf1PJkm59CXb 0BinUVjc67yO1QqDXr3QcIeOHbDVHQImhEJM3Q0QacJ9zQTtou7y80/u9k5od6c0 hOSw9k2a1qTG8/VSsoij+dM27W7az6k463iyT2x8w+i96RY0emEn+tf+3qf6gmX+ IecK4Ydrm9dXQO4cS+QWK93Zj09mSMUqXsPIFnkXmUNej/xKOByD2mKFbcI3Mg/1 SLXoM6gGOMjBF2ajCtOuJ8ngaUY/77eEVcSxCpBfH9mAASO1kcqt7U96LNRLu2ee GKJk/TEIZe5OqlYXiY1JPGOL4QwdTgdt7CJQL2diOpn/6EPCkAByWnJuUWG0z2dm Nq35wfdefIYFYTpe3swBC+V+jaapS4IA87qX0Q3psJO8KslyAZxRG5gQ625N1lzb dd+9bfxADVyLuENaXy1ofChIJkUWCRlkvUIGsplMtWiuDLpWx3c/smWk8Wy7CquN QiFlYQuf/5QlKK5qHH/ldPBB58f8ZXIQKvTsVoZ4cwMjDEr6+Y8/Xbo2aKiZzMNO qRA3zJA7vqRkUMMBUXuI1IEG1RXZtInLSTTyWCmszUtJ/ixGUSlkiAEuRKMfzrgn xehV76To6XM5063MwsAKO9Zg6OpvT0QCdjDCOIv/Awn4Xc
Bug#853651: marked as done (sarg: ftbfs with GCC-7)
Your message dated Tue, 13 Feb 2018 17:34:30 + with message-id and subject line Bug#853651: fixed in sarg 2.3.11-1 has caused the Debian Bug report #853651, regarding sarg: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 853651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sarg Version: 2.3.10-2 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The severity of this report may be raised before the buster release. There is no need to fix this issue in time for the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc7-20170126/sarg_2.3.10-2_unstable_gcc7.log The last lines of the build log are at the end of this report. To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-7/porting_to.html [...] checking for struct sockaddr_storage.ss_len... no checking size of rlim_t... 8 checking whether LLONG_MAX is declared... yes using /usr/share/sarg as the directory to install sarg-php using /usr/share/fonts/truetype/ttf-dejavu as the directory of the fonts using /usr/share/sarg/images as the directory of the images checking for /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl... no checking for /usr/share/sgml/docbook/xsl-stylesheets/manpages/docbook.xsl... no checking for /usr/share/sgml/docbook/stylesheet/xsl/docbook-xsl/html/onechunk.xsl... no checking for /usr/share/sgml/docbook/xsl-stylesheets/html/onechunk.xsl... no configure: creating ./config.status config.status: creating Makefile config.status: creating po/Makefile.in config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode, --disable-dependency-tracking configure: pcre.h was not found so the regexp won't be available in the hostalias make[1]: Leaving directory '/<>' dh_auto_build make -j1 make[1]: Entering directory '/<>' gcc -c -I. -Wdate-time -D_FORTIFY_SOURCE=2 -DBINDIR=\"/usr/bin\" -DSYSCONFDIR=\"/etc/sarg\" -DFONTDIR=\"/usr/share/fonts/truetype/ttf-dejavu\" -DIMAGEDIR=\"/usr/share/sarg/images\" -DSARGPHPDIR=\"/usr/share/sarg\" -DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE_NAME=\"sarg\" -DPACKAGE_TARNAME=\"sarg\" -DPACKAGE_VERSION=\"2.3.10\" -DPACKAGE_STRING=\"sarg\ 2.3.10\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_DIRENT_H=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_TIME_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_NETDB_H=1 -DHAVE_ARPA_INET_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_CTYPE_H=1 -DHAVE_ERRNO_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_STDARG_H=1 -DHAVE_INTTYPES_H=1 -DHA VE_LIMITS_H=1 -DHAVE_LOCALE_H=1 -DHAVE_EXECINFO_H=1 -DHAVE_MATH_H=1 -DHAVE_LIBINTL_H=1 -DHAVE_LIBGEN_H=1 -DHAVE_STDBOOL_H=1 -DHAVE_GETOPT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_GD_H=1 -DHAVE_GDFONTL_H=1 -DHAVE_GDFONTT_H=1 -DHAVE_GDFONTS_H=1 -DHAVE_GDFONTMB_H=1 -DHAVE_GDFONTG_H=1 -DHAVE_LDAP_H=1 -DHAVE_ICONV=1 -DICONV_CONST= -DHAVE_ICONV_H=1 -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DHAVE_FOPEN64=1 -D_LARGEFILE64_SOURCE=1 -DHAVE_BZERO=1 -DHAVE_BACKTRACE=1 -DHAVE_SYMLINK=1 -DHAVE_LSTAT=1 -DHAVE_GETNAMEINFO=1 -DHAVE_GETADDRINFO=1 -DHAVE_MKSTEMP=1 -DSIZEOF_RLIM_T=8 -DRLIM_STRING=\"%lli\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wall -Wno-sign-compar
Bug#850624: marked as done (Manpage sarg.1 installed into wrong directory)
Your message dated Tue, 13 Feb 2018 17:34:30 +
with message-id
and subject line Bug#850624: fixed in sarg 2.3.11-1
has caused the Debian Bug report #850624,
regarding Manpage sarg.1 installed into wrong directory
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.)
--
850624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sarg
Version: 2.3.10-2
Severity: normal
Tags: patch
Currently, sarg ships with the following manpages:
dpkg -c sarg_2.3.10-2_amd64.deb | grep 'usr/share/man' | grep '\.gz$'
/usr/share/man/man1/sarg-reports.1.gz
/usr/share/man/man1/sarg.1.gz
/usr/share/man/man1/man1/sarg.1.gz
man1/man1/sarg.1.gz is in the wrong directory and cannot be read using
man(1).
The following patch fixes the issue:
--- debian/rules.O 2017-01-08 16:59:43.305936141 +0100
+++ debian/rules2017-01-08 16:59:48.325872073 +0100
@@ -23,7 +23,6 @@
--infodir=\$${prefix}/share/info \
--bindir=/usr/bin \
--sysconfdir=/etc/sarg \
- --mandir=/usr/share/man/man1 \
--enable-fontdir=/usr/share/fonts/truetype/ttf-dejavu \
--enable-imagedir=/usr/share/sarg/images \
--enable-sargphp=/usr/share/sarg
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel
Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: sarg
Source-Version: 2.3.11-1
We believe that the bug you reported is fixed in the latest version of
sarg, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luigi Gangitano (supplier of updated sarg 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, 13 Feb 2018 17:12:57 +0100
Source: sarg
Binary: sarg
Architecture: source amd64
Version: 2.3.11-1
Distribution: unstable
Urgency: medium
Maintainer: Luigi Gangitano
Changed-By: Luigi Gangitano
Description:
sarg - squid analysis report generator
Closes: 845455 845546 850624 853651 872425
Changes:
sarg (2.3.11-1) unstable; urgency=medium
.
* New upstream version
- Fixes FTBFS with GCC 7 (Closes: #853651)
- Removed gettext patch integrated upstream
.
* debian/control
- Fix man directory (Closes: #850624, thanks to Michael Stapelberg)
.
* debian/sarg-reports{,.1,.conf}
- Added EXCLUDELOG3 filter (Closes: #872425, thanks to Matus UHLAR)
- Added documentation (Closes: #845455, thanks to r...@chardmore.net)
- Added lastlog options (Closes: #845546, thanks to r...@chardmore.net)
.
* debian/patches/0002-fix-build-errors.patch
- Fix more build errors
.
* debian/rules
- Removed autotools-dev debhelper calls
Checksums-Sha1:
0e9ef41a7457015a36854ed1e16c57cb34be3b24 1758 sarg_2.3.11-1.dsc
c535d1534dd0c7e3a3725d98eb0dd50246e489b0 1344002 sarg_2.3.11.orig.tar.gz
96100cefaccd0a9f546056371ca88c5d32a06cd2 21800 sarg_2.3.11-1.debian.tar.xz
90813f1297d66db578473672500d1f7c27ca4620 281712 sarg-dbgsym_2.3.11-1_amd64.deb
a131c6cff9cc8c15f6d2fa9c2f9cfb3b8910f8a0 6818 sarg_2.3.11-1_amd64.buildinfo
1cc299b32e03878ac1435e6454db579ad4ffaa72 170176 sarg_2.3.11-1_amd64.deb
Checksums-Sha256:
d220cbb646733a343f69ea4d3f0f3760ac93fabe15cc3dc716a63aea94253bf5 1758
sarg_2.3.11-1.dsc
499f698d4bba7d116dada83232a414adb2727fd8f6c048a022208848116fe4f3 1344002
sarg_2.3.11.orig.tar.gz
6afbf233acfebe38a934df2a2f10783b42dab7ec87f59665595dd8b0da8a727a 21800
sarg_2.3.11-1.debian.tar.xz
ba062bd2bea7fe082935ddc98219073c56d9ff61e0179a5bd88a84441017f945 281712
sarg-dbgsym_2.3.11-1_amd64.deb
6a0ba52effaded9cf49154c9e1ac60d2b337e6963dc42a6b7a82a3dc3c6771e7 6818
sarg_2.3.11-1_amd64.buildinfo
ddae2b881c10ac95d7d54b09ca50a7c300a0003d
Bug#872425: marked as done (skip "Period covered by log files::" from cron output)
Your message dated Tue, 13 Feb 2018 17:34:30 +
with message-id
and subject line Bug#872425: fixed in sarg 2.3.11-1
has caused the Debian Bug report #872425,
regarding skip "Period covered by log files::" from cron output
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.)
--
872425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sarg
Version: 2.3.2-2
The sarg-reports already filters out lines containing text in EXCLUDELOG1 and
EXCLUDELOG2 variables:
EXCLUDELOG1="SARG: No records found"
EXCLUDELOG2="SARG: End"
I'm getting mail from the only line left from output:
/etc/cron.daily/sarg:
SARG: Period covered by log files: 16/08/2017-16/08/2017
please filter out this too.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I don't have lysdexia. The Dog wouldn't allow that.
--- End Message ---
--- Begin Message ---
Source: sarg
Source-Version: 2.3.11-1
We believe that the bug you reported is fixed in the latest version of
sarg, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 872...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luigi Gangitano (supplier of updated sarg 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, 13 Feb 2018 17:12:57 +0100
Source: sarg
Binary: sarg
Architecture: source amd64
Version: 2.3.11-1
Distribution: unstable
Urgency: medium
Maintainer: Luigi Gangitano
Changed-By: Luigi Gangitano
Description:
sarg - squid analysis report generator
Closes: 845455 845546 850624 853651 872425
Changes:
sarg (2.3.11-1) unstable; urgency=medium
.
* New upstream version
- Fixes FTBFS with GCC 7 (Closes: #853651)
- Removed gettext patch integrated upstream
.
* debian/control
- Fix man directory (Closes: #850624, thanks to Michael Stapelberg)
.
* debian/sarg-reports{,.1,.conf}
- Added EXCLUDELOG3 filter (Closes: #872425, thanks to Matus UHLAR)
- Added documentation (Closes: #845455, thanks to r...@chardmore.net)
- Added lastlog options (Closes: #845546, thanks to r...@chardmore.net)
.
* debian/patches/0002-fix-build-errors.patch
- Fix more build errors
.
* debian/rules
- Removed autotools-dev debhelper calls
Checksums-Sha1:
0e9ef41a7457015a36854ed1e16c57cb34be3b24 1758 sarg_2.3.11-1.dsc
c535d1534dd0c7e3a3725d98eb0dd50246e489b0 1344002 sarg_2.3.11.orig.tar.gz
96100cefaccd0a9f546056371ca88c5d32a06cd2 21800 sarg_2.3.11-1.debian.tar.xz
90813f1297d66db578473672500d1f7c27ca4620 281712 sarg-dbgsym_2.3.11-1_amd64.deb
a131c6cff9cc8c15f6d2fa9c2f9cfb3b8910f8a0 6818 sarg_2.3.11-1_amd64.buildinfo
1cc299b32e03878ac1435e6454db579ad4ffaa72 170176 sarg_2.3.11-1_amd64.deb
Checksums-Sha256:
d220cbb646733a343f69ea4d3f0f3760ac93fabe15cc3dc716a63aea94253bf5 1758
sarg_2.3.11-1.dsc
499f698d4bba7d116dada83232a414adb2727fd8f6c048a022208848116fe4f3 1344002
sarg_2.3.11.orig.tar.gz
6afbf233acfebe38a934df2a2f10783b42dab7ec87f59665595dd8b0da8a727a 21800
sarg_2.3.11-1.debian.tar.xz
ba062bd2bea7fe082935ddc98219073c56d9ff61e0179a5bd88a84441017f945 281712
sarg-dbgsym_2.3.11-1_amd64.deb
6a0ba52effaded9cf49154c9e1ac60d2b337e6963dc42a6b7a82a3dc3c6771e7 6818
sarg_2.3.11-1_amd64.buildinfo
ddae2b881c10ac95d7d54b09ca50a7c300a0003d9fad4df529db96c7e8e65b2d 170176
sarg_2.3.11-1_amd64.deb
Files:
12deda90f9a61d8d58c58f637027e2e4 1758 web optional sarg_2.3.11-1.dsc
5366f3a9fe4354043b43700362c5e84e 1344002 web optional sarg_2.3.11.orig.tar.gz
d8ed7f0c614434a60e6e5106b4f78abd 21800 web optional sarg_2.3.11-1.debian.tar.xz
017f2b0241f7598da7d6c1bf073a761c 281712 debug optional
sarg-dbgsym_2.3.11-1_amd64.deb
2feb7183197f718bdffc883d694d7a2c 6818 web optional
sarg_2.3.11-1_amd64.buildinfo
19db5157bd868e6b084b297818ff8c04 170176 web optional sarg_2.3.11-1_amd64.deb
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEjUhaNf8ebreQ5Q9tAoTyDCupfO0FAlqDHjQACgkQAoTyDCup
fO1nVxAAqjkpS6brbEMiMe+GIjjrnIU16QfMBWo5EVUZr2roMWcCp/90V+dkDy
Bug#845455: marked as done (sarg: Documentation update needed for sarg-reports)
Your message dated Tue, 13 Feb 2018 17:34:29 + with message-id and subject line Bug#845455: fixed in sarg 2.3.11-1 has caused the Debian Bug report #845455, regarding sarg: Documentation update needed for sarg-reports 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.) -- 845455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sarg Version: 2.3.10-2 Severity: minor Dear Maintainer, I have been trying to set up sarg and while researching solutions to my problems I came across bug 818429 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818429) whose proposed fix was merged into the version this report relates to. The fix adds functionality but documentation (both within the script /usr/sbin/sarg-reports and the manpage) has not been updated and I imagine that users may not understand that only minimal configuration changes are required to make things work in a useful way. In fact it seems that the Debian package maintainers have made several changes to the sarg-reports script over time (I haven't looked at the full change log) as can be seen by comparing the distribution version with the openSUSE version of the same file (https://build.opensuse.org/package/view_file/openSUSE:Factory/sarg/sarg-reports?expand=1) which carries the same version number. I would like to propose changes to the internal documentation of the script (a patch file follows) and to the man page (changes to the text alone follow, in patch format - I don't have experience working with man pages). The revised version number is only a suggestion, of course; I assume you will determine an appropriate version number. It seems to me that fixing the documentation would go some way towards solving the problem raised in bug 369693 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369693), at least as far as sarg is concerned, and especially for users of sarg-reports. -- --- sarg-reports +++ sarg-reports.proposed @@ -6,7 +6,7 @@ # - martijn # - Stas Degteff https://sourceforge.net/users/stas_degteff/ -VER=20050202 +VER=debian-sarg-2.3.10-2 ## What is this? # sarg-reports (this file) is a simple bash script written to automate @@ -43,11 +43,14 @@ #30 02 1 * * sarg-reports monthly #--- END ROOT CRONTAB --- # -#REMEMBER: if you use logrotate, configure it to rotate the logs within MONTHLY basis, -# AFTER sarg-reports created the monthly html report. +#REMEMBER: if you use logrotate, configure it to retain enough logs to ensure availability +# of data for the longest period for which you need a report. +# See https://sourceforge.net/p/sarg/wiki/Keeping%20enough%20log%20to%20process/ +# This version of sarg-reports will use the log file defined in sarg.conf and also +# prior log files which have been rotated out of that location # 3) Customize the following variables: -#(Please, configure accurately the sarg.conf file before) +#(Please, configure accurately the sarg-reports.conf file before) # #(SARG) The sarg executable location # (CONFIG) The sarg main configuration file location @@ -299,6 +302,9 @@ ## HISTORY: +# debian-sarg-2.3.10-2 - use all rotated log files, pass through options from command line +# debian-sarg-? - added reports_autorm function (not used) +# ... - ? # 20050502 - Stas Degteff added support for non latin Charset and added support for OpenBSD # 20030826 - FreeBSD support (thanks to martijn to let me coding on your FreeBSD server :-)) # 20030715 - Some cleanups @@ -314,6 +320,3 @@ # doesn't like this script do: "7 days ago to yesterday" # - Monthly recognition isn't so elegant (is very ugly, i know) # - Suggestions are welcome :-) -# - If you Rotate the squid logs before sarg-reports will run, -# it will not create any html reports -# (TIPS: Rotate the logs after sarg-reports) -- --- sarg-reports-manpage +++ sarg-reports-manpage.proposed @@ -8,7 +8,7 @@ This manual page documents briefly the sarg-reports command. sarg-reports is a script written to automate the SARG (a powerful squid - log analyzer) reports and log management. Sarg it self, provide to end + log analyzer) reports and log management. Sarg itself, provides to end user a generic interface to create reports based on sq
Bug#845546: marked as done (sarg: Proposal for lastlog feature in sarg-reports - patch provided)
Your message dated Tue, 13 Feb 2018 17:34:29 +
with message-id
and subject line Bug#845546: fixed in sarg 2.3.11-1
has caused the Debian Bug report #845546,
regarding sarg: Proposal for lastlog feature in sarg-reports - patch provided
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.)
--
845546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sarg
Version: 2.3.10-2
Severity: wishlist
Dear Maintainer,
The patches below (two of which are diffs from the revised versions I proposed
in bug 845455) include the following proposed changes:
1. Configuration option for number of saved logs per report type
It seems to me that surely I'm not the only one who would like to keep
different numbers of different types of report.
At the same time, different people will have different history requirements.
sarg-reports uses the same sarg.conf for all types of reports, but sarg allows
override of the lastlog setting by using the --lastlog= switch.
The change made in 2.3.10-2 does allow a user (should he/she wish) to pass this
switch to sarg by adjusting the cron jobs which the Debian sarg package
installs for sarg-reports.
However, I reckon that this is a common-enough requirement to justify adding
dedicated settings in sarg-reports.conf.
2. Setting of distinct temporary directory for each run of the script, per
recommendation from Frederic Marchal in case of overlap of cron jobs.
References:
https://sourceforge.net/p/sarg/discussion/363374/thread/efb2f9e9/#3cf7
https://sourceforge.net/p/sarg/discussion/363374/thread/efb2f9e9/#7d4d
I acknowledge that my "rm -rf $TMPDIR" may be a bad idea - I'm not sure how
best to make that safe.
Further, I suspect that my patch in the previous bug may have been faulty as I
had problems applying it - I hope you could work with it and that these ones
are also good enough.
--
--- sarg-reports.proposed
+++ sarg-reports.proposed-with-lastlog
@@ -6,7 +6,7 @@
# - martijn
# - Stas Degteff https://sourceforge.net/users/stas_degteff/
-VER=debian-sarg-2.3.10-2
+VER=debian-sarg-2.3.10-2-with-lastlog
## What is this?
# sarg-reports (this file) is a simple bash script written to automate
@@ -55,6 +55,9 @@
#(SARG) The sarg executable location
# (CONFIG) The sarg main configuration file location
# (HTMLOUT) Location where will be saved the reports
+# (LASTLOGDAILY) Number of previous daily reports to keep (affects "today"
and "manual" logs too)
+# (LASTLOGWEEKLY) Number of previous weekly reports to keep
+# (LASTLOGMONTHLY) Number of previous monthly reports to keep
# (PAGETITLE) The title of main index page
# (LOGOIMG) Image logo to view in main index page
#(LOGOLINK) HTTP web page link of logo
@@ -110,6 +113,7 @@
# TEMP Files
TMPFILE=`/bin/mktemp`
ERRORS="${TMPFILE}.errors"
+TMPDIR=`/bin/mktemp -d`
# Date Calc
MANUALDATE=$2
@@ -210,10 +214,15 @@
{
cat $ERRORS | grep -v "$EXCLUDELOG1" | grep -v "$EXCLUDELOG2"
rm -f $TMPFILE*
+ rm -rf $TMPDIR
}
manual ()
{
+ if [ -n "$LASTLOGDAILY" ]
+then
+ LASTLOG="--lastlog=$LASTLOGDAILY"
+ fi
DAILYOUT=$HTMLOUT/$DAILY
mkdir -p $DAILYOUT
create_index_html
@@ -221,43 +230,59 @@
then
echo "No date given, please specify a valid date (DD/MM/)"
else
- $SARG -f $CONFIG -d $MANUALDATE -o $DAILYOUT ${@} ${ACCESS_LOG}*
+ $SARG -f $CONFIG -w $TMPDIR -d $MANUALDATE -o $DAILYOUT $LASTLOG ${@}
${ACCESS_LOG}*
fi
}
today ()
{
+ if [ -n "$LASTLOGDAILY" ]
+then
+ LASTLOG="--lastlog=$LASTLOGDAILY"
+ fi
DAILYOUT=$HTMLOUT/$DAILY
mkdir -p $DAILYOUT
create_index_html
- $SARG -f $CONFIG -d $TODAY -o $DAILYOUT ${@} ${ACCESS_LOG}* >$ERRORS 2>&1
+ $SARG -f $CONFIG -w $TMPDIR -d $TODAY -o $DAILYOUT $LASTLOG ${@}
${ACCESS_LOG}* >$ERRORS 2>&1
exclude_from_log
}
daily ()
{
+ if [ -n "$LASTLOGDAILY" ]
+then
+ LASTLOG="--lastlog=$LASTLOGDAILY"
+ fi
DAILYOUT=$HTMLOUT/$DAILY
mkdir -p $DAILYOUT
create_index_html
- $SARG -f $CONFIG -d day-1 -o $DAILYOUT ${@} ${ACCESS_LOG}* >$ERRORS 2>&1
+ $SARG -f $CONFIG -w $TMPDIR -d day-1 -o $DAILYOUT $LASTLOG ${@}
${ACCESS_LOG}* >$ERRORS 2>&1
exclude_from_log
}
weekly ()
{
+ if [ -n "$LASTLOGWEEKLY" ]
+then
+ LASTLOG="--lastlog=$LASTLOGWEEKLY"
+ fi
WEEKLYOUT=$HTMLOUT/$WEEKLY
mkdir -p $WEEKLYOUT
create_index_html
- $SARG -f $CONFIG -d week-1 -o $WEEKLYOUT ${@} ${ACCESS_LOG}* >$ERRORS 2>&1
+ $SARG -f $CONFIG -w $
Bug#880782: marked as done (sarg build depends on removed libgd2*-dev provides)
Your message dated Tue, 13 Feb 2018 17:46:19 + with message-id <010201619046437a-e17c2419-a70f-4617-ae75-01c1113f9f2d-000...@eu-west-1.amazonses.com> and subject line Closing bug has caused the Debian Bug report #880782, regarding sarg build depends on removed libgd2*-dev provides 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.) -- 880782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sarg Version: 2.3.10-2 Severity: serious Tags: buster sid The following packages have unmet dependencies: builddeps:sarg : Depends: libgd2-noxpm-dev but it is not installable or libgd2-xpm-dev but it is not installable Please update the build dependency to libgd-dev. --- End Message --- --- Begin Message --- Version: 2.3.10-3 Fixed in not-uploaded version -- Luigi Gangitano -- mailto:lu...@debian.org>> -- mailto:gangit...@lugroma3.org>> GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5 0F6D 0284 F20C 2BA9 7CED --- End Message ---
Bug#659704: marked as done (dtc-xen: [INTL:nl] Dutch translation of debconf templates)
Your message dated Tue, 13 Feb 2018 19:04:17 + with message-id and subject line Bug#659704: fixed in dtc-xen 0.5.17-1.2 has caused the Debian Bug report #659704, regarding dtc-xen: [INTL:nl] Dutch translation of debconf templates 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.) -- 659704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dtc-xen Severity: wishlist Tags: patch l10n Hello, Attached is the updated Dutch translation of the dtc-xen debconf templates. Please include it in your next upload. Regards, -- Jeroen Schot # Dutch translation of dtc-xen debconf templates. # Copyright (C) 2008-2012 THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the dtc-xen package. # Bart Cornelis , 2008. # Jeroen Schot , 2012. # msgid "" msgstr "" "Project-Id-Version: dtc-xen 0.5.15-1\n" "Report-Msgid-Bugs-To: dtc-...@packages.debian.org\n" "POT-Creation-Date: 2010-09-29 14:06+\n" "PO-Revision-Date: 2012-02-13 12:20+0100\n" "Last-Translator: Jeroen Schot \n" "Language-Team: Debian l10n Dutch \n" "Language: nl\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: string #. Description #: ../dtc-xen.templates:1001 msgid "SOAP server login:" msgstr "Gebruikersnaam SOAP-server:" #. Type: string #. Description #: ../dtc-xen.templates:1001 msgid "" "Dtc-xen will start it's Python based SOAP server to listen for incoming " "requests over a TCP socket. A remote application (like the dtc web hosting " "control panel) can then connect to it in order to start, stop, create and " "destroy a VPS." msgstr "" "Dtc-xen zal zijn SOAP-Pythonserver opstarten om te luisteren naar " "binnenkomende verzoeken op een TCP-socket. Een andere applicatie (zoals het " "dtc-webhosting-controlepaneel) kan dan verbinding maken om een VPS te " "starten, stoppen, aanmaken of vernietigen." #. Type: string #. Description #: ../dtc-xen.templates:1001 msgid "Please enter the login name to connect to the server." msgstr "" "Wat is de gebruikersnaam waarmee verbinding gemaakt kan worden met de server?" #. Type: password #. Description #: ../dtc-xen.templates:2001 msgid "SOAP server pass:" msgstr "Wachtwoord SOAP-server:" #. Type: password #. Description #: ../dtc-xen.templates:2001 msgid "" "Dtc-xen will generate a .htpasswd file for the login you have just " "configured." msgstr "" "Dtc-xen maakt een '.htpasswd'-bestand aan voor de gebruiker die u zojuist " "aangegeven hebt." #. Type: password #. Description #: ../dtc-xen.templates:2001 msgid "Please enter the password to use in that file." msgstr "Wat is het wachtwoord dat in dat bestand gebruikt moet worden?" #. Type: string #. Description #: ../dtc-xen.templates:3001 msgid "Debian repository for VPS creation:" msgstr "Bij het aanmaken van VPS te gebruiken Debian-pakketbron:" #. Type: string #. Description #: ../dtc-xen.templates:3001 msgid "" "Please enter the repository to use for creating the VPS (Virtual Private " "Server). The current /etc/apt/sources.list file will be copied to the " "created VPS so the repository you enter here will be used only during the " "debootstrap stage of the VPS creation." msgstr "" "Welke pakketbron (repository) dient gebruikt te worden bij het aanmaken van " "de VPS (virtual private server)? De huidige versie van /etc/apt/sources.list " "wordt gekopieerd naar de aangemaakte VPS, de hier aangegeven pakketbron " "wordt enkel gebruikt tijdens de debootstrap-fase van de VPS-generatie." #. Type: string #. Description #: ../dtc-xen.templates:4001 msgid "Network mask for the VPS:" msgstr "Netwerkmasker voor de VPS:" #. Type: string #. Description #: ../dtc-xen.templates:4001 msgid "" "Please enter the network mask to use in the created Virtual Private Server's " "network settings." msgstr "" "Wat is het netwerkmasker dat gebruikt moet worden voor de " "netwerkinstellingen van de 'Virtual Private Server'?" #. Type: string #. Description #: ../dtc-xen.templates:5001 msgid "Network address for the VPS:" msgstr "Netwerkadres voor de VPS:" #. Type: string #. Description #: ../dtc-xen.templates:5001 msgid "" "Please enter the network address to use in the created Virtual Private " "Server's network settings." msgstr "" "Wat is het netwerkadres dat gebruikt moet worden voor de netwerkinstellingen " "van de 'Virtual Private Server'?" #. Type: string #. Description #: ../dtc-xen.templates:6001 msgid "Broadcast address for the VPS:" msgstr "Broadcast-adres voor de VPS:" #. Type: string #.
Bug#887262: marked as done (dtc-xen should depend on e2fsprogs explicitly)
Your message dated Tue, 13 Feb 2018 19:04:17 + with message-id and subject line Bug#887262: fixed in dtc-xen 0.5.17-1.2 has caused the Debian Bug report #887262, regarding dtc-xen should depend on e2fsprogs explicitly 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.) -- 887262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dtc-xen Version: 0.5.17-1.1 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting there all packages that use e2fsprogs must be identified and gain a dependency on it as e2fsprogs currently is essential. dtc-xen was identified as potentially needing such a dependency, because it mentions tool names from e2fsprogs in the following files: /usr/sbin/dtc-soap-server contains fsck.ext3. According to file it is a a /usr/bin/python script, ASCII text executable /usr/sbin/dtc-xen_migrate contains mkfs.ext3. According to file it is a POSIX shell script, ASCII text executable, with very long lines /usr/sbin/dtc_reinstall_os contains mkfs.ext3. According to file it is a POSIX shell script, ASCII text executable, with very long lines /usr/sbin/dtc_setup_vps_disk contains mkfs.ext3. According to file it is a POSIX shell script, ASCII text executable Please investigate whether these cases are actually uses of a tool from e2fsprogs. Care has been taken to shrink the number of candidates as much as possible, but a few false positives will remain. After doing so, do one of the following: * Add e2fsprogs to Depends. * Add e2fsprogs to Recommends. * Close this bug explaining why e2fsprogs is not used by this package. Once e2fsprogs drops the "Essential: yes" flag, this bug will be upgraded to RC severity. Please note that lintian will warn about such a dependency before lintian 2.5.56. Thanks for your help Helmut --- End Message --- --- Begin Message --- Source: dtc-xen Source-Version: 0.5.17-1.2 We believe that the bug you reported is fixed in the latest version of dtc-xen, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson (supplier of updated dtc-xen 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, 13 Feb 2018 19:39:02 +0100 Source: dtc-xen Binary: dtc-xen dtc-xen-firewall Architecture: source all Version: 0.5.17-1.2 Distribution: unstable Urgency: medium Maintainer: Thomas Goirand Changed-By: Andreas Henriksson Description: dtc-xen- SOAP daemon and scripts to allow control panel management for Xen dtc-xen-firewall - small firewall script for your dom0 Closes: 659704 887262 Changes: dtc-xen (0.5.17-1.2) unstable; urgency=medium . * Non-maintainer upload. . [ Andreas Henriksson ] * Add e2fsprogs dependency (Closes: #887262) . [ Jeroen Schot ] * updated Dutch translation of the dtc-xen debconf templates (Closes: #659704) Checksums-Sha1: 360370f0671d22a3d6879942e6d40af5338ebb83 1926 dtc-xen_0.5.17-1.2.dsc 902a36a9615887a43d5bfc77508dd2c7619808af 54113 dtc-xen_0.5.17-1.2.diff.gz 595311f3e8ba0f1e61fac75c24cf61e5aa954485 13104 dtc-xen-firewall_0.5.17-1.2_all.deb fcd6038a083889a75bbdf25469ec781e3d5e3a8e 85576 dtc-xen_0.5.17-1.2_all.deb 5bb6215721ab0850168b396645f449c435dffc4c 6324 dtc-xen_0.5.17-1.2_amd64.buildinfo Checksums-Sha256: f3dc1b6d24b4893606f108762fad4f8051adb00d284cd0da2ebc7d4046305e84 1926 dtc-xen_0.5.17-1.2.dsc 58f1e9682b85facf9b600aa4982b3b8b3c11034b51e8433fda3f74b4d52dcf78 54113 dtc-xen_0.5.17-1.2.diff.gz 608eae4b8cf9bf3e04469dd76d26dfa245c771dce55fbc159be73a22ebca19ca 13104 dtc-xen-firewall_0.5.17-1.2_all.deb 5dd172a83f714a68be5ea06825e62933c8226a26d9d54fda0c53833d8f369973 85576 dtc-xen_0.5.17-1.2_all.deb e7b2364f44bdc458dd9a04c8eb83d474731e6187d95aafaa79fe3d5a62d2abca 6324 dtc-xen_0.5.17-1.2_amd64.buildinfo Files: aee44b7f52eb4e8018978bd587e608c1 1926 web extra dtc-
Bug#885009: marked as done (extrace: FTBFS on mips*, alpha, and sparc64: SIGSTKFLT undeclared)
Your message dated Tue, 13 Feb 2018 19:04:39 + with message-id and subject line Bug#885009: fixed in extrace 0.4-2 has caused the Debian Bug report #885009, regarding extrace: FTBFS on mips*, alpha, and sparc64: SIGSTKFLT undeclared 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.) -- 885009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: extrace Version: 0.4-1 Severity: important Tags: upstream Justification: fails to build from source User: debian-m...@lists.debian.org Usertags: mips mips64el mipsel Builds of extrace for mips* and the non-release architectures alpha and sparc64 have been failing: extrace.c: In function 'sig2name': extrace.c:156:5: error: 'SIGSTKFLT' undeclared (first use in this function); did you mean 'SIGSTKSZ'? Could you please account for architecture-specific variation in the set of signal names? Since these are generally implemented as preprocessor macros, you should be able to check for their existence with corresponding #ifdef constructs. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: extrace Source-Version: 0.4-2 We believe that the bug you reported is fixed in the latest version of extrace, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Braud-Santoni (supplier of updated extrace 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, 13 Feb 2018 19:11:00 +0100 Source: extrace Binary: extrace Architecture: source amd64 Version: 0.4-2 Distribution: unstable Urgency: medium Maintainer: Nicolas Braud-Santoni Changed-By: Nicolas Braud-Santoni Description: extrace- trace exec() calls system-wide Closes: 885009 885012 Changes: extrace (0.4-2) unstable; urgency=medium . * debian/source/lintian-overrides * Relocate from source.lintian-overrides * Add debian-watch-could-verify-download * Rename debian-watch-may-check-gpg-signature . * Switch to debhelper 11 * Install upstream's changelog * Restrict Architecture to linux-any (Closes: 885012) * Add patch making non-standard signals optional (Closes: 885009) . * Declare compliance with policy 4.1.3 * debian/copyrigt: Use HTTPS for the format URL Checksums-Sha1: 55684d02c2f3b9c2f5b2fa51de9969f11aece3e1 1876 extrace_0.4-2.dsc fdc623036957229d5c630c3b557aed722aae9ea0 6292 extrace_0.4-2.debian.tar.xz 7aae58472f5a0c1157b2fe458e06521da337ff06 18532 extrace-dbgsym_0.4-2_amd64.deb 17afc85ded9c871e15e63c54c2093fc5aa36eaab 5576 extrace_0.4-2_amd64.buildinfo 70bf0b92ab4c254784dbba6d5484f6c012052d54 11372 extrace_0.4-2_amd64.deb Checksums-Sha256: 5fd056ecd466ef39b7fe57977245fbfd8990961a51c5e292fd99d3fd45ad0dd6 1876 extrace_0.4-2.dsc 68499474d87ccc77bf05b90c304e845046b4bece1cab43a97a98fd2e05d64423 6292 extrace_0.4-2.debian.tar.xz e9f77905ec4818ea66daa470d46f66fef387648820df4ce48639ec6748fbad7f 18532 extrace-dbgsym_0.4-2_amd64.deb 4f6513fa1d307fa95dc49f44f2928d987c202f7330a620254d90489e09b6d39e 5576 extrace_0.4-2_amd64.buildinfo c3dceb6a3dd654cf9bb240c7201ef347fe6a7b7a06bb099bf544fac204950896 11372 extrace_0.4-2_amd64.deb Files: 418b565dabb3dc343256e1bcb9f3d063 1876 utils optional extrace_0.4-2.dsc e2b099af667c9a37a0d3b8ecd98f73ea 6292 utils optional extrace_0.4-2.debian.tar.xz aca32d43c77b325c90d766e7819d32eb 18532 debug optional extrace-dbgsym_0.4-2_amd64.deb ac3c0fc89edccd340ff71b37a66225e5 5576 utils optional extrace_0.4-2_amd64.buildinfo 8466031de171d94eb99eb7bb398de3fa 11372 utils optional extrace_0.4-2_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAlqDMzMPHGpjY0BkZWJp YW4ub3JnAAoJELAdGnKsjcmhfIMP/A6ZSjqcIBC7sEptg1KM5P9HYHRwOMfzhhyL ldZimSg8AdtwdQh4XJulZKRJOASqpCUz6oQVKD9ZuEGrbo/oNXMmmeLDX3/uDLFu ThxIlIe6ZE2mfmyGs1shAciywc6p3lwDalDJXvF1Ccf6iB37YMs0o1Cu9vxUli6Q zAtz9z/QN6BT5wp5ZqcCKt/mNC/Hbq4OxRc0yMey43qv+h9BHZNsfV732E5MClDr HOeWGUeVH
Bug#885012: marked as done (extrace: FTBFS on non-Linux: linux/connector.h absent)
Your message dated Tue, 13 Feb 2018 19:04:39 + with message-id and subject line Bug#885012: fixed in extrace 0.4-2 has caused the Debian Bug report #885012, regarding extrace: FTBFS on non-Linux: linux/connector.h absent 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.) -- 885012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: extrace Version: 0.4-1 Severity: important Justification: fails to build from source User: debian-h...@lists.debian.org Usertags: hurd-i386 Builds of extrace for (non-release) non-Linux architectures (just hurd-i386 so far) have been failing: extrace.c:54:10: fatal error: linux/connector.h: No such file or directory If extrace needs Linux-specific APIs, please formally limit its Architecture field to linux-any so that autobuilders for other architectures don't bother trying to cover it. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: extrace Source-Version: 0.4-2 We believe that the bug you reported is fixed in the latest version of extrace, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Braud-Santoni (supplier of updated extrace 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, 13 Feb 2018 19:11:00 +0100 Source: extrace Binary: extrace Architecture: source amd64 Version: 0.4-2 Distribution: unstable Urgency: medium Maintainer: Nicolas Braud-Santoni Changed-By: Nicolas Braud-Santoni Description: extrace- trace exec() calls system-wide Closes: 885009 885012 Changes: extrace (0.4-2) unstable; urgency=medium . * debian/source/lintian-overrides * Relocate from source.lintian-overrides * Add debian-watch-could-verify-download * Rename debian-watch-may-check-gpg-signature . * Switch to debhelper 11 * Install upstream's changelog * Restrict Architecture to linux-any (Closes: 885012) * Add patch making non-standard signals optional (Closes: 885009) . * Declare compliance with policy 4.1.3 * debian/copyrigt: Use HTTPS for the format URL Checksums-Sha1: 55684d02c2f3b9c2f5b2fa51de9969f11aece3e1 1876 extrace_0.4-2.dsc fdc623036957229d5c630c3b557aed722aae9ea0 6292 extrace_0.4-2.debian.tar.xz 7aae58472f5a0c1157b2fe458e06521da337ff06 18532 extrace-dbgsym_0.4-2_amd64.deb 17afc85ded9c871e15e63c54c2093fc5aa36eaab 5576 extrace_0.4-2_amd64.buildinfo 70bf0b92ab4c254784dbba6d5484f6c012052d54 11372 extrace_0.4-2_amd64.deb Checksums-Sha256: 5fd056ecd466ef39b7fe57977245fbfd8990961a51c5e292fd99d3fd45ad0dd6 1876 extrace_0.4-2.dsc 68499474d87ccc77bf05b90c304e845046b4bece1cab43a97a98fd2e05d64423 6292 extrace_0.4-2.debian.tar.xz e9f77905ec4818ea66daa470d46f66fef387648820df4ce48639ec6748fbad7f 18532 extrace-dbgsym_0.4-2_amd64.deb 4f6513fa1d307fa95dc49f44f2928d987c202f7330a620254d90489e09b6d39e 5576 extrace_0.4-2_amd64.buildinfo c3dceb6a3dd654cf9bb240c7201ef347fe6a7b7a06bb099bf544fac204950896 11372 extrace_0.4-2_amd64.deb Files: 418b565dabb3dc343256e1bcb9f3d063 1876 utils optional extrace_0.4-2.dsc e2b099af667c9a37a0d3b8ecd98f73ea 6292 utils optional extrace_0.4-2.debian.tar.xz aca32d43c77b325c90d766e7819d32eb 18532 debug optional extrace-dbgsym_0.4-2_amd64.deb ac3c0fc89edccd340ff71b37a66225e5 5576 utils optional extrace_0.4-2_amd64.buildinfo 8466031de171d94eb99eb7bb398de3fa 11372 utils optional extrace_0.4-2_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAlqDMzMPHGpjY0BkZWJp YW4ub3JnAAoJELAdGnKsjcmhfIMP/A6ZSjqcIBC7sEptg1KM5P9HYHRwOMfzhhyL ldZimSg8AdtwdQh4XJulZKRJOASqpCUz6oQVKD9ZuEGrbo/oNXMmmeLDX3/uDLFu ThxIlIe6ZE2mfmyGs1shAciywc6p3lwDalDJXvF1Ccf6iB37YMs0o1Cu9vxUli6Q zAtz9z/QN6BT5wp5ZqcCKt/mNC/Hbq4OxRc0yMey43qv+h9BHZNsfV732E5MClDr HOeWGUeVHE0xzZEkKVqg6H4QljGo55DfR0QvVy5lhEgSZ1B4dP/tk7dEexr5nYbQ Bd7bLL7zdz6UtdFZYGWm3lNYzRe7GempXNnpNsjGpS9OaC7oECsnTxca1kKwlDhC +KNqDlnNap7z9SHE/UlXeG0qu/sBqjolE5J5hcbX1P
Bug#889893: marked as done (cacti autopkg test failures)
Your message dated Tue, 13 Feb 2018 19:19:23 + with message-id and subject line Bug#889893: fixed in cacti 1.1.35+ds1-1 has caused the Debian Bug report #889893, regarding cacti autopkg test failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 889893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cacti Version: 1.1.34+ds1-1 Severity: important The tests currently fail with: FINISHED --2018-02-07 21:15:24-- Total wall clock time: 0.04s Downloaded: 1 files, 16K in 0s (243 MB/s) localhost/cacti/graphs.php not found Copying /var/log/cacti/cacti.log to artifacts Copying /var/log/apache2/access.log to artifacts Copying /var/log/apache2/error.log to artifacts complete test log at https://ci.debian.net/data/packages/unstable/amd64/c/cacti/latest-autopkgtest/log.gz --- End Message --- --- Begin Message --- Source: cacti Source-Version: 1.1.35+ds1-1 We believe that the bug you reported is fixed in the latest version of cacti, 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 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated cacti 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: Tue, 13 Feb 2018 19:26:14 +0100 Source: cacti Binary: cacti Architecture: source Version: 1.1.35+ds1-1 Distribution: unstable Urgency: medium Maintainer: Cacti Maintainer Changed-By: Paul Gevers Description: cacti - web interface for graphing of monitoring systems Closes: 889893 Changes: cacti (1.1.35+ds1-1) unstable; urgency=medium . * New upstream version 1.1.35 * [tests] Fix for nofollow directive that prevented recursive crawl (Closes: #889893) * [tests] Prevent cron job from running * Add 0001-issue-1336-Fix-issue-with-config-not-being-defined-1.patch from upstream Checksums-Sha1: e6ca04c4cedca1e2ca333222fdd57fde44b5c3f2 2144 cacti_1.1.35+ds1-1.dsc a6b13c3611423cc2e706b60d5bb7cfdb026d00b1 66580 cacti_1.1.35+ds1.orig-docs-source.tar.xz bf9e4dc46819566aa2c63cc4f0076b80e0e487d0 3838282 cacti_1.1.35+ds1.orig.tar.gz 4b176a22dc0dc132b5546b0ecf7bb81028cd6609 52176 cacti_1.1.35+ds1-1.debian.tar.xz Checksums-Sha256: 4d7812a76dd61e3b60f826fa65a94d5fb43510cd1ab73e76c157040161302965 2144 cacti_1.1.35+ds1-1.dsc 4e93415bb3e4d4cb126a8ea027378827214bf93e80e73f8718906a94acc7a318 66580 cacti_1.1.35+ds1.orig-docs-source.tar.xz 01434f67a029a0a463740894d4c7034de8d78b675aafcb065d3b60d97c7d93b0 3838282 cacti_1.1.35+ds1.orig.tar.gz 4f0d9269262f59227bd2d4eb538b0d75b1da5e961d011755b3d5d94c3931c475 52176 cacti_1.1.35+ds1-1.debian.tar.xz Files: 7ce60eaf80a351ce72d58c026e5dfb05 2144 web optional cacti_1.1.35+ds1-1.dsc 9f41c097f6beab7281874a473bbf3a86 66580 web optional cacti_1.1.35+ds1.orig-docs-source.tar.xz 3091971f042aa86b360a2457f33831b8 3838282 web optional cacti_1.1.35+ds1.orig.tar.gz 09c847d62db153568b88553e881ae626 52176 web optional cacti_1.1.35+ds1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlqDNaMACgkQnFyZ6wW9 dQpfawf+MzpJSZoEdJzAbCyHv7O78iqGmKSNNpquoYG6hygKRo2Tj6xp3wO7DUm8 4TvQFwvshjjNiPCXR/MUNITa3nlcx8TiK8By8FIb/xVMtAx7jRwp8j+Lkk9Q6H0Q XdAJ3tBC/khbxyxr40phNY9hrhzu/vXTA02sxh09lFm23q4XgvJDv1d6RYm3YffD Xqoqyikjcna8CCyTN3wF1lXWYGLys7khElGt8S1U5w0lVUDYOxtH+gNVNJvRn7jp fJHUKO6T2QIlDc7joRbUEykHSC7vI5ftciHPejS8vnKYRPAZjFBj13NohvlG92DS H+DnvyKaOEKPoHZQ8qOXtp03i4BM8Q== =pdc6 -END PGP SIGNATURE End Message ---
Bug#831621: marked as done (Updating the libunicode-map-perl Uploaders list)
Your message dated Tue, 13 Feb 2018 19:21:24 + with message-id and subject line Bug#831621: fixed in libunicode-map-perl 0.112-12 has caused the Debian Bug report #831621, regarding Updating the libunicode-map-perl 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.) -- 831621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libunicode-map-perl Version: 0.112-11 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Ruoso has retired, so can't work on the libunicode-map-perl 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 --- Source: libunicode-map-perl Source-Version: 0.112-12 We believe that the bug you reported is fixed in the latest version of libunicode-map-perl, 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 831...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niko Tyni (supplier of updated libunicode-map-perl 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: Tue, 13 Feb 2018 20:52:50 +0200 Source: libunicode-map-perl Binary: libunicode-map-perl Architecture: source Version: 0.112-12 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Niko Tyni Description: libunicode-map-perl - Perl module for mapping charsets from and to UTF16 Unicode Closes: 831621 Changes: libunicode-map-perl (0.112-12) unstable; urgency=medium . [ gregor herrmann ] * Strip trailing slash from metacpan URLs. . [ Salvatore Bonaccorso ] * Update Vcs-Browser URL to cgit web frontend * debian/control: Use HTTPS transport protocol for Vcs-Git URI . [ gregor herrmann ] * Remove Daniel Ruoso from Uploaders on request of the MIA team. (Closes: #831621) * Add Testsuite declaration for autopkgtest-pkg-perl. . [ Niko Tyni ] * Update my email address in Uploaders * Update to debhelper compat level 10 * Update to Standards-Version 4.1.3 * Declare that the package does not need (fake)root to build Checksums-Sha1: 359f9acd34676ebe6081aa0bab54c8dd0b61e3a4 2094 libunicode-map-perl_0.112-12.dsc df60dbdfb144824f0d9ac8067b8da97ed2967a8a 5480 libunicode-map-perl_0.112-12.debian.tar.xz 164316085347dd23dd211bcf5cc62f9231fad2ef 5811 libunicode-map-perl_0.112-12_source.buildinfo Checksums-Sha256: 2b287211f3f3c87a312cd283943b57e53cdeeca37d4e1755e2cfa59a6acb49de 2094 libunicode-map-perl_0.112-12.dsc 529136535e1b736ce2574e26c516aaffe1198a194da6fb9d93622db4f1ef52bd 5480 libunicode-map-perl_0.112-12.debian.tar.xz 7afe28049ed040f6082cdd532250eaebcdab77fee639fc8ed5d5170fb7ff 5811 libunicode-map-perl_0.112-12_source.buildinfo Files: 728d9b7f06b0658f8575583ce006ae6b 2094 perl optional libunicode-map-perl_0.112-12.dsc 3a73d0721dd5b2641452998a2986bf16 5480 perl optional libunicode-map-perl_0.112-12.debian.tar.xz 7728a5295d0758c5d4b5dd26a1374cdb 5811 perl optional libunicode-map-perl_0.112-12_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAlqDNRsACgkQLsD/s7cw Gx8vOA/9EPEPZ6T/kld6i8QnphMwubSjRIplrxL91D3j5nSURDBo5wzM4Y6mUfBL OubAMVf27KPz3lq1Yc1r4/iQ19aFPh2DCLIaxo2P4nQWXHiU4mejRA5MdYnr51b3 iDY1sP+H23ceOb+XvhdYdJNmrPO/EyDTXScpw/ujzgYk0ZvtTXQK7WCtsgllptiQ TFO5qWrlG1Uc0xUt/lCEI7BEdtqEJDx16O9QWRrW9JfrBZ9k6FP9xuKoUnbOmj/C KN9HiSFzATGOKXczF9Y0vBNVmCt49gCjSdB+H6BMQJTqheBITE2LT8qWpuxP5QmP fgvAi1UaUiBsugzosZqeiMo5HV96iMc5L/Y/DEQD5xHaE+HxkB0klj7vCOn580BG XPIqXQByS/xbp+9VyZMt5H1FhPaWaWVChKPRTZmt/L9sRJshH7ucsNi1A0UTnm++ +0sH4GC5wNT3OBlyGCTOtdRPzr1L9nzsnmtlIjJ15gXK6Fzqu01jpe2N9WrBGes9 mex/+GHA9BE0gIZy5cbbjHYlWsHOepapTBet7OTcZaraFLqRkEcwXikxcih0P5kG ibWyLuMn3z/C/WXxK+xTqD4s2myLtf3TmnVh1qqQp4PEncl1YrnNBG7Bnrx3vz83 csjdAoMeXcVFDzGqLEiuKRzgeVQkCOxBIU5Qza8ahKAJLLtcvE4= =xy5b -END PGP SIGNATURE End Message ---
Processed: closing 890034
Processing commands for cont...@bugs.debian.org: > close 890034 4.11-1~exp1 Bug #890034 [src:linux] linux-image-4.9.0-5-amd64: No driver support for Perc H740P RAID Controller Ignoring request to alter fixed versions of bug #890034 to the same values previously set Bug #890034 [src:linux] linux-image-4.9.0-5-amd64: No driver support for Perc H740P RAID Controller Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 890034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#885885: marked as done (FTBTS with linux 4.15, severe warnings with linux 4.14)
Your message dated Tue, 13 Feb 2018 21:04:23 +
with message-id
and subject line Bug#885885: fixed in broadcom-sta 6.30.223.271-8
has caused the Debian Bug report #885885,
regarding FTBTS with linux 4.15, severe warnings with linux 4.14
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.)
--
885885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: broadcom-sta
Version: 6.30.223.271-7
Severity: serious
Tags: patch
Justification: fails to build from source
linux 4.14 changed the kernel_read function prototype.
linux 4.15 deprecated the init_timer function.
Both functions are used by this package.
I am currectly using linux 4.15-rc5 with the attached patches applied
(my NIC is a Broadcom BCM4352).
Not sure the patches are correct, though.
Best regards,
Gerardo Malazdrewicz
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-rc5-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8),
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- a/amd64/src/shared/linux_osl.c 2017-12-29 22:59:17.0 -0400
+++ b/amd64/src/shared/linux_osl.c 2017-12-29 23:44:24.786247269 -0400
@@ -1076,11 +1076,21 @@
{
struct file *fp = (struct file *)image;
int rdlen;
+ loff_t pos;
if (!image)
return 0;
- rdlen = kernel_read(fp, fp->f_pos, buf, len);
+ pos = fp->f_pos;
+ rdlen = kernel_read(fp,
+#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 14, 0)
+ pos,
+#endif
+ buf, len
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 14, 0)
+ ,&pos
+#endif
+ );
if (rdlen > 0)
fp->f_pos += rdlen;
--- a/amd64/src/wl/sys/wl_linux.c 2017-12-29 23:57:29.0 -0400
+++ b/amd64/src/wl/sys/wl_linux.c 2017-12-30 12:32:29.518324068 -0400
@@ -93,7 +93,13 @@
#include
-static void wl_timer(ulong data);
+static void wl_timer(
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+ struct timer_list *tl
+#else
+ ulong data
+#endif
+ );
static void _wl_timer(wl_timer_t *t);
static struct net_device *wl_alloc_linux_if(wl_if_t *wlif);
@@ -2295,9 +2301,19 @@
}
static void
-wl_timer(ulong data)
-{
- wl_timer_t *t = (wl_timer_t *)data;
+wl_timer(
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+ struct timer_list *tl
+#else
+ ulong data
+#endif
+) {
+ wl_timer_t *t =
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+ from_timer(t, tl, timer);
+#else
+ (wl_timer_t *)data;
+#endif
if (!WL_ALL_PASSIVE_ENAB(t->wl))
_wl_timer(t);
@@ -2349,9 +2365,13 @@
bzero(t, sizeof(wl_timer_t));
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+ timer_setup(&t->timer, wl_timer, 0);
+#else
init_timer(&t->timer);
t->timer.data = (ulong) t;
t->timer.function = wl_timer;
+#endif
t->wl = wl;
t->fn = fn;
t->arg = arg;
--- End Message ---
--- Begin Message ---
Source: broadcom-sta
Source-Version: 6.30.223.271-8
We believe that the bug you reported is fixed in the latest version of
broadcom-sta, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Eduard Bloch (supplier of updated broadcom-sta 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: Tue, 13 Feb 2018 21:45:18 +0100
Source: broadcom-sta
Binary: broadcom-sta-common broadcom-sta-dkms broadcom-sta-source
Architecture: source all
Version: 6.30.223.271-8
Distribution: unstable
Urgency: low
Maintainer: Eduard Bloch
Changed-By: Eduard Bloch
Description:
broadcom-sta-common - Common files for the Bro
Bug#886986: marked as done (please remove bump-fasl-loader-version.patch)
Your message dated Tue, 13 Feb 2018 21:34:24 + with message-id and subject line Bug#886986: fixed in clisp 1:2.49.20180212+really2.49.90-1 has caused the Debian Bug report #886986, regarding please remove bump-fasl-loader-version.patch 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.) -- 886986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: clisp Version: 1:2.49.20170913-3 This bug was reported by Bruno Haible by private email, see below. - Forwarded message from Bruno Haible - Date: Thu, 11 Jan 2018 22:42:00 +0100 From: Bruno Haible To: Sébastien Villemot , Norbert Preining Cc: Agustin Martin , Sam Steingold Subject: please remove bump-fasl-loader-version.patch Message-ID: <2525153.Z8IsqQcaN0@omega> Hi Sébastien, In clisp for Debian 'unstable', there is a patch bump-fasl-loader-version.patch, originating from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877223 --- a/src/constobj.d +++ b/src/constobj.d @@ -337,7 +337,7 @@ /* The date of the last change of the bytecode interpreter or the arglist of any built-in function in FUNTAB or FUNTABR */ /* when changing, remove legacy ABI! */ - LISPOBJ(version,"(20100806)") + LISPOBJ(version,"(20100807)") LISPOBJ(machine_type_string,"NIL") LISPOBJ(machine_version_string,"NIL") LISPOBJ(machine_instance_string,"NIL") Please remove this patch. 1) It does not reliably fix the original issue. 2) It has undesired side effects, unrelated to the original issue. Ad 1): The original issue was an error initialization file `/usr/lib/xindy/xindy.mem' was not created by this version of CLISP runtime This error comes from src/spvw_memfile.d, and the clisp version that created the .mem file and the clisp version that attempts to use the .mem file disagree in - either the *object representation* (especially HEAPCODES vs. TYPECODES) [1], - or the set of add-on modules and their symbols. The issue will reoccur when Sébastien uploads new clisp binaries - either from a new clisp version (I'm currently preparing a 2.49.70) that has a different heuristic for choosing the object representation, - or build with a different setting of --enable-portability (because on 32-bit platforms this also has an effect on the object representation and the xindy.mem file remains unchanged. Ad 2): Assume a university installs clisp-2.50 on all its computers: from the Debian packages on Debian machines, and from source on the other machines. (As a matter of fact, the Math department of Utah university does exactly this.) The Debian machines will write .fas files with a version stamp (SYSTEM::VERSION '(20100807.)) and the other machines will write .fas files with a version stamp (SYSTEM::VERSION '(20100806.)) The effect will be that users working in NFS-mounted directories will find that their fas files from one machine don't work on some other machines. This would be a MAJOR annoyance when working with clisp. How to fix the original problem? Rule: When xindy is already installed on a user's machine and a newer clisp build gets installed that has a different .mem file format, the .mem file must be regenerated. clisp could (but does not currently) provide a hash code for the .mem file format. Therefore - not knowing whether the .mem file format has changed or not - the rule to be applied is: When xindy is already installed on a user's machine and a newer clisp build gets installed, the .mem file must be regenerated. How to implement this rule, is Debian specific. I don't think a 'dep:' link will be a maintainable solution. (This would require that clisp provides a command that produces said hash code.) Instead, how about this: - The binary package of xindy includes not only the .mem file but also the set of .fas files that gave rise to it. - The binary package of clisp contains a post-install trigger that will rebuild the xindy.mem file from its .fas files. (And likewise for all other packages that are in the same situation as xindy.) Bruno [1] https://clisp.sourceforge.io/impnotes/typecodes.html - End forwarded message - signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: clisp Source-Version: 1:2.49.20180212+really2.49.90-1 We believe that the bug you reported is fixed in the latest version of clisp, 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 reporti
Bug#885932: marked as done (ITP: libgeo-shapelib-perl -- Perl extension for reading and writing shapefiles as defined by ESRI)
Your message dated Tue, 13 Feb 2018 22:00:11 + with message-id and subject line Bug#885932: fixed in libgeo-shapelib-perl 0.22-1 has caused the Debian Bug report #885932, regarding ITP: libgeo-shapelib-perl -- Perl extension for reading and writing shapefiles as defined by ESRI 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.) -- 885932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: "Francesco P. Lovergine" * Package name: libgeo-shapelib-perl Version : 0.22 Upstream Author : Ari Jolma * URL : https://github.com/ajolma/Geo-Shapelib * License : Artistic Programming Lang: Perl Description : Perl module for reading and writing shapefiles as defined by ESRI This is a module to read, create and write shapefile as defined by ESRI, using Perl. It provides the Perl binding for the Shapelib library. --- End Message --- --- Begin Message --- Source: libgeo-shapelib-perl Source-Version: 0.22-1 We believe that the bug you reported is fixed in the latest version of libgeo-shapelib-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francesco Paolo Lovergine (supplier of updated libgeo-shapelib-perl 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: Tue, 06 Feb 2018 09:39:49 +0100 Source: libgeo-shapelib-perl Binary: libgeo-shapelib-perl Architecture: source amd64 Version: 0.22-1 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Francesco Paolo Lovergine Description: libgeo-shapelib-perl - Perl extension for reading and writing shapefiles as defined by E Closes: 885932 Changes: libgeo-shapelib-perl (0.22-1) unstable; urgency=medium . * Initial release (closes: #885932) . [ Francesco Paolo Lovergine ] * Added missing gbp.conf . [ Bas Couwenberg ] * Restructure control file with cme. * Add standalone license paragraph for Artistic-2.0 license. * Enable all hardening buildflags. * Move Build-Depends-Indep to Build-Depends, no Architecture: all binary packages are built. * Add autopkgtest to test installability. * Improve extended description. * Add upstream metadata. * Add patch to fix pod2man errors. Checksums-Sha1: 5aea3ad3dba5a041eb2b45a85dc98547caeb1b39 2137 libgeo-shapelib-perl_0.22-1.dsc 76f6f6a8407ee9ac9eab3c6fc3d9023028ccfe10 120136 libgeo-shapelib-perl_0.22.orig.tar.gz a754ea9b7302c59bee5474844a81d9eab0839cb1 5420 libgeo-shapelib-perl_0.22-1.debian.tar.xz 3c41935125be1259df10d7b540044cbe4da97905 49572 libgeo-shapelib-perl-dbgsym_0.22-1_amd64.deb 63c2a090d3f9a966b43a24a40fdd0bc1260104df 6161 libgeo-shapelib-perl_0.22-1_amd64.buildinfo 027f36157eb36608c8469980390bf4f5f66784e4 33736 libgeo-shapelib-perl_0.22-1_amd64.deb Checksums-Sha256: c7add09ea4ed2a1d7c0378a1d658b690a93f48e0e589aac7be94c7b49182b893 2137 libgeo-shapelib-perl_0.22-1.dsc 7963fd115042cfea71ad40f479d3553c97c906e34fbb924a76d3b6e06fc7f6ff 120136 libgeo-shapelib-perl_0.22.orig.tar.gz d02d9c8cdae7cb9f583d5111b78ca00ed0d30c279b47f8df088bb7b50e439af9 5420 libgeo-shapelib-perl_0.22-1.debian.tar.xz 689e3b5dc890c918466c9a0fdaf8634eaab853e2ba40375e3c83b0abf443e8a0 49572 libgeo-shapelib-perl-dbgsym_0.22-1_amd64.deb 2ab68ad788948490aa9e01bd3066cb0b97327422f4e586c654a9d5a129271c4a 6161 libgeo-shapelib-perl_0.22-1_amd64.buildinfo 66ce3f6191a3d16a2dc7b65220227ecc36304ec5ad5e46541c65065a29ac7a34 33736 libgeo-shapelib-perl_0.22-1_amd64.deb Files: 3464855e24136047b85fd96d1c82763e 2137 perl optional libgeo-shapelib-perl_0.22-1.dsc a356e7104138aa4470bca863f7383f82 120136 perl optional libgeo-shapelib-perl_0.22.orig.tar.gz bf0333b2b7074140f1ba87f43fc754af 5420 perl optional libgeo-shapelib-perl_0.22-1.debian.tar.xz c00695e52bcd873000e5105a058600bb 49572 debug optional libgeo-shapelib-perl-dbgsym_0.22-1_amd64.deb 5fafa46f9ed7da5407762bc4e4c9b7b9 6161 perl optional libgeo-shapelib-perl_0.22-1_amd64.buildinfo e13cc2d85fe424815adb74c2e94cbf91 3
Bug#890345: marked as done (Depending on "default-jre-headless" Should be Sufficient)
Your message dated Tue, 13 Feb 2018 22:04:16 + with message-id and subject line Bug#890345: fixed in jflex 1.6.1-3 has caused the Debian Bug report #890345, regarding Depending on "default-jre-headless" Should be Sufficient 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.) -- 890345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jflex Version: 1.6.1-2 Severity: wishlist "jflex" seems to me a commandline program, thus depending on "default-jre-headless" should be sufficient. Right now it depends on "default-jre" and "pbuilder" always fetches the whole graphical stack while building "libsmali-java". signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: jflex Source-Version: 1.6.1-3 We believe that the bug you reported is fixed in the latest version of jflex, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated jflex 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, 13 Feb 2018 22:30:33 +0100 Source: jflex Binary: jflex Architecture: source Version: 1.6.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: jflex - lexical analyzer generator for Java Closes: 890345 Changes: jflex (1.6.1-3) unstable; urgency=medium . * Use compat level 11. * Declare compliance with Debian Policy 4.1.3. * Use https for Format field. Update copyright years. * Change dependency from default-jre to default-jre-headless | java7-runtime-headless. Thanks to Kai-Chung Yan for the report. (Closes: #890345) * Change source/target to 1.7. Checksums-Sha1: 078e4a0f19ab0f0479dc2f65b67a3eddd44a6aeb 2089 jflex_1.6.1-3.dsc 1ad46e117999d14787979db7e41d680997e845e5 6160 jflex_1.6.1-3.debian.tar.xz 9173357392e25d0851e4b23adcc888d145fa5fa6 11167 jflex_1.6.1-3_amd64.buildinfo Checksums-Sha256: 0831c99480f45e3d715bafc1e7530a427ac4988a5ed5879f85dd866eb34d5273 2089 jflex_1.6.1-3.dsc ddd44dcb9b556cdce9e0f61a778a742c560430e2abaca87faeb966263792a2fc 6160 jflex_1.6.1-3.debian.tar.xz b92012fa4f706198c87b8729b04ede6804ce676cad2b6bb46b76e62b330f2e88 11167 jflex_1.6.1-3_amd64.buildinfo Files: fbf7a4aa125d14bf901a173bc72057cc 2089 java optional jflex_1.6.1-3.dsc e03c58806eaa0deffc462b1682ce12e4 6160 java optional jflex_1.6.1-3.debian.tar.xz 3424ba1bb13fb5a9c21596d512359323 11167 java optional jflex_1.6.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlqDXWhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkTvsP/3Fr99dhHCEVVjJK5sL+J/mUXQyqMH01iGXd uXyzocNTs4/380j02DWrq+xVh++Dm55oYxAbVXJr3RzUZbHYkoQE1uuO8C3MQOZS gm+/Hb93dnuIwn+wwFjv1KThfDfElwAnXtUOReFsvkAzSGdUL2Bulc+gpG9bQFNY pJgnCJC18kkJiHtnvs9s1YgelM8Vh18eAmunu8wqv1W28AeTT3kzAbxE8wVIwF+G zcmfwdSbcyswrtO5Pf49Dnw/c2VuuNQXKmO66TRHLH0VJgCTiHuzd8W0JRW3EzuO i7uKfPMg73wBG/eGtPltIWu8gGXtMETwF14wQdAwpq0TLqZzASIqYrExry2bPkxr RlXTj0/vQw78gI2k1ahgocgkAMQiuRGGEUzetAfDhhne5HjrA5mjaapx58c8UFA2 3IAHALAjG91hiJmWtwT9d5rZZ627RSg9bchivpyDrGLcdAPG6pde2K+1E4NHpDWh R8zoYlwR8ITGVV7k3LSa1i3VmJjJuDuH1LqkXBv+dIEVAXw9W4TrKG6KMpRZMdB/ j1KQ8x1dOQllcrUD6t/+uTfCy6itD53wUJfGRKFeD+JZTkFF4cKQTTspqGSfBEWh 1SyjOqy3X+zXMuLqUviq3343pSuvOvI7iS38FDPP2A4Lw55yH58YUQDwfKKLuwEi vF0FtQ3E =sWGL -END PGP SIGNATURE End Message ---
Bug#875950: marked as done (xastir: [INTL:sv] Swedish debconf strings)
Your message dated Tue, 13 Feb 2018 22:35:48 + with message-id and subject line Bug#875950: fixed in xastir 2.1.0-1 has caused the Debian Bug report #875950, regarding xastir: [INTL:sv] Swedish debconf strings 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.) -- 875950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: xastir severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. I made few corrections to latest translation. Regards, Jonatan# SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: xastir\n" "Report-Msgid-Bugs-To: xas...@packages.debian.org\n" "POT-Creation-Date: 2015-04-04 02:04+0100\n" "PO-Revision-Date: 2017-09-16 14:55+0200\n" "Last-Translator: Jonatan Nyberg \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: Poedit 1.8.11\n" "Language-Team: \n" #. Type: boolean #. Description #: ../templates:2001 msgid "Should non-superusers be able to use native AX.25 interfaces?" msgstr "Bör icke-superanvändare kunna använda inbyggda AX.25-gränssnittet?" #. Type: boolean #. Description #: ../templates:2001 msgid "Xastir can be installed in a way that allows members of the \"xastir-ax25\" system group to use a native Linux AX.25 interface from within Xastir. Where available this configuration uses Linux capabilities in order to limit the process's privileges to only those required, falling back on installing the binary setuid where Linux capabilities are not available." msgstr "Xastir kan installeras på ett sätt som gör att medlemmar i \"xastir-ax25\"-systemgruppen kan använda ett Linux-AX.25 gränssnitt inifrån Xastir. När denna konfiguration finns tillgänglig använder den Linux förmågor för att begränsa processens privilegier till endast de som krävs, faller tillbaka på installation av binära setuid där Linux förmågor inte är tillgängliga." #. Type: boolean #. Description #: ../templates:2001 msgid "This is recommended over the alternative of running Xastir directly as root, but enabling it may be a security risk, so it is disabled by default. If in doubt, or if you do not intend to use native AX.25 interfaces (using a serial TNC or Internet connection instead), it is suggested to leave it disabled." msgstr "Detta rekommenderas över alternativet att köra Xastir direkt som root, men aktivering kan innebära en säkerhetsrisk, så den är inaktiverad som standard. Om du är osäker, eller om du inte har för avsikt att använda inbyggda AX.25-gränssnittet (genom att använda en seriell TNC- eller Internet-anslutning i stället), föreslås det att lämna den inaktiverad." #. Type: boolean #. Description #: ../templates:2001 msgid "For more detailed information please see /usr/share/doc/xastir/README.Debian." msgstr "För mer detaljerad information se /usr/share/doc/xastir/README.Debian." --- End Message --- --- Begin Message --- Source: xastir Source-Version: 2.1.0-1 We believe that the bug you reported is fixed in the latest version of xastir, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dave Hibberd (supplier of updated xastir 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: Tue, 13 Feb 2018 22:08:14 + Source: xastir Binary: xastir Architecture: source amd64 Version: 2.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: Dave Hibberd Description: xastir - X Amateur Station Tracking and Information Reporting Closes: 861005 875950 Changes: xastir (2.1.0-1) unstable; urgency=medium . * New upstream release - debian/patches/* refreshed - debian/xastir.docs updated * Menu Icon is back (Closes: #861005) - debian/xastir.install updated to put icon in pixmaps folder - debia
Bug#861005: marked as done (xastir: no icon in menus)
Your message dated Tue, 13 Feb 2018 22:35:48 + with message-id and subject line Bug#861005: fixed in xastir 2.1.0-1 has caused the Debian Bug report #861005, regarding xastir: no icon in menus 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.) -- 861005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xastir Version: 2.0.8-2+b3 Severity: minor Dear Maintainer, xastir has no icon in the menus on kde, mate and other desktop environments. It would be nice to see a little icon beside the program in the list! Thanks, Hibby -- 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_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xastir depends on: ii debconf [debconf-2.0]1.5.60 ii libax25 0.0.12-rc4-1 ii libbz2-1.0 1.0.6-8.1 ii libc62.24-9 ii libcurl3-gnutls 7.52.1-3 ii libdb5.3 5.3.28-12+b1 ii libfreetype6 2.6.3-3.1 ii libgdal202.1.2+dfsg-3 ii libgeotiff2 1.4.2-2+b1 ii libgomp1 6.3.0-11 ii libgraphicsmagick-q16-3 1.3.25-8 ii libice6 2:1.0.9-2 ii libjbig0 2.1-3.1+b2 ii libjpeg62-turbo 1:1.5.1-2 ii liblcms2-2 2.8-4 ii liblzma5 5.2.2-1.2+b1 ii libpcre3 2:8.39-3 ii libpng16-16 1.6.28-1 ii libproj124.9.3-1 ii libshp2 1.4.0-1 ii libsm6 2:1.2.2-1+b3 ii libtiff5 4.0.7-5 ii libwebp6 0.5.2-1 ii libwmf0.2-7 0.2.8.4-10.6 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxm4 2.3.4-13 ii libxml2 2.9.4+dfsg1-2.2 ii libxt6 1:1.1.5-1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages xastir recommends: ii festival 1:2.4~release-3+b1 ii python2.7.13-2 Versions of packages xastir suggests: ii direwolf1.3-2 ii soundmodem 0.20-5+b1 -- debconf information excluded signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: xastir Source-Version: 2.1.0-1 We believe that the bug you reported is fixed in the latest version of xastir, 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 861...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dave Hibberd (supplier of updated xastir 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: Tue, 13 Feb 2018 22:08:14 + Source: xastir Binary: xastir Architecture: source amd64 Version: 2.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: Dave Hibberd Description: xastir - X Amateur Station Tracking and Information Reporting Closes: 861005 875950 Changes: xastir (2.1.0-1) unstable; urgency=medium . * New upstream release - debian/patches/* refreshed - debian/xastir.docs updated * Menu Icon is back (Closes: #861005) - debian/xastir.install updated to put icon in pixmaps folder - debian/xastir.desktop updated * Small fixes for sv debconf strings (Closes: #875950) - Thanks to Jonatan Nyberg * Hardening Added - debian/rules updated * CVS migrated to salsa - debian/control updated * debhelper 11 & standards updated - debian/control updated - debian/compat updated * debian/watch now tracks upstream gith
Bug#510923: marked as done (zoom indicator not ready to deal arbitrary --zoom value)
Your message dated Wed, 14 Feb 2018 00:02:14 +0100 with message-id <20180213230214.gz924...@zedat.fu-berlin.de> and subject line Re: zoom indicator not ready to deal arbitrary --zoom value has caused the Debian Bug report #510923, regarding zoom indicator not ready to deal arbitrary --zoom value 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.) -- 510923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf-reader Version: 3.02-1.4 Severity: wishlist File: /usr/share/man/man1/xpdf.1.gz At -z zoom in the man page, mention that e.g., if you say -z 172, 150 will be chosen for you. --- End Message --- --- Begin Message --- closing as this seems to be fixed now (testing xpdf 3.04-5)--- End Message ---
Bug#783913: marked as done (xpdf: -cont no more works)
Your message dated Wed, 14 Feb 2018 00:07:23 +0100 with message-id <20180213230723.gb924...@zedat.fu-berlin.de> and subject line Re: xpdf: -cont no more works has caused the Debian Bug report #783913, regarding xpdf: -cont no more works 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.) -- 783913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.03-17+b1 Dead maintainer(s), After upgrading wheezy to jessie, xpdf consistently stopped showing documents in continuous mode. For example: xpdf -cont PLRM.pdf & xpdf.real -cont PLRM.pdf & where the file is taken from http://www.adobe.com/products/postscript/pdfs/PLRM.pdf display the file in the usual per-page mode (instead of the continuous one). There are no user-private .xpdfrc, no aliases. The system-wide /etc/xpdfrc has no occurrences of "continuous...". The man page still mentions -cont, however. Any help? Best, Jaakov. --- End Message --- --- Begin Message --- Control: fixed 783913 3.04-5 closing as -cont seems to work now--- End Message ---
Bug#833673: marked as done (xpdf -z option under jessie)
Your message dated Wed, 14 Feb 2018 00:04:44 +0100 with message-id <20180213230444.ga924...@zedat.fu-berlin.de> and subject line Re: xpdf -z option under jessie has caused the Debian Bug report #833673, regarding xpdf -z option under jessie 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.) -- 833673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xpdf Version: 3.03 (jessie amd64) The -z option no longer works. It used to work in wheezy and many releases efore that. --help says it is still there. You can give it and it doesn't complain. It just has no effect. Jeff (http://engineering.purdue.edu/~qobi) --- End Message --- --- Begin Message --- Control: fixed 833673 3.04-5 closing as -z seems to be working now--- End Message ---
Bug#887365: marked as done (ignition-msgs: Update ignition-msgs to 1.0.0 version)
Your message dated Tue, 13 Feb 2018 15:17:11 -0800 with message-id and subject line Re: Bug#887365: ignition-msgs: Update ignition-msgs to 1.0.0 version has caused the Debian Bug report #887365, regarding ignition-msgs: Update ignition-msgs to 1.0.0 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.) -- 887365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ignition-msgs Version: 1.0.0 Severity: wishlist Update igniton-msgs to latest 1.0.0 version in debian Sid. The packaging work is ready in the debian-science git: https://salsa.debian.org/science-team/ignition-msgs A test run has been run in the OSRF buildfarm: https://build.osrfoundation.org/view/All/job/ignition-msgs-pkg_builder-master-debian_sid-amd64/52/ Thanks. --- End Message --- --- Begin Message --- 1.0.0 is already present in unstable On Mon, Jan 15, 2018 at 6:35 AM, Jose Luis Rivero wrote: > Source: ignition-msgs > Version: 1.0.0 > Severity: wishlist > > Update igniton-msgs to latest 1.0.0 version in debian Sid. > > The packaging work is ready in the debian-science git: > https://salsa.debian.org/science-team/ignition-msgs > > A test run has been run in the OSRF buildfarm: > https://build.osrfoundation.org/view/All/job/ignition- > msgs-pkg_builder-master-debian_sid-amd64/52/ > > Thanks. > > -- > debian-science-maintainers mailing list > debian-science-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/ > debian-science-maintainers > --- End Message ---
Bug#869777: marked as done (yara tests fail on ARM32, when run on a 64bit kernel)
Your message dated Tue, 13 Feb 2018 23:21:26 +
with message-id
and subject line Bug#869777: fixed in yara 3.7.1-2
has caused the Debian Bug report #869777,
regarding yara tests fail on ARM32, when run on a 64bit kernel
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.)
--
869777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:yara
Version: 3.6.3+dfsg-1
Forwarded: https://github.com/VirusTotal/yara/issues/716
Tags: upstream
yara tests fail on ARM32, when run on a 64bit kernel.
This turns out to be because the codebase is full of code that assumes unaligned
access is OK, for example stuff like this
https://github.com/VirusTotal/yara/blob/master/libyara/exec.c#L224 but also
more subtly stuff like
https://github.com/VirusTotal/yara/blob/master/libyara/scan.c#L409
(new_match is only guaranteed to be 4-byte-aligned and crashes when you access
an 8 byte field).
make check-TESTS
make[3]: Entering directory '/<>/yara-3.6.3+dfsg'
make[4]: Entering directory '/<>/yara-3.6.3+dfsg'
PASS: test-alignment
FAIL: test-rules
FAIL: test-pe
FAIL: test-elf
PASS: test-version
FAIL: test-exception
==
yara 3.6.3: ./test-suite.log
==
# TOTAL: 6
# PASS: 2
# SKIP: 0
# XFAIL: 0
# FAIL: 4
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: test-rules
yr_rules_scan_mem: error
FAIL test-rules (exit status: 1)
FAIL: test-pe
=
yr_rules_scan_mem: error
FAIL test-pe (exit status: 1)
FAIL: test-elf
==
yr_rules_scan_mem: error
FAIL test-elf (exit status: 1)
FAIL: test-exception
Scanning for ""...
err = 4, matches = 0
Sending blocked SIGUSR1 to ourselves...
Scanning for {00 00 00 00}...
err = 4, matches = 0
Scanning for ""...
err = 4, matches = 0
Expected subprocess to be terminated by signal
Test: crash
Test: crash-no-handle
Test: blocked-signal
Test: crash-other-thread
FAIL test-exception (exit status: 1)
Testsuite summary for yara 3.6.3
# TOTAL: 6
# PASS: 2
# SKIP: 0
# XFAIL: 0
# FAIL: 4
# XPASS: 0
# ERROR: 0
See ./test-suite.log
Please report to vmalva...@virustotal.com
Makefile:1000: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: yara
Source-Version: 3.7.1-2
We believe that the bug you reported is fixed in the latest version of
yara, 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 869...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hilko Bengen (supplier of updated yara 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: Tue, 13 Feb 2018 23:27:11 +0100
Source: yara
Binary: yara libyara3 libyara-dev yara-doc
Architecture: source
Version: 3.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Forensics
Changed-By: Hilko Bengen
Description:
libyara-dev - YARA development libraries and headers
libyara3 - YARA shared library
yara - Pattern matching swiss knife for malware researchers
yara-doc - HTML documentation for YARA
Closes: 869777
Changes:
yara (3.7.1-2) unstable; urgency=medium
.
* Fix unaligned access that leads to failing tests. Thanks to Matthias
Klose for the patch. (Closes: #869777)
Checksums-Sha1:
b3a2ddee28377f924fec10ee9cfd14b1e149280f 2104 yara_3.7.1-2.dsc
d692dac21def535b4e0beb949cb01d8852dfe109 7880 yara_3.7.1-2.debian.tar.xz
eb6fc1a98b22b0079b51eff9120abe733d38 4086 yara_3.7.1-2_source.buildinfo
Checksums-Sha256:
390adba34dc539b856274c4bbc7b37aec58840b7e95916b59f13fbc3a791653f 2104
yara_3.7.1-2.dsc
447439a9f1fca3801a2d9a58cd73becce14494505b4efdf1ae5e227c08050856 7880
yara_3.7.1-2.debian.tar.xz
f0a819fbddfed093969ea004bd8fb19bb31e5b230d76f777cdddfd3cfef98dc
Bug#833146: marked as done (flex FTCBFS: executes host architectue stage1flex during build)
Your message dated Wed, 14 Feb 2018 00:19:27 + with message-id and subject line Bug#833146: fixed in flex 2.6.4-2 has caused the Debian Bug report #833146, regarding flex FTCBFS: executes host architectue stage1flex during build 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.) -- 833146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flex Version: 2.6.1-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap Hi Manoj, I see that you found time for working on flex again. Unfortunately the upstream changes to 2.6.1 make it fail to cross build again. This time, a stage1flex was added to produce the scanner built into flex itself. Of course, we can't just run stage1flex during a cross build. I'm attaching a patch that uses the system flex (required for help2man already) instead. With that patch and fixing flex to be M-A:foreign again and working around #815172, I can successfully cross build flex again. Could you apply this patch? Also what's your progress on the flex/libfl-dev split MBF? I see that you asked on d-devel for it and there were no objections. What's the progress of it? Helmut --- flex-2.6.1/configure.ac +++ flex-2.6.1/configure.ac @@ -70,6 +70,7 @@ FLEXexe='$(top_builddir)/src/flex$(EXEEXT)' fi AC_SUBST(FLEXexe) +AM_CONDITIONAL([CROSS_COMPILING],[test "$cross_compiling" = yes]) # Check for a m4 that supports -P --- flex-2.6.1/debian/changelog +++ flex-2.6.1/debian/changelog @@ -1,3 +1,10 @@ +flex (2.6.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: (Closes: #-1) + + -- Helmut Grohne Mon, 01 Aug 2016 13:28:35 +0200 + flex (2.6.1-1) unstable; urgency=low * New upstream version. The development of flex ias transitionaing to +++ flex-2.6.1/src/Makefile.am @@ -89,8 +89,13 @@ stage1scan.l: scan.l cp $(srcdir)/scan.l $(srcdir)/stage1scan.l +if CROSS_COMPILING +stage1scan.c: stage1scan.l + $(FLEXexe) -o $@ $< +else stage1scan.c: stage1scan.l stage1flex$(EXEEXT) $(top_builddir)/src/stage1flex$(EXEEXT) -o $@ $< +endif # Explicitly describe dependencies. # You can recreate this with `gcc -I. -MM *.c' --- End Message --- --- Begin Message --- Source: flex Source-Version: 2.6.4-2 We believe that the bug you reported is fixed in the latest version of flex, 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 833...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manoj Srivastava (supplier of updated flex 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, 13 Feb 2018 15:25:11 -0800 Source: flex Binary: flex flex-doc libfl-dev Architecture: source amd64 all Version: 2.6.4-2 Distribution: unstable Urgency: medium Maintainer: Manoj Srivastava Changed-By: Manoj Srivastava Description: flex - fast lexical analyzer generator flex-doc - Documentation for flex (a fast lexical analyzer generator) libfl-dev - static library for flex (a fast lexical analyzer generator) Closes: 833146 Changes: flex (2.6.4-2) unstable; urgency=medium . * Added get-orig-source target, and updated the watch file * Bug fix: "flex FTCBFS: executes host architectue stage1flex during build", thanks to Helmut Grohne (Closes: #833146). This reinstates Helmut's original fix. There was a question about not using help2man in the first place. I considered it; but upstream continues to use help2man, including it in autoconf. I think Helmut's fix is elegant, and saves work as flex's options change over time, and is a smaller delta from upstream. Checksums-Sha1: bd1ecbe85fcec46a92a08a2805c00319c2d22522 2009 flex_2.6.4-2.dsc 8db99df2af54ffc0d0544953206a05078bcf1b02 57939 flex_2.6.4-2.diff.gz 68afa9657175f9c8a4f5cf2d737d979f3f8d6798 159844 flex-dbgsym_2.6.4-2_amd64.deb 9d5658b1af467d174c04226c07bda26211142347 762472 flex-doc_2.6.4-2_all.deb eaabb0ecd5250b65080bdd9d7ad056545e44e997 8513 flex_2.6.4-2_amd64.buildinfo dd003744ea2bd0908021147f4db308085ab3062b 454508 flex_2.6.4-2_amd64.deb 0f3a4abf72fb45ca9cb37e8d7e711f8f0fada1d1 101916 li
Bug#842261: marked as done (make: Typo in french translation)
Your message dated Tue, 13 Feb 2018 17:02:15 -0800 with message-id <87a7wcfko8@glaurung.internal.golden-gryphon.com> and subject line This issue is fixed in the latest upload. has caused the Debian Bug report #842261, regarding make: Typo in french translation to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 842261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: make Version: 4.1-9 Severity: wishlist Tags: patch Hello, There is a small typo in the french translation of make messages, see attached patch (compressed to avoid charset conversions). Samuel -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0 (SMP w/4 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 make depends on: ii libc6 2.24-5 make recommends no packages. Versions of packages make suggests: ii make-doc 4.1-3 -- no debconf information -- Samuel Les roots ne sont plus ce qu'ils étaient...Maintenant il sont dioxinés, c'est de la m... ! Avant on les élevaient avec du bon unix mais ça été remplacé par des farines industrielles nouvelles technologies (NT). -+- JdK in NPC : Exigez un root élevé sous la mère ! -+- patch.gz Description: application/gunzip --- End Message --- --- Begin Message --- Package: make-dfsg Version: 4.2.1-1 The new upstream comes with an updated translation. manoj -- Speak softly and own a big, mean Doberman. Dave Millman Manoj Srivastava 4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C smime.p7s Description: S/MIME cryptographic signature --- End Message ---
Bug#887659: marked as done (RFS: urlwatch/2.7-1 [ITA])
Your message dated Wed, 14 Feb 2018 11:08:19 +0800 with message-id and subject line Re: Bug#887659: RFS: urlwatch/2.7-1 [ITA] has caused the Debian Bug report #887659, regarding RFS: urlwatch/2.7-1 [ITA] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 887659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "urlwatch" * Package name: urlwatch Version : 2.7-1 Upstream Author : Thomas Perl * URL : http://thp.io/2008/urlwatch/ * License : BSD-3-clause Section : web It builds those binary packages: urlwatch - tool for monitoring webpages for updates To access further information about this package, please visit the following URL: https://mentors.debian.net/package/urlwatch Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/u/urlwatch/urlwatch_2.7-1.dsc More information about urlwatch can be obtained from https://github.com/thp/urlwatch. Urlwatch depends on a new package I've uploaded : minidb. I'm looking for a sponsor for this two packages. See https://mentors.debian.net/package/minidb Changes since the last upload: urlwatch (2.7-1) unstable; urgency=low * Upgrade Upstream version 2.7 (Closes: #798312) * Switched watch to github sources * Removed existing patches as changes wasn't pertinent anymore * Added a patch to make nose tests work with pybuild (accepted by upstream) * New maintainer (Closes: #831272) * New version, now support ssl_ni_verify option (Closes: #771907) -- Maxime Werlen Tue, 16 Jan 2018 21:17:12 +0100 Regards, Maxime Werlen --- End Message --- --- Begin Message --- On Tue, Feb 13, 2018 at 1:03 PM, Paul Wise wrote: > There is only the blocker of ftp-masters accepting minidb now. They accepted minidb quickly, so I have uploaded urlwatch. In addition to the things I already mentioned, please: Set debtags on minidb once the site knows about it: https://debtags.debian.org/edit/minidb Review the debtags for urlwatch: https://debtags.debian.org/edit/urlwatch Upload a screenshot of typical urlwatch usage: https://screenshots.debian.net/package/urlwatch Keep an eye on your DMD, DDPO and DPT pages: https://udd.debian.org/dmd/?maxime%40werlen.fr#todo https://qa.debian.org/developer.php?email=maxime%40werlen.fr https://tracker.debian.org/pkg/minidb https://tracker.debian.org/pkg/urlwatch For future uploads, please post a new RFS. -- bye, pabs https://wiki.debian.org/PaulWise--- End Message ---
Bug#771907: marked as done (urlwatch: option for disabling certificate verification)
Your message dated Wed, 14 Feb 2018 03:20:59 + with message-id and subject line Bug#771907: fixed in urlwatch 2.7-1 has caused the Debian Bug report #771907, regarding urlwatch: option for disabling certificate verification 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.) -- 771907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: urlwatch Version: 1.15-3 Severity: wishlist python2.7 in Debian has recently started to verify TLS certificates by default: https://bugs.python.org/issue22417 Please add an option to disable certificate verification. -- Jakub Wilk --- End Message --- --- Begin Message --- Source: urlwatch Source-Version: 2.7-1 We believe that the bug you reported is fixed in the latest version of urlwatch, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maxime Werlen (supplier of updated urlwatch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Feb 2018 06:21:33 +0100 Source: urlwatch Binary: urlwatch Architecture: source Version: 2.7-1 Distribution: unstable Urgency: low Maintainer: Maxime Werlen Changed-By: Maxime Werlen Description: urlwatch - tool for monitoring webpages for updates Closes: 771907 798312 831272 Changes: urlwatch (2.7-1) unstable; urgency=low . * Upgrade Upstream version 2.7. (Closes: #798312) * Removed existing patches as changes wasn't pertinent anymore. * Added a patch to make nose tests work with pybuild (accepted by upstream). * Added a patch fo fix a setuptools warning (accepted by upstream). * Added a patch to remove dependencies from upstream Readme. * Added upstream metadata informations. * Added a NEWS.debian file about migration from urlwatch 1.15 * Added some tests. * Upgraded DH compat to 11. * Changed source repo to salsa.debian.org. * New maintainer. (Closes: #831272) * New version, now support ssl_ni_verify option. (Closes: #771907) Checksums-Sha1: 0448a50dc194e93fb89bfaba207b3f504772e73d 2047 urlwatch_2.7-1.dsc 320a452b5d964fbfb9ff4c8534084cc5ab182a7e 31653 urlwatch_2.7.orig.tar.gz 42a365da9f14134443fecb18a2987063b9e3f78e 5876 urlwatch_2.7-1.debian.tar.xz Checksums-Sha256: 03b6b283b3e28ac33916d2e94964df2cf5aff99c0c047f8d33bb23296e91fbae 2047 urlwatch_2.7-1.dsc 0a7b46d161501463dda99a1d82daf00237e2627616beaa6ccbf04d6c70c68ded 31653 urlwatch_2.7.orig.tar.gz 8e15ec715ba8e396a2d35007d3c2639ab42bc414ece0c729972fed43c9474051 5876 urlwatch_2.7-1.debian.tar.xz Files: 3df18345d985e0e3abc727496765de33 2047 web optional urlwatch_2.7-1.dsc 1ce2f7fc219b12ba5705047965037859 31653 web optional urlwatch_2.7.orig.tar.gz b25114b1faf02ae4dcf927bd959ba3d5 5876 web optional urlwatch_2.7-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAlqDqAUACgkQMRa6Xp/6 aaOZKxAAuckua/u86zFw5CZn5TSRze8G+865gHtcIMLopYG2JXrs8S4YEPeufcs4 8DYgdL3Sg0e8dbXAcKGlrJtyNURtoEGSR3sFyfB+qD2yOl12GsVqR5GpcfThiu5V 88eRPS5GKdxg/eni2QG/B0TOnI/eWqkLSx3VqhECavYpo7ETk0McxrzdvT2O7TOs 3R4ScC8JyexTaWh8vjwib9FJHiRxA2RqPfqVRBulT+td9m3Oaj1Y5uuXW01Rbo71 V02MLEZrL/+tgPYEcpCFqV9bv7qasu89S+/eEd4RrjgOKun+/T0MpFoGUJrryFWs c7RQS5EGsWJhJJUW1hXOKOT+CCinxDG1ZuiyptjYlWQJXd79poVVFSfdwAVNoCQv HS5YE/Z66ZyjmL50xi0tg+tTiAAMs5RiO/Zo9Pfi9WElqJZFxzwNaYiQJoKGww5c SKAxdw7amngFeOHtGlzYNHy8sV8XVq2IhjmcFQezQr2lizfQVDgVQuK/WGc5amqV /80/NcjxeOe270srtQAsM+dQuul9oAHazGMyuUwVR0M8966uUKwBa9xG4rvmmB/R jQo8o2t0kCQeRE0SVqAhTWfzVP3miTmtn7x9VR9zoIO4T+ZGJhBMRDW+4+Lk/X5N 8V7lpaIbShOG32zPUGnh2vw0+z9OzsweknpuB25C+UZv1PsFc8g= =1YMU -END PGP SIGNATURE End Message ---
Bug#798312: marked as done (urlwatch: new upstream release 1.18)
Your message dated Wed, 14 Feb 2018 03:20:59 + with message-id and subject line Bug#798312: fixed in urlwatch 2.7-1 has caused the Debian Bug report #798312, regarding urlwatch: new upstream release 1.18 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.) -- 798312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: urlwatch Version: 1.18 Severity: normal Dear Maintainer, urlwatch 1.18 adds lots of new features and fixes some bugs: * Fallback to using pwd if os.getlogin() fails (fixes #2) * Handle HTTP compression (Content-encoding: gzip/deflate) * Add option to suppress output on stdout (-q/--quiet) * Allow customizing subject when sending e-mail (-S/--subject) * Added support for TLS and SMTP auth (-p/--pass, -T/--tls, -A/--auth) * Added support for specifying cache directory (-c/--cache) * Add support for HTTP Auth to urlwatch.handler (fixes #10) An update of the package to the latest upstream release would be welcomed. https://thp.io/2008/urlwatch/urlwatch-1.18.tar.gz Thank you. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (600, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-desktop (SMP w/6 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) --- End Message --- --- Begin Message --- Source: urlwatch Source-Version: 2.7-1 We believe that the bug you reported is fixed in the latest version of urlwatch, 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 798...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maxime Werlen (supplier of updated urlwatch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Feb 2018 06:21:33 +0100 Source: urlwatch Binary: urlwatch Architecture: source Version: 2.7-1 Distribution: unstable Urgency: low Maintainer: Maxime Werlen Changed-By: Maxime Werlen Description: urlwatch - tool for monitoring webpages for updates Closes: 771907 798312 831272 Changes: urlwatch (2.7-1) unstable; urgency=low . * Upgrade Upstream version 2.7. (Closes: #798312) * Removed existing patches as changes wasn't pertinent anymore. * Added a patch to make nose tests work with pybuild (accepted by upstream). * Added a patch fo fix a setuptools warning (accepted by upstream). * Added a patch to remove dependencies from upstream Readme. * Added upstream metadata informations. * Added a NEWS.debian file about migration from urlwatch 1.15 * Added some tests. * Upgraded DH compat to 11. * Changed source repo to salsa.debian.org. * New maintainer. (Closes: #831272) * New version, now support ssl_ni_verify option. (Closes: #771907) Checksums-Sha1: 0448a50dc194e93fb89bfaba207b3f504772e73d 2047 urlwatch_2.7-1.dsc 320a452b5d964fbfb9ff4c8534084cc5ab182a7e 31653 urlwatch_2.7.orig.tar.gz 42a365da9f14134443fecb18a2987063b9e3f78e 5876 urlwatch_2.7-1.debian.tar.xz Checksums-Sha256: 03b6b283b3e28ac33916d2e94964df2cf5aff99c0c047f8d33bb23296e91fbae 2047 urlwatch_2.7-1.dsc 0a7b46d161501463dda99a1d82daf00237e2627616beaa6ccbf04d6c70c68ded 31653 urlwatch_2.7.orig.tar.gz 8e15ec715ba8e396a2d35007d3c2639ab42bc414ece0c729972fed43c9474051 5876 urlwatch_2.7-1.debian.tar.xz Files: 3df18345d985e0e3abc727496765de33 2047 web optional urlwatch_2.7-1.dsc 1ce2f7fc219b12ba5705047965037859 31653 web optional urlwatch_2.7.orig.tar.gz b25114b1faf02ae4dcf927bd959ba3d5 5876 web optional urlwatch_2.7-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAlqDqAUACgkQMRa6Xp/6 aaOZKxAAuckua/u86zFw5CZn5TSRze8G+865gHtcIMLopYG2JXrs8S4YEPeufcs4 8DYgdL3Sg0e8dbXAcKGlrJtyNURtoEGSR3sFyfB+qD2yOl12GsVqR5GpcfThiu5V 88eRPS5GKdxg/eni2QG/B0TOnI/eWqkLSx3VqhECavYpo7ETk0McxrzdvT2O7TOs 3R4ScC8JyexTaWh8vjwib9FJHiRxA2RqPfqVRBulT+td9m3Oaj1Y5uuXW01Rbo71 V02MLEZrL/+tgPYEcpCFqV9bv7qasu89S+/eEd4RrjgOKun+/T0MpFoGUJrryFWs c7RQS5EGsWJhJJUW1hXOKOT+CCinxDG1ZuiyptjYlWQJXd79poVVFSfdwAVNoCQv HS5YE/Z66Z
Bug#831272: marked as done (ITA: urlwatch -- tool for monitoring webpages for updates)
Your message dated Wed, 14 Feb 2018 03:20:59 + with message-id and subject line Bug#831272: fixed in urlwatch 2.7-1 has caused the Debian Bug report #831272, regarding ITA: urlwatch -- tool for monitoring webpages for updates 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.) -- 831272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: normal The current maintainer of urlwatch, Franck Joncourt , has retired. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: urlwatch Binary: urlwatch Version: 1.15-3 Maintainer: Franck Joncourt Build-Depends: debhelper (>= 7.0.50) Build-Depends-Indep: python (>= 2.6.6-3~), python-concurrent.futures Architecture: all Standards-Version: 3.9.4 Format: 3.0 (quilt) Files: e01d684c3f1599c6f9716fee8a428f6d 1270 urlwatch_1.15-3.dsc d5ab654d59823238b69f557338cdbc93 13105 urlwatch_1.15.orig.tar.gz d8bff1bfcf521589931015099d8df526 4308 urlwatch_1.15-3.debian.tar.gz Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/urlwatch.git;a=summary Vcs-Git: git://anonscm.debian.org/collab-maint/urlwatch.git Checksums-Sha256: 12516f59fb8e752857f32ad5c2717faba06d9341819ff3a0bb189384eced527c 1270 urlwatch_1.15-3.dsc b1bdc3aa5bc55c203c6a9df293dee3963061dae610b06ade0f1f8eb100abeb3f 13105 urlwatch_1.15.orig.tar.gz c3f72176e77b4600bd04637537d6244488deff9acc64b9226ad014129468b1af 4308 urlwatch_1.15-3.debian.tar.gz Homepage: http://thpinfo.com/2008/urlwatch/ Package-List: urlwatch deb web extra Directory: pool/main/u/urlwatch Priority: source Section: web Package: urlwatch Binary: urlwatch Version: 1.15-3 Maintainer: Franck Joncourt Build-Depends: debhelper (>= 7.0.50) Build-Depends-Indep: python (>= 2.6.6-3~), python-concurrent.futures Architecture: all Standards-Version: 3.9.4 Format: 3.0 (quilt) Files: e01d684c3f1599c6f9716fee8a428f6d 1270 urlwatch_1.15-3.dsc d5ab654d59823238b69f557338cdbc93 13105 urlwatch_1.15.orig.tar.gz d8bff1bfcf521589931015099d8df526 4308 urlwatch_1.15-3.debian.tar.gz Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/urlwatch.git;a=summary Vcs-Git: git://anonscm.debian.org/collab-maint/urlwatch.git Checksums-Sha1: cd44bc683d636bf6ddaf72462c07ba1b479fd68e 1270 urlwatch_1.15-3.dsc 5d31b1c21ef8dd43f126b0001e3d7a64153dea71 13105 urlwatch_1.15.orig.tar.gz 55f5987dd93311c3f7ebdc131cecb71b8556fe97 4308 urlwatch_1.15-3.debian.tar.gz Checksums-Sha256: 12516f59fb8e752857f32ad5c2717faba06d9341819ff3a0bb189384eced527c 1270 urlwatch_1.15-3.dsc b1bdc3aa5bc55c203c6a9df293dee3963061dae610b06ade0f1f8eb100abeb3f 13105 urlwatch_1.15.orig.tar.gz c3f72176e77b4600bd04637537d6244488deff9acc64b9226ad014129468b1af 4308 urlwatch_1.15-3.debian.tar.gz Homepage: http://thpinfo.com/2008/urlwatch/ Package-List: urlwatch deb web extra Directory: pool/main/u/urlwatch Priority: source Section: web Package: urlwatch Version: 1.15-3 Installed-Size: 93 Maintainer: Franck Joncourt Architecture: all Depends: python (>= 2.6.6-7~), python-concurrent.futures Recommends: python-vobject, python-utidylib, lynx Suggests: html2text Description-en: tool for monitoring webpages for updates This script is intended to help you watch URLs and get notified (via email) of any changes. The change notification will include the URL that has changed and a unified diff of what has changed. The script supports the use of a filtering hook function to strip trivially-varying elements of a webpage. Description-md5: 8d22938bf95fd6b49e05a9bd5ae08997 Homepage: http://thpinfo.com/2008/urlwatch/ Tag: implemented-in::python, interface::commandline, role::program, scope::utility, use::monitor Section: web Priority: extra Filename: pool/main/u/urlwatch/urlwatch_1.15-3_all.deb Size: 17490 MD5sum: fdcfd81777b5072a62b1fdb90b934f13 SHA256: e2aebc8d83566d42ed128a67f0f4f352035889d289e8f1d381fccadc8951e1ea Package: urlwatch Version: 1.15-3 Installed-Size: 93 Maintainer: Franck Joncourt Architecture: all Depends: python (>= 2.6.6-7~), python-concurrent.futures Recommends: python-vobject, python-utidylib, lynx Suggests: html2text Description-en: tool for monitoring webpages for updates This script is intended to help you watch URLs and get notified (via email) of any
Bug#864428: marked as done (RFS: bitfield/1.0.1-1 [ITP #864358])
Your message dated Wed, 14 Feb 2018 04:35:34 + with message-id and subject line closing RFS: bitfield/1.0.1-1 [ITP #864358] has caused the Debian Bug report #864428, regarding RFS: bitfield/1.0.1-1 [ITP #864358] 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.) -- 864428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "bitfield" * Package name : bitfield Version : 0.6.3-1 Upstream Author : Vitalie Ciubotaru (me) * URL : https://github.com/ciubotaru/bitfield * License : GPLv3+ Section : libs It builds those binary packages: bitfield - bit array manipulation library in C bitfield-dev - bit array manipulation library in C -- development package To access further information about this package, please visit the following URL: https://mentors.debian.net/package/bitfield Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/b/bitfield/bitfield_0.6.3-1.dsc Best regards, Vitalie Ciubotaru --- End Message --- --- Begin Message --- Package bitfield has been removed from mentors.--- End Message ---
Bug#887295: marked as done (tomb should depend on e2fsprogs explicitly)
Your message dated Wed, 14 Feb 2018 05:50:06 + with message-id and subject line Bug#887295: fixed in tomb 2.5+dfsg1-1 has caused the Debian Bug report #887295, regarding tomb should depend on e2fsprogs explicitly 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.) -- 887295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tomb Version: 2.4+dfsg1-1 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting there all packages that use e2fsprogs must be identified and gain a dependency on it as e2fsprogs currently is essential. tomb was identified as potentially needing such a dependency, because it mentions tool names from e2fsprogs in the following files: /usr/bin/tomb contains e2fsck, mkfs.ext4, resize2fs and tune2fs. According to file it is a a /usr/bin/env zsh script, ASCII text executable Please investigate whether these cases are actually uses of a tool from e2fsprogs. Care has been taken to shrink the number of candidates as much as possible, but a few false positives will remain. After doing so, do one of the following: * Add e2fsprogs to Depends. * Add e2fsprogs to Recommends. * Close this bug explaining why e2fsprogs is not used by this package. Once e2fsprogs drops the "Essential: yes" flag, this bug will be upgraded to RC severity. Please note that lintian will warn about such a dependency before lintian 2.5.56. Thanks for your help Helmut --- End Message --- --- Begin Message --- Source: tomb Source-Version: 2.5+dfsg1-1 We believe that the bug you reported is fixed in the latest version of tomb, 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 887...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. ChangZhuo Chen (陳昌倬) (supplier of updated tomb 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: Wed, 14 Feb 2018 13:29:49 +0800 Source: tomb Binary: tomb Architecture: source Version: 2.5+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Packaging Team Changed-By: ChangZhuo Chen (陳昌倬) Description: tomb - crypto undertaker Closes: 887295 Changes: tomb (2.5+dfsg1-1) unstable; urgency=medium . [ Andreas Henriksson ] * Add e2fsprogs dependency (Closes: #887295) . [ ChangZhuo Chen (陳昌倬) ] * New upstream release. * Bump Standards-Version to 4.1.3. * Bump compat to 11. * Update Vcs-* fields to salsa.debian.org. Checksums-Sha1: 3e8f03149f7fdac723f77a962c74d9f5074ffc59 1931 tomb_2.5+dfsg1-1.dsc 4eb6c4fb1dd8fa8781d7b179f55242af5575c469 1378896 tomb_2.5+dfsg1.orig.tar.gz ae28c39c693d6fd8ad2ece3bd7c1cfb2afc22443 2564 tomb_2.5+dfsg1-1.debian.tar.xz 3e2f428834eed75b4e2ff282d2197498b49a8f99 5389 tomb_2.5+dfsg1-1_source.buildinfo Checksums-Sha256: e30b243c716894b2d5461b60156bd1b8a252b46112de46b2b26f8afe19a626d2 1931 tomb_2.5+dfsg1-1.dsc fbd194d24a8ec258bb5b92ee09712e58d8e5fb191a1231f286609bbab989c2e8 1378896 tomb_2.5+dfsg1.orig.tar.gz 4f572beb2e8d1af12fbbb0ec25240cd667be5883401f02640182c56a1e11a0f5 2564 tomb_2.5+dfsg1-1.debian.tar.xz db42163ef90e42874747bb0bfc17bcb01e481d6e71f3baad6b15bc06412a2976 5389 tomb_2.5+dfsg1-1_source.buildinfo Files: 829f784442596541c8dc722081d08f49 1931 utils optional tomb_2.5+dfsg1-1.dsc d2cde89aef064050a5ba90f9d6248ae7 1378896 utils optional tomb_2.5+dfsg1.orig.tar.gz 004948bb3c2d1a8aacb530582a1c447b 2564 utils optional tomb_2.5+dfsg1-1.debian.tar.xz 28ac51293207fb6ddff100d65273f4db 5389 utils optional tomb_2.5+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEugQ0bcLh/mPHkIeTzGWwzewnXVsFAlqDyWYACgkQzGWwzewn XVvqLQ//ZUQwQirJE0lHZpjV2Tq7fGnmHdsRYyXKMIKbVOiVmP/NWuu6+xP81oPK HNKyNS3S7No+n9WmpNJxHbxVyOjaQGoZtAOjgIos//cQCwdS/Tsp1wF9zmGchItQ 6Wbg6SFMdIO4bnU4QtxD1UyMIf7j4zRttg2kPcixddEPrNSN757KlG0eu9aVoNEz WP6Vn+QH20BJWnoI+ZPSHGxpkOknHJIrtVZLA8Olepe80E1wziD6DGLUtmpqT4bR 8ROVVwyKtuPOqFTKPgzhPzy8muap98
Bug#890319: marked as done (telegram-desktop: please package telegram upstream v1.2.8)
Your message dated Wed, 14 Feb 2018 08:49:35 +0300 with message-id <2518568d-9a73-2ac5-a56a-6964843f0...@ya.ru> and subject line Re: Bug#890319: telegram-desktop: please package telegram upstream v1.2.8 has caused the Debian Bug report #890319, regarding telegram-desktop: please package telegram upstream v1.2.8 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.) -- 890319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: telegram-desktop Version: 1.2.6-2 Severity: wishlist Dear Maintainer, Please package new upstream v1.2.8 https://github.com/telegramdesktop/tdesktop/releases/tag/v1.2.8 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IN.UTF-8), LANGUAGE=en_IN.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IN.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages telegram-desktop depends on: ii libavcodec57 7:3.4.1-1+b2 ii libavformat577:3.4.1-1+b2 ii libavutil55 7:3.4.1-1+b2 ii libc62.26-6 ii libgcc1 1:7.2.0-19 ii libglib2.0-0 2.54.3-2 ii libminizip1 1.1-8+b1 ii libopenal1 1:1.18.2-2 ii libqt5core5a [qtbase-abi-5-9-2] 5.9.2+dfsg-9 ii libqt5dbus5 5.9.2+dfsg-9 ii libqt5gui5 5.9.2+dfsg-9 ii libqt5network5 5.9.2+dfsg-9 ii libqt5widgets5 5.9.2+dfsg-9 ii libssl1.11.1.0g-2 ii libstdc++6 7.2.0-19 ii libswresample2 7:3.4.1-1+b2 ii libswscale4 7:3.4.1-1+b2 ii libtgvoip1.0 1.0~git20170704.445433f-4 ii libx11-6 2:1.6.4-3 ii qt5-image-formats-plugins5.9.2-2 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages telegram-desktop recommends: ii libappindicator3-1 0.4.92-5 telegram-desktop suggests no packages. -- 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 EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 --- End Message --- --- Begin Message --- Control: tag -1 wontfix Hi, 13.02.2018 15:07, shirish शिरीष пишет: > Please package new upstream v1.2.8 > > https://github.com/telegramdesktop/tdesktop/releases/tag/v1.2.8 Sorry, this is pre-release version and so it won't be packaged. The latest stable version available on desktop.telegram.org is v1.2.6.--- End Message ---
Processed: closing 794166
Processing commands for cont...@bugs.debian.org: > close 794166 Bug #794166 [wnpp] ITP: ddnet -- A Teeworlds modification with a unique cooperative gameplay Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 794166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
