Bug#1026373: json11: Upstream dead, known encoding bugs
Control: severity -1 serious Last remaining package in unstable dropped its (build-)depends, raising severity so json11 will go away from testing.
Processed: Re: json11: Upstream dead, known encoding bugs
Processing control commands: > severity -1 serious Bug #1026373 [src:json11] json11: Upstream dead, known encoding bugs Severity set to 'serious' from 'important' -- 1026373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984274: openclonk: ftbfs with GCC-11
Source: openclonk Version: 8.1-2 Followup-For: Bug #984274 X-Debbugs-Cc: i...@hack3r.moe Hello, I've attached a patch that includes header in relevant file and fixes GCC 11 build. If more help is needed, please let me know. Cheers, Eric --- a/src/script/C4AulParse.cpp +++ b/src/script/C4AulParse.cpp @@ -15,6 +15,8 @@ */ // parses scripts +#include + #include "C4Include.h" #include "script/C4AulParse.h"
Bug#863596: marked as done (mytop can't be installed)
Your message dated Tue, 20 Dec 2022 15:58:19 + with message-id and subject line Bug#1026428: Removed package(s) from unstable has caused the Debian Bug report #863596, regarding mytop can't be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 863596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mytop Version: 1.9.1-4 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, with the last mariadb upgrade I get: ~ > apt-get install mytop Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation angefordert haben oder, wenn Sie die Unstable-Distribution verwenden, dass einige erforderliche Pakete noch nicht erstellt wurden oder Incoming noch nicht verlassen haben. Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen: Die folgenden Pakete haben unerfüllte Abhängigkeiten: mariadb-client-10.1 : Kollidiert mit: mytop aber 1.9.1-4 soll installiert werden E: Fehler: Unterbrechungen durch pkgProblemResolver::Resolve hervorgerufen; dies könnte durch zurückgehaltene Pakete verursacht worden sein. - -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/6 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) -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlkrl74ACgkQCfifPIyh 0l21fxAAh4bIU82OrwMKbBCbM3JP652VrfY7Qw5flAdeyEVBfSDYaoJcCSt1oJK3 00ncmRNVHj37wVz4W4qhy/0qE8U4Ly2jIka3GorsIsDQNfS6c0TUVnfplxqQiKtS 504xocVVLpv1Rr/RxovqlMhLyGlq5g3H4bdtHjGkvCxiht5Pv+aVJxejXk/beFgi 6c6fQLXN+G+Uu42lT++b/7ej1jPoxZvjQuKIpx1A2XvI9036e0TRXcWpjLWyAzot f2YiJnJy2+lewbexyDlJnXZALDfNIaGUrrvA0N9H9lzQv+KG5ZomLOFK96UiD4O3 DLbJuAstGxBD1tdlX5cpTAgxE8DnpqSZsGJo9u/qOkPP8fAbPrWHtFmo4i1oPhAL x7nFt+mtZbp+siAFtKa1OXqjj/k3J09JkUxIcjjgniyIu/dGVURs970NTOSxTxSg qxqvTWvGkgxh0YHo0GK3wj/ppVfmxrGdouCZ/zY8tloyVWY26gzgUxtO6owy8Xyj IFGURHdaDycsIwfr327J6tQolk9/1dUdYg0ZSgIHWzElsztHthZugHaTBZIDFo19 7Rj6xSdXkqBMN+P6Nh33BKb4rfvWLa1UIvg7KprQnBDXUojPyuJORjZlZGal3cWf XNdRX1YC9BN3eulfyDPiWUWuaoEDNAZElx0PpHBopSjE0Mvdp5k= =dXLj -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 1.9.1-5+rm Dear submitter, as the package mytop has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026428 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#903113: marked as done (mytop error when using MySQL ANSI_QUOTES mode: Use of uninitialized value in string ne at /usr/bin/mytop line 1063.)
Your message dated Tue, 20 Dec 2022 15:58:19 +
with message-id
and subject line Bug#1026428: Removed package(s) from unstable
has caused the Debian Bug report #903113,
regarding mytop error when using MySQL ANSI_QUOTES mode: Use of uninitialized
value in string ne at /usr/bin/mytop line 1063.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
903113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mytop
Version: 1.9.1-4
Perl version: 5.18.2-2ubuntu1.6
I encountered this bug in the Ubuntu package and reported it here:
https://bugs.launchpad.net/bugs/1778745
I have verified that the problem also exists in Debian unstable.
Output when run on a system with sql-mode including ANSI_QUOTES:
MySQL on localhost (5.6.33)load 0.39 0.54 0.58 2/1749 31690 up
124+10:33:39 [10:20:13]
Queries: 6.7M qps:1 Slow: 107.0 Se/In/Up/De(%):
87/00/11/00
Sorts: 0 qps now:1 Slow qps: 0.0 Threads:3 ( 1/ 3)
00/00/00/00
Key Efficiency: 99.9% Bps in/out: 274.6/205.3 Now in/out: 22.6/ 2.4k
Use of uninitialized value in string ne at /usr/bin/mytop line 1063.
ReadOnly
Id User Host/IP DB TimeCmdState Query
-- --- -- ---
- --
1007 root localhost 0 Query init show f
I'm running MySQL with the following sql-mode in my.cnf:
sql-mode = "STRICT_TRANS_TABLES,ANSI_QUOTES,NO_ENGINE_SUBSTITUTION"
By default MySQL treats single and double quotes interchangeably and
uses backticks for escaping table/column names.
The "ANSI_QUOTES" option causes MySQL to use ANSI standard quoting
(double quotes), so it no longer allows double quotes for string
literals.
Line 1063 of mytop is:
my($data) = Hashes('show global variables like "read_only"');
Attempting to execute that statement results in the following error from MySQL:
mysql> show global variables like "read_only";
ERROR 1064 (42000): You have an error in your SQL syntax; check the
manual that corresponds to your MySQL server version for the right
syntax to use near '"read_only"' at line 1
Whereas using single quotes works as expected:
mysql> show global variables like 'read_only';
+---+---+
| Variable_name | Value |
+---+---+
| read_only | OFF |
+---+---+
1 row in set (0,00 sec)
When MySQL's sql-mode is set to include ANSI_QUOTES mytop spits out
the following in the header:
Use of uninitialized value in string ne at /usr/bin/mytop line 1063.
ReadOnly
Changing line 1063 to use single quotes in the SQL statement sent to
MySQL resolves the problem.
The fix is just to swap the single quotes to double quotes in that
line, and vice versa as in the attached patch.
--
Michael Wood
Description: fix quoting when in ANSI_QUOTES mode
Author: Michael Wood
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1778745
--- a/mytop
+++ b/mytop
@@ -1059,7 +1059,7 @@ sub GetData()
$lines_left--;
-my($read_only) = Hashes('show global variables like "read_only"');
+my($read_only) = Hashes("show global variables like 'read_only'");
if ($read_only->{Value} ne "OFF")
{
print RED() if ($HAS_COLOR) ;
--- End Message ---
--- Begin Message ---
Version: 1.9.1-5+rm
Dear submitter,
as the package mytop has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1026428
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1006290: marked as done (kvmtool: CVE-2021-45464: hypervisor escape and host code execution)
Your message dated Tue, 20 Dec 2022 16:05:26 + with message-id and subject line Bug#1026459: Removed package(s) from unstable has caused the Debian Bug report #1006290, regarding kvmtool: CVE-2021-45464: hypervisor escape and host code execution to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1006290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kvmtool Version: 0.20170904-1.1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for kvmtool. CVE-2021-45464[0]: | hypervisor escape and host code execution 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-2021-45464 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45464 [1] https://www.kalmarunionen.dk/writeups/2021/hxp-2021/lkvm/ Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.20170904-2+rm Dear submitter, as the package kvmtool has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026459 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#569831: marked as done (debget: doesn't handle 1:N source:binary packages)
Your message dated Tue, 20 Dec 2022 16:04:26 + with message-id and subject line Bug#1026457: Removed package(s) from unstable has caused the Debian Bug report #569831, regarding debget: doesn't handle 1:N source:binary packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 569831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debget Version: 1.6+nmu1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 i'd expect that when downloading binary package(s) with -b that it fetched all binary packages produced by the source package in question. rangda[/home/sean/debian] debget -b php5 :) dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. pool/main/p/php5/php5_5.3.1-4.diff.gz pool/main/p/php5/php5_5.3.1-4.dsc pool/main/p/php5/php5_5.3.1.orig.tar.gz pool/main/p/php5/php5_5.3.1-4_all.deb rangda[/home/sean/debian] apt-cache showsrc php5 | grep Binary | head -1 :) Binary: php5, php5-common, libapache2-mod-php5, libapache2-mod-php5filter, php5-cgi, php5-cli, php5-dev, php5-dbg, php-pear, php5-curl, php5-gd, php5-gmp, php5-imap, php5-interbase, php5-ldap, php5-mcrypt, php5-mhash, php5-mysql, php5-odbc, php5-pgsql, php5-pspell, php5-recode, php5-snmp, php5-sqlite, php5-sybase, php5-tidy, php5-xmlrpc, php5-xsl - -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debget depends on: ii libapt-pkg-perl 0.1.24 Perl interface to libapt-pkg ii libproc-waitstat-perl 1.00-4 interpret and act on wait() status ii libwww-perl 5.834-1Perl HTTP/WWW client/server librar ii perl 5.10.1-11 Larry Wall's Practical Extraction ii perl-modules [libnet-perl]5.10.1-11 Core Perl modules debget recommends no packages. Versions of packages debget suggests: ii devscripts2.10.61scripts to make the life of a Debi - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLeB7BynjLPm522B0RAowzAJ42TCGsZWgfcwFNyy40c6NnR1qtxQCfWlWm Wfmwr7AdgLOARt+MOogwHrQ= =x1tK -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 1.6+nmu6+rm Dear submitter, as the package debget has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026457 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#318643: marked as done (debget: doesn't work (segfaults))
Your message dated Tue, 20 Dec 2022 16:04:26 + with message-id and subject line Bug#1026457: Removed package(s) from unstable has caused the Debian Bug report #318643, regarding debget: doesn't work (segfaults) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 318643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debget Version: 1.5 Severity: important Hi, thanks for maintaining this package. When I try to use debget, it segfaults without downloading anything. stefan@Arkelon:/tmp$ debget debget debget: can't get pool directory for debget Speicherzugriffsfehler Maybe this bug is related to (or the same as) #317058. Cheers, Stefan. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11nh4 Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Versions of packages debget depends on: ii libapt-pkg-perl 0.1.15 Perl interface to libapt-pkg ii libproc-waitstat-perl 1.00-3 interpret and act on wait() status ii libwww-perl 5.803-4WWW client/server library for Perl ii perl 5.8.7-4Larry Wall's Practical Extraction ii perl-modules [libnet-perl]5.8.7-4Core Perl modules debget recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1.6+nmu6+rm Dear submitter, as the package debget has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026457 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#816393: marked as done (debget: does not download tar.xz orig files)
Your message dated Tue, 20 Dec 2022 16:04:26 + with message-id and subject line Bug#1026457: Removed package(s) from unstable has caused the Debian Bug report #816393, regarding debget: does not download tar.xz orig files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 816393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debget Version: 1.6+nmu3 Severity: important Dear Maintainer, debget is unable to download packages with orig tarballs compresses with xz. Example: $ debget nghttp2 pool/main/n/nghttp2/nghttp2_1.8.0-1.dsc debget: no files in pool/main/n/nghttp2 match /(?^:^nghttp2_1\.8\.0\.orig\.tar\.gz$)/ This renders the package unusable to roughly 1/8 of all source packages. Cheers, Tomasz -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.2 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debget depends on: ii libapt-pkg-perl 0.1.29+b5 ii libproc-waitstat-perl1.00-4.2 ii libwww-perl 6.15-1 ii perl 5.22.1-7 ii perl-modules-5.22 [libnet-perl] 5.22.1-7 debget recommends no packages. Versions of packages debget suggests: ii devscripts 2.16.1 -- no debconf information --- End Message --- --- Begin Message --- Version: 1.6+nmu6+rm Dear submitter, as the package debget has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026457 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#723580: marked as done (kytea: bad package description)
Your message dated Tue, 20 Dec 2022 16:04:52 + with message-id and subject line Bug#1026458: Removed package(s) from unstable has caused the Debian Bug report #723580, regarding kytea: bad 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.) -- 723580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kytea Version: 0.4.6+dfsg-2 Severity: wishlist Tags: patch This package has a terrible package description. (I'm still only calling this a wishlist bug, though.) > Package: kytea [...] > Description: morphological analysis system with pointwise predictors Not bad, but the implementation details aren't worth putting in the synopsis. What it does need to establish in the synopsis is that this is for morphological analysis in the linguistic sense, rather than the biological or marketing senses - see: http://en.wikipedia.org/wiki/Morphological_analysis The easy way to do that is to insert the word "text". > KyTea is morphological analysis system based on pointwise predictors. ^ Missing article: KyTea is *a* morphological analysis system. Implementation details are okay here, but talking about "pointwise predictors" is excruciatingly esoteric. "Pointwise classifier" is already specialist jargon; and stretching it you can talk about pointwise classifier-based analyses making "pointwise predictions" (though it's rather weird to talk about morphological judgements as "predictions"). But you'll notice if you google the expression that almost the entire top page of results is versions of this package description! The home page has some clearer explanations that avoid the phrase, and I recommend using some of that text. > It separetes sentences into words, tagging and predict pronunciations. ^ --- ^ Spelling: "separAtes". "Tagging" on its own can be unclear; I would suggest "tagging parts of speech". "Predict" should be "predicting", or preferably (as on the home page) "estimating". It's only a prediction if the word has never been spoken before! > The pronunciation of KyTea is same as cutie. ^ Missing article, and awkward phrasing - you could simply say when you first mention KyTea that it's "pronounced 'cutie'". In fact, you could start by explaining the name - it would at least serve to distract slightly from the fact that somebody has made a rather bad prediction of how "kytea" would be pronounced. The mention of Kyoto would also be useful for another reason: the description so far gives no hint of the fact that KyTea is specifically designed to handle (unromanised, unspaced) Japanese script. That may seem obvious to you, but if somebody is looking for a tool to do POS-tagging on the collected works of Shakespeare then it's the job of this package description to let them know that KyTea isn't what they're after. > . > This package contains predictor and training tool. Likewise for the other packages in the set: > Package: libkytea0 [...] > Description: library of KyTea Standardise these synopses. > KyTea is morphological analysis system based on pointwise predictors. > It separetes sentences into words, tagging and predict pronunciations. > The pronunciation of KyTea is same as cutie. As above. > . > This package contains shared libraries of KyTea. Missing article. I would also make it "for" rather than "of". > Package: libkytea-dev [...] > Description: library of KyTea : development files As above. Colons in English never have preceding space, but I'd recommend using a dash anyway. > KyTea is morphological analysis system based on pointwise predictors. > It separetes sentences into words, tagging and predict pronunciations. > The pronunciation of KyTea is same as cutie. > . > This package contains development files of KyTea. All as above. My recommended replacement text: | Package: libkytea0 [...] | Description: text morphological analysis system - libraries | The Kyoto Text Analysis toolkit (KyTea, pronounced "cutie") is a general | morphological analysis system with a focus on Japanese, Chinese, and | other languages requiring word or morpheme segmentation. It uses a | pointwise classifier-based approach to split sentences into words, | tagging parts of speech and estimating pronunciations. | . | This package contains the shared libraries for KyTea. | | Package: kytea [...] | Description: text morphological analysis system - binaries | The Kyoto Text Ana
Bug#799805: marked as done (kytea: Problem with upcoming new version of liblinear)
Your message dated Tue, 20 Dec 2022 16:04:52 +
with message-id
and subject line Bug#1026458: Removed package(s) from unstable
has caused the Debian Bug report #799805,
regarding kytea: Problem with upcoming new version of liblinear
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
799805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kytea
Version: 0.4.6+dfsg-2
Severity: important
Hi,
I recently uploaded a new version of liblinear to experimental. This new
version bumps the SONAME. Among other things, the declaration of "struct
problem" in linear.h changed:
> struct problem
> {
> int l, n;
> - int *y;
> + double *y;
> struct feature_node **x;
> double bias;/* < 0 if no bias term */
> };
Test-rebuilding the reverse dependency kytea resulted in a FTBFS because
of the above change:
> kytea-model.cpp: In member function 'void kytea::KyteaModel::trainModel(const
> std::vector >&, std::vector&, double, int,
> double, double)':
> kytea-model.cpp:180:12: error: cannot convert 'int*' to 'double*' in
> assignment
> prob.y = &ys.front();
^^
After applying the following simple workaround to
src/lib/kytea-model.cpp, the package builds successfully again:
> // }
> // cerr << endl;
> // }
> -prob.y = &ys.front();
> +vector ys_d(ys.begin(), ys.end());
> +prob.y = &ys_d.front();
>
> // allocate the feature space
> feature_node** myXs =
> (feature_node**)malloc(sizeof(feature_node*)*xs.size());
However, unfortunately the one test no longer passes. It just hangs in
what appears to be an infinite loop. Specifically, it hangs at the test
for logistic regression: that's the second test (with "-solver 0") in
src/test/test-analysis.h.
The hang occurs in the trainAll() step. That calls trainWS() (commented
as "word segmenter"), which prepares some data, and then eventually calls
> wsModel_->trainModel(xs,ys,config_->getBias(),config_->getSolverType(),config_->getEpsilon(),config_->getCost());
That's as far as I got.
I'm not familiar with kytea, so I'm not sure what data is being prepared
here and how, which makes debugging difficult.
I'd appreciate it if you, or your upstream, could take a look!
Regards,
Christian
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.4.6+dfsg-3+rm
Dear submitter,
as the package kytea has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1026458
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#804356: marked as done (kytea: FTBFS: kytea-model.cpp:180:12: error: cannot convert 'int*' to 'double*' in assignment)
Your message dated Tue, 20 Dec 2022 16:04:52 + with message-id and subject line Bug#1026458: Removed package(s) from unstable has caused the Debian Bug report #799805, regarding kytea: FTBFS: kytea-model.cpp:180:12: error: cannot convert 'int*' to 'double*' in assignment to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 799805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kytea Version: 0.4.6+dfsg-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, kytea fails to build from source in unstable/amd64: [..] libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../src/include/kytea -I./../include -DPKGDATADIR=\"/usr/share/kytea\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c kytea-model.cpp -fPIC -DPIC -o .libs/kytea-model.o kytea-model.cpp: In member function 'void kytea::KyteaModel::trainModel(const std::vector >&, std::vector&, double, int, double, double)': kytea-model.cpp:180:12: error: cannot convert 'int*' to 'double*' in assignment prob.y = &ys.front(); ^ Makefile:454: recipe for target 'kytea-model.lo' failed make[3]: *** [kytea-model.lo] Error 1 make[3]: Leaving directory '/build/kytea-0.4.6+dfsg/src/lib' Makefile:349: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/build/kytea-0.4.6+dfsg/src' Makefile:449: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/build/kytea-0.4.6+dfsg' dh_auto_build: make -j1 returned exit code 2 debian/rules:4: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/kytea_0.4.6+dfsg-2.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- kytea.0.4.6+dfsg-2.unstable.amd64.log.txt.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 0.4.6+dfsg-3+rm Dear submitter, as the package kytea has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026458 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#827525: marked as done (kvmtool: FTBFS on mips64el: guest/guest_init.o: linking 32-bit code with 64-bit code)
Your message dated Tue, 20 Dec 2022 16:05:26 + with message-id and subject line Bug#1026459: Removed package(s) from unstable has caused the Debian Bug report #827525, regarding kvmtool: FTBFS on mips64el: guest/guest_init.o: linking 32-bit code with 64-bit code to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 827525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kvmtool Version: 0.20160419-1 Severity: important Tags: sid + patch Justification: FTBFS User: debian-m...@lists.debian.org Usertags: mips-patch Package kvmtool FTBFS for mips64el with the following error: > LINK lkvm > /usr/bin/ld: guest/guest_init.o: warning: linking abicalls files with > non-abicalls files > /usr/bin/ld: guest/guest_init.o: linking 32-bit code with 64-bit code > /usr/bin/ld: failed to merge target specific data of file guest/guest_init.o > collect2: error: ld returned 1 exit status > Makefile:381: recipe for target 'lkvm' failed > make[1]: *** [lkvm] Error 1 Full build log: https://buildd.debian.org/status/fetch.php?pkg=kvmtool&arch=mips64el&ver=0.20160419-1&stamp=1463209003 The reason for that is behaviour is the way of creation guest_init.o. > ld -r -b binary -o guest/guest_init.o guest/init Resulting file is "MIPS-I" instead of expected "MIPS64 rel2". > file guest/guest_init.o.cp > guest/guest_init.o.cp: ELF 64-bit LSB relocatable, MIPS, MIPS-I version 1 > (SYSV), not stripped If options "-r -b binary" are used, linker will ignore flags of input file "Flags: 0x8006, pic, cpic, mips64r2", and flags of resulting guest_init.o file will be "Flags: 0x0". Solution for this issue could be using different method for creation guest_init.o. If xxd and gcc are used instead of ld, resulting file will have regular flags. > xxd -i guest/init | $(CC) -c -x c - -o guest/guest_init.o Here are proposed changes for this issue. http://www.spinics.net/lists/kvm/msg118016.html I have created a patch that fixes this issue modeled on mentioned solution. Using this patch I was able to build kvmtool for mips64el, mipsel, i386, amd64. The patch is attached. Could you please consider including this patch. --- kvmtool-0.20160419.orig/Makefile +++ kvmtool-0.20160419/Makefile @@ -395,8 +395,7 @@ endif $(GUEST_INIT): guest/init.c $(E) " LINK" $@ $(Q) $(CC) $(GUEST_INIT_FLAGS) guest/init.c -o $@ - $(Q) $(LD) -r -b binary -o guest/guest_init.o $(GUEST_INIT) - + $(Q) xxd -i $@ | $(CC) -c -x c - -o guest/guest_init.o %.s: %.c $(Q) $(CC) -o $@ -S $(CFLAGS) -fverbose-asm $< --- kvmtool-0.20160419.orig/builtin-setup.c +++ kvmtool-0.20160419/builtin-setup.c @@ -146,8 +146,8 @@ static int extract_file(const char *gues return 0; } -extern char _binary_guest_init_start; -extern char _binary_guest_init_size; +extern char guest_init; +extern char guest_init_len; extern char _binary_guest_pre_init_start; extern char _binary_guest_pre_init_size; @@ -163,8 +163,8 @@ int kvm_setup_guest_init(const char *gue return err; #endif err = extract_file(guestfs_name, "virt/init", -&_binary_guest_init_start, -&_binary_guest_init_size); +&guest_init, +&guest_init_len); return err; } #else --- End Message --- --- Begin Message --- Version: 0.20170904-2+rm Dear submitter, as the package kvmtool has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026459 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#817962: marked as done (kvmtool: needs an appropriate initrd and/or a new flavour of Linux kernel image)
Your message dated Tue, 20 Dec 2022 16:05:26 + with message-id and subject line Bug#1026459: Removed package(s) from unstable has caused the Debian Bug report #817962, regarding kvmtool: needs an appropriate initrd and/or a new flavour of Linux kernel image to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 817962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kvmtool Version: 0.20160203-1 Severity: important I don't think we should ship kvmtool in stretch without a Linux kernel flavour for it. If you agree, please upgrade this bug to serious. Right now the Debian Linux kernel packages don't have CONFIG_NET_9P_VIRTIO and CONFIG_VIRTIO_NET enabled. For kvmtool we probably want a trimmed down Linux flavour for both speed and attack surface reduction. pabs@chianamo ~ $ lkvm run # lkvm run -k /boot/vmlinuz-4.4.0-1-amd64 -m 448 -c 4 --name guest-15121 PPrroobbiinngg EE ((ee==oo ttoo ddiissaabbllee)).. ookk [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160224 (Debian 5.3.1-10) ) #1 SMP Debian 4.4.4-2 (2016-03-09) [0.00] Command line: noapic noacpi pci=conf1 reboot=k panic=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 console=ttyS0 earlyprintk=serial i8042.noaux=1 rw rootflags=trans=virtio,version=9p2000.L,cache=loose rootfstype=9p init=/virt/pre_init ip=dhcp [0.00] CPU: vendor_id 'LKVMLKVMLKVM' unknown, using generic init. [0.00] CPU: Your system may be unstable. [0.00] x86/fpu: Legacy x87 FPU detected. [0.00] x86/fpu: Using 'lazy' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000e] reserved [0.00] BIOS-e820: [mem 0x0010-0x1bff] usable [0.00] bootconsole [earlyser0] enabled [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] Hypervisor detected: KVM [0.00] e820: last_pfn = 0x1c000 max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] MTRR: Disabled [0.00] CPU MTRRs all blank - virtualized system. [0.00] found SMP MP-table at [mem 0x000f0370-0x000f037f] mapped at [880f0370] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI BIOS Error (bug): A valid RSDP was not found (20150930/tbxfroot-243) [0.00] No NUMA configuration found [0.00] Faking a node at [mem 0x-0x1bff] [0.00] NODE_DATA(0) allocated [mem 0x1bffc000-0x1bff] [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [0.00] kvm-clock: cpu 0, msr 0:1bff4001, primary cpu clock [0.00] kvm-clock: using sched offset of 189012120618513 cycles [0.00] clocksource: kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [0.00] Zone ranges: [0.00] DMA32[mem 0x1000-0x1bff] [0.00] Normal empty [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009efff] [0.00] node 0: [mem 0x0010-0x1bff] [0.00] Initmem setup node 0 [mem 0x1000-0x1bff] [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] Intel MultiProcessor Specification v1.4 [0.00] MPTABLE: OEM ID: KVMCPU00 [0.00] MPTABLE: Product ID: 0.1 [0.00] MPTABLE: APIC at: 0xFEE0 [0.00] Processor #0 (Bootup-CPU) [0.00] Processor #1 [0.00] Processor #2 [0.00] Processor #3 [0.00] IOAPIC[0]: apic_id 5, version 17, address 0xfec0, GSI 0-23 [0.00] Unknown bustype - ignoring [0.00] Processors: 4 [0.00] smpboot: Allowing 5 CPUs, 1 hotplug CPUs [0.00] PM: Registered nosave memory: [mem 0x-0x0fff] [0.00] PM: Registered nosave memory: [mem 0x0009f000-0x0009] [0.0
Bug#872986: marked as done (kvmtool: lkvm setup fails with Fatal: Fail to setup ...)
Your message dated Tue, 20 Dec 2022 16:05:26 +
with message-id
and subject line Bug#1026459: Removed package(s) from unstable
has caused the Debian Bug report #872986,
regarding kvmtool: lkvm setup fails with Fatal: Fail to setup ...
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
872986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kvmtool
Version: 0.20161128-1
Severity: normal
Dear Maintainer,
I have near zero knowledge about lkvm, so I don't know if I do sth. wrong,
but this seems to be a bug in lkvm.
with a nonexistant .lkvm directory with linux 4.4.83 (from mainline-ppa),
on stretch amd64:
# lkvm setup test
Fatal: Fail to setup /root/.lkvm/test/virt/init
strace shows some weird write() calls:
open("/root/.lkvm/test/virt/pre_init", O_WRONLY|O_CREAT|O_EXCL, 0755) = 3
write(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\2\0>\0\1\0\0\0\f\1@\0\0\0\0\0"...,
4294968080) = 114688
close(3)= 0
open("/root/.lkvm/test/virt/init", O_WRONLY|O_CREAT|O_EXCL, 0755) = 3
write(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360\10\0\0\0\0\0\0"...,
4294980768) = -1 EFAULT (Bad address)
write(2, " Fatal: Fail to setup /root/.lk"..., 50 Fatal: Fail to setup
/root/.lkvm/test/virt/init) = 50
exit_group(128) = ?
+++ exited with 128 +++
Note the length arg to both writes - the first is 0x10310, the second
0x134a0, which looks like some 32/64 bit issue (as in, passing an int
for a size_t or so).
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.83-040483-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages kvmtool depends on:
ii libaio1 0.3.110-3
ii libc62.24-11+deb9u1
ii libsdl1.2debian 1.2.15+dfsg1-4
ii libvncserver10.9.11+dfsg-1
ii zlib1g 1:1.2.8.dfsg-5
kvmtool recommends no packages.
kvmtool suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.20170904-2+rm
Dear submitter,
as the package kvmtool has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1026459
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#817965: marked as done (kvmtool: dumps core when Linux reboots: in gdb: Program received signal SIG34, Real-time event 34.)
Your message dated Tue, 20 Dec 2022 16:05:26 + with message-id and subject line Bug#1026459: Removed package(s) from unstable has caused the Debian Bug report #817965, regarding kvmtool: dumps core when Linux reboots: in gdb: Program received signal SIG34, Real-time event 34. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 817965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kvmtool Version: 0.20160203-1 Severity: normal Due to #817962, Linux reboots after not finding the filesystem and then lkvm crashes due to not handling the reboot properly. gdb gives this: Program received signal SIG34, Real-time event 34. Full log and backtrace: pabs@chianamo ~ $ lkvm run ... [0.348574] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -19 [0.349459] Please append a correct "root=" boot option; here are the available partitions: [0.350443] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.351421] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.0-1-amd64 #1 Debian 4.4.4-2 [0.352476] 0086 cc1a1833 812ea6b5 817eea98 [0.352563] 88001a083ea0 8116619a 8810 88001a083eb0 [0.352563] 88001a083e48 cc1a1833 8808 88001a083eb8 [0.352563] Call Trace: [0.352563] [] ? dump_stack+0x5c/0x77 [0.352563] [] ? panic+0xd3/0x215 [0.352563] [] ? mount_block_root+0x202/0x296 [0.352563] [] ? prepare_namespace+0x131/0x167 [0.352563] [] ? kernel_init_freeable+0x1e2/0x205 [0.352563] [] ? rest_init+0x80/0x80 [0.352563] [] ? kernel_init+0xa/0xe0 [0.352563] [] ? ret_from_fork+0x3f/0x70 [0.352563] [] ? rest_init+0x80/0x80 [0.352563] Kernel Offset: disabled [0.352563] Rebooting in 1 seconds.. # KVM compatibility warning. virtio-9p device was not detected. While you have requested a virtio-9p device, the guest kernel did not initialize it. Please make sure that the guest kernel was compiled with CONFIG_NET_9P_VIRTIO=y enabled in .config. # KVM compatibility warning. virtio-net device was not detected. While you have requested a virtio-net device, the guest kernel did not initialize it. Please make sure that the guest kernel was compiled with CONFIG_VIRTIO_NET=y enabled in .config. Segmentation fault (core dumped) pabs@chianamo ~ $ gdb -batch -n -ex 'set height 0' -ex run -ex bt -ex 'thread apply all bt full' --args lkvm run ... [0.334751] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -19 [0.335359] Please append a correct "root=" boot option; here are the available partitions: [0.336047] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.336733] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.4.0-1-amd64 #1 Debian 4.4.4-2 [0.337344] 0086 cde01d0b 812ea6b5 817eea98 [0.337969] 88001a083ea0 8116619a 8810 88001a083eb0 [0.338592] 88001a083e48 cde01d0b 8808 88001a083eb8 [0.339214] Call Trace: [0.339422] [] ? dump_stack+0x5c/0x77 [0.339842] [] ? panic+0xd3/0x215 [0.340030] [] ? mount_block_root+0x202/0x296 [0.340030] [] ? prepare_namespace+0x131/0x167 [0.340030] [] ? kernel_init_freeable+0x1e2/0x205 [0.340030] [] ? rest_init+0x80/0x80 [0.340030] [] ? kernel_init+0xa/0xe0 [0.340030] [] ? ret_from_fork+0x3f/0x70 [0.340030] [] ? rest_init+0x80/0x80 [0.340030] Kernel Offset: disabled [0.340030] Rebooting in 1 seconds.. Program received signal SIG34, Real-time event 34. [Switching to Thread 0x7fffcfda9700 (LWP 13949)] 0x76bd32d7 in ioctl () at ../sysdeps/unix/syscall-template.S:81 81 ../sysdeps/unix/syscall-template.S: No such file or directory. #0 0x76bd32d7 in ioctl () at ../sysdeps/unix/syscall-template.S:81 #1 0x00409455 in kvm_cpu__run (vcpu=) at kvm-cpu.c:40 #2 0x0040950f in kvm_cpu__start (cpu=0x6555c0) at kvm-cpu.c:99 #3 0x004051a7 in kvm_cpu_thread (arg=) at builtin-run.c:174 #4 0x779bd284 in start_thread (arg=0x7fffcfda9700) at pthread_create.c:333 #5 0x76bdaa4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fffce5a6700 (LWP 13952)): #0 __pthread_kill (threadid=, signo=34) at ../sysdeps/unix/sysv/linux/pthread_kill.c:62 pd =
Bug#966893: marked as done (kvmtool: FTBFS: string_fortified.h:34:10: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=])
Your message dated Tue, 20 Dec 2022 16:05:26 + with message-id and subject line Bug#1026459: Removed package(s) from unstable has caused the Debian Bug report #966893, regarding kvmtool: FTBFS: string_fortified.h:34:10: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kvmtool Version: 0.20170904-1.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -c -Wp,-MD,./.kvm-cmd.o.d -DCONFIG_GUEST_INIT -DCONFIG_GUEST_PRE_INIT > -Wdate-time -D_FORTIFY_SOURCE=2 -DCONFIG_X86_64 -DCONFIG_X86 > -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DKVMTOOLS_VERSION='""' > -DBUILD_ARCH='"x86"' -Iinclude -Ix86/include -O2 -fno-strict-aliasing -g > -Wall -Wformat=2 -Winit-self -Wmissing-declarations -Wmissing-prototypes > -Wnested-externs -Wno-system-headers -Wold-style-definition -Wredundant-decls > -Wsign-compare -Wstrict-prototypes -Wundef -Wvolatile-register-var > -Wwrite-strings -Wno-format-nonliteral -Werror -DCONFIG_HAS_VNCSERVER > -DCONFIG_HAS_SDL -DCONFIG_HAS_ZLIB -DCONFIG_HAS_AIO kvm-cmd.c -o kvm-cmd.o > In file included from /usr/include/string.h:495, > from include/kvm/util.h:17, > from include/kvm/mutex.h:6, > from include/kvm/uip.h:5, > from net/uip/csum.c:1: > In function ‘memcpy’, > inlined from ‘uip_csum_udp’ at net/uip/csum.c:58:3: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34:10: error: writing 1 > byte into a region of size 0 [-Werror=stringop-overflow=] >34 | return __builtin___memcpy_chk (__dest, __src, __len, __bos0 > (__dest)); > | > ^~ > In file included from net/uip/csum.c:1: > net/uip/csum.c: In function ‘uip_csum_udp’: > include/kvm/uip.h:132:6: note: at offset 0 to object ‘sport’ with size 2 > declared here > 132 | u16 sport; > | ^ > In file included from /usr/include/string.h:495, > from include/kvm/util.h:17, > from include/kvm/mutex.h:6, > from include/kvm/uip.h:5, > from net/uip/csum.c:1: > In function ‘memcpy’, > inlined from ‘uip_csum_udp’ at net/uip/csum.c:55:3: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34:10: error: writing 1 > byte into a region of size 0 [-Werror=stringop-overflow=] >34 | return __builtin___memcpy_chk (__dest, __src, __len, __bos0 > (__dest)); > | > ^~ > In file included from net/uip/csum.c:1: > net/uip/csum.c: In function ‘uip_csum_udp’: > include/kvm/uip.h:132:6: note: at offset 0 to object ‘sport’ with size 2 > declared here > 132 | u16 sport; > | ^ > In file included from /usr/include/string.h:495, > from include/kvm/util.h:17, > from include/kvm/mutex.h:6, > from include/kvm/uip.h:5, > from net/uip/csum.c:1: > In function ‘memcpy’, > inlined from ‘uip_csum_tcp’ at net/uip/csum.c:89:3: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34:10: error: writing 1 > byte into a region of size 0 [-Werror=stringop-overflow=] >34 | return __builtin___memcpy_chk (__dest, __src, __len, __bos0 > (__dest)); > | > ^~ > In file included from net/uip/csum.c:1: > net/uip/csum.c: In function ‘uip_csum_tcp’: > include/kvm/uip.h:147:6: note: at offset 0 to object ‘sport’ with size 2 > declared here > 147 | u16 sport; > | ^ > In file included from /usr/include/string.h:495, > from include/kvm/util.h:17, > from include/kvm/mutex.h:6, > from include/kvm/uip.h:5, > from net/uip/csum.c:1: > In function ‘memcpy’, > inlined from ‘uip_csum_tcp’ at net/uip/csum.c:86:3: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34:10: error: writing 1 > byte into a region of size 0 [-Werror=stringop-overflow=] >34 | return __builtin___memcpy_chk (__dest, __src, __len, __bos0 > (__dest)); > | > ^~ > In file
Bug#982237: marked as done (kvmtool: please stop using cdrkit (genisoimage))
Your message dated Tue, 20 Dec 2022 16:05:26 + with message-id and subject line Bug#1026459: Removed package(s) from unstable has caused the Debian Bug report #982237, regarding kvmtool: please stop using cdrkit (genisoimage) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kvmtool Version: 0.20170904-1.1 Severity: important Dear kvmtool Maintainers, your package build-depends on genisoimage, built from cdrkit sources. cdrkit does not have a path forward, please switch away from it rather soon. I'm told xorriso and libburnia are alternatives and are alive and doing well. It's been suggested cdrkit should not be in bookworm. Chris --- End Message --- --- Begin Message --- Version: 0.20170904-2+rm Dear submitter, as the package kvmtool has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026459 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#999257: marked as done (debget: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Tue, 20 Dec 2022 16:04:26 + with message-id and subject line Bug#1026457: Removed package(s) from unstable has caused the Debian Bug report #999257, regarding debget: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debget Version: 1.6+nmu4 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 1.6+nmu6+rm Dear submitter, as the package debget has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026457 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1026428: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: mytop |1.9.1-5 | source, all --- Reason --- RoQA; unmaintained copy; included in mariadb -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1026428 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026428: Removed package(s) from unstable
Version: 1.9.1-5+rm Dear submitter, as the package mytop has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026428 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026457: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: debget | 1.6+nmu6 | source, all --- Reason --- RoQA; Orphaned, RC buggy, not in stable nor in testing -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1026457 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026457: Removed package(s) from unstable
Version: 1.6+nmu6+rm Dear submitter, as the package debget has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026457 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026458: Removed package(s) from unstable
Version: 0.4.6+dfsg-3+rm Dear submitter, as the package kytea has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026458 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026458: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: kytea | 0.4.6+dfsg-2 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x kytea | 0.4.6+dfsg-3 | source libkytea-dev | 0.4.6+dfsg-2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libkytea0 | 0.4.6+dfsg-2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; Orphaned, RC buggy, not in stable nor in testing -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1026458 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026459: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: kvmtool | 0.20170904-1.1 | source, amd64, arm64, armhf, i386, mips64el, mipsel, ppc64el kvmtool | 0.20170904-2 | source --- Reason --- RoQA; Orphaned, RC buggy, not in stable nor in testing -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1026459 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026459: Removed package(s) from unstable
Version: 0.20170904-2+rm Dear submitter, as the package kvmtool has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026459 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026536: nitpic: FTBFS: elf-sframe.c:526: undefined reference to `sframe_encoder_write'
Source: nitpic Version: 0.1-17 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libbfd.a(elf-sframe.o): > in function `_bfd_elf_write_section_sframe': > /build/binutils-IJ3Mfh/binutils-2.39.50.20221208/builddir-single/bfd/../../bfd/elf-sframe.c:526: > undefined reference to `sframe_encoder_write' > /usr/bin/ld: > /build/binutils-IJ3Mfh/binutils-2.39.50.20221208/builddir-single/bfd/../../bfd/elf-sframe.c:541: > undefined reference to `sframe_encoder_free' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/12/20/nitpic_0.1-17_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1026546: zope.testing: FTBFS: AssertionError: Failed doctest test for doctestcase.txt
Source: zope.testing Version: 4.10-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py config > /usr/lib/python3/dist-packages/setuptools/dist.py:286: > SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, > consider using implicit namespaces instead (PEP 420). > warnings.warn(msg, SetuptoolsDeprecationWarning) > running config > I: pybuild base:240: python3.10 setup.py config > /usr/lib/python3/dist-packages/setuptools/dist.py:286: > SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, > consider using implicit namespaces instead (PEP 420). > warnings.warn(msg, SetuptoolsDeprecationWarning) > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3.11 setup.py build > /usr/lib/python3/dist-packages/setuptools/dist.py:286: > SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated, > consider using implicit namespaces instead (PEP 420). > warnings.warn(msg, SetuptoolsDeprecationWarning) > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_zope.testing/build/zope > copying src/zope/__init__.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope > creating > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/__init__.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/doctestcase.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/tests.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/renormalizing.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/exceptions.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/loghandler.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/test_renormalizing.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/setupstack.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/module.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/server.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/wait.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/loggingsupport.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/formparser.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/testrunner.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/cleanup.py -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > running egg_info > writing src/zope.testing.egg-info/PKG-INFO > writing dependency_links to src/zope.testing.egg-info/dependency_links.txt > writing namespace_packages to src/zope.testing.egg-info/namespace_packages.txt > writing requirements to src/zope.testing.egg-info/requires.txt > writing top-level names to src/zope.testing.egg-info/top_level.txt > reading manifest file 'src/zope.testing.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching '*.txt' under directory 'docs' > warning: no files found matching 'Makefile' under directory 'docs' > adding license file 'LICENSE.txt' > writing manifest file 'src/zope.testing.egg-info/SOURCES.txt' > copying src/zope/testing/cleanup.txt -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/doctestcase.txt -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/formparser.txt -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/loggingsupport.txt -> > /<>/.pybuild/cpython3_3.11_zope.testing/build/zope/testing > copying src/zope/testing/module.tx
Bug#949319: marked as done (ITS: tolua++)
Your message dated Tue, 20 Dec 2022 18:22:42 +0100 with message-id <784a3159-b8ab-b534-bdb4-7aa26ee5b...@debian.org> and subject line Re: Bug#949319: ITS: tolua++ has caused the Debian Bug report #949319, regarding ITS: tolua++ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 949319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tolua++ Severity: important Version: 1.0.93-3 X-Debbugs-CC: vch...@debian.org Hi Vincent, After looking into a package you maintain in Debian (tolua++, https://tracker.debian.org/pkg/tolua++), I found that this package received no update since 2012 and is not in good shape. As a result, I am filing an ITS (Intent to Salvage) request against your package according to section 5.12 in Debian Developers' Reference. [1] Please let me know if you are still willing to maintain this package. According to the criteria listed at [2], I will upload a Non-maintainer Upload (NMU) of tolua++ onto DELAYED/7 after 21 days (Feb. 09, 2020) to continue with the package salvaging. If it's necessary to pause the ITS process, please let me know immediately by replying this bug report. Thank you for your previous work on tolua++ and looking forward to your reply. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- The package was orphaned, so anyone can easily adopt it.--- End Message ---
Bug#1026619: python-fire: FTBFS: AttributeError: module 'asyncio' has no attribute 'coroutine'
Source: python-fire Version: 0.4.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build -Spybuild --with python3 >dh_update_autotools_config -O-Spybuild >dh_autoreconf -O-Spybuild >dh_auto_configure -O-Spybuild > I: pybuild base:240: python3.11 setup.py config > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'license-file' will not be supported in future versions. > Please use the underscore name 'license_file' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: > SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use > license_files instead. > warnings.warn(msg, warning_class) > running config > I: pybuild base:240: python3.10 setup.py config > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'license-file' will not be supported in future versions. > Please use the underscore name 'license_file' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: > SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use > license_files instead. > warnings.warn(msg, warning_class) > running config >dh_auto_build -O-Spybuild > I: pybuild base:240: /usr/bin/python3.11 setup.py build > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'license-file' will not be supported in future versions. > Please use the underscore name 'license_file' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: > SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use > license_files instead. > warnings.warn(msg, warning_class) > running build > running build_py > creating /<>/.pybuild/cpython3_3.11/build/fire > copying fire/__init__.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/formatting.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/parser.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/docstrings_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/core.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/value_types.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/inspectutils.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/__main__.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/parser_fuzz_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/main_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/formatting_windows.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/test_components_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/trace.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/parser_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/formatting_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/decorators.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/helptext.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/decorators_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/test_components_bin.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/test_components.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/fire_import_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/completion_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/core_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/inspectutils_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/interact.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/test_components_py3.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/fire_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/custom_descriptions_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/docstrings_fuzz_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/docstrings.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/custom_descriptions.py -> > /&
Bug#1026763: tuxcmd: FTBFS: /usr/bin/ld.bfd: cannot find -lgthread-2.0: No such file or directory
Source: tuxcmd Version: 0.6.70+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > echo "const" > fpcver.inc > echo " ConstFPCVersionString = '`fpc -iW`';" >> fpcver.inc > echo " ConstFPCDateString = '`fpc -iD`';" >> fpcver.inc > echo " ConstFPCCompilerOSString = '`fpc -iSO`';" >> fpcver.inc > echo " ConstFPCCompilerHostProcessorString = '`fpc -iSP`';" >> fpcver.inc > echo " ConstFPCTargetOSString = '`fpc -iTO`';" >> fpcver.inc > echo " ConstFPCTargetProcessorString = '`fpc -iTP`';" >> fpcver.inc > fpc -Mdelphi -vweh -Un -Ci -Co -XX "-k-z noexecstack" -O3 \ > -Fu./libgtk_kylix -Fu./translations -Fu./vfs \ > tuxcmd.dpr > Hint: Start of reading config file /etc/fpc.cfg > Hint: End of reading config file /etc/fpc.cfg > Free Pascal Compiler version 3.2.2+dfsg-17 [2022/11/27] for x86_64 > Copyright (c) 1993-2021 by Florian Klaempfl and others > Target OS: Linux for x86-64 > Compiling tuxcmd.dpr > Compiling ./libgtk_kylix/GTKForms.pas > Compiling ./libgtk_kylix/GTKControls.pas > Compiling ./libgtk_kylix/GTKMenus.pas > Compiling ./libgtk_kylix/GTKConsts.pas > GTKConsts.pas(27,13) Hint: Unit "gdk2" not used in GTKConsts > Writing Resource String Table file: GTKConsts.rsj > Compiling ./libgtk_kylix/GTKUtils.pas > Compiling ./libgtk_kylix/GTKClasses.pas > Compiling ./libgtk_kylix/GTKUtils.pas > GTKClasses.pas(27,12) Hint: Unit "gdk2" not used in GTKClasses > Compiling ./libgtk_kylix/GTKPixbuf.pas > Compiling ./libgtk_kylix/GTKStdCtrls.pas > GTKStdCtrls.pas(284,30) Hint: Parameter "button" not used > GTKStdCtrls.pas(543,38) Hint: Parameter "ToggleButton" not used > GTKStdCtrls.pas(707,32) Hint: Parameter "editable" not used > GTKStdCtrls.pas(231,28) Hint: Parameter "Sender" not used > GTKStdCtrls.pas(27,12) Hint: Unit "gdk2" not used in GTKStdCtrls > GTKPixbuf.pas(27,13) Hint: Unit "gdk2" not used in GTKPixbuf > Compiling ./libgtk_kylix/GTKForms.pas > GTKForms.pas(283,38) Hint: Parameter "widget" not used > GTKForms.pas(283,58) Hint: Parameter "event" not used > GTKForms.pas(288,31) Hint: Parameter "anobject" not used > GTKForms.pas(293,40) Hint: Parameter "widget" not used > GTKForms.pas(293,61) Hint: Parameter "allocation" not used > GTKForms.pas(67,26) Hint: Parameter "Sender" not used > GTKForms.pas(712,45) Warning: Conversion between ordinals and pointers is not > portable > GTKForms.pas(745,45) Hint: Conversion between ordinals and pointers is not > portable > GTKForms.pas(802,37) Hint: Parameter "dialog" not used > Compiling ./libgtk_kylix/GTKExtCtrls.pas > GTKExtCtrls.pas(381,28) Hint: Parameter "widget" not used > GTKExtCtrls.pas(381,49) Hint: Parameter "allocation" not used > GTKExtCtrls.pas(440,36) Hint: Parameter "notebook" not used > GTKExtCtrls.pas(440,60) Hint: Parameter "page" not used > GTKExtCtrls.pas(440,84) Hint: Parameter "page_num" not used > GTKExtCtrls.pas(544,127) Warning: Local variable "expand" does not seem to be > initialized > GTKExtCtrls.pas(544,143) Warning: Local variable "packtype" does not seem to > be initialized > GTKExtCtrls.pas(544,133) Warning: Local variable "fill" does not seem to be > initialized > GTKExtCtrls.pas(557,133) Warning: Local variable "fill" does not seem to be > initialized > GTKExtCtrls.pas(557,143) Warning: Local variable "packtype" does not seem to > be initialized > GTKExtCtrls.pas(557,127) Warning: Local variable "expand" does not seem to be > initialized > GTKExtCtrls.pas(573,34) Hint: Parameter "optionmenu" not used > GTKExtCtrls.pas(171,28) Hint: Parameter "Sender" not used > GTKExtCtrls.pas(27,12) Hint: Unit "gdk2" not used in GTKExtCtrls > GTKExtCtrls.pas(27,47) Hint: Unit "GTKConsts" not used in GTKExtCtrls > GTKMenus.pas(166,33) Hint: Parameter "menuitem" not used > GTKMenus.pas(145,16) Hint: Unit "GTKExtCtrls" not used in GTKMenus > GTKControls.pas(427,41) Hint: Parameter "widget" not used > GTKControls.pas(102,26) Hint: Parameter "Value" not used > GTKControls.pas(531,38) Hint: Parameter "widget" not used > GTKControls.pas(5
Bug#1006765: marked as done (ITS: sispmctl)
Your message dated Tue, 20 Dec 2022 23:21:16 +0100 with message-id and subject line Re: ITS: sispmctl has caused the Debian Bug report #1006765, regarding ITS: sispmctl to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1006765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sispmctl Version: 3.1-1 Severity: important X-Debbugs-CC: m...@qa.debian.org X-Debbugs-CC: Uwe Hermann The current Debian package has major deficiencies: The most important one being that current hardware is not supported (#929612) New upstream releases resolving the issues have not been packaged for years by Debian. Responses by the package maintainer are missing. As I am the maintainer of the upstream package in https://sourceforge.net/projects/sispmctl/ I would like to take over the maintainership for the package. Best regards Heinrich Schuchardt --- End Message --- --- Begin Message --- The package is orphaned. Please just adopt it if you are still interested in maintaining it.--- End Message ---
Processed (with 1 error): Re: Bug#981637: ifscheme: ifup no longer recognises interface names with ifscheme suffixes
Processing control commands: > tags -1 = confirmed Bug #981637 [ifscheme] ifscheme: ifup no longer recognises interface names with ifscheme suffixes Added tag(s) confirmed. > severity serious Unknown command or malformed arguments to command. -- 981637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981637: ifscheme: ifup no longer recognises interface names with ifscheme suffixes
Control: tags -1 = confirmed Control: severity serious * Richard Lewis : [..] > Just recently I installed "unstable" from scratch on a Dell > XPS 13 9343. And now ifscheme doesn't work anymore. [..] > But when I try to select a network and bring up the interface, I get > the error "unknown interface": > > $ sudo ifscheme home > Scheme changed to home. > $ sudo ifup -v wlp2s0 > ifup: running mapping script ifscheme-mapping on wlp2s0 > ifup: ignoring unknown interface wlp2s0=wlp2s0 Can confirm in unstable with ifscheme 1.7-6 and ifupdown 0.8.36 and a "quote normal" enp0s1 ethernet interface. Raising to serious as it would appear ifscheme is just broken. Chris
Processed: severity of 981637 is serious
Processing commands for cont...@bugs.debian.org: > severity 981637 serious Bug #981637 [ifscheme] ifscheme: ifup no longer recognises interface names with ifscheme suffixes Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 981637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of sysv-rc-conf_0.99-10_source.changes
sysv-rc-conf_0.99-10_source.changes uploaded successfully to localhost along with the files: sysv-rc-conf_0.99-10.dsc sysv-rc-conf_0.99-10.debian.tar.xz sysv-rc-conf_0.99-10_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
sysv-rc-conf_0.99-10_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Dec 2022 00:29:13 + Source: sysv-rc-conf Architecture: source Version: 0.99-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Chris Hofstaedtler Closes: 791689 859693 Changes: sysv-rc-conf (0.99-10) unstable; urgency=medium . * QA upload. * Depend on sysvinit-core, as this tool is at best useless or worse, wrong on non-sysvinit systems. (Closes: #859693, #791689) Checksums-Sha1: e5f06c7657ad076451395730cc245ab0f0045a68 1879 sysv-rc-conf_0.99-10.dsc c6e8a4948657b1d0bf62ef88c72ffce427387e23 9036 sysv-rc-conf_0.99-10.debian.tar.xz 3a48f26dc4e85f55be1378cf62bbad51071e5e8d 5865 sysv-rc-conf_0.99-10_source.buildinfo Checksums-Sha256: c1bbf07034edf9dce75352819cb24d3d39bfda6378c9bb53fe4cb0eabfbf3edb 1879 sysv-rc-conf_0.99-10.dsc 214033300a090a475cef6078da57adbc6b83e75f6ea4ba13959ad23b5cbcabcd 9036 sysv-rc-conf_0.99-10.debian.tar.xz 18522044dee00013dea8e3f9a8365d40fd82890189cdaf9c8b7877cf4d4b1d62 5865 sysv-rc-conf_0.99-10_source.buildinfo Files: 5bb51ea8d18be4df02ae90f847d5cda4 1879 admin optional sysv-rc-conf_0.99-10.dsc e0437436ff192c965399bd3b3535ccc1 9036 admin optional sysv-rc-conf_0.99-10.debian.tar.xz d007847e3af91b8ccdaf921177160931 5865 admin optional sysv-rc-conf_0.99-10_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmOiVDwACgkQXBPW25MF LgOcog/9F4O0q0CXbwAvK3BxZW1opMorkTqyqLuU5gtMohYuF51cjouUIqEso7sH MjSCdzS0zwAHQJon8kj3PkrA4q6yT7UsSg0d4z8zc3upaORtpQAQ0KA6UT3rvJKO ZXGyuq9l5vSCpE7D6jA74sIrpoYNEZUjtS66kgWbOVOUbtj+XuOVy3Ld8aUTXEkG RqxJSv9olvntp5aMYj4T3r/njY65bbKc9FHj4DeUrC4jzY9PN7Q1hMdBN+i3aSAB ZeCPZvUwtjyY9wWzL676xtu2oEaShCOrFF3A+NalRkwX1Sm8LOL8RzEEkFPeRX9q oVjj9WvYGoF/I3yJpJgPPXOn8qaK9xkoLV9Bmagz8SwlJSZ96CjDFdE5Du4TtR9L SqPy/3ZO7o8jz9BK9PVAzfCGvpNJgbN8Udb//Fnb7ixIFm9hivmVLBve7c9R29Xo MYa+LIJArlStqRpwS0dr4epEMuUbGyEUWcQQQKnl4N/X6xDUnAeF8KruCoQvjOkL eId9XecGoM6nT+/TiFAZ26dtcse1gYTLLbiTonPyg2p+7S7zLw5o7t+GhZNRYCt5 F12dCulfFJeKdcO4DTpg3+O7Qu5T9sa7VUDWVM50IOvfaeTvYrOHm2ZlzEoA3XPE wTk7L8DUTwrkHwzZDEQWoZenJg2lhUGOXUrzE7TqKnUT+wvzFug= =7DUe -END PGP SIGNATURE-
Bug#791689: marked as done (make Conflict with systemd?)
Your message dated Wed, 21 Dec 2022 01:01:22 + with message-id and subject line Bug#791689: fixed in sysv-rc-conf 0.99-10 has caused the Debian Bug report #791689, regarding make Conflict with systemd? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 791689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- X-Debbugs-cc: rcc...@packages.debian.org, syst...@packages.debian.org Package: sysv-rc-conf Version: 0.99-7 Severity: wishlist Shouldn't some kind of Conflict or Breaks or warning be made for packages such as sysv-rc-conf and rcconf, which might no longer work 100% as intended, after systemd is installed? --- End Message --- --- Begin Message --- Source: sysv-rc-conf Source-Version: 0.99-10 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of sysv-rc-conf, 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 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated sysv-rc-conf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Dec 2022 00:29:13 + Source: sysv-rc-conf Architecture: source Version: 0.99-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Chris Hofstaedtler Closes: 791689 859693 Changes: sysv-rc-conf (0.99-10) unstable; urgency=medium . * QA upload. * Depend on sysvinit-core, as this tool is at best useless or worse, wrong on non-sysvinit systems. (Closes: #859693, #791689) Checksums-Sha1: e5f06c7657ad076451395730cc245ab0f0045a68 1879 sysv-rc-conf_0.99-10.dsc c6e8a4948657b1d0bf62ef88c72ffce427387e23 9036 sysv-rc-conf_0.99-10.debian.tar.xz 3a48f26dc4e85f55be1378cf62bbad51071e5e8d 5865 sysv-rc-conf_0.99-10_source.buildinfo Checksums-Sha256: c1bbf07034edf9dce75352819cb24d3d39bfda6378c9bb53fe4cb0eabfbf3edb 1879 sysv-rc-conf_0.99-10.dsc 214033300a090a475cef6078da57adbc6b83e75f6ea4ba13959ad23b5cbcabcd 9036 sysv-rc-conf_0.99-10.debian.tar.xz 18522044dee00013dea8e3f9a8365d40fd82890189cdaf9c8b7877cf4d4b1d62 5865 sysv-rc-conf_0.99-10_source.buildinfo Files: 5bb51ea8d18be4df02ae90f847d5cda4 1879 admin optional sysv-rc-conf_0.99-10.dsc e0437436ff192c965399bd3b3535ccc1 9036 admin optional sysv-rc-conf_0.99-10.debian.tar.xz d007847e3af91b8ccdaf921177160931 5865 admin optional sysv-rc-conf_0.99-10_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmOiVDwACgkQXBPW25MF LgOcog/9F4O0q0CXbwAvK3BxZW1opMorkTqyqLuU5gtMohYuF51cjouUIqEso7sH MjSCdzS0zwAHQJon8kj3PkrA4q6yT7UsSg0d4z8zc3upaORtpQAQ0KA6UT3rvJKO ZXGyuq9l5vSCpE7D6jA74sIrpoYNEZUjtS66kgWbOVOUbtj+XuOVy3Ld8aUTXEkG RqxJSv9olvntp5aMYj4T3r/njY65bbKc9FHj4DeUrC4jzY9PN7Q1hMdBN+i3aSAB ZeCPZvUwtjyY9wWzL676xtu2oEaShCOrFF3A+NalRkwX1Sm8LOL8RzEEkFPeRX9q oVjj9WvYGoF/I3yJpJgPPXOn8qaK9xkoLV9Bmagz8SwlJSZ96CjDFdE5Du4TtR9L SqPy/3ZO7o8jz9BK9PVAzfCGvpNJgbN8Udb//Fnb7ixIFm9hivmVLBve7c9R29Xo MYa+LIJArlStqRpwS0dr4epEMuUbGyEUWcQQQKnl4N/X6xDUnAeF8KruCoQvjOkL eId9XecGoM6nT+/TiFAZ26dtcse1gYTLLbiTonPyg2p+7S7zLw5o7t+GhZNRYCt5 F12dCulfFJeKdcO4DTpg3+O7Qu5T9sa7VUDWVM50IOvfaeTvYrOHm2ZlzEoA3XPE wTk7L8DUTwrkHwzZDEQWoZenJg2lhUGOXUrzE7TqKnUT+wvzFug= =7DUe -END PGP SIGNATURE End Message ---
Bug#859693: marked as done (sysv-rc-conf: disabling auto-start of a systemd service appears successful but is not)
Your message dated Wed, 21 Dec 2022 01:01:22 + with message-id and subject line Bug#859693: fixed in sysv-rc-conf 0.99-10 has caused the Debian Bug report #859693, regarding sysv-rc-conf: disabling auto-start of a systemd service appears successful but is not to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 859693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sysv-rc-conf Version: 0.99-7 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: user To: Debian Bug Tracking System Subject: sysv-rc-conf: disabling a systemd service appears to work but the service still runs Message-ID: <20170406034251.3634.68427.reportbug@computer> X-Mailer: reportbug 6.6.3 Date: Wed, 05 Apr 2017 20:42:51 -0700 X-Debbugs-Cc: user@localhost.localdomain Package: sysv-rc-conf Version: 0.99-7 Severity: important Dear Maintainer, I have lighttpd and sysv-rc-conf installed from the standard Jessie (currently Stable) repos. For security and other reasons, I used sysv-rc-conf to disable auto-starting of lighttpd and some other services. The program's console UI "properly" cleared the auto-start boxes for lighttpd (and other services) in all runlevels and exited normally. Upon rebooting, I was very upset to learn that lighttpd had auto-started anyway (seen with "service lighttpd status" which shows it as executing with /lib/systemd/system/lighttpd.service ). Other services, those which start from /etc/init.d/* seem to respond correctly, though. Note that this is a real-world impact of related bug #791689 If users are led to believe that a service has been disabled when it is in fact still running, the consequences could be serious from a security perspective, not to mention that if updates are made to the unit files themselves, major conflicts could emerge from duplicate services and so on. Thank you very much. -- System Information: Debian Release: 8.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sysv-rc-conf depends on: ii libcurses-ui-perl 0.9609-1 ii sysv-rc2.88dsf-59 sysv-rc-conf recommends no packages. sysv-rc-conf suggests no packages. -- no debconf information -- System Information: Debian Release: 8.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sysv-rc-conf depends on: ii libcurses-ui-perl 0.9609-1 ii sysv-rc2.88dsf-59 sysv-rc-conf recommends no packages. sysv-rc-conf suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: sysv-rc-conf Source-Version: 0.99-10 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of sysv-rc-conf, 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. Chris Hofstaedtler (supplier of updated sysv-rc-conf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Dec 2022 00:29:13 + Source: sysv-rc-conf Architecture: source Version: 0.99-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Chris Hofstaedtler Closes: 791689 859693 Changes: sysv-rc-conf (0.99-10) unstable; urgency=medium . * QA upload.
Bug#1026788: [INTL:es] Spanish translation of the debconf template
Package: spamprobe Severity: wishlist Tags: patch l10n Hello, You can find enclosed the Spanish translation template to be uploaded with the latest package build. Cheers, -- Camaleón# spamprobe po-debconf translation to Spanish # Copyright (C) 2010 Software in the Public Interest # This file is distributed under the same license as the spamprobe package. # # Changes: # - Initial translation # Omar Campagne , 2010 # # - Updates # TRANSLATOR # # Traductores, si no conocen el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español # http://www.debian.org/intl/spanish/ # especialmente las notas y normas de traducción en # http://www.debian.org/intl/spanish/notas # # - La guía de traducción de po's de debconf: # /usr/share/doc/po-debconf/README-trans # o http://www.debian.org/intl/l10n/po-debconf/README-trans # msgid "" msgstr "" "Project-Id-Version: spamprobe 1.4d-12.1\n" "Report-Msgid-Bugs-To: spampr...@packages.debian.org\n" "POT-Creation-Date: 2014-02-11 15:44+0100\n" "PO-Revision-Date: 2022-12-09 17:24+0100\n" "Last-Translator: Camaleón \n" "Language-Team: Debian l10n Spanish \n" "Language: es\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Poedit 2.4.2\n" #. Type: note #. Description #: ../templates:2001 msgid "Upgrading to Berkeley DB 5.3" msgstr "Actualizando a la versión 5.3 de la base de datos de Berkeley" #. Type: note #. Description #: ../templates:2001 msgid "" "As of spamprobe 1.4d-12.1, the database format changed to Berkeley DB 5.3 " "and spamprobe is no longer able to modify databases using an older format." msgstr "" "A partir de la versión 1.4d-12.1 de spamprobe, el formato de la base de " "datos cambió al formato de la versión 5.3 de la base de datos de Berkeley, y " "spamprobe ya no es capaz de modificar bases de datos con un formato anterior " "a éste." #. Type: note #. Description #: ../templates:2001 msgid "" "Since there is no general way to locate all existing databases, no automatic " "upgrade is attempted. A manual upgrade path using spamprobe export/import is " "outlined in the 'DATABASE MAINTENANCE' section of the spamprobe(1) manual " "page." msgstr "" "Debido a que no existe una manera general de ubicar todas las bases de datos " "existentes, no se intenta ninguna actualización automática. Se describe una " "vía para actualizar, usando las funciones de exportar e importar de " "spamprobe, en la sección «DATABASE MAINTENANCE» de la página de manual de " "spamprobe(1)." #. Type: note #. Description #: ../templates:2001 msgid "" "All spamprobe users on this system should be informed of this change and " "advised to read the README.Debian file." msgstr "" "Se debería informar de este cambio a todos los usuarios de spamprobe en el " "sistema, así como recomendar la lectura del fichero «README.Debian»." #. Type: note #. Description #: ../templates:2001 msgid "" "To avoid this issue at next Berkeley DB migration, converting to another " "data file format, like 'hash', is recommended. See documentation of the -d " "option in spamprobe(1) man page." msgstr "" "Para evitar este problema durante la siguiente actualización de la base de " "datos de Berkeley, se recomienda la conversión a otro formato de fichero de " "datos, como «hash». Consulte la documentación de la opción «-d» en la página " "de manual de spamprobe."
