Processed: bug 980007 is forwarded to https://github.com/open-iscsi/tcmu-runner/issues/645
Processing commands for cont...@bugs.debian.org: > forwarded 980007 https://github.com/open-iscsi/tcmu-runner/issues/645 Bug #980007 [src:tcmu] tcmu: CVE-2020-28374 Set Bug forwarded-to-address to 'https://github.com/open-iscsi/tcmu-runner/issues/645'. > thanks Stopping processing here. Please contact me if you need assistance. -- 980007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980030: vim-gtk3: gvim Could not load pixbuf defaults to vim with no gui
Package: vim-gtk3 Version: 2:8.2.1913-1+b2 Severity: grave Justification: renders package unusable Dear Maintainer, After latest system update gvim does not load gui.It shows following error messages. * (gvim:1792): Gtk-WARNING **: 12:28:53.889: Could not load a pixbuf from /org/gtk/libgtk/icons/16x16/status/image-missing.png. This may indicate that pixbuf loaders or the mime database could not be found. ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3) Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3) Vim: Caught deadly signal ABRT Vim: Finished. E852: The child process failed to start the GUI Press ENTER or type command to continue * Tried update-mime-database /usr/share/mime and also /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders --update-cache Also tried after removing .vimrc. -- Package-specific info: --- real paths of main Vim binaries --- /usr/bin/vi is /usr/bin/vim.gtk3 /usr/bin/vim is /usr/bin/vim.gtk3 /usr/bin/gvim is /usr/bin/vim.gtk3 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=ml_IN.UTF-8@pvm, LC_CTYPE=ml_IN.UTF-8@pvm (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vim-gtk3 depends on: ii libacl1 2.2.53-9 ii libc62.31-9 ii libcairo21.16.0-5 ii libcanberra0 0.30-7 ii libgdk-pixbuf2.0-0 2.40.2-2 ii libglib2.0-0 2.66.4-1 ii libgpm2 1.20.7-6 ii libgtk-3-0 3.24.24-1 ii libice6 2:1.0.10-1 ii liblua5.2-0 5.2.4-1.1+b3 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libperl5.32 5.32.0-6 ii libpython3.9 3.9.1-1 ii libruby2.7 2.7.2-3 ii libselinux1 3.1-2+b2 ii libsm6 2:1.2.3-1 ii libtcl8.68.6.11+dfsg-1 ii libtinfo66.2+20201114-2 ii libx11-6 2:1.6.12-1 ii libxt6 1:1.2.0-1 ii vim-common 2:8.2.1913-1 ii vim-gui-common 2:8.2.1913-1 ii vim-runtime 2:8.2.1913-1 vim-gtk3 recommends no packages. Versions of packages vim-gtk3 suggests: pn cscope ii fonts-dejavu 2.37-2 ii gnome-icon-theme 3.12.0-3 pn vim-doc -- no debconf information
Bug#954352: marked as done (pymca: Missing dependency "python3-scipy", probably in "python3-silx")
Your message dated Wed, 13 Jan 2021 07:40:34 +0100 with message-id <874kjltk4d@synchrotron-soleil.fr> and subject line forgot to closed has caused the Debian Bug report #954352, regarding pymca: Missing dependency "python3-scipy", probably in "python3-silx" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 954352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pymca Version: 5.4.3+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, I installed "pymca" on a debian 10 system, this draggs the dependencies: * python3-pymca5 * python3-silx The package python3-silx apparently requires python3-scipy, the graphical user interface does not load and crashed at start up. Cheers, Jerpme -- System Information: Debian Release: 10.3 APT prefers stable APT policy: (800, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF8:fr:en_GB.UTF8:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pymca depends on: ii python3 3.7.3-1 ii python3-numpy 1:1.16.2-1 ii python3-pymca5 5.4.3+dfsg-1 pymca recommends no packages. pymca suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 22264--- End Message ---
Bug#979173: marked as done (libtool ftbfs with new gnulib)
Your message dated Wed, 13 Jan 2021 00:24:41 -0500 with message-id and subject line Re: libtool ftbfs with new gnulib has caused the Debian Bug report #979173, regarding libtool ftbfs with new gnulib to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtool Version: 2.4.6-14 Severity: serious Tags: ftbfs patch User: helm...@debian.org Usertags: rebootstrap libtool started to ftbfs with the recent gnulib upload. It needs to bump the autoconf version to build again. The attached patch makes it work again. Helmut --- libtool-2.4.6.orig/configure.ac +++ libtool-2.4.6/configure.ac @@ -24,7 +24,7 @@ -AC_PREREQ(2.63) +AC_PREREQ(2.64) dnl Oldest automake required for bootstrap is below in AM_INIT_AUTOMAKE. --- End Message --- --- Begin Message --- Version: 2.4.6-15 On Sun, 3 Jan 2021 20:17:17 +0100 Helmut Grohne wrote: > Source: libtool > Version: 2.4.6-14 > Severity: serious > Tags: ftbfs patch > User: helm...@debian.org > Usertags: rebootstrap > > libtool started to ftbfs with the recent gnulib upload. It needs to bump > the autoconf version to build again. The attached patch makes it work > again. I believe this patch is reflected in the latest upload. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: unmerge #948781 debmake-doc: FTBFS: Segmentation fault
Processing commands for cont...@bugs.debian.org: > unmerge 948781 Bug #948781 [itstool] debmake-doc: FTBFS: Segmentation fault Bug #919058 [itstool] its-tools: crashes when freeing xmlDocs Disconnected #948781 from all other report(s). > thanks Stopping processing here. Please contact me if you need assistance. -- 919058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919058 948781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979978: marked as done (lime-forensics-dkms: unable to make or make install due to error set_fs)
Your message dated Wed, 13 Jan 2021 05:05:39 + with message-id and subject line Bug#979978: fixed in lime-forensics 1.9.1-2 has caused the Debian Bug report #979978, regarding lime-forensics-dkms: unable to make or make install due to error set_fs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lime-forensics-dkms Version: 1.9.1-1 Severity: normal Tags: ftbfs Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Trying to install lime-forensics-dkms * What exactly did you do (or not do) that was effective (or ineffective)? tried to install via apt * What was the outcome of this action? instead of building the modules it just errors out and gives error ‘setup_tcp’: /usr/src/lime-forensics-1.9.1-1/tcp.c:77:10: error: implicit declaration of function ‘get_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] /usr/src/lime-forensics-1.9.1-1/tcp.c:77:10: error: incompatible types when assigning to type ‘mm_segment_t’ from type ‘int’ /usr/src/lime-forensics-1.9.1-1/tcp.c:78:5: error: implicit declaration of function ‘set_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] 78 | set_fs(KERNEL_DS); | ^~ /usr/src/lime-forensics-1.9.1-1/tcp.c:78:12: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 78 | set_fs(KERNEL_DS); /usr/src/lime-forensics-1.9.1-1/tcp.c:78:12: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 78 | set_fs(KERNEL_DS); /usr/src/lime-forensics-1.9.1-1/tcp.c:78:12: note: each undeclared identifier is reported only once for each function it appears in /usr/src/lime-forensics-1.9.1-1/tcp.c:49:12: warning: unused variable ‘opt’ [-Wunused-variable] * What outcome did you expect instead? for the application to compile and build the modules *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lime-forensics-dkms depends on: ii dkms 2.8.4-1 Versions of packages lime-forensics-dkms recommends: ii linux-headers-amd64 5.10.5-1 lime-forensics-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: lime-forensics Source-Version: 1.9.1-2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of lime-forensics, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated lime-forensics package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Jan 2021 01:10:57 -0300 Source: lime-forensics Architecture: source Version: 1.9.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Joao Eriberto Mota Filho Closes: 979978 Changes: lime-forensics (1.9.1-2) unstable; urgency=medium . * debian/control: bumped Standards-Version to 4.5.1. * debian/copyright: updated packaging copyright years. * debian/patches/10_fix_5.10.patch: created to fix build and install for kernel 5.10. Thanks to Hans-Peter Jansen . (Closes: #979978). Checksums-Sha1: ccf89dbb3ec04c7a82e6b32d94eff459b7fb8aa7 2060 lime-forensics_1.9.1-2.dsc d0ead5261089a68051c05905b08ca928cc7621da 6080 lime-forensics_1.9.1-2.debian.tar.xz 4a2720cf77bca1c9de47521f98064a280893b178 6150 lime-forensics_1.9.1-2_source.buildinfo
Bug#957610: nn: ftbfs with GCC-10
Source: nn
Version: 6.7.3-12
Followup-For: Bug #957610
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/07-gcc-10.diff: Fix FTBFS with GCC 10.
Thanks for considering the patch.
Logan
diff -Nru nn-6.7.3/debian/patches/07-gcc-10.diff
nn-6.7.3/debian/patches/07-gcc-10.diff
--- nn-6.7.3/debian/patches/07-gcc-10.diff 1969-12-31 19:00:00.0
-0500
+++ nn-6.7.3/debian/patches/07-gcc-10.diff 2021-01-12 23:33:20.0
-0500
@@ -0,0 +1,114 @@
+--- a/global.h
b/global.h
+@@ -172,7 +172,7 @@
+ extern group_header *current_group, *group_sequence, *rc_sequence;
+
+
+-int l_g_index, s_g_first;
++extern int l_g_index, s_g_first;
+
+ #define Loop_Groups_Number(num) \
+ for (num = 0; num < master.number_of_groups; num++)
+--- a/db.c
b/db.c
+@@ -130,6 +130,8 @@
+ static char*group_position = NULL;
+ static article_number current_digest_article = 0;
+
++int l_g_index, s_g_first;
++
+ int
+ init_group(register group_header * gh)
+ {
+--- a/nn_term.h
b/nn_term.h
+@@ -48,7 +48,7 @@
+ */
+
+
+-int prompt_line; /* prompt line */
++extern int prompt_line; /* prompt line */
+
+ #define P_MOVE (char *)1
+ #define P_REDRAW (char *)5
+--- a/term.c
b/term.c
+@@ -140,6 +140,7 @@
+ int show_current_time = 1;
+ int conf_dont_sleep = 0;
+ int prompt_length;
++int prompt_line;
+ int terminal_speed = 0;
+ int slow_speed = 1200;
+ int any_message = 0;
+--- a/articles.c
b/articles.c
+@@ -33,6 +33,9 @@
+ int body_search_header = 0;
+ int cross_post_limit = 0;
+
++article_number n_articles;
++article_header **articles;
++
+ extern int ignore_fancy_select;
+ extern int killed_articles;
+
+--- a/articles.h
b/articles.h
+@@ -10,8 +10,8 @@
+
+ /* article headers */
+
+-article_number n_articles;
+-article_header **articles;
++extern article_number n_articles;
++extern article_header **articles;
+
+
+ typedef struct thunk {
+--- a/news.h
b/news.h
+@@ -44,7 +44,9 @@
+ char *ng_xlines;/* lines (from header) */
+ int ng_lines; /* lines (decoded) */
+ char *ng_comment; /* comment-to (rfmail) */
+-} news;
++};
++
++extern struct news_header news;
+
+
+ /*
+@@ -62,7 +64,9 @@
+ char *dg_to;/* to*/
+
+ int dg_lines; /* lines (pseudo field) */
+-} digest;
++};
++
++extern struct digest_header digest;
+
+
+ #define NEWS_HEADER_BUFFER 4096
+--- a/digest.c
b/digest.c
+@@ -23,6 +23,8 @@
+
+ /* digest.c */
+
++struct digest_header digest;
++
+ static char **dg_hdr_field(register char *lp, int all);
+
+ int strict_from_parse = 2;
+--- a/news.c
b/news.c
+@@ -22,6 +22,8 @@
+
+ /* news.c */
+
++struct news_header news;
++
+ static char **art_hdr_field(register char *lp, int all);
+
+
diff -Nru nn-6.7.3/debian/patches/series nn-6.7.3/debian/patches/series
--- nn-6.7.3/debian/patches/series 2020-04-04 05:57:39.0 -0400
+++ nn-6.7.3/debian/patches/series 2021-01-12 23:25:33.0 -0500
@@ -5,3 +5,4 @@
04-spelling.diff
05-fix-compile.diff
06-maintainers-additions.diff
+07-gcc-10.diff
Processed: Re: nn: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957610 [src:nn] nn: ftbfs with GCC-10 Added tag(s) patch. -- 957610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979978: lime-forensics-dkms: unable to make or make install due to error set_fs
Thanks a lot Gregory and Paul. I will use a PR from upstream site[1]. I tested this patch and it works fine. The patch used in Ubuntu seems a bit wrong[2]. [1] https://github.com/504ensicsLabs/LiME/pull/85 [2] https://github.com/504ensicsLabs/LiME/pull/83 Cheers, Eriberto Em ter., 12 de jan. de 2021 às 11:26, Paul Wise escreveu: > > Control: severity -1 serious > Control: tags -1 - ftbfs > Control: tags -1 + patch > > On Tue, 12 Jan 2021 09:00:57 -0500 Gregory Lamarche wrote: > > >* What was the outcome of this action? instead of building the modules > > it just errors out and gives error > > It looks like Ubuntu have a patch for this: > > https://patches.ubuntu.com/l/lime-forensics/lime-forensics_1.9.1-1ubuntu1.patch > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise
Bug#980024: pdmenu: FTBFS with GCC 10
Source: pdmenu Version: 1.3.4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, pdmenu currently FTBFS in unstable with GCC 10 as default. There is a patch in the linked VCS repo from September that has not been uploaded - can you please consider uploading it? We applied it successfully in Ubuntu but would prefer not to carry a delta. Thanks, Logan
Bug#980023: petri-foo: FTBFS with GCC 10
Source: petri-foo
Version: 0.1.87-4
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Hi,
petri-foo currently FTBFS on rebuild in unstable with GCC 10 as default
because of a variable being defined multiple times.
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch: Fix FTBFS with GCC 10.
Thanks for considering the patch.
Logan
diff -Nru petri-foo-0.1.87/debian/control petri-foo-0.1.87/debian/control
--- petri-foo-0.1.87/debian/control 2018-02-05 11:51:44.0 -0500
+++ petri-foo-0.1.87/debian/control 2021-01-12 22:37:28.0 -0500
@@ -1,8 +1,7 @@
Source: petri-foo
Section: sound
Priority: optional
-Maintainer: Ubuntu Developers
-XSBC-Original-Maintainer: Debian Multimedia Maintainers
+Maintainer: Debian Multimedia Maintainers
Uploaders:
Alessio Treglia ,
Jaromír Mikeš
diff -Nru petri-foo-0.1.87/debian/patches/gcc-10.patch
petri-foo-0.1.87/debian/patches/gcc-10.patch
--- petri-foo-0.1.87/debian/patches/gcc-10.patch1969-12-31
19:00:00.0 -0500
+++ petri-foo-0.1.87/debian/patches/gcc-10.patch2021-01-12
22:37:27.0 -0500
@@ -0,0 +1,21 @@
+--- a/gui/gui.c
b/gui/gui.c
+@@ -93,6 +93,8 @@
+ /* current patch, makes passing patch id to sample editor easier */
+ static int cur_patch = -1;
+
++GtkRecentManager *recent_manager;
++
+
+ GtkWidget* gui_title_new(const char* msg)
+ {
+--- a/gui/gui.h
b/gui/gui.h
+@@ -107,6 +107,6 @@
+
+ void gui_set_session_mode(void);
+
+-GtkRecentManager *recent_manager;
++extern GtkRecentManager *recent_manager;
+
+ #endif /* __GUI_H__ */
diff -Nru petri-foo-0.1.87/debian/patches/series
petri-foo-0.1.87/debian/patches/series
--- petri-foo-0.1.87/debian/patches/series 2016-12-23 10:09:46.0
-0500
+++ petri-foo-0.1.87/debian/patches/series 2021-01-12 22:36:12.0
-0500
@@ -1,2 +1,3 @@
0003-desktop_file_fix.patch
0005-spelling.patch
+gcc-10.patch
Bug#978680: marked as done (xfce4-indicator-plugin: build-depends on obsolete package.)
Your message dated Wed, 13 Jan 2021 02:24:39 + with message-id and subject line Bug#978680: fixed in xfce4-indicator-plugin 2.4.0-1 has caused the Debian Bug report #978680, regarding xfce4-indicator-plugin: build-depends on obsolete package. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xfce4-indicator-plugin Version: 2.3.4-2 Severity: serious Tags: bullseye, sid xfce4-indictor-plugin build-depends on libexo-1-dev which is no longer built by the exo source package, it is still present in unstable as a cruft package, but is completely gone from testing. --- End Message --- --- Begin Message --- Source: xfce4-indicator-plugin Source-Version: 2.4.0-1 Done: Unit 193 We believe that the bug you reported is fixed in the latest version of xfce4-indicator-plugin, 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 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Unit 193 (supplier of updated xfce4-indicator-plugin 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: SHA384 Format: 1.8 Date: Tue, 12 Jan 2021 20:30:45 -0500 Source: xfce4-indicator-plugin Architecture: source Version: 2.4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Xfce Maintainers Changed-By: Unit 193 Closes: 978680 Changes: xfce4-indicator-plugin (2.4.0-1) unstable; urgency=medium . * Team upload. * d/watch: Update for mirrorbit and use uscan special strings. * New upstream version 2.4.0. - Refresh patch. * d/compat, d/control: - Drop d/compat in favor of debhelper-compat, bump to 12. * d/control: - Drop gtk-doc-tools and libexo-1-dev from Build-Depends. (Closes: #978680) - Update 'Homepage' field, goodies.xfce → docs.xfce. - R³: no. * d/rules: Drop autoreconf override, no longer needed. * Update Standards-Version to 4.5.1. Checksums-Sha1: 062c7299bfa01357b3820bf56defc41fd468b9d0 2333 xfce4-indicator-plugin_2.4.0-1.dsc 15f9c4b01e8cce7fe36503447d9c748b95b08a94 389228 xfce4-indicator-plugin_2.4.0.orig.tar.bz2 152ca3ca9fe67fd793c5932038ad5232ef5e32e4 5900 xfce4-indicator-plugin_2.4.0-1.debian.tar.xz 7f34bfa00e8c3ae0c12c05a2a13262834d8b5ed6 15619 xfce4-indicator-plugin_2.4.0-1_amd64.buildinfo Checksums-Sha256: 005c29841b380cc728bd8526101646ce12fc1ae4e8eccad5c197aa33ee40b6a3 2333 xfce4-indicator-plugin_2.4.0-1.dsc 0cbd42bff37dc4c688802a0aa921eabcb27adb724e4b99457c19de17102614ae 389228 xfce4-indicator-plugin_2.4.0.orig.tar.bz2 482f92b9702183f755271864d22662f23b3d734bede5603b32d885751ad743da 5900 xfce4-indicator-plugin_2.4.0-1.debian.tar.xz 69a5162ff9e6d94e94dad87948401d32bd8be3bb4b97639cadae536993324962 15619 xfce4-indicator-plugin_2.4.0-1_amd64.buildinfo Files: 7c349982fb9fe7497aaef26086ed2d53 2333 xfce optional xfce4-indicator-plugin_2.4.0-1.dsc ae9d2696e80ba9dac4defa0cdd864fc7 389228 xfce optional xfce4-indicator-plugin_2.4.0.orig.tar.bz2 ba2dd97c9272ceb6d9be9c04b2c1301a 5900 xfce optional xfce4-indicator-plugin_2.4.0-1.debian.tar.xz fa0fcbd6e58523659f8b3d5df064aa6f 15619 xfce optional xfce4-indicator-plugin_2.4.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAl/+TnUACgkQUAHhsJqj dEsYfg/9GA8/YDCfRygOu+EwEDeLiQ+TbYV0CqXQ6rRY+xmJELX/18UimSQ/B02Z k/0jMzw1ob1u5SSywfg3hh5Yh1x31okhY63hRzEAoTSk6J9VXuB5pFBuwIoV74CL oTmJLEInSgBYWG3YMm/3WkorModNKhZIJ82YuUh4DFWVKoItsFeCWGv+wH4ID2b+ fDChTmHQ9Fgw06leAf3zmnCKuzFNR+v8/+ULykuGjFCFao6DI4boKjHyC/KhZfBL fBuYw+IzAzX8FTfPDTJSMO+Pzk7FKlPBfXLyMvqw1U5A4ElFhhnXgCr0fklt6egB s9o28sEpnwhfs4Gs4JLyNmhNURxh1/EJJcs8/LDJX31ax5/arcEGFLKBYI5Y+ZYo nxc44rJoAUfMdwm5FwD6/NvVxcSOZbHCMoVlbPno0X8PultUUllrLnWK0LGrkNwz 09L5Afcma0N+rvkwOuutgluY05mm4FIKLaNq7iEsExhZd7ZzMJdQTPjRkgWy0IYl MBt9isNX1Ql/b1duao5QKRqeUfmHfVQzgC5AtdscnfamIQf+W3g/IrWeZtgrHhLr w+BTLiiGy9N5YIuM/h1HbZzLQu/cFJCzuZrbjsXJKZPkQ6xbjmn8BHbGRWVPHhtw gsQwRwm90KkfOrpkQ7kDbyc8jnz2IHnZqn6pCUGPxQswtBlKXCY= =aWrh -END PGP SIGNATURE End Message ---
Bug#979621: marked as done (pandas: autopkgtest regression in testing: No tables found)
Your message dated Tue, 12 Jan 2021 22:48:45 +
with message-id
and subject line Bug#979621: fixed in pandas 1.1.5+dfsg-2
has caused the Debian Bug report #979621,
regarding pandas: autopkgtest regression in testing: No tables found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
979621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandas
Version: 1.1.5+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of this report. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
By the way: as your test is accessing the internet, you should add a
"needs-internet" restriction
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pandas/9462264/log.gz
=== FAILURES
===
_ TestReadHtml.test_banklist_url_positional_match[bs4]
_
self =
@tm.network
def test_banklist_url_positional_match(self):
url = "http://www.fdic.gov/bank/individual/failed/banklist.html;
# Passing match argument as positional should cause a FutureWarning.
with tm.assert_produces_warning(FutureWarning):
> df1 = self.read_html(
url, "First Federal Bank of Florida", attrs={"id": "table"}
)
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pandas
Source-Version: 1.1.5+dfsg-2
Done: Rebecca N. Palmer
We believe that the bug you reported is fixed in the latest version of
pandas, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rebecca N. Palmer (supplier of updated pandas package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 12 Jan 2021 21:06:04 +
Source: pandas
Architecture: source
Version: 1.1.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Rebecca N. Palmer
Closes: 977470 979621
Changes:
pandas (1.1.5+dfsg-2) unstable; urgency=medium
.
* Remove dead URL from tests/examples. (Closes: #979621)
* Mark autopkgtest needs-internet.
* Revert "Print uname etc during build".
* Mark matplotlib nocheck/nodoc and allow building on ports without
matplotlib or numexpr. (Closes: #977470)
* Add python3-tabulate build/test-depends.
* Add bottleneck and numexpr test-depends.
* Tests: don't require warnings that jedi no longer produces.
Checksums-Sha1:
d786111ad97fb88f1ce2ebc982b5549c51c43b1d 4425 pandas_1.1.5+dfsg-2.dsc
21fe479cadefb4f60fa88d694f34ec1e9c18df57 6
pandas_1.1.5+dfsg-2.debian.tar.xz
024d39996177b37337842a024ed7cb1bfc189143 6001
pandas_1.1.5+dfsg-2_source.buildinfo
Checksums-Sha256:
ed848fe62c68034f908fc6856262a1d41c38e4fef2656a8ec55339fc4e8f90b1 4425
pandas_1.1.5+dfsg-2.dsc
d434fe80151306a15282699255f40af6faf3568e595a0d50934f637e9c9b4a1e 6
pandas_1.1.5+dfsg-2.debian.tar.xz
1c525c730827f7791887cd6066351bdd1d9d44bd0a7a411472626ae51b3df3cd 6001
pandas_1.1.5+dfsg-2_source.buildinfo
Files:
d3646ba1b5d3c945752954c3f41e749e 4425 python optional pandas_1.1.5+dfsg-2.dsc
8e4c074508a8d1a02878dd74af643c24 6 python optional
pandas_1.1.5+dfsg-2.debian.tar.xz
0186973cd20bef941243d1a59430e07c 6001 python optional
pandas_1.1.5+dfsg-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAl/+IOgYHHJlYmVjY2Ff
cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJmrbEQAJ9VADr/k9SUczmAnLs6uhAt
MWtrVVOXSg1SNPmQxih+SAK/jxbdcqQKJsLb9dS5/6QnU3aWabsdnahnHIbqXU8X
JyZM9pR4wRlB1Bo18c7Ku+t7fNh0vqVi3xJ0VQGfNSVy1D1XLSHDZ3Nhvd8v/9XY
KQCF3tE4aURvpgYhjTF0yGjUmwapW0YqDGqw7/GpyK/1F37oSPNVQO+ivUe/OzY8
Bug#975851: marked as done (sensible-utils: FTBFS: po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of 'full', 'counter', 'noline', 'file' or 'never'))
Your message dated Tue, 12 Jan 2021 22:48:50 +
with message-id
and subject line Bug#975851: fixed in sensible-utils 0.0.14
has caused the Debian Bug report #975851,
regarding sensible-utils: FTBFS: po4a::po: Invalid value for option 'porefs'
('noline,wrap' is not one of 'full', 'counter', 'noline', 'file' or 'never')
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
975851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sensible-utils
Version: 0.0.12+nmu1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/man'
> Makefile:541: warning: ignoring prerequisites on suffix rule definition
> Makefile:543: warning: ignoring prerequisites on suffix rule definition
> Makefile:545: warning: ignoring prerequisites on suffix rule definition
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-editor.man
> >sensible-editor.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-browser.man
> >sensible-browser.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-pager.man
> >sensible-pager.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' select-editor.man
> >select-editor.1
> po4a --previous --srcdir . --destdir . --no-backups --porefs noline,wrap
> --msgmerge-opt=--add-location=file --package-name sensible-utils
> ./po4a/po4a.cfg
> po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of
> 'full', 'counter', 'noline', 'file' or 'never')
> make[2]: *** [Makefile:536: man.stamp] Error 2
The full build log is available from:
http://qa-logs.debian.net/2020/11/25/sensible-utils_0.0.12+nmu1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: sensible-utils
Source-Version: 0.0.14
Done: Bastien Roucariès
We believe that the bug you reported is fixed in the latest version of
sensible-utils, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastien Roucariès (supplier of updated sensible-utils
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 12 Jan 2021 22:01:50 +
Source: sensible-utils
Architecture: source
Version: 0.0.14
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar
Bug#979744: marked as done (libpmix2: pmix_psquash_base_select failed during pmix_init)
Your message dated Tue, 12 Jan 2021 22:35:40 + with message-id and subject line Bug#979744: fixed in pmix 4.0.0-3 has caused the Debian Bug report #979744, regarding libpmix2: pmix_psquash_base_select failed during pmix_init to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpmix2 Version: 4.0.0-2 Severity: normal Control: affects -1 src:mpi4py libpetsc-real3.14 dolfix dolfinx The latest permutation of openmpi 4.1.0-5 and pmix2 4.0.0-2 is still causing tests in client applications to fail. For instance, an example from petsc debci, https://ci.debian.net/data/autopkgtest/testing/amd64/p/petsc/9558266/log.gz reports: = run testex5f Possible error running Fortran example src/snes/tutorials/ex5f with 1 MPI process See http://www.mcs.anl.gov/petsc/documentation/faq.html -- It looks like pmix_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during pmix_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an PMIX developer): pmix_psquash_base_select failed --> Returned value -46 instead of PMIX_SUCCESS -- [ci-010-e68ada94:15922] PMIX ERROR: NOT-FOUND in file ../../../src/server/pmix_server.c at line 386 I'm not sure if this needs to be fixed in openmpi or in pmix, but since the message refers to pmix, I'm filing against libpmix2. Transfer to openmpi if needed. Thanks! Drew -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpmix2 depends on: ii libc62.31-9 ii libevent-core-2.1-7 2.1.12-stable-1 ii libevent-pthreads-2.1-7 2.1.12-stable-1 ii libhwloc-plugins 2.4.0+dfsg-3 ii libhwloc15 2.4.0+dfsg-3 ii zlib1g 1:1.2.11.dfsg-2 libpmix2 recommends no packages. libpmix2 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: pmix Source-Version: 4.0.0-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of pmix, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated pmix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 15:11:53 + Source: pmix Architecture: source Version: 4.0.0-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 978066 979744 Changes: pmix (4.0.0-3) unstable; urgency=medium . * Regression: ensure pmix-mca-params.conf is installed in share directory to provide correct mca_base_component_path. Closes: #978066, #979744 Checksums-Sha1: 130c64f1c0194d00945c023d3be49d92e9e5300b 2219 pmix_4.0.0-3.dsc 1cd1f73c644b3ecac751d18f684c2cd16d624649 8964 pmix_4.0.0-3.debian.tar.xz Checksums-Sha256: ce9304d2fb5fb5a8a40b49021724500724410456dd9d99c3afbf957162ed241e 2219 pmix_4.0.0-3.dsc f538b1057afaa4173e6d8cd5c111a65d702c0d1e62b9ea85597b6f11e390c18c 8964 pmix_4.0.0-3.debian.tar.xz Files: 57562546bb40894db4007c7a8ab11d14 2219 net optional pmix_4.0.0-3.dsc e0783ba33f2a3ad569e69dfc13bc1e59 8964 net optional pmix_4.0.0-3.debian.tar.xz -BEGIN PGP SIGNATURE-
Bug#978066: marked as done (pmix: breaks openmpi autopkgtest)
Your message dated Tue, 12 Jan 2021 22:35:40 + with message-id and subject line Bug#978066: fixed in pmix 4.0.0-3 has caused the Debian Bug report #978066, regarding pmix: breaks openmpi autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pmix Version: 4.0.0~rc1-1 Severity: serious Tags: ftbfs Control: affects -1 + src:deal.ii X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Hi Maintainer The upload of pmix 4.0.0~rc1-1 to unstable causes the autopkgtests of openmpi in testing to fail [1]. I've copied what I hope is the relevant part of the log below. There's also a FTBFS in the recent binNMU of deal.ii [2]. I believe this is related to pmix rather than openmpi as the binNMU failed in Ubuntu as well, where they have the new pmix, but not the new openmpi. Regards Graham [1] https://ci.debian.net/packages/o/openmpi/testing/amd64/ [2] https://buildd.debian.org/status/package.php?p=deal.ii=unstable autopkgtest [06:32:43]: test hello2: [--- [ci-359-a03b0931:01932] *** Process received signal *** [ci-359-a03b0931:01932] Signal: Segmentation fault (11) [ci-359-a03b0931:01932] Signal code: Invalid permissions (2) [ci-359-a03b0931:01932] Failing at address: 0x5632cd610c70 [ci-359-a03b0931:01932] [ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7fcc11a84d00] [ci-359-a03b0931:01932] [ 1] [0x5632cd610c70] [ci-359-a03b0931:01932] *** End of error message *** Segmentation fault autopkgtest [06:32:46]: test hello2: ---] autopkgtest [06:32:46]: test hello2: - - - - - - - - - - results - - - - - - - - - - hello2 FAIL non-zero exit status 139 autopkgtest [06:32:46]: test hello2: - - - - - - - - - - stderr - - - - - - - - - - [ci-359-a03b0931:01932] *** Process received signal *** [ci-359-a03b0931:01932] Signal: Segmentation fault (11) [ci-359-a03b0931:01932] Signal code: Invalid permissions (2) [ci-359-a03b0931:01932] Failing at address: 0x5632cd610c70 [ci-359-a03b0931:01932] [ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7fcc11a84d00] [ci-359-a03b0931:01932] [ 1] [0x5632cd610c70] [ci-359-a03b0931:01932] *** End of error message *** Segmentation fault autopkgtest [06:32:47]: test hello4: preparing testbed Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up autopkgtest-satdep (0) ... (Reading database ... 18479 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [06:32:53]: test hello4: [--- [ci-359-a03b0931:02130] *** Process received signal *** [ci-359-a03b0931:02130] Signal: Segmentation fault (11) [ci-359-a03b0931:02130] Signal code: Invalid permissions (2) [ci-359-a03b0931:02130] Failing at address: 0x55dfd16e6d00 [ci-359-a03b0931:02130] [ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7f137754cd00] [ci-359-a03b0931:02130] [ 1] [0x55dfd16e6d00] [ci-359-a03b0931:02130] *** End of error message *** Segmentation fault autopkgtest [06:32:54]: test hello4: ---] autopkgtest [06:32:55]: test hello4: - - - - - - - - - - results - - - - - - - - - - hello4 FAIL non-zero exit status 139 autopkgtest [06:32:55]: test hello4: - - - - - - - - - - stderr - - - - - - - - - - [ci-359-a03b0931:02130] *** Process received signal *** [ci-359-a03b0931:02130] Signal: Segmentation fault (11) [ci-359-a03b0931:02130] Signal code: Invalid permissions (2) [ci-359-a03b0931:02130] Failing at address: 0x55dfd16e6d00 [ci-359-a03b0931:02130] [ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7f137754cd00] [ci-359-a03b0931:02130] [ 1] [0x55dfd16e6d00] [ci-359-a03b0931:02130] *** End of error message *** Segmentation fault autopkgtest [06:32:55]: summary hello1 FAIL non-zero exit status 139 hello2 FAIL non-zero exit status 139 hello4 FAIL non-zero exit status 139 --- End Message --- --- Begin Message --- Source: pmix Source-Version: 4.0.0-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of pmix, which is due to be installed in the Debian FTP archive. A summary of the changes between this
Processed: limit source to sensible-utils, tagging 913559, tagging 953134, tagging 397051, tagging 975851 ...
Processing commands for cont...@bugs.debian.org:
> limit source sensible-utils
Limiting to bugs with field 'source' containing at least one of 'sensible-utils'
Limit currently set to 'source':'sensible-utils'
> tags 913559 + pending
Bug #913559 [sensible-utils] sensible-utils: select-editor should quote path
used in the script
Added tag(s) pending.
> tags 953134 + pending
Bug #953134 [sensible-utils] sensible-utils: 0.0.12+nmu1 broke recursion
protection
Added tag(s) pending.
> tags 397051 + pending
Bug #397051 [sensible-utils] debianutils: sensible-editor(1) should mention
VISUAL
Added tag(s) pending.
> tags 975851 + pending
Bug #975851 [src:sensible-utils] sensible-utils: FTBFS: po4a::po: Invalid value
for option 'porefs' ('noline,wrap' is not one of 'full', 'counter', 'noline',
'file' or 'never')
Added tag(s) pending.
> tags 969587 + pending
Bug #969587 [sensible-utils] sensible-utils: document select-editor and
.selected_editor file
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
397051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397051
913559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913559
953134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953134
969587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969587
975851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#980012: marked as done (FTBFS: TypeError: Cannot read property 'register' of undefined)
Your message dated Tue, 12 Jan 2021 22:49:45 +0100 with message-id <651a4879-54b2-81da-8c54-02421ecde...@debian.org> and subject line Re: Bug#980012: FTBFS: TypeError: Cannot read property 'register' of undefined has caused the Debian Bug report #980012, regarding FTBFS: TypeError: Cannot read property 'register' of undefined to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: coffeescript Version: 1.12.8~dfsg-4 Severity: serious coffeescript build seems broken. Logs: dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building coffeescript using existing ./coffeescript_1.12.8~dfsg.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building coffeescript in coffeescript_1.12.8~dfsg-5.debian.tar.xz dpkg-source: info: building coffeescript in coffeescript_1.12.8~dfsg-5.dsc debian/rules binary CDBS WARNING: copyright-check disabled - licensecheck is missing. test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p "." Scanning upstream source for new/changed copyright notices... set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive --copyright --deb-fmt --ignore '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 -- * | /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints /bin/sh: 1: /usr/bin/licensecheck: not found 0 combinations of copyright and licensing found. No new copyright notices found - assuming no news is good news... touch debian/stamp-copyright-check mkdir -p "debian/upstream-cruft" cp -a "lib" "debian/upstream-cruft/lib"; touch debian/stamp-upstream-cruft mkdir -p docs/v1/browser-compiler chmod +x bin/cake bin/cake build bin/cake build bin/cake build:browser bin/cake test (node:2439631) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (node:2439631) [DEP0124] DeprecationWarning: REPLServer.rli is deprecated passed 856 tests in 1.66 seconds bin/cake test:browser /<>/Cakefile:450 CoffeeScript.register(); ^ TypeError: Cannot read property 'register' of undefined at runTests (/<>/Cakefile:450:18) at Object.action (/<>/Cakefile:562:19) at invoke (/<>/lib/coffee-script/cake.js:44:26) at Object.exports.run (/<>/lib/coffee-script/cake.js:70:20) at Object. (/<>/bin/cake:15:42) at Module._compile (internal/modules/cjs/loader.js:999:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) at Module.load (internal/modules/cjs/loader.js:863:32) at Function.Module._load (internal/modules/cjs/loader.js:708:14) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) at internal/main/run_main_module.js:17:47 --- End Message --- --- Begin Message --- Problem is related to uglifyjs 3, not a coffeescript bug--- End Message ---
Bug#980009: marked as done (node-js-yaml frequently FTBFS: test timeout)
Your message dated Tue, 12 Jan 2021 21:50:23 + with message-id and subject line Bug#980009: fixed in node-js-yaml 3.14.1+dfsg+~3.12.6-2 has caused the Debian Bug report #980009, regarding node-js-yaml frequently FTBFS: test timeout to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-js-yaml Version: 3.14.1+dfsg+~3.12.6-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-js-yaml.html https://buildd.debian.org/status/fetch.php?pkg=node-js-yaml=all=3.14.1%2Bdfsg%2B~3.12.6-1=1610381331=0 ... 254 passing (3s) 1 failing 1) Properties Load from dumped should be the original object: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/<>/test/25-dumper-fuzzy.js) at Test.Runnable._timeoutError (/usr/share/nodejs/mocha/lib/runnable.js:432:10) at done (/usr/share/nodejs/mocha/lib/runnable.js:306:18) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:387:7) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:352:5) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:677:10) at /usr/share/nodejs/mocha/lib/runner.js:801:12 at next (/usr/share/nodejs/mocha/lib/runner.js:594:14) at /usr/share/nodejs/mocha/lib/runner.js:604:7 at next (/usr/share/nodejs/mocha/lib/runner.js:486:14) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:572:5) at processImmediate (internal/timers.js:461:21) dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 make: *** [debian/rules:8: binary-indep] Error 25 --- End Message --- --- Begin Message --- Source: node-js-yaml Source-Version: 3.14.1+dfsg+~3.12.6-2 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-js-yaml, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-js-yaml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 22:25:37 +0100 Source: node-js-yaml Architecture: source Version: 3.14.1+dfsg+~3.12.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 980009 Changes: node-js-yaml (3.14.1+dfsg+~3.12.6-2) unstable; urgency=medium . * Increase test timeout (Closes: #980009) Checksums-Sha1: c535eac144ed31ab95188f0fee5ee49dc209396a 2612 node-js-yaml_3.14.1+dfsg+~3.12.6-2.dsc 2a3f7355d5b9c9bc10f1648ab8b6399f8684a0d4 89956 node-js-yaml_3.14.1+dfsg+~3.12.6-2.debian.tar.xz Checksums-Sha256: d4b898c81ce6e726d4e26c4a026f89419b6be3647edd687abfba9fbcc948f15b 2612 node-js-yaml_3.14.1+dfsg+~3.12.6-2.dsc 154d9a87ddccbaa46da8e170f699e7416529ad55aaec53026b67e10eab3cc531 89956 node-js-yaml_3.14.1+dfsg+~3.12.6-2.debian.tar.xz Files: 05774eb285e99943d706edf7a9618a6d 2612 javascript optional node-js-yaml_3.14.1+dfsg+~3.12.6-2.dsc d51589f4d037828d21882e50c70d1ae8 89956 javascript optional node-js-yaml_3.14.1+dfsg+~3.12.6-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/+FBkACgkQ9tdMp8mZ 7unWnA//YgIO4UH9Cq1WRA/Q9VIyvzV7gFJ9o5nVJvriugthmLe6YCvyMoDFoJBm xV07Oj8G6uHBbCESi5tbpRqs1zPDuwgGxRs8srY136vFgdqHbLLVc3F+PmFTZ8om +7dOFzT/g7HfOYfTEHKExrTvRXwvHodVsKWXK8sirP/j8x2gW5XtvDop2e7OaXKT X5fR63vZWZiAOI8+e07lbqHyc3BJd9M7g3XovvEk4SZxS2AgB1jHwXb+3tbZMMSQ 18qwEaDrvEnsOc3DSsy87O/StHvm+AL6WRKvi5A+unQIRSqAfLo5x7iWOgIGvwZX CyCmoNrOMZGnUcSk38HbjlMosieskCSwf/F/Il0YKosxzN1cA5YAujcRDAsIFR1J 6jQALiBZAQ+Ng11JvqPcMqRb4al7agoq4nawyDPQ0U1NbnPPx/fJttZfi9f/oLFx 2bMPdhy94694HAJvUDQa6Xq5Q/xp87H/H8OtUoIgOJ0UeNjXP5+wqLHHu1bKDTJP F5m3NqwBKCmtDk7Xu7Z4luJd9kqQvbnfjQCyFWsh6kLXIAhgBydMXmZucBIlLWZV 3JPPPoffMLbl5WWr15CvincRLP5LW8E/OuGAByz/ZJE5jOOKSANFmLN71fJ6bmts OACskO+tkn4FjvCkbTakRECWeZ2qBUa5R5n/JqdGO9yDsX2Wki8= =wQfj -END PGP
Bug#980012: FTBFS: TypeError: Cannot read property 'register' of undefined
Package: coffeescript Version: 1.12.8~dfsg-4 Severity: serious coffeescript build seems broken. Logs: dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building coffeescript using existing ./coffeescript_1.12.8~dfsg.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building coffeescript in coffeescript_1.12.8~dfsg-5.debian.tar.xz dpkg-source: info: building coffeescript in coffeescript_1.12.8~dfsg-5.dsc debian/rules binary CDBS WARNING: copyright-check disabled - licensecheck is missing. test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p "." Scanning upstream source for new/changed copyright notices... set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive --copyright --deb-fmt --ignore '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 -- * | /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints /bin/sh: 1: /usr/bin/licensecheck: not found 0 combinations of copyright and licensing found. No new copyright notices found - assuming no news is good news... touch debian/stamp-copyright-check mkdir -p "debian/upstream-cruft" cp -a "lib" "debian/upstream-cruft/lib"; touch debian/stamp-upstream-cruft mkdir -p docs/v1/browser-compiler chmod +x bin/cake bin/cake build bin/cake build bin/cake build:browser bin/cake test (node:2439631) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (node:2439631) [DEP0124] DeprecationWarning: REPLServer.rli is deprecated passed 856 tests in 1.66 seconds bin/cake test:browser /<>/Cakefile:450 CoffeeScript.register(); ^ TypeError: Cannot read property 'register' of undefined at runTests (/<>/Cakefile:450:18) at Object.action (/<>/Cakefile:562:19) at invoke (/<>/lib/coffee-script/cake.js:44:26) at Object.exports.run (/<>/lib/coffee-script/cake.js:70:20) at Object. (/<>/bin/cake:15:42) at Module._compile (internal/modules/cjs/loader.js:999:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) at Module.load (internal/modules/cjs/loader.js:863:32) at Function.Module._load (internal/modules/cjs/loader.js:708:14) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) at internal/main/run_main_module.js:17:47
Processed: src:r-cran-dbplyr: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 2.0.0-1 Bug #980011 [src:r-cran-dbplyr] src:r-cran-dbplyr: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions r-cran-dbplyr/2.0.0-1. Bug #980011 [src:r-cran-dbplyr] src:r-cran-dbplyr: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 980011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980011: src:r-cran-dbplyr: fails to migrate to testing for too long: autopkgtest regression
Source: r-cran-dbplyr Version: 1.4.4-1 Severity: serious Control: close -1 2.0.0-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:r-cran-dbplyr in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-dbplyr OpenPGP_signature Description: OpenPGP digital signature
Bug#980009: marked as pending in node-js-yaml
Control: tag -1 pending Hello, Bug #980009 in node-js-yaml reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-js-yaml/-/commit/2b0a3b045dfd69c8eac3b038b643ca5433f4bd4d Increase test timeout Closes: #980009 (this message was generated automatically) -- Greetings https://bugs.debian.org/980009
Processed: Bug#980009 marked as pending in node-js-yaml
Processing control commands: > tag -1 pending Bug #980009 [src:node-js-yaml] node-js-yaml frequently FTBFS: test timeout Added tag(s) pending. -- 980009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980009: node-js-yaml frequently FTBFS: test timeout
Source: node-js-yaml Version: 3.14.1+dfsg+~3.12.6-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-js-yaml.html https://buildd.debian.org/status/fetch.php?pkg=node-js-yaml=all=3.14.1%2Bdfsg%2B~3.12.6-1=1610381331=0 ... 254 passing (3s) 1 failing 1) Properties Load from dumped should be the original object: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/<>/test/25-dumper-fuzzy.js) at Test.Runnable._timeoutError (/usr/share/nodejs/mocha/lib/runnable.js:432:10) at done (/usr/share/nodejs/mocha/lib/runnable.js:306:18) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:387:7) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:352:5) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:677:10) at /usr/share/nodejs/mocha/lib/runner.js:801:12 at next (/usr/share/nodejs/mocha/lib/runner.js:594:14) at /usr/share/nodejs/mocha/lib/runner.js:604:7 at next (/usr/share/nodejs/mocha/lib/runner.js:486:14) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:572:5) at processImmediate (internal/timers.js:461:21) dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 make: *** [debian/rules:8: binary-indep] Error 25
Processed: Re: Bug#976097: python3-django-postorius cannot be installed in testing
Processing control commands: > retitle -1 postorius: autopkgtest failure Bug #976097 [src:postorius] python3-django-postorius cannot be installed in testing Changed Bug title to 'postorius: autopkgtest failure' from 'python3-django-postorius cannot be installed in testing'. -- 976097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962203: NMU
Of course I would be willing to help out on package maintenance: I won't be able to do much this week, but in coming weeks I should be more helpful signature.asc Description: This is a digitally signed message part
Bug#976097: python3-django-postorius cannot be installed in testing
Control: retitle -1 postorius: autopkgtest failure On Sun, Nov 29, 2020 at 06:42:17PM +0100, Matthias Klose wrote: > Package: src:postorius > Version: 1.3.2-2.1 > Severity: serious > Tags: sid bullseye > > python3-django-postorius cannot be installed in testing. The autopkg tests > pass > in unstable but fail in testing. > > see https://ci.debian.net/packages/p/postorius/testing/amd64/ > > [...] > Updating certificates in /etc/ssl/certs... > 126 added, 0 removed; done. > Setting up libpython3.8-stdlib:amd64 (3.8.6-1) ... > Setting up python3.8 (3.8.6-1) ... > Processing triggers for ca-certificates (20200601) ... > Updating certificates in /etc/ssl/certs... > 0 added, 0 removed; done. > Running hooks in /etc/ca-certificates/update.d... > done. > autopkgtest: WARNING: package python3-django-postorius is not installed though > it should be >... This looks like temporary breakagge during the python3 transition. Current failures are: https://ci.debian.net/packages/p/postorius/ ...Creating test database for alias 'default'... .x.x..F..E.E..EEE.E..EEE.EEE...autopkgtest [17:25:11]: ERROR: timed out on command "su -s /bin/bash root -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.8k_pq1u2/downtmp/build.ZWo/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.8k_pq1u2/downtmp/python3-django-postorius-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.8k_pq1u2/downtmp/python3-django-postorius-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.8k_pq1u2/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.8k_pq1u2/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=48; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export AUTOPKGTEST_NORMAL_USER=debci; export ADT_NORMAL_USER=debci; chmod +x /tmp/autopkgtest-lxc.8k_pq1u2/downtmp/build.ZWo/src/debian/tests/python3-django-postorius; touch /tmp/autopkgtest-lxc.8k_pq1u2/downtmp/python3-django-postorius-stdout /tmp/autopkgtest-lxc.8k_pq1u2/downtmp/python3-django-postorius-stderr; /tmp/autopkgtest-lxc.8k_pq1u2/downtmp/build.ZWo/src/debian/tests/python3-django-postorius 2> >(tee -a /tmp/autopkgtest-lxc.8k_pq1u2/downtmp/python3-django-postorius-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.8k_pq1u2/downtmp/python3-django-postorius-stdout);" (kind: test) autopkgtest [17:25:11]: test python3-django-postorius: ---] autopkgtest [17:25:11]: test python3-django-postorius: - - - - - - - - - - results - - - - - - - - - - python3-django-postorius FAIL timed out cu Adrian
Processed: tagging 974011
Processing commands for cont...@bugs.debian.org: > tags 974011 + pending Bug #974011 [xmille] xmille: Incorrect license/copyright for xmille Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 974011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979942: [Pkg-javascript-devel] Bug#979942: Bug#979942: Bug#979942: embedding dead code is no fix to bug for removing that same dead code
Quoting Bastien ROUCARIES (2021-01-12 21:17:36) > Fixed it was a little bit hard to test options of compression one by > one but it work now. Great! Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#977960: marked as done (dangling /usr/share/javascript/jquery/jquery.js symlink)
Your message dated Tue, 12 Jan 2021 20:26:30 + with message-id and subject line Bug#977960: fixed in node-jquery 3.5.1+dfsg+~3.5.5-6 has caused the Debian Bug report #977960, regarding dangling /usr/share/javascript/jquery/jquery.js symlink to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjs-jquery Version: 3.5.1+dfsg+~3.5.5-1 Severity: serious Tags: sid bullseye There's at least one dangling /usr/share/javascript/jquery/jquery.js symlink $ dpkg -S /usr/share/javascript/jquery/jquery.js libjs-jquery: /usr/share/javascript/jquery/jquery.js $ ls -l /usr/share/javascript/jquery/jquery.js lrwxrwxrwx 1 root root 34 Dec 22 08:27 /usr/share/javascript/jquery/jquery.js -> ../../nodejs/jquery/dist/jquery.js $ ls -lL /usr/share/javascript/jquery/jquery.js ls: cannot access '/usr/share/javascript/jquery/jquery.js': No such file or directory --- End Message --- --- Begin Message --- Source: node-jquery Source-Version: 3.5.1+dfsg+~3.5.5-6 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of node-jquery, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated node-jquery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 20:48:16 +0100 Source: node-jquery Architecture: source Version: 3.5.1+dfsg+~3.5.5-6 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 977960 979993 Changes: node-jquery (3.5.1+dfsg+~3.5.5-6) unstable; urgency=medium . * Team upload . * fix maintscript to cover releases before it was fixed (including versions where it was fixed but without covering intermediaries - i.e. up until _this_ release); closes: bug#977960, #979993, thanks to Veiko Aasa Checksums-Sha1: 8f40adaa46c6a7f9ec5f247f59ed4d2bfc769f3b 2689 node-jquery_3.5.1+dfsg+~3.5.5-6.dsc b9bcb680c3b8a4a5b3fb37c39bfd1fce62e998b9 5692 node-jquery_3.5.1+dfsg+~3.5.5-6.debian.tar.xz bc06be24ebb3e8f38cb3d6afb80542b5550d0f22 10897 node-jquery_3.5.1+dfsg+~3.5.5-6_amd64.buildinfo Checksums-Sha256: 7974c89827411ac385c1c679ef372f67bb81ba8f2ea9734f91eb1154d20232f3 2689 node-jquery_3.5.1+dfsg+~3.5.5-6.dsc 319b226090c907b81380cac2e161434263600f6222a418c3357dc7e8fa45c7f4 5692 node-jquery_3.5.1+dfsg+~3.5.5-6.debian.tar.xz d569b666bb9d06aaf0ad26e4f40ccac6be69ded6d60a925a0e0b81ffb4194d9c 10897 node-jquery_3.5.1+dfsg+~3.5.5-6_amd64.buildinfo Files: bae7184fcc4d8236a36a17b2b673a01f 2689 javascript optional node-jquery_3.5.1+dfsg+~3.5.5-6.dsc d5a2931be58d41450050f64c2c1c6e33 5692 javascript optional node-jquery_3.5.1+dfsg+~3.5.5-6.debian.tar.xz e66e7a337164272707dab893fcace56d 10897 javascript optional node-jquery_3.5.1+dfsg+~3.5.5-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/9/kAACgkQLHwxRsGg ASGp4Q//dD9f83zMMZvINWWll2+13HKi+lFRM83NKdneSUuA97PTOEmYadaHkC7e hkb8Tm6vcA3zMD3feOYv+L0L1hEbZ6ru7eGQl4Mu14KJVV9cczeJLEEs/45kxvR7 AMqjf8HzJEkdQvYNPx6ykqYYzll1MmqzWHpTVCON6zWDe+cJg5yjSul4YQ3W/fVK Va4PkvsgCL4pO74e5ALs4a5ZI/fTuCowmTHarKoQqCZpLw0eDz6zKtPO2/LXKuGl aWDqOkBbwMIedpYnX4WnucQIoIeCVbRRRqe96hCXpCdLI+c9YrjAYycGk3XUix6n bhR+Yg6FOO6BmSIgNZD0LtkRKukysR3ADWJCGN9xB4d1H4h0pth2xgRzAnEcZQ3T Ua037KFpPGdETm/xkqSjdgjpRlprxqmyAlpXQ1KuSISJjPM3W2LfANIQVpmskQFC bo9/nR1OMI9qf44f2Btyt+koJJ52Hd/nFIznlZW1asNWQQTiDSNC9CzmxEQtBwzi 2U27FfpJvKBiFx0peAgoJo1+IIllWlAiUqPB1EepWvrcz15IGI846PxehXwluf/j 6PMYsK/ZKvYKuVmGQSYMCUCI8JflB+HranAa98yACpY21+v9MYHNQBsoPTZC9qLC 0agKLuLYvB/vmbDDRIGr0kTgxuh9q7TNLysg/uOAlvPMAdbe3iI= =OH2m -END PGP SIGNATURE End Message ---
Bug#979942: marked as done (node-browser-pack: node-uglify is deprecated in favor of uglifyjs)
Your message dated Tue, 12 Jan 2021 20:26:17 + with message-id and subject line Bug#979942: fixed in node-browser-pack 6.1.0+ds-8 has caused the Debian Bug report #979942, regarding node-browser-pack: node-uglify is deprecated in favor of uglifyjs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-browser-pack Severity: important node-browser-pack build depends on node-uglify which is deprecated and will be removed from bullseye (#958117), please update your (build) dependency in favor of uglifyjs or uglifyjs.terser https://bugs.debian.org/958117 (sent using mass-bug) --- End Message --- --- Begin Message --- Source: node-browser-pack Source-Version: 6.1.0+ds-8 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of node-browser-pack, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated node-browser-pack package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 20:04:51 + Source: node-browser-pack Architecture: source Version: 6.1.0+ds-8 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Bastien Roucariès Closes: 979942 Changes: node-browser-pack (6.1.0+ds-8) unstable; urgency=medium . * Bug fix: "node-uglify is deprecated in favor of uglifyjs", thanks to y...@debian.org; (Closes: #979942). * rm prebublish.bin from installed package Checksums-Sha1: 8da9c4f0e252e58286f40a608291a6aa1b4df120 2473 node-browser-pack_6.1.0+ds-8.dsc de7c0259e7b77870c77adfc3ec15bfb06a76 5032 node-browser-pack_6.1.0+ds-8.debian.tar.xz e6bb80b4727a279cb17fff111d6a06da117bd53a 10381 node-browser-pack_6.1.0+ds-8_source.buildinfo Checksums-Sha256: b95d4ee4d5bc2120e1288244b97867cb45a17aa30697dde2a24d85fc26aa1ea6 2473 node-browser-pack_6.1.0+ds-8.dsc 37f8f4e24011d0b8d35fb33a20c5622e018b2797ecf13001f36954f7662ac4c1 5032 node-browser-pack_6.1.0+ds-8.debian.tar.xz b5418ca309c8a70f1057591e06cea956dea093631a4894ade7a4c8ed17b2b0e7 10381 node-browser-pack_6.1.0+ds-8_source.buildinfo Files: 7c347f99c0937d9a8c4b699f56f78ea3 2473 javascript optional node-browser-pack_6.1.0+ds-8.dsc da16e127b0955420276aa531809ce482 5032 javascript optional node-browser-pack_6.1.0+ds-8.debian.tar.xz 7207320c1f028466e770d6474ffb 10381 javascript optional node-browser-pack_6.1.0+ds-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAl/+A1MACgkQADoaLapB CF+e2Q/+NVVzR85MAA8iJ4X9eTVf7IpDLvedyLtOmTP0SL+tvlWrkVdYWaaDrfr7 JgqgQ4vl3l0k+Nsb3aaGl4xD7q4wuvhYidxEDMAdAwcecG5jlUh55DMOpOU+4366 TVTjTwFhG5eIQLIis9LSiF/xH/er9qY8IhGhotmSErftF/cv80kmt2EOMX20LdqT 25CGmbh6XbsYqtIJp686AofYXzLSH0cCGYoO46xaCRFAPK23B89v5EGYrK/LA5jd ulYrIWuyK7m4ynQLLYprps4/E4Z9NTRbxgFPBuYuyPA6kzrSaq5pe08HsmXvzBll bw/HsJox/SLLk/5XsbCqxJuhsQH63KaeVal7Sk13ucdhwpg6i0xg55nE3IiB7vBT hpSNds34PkVlLo/uSfLyh5R3+UarRW6HQwkK1MKFxIzYuAhf/JXc2JQ+2L7sbNHA tt1sdgVS2+40xsclMMI0KZYihvQmykLrFlGgJzBIr9LgqPK40gp4SmA/QhQHM8+o MqLfmRnh9GYlSvnk4b6fkzPdGDzv2x3HgjDqicSUp4aZq6dkDn6sEt4KAUb/1sd/ hku8nD7OlFH4DCZXqQ3lRTztbS1iUX7TXz8FBOqMTKIfilS7yjUmr/E//5kaO2g0 qFsgQrnWftsVNAclG285PtLU5cqjP5uOEaZpJSjNvCR9zNhvM+0= =Y6nt -END PGP SIGNATURE End Message ---
Processed: limit source to node-browser-pack, tagging 979942
Processing commands for cont...@bugs.debian.org: > limit source node-browser-pack Limiting to bugs with field 'source' containing at least one of 'node-browser-pack' Limit currently set to 'source':'node-browser-pack' > tags 979942 + pending Bug #979942 [node-browser-pack] node-browser-pack: node-uglify is deprecated in favor of uglifyjs Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 979942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979942: [Pkg-javascript-devel] Bug#979942: Bug#979942: embedding dead code is no fix to bug for removing that same dead code
Hi, Fixed it was a little bit hard to test options of compression one by one but it work now. Le mar. 12 janv. 2021 à 17:48, Xavier a écrit : > > Control: tags -1 reopen > Control: severity -1 serious > > Le 12/01/2021 à 18:17, Jonas Smedegaard a écrit : > > Quoting Debian FTP Masters (2021-01-12 18:06:40) > >> node-browser-pack (6.1.0+ds-7) unstable; urgency=medium > >> . > >>* Team upload > >>* Bump debhelper compatibility level to 13 > >>* Declare compliance with policy 4.5.1 > >>* Use dh-sequence-nodejs > >>* Remove dependency to node-uglify but embed node-uglify in > >> build_modules > >> else build file is wrong (Closes: #979942) > > > > Do I read the above correctly that node-browser-pack "fixes" node-uglify > > going away by embedding it, hidden? > > > > I disagree that that is a fix. > > OK, but I didn't succeed to fix that, let's reopen, upgrade severity and > wait for someone else to fix it > > -- > Pkg-javascript-devel mailing list > pkg-javascript-de...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Bug#980007: tcmu: CVE-2020-28374
Source: tcmu Version: 1.5.2-5 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 tcmu. CVE-2020-28374[0]: | Linux SCSI target (LIO) unrestricted copy offload A patch was provided in [1] but at time of writing it does not apper to be yet in the upstream repository. Further information in [2]. 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-2020-28374 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28374 [1] https://bugzilla.suse.com/show_bug.cgi?id=1180676 [2] https://www.openwall.com/lists/oss-security/2021/01/12/12 Regards, Salvatore
Bug#979843: marked as done (python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png')
Your message dated Tue, 12 Jan 2021 21:12:49 +0100 with message-id and subject line Re: Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png' has caused the Debian Bug report #979843, regarding python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django Version: 2:2.2.17-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent in testing the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django/9501583/log.gz == FAIL: test_attach_file (mail.tests.MailTests) Test attaching a file against different mimetypes and make sure that -- Traceback (most recent call last): File "/usr/lib/python3.9/unittest/case.py", line 59, in testPartExecutor yield File "/usr/lib/python3.9/unittest/case.py", line 593, in run self._callTestMethod(testMethod) File "/usr/lib/python3.9/unittest/case.py", line 550, in _callTestMethod method() File "/tmp/autopkgtest-lxc.pw5bm44p/downtmp/autopkgtest_tmp/tests/mail/tests.py", line 472, in test_attach_file self.assertEqual(mimetypes.guess_type(basename)[0], real_mimetype) File "/usr/lib/python3.9/unittest/case.py", line 831, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.9/unittest/case.py", line 1211, in assertMultiLineEqual self.fail(self._formatMessage(msg, standardMsg)) File "/usr/lib/python3.9/unittest/case.py", line 670, in fail raise self.failureException(msg) AssertionError: 'image/vnd.mozilla.apng' != 'image/png' - image/vnd.mozilla.apng + image/png OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Arg, sorry, I missed the follow up somehow. Mea culpa Paul On 12-01-2021 21:03, Paul Gevers wrote: > Control: reopen -1 > > Hi Chris, > > On 12-01-2021 13:57, Chris Lamb wrote: >> This appears to be returning the correct result. Has another mimetype- >> related package been updated recently? I can't seem to locate one. > > Did you see > https://lists.debian.org/msgid-search/20210108232226.gb23...@bubu.plessy.net > > And, please don't close the bug until the regression in testing is > really solved. https://ci.debian.net/packages/p/python-django/ shows > your package fails it's autopkgtest since a couple of days on all > architectures it got tested. > > Paul > OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Processed: Re: Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png'
Processing control commands:
> reopen -1
Bug #979843 {Done: "Chris Lamb" } [src:python-django]
python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' !=
'image/png'
Bug reopened
Ignoring request to alter fixed versions of bug #979843 to the same values
previously set
--
979843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png'
Control: reopen -1 Hi Chris, On 12-01-2021 13:57, Chris Lamb wrote: > This appears to be returning the correct result. Has another mimetype- > related package been updated recently? I can't seem to locate one. Did you see https://lists.debian.org/msgid-search/20210108232226.gb23...@bubu.plessy.net And, please don't close the bug until the regression in testing is really solved. https://ci.debian.net/packages/p/python-django/ shows your package fails it's autopkgtest since a couple of days on all architectures it got tested. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#979733: marked as done (teg: FTBFS on several architectures)
Your message dated Tue, 12 Jan 2021 19:18:38 + with message-id and subject line Bug#979733: fixed in teg 0.12.0-2 has caused the Debian Bug report #979733, regarding teg: FTBFS on several architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: teg Version: 0.12.0-1 Severity: serious teg 0.12.0-1 FTBFS on several architectures. We are aware of the problem which has been reported upstream. https://github.com/wfx/teg/issues/25 --- End Message --- --- Begin Message --- Source: teg Source-Version: 0.12.0-2 Done: Reiner Herrmann We believe that the bug you reported is fixed in the latest version of teg, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated teg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 19:23:07 +0100 Source: teg Architecture: source Version: 0.12.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Reiner Herrmann Closes: 979733 Changes: teg (0.12.0-2) unstable; urgency=medium . * Team upload. * Fix FTBFS due to unittest failures on some architectures. (Closes: #979733) Checksums-Sha1: d90f3439481dc2d8b5196b98690f95718ced7586 2108 teg_0.12.0-2.dsc b05f64ec88c33ef1c1ef01dfc291583351f4a402 8344 teg_0.12.0-2.debian.tar.xz cee657dc9de352122ecefbe7c64c4f8fba4070c6 14612 teg_0.12.0-2_amd64.buildinfo Checksums-Sha256: babfac276cd96f8cb940cfc07cc2795fd969786d43bc1829c61a6de196cc6a3c 2108 teg_0.12.0-2.dsc 651f99a02d5577e05cd6bf359727e9476133d0fabf48e1e2475489224ca39ce8 8344 teg_0.12.0-2.debian.tar.xz b17363fd6ae918af2bb7106b6f419d98df913a10d24c304a11f560e95c8fbfcc 14612 teg_0.12.0-2_amd64.buildinfo Files: f3043aeb423038f6a35d1cd59e8f8b00 2108 games optional teg_0.12.0-2.dsc 84dc21aa43b270c5ba9e3a92fcb9e178 8344 games optional teg_0.12.0-2.debian.tar.xz 6b7a62dadc4663f8e5e08034e87967c9 14612 games optional teg_0.12.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl/97+VfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkAAkP/0Gj/Xu9hivfpHhWg2Qsw9+KziMuVciy8lnz lDU3xLD+fHeegkzOYRQXRvkM1qvznR/sPN8p8kKGmRjQTNlkKZkhX7nXFkVkNzVj ZdXUz/vbUMPnOiQ2Z8BwSAR0pVAXAOirJSpCy5mrNmwiMn3P2hMB7FgG09s9i96Y bcuhjxINAMMkTfCI//IKt/utgBmzmmkbd6MZ0ROEvkum/rGw5r1hWW8+KnodLQ0I ta6/y9Gm5YBbYy0Ksj5JQNr7s31yK7HwHnBrUwTM2tqkT8YzcFwnGye80zuU3Xdt A2wwmqZE6QSbeB3eMOFaGJEQnWFFI4BJdMJZ7hPPf11zC6THAaTSQKI4FHK8DrJ0 1tbbIcpSU0s+NbM1y8tjQvdXHfFWtmD1sp5MbxkUZGxfcO0xL0IYcpu24uLZxPd+ lbYl8z2HvwR0UbkfQXeSdkrg+TwwMRbRZSSatM7XMXMVHGL++EWcAaBMUEWnBhFU o3Pw8/5FtcGUrmIqWkYrL9rWtviq2hkqDp6Qfrt0fnz16S7jBF24Xd2gAYnHejOK dPhedWDPgzzyyjSWrC744faZJt53BVIAWpIKdwMg9zfSgfyQJrTn3E73iEestmp/ dT6xcgEZQg4nkNu75L+erV+Ug571aUougdpkifjPEvH8YIOHPJu2sQk3bBTEfMyV H0bK1fxz =CoZl -END PGP SIGNATURE End Message ---
Bug#979609:
I had been testing little more and I can see the same problem with other packages (syndie and stegosuite) which are using libswt-cairo-gtk-4-jni. So, all the three packages using libswt-cairo-gtk-4-jni triggers the segfault in ppc64el. -- Regards Sudip
Bug#979246: src:fonts-ddc-uchen: invalid maintainer address
Hi Sruthi, On Mon, 04 Jan 2021 17:52:01 +0100 Ansgar wrote: > Source: fonts-ddc-uchen > Version: 1.0-1 > Severity: serious > X-Debbugs-Cc: fonts-ddc-uchen > > The maintainer address is invalid, see below. > > Ansgar > > Start of forwarded message > From: Mail Delivery System > Subject: Mail delivery failed: returning message to sender > Date: Mon, 04 Jan 2021 14:33:44 + I'm Cc'ing you manually on this bug since you are the maintainer but the email is incorrect (s...@openmailbox.org). Let me know if you don't have time to attend to it, I'll do an NMU with your address fixed. Note: this also affects ruby-fog-cloudatcost Best, -- Baptiste Beauplat - lyknode OpenPGP_signature Description: OpenPGP digital signature
Bug#979717: seconded!
seconded! maybe even integrate its stuff into vrms? and the same for flatpak?
Processed: reopening 979942
Processing commands for cont...@bugs.debian.org:
> reopen 979942
Bug #979942 {Done: Xavier Guimard } [node-browser-pack]
node-browser-pack: node-uglify is deprecated in favor of uglifyjs
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-browser-pack/6.1.0+ds-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979184: marked as done (rust-lazycell: newly introduced binary packages uninstallable.)
Your message dated Tue, 12 Jan 2021 17:50:58 + with message-id and subject line Bug#979184: fixed in rust-lazycell 1.3.0-3 has caused the Debian Bug report #979184, regarding rust-lazycell: newly introduced binary packages uninstallable. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-lazycell Version: 1.3.0-1 Severity: serious The upload of rust-lazycell 1.3.0-1 introduced three new binary packages, two of which are currently uninstallable. This is preventing the package from migrating to testing which is annoying the release team (see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977583 ) I believe that the "nightly-testing" and "clippy" features should simply be dropped, both of them appear to me to be related to linting the package with clippy rather than actual runtime features. If noone objects I will make an upload dropping these features in a week or so. --- End Message --- --- Begin Message --- Source: rust-lazycell Source-Version: 1.3.0-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-lazycell, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-lazycell package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 17:23:12 + Source: rust-lazycell Architecture: source Version: 1.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 979184 Changes: rust-lazycell (1.3.0-3) unstable; urgency=medium . * Team upload. * Package lazycell 1.3.0 from crates.io using debcargo 2.4.3 * Drop uninstallable clippy and nightly-testing features. (Closes: 979184) Checksums-Sha1: b0c29cdaa5e69ac640aa7db33025b1030e4d4308 2257 rust-lazycell_1.3.0-3.dsc 199b0d88d54660f284bdf1547f426ad764310640 3256 rust-lazycell_1.3.0-3.debian.tar.xz 91dba0242ea0d4221faed6a17762e619909228dc 6682 rust-lazycell_1.3.0-3_source.buildinfo Checksums-Sha256: 34e781c12ea2e4427d206228043f8b8f9316afb6ad36f356c501a9482ad49aa2 2257 rust-lazycell_1.3.0-3.dsc 918eb5264111bf5a18611e40e9476240e08f966efad80bb057b529b232c3d844 3256 rust-lazycell_1.3.0-3.debian.tar.xz 8bd1575c98405e7872b070c3cad11b229a706b85a404c3dc04b621a7e1c5ad5a 6682 rust-lazycell_1.3.0-3_source.buildinfo Files: 7646b33aeef5e36503ee0be82352ddae 2257 rust optional rust-lazycell_1.3.0-3.dsc eb6c03cd7e751e5c50ad6bfa505c8602 3256 rust optional rust-lazycell_1.3.0-3.debian.tar.xz d0e5b3b266e4e8661e6223e12bc42471 6682 rust optional rust-lazycell_1.3.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl/920IUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuhnA/+PpBsKJ/VhJrJZywLNzQGwIB33WZb 2/ewKK32w71K9hzED2VoHMi2udUgD56yBDA5ZqRnLx3Pc1VMUIcfDMpPP/JAed8p XOE8slsoYyabzyHIhIrAHkfgNaAONp7T6m4LSJOXjKZ5vRZ2KZfd/+43tFRcAfpq stwtfr2fOUX3Zw1tJdqT1HVl2kt4QEYM0BXYOXBZr9/DVc4aD9nkXWkBFTQzhhxD x/vsADAgHOmIYDk7WS1a/O82RF8mMLS2E6cll+GirTV9phJCEHAeGYoOtxFI5Zrf H8Yu0qfBWhJBN3oDPgGBpZCXo20shU+CKgzRSCzW7NBlqH4pAJmdu41MDpnNfOCl V8FXfzFTGKZXK7xcTAx+UETbzLAluaYcVWddH89lQ80757e6oTnUSxZBeG91vlpL 2GcA2+9BPhrskHsHDidwnwTbSXCXHC0Rrn76MpG4itWqY+oQr1/tPcBvZ2iG+D8z fIe24nXhQKa4EY6LqE7I38b1Fuv6isSOTB5MZ2xc8SXdlj7RQrVm6zfgWU18m8Hq O9BF6YofhyOBzuu8kNYHa3Md7FPcaDSpek920PaSIRe/A0VErR1fKF86RVdcQJkj K3yU+oeXrM8UYfHnai6MZzQLOyjccm7evQXYwVRgjIR8Yiu3kBYuQDuwcQkkmvKp RrzY8DIgGblh9Xk= =i3+q -END PGP SIGNATURE End Message ---
Processed (with 1 error): Re: [Pkg-javascript-devel] Bug#979942: embedding dead code is no fix to bug for removing that same dead code
Processing control commands:
> tags -1 reopen
Unknown tag/s: reopen.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye
bullseye-ignore bookworm bookworm-ignore.
> severity -1 serious
Bug #979942 {Done: Xavier Guimard } [node-browser-pack]
node-browser-pack: node-uglify is deprecated in favor of uglifyjs
Severity set to 'serious' from 'important'
--
979942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979843: marked as done (python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png')
Your message dated Tue, 12 Jan 2021 16:59:44 + with message-id <6d0a213e-53d2-4b5b-aeec-3ab76d0f9...@www.fastmail.com> and subject line Re: Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png' has caused the Debian Bug report #979843, regarding python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django Version: 2:2.2.17-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent in testing the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django/9501583/log.gz == FAIL: test_attach_file (mail.tests.MailTests) Test attaching a file against different mimetypes and make sure that -- Traceback (most recent call last): File "/usr/lib/python3.9/unittest/case.py", line 59, in testPartExecutor yield File "/usr/lib/python3.9/unittest/case.py", line 593, in run self._callTestMethod(testMethod) File "/usr/lib/python3.9/unittest/case.py", line 550, in _callTestMethod method() File "/tmp/autopkgtest-lxc.pw5bm44p/downtmp/autopkgtest_tmp/tests/mail/tests.py", line 472, in test_attach_file self.assertEqual(mimetypes.guess_type(basename)[0], real_mimetype) File "/usr/lib/python3.9/unittest/case.py", line 831, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.9/unittest/case.py", line 1211, in assertMultiLineEqual self.fail(self._formatMessage(msg, standardMsg)) File "/usr/lib/python3.9/unittest/case.py", line 670, in fail raise self.failureException(msg) AssertionError: 'image/vnd.mozilla.apng' != 'image/png' - image/vnd.mozilla.apng + image/png OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi Sandro, > > This appears to be returning the correct result. Has another mimetype- > > related package been updated recently? I can't seem to locate one. > > yup, it was fixed in > https://packages.qa.debian.org/m/media-types/news/20210107T225251Z.html Ah, thanks for the reference. Closing this bug... Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk ` End Message ---
Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png'
Hi Sandro, > > This appears to be returning the correct result. Has another mimetype- > > related package been updated recently? I can't seem to locate one. > > yup, it was fixed in > https://packages.qa.debian.org/m/media-types/news/20210107T225251Z.html Ah, thanks for the reference. Closing this bug... Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Processed: reassign 975198 to log4cplus, fixed 975198 in log4cplus/2.0.5-3, unblock 975198 with 975665 ...
Processing commands for cont...@bugs.debian.org:
> reassign 975198 log4cplus
Bug #975198 {Done: Tobias Frost } [src:slic3r-prusa]
slic3r-prusa: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4
test ARGS=-V ARGS\+=-j4 returned exit code 2
Bug reassigned from package 'src:slic3r-prusa' to 'log4cplus'.
No longer marked as found in versions slic3r-prusa/2.2.0+dfsg1-3.
Ignoring request to alter fixed versions of bug #975198 to the same values
previously set
> fixed 975198 log4cplus/2.0.5-3
Bug #975198 {Done: Tobias Frost } [log4cplus] slic3r-prusa:
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS=-V
ARGS\+=-j4 returned exit code 2
Marked as fixed in versions log4cplus/2.0.5-3.
> unblock 975198 with 975665
Bug #975198 {Done: Tobias Frost } [log4cplus] slic3r-prusa:
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS=-V
ARGS\+=-j4 returned exit code 2
975198 was blocked by: 978617 975665
975198 was not blocking any bugs.
Removed blocking bug(s) of 975198: 975665
> forcemerge 978617 978617
Bug #978617 {Done: Tobias Frost } [liblog4cplus-2.0.5]
liblog4cplus-2.0.5: liblog4cplus exports symbols from unrelated header-only
library (Catch)
Merged 978617
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
975198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975198
978617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#975665: slic3r-prusa: FTBFS against boost_1.74
Package: slic3r-prusa Followup-For: Bug #975665 Control: tags -1 fixed-upstream Control: forwarded -1 https://github.com/prusa3d/PrusaSlicer/issues/4264 Well, OpenSuse released the new upstream version, which fixed the boost problem, and the link above stopped working afterwards. Updating meta-data to point to the prusa PR. Cheers, tobi
Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png'
> This appears to be returning the correct result. Has another mimetype- > related package been updated recently? I can't seem to locate one. yup, it was fixed in https://packages.qa.debian.org/m/media-types/news/20210107T225251Z.html -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Processed: Re: slic3r-prusa: FTBFS against boost_1.74
Processing control commands: > tags -1 fixed-upstream Bug #975665 [slic3r-prusa] slic3r-prusa: FTBFS against boost_1.74 Added tag(s) fixed-upstream. > forwarded -1 https://github.com/prusa3d/PrusaSlicer/issues/4264 Bug #975665 [slic3r-prusa] slic3r-prusa: FTBFS against boost_1.74 Set Bug forwarded-to-address to 'https://github.com/prusa3d/PrusaSlicer/issues/4264'. -- 975665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975198: marked as done (slic3r-prusa: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS=-V ARGS\+=-j4 returned exit code 2)
Your message dated Tue, 12 Jan 2021 17:42:50 +0100 with message-id and subject line Re: slic3r-prusa: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS=-V ARGS\+=-j4 returned exit code 2 has caused the Debian Bug report #975198, regarding slic3r-prusa: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS=-V ARGS\+=-j4 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 975198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slic3r-prusa Version: 2.2.0+dfsg1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process -V -j4 > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: libnest2d_tests > > 1: Test command: > /<>/obj-x86_64-linux-gnu/tests/libnest2d/libnest2d_tests > 1: Test timeout computed to be: 1000 > test 2 > Start 2: libslic3r_tests > > 2: Test command: > /<>/obj-x86_64-linux-gnu/tests/libslic3r/libslic3r_tests > 2: Test timeout computed to be: 1000 > test 3 > Start 3: slic3rutils_tests > > 3: Test command: > /<>/obj-x86_64-linux-gnu/tests/slic3rutils/slic3rutils_tests " > exclude:[NotWorking]" > 3: Test timeout computed to be: 1000 > test 4 > Start 4: fff_print_tests > > 4: Test command: > /<>/obj-x86_64-linux-gnu/tests/fff_print/fff_print_tests > 4: Test timeout computed to be: 1000 > 1: Testing Angles > 1: Passed in 0.000842 [seconds] > 1: > 1: Testing ItemCreationAndDestruction > 1: Passed in 8e-06 [seconds] > 1: > 1: Testing boundingCircle > 1: Passed in 0.00274 [seconds] > 1: > 1: Testing Distance > 1: Passed in 9e-06 [seconds] > 1: > 1: Testing Area > 1: Passed in 1e-05 [seconds] > 1: > 1: Testing IsPointInsidePolygon > 1: Passed in 1.4e-05 [seconds] > 1: > 1: Testing LeftAndDownPolygon > 1: Passed in 0.000452 [seconds] > 1: > 1: Testing ArrangeRectanglesTight > 1: Passed in 0.001862 [seconds] > 1: > 1: Testing ArrangeRectanglesLoose > 1: Passed in 0.00253 [seconds] > 1: > 1: Testing BottomLeftStressTest > 1: Passed in 0.000801 [seconds] > 1: > 1: Testing convexHull > 1: Passed in 8e-06 [seconds] > 1: > 1: Testing PrusaPartsShouldFitIntoTwoBins > 2: terminate called after throwing an instance of 'std::bad_alloc' > 2: what(): std::bad_alloc > 1/5 Test #2: libslic3r_tests ..Child aborted***Exception: > 0.02 sec > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > > test 5 > Start 5: sla_print_tests > > 5: Test command: > /<>/obj-x86_64-linux-gnu/tests/sla_print/sla_print_tests > 5: Test timeout computed to be: 1000 > 5: terminate called after throwing an instance of 'std::bad_alloc' > 5: what(): std::bad_alloc > 2/5 Test #5: sla_print_tests ..Child aborted***Exception: > 0.01 sec > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > > 4: Testing Scenario: init_print functionality > 4: Given: A default config > 4: When: init_print is called with a single mesh. > 4: Then: One mesh/printobject is in the resulting Print object. > 4: Given: A default config > 4: When: init_print is called with a single mesh. > 4: Then: print.process() doesn't crash. > 4: Given: A default config > 4: When: init_print is called with a single mesh. > 4: Then: Export gcode functions outputs text. > 3: Filters: exclude:[NotWorking] > 3: No test cases matched 'exclude:[NotWorking]' > 3: > === > 3: No tests ran > 3: > 4: Passed in 0.32673 [seconds] > 4: > 4: Testing Scenario: ExtrusionEntityCollection: Polygon flattening > 4: Given: A Extrusion Entity Collection with a child that has one child > that is marked as no-sort > 4: When: The EEC is flattened with default options
Processed: py2removal bugs severity updates - 2021-01-12 16:30:41.384261+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # not all bin pkgs are leaf for src:pam-python, lower severity > severity 937234 normal Bug #937234 [src:pam-python] pam-python: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > # not all bin pkgs are leaf for src:thunarx-python, lower severity > severity 938665 normal Bug #938665 [src:thunarx-python] thunarx-python: Python2 removal in sid/bullseye Severity set to 'normal' from 'serious' > # python-jinja2 is a module and has 0 external rdeps or not in testing > severity 936765 serious Bug #936765 [src:jinja2] jinja2: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # mklibs-copy is an application and has 0 external rdeps or not in testing > severity 937054 serious Bug #937054 [src:mklibs] mklibs: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936765 937054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937054 937234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937234 938665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 979983 is forwarded to https://github.com/MolSSI/QCElemental/issues/83#issuecomment-757475240
Processing commands for cont...@bugs.debian.org: > forwarded 979983 > https://github.com/MolSSI/QCElemental/issues/83#issuecomment-757475240 Bug #979983 [src:qcelemental] qcelemental downloads from the internet during the build Set Bug forwarded-to-address to 'https://github.com/MolSSI/QCElemental/issues/83#issuecomment-757475240'. > thanks Stopping processing here. Please contact me if you need assistance. -- 979983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 886499
Processing commands for cont...@bugs.debian.org: > # this is really stretch only > close 886499 3.4.3-1 Bug #886499 [kodi-pvr-hdhomerun] kodi-pvr-hdhomerun: Incompatible with Kodi 2:17.1+dfsg1-3 from Stretch Marked as fixed in versions kodi-pvr-hdhomerun/3.4.3-1. Bug #886499 [kodi-pvr-hdhomerun] kodi-pvr-hdhomerun: Incompatible with Kodi 2:17.1+dfsg1-3 from Stretch Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 886499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979984: breaks on check with "NameError: name 'get_binary_stdin' is not defined"
Package: pyzor Version: 1:1.0.0-5 Severity: grave Hi! The fix for https://bugs.debian.org/923077 seems to have introduced a serious regressing, causing pyzor to stop working on check: ~$ pyzor check < testmail Traceback (most recent call last): File "/usr/bin/pyzor", line 411, in main() File "/usr/bin/pyzor", line 152, in main if not dispatch(client, servers, config): File "/usr/bin/pyzor", line 240, in check for digested in get_input_handler(style): File "/usr/bin/pyzor", line 177, in _get_input_msg msg = email.message_from_bytes(get_binary_stdin().read()) NameError: name 'get_binary_stdin' is not defined The fix from https://github.com/SpamExperts/pyzor/commit/6332a429ed415187599ecce7d8a169ee19f0bbe5 is not enough, as the code from https://github.com/SpamExperts/pyzor/commit/67b471dd168db9468548aef3ffadca9554164ac0 implementing this function is needed for it to work. Gentoo carries the same fix at https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=300f46c1c52cc79238e88dba28241a6e78525966 Grüße, Sven. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pyzor depends on: ii python3 3.9.1-1 pyzor recommends no packages. Versions of packages pyzor suggests: pn pyzor-doc -- debconf-show failed
Bug#979983: [Debichem-devel] Bug#979983: qcelemental downloads from the internet during the build
Hi,
On Tue, Jan 12, 2021 at 05:31:51PM +0200, Adrian Bunk wrote:
> matchobj =
>
> def process_pubchem(matchobj):
> pubsearch = matchobj.group("pubsearch")
>
> # search pubchem for the provided string
> try:
> results = pubchem.get_pubchem_results(pubsearch)
> except Exception as e:
> > raise ValidationError(e.message)
> E qcelemental.exceptions.ValidationError: Input Error:
> PubchemError
> E
> E received when trying to open
> E
> https://pubchem.ncbi.nlm.nih.gov/rest/pug/compound/cid/223/property/IUPACName,MolecularFormula,Charge/JSON
> E Check your internet connection, and the above URL, and try
> again.
>
> qcelemental/molparse/from_string.py:309: ValidationError
I noticed, and I mentioned it in
https://github.com/MolSSI/QCElemental/issues/83#issuecomment-757475240
but no reply from upstream so far.
Michael
Bug#979983: qcelemental downloads from the internet during the build
Source: qcelemental
Version: 0.17.0+dfsg-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=qcelemental=all=0.17.0%2Bdfsg-2=1610282048=0
...
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dh_auto_test
I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build; python3.9
-m pytest
= test session starts ==
platform linux -- Python 3.9.1, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /<>
plugins: cov-2.10.1
collected 998 items
qcelemental/molutil/test_molutil.py s..sss..sss.ss...s.. [ 3%]
.[ 3%]
qcelemental/tests/test_constants.py [ 7%]
x[ 8%]
qcelemental/tests/test_covalentradii.py .[ 10%]
qcelemental/tests/test_datum.py .[ 12%]
qcelemental/tests/test_importing.py .. [ 14%]
qcelemental/tests/test_info.py [ 18%]
qcelemental/tests/test_model_general.py [ 19%]
qcelemental/tests/test_model_results.py [ 22%]
.[ 23%]
qcelemental/tests/test_molecule.py .sss. [ 26%]
...s... [ 28%]
qcelemental/tests/test_molparse_align_chiral.py ss [ 29%]
qcelemental/tests/test_molparse_from_schema.py [ 30%]
qcelemental/tests/test_molparse_from_string.py . [ 33%]
[ 40%]
[ 41%]
qcelemental/tests/test_molparse_parse_nucleus_label.py . [ 42%]
qcelemental/tests/test_molparse_pubchem.py FFF...FFF [ 43%]
qcelemental/tests/test_molparse_reconcile_nucleus.py ... [ 45%]
[ 48%]
qcelemental/tests/test_molparse_to_schema.py .. [ 49%]
qcelemental/tests/test_molparse_to_string.py ... [ 52%]
[ 52%]
qcelemental/tests/test_molparse_validate_and_fill_chgmult.py ... [ 54%]
[ 59%]
qcelemental/tests/test_periodictable.py [ 62%]
[ 70%]
x[ 71%]
qcelemental/tests/test_testing.py .. [ 75%]
.. [ 77%]
qcelemental/tests/test_units.py [ 81%]
[ 88%]
... [ 89%]
qcelemental/tests/test_utils.py [ 93%]
..sss[ 96%]
qcelemental/tests/test_vanderwaalsradii.py [ 99%]
qcelemental/util/test_gph_uno_bipartite.py [ 99%]
qcelemental/util/test_scipy_hungarian.py .. [100%]
=== FAILURES ===
...
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
matchobj =
def process_pubchem(matchobj):
pubsearch = matchobj.group("pubsearch")
# search pubchem for the provided string
try:
results = pubchem.get_pubchem_results(pubsearch)
except Exception as e:
> raise ValidationError(e.message)
E qcelemental.exceptions.ValidationError: Input Error:
PubchemError
E
E received when trying to open
E
https://pubchem.ncbi.nlm.nih.gov/rest/pug/compound/cid/223/property/IUPACName,MolecularFormula,Charge/JSON
E Check your internet connection, and the above URL, and try
again.
qcelemental/molparse/from_string.py:309: ValidationError
- Captured stdout call -
Searching PubChem database for CID 223
=== warnings summary ===
.pybuild/cpython3_3.9/build/qcelemental/tests/test_molparse_from_string.py: 10
warnings
/usr/lib/python3/dist-packages/numpy/core/_asarray.py:83:
Processed: notfixed 930931 in 9.4.2-1~bpo9+1, notfixed 979063 in 0.3.1+dfsg-3, notfixed 979063 in 0.3.1+dfsg-3.1
Processing commands for cont...@bugs.debian.org:
> # unconfuse the bts
> notfixed 930931 9.4.2-1~bpo9+1
Bug #930931 {Done: Carsten Leonhardt } [bacula-sd]
/usr/sbin/btape: btape crashes on "fill" test with segmentation fault
No longer marked as fixed in versions 9.4.2-1~bpo9+1.
> # no longer useless, civicrm is back
> notfixed 979063 0.3.1+dfsg-3
Bug #979063 {Done: Dmitry Smirnov } [php-font-lib]
php-font-lib: Useless in Debian
No longer marked as fixed in versions php-font-lib/0.3.1+dfsg-3.
> notfixed 979063 0.3.1+dfsg-3.1
Bug #979063 {Done: Dmitry Smirnov } [php-font-lib]
php-font-lib: Useless in Debian
No longer marked as fixed in versions php-font-lib/0.3.1+dfsg-3.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
930931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930931
979063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#978192: marked as done (xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’?)
Your message dated Tue, 12 Jan 2021 15:07:11 + with message-id and subject line Bug#978192: fixed in nvidia-settings 460.32.03-1 has caused the Debian Bug report #978192, regarding xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xfce4-sensors-plugin Version: 1.3.0-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I../include -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG > -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -pthread > -I/usr/include/xfce4/libxfce4ui-2 -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/xfce4 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/xfce4 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include > -I/usr/include/NVCtrl -pthread -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o libxfce4sensors_la-nvidia.lo `test -f > 'nvidia.c' || echo './'`nvidia.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wdate-time > -D_FORTIFY_SOURCE=2 -DNDEBUG -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" > -pthread -I/usr/include/xfce4/libxfce4ui-2 -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/xfce4 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/xfce4 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include > -I/usr/include/NVCtrl -pthread -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid >
Bug#976579: marked as done (libgsecuredelete: FTBFS: gsecuredelete.vapi:8.3-8.25: error: `Gsd.Intl' already contains a definition for `init')
Your message dated Tue, 12 Jan 2021 15:06:42 +
with message-id
and subject line Bug#976579: fixed in libgsecuredelete 0.3-3
has caused the Debian Bug report #976579,
regarding libgsecuredelete: FTBFS: gsecuredelete.vapi:8.3-8.25: error:
`Gsd.Intl' already contains a definition for `init'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
976579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgsecuredelete
Version: 0.3-2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> make[4]: Entering directory '/<>/gsecuredelete'
> rm -f test_vala.stamp && echo stamp > test_vala.stamp-t
> /usr/bin/valac --pkg=glib-2.0 --pkg=posix --vapidir=. --pkg=gsecuredelete -C
> main.vala gsecuredelete.vapi
> gsecuredelete.vapi:23.3-23.23: warning: Creation method of abstract class
> cannot be public.
> public AsyncOperation ();
> ^
> gsecuredelete.vapi:79.3-79.30: warning: Creation method of abstract class
> cannot be public.
> public SecureDeleteOperation ();
>
> gsecuredelete.vapi:100.3-100.26: warning: Creation method of abstract class
> cannot be public.
> public ZeroableOperation ();
>
> gsecuredelete.vapi:23.3-23.23: warning: Creation method of abstract class
> cannot be public.
> public AsyncOperation ();
> ^
> gsecuredelete.vapi:79.3-79.30: warning: Creation method of abstract class
> cannot be public.
> public SecureDeleteOperation ();
>
> gsecuredelete.vapi:100.3-100.26: warning: Creation method of abstract class
> cannot be public.
> public ZeroableOperation ();
>
> gsecuredelete.vapi:8.3-8.25: error: `Gsd.Intl' already contains a definition
> for `init'
> public static void init ();
> ^^^
> gsecuredelete.vapi:8.3-8.25: note: previous definition of `init' was here
> public static void init ();
> ^^^
> gsecuredelete.vapi:11.2-11.51: error: `Gsd' already contains a definition for
> `AsyncOperation'
> public abstract class AsyncOperation : GLib.Object {
> ^^
> gsecuredelete.vapi:11.2-11.51: note: previous definition of `AsyncOperation'
> was here
> public abstract class AsyncOperation : GLib.Object {
> ^^
> gsecuredelete.vapi:42.2-42.53: error: `Gsd' already contains a definition for
> `DeleteOperation'
> public class DeleteOperation : Gsd.ZeroableOperation {
>
> gsecuredelete.vapi:42.2-42.53: note: previous definition of `DeleteOperation'
> was here
> public class DeleteOperation : Gsd.ZeroableOperation {
>
> gsecuredelete.vapi:53.2-53.51: error: `Gsd' already contains a definition for
> `FillOperation'
> public class FillOperation : Gsd.ZeroableOperation {
> ^^
> gsecuredelete.vapi:53.2-53.51: note: previous definition of `FillOperation'
> was here
> public class FillOperation : Gsd.ZeroableOperation {
> ^^
> gsecuredelete.vapi:69.2-69.54: error: `Gsd' already contains a definition for
> `MemOperation'
> public class MemOperation : Gsd.SecureDeleteOperation {
> ^
> gsecuredelete.vapi:69.2-69.54: note: previous definition of `MemOperation'
> was here
> public class MemOperation : Gsd.SecureDeleteOperation {
> ^
> gsecuredelete.vapi:73.2-73.65: error: `Gsd' already contains a definition for
> `SecureDeleteOperation'
> public abstract class SecureDeleteOperation : Gsd.AsyncOperation {
>
> gsecuredelete.vapi:73.2-73.65: note: previous definition of
> `SecureDeleteOperation' was here
> public abstract class
Bug#957473: marked as done (libreswan: ftbfs with GCC-10)
Your message dated Tue, 12 Jan 2021 14:48:51 + with message-id and subject line Bug#957473: fixed in libreswan 4.1-1 has caused the Debian Bug report #957473, regarding libreswan: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libreswan Version: 3.29-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libreswan_3.29-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] -MF ../../OBJ.linux.amd64/lib/libswan/deltatime.d \ -MP -MMD -MT deltatime.o \ -o ../../OBJ.linux.amd64/lib/libswan/deltatime.o \ -c /<>/lib/libswan/deltatime.c cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -I../../lib/libcrypto -DPFKEYV2 -I. -I/<> -I/usr/include/nss -I/usr/include/nspr -DNSS_IPSEC_PROFILE -I/<>/include -DTimeZoneOffset=timezone -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -Dlinux -DHAVE_UDPFROMTO=1 -DHAVE_IP_PKTINFO=1 -std=gnu99 -g -Werror -Wall -Wextra -Wformat -Wformat-nonliteral -Wformat-security -Wundef -Wmissing-declarations -Wredundant-decls -Wnested-externs -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-all -fno-strict-aliasing -fPIE -DPIE -DNETKEY_SUPPORT -DPFKEY -DUSE_DNSSEC -DDEFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" -DUSE_NIC_OFFLOAD -DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG -DLIBLDAP -DHAVE_NM -DXAUTH_HAVE_PAM -DUSE_3DES -DUSE_AES -DUSE_CAMELLIA -DUSE_CHACHA -DUSE_DH2 -DUSE_DH31 -DUSE_MD5 -DUSE_SERPENT -DUSE_SHA1 -DUSE_SHA2 -DUSE_TWOFISH -DUSE_XCBC -DDEFAULT_RUNDIR=\"/run/plu to\" -DFIPSPRODUCTCHECK=\"/etc/system-fips\" -DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" -DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" -DIPSEC_EXECDIR=\"/usr/lib/ipsec\" -DIPSEC_SBINDIR=\"/usr/sbin\" -DIPSEC_VARDIR=\"/var\" -DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" -DIPSEC_SECRETS_FILE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DUSE_FORK=1 -DUSE_VFORK=0 -DUSE_DAEMON=0 -DUSE_PTHREAD_SETSCHEDPRIO=1 -DGCC_LINT -DALLOW_MICROSOFT_BAD_PROPOSAL -DHAVE_LIBCAP_NG -I/<>/include -I/usr/include/nss -I/usr/include/nspr -DNSS_IPSEC_PROFILE -pthread -DTimeZoneOffset=timezone -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -Dlinux -DHAVE_UDPFROMTO=1 -DHAVE_IP_PKTINFO=1 -std=gnu99 -g -Werror -Wall -Wextra -Wformat -Wformat-nonliteral -Wformat-security -Wundef -Wmissing-declarations -Wredundant-decls -Wnested-externs -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-all -fno-strict-aliasing -fPIE -DPIE -DNETKEY_SUPPORT -DPFKEY -DUSE_DNSSEC -DD EFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" -DUSE_NIC_OFFLOAD -DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG -DLIBLDAP -DHAVE_NM -DXAUTH_HAVE_PAM -DUSE_3DES -DUSE_AES -DUSE_CAMELLIA -DUSE_CHACHA -DUSE_DH2 -DUSE_DH31 -DUSE_MD5 -DUSE_SERPENT -DUSE_SHA1 -DUSE_SHA2 -DUSE_TWOFISH -DUSE_XCBC -DDEFAULT_RUNDIR=\"/run/pluto\" -DFIPSPRODUCTCHECK=\"/etc/system-fips\" -DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" -DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" -DIPSEC_EXECDIR=\"/usr/lib/ipsec\" -DIPSEC_SBINDIR=\"/usr/sbin\" -DIPSEC_VARDIR=\"/var\" -DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" -DIPSEC_SECRETS_FILE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DUSE_FORK=1
Bug#966017: marked as done (libreswan FTBFS with libselinux 3.1)
Your message dated Tue, 12 Jan 2021 14:48:51 +
with message-id
and subject line Bug#966017: fixed in libreswan 4.1-1
has caused the Debian Bug report #966017,
regarding libreswan FTBFS with libselinux 3.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libreswan
Version: 3.32-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libreswan.html
...
In file included from
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c:17:
/build/1st/libreswan-3.32/programs/pluto/security_selinux.h:23:1: error:
'security_context_t' is deprecated [-Werror=deprecated-declarations]
23 | int within_range(security_context_t sl, security_context_t range);
| ^~~
/build/1st/libreswan-3.32/programs/pluto/security_selinux.h:23:1: error:
'security_context_t' is deprecated [-Werror=deprecated-declarations]
...
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c: In function
'init_avc':
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c:31:2: error:
'avc_init' is deprecated: Use avc_open and selinux_set_callback
[-Werror=deprecated-declarations]
31 | if (avc_init("libreswan", NULL, NULL, NULL, NULL) == 0)
| ^~
...
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c: At top level:
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c:37:1: error:
'security_context_t' is deprecated [-Werror=deprecated-declarations]
37 | int within_range(security_context_t sl, security_context_t range)
| ^~~
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c:37:1: error:
'security_context_t' is deprecated [-Werror=deprecated-declarations]
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c: In function
'within_range':
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c:63:3: error:
'sidput' is deprecated [-Werror=deprecated-declarations]
63 | sidput(slsid);
| ^~
...
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c:75:3: error:
'sidput' is deprecated [-Werror=deprecated-declarations]
75 | sidput(slsid);
| ^~
...
/build/1st/libreswan-3.32/programs/pluto/security_selinux.c:76:3: error:
'sidput' is deprecated [-Werror=deprecated-declarations]
76 | sidput(rangesid);
| ^~
...
--- End Message ---
--- Begin Message ---
Source: libreswan
Source-Version: 4.1-1
Done: Daniel Kahn Gillmor
We believe that the bug you reported is fixed in the latest version of
libreswan, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Kahn Gillmor (supplier of updated libreswan
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 Jan 2021 09:24:42 -0500
Source: libreswan
Architecture: source
Version: 4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor
Changed-By: Daniel Kahn Gillmor
Closes: 957473 966017
Changes:
libreswan (4.1-1) unstable; urgency=medium
.
* New upstream version (Closes: #957473, #966017)
* Standards-Version: bumped to 4.5.1 (no changes needed)
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* refresh patches
* clean up debian/copyright, following upstream cleanup
* indicate that neither of these patches need to be forwarded upstream
* d/rules: track new compilation configuration from upstream
* drop unneeded lintian overrides
* clean up spelling
* avoid shipping accidental backup files
Checksums-Sha1:
db7d55b6eb2929d7d27d847529c11fc885adb881 2035 libreswan_4.1-1.dsc
ae1bbe86a2223aa008f8bf2768e7320c5a7aae9d 3427012 libreswan_4.1.orig.tar.gz
dd718f6ba9e8b74c82750172923005bfb6c4202e 862 libreswan_4.1.orig.tar.gz.asc
e7d395eef56651fdb21aa16acb92055fddb315b7 23032 libreswan_4.1-1.debian.tar.xz
8b02acb6de5d08fcda7197295603b9d1a0aad0ac 10839 libreswan_4.1-1_amd64.buildinfo
Checksums-Sha256:
Bug#964609: marked as done (pyxdg: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13)
Your message dated Tue, 12 Jan 2021 14:35:04 +
with message-id
and subject line Bug#964609: fixed in pyxdg 0.27-1
has caused the Debian Bug report #964609,
regarding pyxdg: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i
python{version} -p 3.8 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
964609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyxdg
Version: 0.26-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tar xJf debian/test-example.tar.xz
> dh_auto_configure
> I: pybuild base:217: python3.8 setup.py config
> running config
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/DesktopEntry.py ->
> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/Mime.py -> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/__init__.py ->
> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/Menu.py -> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/IniFile.py -> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/Exceptions.py ->
> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/IconTheme.py ->
> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/util.py -> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/RecentFiles.py ->
> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/Config.py -> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/MenuEditor.py ->
> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/BaseDirectory.py ->
> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
> copying xdg/Locale.py -> /<>/.pybuild/cpython3_3.8_xdg/build/xdg
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8_xdg/build;
> python3.8 -m nose -v test
> test_load_config_paths (test-basedirectory.BaseDirectoryTest) ... ok
> test_load_first_config (test-basedirectory.BaseDirectoryTest) ... ok
> test_runtime_dir (test-basedirectory.BaseDirectoryTest) ... ok
> test_runtime_dir_notset (test-basedirectory.BaseDirectoryTest) ... ok
> test_save_cache_path (test-basedirectory.BaseDirectoryTest) ... ok
> test_save_config_path (test-basedirectory.BaseDirectoryTest) ... ok
> test_save_data_path (test-basedirectory.BaseDirectoryTest) ... ok
> test_basic (test-desktop.DesktopEntryTest) ... ok
> test_invalid (test-desktop.DesktopEntryTest) ... ok
> test_invalid_unicode (test-desktop.DesktopEntryTest) ... ok
> test_unicode_name (test-desktop.DesktopEntryTest) ... ok
> test_validate (test-desktop.DesktopEntryTest) ... ok
> test_values (test-desktop.DesktopEntryTest) ... ok
> test_write_file (test-desktop.DesktopEntryTest) ... ok
> test_absent (test-desktop.TestTryExec) ... ok
> test_no_TryExec (test-desktop.TestTryExec) ... ok
> test_present (test-desktop.TestTryExec) ... ok
> test_read_icon_data (test-icon.IconDataTest) ... ok
> test_find_icon_exists (test-icon.IconThemeTest) ... ok
> test_find_icon_nonexistant (test-icon.IconThemeTest) ... ok
> test_validate_icon_theme (test-icon.IconThemeTest) ... ok
> test_check_string (test-inifile.IniFileTest) ... ok
> test_modify (test-inifile.IniFileTest) ... ok
> test_value_types (test-inifile.IniFileTest) ... ok
> test_expand_languages (test-locale.LocaleTest) ... ok
> test_rule_from_filename (test-menu-rules.RulesTest) ... ok
> test_rule_from_node (test-menu-rules.RulesTest) ... ERROR
> test_empty_legacy_dirs (test-menu.MenuTest) ... ok
> This was failing on systems which didn't have kde-config installed. ... ok
> test_parse_menu (test-menu.MenuTest) ... ok
> test_unicode_menuentry (test-menu.MenuTest) ... ok
> test_all_matches (test-mime.GlobDBTest) ... ok
> test_build_globdb (test-mime.GlobDBTest) ... ok
> test_first_match (test-mime.GlobDBTest) ... ok
> test_get_extensions (test-mime.GlobDBTest) ... ok
> test_parsing (test-mime.GlobsParsingTest) ... ok
> test_match_data (test-mime.MagicDBTest) ... ok
> test_match_file (test-mime.MagicDBTest) ... ok
> test_match_nested (test-mime.MagicDBTest) ... ok
> test_parsing (test-mime.MagicDBTest) ... ok
> test_by_name (test-mime.MimeTest) ... ok
> test_canonical (test-mime.MimeTest) ... ok
> test_create_mimetype (test-mime.MimeTest) ... ok
> test_get_comment
Bug#968399: marked as done (pyxdg ftbfs, test failure)
Your message dated Tue, 12 Jan 2021 14:35:04 +
with message-id
and subject line Bug#964609: fixed in pyxdg 0.27-1
has caused the Debian Bug report #964609,
regarding pyxdg ftbfs, test failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
964609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyxdg
Version: 0.26-3
Severity: serious
Tags: sid bullseye
seen in unstable, in the build, and in the autopkg tests:
[...]
==
ERROR: test_rule_from_node (test-menu-rules.RulesTest)
--
Traceback (most recent call last):
File
"/packages/tmp/pyxdg-0.26/.pybuild/cpython3_3.8_xdg/build/test/test-menu-rules.py",
line 166, in test_rule_from_node
rule = parser.parse_rule(root)
File "/packages/tmp/pyxdg-0.26/.pybuild/cpython3_3.8_xdg/build/xdg/Menu.py",
line 768, in parse_rule
return Rule(type, tree)
File "/packages/tmp/pyxdg-0.26/.pybuild/cpython3_3.8_xdg/build/xdg/Menu.py",
line 421, in __init__
self.code = compile(self.expression, '', 'eval')
ValueError: Name node can't be used with 'False' constant
--
Ran 55 tests in 2.178s
FAILED (errors=1)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd
/packages/tmp/pyxdg-0.26/.pybuild/cpython3_3.8_xdg/build; python3.8 -m nose -v
test
dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8
returned exit code 13
make: *** [debian/rules:7: build] Error 25
--- End Message ---
--- Begin Message ---
Source: pyxdg
Source-Version: 0.27-1
Done: Andrej Shadura
We believe that the bug you reported is fixed in the latest version of
pyxdg, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrej Shadura (supplier of updated pyxdg package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 Jan 2021 15:17:29 +0100
Source: pyxdg
Architecture: source
Version: 0.27-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andrej Shadura
Closes: 949738 964609
Changes:
pyxdg (0.27-1) unstable; urgency=medium
.
[ Andrej Shadura ]
* New upstream release (Closes: #949738, #964609).
* Refresh patches and drop a patch applied upstream.
* Provide the actual module name.
* Add a compatibility layer for the alternative
xdg package.
.
[ Debian Janitor ]
* Use secure URI in Homepage field.
.
[ Håvard Flaget Aasen ]
* Set upstream metadata fields: Bug-Database, Bug-Submit,
Repository, Repository-Browse.
.
[ Ondřej Nový ]
* d/control: Update Maintainer field with new Debian Python Team
contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
Checksums-Sha1:
14252a517ecee93de806337138d03b7c3d5b50b5 1878 pyxdg_0.27-1.dsc
e4afee88cc156da408e10508a1a21b16082781b0 59753 pyxdg_0.27.orig.tar.gz
48c388a577cb7a98b8effd54a3d191cf16d5f91b 14628 pyxdg_0.27-1.debian.tar.xz
Checksums-Sha256:
8d9b230783e92b22cbd8cc4fab42deb3da17f058a06d45c130bc374b6c39079f 1878
pyxdg_0.27-1.dsc
80bd93aae5ed82435f20462ea0208fb198d8eec262e831ee06ce9ddb6b91c5a5 59753
pyxdg_0.27.orig.tar.gz
bc731c0940e0d47cfec679f5e7eb47fed53618ccf299da57ad872c17e50b231f 14628
pyxdg_0.27-1.debian.tar.xz
Files:
78ec5ca466bc7e951c6720dfdd6cc845 1878 python optional pyxdg_0.27-1.dsc
2a2844c21b1b038d74433a0c4aef0a88 59753 python optional pyxdg_0.27.orig.tar.gz
7fa1b85fb0699b52ea59e28ba0432bca 14628 python optional
pyxdg_0.27-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl/9r9sACgkQXkCM2RzY
OdKMcAf+JarCmGrI0sVCC8KVf8wpu3XI8bbaz3rgiCsitYSBOJJSex5+vRAylNjv
a41uXboxSJ+M7IEkuMWkkuiYeqKYtgoEILlDgF/FjgtftP5U7xmNkD2pNJwKlZt7
34yluD5q72sBdF9OmzLWlq4quBYMgHbABlzxz6QdYnuyaE4nNuldgfB4C/0k86vi
/1V9whsikuCY5j6MhYM2UD7Jmh+gPD4C9fvsGFXWnMoh8gAl4dK0hhKn5ixlnFk5
Processed: downgrading severity of #977468 to non-RC
Processing commands for cont...@bugs.debian.org: > severity 977468 important Bug #977468 [src:log4net] CVE-2018-1285 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 977468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: lime-forensics-dkms: unable to make or make install due to error set_fs
Processing control commands: > severity -1 serious Bug #979978 [lime-forensics-dkms] lime-forensics-dkms: unable to make or make install due to error set_fs Severity set to 'serious' from 'normal' > tags -1 - ftbfs Bug #979978 [lime-forensics-dkms] lime-forensics-dkms: unable to make or make install due to error set_fs Removed tag(s) ftbfs. > tags -1 + patch Bug #979978 [lime-forensics-dkms] lime-forensics-dkms: unable to make or make install due to error set_fs Added tag(s) patch. -- 979978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978954: pepperflashplugin-nonfree: should not be part of next stable Debian release
But let me add that even if Opera fixes that, users may think they want to enable flash, try to install pepperflashplugin-nonfree, and with that screw up dpkg. So the issue happens before they try to enable it in a browser. I.e. as long as the package in its current state is present in the archive. / Gunnar
Bug#978954: pepperflashplugin-nonfree: should not be part of next stable Debian release
Hi Paul! On 2021-01-12 14:52, Ying-Chun Liu (PaulLiu) wrote: Do you know why Opera's debian package doesn't drop the dependency of pepperflashplugin-nonfree?? No. I suspect it's simply an oversight (which creates issues at the moment). Cheers, / Gunnar
Bug#976579: libgsecuredelete: FTBFS in debian (patch)`
Hi, libgsecuredelete currently fails to build in Debian: see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976579. This is due to some automake strangeness: generated valac command line seems wrong, according to Rico Tzschichholz, aka ricotz, upstream Vala contributor. The attached patch (courtesy of ricotz) allows to build properly. I also managed to successfully build and use nautilus-wipe with the resulting lib. Also, the vapi path follows vala recommendation and is put in /usr/share/vala/vapi. It was also suggested the *_vala.stamp file should be deleted before build to ensure the code is properly generated. I implemented this in the debian package (to be uploaded soon). Please, consider including this patch. Cheers, -- Clément Hermann (nodens) (with my Tails contributor and Debian Privacy Packaging Team member hats both on) Description: Fix valac call generation in gsecuredelete/Makefile.am Should avoid "already contains a definition for" errors by using vala properly Author: Rico Tzschichholz Forwarded: yes Last-Update: 2021-01-11 --- This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ diff --git a/gsecuredelete/Makefile.am b/gsecuredelete/Makefile.am index c5c62e3..b7dcc18 100644 --- a/gsecuredelete/Makefile.am +++ b/gsecuredelete/Makefile.am @@ -26,15 +26,16 @@ libgsecuredelete_la_SOURCES = gsd-async-operation.vala \ gsd-swap-operation.vala \ gsd-utils.vala \ gsd-zeroable-operation.vala -libgsecuredelete_la_include_HEADERS = gsecuredelete.h \ - gsecuredelete.vapi +libgsecuredelete_la_include_HEADERS = gsecuredelete.h + +vapidir = $(datadir)/vala/vapi +dist_vapi_DATA = gsecuredelete.vapi test_VALAFLAGS = $(AM_VALAFLAGS) --vapidir=. --pkg=gsecuredelete test_SOURCES = main.vala test_LDADD = libgsecuredelete.la gsecuredelete.vapi: libgsecuredelete_la_vala.stamp -test_vala.stamp: gsecuredelete.vapi $(libgsecuredelete_la_SOURCES:.vala=.c): gsd-config.h
Bug#978954: pepperflashplugin-nonfree: should not be part of next stable Debian release
Hey Gunnar, Do you know why Opera's debian package doesn't drop the dependency of pepperflashplugin-nonfree?? I didn't find Opera's official announcement about their roadmap of Flash's EOL. But other browsers are already starting blocking flash. Even with the plugin installed they still refuse to load flash content. Yours, Paul
Bug#977656: zfs-dkms: Fail to build with 5.10 kernel
Hi, Can someone give an estimated timeline for this fix to get into testing (bullseye)? Bye Andrea
Bug#979843: python-django: autopkgtest regression in testing: 'image/vnd.mozilla.apng' != 'image/png'
Hi Paul et al.,
> With a recent in testing the autopkgtest of your package started to
> fail. I copied some of the output at the bottom of this report. Can you
> please investigate the situation and fix it?
Hm, I can't seem to reproduce this failing test:
$ dpkg-parsechangelog | grep Version
Version: 2:2.2.17-2
$ LC_ALL=C.UTF-8 PYTHONPATH=. python3 tests/runtests.py --verbosity 2
mail.tests.MailTests.test_attach_file
Testing against Django installed in
'/home/lamby/git/debian/python-team/modules/python-django/django' with up to 8
processes
Importing application mail
Skipping setup of unused database(s): default, other.
System check identified no issues (0 silenced).
test_attach_file (mail.tests.MailTests)
Test attaching a file against different mimetypes and make sure that ... ok
--
Ran 1 test in 0.017s
Still, we can dig in a bit more:
> AssertionError: 'image/vnd.mozilla.apng' != 'image/png'
> - image/vnd.mozilla.apng
> + image/png
ie. it is expecting "image/png" but gets "image/vnd.mozilla.apng" when
guessing the mimetype of a file called "image.png". A minimal testcase
of this is as follows, I think:
$ python3 -c "import mimetypes; print(mimetypes.guess_type('file.png'))"
('image/png', None)
This appears to be returning the correct result. Has another mimetype-
related package been updated recently? I can't seem to locate one.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org chris-lamb.co.uk
`-
Bug#979970: libselinux1: dependency to newer libc6 ignored by/missing for aptitude
Package: libselinux1 Version: 2.8-1+b1 Severity: grave Right now, an update from buster to bullseye on amd64 completely bricks the system because libselinux1 is requiring a libc6 which is not yet installed on the system: Preparing to unpack .../0-libselinux1_3.1-2+b2_amd64.deb ... De-configuring libselinux1:i386 (2.8-1+b1) ... Unpacking libselinux1:amd64 (3.1-2+b2) over (2.8-1+b1) ... tar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.30' not found (required by /lib/x86_64-linux-gnu/libselinux.so.1) dpkg-deb: error: tar subprocess returned error exit status 1 It is then not possible anymore to recover the system because dpkg (mv, ...) is no longer working. There is most likely some kind dependency missing to let aptitude known that it must first update libc6 before it can update libselinux1. At least on this system, the installed version of libc6 for amd64 and i386 was still 2.28-10 when this happened
Bug#979851: marked as done (fp-compiler-3.2.0: missing backslash in postinst, line 68)
Your message dated Tue, 12 Jan 2021 12:03:41 + with message-id and subject line Bug#979850: fixed in fpc 3.2.0+dfsg-11 has caused the Debian Bug report #979850, regarding fp-compiler-3.2.0: missing backslash in postinst, line 68 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: normal Dear Maintainer, Installation of the package fails, line 68 of the postinst script misses a backslash at the end of the line Best wishes, Jan -- System Information: Debian Release: bullseye/sid APT prefers experimental APT policy: (800, 'experimental'), (500, 'master'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.5-xanmod1 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fp-compiler-3.2.0 depends on: hi binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: ii fp-utils-3.2.0 3.2.0+dfsg-9 Versions of packages fp-compiler-3.2.0 suggests: ii fp-docs-3.2.0 3.2.0+dfsg-9 -- debconf information excluded --- End Message --- --- Begin Message --- Source: fpc Source-Version: 3.2.0+dfsg-11 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of fpc, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated fpc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 11:45:42 + Source: fpc Architecture: source Version: 3.2.0+dfsg-11 Distribution: bullseye Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Graham Inggs Closes: 979850 Changes: fpc (3.2.0+dfsg-11) bullseye; urgency=medium . * Add missing backslash in fp-compiler.postinst (Closes: #979850) * Upload to bullseye since fp-compiler is not installable in unstable Checksums-Sha1: 26bdfc0c485cae961c29c0280744040a6cc87f3d 4371 fpc_3.2.0+dfsg-11.dsc 0294ba8554146406230834b44d4bfecbce9f14ec 267432 fpc_3.2.0+dfsg-11.debian.tar.xz Checksums-Sha256: 95b32064d14cf922568088d8655c9404ed0c3d9e9a5edcd8fcf762dc1e432c61 4371 fpc_3.2.0+dfsg-11.dsc bf58369c42b02dd20e59ec932166e25aa5b39225a7b68ab23978ccde6c09b2ad 267432 fpc_3.2.0+dfsg-11.debian.tar.xz Files: ff250dd1d92e385a044e319c41ca8968 4371 devel optional fpc_3.2.0+dfsg-11.dsc 39b32701ea63d7348758010a86140d34 267432 devel optional fpc_3.2.0+dfsg-11.debian.tar.xz -BEGIN PGP SIGNATURE- iQIyBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl/9jS4ACgkQr8/sjmac 4cK2Ag/4+RwToVPqZqULrCeapM6lj2rv9u11C2J4zCv701leQCR0TxEW8IlZlQLi sahMhcC5Rnl+MaVaqe2BSWWMbFsJYOD1eFvgNX36UsLuh0fzZdTYtXmOsGR4uxju 1mPwLI7A9N10Vo8pc5cD8NShLG3mc3Eb6Pn8Dieq77GkzHmNOTUB4yOagSw7KKhe V7Z6AaLdENl8TlkllWS9Ho6aDY37fK8NgpFtDYnUAHB+3hc7axY1FwtF+pRUizn6 0BIh9vw3D7AWgXB7qlVDvK9XOZv0BXN0huecp7K1GPqYYIBt/vDPAAQzlYL1LLRn 2O/2vukWT3SshFoPU1LEQGYTRxCBs6pKO7SoiXb1QeY4ABlLqPHOaswpq3g1/0Pu J6DI6sQq2RrWGYiQnHBN1W3SepGaSglu8LdWyJzlc1OuOH+jS5jLKSpHk1KUCWH7 t2P3RDgmMX24FxLfciGMg9hB0M6oEBOCfWSdETCe6YydJgbDKWDIV7SdBT4MW8H2 59fOXhQRjyvtFyfa7rCdxt1V8itEqDSNET3qbHsZMw5t9eP7GtT2xwRhxpIKhLZT W+2DjksaYXw6tvO+juzjhFfdYHaOvaHW22FTB2HUFH/7HrUy5jf41jobxCdlTn7+ 2jH4pxfbbhD7JIWPXEue0U3Oy7xEzbZUR2ahmUKDbmt4gnaaCA== =y/Rd -END PGP SIGNATURE End Message ---
Bug#979862: marked as done (fp-compiler-3.2.0+dfsg-9 error when installing)
Your message dated Tue, 12 Jan 2021 12:03:41 +
with message-id
and subject line Bug#979850: fixed in fpc 3.2.0+dfsg-11
has caused the Debian Bug report #979850,
regarding fp-compiler-3.2.0+dfsg-9 error when installing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
979850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fp-compiler-3.2.0
Version: 3.2.0+dfsg-9
Severity: important
Tags: patch
X-Debbugs-Cc: serfyo...@yandex.ru
Dear Maintainer,
Packet:
fp-compiler-3.2.0_3.2.0+dfsg-9_amd64.deb
control.tar.xz
postinst
line
--slave ${MAN_DIR}/fpcres.1.gz fpcres.1.gz ${MAN_DIR}/fpcres-3.2.0.1.gz
must be
--slave ${MAN_DIR}/fpcres.1.gz fpcres.1.gz ${MAN_DIR}/fpcres-3.2.0.1.gz
\
otherwise the next line
--slave ${MAN_DIR}/fpcmkcfg.1.gz fpcmkcfg.1.gz
${MAN_DIR}/fpcmkcfg-3.2.0.1.gz
is not executed and the installation of the package gives an error.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fp-compiler-3.2.0 depends on:
ii binutils 2.35.1-7
ii debconf [debconf-2.0] 1.5.74
ii fp-units-rtl-3.2.0 3.2.0+dfsg-9
ii libc6 2.31-9
Versions of packages fp-compiler-3.2.0 recommends:
ii fp-utils-3.2.0 3.2.0+dfsg-9
Versions of packages fp-compiler-3.2.0 suggests:
ii fp-docs-3.2.0 3.2.0+dfsg-9
-- debconf information:
fp-compiler/rename_cfg: true
fp-compiler/windres-select: Select manually
fp-compiler/windres: Select manually
--- End Message ---
--- Begin Message ---
Source: fpc
Source-Version: 3.2.0+dfsg-11
Done: Graham Inggs
We believe that the bug you reported is fixed in the latest version of
fpc, 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 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Graham Inggs (supplier of updated fpc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 12 Jan 2021 11:45:42 +
Source: fpc
Architecture: source
Version: 3.2.0+dfsg-11
Distribution: bullseye
Urgency: medium
Maintainer: Pascal Packaging Team
Changed-By: Graham Inggs
Closes: 979850
Changes:
fpc (3.2.0+dfsg-11) bullseye; urgency=medium
.
* Add missing backslash in fp-compiler.postinst (Closes: #979850)
* Upload to bullseye since fp-compiler is not installable in unstable
Checksums-Sha1:
26bdfc0c485cae961c29c0280744040a6cc87f3d 4371 fpc_3.2.0+dfsg-11.dsc
0294ba8554146406230834b44d4bfecbce9f14ec 267432 fpc_3.2.0+dfsg-11.debian.tar.xz
Checksums-Sha256:
95b32064d14cf922568088d8655c9404ed0c3d9e9a5edcd8fcf762dc1e432c61 4371
fpc_3.2.0+dfsg-11.dsc
bf58369c42b02dd20e59ec932166e25aa5b39225a7b68ab23978ccde6c09b2ad 267432
fpc_3.2.0+dfsg-11.debian.tar.xz
Files:
ff250dd1d92e385a044e319c41ca8968 4371 devel optional fpc_3.2.0+dfsg-11.dsc
39b32701ea63d7348758010a86140d34 267432 devel optional
fpc_3.2.0+dfsg-11.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIyBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl/9jS4ACgkQr8/sjmac
4cK2Ag/4+RwToVPqZqULrCeapM6lj2rv9u11C2J4zCv701leQCR0TxEW8IlZlQLi
sahMhcC5Rnl+MaVaqe2BSWWMbFsJYOD1eFvgNX36UsLuh0fzZdTYtXmOsGR4uxju
1mPwLI7A9N10Vo8pc5cD8NShLG3mc3Eb6Pn8Dieq77GkzHmNOTUB4yOagSw7KKhe
V7Z6AaLdENl8TlkllWS9Ho6aDY37fK8NgpFtDYnUAHB+3hc7axY1FwtF+pRUizn6
0BIh9vw3D7AWgXB7qlVDvK9XOZv0BXN0huecp7K1GPqYYIBt/vDPAAQzlYL1LLRn
2O/2vukWT3SshFoPU1LEQGYTRxCBs6pKO7SoiXb1QeY4ABlLqPHOaswpq3g1/0Pu
J6DI6sQq2RrWGYiQnHBN1W3SepGaSglu8LdWyJzlc1OuOH+jS5jLKSpHk1KUCWH7
t2P3RDgmMX24FxLfciGMg9hB0M6oEBOCfWSdETCe6YydJgbDKWDIV7SdBT4MW8H2
59fOXhQRjyvtFyfa7rCdxt1V8itEqDSNET3qbHsZMw5t9eP7GtT2xwRhxpIKhLZT
W+2DjksaYXw6tvO+juzjhFfdYHaOvaHW22FTB2HUFH/7HrUy5jf41jobxCdlTn7+
2jH4pxfbbhD7JIWPXEue0U3Oy7xEzbZUR2ahmUKDbmt4gnaaCA==
=y/Rd
-END PGP
Bug#979853: marked as done (fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found)
Your message dated Tue, 12 Jan 2021 12:03:41 + with message-id and subject line Bug#979850: fixed in fpc 3.2.0+dfsg-11 has caused the Debian Bug report #979850, regarding fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Hi! During postinst the following happens: Setting up fp-compiler-3.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak" /var/lib/dpkg/info/fp-compiler-3.2.0:amd64.postinst: line 68: --slave: command not found Reason: Line 67 misses the \ at the end for the continuation line to work. Grüße Sven. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (400, 'testing'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages fp-compiler-3.2.0 depends on: ii binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: ii fp-utils-3.2.0 3.2.0+dfsg-9 Versions of packages fp-compiler-3.2.0 suggests: pn fp-docs-3.2.0 -- debconf information excluded --- End Message --- --- Begin Message --- Source: fpc Source-Version: 3.2.0+dfsg-11 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of fpc, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated fpc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 11:45:42 + Source: fpc Architecture: source Version: 3.2.0+dfsg-11 Distribution: bullseye Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Graham Inggs Closes: 979850 Changes: fpc (3.2.0+dfsg-11) bullseye; urgency=medium . * Add missing backslash in fp-compiler.postinst (Closes: #979850) * Upload to bullseye since fp-compiler is not installable in unstable Checksums-Sha1: 26bdfc0c485cae961c29c0280744040a6cc87f3d 4371 fpc_3.2.0+dfsg-11.dsc 0294ba8554146406230834b44d4bfecbce9f14ec 267432 fpc_3.2.0+dfsg-11.debian.tar.xz Checksums-Sha256: 95b32064d14cf922568088d8655c9404ed0c3d9e9a5edcd8fcf762dc1e432c61 4371 fpc_3.2.0+dfsg-11.dsc bf58369c42b02dd20e59ec932166e25aa5b39225a7b68ab23978ccde6c09b2ad 267432 fpc_3.2.0+dfsg-11.debian.tar.xz Files: ff250dd1d92e385a044e319c41ca8968 4371 devel optional fpc_3.2.0+dfsg-11.dsc 39b32701ea63d7348758010a86140d34 267432 devel optional fpc_3.2.0+dfsg-11.debian.tar.xz -BEGIN PGP SIGNATURE- iQIyBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl/9jS4ACgkQr8/sjmac 4cK2Ag/4+RwToVPqZqULrCeapM6lj2rv9u11C2J4zCv701leQCR0TxEW8IlZlQLi sahMhcC5Rnl+MaVaqe2BSWWMbFsJYOD1eFvgNX36UsLuh0fzZdTYtXmOsGR4uxju 1mPwLI7A9N10Vo8pc5cD8NShLG3mc3Eb6Pn8Dieq77GkzHmNOTUB4yOagSw7KKhe V7Z6AaLdENl8TlkllWS9Ho6aDY37fK8NgpFtDYnUAHB+3hc7axY1FwtF+pRUizn6 0BIh9vw3D7AWgXB7qlVDvK9XOZv0BXN0huecp7K1GPqYYIBt/vDPAAQzlYL1LLRn 2O/2vukWT3SshFoPU1LEQGYTRxCBs6pKO7SoiXb1QeY4ABlLqPHOaswpq3g1/0Pu J6DI6sQq2RrWGYiQnHBN1W3SepGaSglu8LdWyJzlc1OuOH+jS5jLKSpHk1KUCWH7 t2P3RDgmMX24FxLfciGMg9hB0M6oEBOCfWSdETCe6YydJgbDKWDIV7SdBT4MW8H2 59fOXhQRjyvtFyfa7rCdxt1V8itEqDSNET3qbHsZMw5t9eP7GtT2xwRhxpIKhLZT W+2DjksaYXw6tvO+juzjhFfdYHaOvaHW22FTB2HUFH/7HrUy5jf41jobxCdlTn7+ 2jH4pxfbbhD7JIWPXEue0U3Oy7xEzbZUR2ahmUKDbmt4gnaaCA== =y/Rd -END PGP SIGNATURE End Message ---
Bug#979850: marked as done (fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script)
Your message dated Tue, 12 Jan 2021 12:03:41 + with message-id and subject line Bug#979850: fixed in fpc 3.2.0+dfsg-11 has caused the Debian Bug report #979850, regarding fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Dear maintainer, At upgrade time: Setting up fp-compiler-5.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak" /var/lib/dpkg/info/fp-compiler-3.2.0:amd64.postinst: 68: --slave: not found dpkg: error processing package fp-compiler-3.2.0:amd64 (--configure): This is because there is a missing '\' ant the end of line 67. Thanks, -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fp-compiler-3.2.0 depends on: ii binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: pn fp-utils-3.2.0 Versions of packages fp-compiler-3.2.0 suggests: pn fp-docs-3.2.0 -- debconf information excluded --- End Message --- --- Begin Message --- Source: fpc Source-Version: 3.2.0+dfsg-11 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of fpc, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated fpc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 11:45:42 + Source: fpc Architecture: source Version: 3.2.0+dfsg-11 Distribution: bullseye Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Graham Inggs Closes: 979850 Changes: fpc (3.2.0+dfsg-11) bullseye; urgency=medium . * Add missing backslash in fp-compiler.postinst (Closes: #979850) * Upload to bullseye since fp-compiler is not installable in unstable Checksums-Sha1: 26bdfc0c485cae961c29c0280744040a6cc87f3d 4371 fpc_3.2.0+dfsg-11.dsc 0294ba8554146406230834b44d4bfecbce9f14ec 267432 fpc_3.2.0+dfsg-11.debian.tar.xz Checksums-Sha256: 95b32064d14cf922568088d8655c9404ed0c3d9e9a5edcd8fcf762dc1e432c61 4371 fpc_3.2.0+dfsg-11.dsc bf58369c42b02dd20e59ec932166e25aa5b39225a7b68ab23978ccde6c09b2ad 267432 fpc_3.2.0+dfsg-11.debian.tar.xz Files: ff250dd1d92e385a044e319c41ca8968 4371 devel optional fpc_3.2.0+dfsg-11.dsc 39b32701ea63d7348758010a86140d34 267432 devel optional fpc_3.2.0+dfsg-11.debian.tar.xz -BEGIN PGP SIGNATURE- iQIyBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl/9jS4ACgkQr8/sjmac 4cK2Ag/4+RwToVPqZqULrCeapM6lj2rv9u11C2J4zCv701leQCR0TxEW8IlZlQLi sahMhcC5Rnl+MaVaqe2BSWWMbFsJYOD1eFvgNX36UsLuh0fzZdTYtXmOsGR4uxju 1mPwLI7A9N10Vo8pc5cD8NShLG3mc3Eb6Pn8Dieq77GkzHmNOTUB4yOagSw7KKhe V7Z6AaLdENl8TlkllWS9Ho6aDY37fK8NgpFtDYnUAHB+3hc7axY1FwtF+pRUizn6 0BIh9vw3D7AWgXB7qlVDvK9XOZv0BXN0huecp7K1GPqYYIBt/vDPAAQzlYL1LLRn 2O/2vukWT3SshFoPU1LEQGYTRxCBs6pKO7SoiXb1QeY4ABlLqPHOaswpq3g1/0Pu J6DI6sQq2RrWGYiQnHBN1W3SepGaSglu8LdWyJzlc1OuOH+jS5jLKSpHk1KUCWH7 t2P3RDgmMX24FxLfciGMg9hB0M6oEBOCfWSdETCe6YydJgbDKWDIV7SdBT4MW8H2 59fOXhQRjyvtFyfa7rCdxt1V8itEqDSNET3qbHsZMw5t9eP7GtT2xwRhxpIKhLZT W+2DjksaYXw6tvO+juzjhFfdYHaOvaHW22FTB2HUFH/7HrUy5jf41jobxCdlTn7+ 2jH4pxfbbhD7JIWPXEue0U3Oy7xEzbZUR2ahmUKDbmt4gnaaCA== =y/Rd -END PGP SIGNATURE End Message ---
Processed: fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script
Processing commands for cont...@bugs.debian.org:
> forcemerge 979850 979851 979862
Bug #979850 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script
Bug #979853 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not
found
Bug #979851 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0: missing backslash in postinst, line 68
Severity set to 'grave' from 'normal'
Added tag(s) patch.
Bug #979850 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script
Added tag(s) patch.
Added tag(s) patch.
Bug #979862 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0+dfsg-9 error when installing
Severity set to 'grave' from 'important'
Bug #979853 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not
found
Merged 979850 979851 979853 979862
> reopen 979850
Bug #979850 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script
Bug #979851 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0: missing backslash in postinst, line 68
Bug #979853 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not
found
Bug #979862 {Done: Utkarsh Gupta } [fp-compiler-3.2.0]
fp-compiler-3.2.0+dfsg-9 error when installing
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fpc/3.2.0+dfsg-10.
No longer marked as fixed in versions fpc/3.2.0+dfsg-10.
No longer marked as fixed in versions fpc/3.2.0+dfsg-10.
No longer marked as fixed in versions fpc/3.2.0+dfsg-10.
> severity 979850 serious
Bug #979850 [fp-compiler-3.2.0] fp-compiler-3.2.0: missing '\' at end of line
67 in postinst script
Bug #979851 [fp-compiler-3.2.0] fp-compiler-3.2.0: missing backslash in
postinst, line 68
Bug #979853 [fp-compiler-3.2.0] fp-compiler-3.2.0: does not install: postinst:
line 68: --slave: command not found
Bug #979862 [fp-compiler-3.2.0] fp-compiler-3.2.0+dfsg-9 error when installing
Severity set to 'serious' from 'grave'
Severity set to 'serious' from 'grave'
Severity set to 'serious' from 'grave'
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979850
979851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979851
979853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979853
979862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979879: arpack: FTBFS on kfreebsd, m68k and sh4 due to tests failure
Source: arpack Version: 3.8.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, Currently arpack FTBFS on kfreebsd, m68k and sh4 due to tests failures The difference with the other architectures is that the latest version of openmpi is not built on these. I would make the tests non-fatal on these architectures for now until openmpi builds properly. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#975794: marked as done (node-agent-base: FTBFS: Type 'undefined' is not assignable to type 'Duplex | Pick | Agent | PromiseLike'.)
Your message dated Tue, 12 Jan 2021 10:20:21 + with message-id and subject line Bug#975794: fixed in node-agent-base 6.0.2-2 has caused the Debian Bug report #975794, regarding node-agent-base: FTBFS: Type 'undefined' is not assignable to type 'Duplex | Pick | Agent | PromiseLike'. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 975794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-agent-base Version: 6.0.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir --parents node_modules/@types > cp -ar /usr/share/nodejs/@types/debug node_modules/@types > cp -ar /usr/share/nodejs/@types/mocha node_modules/@types > cp -ar /usr/share/nodejs/@types/node node_modules/@types > cp -ar /usr/share/nodejs/@types/semver node_modules/@types > tsc > src/promisify.ts(27,15): error TS2345: Argument of type 'Duplex | Pick "addRequest"> | Agent | undefined' is not assignable to parameter of type > 'Duplex | Pick | Agent | > PromiseLike'. > Type 'undefined' is not assignable to type 'Duplex | Pick "addRequest"> | Agent | PromiseLike'. > make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/11/25/node-agent-base_6.0.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: node-agent-base Source-Version: 6.0.2-2 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-agent-base, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-agent-base package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Jan 2021 10:59:13 +0100 Source: node-agent-base Architecture: source Version: 6.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 975794 979790 Changes: node-agent-base (6.0.2-2) unstable; urgency=medium . * Team upload . [ Pirate Praveen ] * Tighten build dependencies for typescript definitions . [ Xavier Guimard ] * Declare compliance with policy 4.5.1 * Modernize debian/watch * Add ctype=nodejs to component(s) * Fix typescript ≥ 4.1 regression (Closes: #975794) * Update build dependencies: replace node-typescript-types by node-types-node (Closes: #979790) * Enable autopkgtest (missing testsuite) * Use debian/nodejs/extlinks instead of debiran/rules hook Checksums-Sha1: 1f81d00d50fb7686c9cf76cdf0f06ab81d824cf9 2565 node-agent-base_6.0.2-2.dsc ae48e0b160007d6b49a2ecfa9ff06b7f23e041b9 3660 node-agent-base_6.0.2-2.debian.tar.xz Checksums-Sha256: 1058563f75ae0524f77d31590231769dc7e698c11cf90e81a40b99618371545c 2565 node-agent-base_6.0.2-2.dsc 847d705a3594890363441e4b2de60c93d5dfea1ff61140fba8b432c960c3021e 3660 node-agent-base_6.0.2-2.debian.tar.xz Files: 2b6f5375323ed7da00af47cde0132050 2565 javascript optional node-agent-base_6.0.2-2.dsc 0bedeb306e8bb86d8a5a85aea4b98d70 3660 javascript optional node-agent-base_6.0.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/9czcACgkQ9tdMp8mZ 7unMHw/+MdqA0C+rNR3V6W0MTLps9d6ITJVWr1/YHFOqsZdZIykOTCfLvcniOpfz g5J0S+xsJH6i8yBkeD0xSA4/5r3dtlHA/bTN5ZXradrQR61Xth0HmN+jSrzeAckQ 74n8Lbyttv1AI0kpigbVCdEkmX8PiYSVTTOY4kREkc5oYabMFY7TrALqcbbZD29P vWZARfdlPodUU7KJxDyNV1rVxsQjumfH1jnc49Rmta1nQmkFcB4Bq7RUo54FOKtw
Processed: fixed 979063 in php-font-lib/0.3.1+dfsg-3.1
Processing commands for cont...@bugs.debian.org:
> fixed 979063 php-font-lib/0.3.1+dfsg-3.1
Bug #979063 {Done: Dmitry Smirnov } [php-font-lib]
php-font-lib: Useless in Debian
Marked as fixed in versions php-font-lib/0.3.1+dfsg-3.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979875: src:goban: invalid maintainer address
Source: goban Version: 1.1-5 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Sat, 09 Jan 2021 22:54:03 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: r...@toor.fi.eu.org all hosts for 'toor.fi.eu.org' have been failing for a long time and were last tried after this message arrived Reporting-MTA: dns; muffat.debian.org Action: failed Final-Recipient: rfc822;root@toor.fi.eu.org Status: 5.0.0
Bug#904576: python3-hug: fails to install with Python 3.7
Hi, according to https://github.com/hugapi/hug/issues/631 this issue was resolved with version 2.4.1 of hug. So, given that 2.4.1 was uploaded two years ago and 2.6.0 was uploaded one year ago I think we can close this bug? cheers, Birger -- // Birger Schacht // CERT Austria - https://www.cert.at/ // Eine Initiative der nic.at GmbH - https://www.nic.at/ // Firmenbuchnummer 172568b, LG Salzburg
Bug#979874: node-cross-spawn-async: Keep out of testing
Package: node-cross-spawn-async Version: 2.2.5-4 Severity: serious As node-cross-spawn, node-cross-spawn-async shoul d be kept out of Bullseye
Bug#975794: marked as pending in node-agent-base
Control: tag -1 pending Hello, Bug #975794 in node-agent-base reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-agent-base/-/commit/5a3c1d10828ca88ca5c275a65b8be87b81e38ed0 Fix typescript ≥ 4.1 regression Closes: #975794 (this message was generated automatically) -- Greetings https://bugs.debian.org/975794
Processed: Bug#975794 marked as pending in node-agent-base
Processing control commands: > tag -1 pending Bug #975794 [src:node-agent-base] node-agent-base: FTBFS: Type 'undefined' is not assignable to type 'Duplex | Pick | Agent | PromiseLike'. Added tag(s) pending. -- 975794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970809: marked as done (python3-venv is gone)
Your message dated Tue, 12 Jan 2021 09:36:06 +0100 with message-id and subject line Re: Bug#970809: python3-venv is gone has caused the Debian Bug report #970809, regarding python3-venv is gone to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 970809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pipx Version: 0.12.3.1-3 Severity: serious Tags: sid bullseye This package depends or build-depends on python3-venv, which is gone upstream. Please remove or re-implement that usage. --- End Message --- --- Begin Message --- Hi, On Fri, 08 Jan 2021, Raphael Hertzog wrote: > > This package depends or build-depends on python3-venv, which is gone > > upstream. > > Please remove or re-implement that usage. > > Can you be more verbose and back up this assertion with something > concrete? > > What is gone exactly? Doko replied on IRC that what's gone is /usr/bin/pyvenv but we don't use that and we don't need it in this package. So there's nothing to fix really. Closing the bug. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS--- End Message ---
Bug#979853: marked as done (fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found)
Your message dated Tue, 12 Jan 2021 08:48:40 + with message-id and subject line Bug#979850: fixed in fpc 3.2.0+dfsg-10 has caused the Debian Bug report #979850, regarding fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Hi! During postinst the following happens: Setting up fp-compiler-3.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak" /var/lib/dpkg/info/fp-compiler-3.2.0:amd64.postinst: line 68: --slave: command not found Reason: Line 67 misses the \ at the end for the continuation line to work. Grüße Sven. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (400, 'testing'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages fp-compiler-3.2.0 depends on: ii binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: ii fp-utils-3.2.0 3.2.0+dfsg-9 Versions of packages fp-compiler-3.2.0 suggests: pn fp-docs-3.2.0 -- debconf information excluded --- End Message --- --- Begin Message --- Source: fpc Source-Version: 3.2.0+dfsg-10 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of fpc, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated fpc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 13:51:28 +0530 Source: fpc Architecture: source Version: 3.2.0+dfsg-10 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Utkarsh Gupta Closes: 979850 979851 979853 979862 Changes: fpc (3.2.0+dfsg-10) unstable; urgency=medium . * Non-maintainer upload. * Add a missing backslash in postint script. (Closes: #979850, #979853, #979862, #979851) Checksums-Sha1: dcd9bf4282e93783cb3ce8232fef853e3120 4400 fpc_3.2.0+dfsg-10.dsc 5ede727382f97abd2c7c5cc3848ad0f556b57459 267456 fpc_3.2.0+dfsg-10.debian.tar.xz e53159a5685d271a706b6bc0e963cf07f1fb158e 18567 fpc_3.2.0+dfsg-10_amd64.buildinfo Checksums-Sha256: d0dd1857fc8658e13a4d1bf66add5b6e035cb8b56483b74574c969b73117da71 4400 fpc_3.2.0+dfsg-10.dsc 692605f332be67d89e23fe4dbbd90286e70ab7c2f2f6f67877490e035561be91 267456 fpc_3.2.0+dfsg-10.debian.tar.xz a8de585b8b91bf4d43bb44de1dbc10070203a3416846b014b59f5896b9f6edcf 18567 fpc_3.2.0+dfsg-10_amd64.buildinfo Files: 932999b406271243d2bb289f9d9d2754 4400 devel optional fpc_3.2.0+dfsg-10.dsc 7b1d728f1cf5ad73ad029306cceeaa03 267456 devel optional fpc_3.2.0+dfsg-10.debian.tar.xz 2aabf8a99fb454a3e35e190bfcc02576 18567 devel optional fpc_3.2.0+dfsg-10_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl/9X5oTHHV0a2Fyc2hA ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlun7D/9HyIIve3JqzFrRanu6CONyWC06TGb9 E/G4W3687iqzRHE1uQ9ESUHQn5+MAlN+XcOkUbZ3oNwJUa+LPHZpP5Wiz/j6t6tD wV4UySVpmjESYi7UECzrxfGlXnURgfXleHcf9v03BtokYcGFyLhRowgyBI4PuAMY IFcEI3z0gQRcF/TKVSaZAt2MgAXNl3xgCm9kOETZ5mZ7uWnNMlT4pjChL+tyy2Ot uNEusK4GsUcLDk1VzYV2x2Ga5bYXXuJ43VEflVgtuBLS+7yTU0Fn25KvW9fssvtz sRsxZV7/Twn6royH1fjBeAYWu54V4kuDIfhtOdtgxmcXScTgWZTsxWbT35F879nH OJrk3SHJnP1KhUEmLt69FoKXf8linMCf3YnST89AXM5dSzaoYxuY+/V402dEH4Yf
Bug#979853: marked as done (fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found)
Your message dated Tue, 12 Jan 2021 08:48:40 + with message-id and subject line Bug#979853: fixed in fpc 3.2.0+dfsg-10 has caused the Debian Bug report #979853, regarding fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Hi! During postinst the following happens: Setting up fp-compiler-3.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak" /var/lib/dpkg/info/fp-compiler-3.2.0:amd64.postinst: line 68: --slave: command not found Reason: Line 67 misses the \ at the end for the continuation line to work. Grüße Sven. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (400, 'testing'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages fp-compiler-3.2.0 depends on: ii binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: ii fp-utils-3.2.0 3.2.0+dfsg-9 Versions of packages fp-compiler-3.2.0 suggests: pn fp-docs-3.2.0 -- debconf information excluded --- End Message --- --- Begin Message --- Source: fpc Source-Version: 3.2.0+dfsg-10 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of fpc, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated fpc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 13:51:28 +0530 Source: fpc Architecture: source Version: 3.2.0+dfsg-10 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Utkarsh Gupta Closes: 979850 979851 979853 979862 Changes: fpc (3.2.0+dfsg-10) unstable; urgency=medium . * Non-maintainer upload. * Add a missing backslash in postint script. (Closes: #979850, #979853, #979862, #979851) Checksums-Sha1: dcd9bf4282e93783cb3ce8232fef853e3120 4400 fpc_3.2.0+dfsg-10.dsc 5ede727382f97abd2c7c5cc3848ad0f556b57459 267456 fpc_3.2.0+dfsg-10.debian.tar.xz e53159a5685d271a706b6bc0e963cf07f1fb158e 18567 fpc_3.2.0+dfsg-10_amd64.buildinfo Checksums-Sha256: d0dd1857fc8658e13a4d1bf66add5b6e035cb8b56483b74574c969b73117da71 4400 fpc_3.2.0+dfsg-10.dsc 692605f332be67d89e23fe4dbbd90286e70ab7c2f2f6f67877490e035561be91 267456 fpc_3.2.0+dfsg-10.debian.tar.xz a8de585b8b91bf4d43bb44de1dbc10070203a3416846b014b59f5896b9f6edcf 18567 fpc_3.2.0+dfsg-10_amd64.buildinfo Files: 932999b406271243d2bb289f9d9d2754 4400 devel optional fpc_3.2.0+dfsg-10.dsc 7b1d728f1cf5ad73ad029306cceeaa03 267456 devel optional fpc_3.2.0+dfsg-10.debian.tar.xz 2aabf8a99fb454a3e35e190bfcc02576 18567 devel optional fpc_3.2.0+dfsg-10_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl/9X5oTHHV0a2Fyc2hA ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlun7D/9HyIIve3JqzFrRanu6CONyWC06TGb9 E/G4W3687iqzRHE1uQ9ESUHQn5+MAlN+XcOkUbZ3oNwJUa+LPHZpP5Wiz/j6t6tD wV4UySVpmjESYi7UECzrxfGlXnURgfXleHcf9v03BtokYcGFyLhRowgyBI4PuAMY IFcEI3z0gQRcF/TKVSaZAt2MgAXNl3xgCm9kOETZ5mZ7uWnNMlT4pjChL+tyy2Ot uNEusK4GsUcLDk1VzYV2x2Ga5bYXXuJ43VEflVgtuBLS+7yTU0Fn25KvW9fssvtz sRsxZV7/Twn6royH1fjBeAYWu54V4kuDIfhtOdtgxmcXScTgWZTsxWbT35F879nH OJrk3SHJnP1KhUEmLt69FoKXf8linMCf3YnST89AXM5dSzaoYxuY+/V402dEH4Yf
Bug#979850: marked as done (fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script)
Your message dated Tue, 12 Jan 2021 08:48:40 + with message-id and subject line Bug#979853: fixed in fpc 3.2.0+dfsg-10 has caused the Debian Bug report #979853, regarding fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Dear maintainer, At upgrade time: Setting up fp-compiler-5.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak" /var/lib/dpkg/info/fp-compiler-3.2.0:amd64.postinst: 68: --slave: not found dpkg: error processing package fp-compiler-3.2.0:amd64 (--configure): This is because there is a missing '\' ant the end of line 67. Thanks, -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fp-compiler-3.2.0 depends on: ii binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: pn fp-utils-3.2.0 Versions of packages fp-compiler-3.2.0 suggests: pn fp-docs-3.2.0 -- debconf information excluded --- End Message --- --- Begin Message --- Source: fpc Source-Version: 3.2.0+dfsg-10 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of fpc, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated fpc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 13:51:28 +0530 Source: fpc Architecture: source Version: 3.2.0+dfsg-10 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Utkarsh Gupta Closes: 979850 979851 979853 979862 Changes: fpc (3.2.0+dfsg-10) unstable; urgency=medium . * Non-maintainer upload. * Add a missing backslash in postint script. (Closes: #979850, #979853, #979862, #979851) Checksums-Sha1: dcd9bf4282e93783cb3ce8232fef853e3120 4400 fpc_3.2.0+dfsg-10.dsc 5ede727382f97abd2c7c5cc3848ad0f556b57459 267456 fpc_3.2.0+dfsg-10.debian.tar.xz e53159a5685d271a706b6bc0e963cf07f1fb158e 18567 fpc_3.2.0+dfsg-10_amd64.buildinfo Checksums-Sha256: d0dd1857fc8658e13a4d1bf66add5b6e035cb8b56483b74574c969b73117da71 4400 fpc_3.2.0+dfsg-10.dsc 692605f332be67d89e23fe4dbbd90286e70ab7c2f2f6f67877490e035561be91 267456 fpc_3.2.0+dfsg-10.debian.tar.xz a8de585b8b91bf4d43bb44de1dbc10070203a3416846b014b59f5896b9f6edcf 18567 fpc_3.2.0+dfsg-10_amd64.buildinfo Files: 932999b406271243d2bb289f9d9d2754 4400 devel optional fpc_3.2.0+dfsg-10.dsc 7b1d728f1cf5ad73ad029306cceeaa03 267456 devel optional fpc_3.2.0+dfsg-10.debian.tar.xz 2aabf8a99fb454a3e35e190bfcc02576 18567 devel optional fpc_3.2.0+dfsg-10_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl/9X5oTHHV0a2Fyc2hA ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlun7D/9HyIIve3JqzFrRanu6CONyWC06TGb9 E/G4W3687iqzRHE1uQ9ESUHQn5+MAlN+XcOkUbZ3oNwJUa+LPHZpP5Wiz/j6t6tD wV4UySVpmjESYi7UECzrxfGlXnURgfXleHcf9v03BtokYcGFyLhRowgyBI4PuAMY IFcEI3z0gQRcF/TKVSaZAt2MgAXNl3xgCm9kOETZ5mZ7uWnNMlT4pjChL+tyy2Ot uNEusK4GsUcLDk1VzYV2x2Ga5bYXXuJ43VEflVgtuBLS+7yTU0Fn25KvW9fssvtz sRsxZV7/Twn6royH1fjBeAYWu54V4kuDIfhtOdtgxmcXScTgWZTsxWbT35F879nH OJrk3SHJnP1KhUEmLt69FoKXf8linMCf3YnST89AXM5dSzaoYxuY+/V402dEH4Yf pheJ9jrwm9mekYvu4Ul8Q1RPptmasGmOJgoVzcOaJgqIRSXc5M8lDQJ8lGQCih0L IM+gsupG+yfzRIJT7U4+HivTcCB50rYLUEv91wVh7easRZQQUKSzJmmL5IikyBj4
Bug#979850: marked as done (fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script)
Your message dated Tue, 12 Jan 2021 08:48:40 + with message-id and subject line Bug#979850: fixed in fpc 3.2.0+dfsg-10 has caused the Debian Bug report #979850, regarding fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Dear maintainer, At upgrade time: Setting up fp-compiler-5.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak" /var/lib/dpkg/info/fp-compiler-3.2.0:amd64.postinst: 68: --slave: not found dpkg: error processing package fp-compiler-3.2.0:amd64 (--configure): This is because there is a missing '\' ant the end of line 67. Thanks, -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fp-compiler-3.2.0 depends on: ii binutils 2.35.1-7 ii debconf [debconf-2.0] 1.5.74 ii fp-units-rtl-3.2.0 3.2.0+dfsg-9 ii libc6 2.31-9 Versions of packages fp-compiler-3.2.0 recommends: pn fp-utils-3.2.0 Versions of packages fp-compiler-3.2.0 suggests: pn fp-docs-3.2.0 -- debconf information excluded --- End Message --- --- Begin Message --- Source: fpc Source-Version: 3.2.0+dfsg-10 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of fpc, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated fpc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Jan 2021 13:51:28 +0530 Source: fpc Architecture: source Version: 3.2.0+dfsg-10 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Utkarsh Gupta Closes: 979850 979851 979853 979862 Changes: fpc (3.2.0+dfsg-10) unstable; urgency=medium . * Non-maintainer upload. * Add a missing backslash in postint script. (Closes: #979850, #979853, #979862, #979851) Checksums-Sha1: dcd9bf4282e93783cb3ce8232fef853e3120 4400 fpc_3.2.0+dfsg-10.dsc 5ede727382f97abd2c7c5cc3848ad0f556b57459 267456 fpc_3.2.0+dfsg-10.debian.tar.xz e53159a5685d271a706b6bc0e963cf07f1fb158e 18567 fpc_3.2.0+dfsg-10_amd64.buildinfo Checksums-Sha256: d0dd1857fc8658e13a4d1bf66add5b6e035cb8b56483b74574c969b73117da71 4400 fpc_3.2.0+dfsg-10.dsc 692605f332be67d89e23fe4dbbd90286e70ab7c2f2f6f67877490e035561be91 267456 fpc_3.2.0+dfsg-10.debian.tar.xz a8de585b8b91bf4d43bb44de1dbc10070203a3416846b014b59f5896b9f6edcf 18567 fpc_3.2.0+dfsg-10_amd64.buildinfo Files: 932999b406271243d2bb289f9d9d2754 4400 devel optional fpc_3.2.0+dfsg-10.dsc 7b1d728f1cf5ad73ad029306cceeaa03 267456 devel optional fpc_3.2.0+dfsg-10.debian.tar.xz 2aabf8a99fb454a3e35e190bfcc02576 18567 devel optional fpc_3.2.0+dfsg-10_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl/9X5oTHHV0a2Fyc2hA ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlun7D/9HyIIve3JqzFrRanu6CONyWC06TGb9 E/G4W3687iqzRHE1uQ9ESUHQn5+MAlN+XcOkUbZ3oNwJUa+LPHZpP5Wiz/j6t6tD wV4UySVpmjESYi7UECzrxfGlXnURgfXleHcf9v03BtokYcGFyLhRowgyBI4PuAMY IFcEI3z0gQRcF/TKVSaZAt2MgAXNl3xgCm9kOETZ5mZ7uWnNMlT4pjChL+tyy2Ot uNEusK4GsUcLDk1VzYV2x2Ga5bYXXuJ43VEflVgtuBLS+7yTU0Fn25KvW9fssvtz sRsxZV7/Twn6royH1fjBeAYWu54V4kuDIfhtOdtgxmcXScTgWZTsxWbT35F879nH OJrk3SHJnP1KhUEmLt69FoKXf8linMCf3YnST89AXM5dSzaoYxuY+/V402dEH4Yf pheJ9jrwm9mekYvu4Ul8Q1RPptmasGmOJgoVzcOaJgqIRSXc5M8lDQJ8lGQCih0L IM+gsupG+yfzRIJT7U4+HivTcCB50rYLUEv91wVh7easRZQQUKSzJmmL5IikyBj4
Processed: forcibly merging 979850 979853
Processing commands for cont...@bugs.debian.org: > forcemerge 979850 979853 Bug #979850 [fp-compiler-3.2.0] fp-compiler-3.2.0: missing '\' at end of line 67 in postinst script Bug #979853 [fp-compiler-3.2.0] fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found Merged 979850 979853 > thanks Stopping processing here. Please contact me if you need assistance. -- 979850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979850 979853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979022: marked as done (Useless in Debian)
Your message dated Tue, 12 Jan 2021 19:10:01 +1100 with message-id <2397700.4ZqFxWmyiA@deblab> and subject line Done: Useless in Debian has caused the Debian Bug report #979022, regarding Useless in Debian to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: php-dompdf Severity: serious [ Reported by a team member to see the package removed from testing ] php-dompdf was introduced in Debian as part of the ownCloud packaging effort, but no packages depend on it anymore, so I don’t believe it’s useful to keep it around. Unless someone disagree with the above, I intend to ask for removal of this package soon (so if you read this message years from now, no need to ask for permission to act on what I’ve failed to…). Thank you Holger for reminding me that this package is still around! Regards David signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Package: php-dompdf Version: 0.6.2+dfsg-3 This package is orphaned [1] so there is no need to emphasise that fact so strongly. One valid depending package (CiviCRM) definitely makes php-dompdf useful, not useless. Hopefully someone will adopt php-dompdf and as CiviCRM maintainer, I will definitely consider taking care of php-dompdf, if my work capacity allows. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978994 Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#979063: marked as done (php-font-lib: Useless in Debian)
Your message dated Tue, 12 Jan 2021 19:06:06 +1100 with message-id <1848999.CAYGLEb3MN@deblab> and subject line Done: php-font-lib: Useless in Debian has caused the Debian Bug report #979063, regarding php-font-lib: Useless in Debian to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 979063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: php-font-lib Version: 0.3.1+dfsg-3.1 Severity: serious X-Debbugs-Cc: taf...@debian.org, only...@debian.org, hol...@debian.org [ Trying to remove the package from bullseye at least ] Similar to php-dompdf [1], this package is pretty useless for bullseye, since it is only needed by php-dompdf, which is not depent on by any package in testing. Only possible candidate would be civicrm [2], which seems not be able to make it to bullseye. Also see the orphan [3]. Best Regards Markus Frosch [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979022 [2] https://tracker.debian.org/pkg/civicrm [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978995 --- End Message --- --- Begin Message --- Package: php-font-lib Version: 0.3.1+dfsg-3 The package is orphaned [1] so there is no need to emphasise that fact so strongly. One valid depending package definitely makes php-font-lib useful and desirable. Hopefully someone will adopt it. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978995 Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. signature.asc Description: This is a digitally signed message part. --- End Message ---
