Bug#888025: gpgsm: UI asks insane, unanswerable trust questions
Also noticed a modal messagebox popping up regularly when having kmail running. Below is a workaround that simply always answers the question with no instead of asking. --- gnupg2-2.2.43.orig/agent/trustlist.c +++ gnupg2-2.2.43/agent/trustlist.c @@ -687,6 +687,9 @@ agent_marktrusted (ctrl_t ctrl, const ch if (!nameformatted) return gpg_error_from_syserror (); + // We do not trust this. Do not show that dialog. + return gpg_error (GPG_ERR_NOT_TRUSTED); + /* First a general question whether this is trusted. */ desc = xtryasprintf ( /* TRANSLATORS: This prompt is shown by the Pinentry
Bug#1056770: braillefont: Description in debian/control has a new line in the middle of a sentence
s/liik/look (: signature.asc Description: This is a digitally signed message part.
Bug#1056770: braillefont: Description in debian/control has a new line in the middle of a sentence
Hi, did reformat the long description - the newline ended up at the same position of the sentence as before, but I think, it should liik more sane now - braillefont runs interactively on the console - one can enter a (short) text, that will be converted into a bitmapped version and printed using the Braille range of Unicode. signature.asc Description: This is a digitally signed message part.
Bug#1056770: braillefont: Description in debian/control has a new line in the middle of a sentence
Test results - Mail to 1056...@bugs.debian.org - - received by maintainer - *not* received by bug submitter - recorded in the bts (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056770#10) Mail to 1056770-submit...@bugs.debian.org - - *not* received by maintainer - received by bug submitter - recorded in the bts (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056770#13) Mail to both - - received by maintainer - received by bug submitter - recorded in the bts (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056770#18) signature.asc Description: This is a digitally signed message part.
Bug#1056770: braillefont: Description in debian/control has a new line in the middle of a sentence
Hi, and finally, this mail does address both 1056...@bugs.debian.org and 1056770-submit...@bugs.debian.org Thanks for taking part in this experiment. And indeed, from the first look, this seems to be a valid bug :) urbec signature.asc Description: This is a digitally signed message part.
Bug#1056770: braillefont: Description in debian/control has a new line in the middle of a sentence
Hi, this mail does address only 1056...@bugs.debian.org urbec signature.asc Description: This is a digitally signed message part.
Bug#1054313: ITP: fonts-ottilie-kurrent -- font for German Kurrent using thick curvy hand written-like letters
Package: wnpp Severity: wishlist Owner: Judit Foglszinger X-Debbugs-Cc: debian-de...@lists.debian.org, ur...@debian.org * Package name: fonts-ottilie-kurrent Version : 0~20130218 Upstream Contact: Peter Wiegel * URL : http://www.peter-wiegel.de/Ottilie.html * License : OFL-1.1-RFN Programming Lang: Description : font for German Kurrent using thick curvy hand written-like letters This proportional font resembles a younger version of the German Kurrent cursive script from around 1900 and aims to look like a curvy handwriting using a thick pen. . One can use it as aid to learn Kurrent, for tattoos or other text, where readability is less important. . Kurrent has been used for hand writing over 500 years, undergoing various transformations until it has been replaced by the nowadays more well-known Sütterlin script from 1911. I plan to maintain this within the Debian fonts team. signature.asc Description: This is a digitally signed message part.
Bug#405339: Solarwolf font error
tags #405339 + unreproducible thanks Hi, since this bug was reported over 16 years ago, pygame has made lots of changes, among others to its font handling code. Eg the mentioned error message "unable to read font filename" has been replaced in 2010 with "unable to read font file '%.1024s'" - https://github.com/pygame/pygame/commit/4772a872b3e72a59e507ecb3f4ed55b44fd375cb and been removed in 2022 - https://github.com/pygame/pygame/commit/e5659f146d83702ccb4db16af6e3b73d1d2845f1 Also at the current point in time cannot reproduce this bug (or a similar one with different error messages), so I'm tagging it accordingly and plan to close it in a few weeks. Thanks for reporting it and if it still or again :) occurs, feel free to reply or reopen, if it's already closed at that time. signature.asc Description: This is a digitally signed message part.
Bug#990070: irssi: -actcolor parameter for /highlight is not always respected
forwarded 990070 https://github.com/irssi/irssi/issues/1479 thanks Hi, forwarded this to upstream, let's see :) signature.asc Description: This is a digitally signed message part.
Bug#1041517: sendemail: when using starttls, SSL_verifycn_name is not set, leading to hostname verification failed
Package: sendemail
Version: 1.56-5.1
Severity: normal
Tags: patch
Hi,
when using sendemail to send an email with
relay mail-submit.debian.org (uses starttls),
hostname verification fails -
$ sendEmail -o tls=yes -f "ur...@debian.org" \
-t recip...@example.org -s mail-submit.debian.org:587 \
-o message-file=/tmp/mail.txt \
-xu urbec -xp the-password-is-always-password \
-u "Test email"
Jul 13 21:06:32 (...) sendEmail[11565]: ERROR => TLS setup failed: hostname
verification failed
$
Non recent versions of SSL.pm also did show the following error message -
Use of uninitialized value $2 in concatenation (.) or string at
/usr/share/perl5/IO/Socket/SSL.pm line 792.
The current version in sid replaces the missing hostname
with the sender's IP, so no error message beyond
"hostname verification failed" anymore.
(versions before bookworm just allowed IP addresses as always verified,
but that's no longer the case)
The following patch passes the hostname -
Description: Fix TLS hostname verification.
Author: Unit 193
Forwarded: no
--- sendemail-1.56.orig/sendEmail
+++ sendemail-1.56/sendEmail
@@ -1930,7 +1930,10 @@ if( $conf{'use_sendmail'} ) {
if ($conf{'tls_server'} == 1 and $conf{'tls_client'} == 1 and
$opt{'tls'} =~ /^(yes|auto)$/) {
printmsg("DEBUG => Starting TLS", 2);
if (SMTPchat('STARTTLS')) { quit($conf{'error'}, 1); }
-if (! IO::Socket::SSL->start_SSL($SERVER, SSL_version =>
'SSLv23:!SSLv2')) {
+if (! IO::Socket::SSL->start_SSL($SERVER,
+ SSL_version => 'TLSv12:!SSLv2',
+ SSL_verifycn_scheme => 'smtp',
+ SSL_verifycn_name => $conf{'server'})) {
quit("ERROR => TLS setup failed: " .
IO::Socket::SSL::errstr(), 1);
}
printmsg("DEBUG => TLS: Using cipher: ". $SERVER->get_cipher(), 3);
signature.asc
Description: This is a digitally signed message part.
Bug#1037043: (no subject)
severity 1037043 important thanks Hi, seems, it only crashes with libsdl1.2-compat-shim installed, so not for everyone and the submitter is ok with downgrading it to important to keep pink ponies in bookworm one week before the release.
Bug#1032505: braillefont FTCBFS: unsatisfiable binutils dependency
tags 1032505 + pending stop Hi, thanks for your patch signature.asc Description: This is a digitally signed message part.
Bug#1030184: ezquake FTBFS
Source: ezquake Version: 3.6.1-1 Severity: serious Tags: ftbfs Hi, ezquake fails to build from source on the buildds. https://buildd.debian.org/status/package.php?p=ezquake&suite=sid (log eg https://buildd.debian.org/status/fetch.php?pkg=ezquake&arch=amd64&ver=3.6.1-1&stamp=1674575852&raw=0) ... FAILED: ezquake.p/common.c.o cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu -I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 -I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror -Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation -Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 '-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 -DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast -Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG -DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND -DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ ezquake.p/common.c.o -MF ezquake.p/common.c.o.d -o ezquake.p/common.c.o -c ../common.c ../common.c: In function ‘COM_WriteToUniqueTempFile’: ../common.c:429:17: error: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] 429 | write(fd, buffer, bytes); | ^~~~ cc1: all warnings being treated as errors [128/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu -I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 -I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror -Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation -Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 '-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 -DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast -Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG -DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND -DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ ezquake.p/com_msg.c.o -MF ezquake.p/com_msg.c.o.d -o ezquake.p/com_msg.c.o -c ../com_msg.c [129/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu -I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 -I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror -Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation -Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 '-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 -DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast -Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG -DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND -DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ ezquake.p/config_manager.c.o -MF ezquake.p/config_manager.c.o.d -o ezquake.p/config_manager.c.o -c ../config_manager.c [130/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu -I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 -I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror -Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation -Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 '-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 -DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast -Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG -DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND -DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ ezquake.p/console.c.o -MF ezquake.p/console.c.o.d -o ezquake.p/console.c.o -c ../console.c ninja: build stopped: subcommand failed. dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v returned exit code 1 make: *** [debian/rules:12: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 signature.asc Description: This is a digitally signed message part.
Bug#1011923: ice-builder-gradle: FTBFS with OpenJDK 17 due to an illegal reflective access
user debian-rele...@lists.debian.org usertag 1011923 + bsp-2022-11-nl-tilburg tags 1005719 + moreinfo thank you Hi, I tried to reproduce this using sbuild and the build did succeed, wether I kept the default dependency of default-jdk or replaced it with explicitly refering to openjdk-17-jdk. (got some stack traces (see at bottom for one of them), but the build still succeded) How do you build the package to get this ftbfs? --- one of the stack traces during build - Starting Build Settings evaluated using settings file '/<>/settings.gradle'. Projects loaded. Root project using build file '/<>/build.gradle'. Included projects: [root project 'slice'] Evaluating root project 'slice' using build file '/<>/build.gradle'. Creating new cache for metadata-1.1/results, path /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access org.gradle.cache.internal.DefaultCacheAccess@364fd4ae The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. at org.gradle.api.internal.AbstractTask.leftShift(AbstractTask.java:618) at org.gradle.api.Task$leftShift.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128) at build_br256y3y0jx26wjwsor9zxs5d.run(/<>/build.gradle:100) at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:90) at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:199) at org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77) at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:204) at org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:61) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110) at org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:58) at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:41) at org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:26) at org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34) at org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:64) at org.gradle.configuration.project.LifecycleProjectEvaluator.access$100(LifecycleProjectEvaluator.java:34) at org.gradle.configuration.project.LifecycleProjectEvaluator$ConfigureProject.run(LifecycleProjectEvaluator.java:110) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110) at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:50) at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:666) at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:135) at org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:35) at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:60) at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:38) at org.gradle.initialization.DefaultGradleLauncher$ConfigureBuild.run(DefaultGradleLauncher.java:249) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.Def
Bug#1022856: atril: Patch to transition to webkit2gtk-4.1
Package: atril Version: 1.26.0-1 Severity: wishlist Tags: patch X-Debbugs-Cc: ur...@debian.org, unit...@debian.org Hi, have attached a patch by Unit193 for transitioning atril to webkit2gtk-4.1 >From 8578ecbe3ede1b0766710b9c9e75d01dc78636c8 Mon Sep 17 00:00:00 2001 From: Unit 193 Date: Wed, 26 Oct 2022 08:40:51 -0400 Subject: [PATCH] d/control, d/p/1001-webkit4.1.patch: Transition to webkit2gtk-4.1. --- debian/control | 2 +- debian/patches/1001-webkit2gtk4.1.patch | 15 +++ debian/patches/series | 1 + 3 files changed, 17 insertions(+), 1 deletion(-) create mode 100644 debian/patches/1001-webkit2gtk4.1.patch create mode 100644 debian/patches/series diff --git a/debian/control b/debian/control index b8a44ce..4bd2e91 100644 --- a/debian/control +++ b/debian/control @@ -25,7 +25,7 @@ Build-Depends: debhelper-compat (= 13), libspectre-dev, libsynctex-dev, libtiff-dev, - libwebkit2gtk-4.0-dev, + libwebkit2gtk-4.1-dev, libx11-dev, libxml2-dev, libxml2-utils, diff --git a/debian/patches/1001-webkit2gtk4.1.patch b/debian/patches/1001-webkit2gtk4.1.patch new file mode 100644 index 000..149071a --- /dev/null +++ b/debian/patches/1001-webkit2gtk4.1.patch @@ -0,0 +1,15 @@ +Description: Search for webkit2gtk-4.1. +Author: Unit 193 +Forwarded: no + +--- atril-1.26.0.orig/configure.ac atril-1.26.0/configure.ac +@@ -622,7 +622,7 @@ AC_ARG_ENABLE(epub, + + have_webkit="no" + if test "x$enable_epub" = "xyes"; then +-PKG_CHECK_MODULES(EPUB, webkit2gtk-4.0 >= $WEBKIT_REQUIRED \ ++PKG_CHECK_MODULES(EPUB, webkit2gtk-4.1 >= $WEBKIT_REQUIRED \ +libxml-2.0 >= $LIBXML_REQUIRED zlib,have_webkit=yes,have_webkit=no) + + if test "x$have_webkit" = "xyes"; then diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..108af4f --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +1001-webkit2gtk4.1.patch -- 2.35.1
Bug#1019696: workaround
Attached a suggestion from IRC for a workaround - the author is ok with sharing
it here -
I mostly just want to throw it there, for the case someone feels inspired by it
;)
Have tested it with gallery-dl, but not any more packages.
>From a8ac7e35dceda4dd732f2bff05bac51ffab5927f Mon Sep 17 00:00:00 2001
Subject: [PATCH] Fixing handling of github address
See bug #1019696
devscripts: uscan does not work with github anymore -
https://bugs.debian.org/1019696
---
lib/Devscripts/Uscan/WatchLine.pm | 16
lib/Devscripts/Uscan/http.pm | 2 +-
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/lib/Devscripts/Uscan/WatchLine.pm b/lib/Devscripts/Uscan/WatchLine.pm
index 272a8d8..d5494f8 100644
--- a/lib/Devscripts/Uscan/WatchLine.pm
+++ b/lib/Devscripts/Uscan/WatchLine.pm
@@ -726,6 +726,22 @@ EOF
$filepattern .= '(?:\?.*)?';
}
+# Handle github.com addresses specially
+if (!$self->shared->{bare} and $self->mode ne 'git' and $base =~ m%^https?://github\.com/% and $base !~ m%tags$%) {
+uscan_verbose "GitHub re-write rule. Abandon all hope ye who enter here.";
+my ($user, $repo) = $base =~ m%^https?://github\.com/([^\/]+)/([^\/]+)/%;
+$base =~ s%^https?://github\.com/%https://api.github.com/repos/%;
+if ($base =~ m%tags$%) {
+# Yes, the full path is needed. We can't use the provided filepattern as it needs to lack an extension.
+$filepattern = "https://api\\.github\\.com/repos/$user/$repo/tarball/refs/tags/(?:[-_v]?(\\d[-+.:~\\da-zA-Z]*))";
+} else {
+$filepattern =~ s%^.*/\)?%%;
+$filepattern =~ s%^%(?:https://api\\.github\\.com/repos/$user/$repo/tarball/(?:[-_v]?(\\d[-+.:~\\da-zA-Z]*))|https://github\\.com/$user/$repo/releases/download/v?(?:\\d[\\d\\.]*)/%;
+$filepattern =~ s%$%)%;
+}
+$self->searchmode('plain');
+}
+
# Handle pypi.python.org addresses specially
if ( !$self->shared->{bare}
and $base =~ m%^https?://pypi\.python\.org/packages/source/%) {
diff --git a/lib/Devscripts/Uscan/http.pm b/lib/Devscripts/Uscan/http.pm
index 0da9798..c08bff3 100644
--- a/lib/Devscripts/Uscan/http.pm
+++ b/lib/Devscripts/Uscan/http.pm
@@ -482,7 +482,7 @@ sub parse_href {
# exception, otherwise $mangled_version = 1
$mangled_version = '';
} else {
-$mangled_version = join(".",
+$mangled_version = join("",
map { $_ if defined($_) }
ref $match eq 'ARRAY' ? @$match : $href =~ m&^$_pattern$&);
}
--
2.35.1
Bug#1005719: mumble: diff for NMU version 1.3.4-1.1
Date: Mon, 12 Sep 2022 08:00:43 +0700
X-NMUDIFF-Version: 2.22.2
Control: tags 1005719 + pending
Dear maintainer,
I've prepared an NMU for mumble (versioned as 1.3.4-1.1) and
it was uploaded to DELAYED/3. Please feel free to tell me if it
should be delayed longer.
Regards.diff -Nru mumble-1.3.4/debian/changelog mumble-1.3.4/debian/changelog
--- mumble-1.3.4/debian/changelog 2021-03-01 16:29:33.0 +0700
+++ mumble-1.3.4/debian/changelog 2022-09-12 00:37:43.0 +0700
@@ -1,3 +1,12 @@
+mumble (1.3.4-1.1) unstable; urgency=medium
+
+ [ Steve Langasek ]
+ * Non-maintainer upload.
+ * debian/patches/openssl-3.0-compat.patch: port upstream patch for building against
+openssl 3.0. Closes: #1005719.
+
+ -- Judit Foglszinger Mon, 12 Sep 2022 00:37:43 +0700
+
mumble (1.3.4-1) unstable; urgency=medium
* New upstream bugfix release from 2021-02-10
diff -Nru mumble-1.3.4/debian/patches/55-openssl-3.0-compat.patch mumble-1.3.4/debian/patches/55-openssl-3.0-compat.patch
--- mumble-1.3.4/debian/patches/55-openssl-3.0-compat.patch 1970-01-01 07:00:00.0 +0700
+++ mumble-1.3.4/debian/patches/55-openssl-3.0-compat.patch 2022-09-11 23:34:00.0 +0700
@@ -0,0 +1,351 @@
+Description: support building against openssl 3.0
+ Based on upstream commit 02ddcf8c5dbd71e6e72c7ad81a6b66e62ea0fa6f
+Author: Terry Geng ,
+Steve Langasek
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1962721
+Last-Update: 2022-03-09
+Forwarded: not-needed
+
+Index: mumble-1.3.4/src/SelfSignedCertificate.cpp
+===
+--- mumble-1.3.4.orig/src/SelfSignedCertificate.cpp
mumble-1.3.4/src/SelfSignedCertificate.cpp
+@@ -32,107 +32,85 @@
+ return 1;
+ }
+
+-bool SelfSignedCertificate::generate(CertificateType certificateType, QString clientCertName, QString clientCertEmail, QSslCertificate &qscCert, QSslKey &qskKey) {
+- bool ok = true;
+- X509 *x509 = NULL;
+- EVP_PKEY *pkey = NULL;
+- RSA *rsa = NULL;
+- BIGNUM *e = NULL;
+- X509_NAME *name = NULL;
+- ASN1_INTEGER *serialNumber = NULL;
+- ASN1_TIME *notBefore = NULL;
+- ASN1_TIME *notAfter = NULL;
+- QString commonName;
+- bool isServerCert = certificateType == CertificateTypeServerCertificate;
+-
+- if (CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON) == -1) {
+- ok = false;
+- goto out;
++EVP_PKEY *SelfSignedCertificate::generate_rsa_keypair() {
++ EVP_PKEY *pkey = EVP_PKEY_new();
++ if (!pkey) {
++ return nullptr;
++ }
++
++#if OPENSSL_VERSION_NUMBER >= 0x1010L
++ EVP_PKEY_CTX *ctx = EVP_PKEY_CTX_new_id(EVP_PKEY_RSA, nullptr);
++ if (!ctx) {
++ return nullptr;
++ }
++ if (EVP_PKEY_keygen_init(ctx) <= 0) {
++ return nullptr;
++ }
++ if (EVP_PKEY_CTX_set_rsa_keygen_bits(ctx, 2048) <= 0) {
++ return nullptr;
++ }
++ if (EVP_PKEY_keygen(ctx, &pkey) <= 0) {
++ return nullptr;
++ }
++ EVP_PKEY_CTX_free(ctx);
++#else
++ RSA *rsa = RSA_new();
++ BIGNUM *e = BN_new();
++ if (!rsa) {
++ return nullptr;
+ }
+-
+- x509 = X509_new();
+- if (x509 == NULL) {
+- ok = false;
+- goto out;
+- }
+-
+- pkey = EVP_PKEY_new();
+- if (pkey == NULL) {
+- ok = false;
+- goto out;
+- }
+-
+- rsa = RSA_new();
+- if (rsa == NULL) {
+- ok = false;
+- goto out;
+- }
+-
+- e = BN_new();
+- if (e == NULL) {
+- ok = false;
+- goto out;
++ if (!e) {
++ return nullptr;
+ }
+ if (BN_set_word(e, 65537) == 0) {
+- ok = false;
+- goto out;
++ return nullptr;
+ }
+-
+- if (RSA_generate_key_ex(rsa, 2048, e, NULL) == 0) {
+- ok = false;
+- goto out;
++ if (RSA_generate_key_ex(rsa, 2048, e, nullptr) == 0) {
++ return nullptr;
+ }
+-
+ if (EVP_PKEY_assign_RSA(pkey, rsa) == 0) {
+- ok = false;
+- goto out;
+- }
+-
+- if (X509_set_version(x509, 2) == 0) {
+- ok = false;
+- goto out;
+- }
+-
+- serialNumber = X509_get_serialNumber(x509);
+- if (serialNumber == NULL) {
+- ok = false;
+- goto out;
+- }
+- if (ASN1_INTEGER_set(serialNumber, 1) == 0) {
+- ok = false;
+- goto out;
+- }
++ return nullptr;
++}
++ BN_free(e);
++ RSA_free(rsa);
++#endif
++ return pkey;
++}
+
+- notBefore = X509_get_notBefore(x509);
+- if (notBefore == NULL) {
+- ok = false;
+- goto out;
+- }
+- if (X509_gmtime_adj(notBefore, 0) == NULL) {
+- ok = false;
+- goto out;
++#define CHECK(statement) \
++ if (!(statement)) { \
++ ok = false; \
++ goto out;\
+ }
+
+- notAfter = X509_get_notAfter(x509);
+- if (notAfter == NULL) {
+- ok = false;
+- goto out;
+- }
+- if (X509_gmtime_adj(notAfter, 60*60*24*365*20) == NULL) {
+- ok = false;
+- goto out;
+- }
+-
+- if (X509_set_pubkey(x509, pkey) == 0) {
+- ok = false;
+- goto out;
+- }
++bool SelfSignedCertificate::generate(CertificateType certificateType, QString clientCertName, QString clientCertEmail,
++QSslCertificate &qscCert, QSslKey &qskKey) {
++ bool ok= true;
++ EVP_PKEY *pkey = nullptr;
++ X509 *x509
Bug#1008859: RFS: solarwolf/1.5+dfsg1-5 -- Collect the boxes and don't become mad
Thanks for uploading :) signature.asc Description: This is a digitally signed message part.
Bug#1008859: RFS: solarwolf/1.5+dfsg1-5 -- Collect the boxes and don't become mad
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "solarwolf": * Package name: solarwolf Version : 1.5+dfsg1-5 Upstream Author : Pete Shinners * URL : https://www.pygame.org/shredwheat/solarwolf/index.shtml * License : LGPL-2.1, GPL-2 * Vcs : https://salsa.debian.org/games-team/solarwolf Section : games Solarwolf has transparency problems with a few pictures, with pygame version 2.1.2, that is in sid now. This upload is to fix those. The source builds the following binary packages: solarwolf - Collect the boxes and don't become mad To access further information about this package, please visit the following URL: https://mentors.debian.net/package/solarwolf/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/solarwolf/solarwolf_1.5+dfsg1-5.dsc Changes since the last upload: solarwolf (1.5+dfsg1-5) unstable; urgency=low . * patches: Fixing transparency loss of powerup symbols/bullet time effect due to transition to pygame2 (Closes: #1008771) Regards, -- Judit Foglszinger signature.asc Description: This is a digitally signed message part.
Bug#1008771: solarwolf: Powerup graphics have transparency problems with pygame2
Package: solarwolf Version: 1.5+dfsg1-4 Severity: normal Hi, since the upgrade to pygame2, the power-up graphics no longer look properly - now they are black small squares with a little picture inside. They are both lacking transparency and the proper animated rund green background. Before they looked like /---\ <-- transparent background with green, animated picture | O | \---/ Now they look like x x <-- black, intransparent background O x x Please fix that :D -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages solarwolf depends on: ii python3 3.9.7-1 ii python3-pygame 2.1.2+dfsg-3 solarwolf recommends no packages. solarwolf suggests no packages. -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#1008129: RFS: solarwolf/1.5+dfsg1-4 [ITA] -- Collect the boxes and don't become mad
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "solarwolf": * Package name: solarwolf Version : 1.5+dfsg1-4 Upstream Author : Pete Shinners * URL : https://www.pygame.org/shredwheat/solarwolf/index.shtml * License : LGPL-2.1, GPL-2 * Vcs : https://salsa.debian.org/games-team/solarwolf Section : games Left out things like forwarding patches to upstream and adding an upstream metafile for now, because current upstream is dead, and it's not clear yet, if existing forks on the web can be counted as successors. I still would like to do an upload now to fix #497974, what I find a quite annoying bug, since it makes it impossible to completely disable sound in the game itself. The source builds the following binary packages: solarwolf - Collect the boxes and don't become mad To access further information about this package, please visit the following URL: https://mentors.debian.net/package/solarwolf/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/solarwolf/solarwolf_1.5+dfsg1-4.dsc Changes since the last upload: solarwolf (1.5+dfsg1-4) unstable; urgency=low . * control: New maintainer (Closes: #930142) * control: Adding Debian Games Team to uploaders. * control: Incrementing debhelper-compat to 13 * control: Adding dh-sequence-python3 * control: Adding Vcs-Git and Vcs-Browser fields * control: Bumping standards version to 4.6.0, no changes needed. * control: Correcting number of levels in long description s/48/60 * patches: Fixing game start sound not respecting sound settings. (Closes: #497974) Thanks to Daniel Watkins on whoms patch the fix is based on. * solarwolf.lintian_overrides: Overriding tag package-contains-documentation-outside-usr-share-doc, levels.txt is game data, not documentation. * Readme.source: explain how to retrieve the orig tarball and why no watch file is used. Regards, -- Judit Foglszinger signature.asc Description: This is a digitally signed message part.
Bug#1004487: ITP: fonts-fantasma -- font with a bit roundly-shaped and spiky/edgy-ended letters
Package: wnpp X-Debbugs-Cc: debian-de...@lists.debian.org Owner: Judit Foglszinger X-Debbugs-Cc: ur...@debian.org Severity: wishlist * Package name: fonts-fantasma Version : 1.0 Upstream Author : Froyo Tam * URL : https://github.com/froyotam/Fantasma * License : GPL-3 with font exception Description : font with a bit roundly-shaped and spiky/edgy-ended letters This is a proportional, sans serif font with a bit roundly-shaped and spiky/edgy-ended letters that can be used for headlines or graphics. It will be maintained in the Fonts team. signature.asc Description: This is a digitally signed message part.
Bug#982459: mdadm --examine in chroot without /proc,/dev,/sys mounted corrupts host's filesystem
Hi, > I could reproduce the bug with /dev *NOT* mounted in chroot. It seems > independent of /sys being mounted in chroot. tried again but still fail to reproduce (same configuration as last time, just with /proc mounted to chroot/proc, rest not mounted). Additionally tried it with a RAID0 and also to install a kernel with initrd to the chroot, though again didn't manage to get the host file system corrupted. (system used for that second try was RC2 of bullseye on virtualbox, raid was configured using the Debian installer) I think, I need to give up on this. Maybe someone else has an idea. signature.asc Description: This is a digitally signed message part.
Bug#956898: nm.debian.org: count "approved" processes as "done" from the AM point of view
Fixed in git. https://salsa.debian.org/nm-team/nm.debian.org/-/commit/2554b3160e9b67ec1b6c3fe3dc50ef1169066ca2 signature.asc Description: This is a digitally signed message part.
Bug#990070: irssi: -actcolor parameter for /highlight is not always respected
Package: irssi Version: 1.2.3-1 Severity: minor Hi, while trying to set two differently colored highlights for my nickname, depending on if it's the first word in the line or not, I observed the following. (as using a random word had the same results, I'll use the string "aaa" here) Commands used: /hilight -actcolor %G -color %G -regexp (?!^)aaa /hilight -actcolor %M -color %M -regexp ^aaa Expected behaviour: - If "aaa" is at the beginning of a line (eg aaa is this), there is a magenta colored highlight, both in the status bar and in the channel where "aaa" was written. - If "aaa" is somewhere else than the beginning of line (eg this is aaa), both highlights happen in green. Actual behaviour: - If "aaa" is at the beginning of a line (eg aaa is this), there is a magenta colored highlight in the channel where "aaa" was written, but the highlight in the status bar is green. - If "aaa" is somewhere else than the beginning of line (eg this is aaa), both highlights happen in green as expected. If /hilight -actcolor %M -color %M -regexp ^aaa is used alone, the coloring is as expected, so the two commands seem to interfere with each other; though not sure how, because if one command just would falsely match both cases, I'd expect both colors being wrong. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Kernel taint flags: 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages irssi depends on: ii libc6 2.31-11 ii libglib2.0-02.66.8-1 ii libperl5.32 5.32.1-3 ii libssl1.1 1.1.1k-1 ii libtinfo6 6.2+20201114-2 ii perl5.32.1-3 ii perl-base [perlapi-5.32.1] 5.32.1-3 irssi recommends no packages. Versions of packages irssi suggests: pn irssi-scripts -- no debconf information
Bug#988347: tuxpaint-stamps-default: Broken image placeholder is shown instead of melon stamp
Package: tuxpaint-stamps-default Version: 2014.08.23-3.1 Severity: minor Tags: patch Hi, the melon stamp in tuxpaint is broken (placeholder image for broken pictures is shown instead of the melon picture); from gimp's error message I assume that the reason is the picture being an inkscape svg instead of a plain svg: Opening '/usr/share/tuxpaint/stamps/food/fruit/cartoon/watermelon.svg' failed: Could not open '/usr/share/tuxpaint/stamps/food/fruit/cartoon/watermelon.svg' for reading: XML parse error: error code=201 (3) in (null):12:30: Namespace prefix inkscape for label on g is not defined Attached a patch with the same melon picture, just saved as plain svg. Description: Fixing melon stamp Instead of a melon, a placeholder for broken images is shown in tuxpaint. This patch replaces the current inkscape svg with a plain svg what brings the melon stamp back. Bug: Bug-Debian: https://bugs.debian.org/ Bug-Ubuntu: https://launchpad.net/bugs/ Forwarded: Reviewed-By: Last-Update: 2021-05-10 --- tuxpaint-stamps-2014.08.23.orig/stamps/food/fruit/cartoon/watermelon.svg +++ tuxpaint-stamps-2014.08.23/stamps/food/fruit/cartoon/watermelon.svg @@ -1,15 +1,30 @@ - http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd"; + xmlns:dc="http://purl.org/dc/elements/1.1/"; + xmlns:cc="http://creativecommons.org/ns#"; + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; + xmlns:svg="http://www.w3.org/2000/svg"; + xmlns="http://www.w3.org/2000/svg"; height="21cm" id="svg2" - width="21cm"> + width="21cm" + version="1.1"> + + + +image/svg+xml +http://purl.org/dc/dcmitype/StillImage"; /> + + + + + + id="layer1"> signature.asc Description: This is a digitally signed message part.
Bug#982459: mdadm --examine in chroot without /proc,/dev,/sys mounted corrupts host's filesystem
tags 982459 +moreinfo user debian-rele...@lists.debian.org usertags -1 + bsp-2021-04-AT-Salzburg thank you Hi, can you reproduce this bug on bullseye? (4.1-11) If so, what is your configuration (VM used, type of RAID)? Are all three conditions (/proc, /dev and /sys not mounted) required or does this also happen, if eg /dev and /sys are there but not /proc? If it still occurs until there would be a proper fix by upstream, a workaround like "are we in a chroot, if so, are the required things mounted, if not, fail", could be used to avoid the file system corruption. My own observations: Could not reproduce in virtualbox (both chroot and host system using recent bullseye), using RAID1, /dev/md0 on / type ext4 (rw,relatime,errors=remount-ro) # chroot chroot / # mdadm --examine --scan --config=partitions / # mdadm: cannot open /proc/partitions / # mdadm: No devices listed in partitions (in background on host running the mentioned find / command) No filesystem corruption after over 15 minutes, running the mdadm command in chroot several times didn't make a difference on that. signature.asc Description: This is a digitally signed message part.
Bug#985324: unblock: solarwolf/1.5+dfsg1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: ur...@debian.org, a...@debian.org Please unblock package solarwolf [ Reason ] The change fixes grave bug #984673 by replacing deprecated (and since python 3.9 removed) method isAlive() of threading.Thread with its successor is_alive(). [ Impact ] solarwolf currently fails to start in testing and will be autoremoved on April 04. [ Tests ] (manual) With the change can start and play the game, without not. [ Risks ] Change is trivial and the recommeded fix in the python 3.9 release notes [1] - "The isAlive() method of threading.Thread has been removed. It was deprecated since Python 3.8. Use is_alive() instead." [1] https://docs.python.org/3/whatsnew/3.9.html [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock solarwolf/1.5+dfsg1-3 diff -Nru solarwolf-1.5+dfsg1/debian/changelog solarwolf-1.5+dfsg1/debian/changelog --- solarwolf-1.5+dfsg1/debian/changelog 2020-03-23 06:22:20.0 +0700 +++ solarwolf-1.5+dfsg1/debian/changelog 2021-03-15 06:25:59.0 +0700 @@ -1,3 +1,11 @@ +solarwolf (1.5+dfsg1-3) unstable; urgency=medium + + * QA upload. + * Fix runtime error Thread object has no attribute isAlive. +Thanks to Judit Foglszinger for the patch. (Closes: #984673) + + -- Markus Koschany Mon, 15 Mar 2021 00:25:59 +0100 + solarwolf (1.5+dfsg1-2) unstable; urgency=medium * QA upload. diff -Nru solarwolf-1.5+dfsg1/debian/patches/replacing-isAlive-with-is_alive.patch solarwolf-1.5+dfsg1/debian/patches/replacing-isAlive-with-is_alive.patch --- solarwolf-1.5+dfsg1/debian/patches/replacing-isAlive-with-is_alive.patch 1970-01-01 07:00:00.0 +0700 +++ solarwolf-1.5+dfsg1/debian/patches/replacing-isAlive-with-is_alive.patch 2021-03-15 06:25:59.0 +0700 @@ -0,0 +1,33 @@ +Description: Replacing isAlive with is_alive + solarwolf fails to start because of an AttributeError: Thread object + has no attribute isAlive. The function was removed in Python 3.9. The patch + replaces it with the new one is_alive(). +--- +Bug-Debian: https://bugs.debian.org/984673 +Forwarded: no +Reviewed-By: Markus Koschany +Last-Update: 2021-03-12 + +--- solarwolf-1.5+dfsg1.orig/code/gameinit.py solarwolf-1.5+dfsg1/code/gameinit.py +@@ -161,7 +161,7 @@ class GameInit: + + now = pygame.time.get_ticks() + #we let the screen stay up for at about 1 second +-if not self.thread.isAlive(): ++if not self.thread.is_alive(): + if load_finished_status >= 0: + if now-self.starttime > 1200: + self.quit() +--- solarwolf-1.5+dfsg1.orig/code/gamenews.py solarwolf-1.5+dfsg1/code/gamenews.py +@@ -234,7 +234,7 @@ class GameNews: + self.clocks += 1 + self.cleartext() + +-if self.thread and (not self.thread.isAlive() and self.success): ++if self.thread and (not self.thread.is_alive() and self.success): + self.download_finished() + + clearme = None + diff -Nru solarwolf-1.5+dfsg1/debian/patches/series solarwolf-1.5+dfsg1/debian/patches/series --- solarwolf-1.5+dfsg1/debian/patches/series 2019-09-29 21:12:23.0 +0700 +++ solarwolf-1.5+dfsg1/debian/patches/series 2021-03-15 06:25:59.0 +0700 @@ -2,3 +2,4 @@ music.patch spelling.patch python3.patch +replacing-isAlive-with-is_alive.patch signature.asc Description: This is a digitally signed message part.
Bug#976400: RFS: braillefont/1.0-3 -- Prints a bitmapped version of a text using Unicode Braille symbols
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "braillefont": * Package name: braillefont Version : 1.0-3 Upstream Author : Adam Borowski * URL : https://github.com/kilobyte/braillefont * License : CC0 * Vcs : https://salsa.debian.org/debian/braillefont Section : text It builds those binary packages: braillefont - Prints a bitmapped version of a text using Unicode Braille symbols To access further information about this package, please visit the following URL: https://mentors.debian.net/package/braillefont/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/b/braillefont/braillefont_1.0-3.dsc Changes since the last upload: braillefont (1.0-3) unstable; urgency=medium . * control: bumping standards version - no changes needed. * rules: converting to dh * control: changing section from games to text * copyright: adding upstream contact * source: overriding lintian tag maintainer-manual-page * patches: patching Makefile to support build flags * rules: removing override for dh_auto_build * patches: fixing possible buffer overflow in fgetws * upstream/metadata: adding file mostly as generated by lintian-brush Regards, -- Judit Foglszinger signature.asc Description: This is a digitally signed message part.
Bug#972380: braillefont FTBFS
tags 972380 +pending thanks Fixed in vcs. signature.asc Description: This is a digitally signed message part.
Bug#964867: crashes when clicking on something not a link in New Game menu
Package: monsterz
Version: 0.7.1-11+b1
Severity: minor
to reproduce:
New Game-> *click on something, that is not a link* -> *crashes*
For example I clicked into the upper left corner:
Traceback (most recent call last):
File "/usr/share/games/monsterz/monsterz.py", line 2043, in
main()
File "/usr/share/games/monsterz/monsterz.py", line 2038, in main
monsterz.go()
File "/usr/share/games/monsterz/monsterz.py", line 1288, in go
iterator()
File "/usr/share/games/monsterz/monsterz.py", line 1565, in iterate_new
elif event.type == MOUSEBUTTONDOWN and narea >= 10:
TypeError: '>=' not supported between instances of 'NoneType' and 'int'
A quick fix would be to check if narea is None.
--- monsterz.py 2020-07-11 20:26:48.0 +0700
+++ /tmp/monsterz.py2020-07-11 20:25:58.314438447 +0700
@@ -1562,7 +1562,7 @@
system.play('whip')
self.status = STATUS_MENU
return
-elif event.type == MOUSEBUTTONDOWN and narea >= 10:
+elif event.type == MOUSEBUTTONDOWN and narea is not None and narea
>= 10:
system.play('whip')
if narea == ACTION_MOREMONSTERZ:
if items < 8:
signature.asc
Description: This is a digitally signed message part.
Bug#956818: developers-reference: contradictory information about removing packages from Incoming
Added a patch for clarifying removability from upload queue. >From c354889d127882bcb123c6c30f1d96a3bb09d5fe Mon Sep 17 00:00:00 2001 From: Judit Foglszinger Date: Fri, 24 Apr 2020 05:35:04 +0700 Subject: [PATCH] Adding footnote clarifying removability of packages from the upload queue --- source/pkgs.rst | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/source/pkgs.rst b/source/pkgs.rst index d95cab5..ae3e8ab 100644 --- a/source/pkgs.rst +++ b/source/pkgs.rst @@ -1144,7 +1144,7 @@ Removing packages from ``Incoming`` In the past, it was possible to remove packages from ``incoming``. However, with the introduction of the new incoming system, this is no -longer possible. Instead, you have to upload a new revision of your +longer possible. [4]_ Instead, you have to upload a new revision of your package with a higher version than the package you want to replace. Both versions will be installed in the archive but only the higher version will actually be available in ``unstable`` since the previous version @@ -2456,3 +2456,8 @@ this, contact ``debian-de...@lists.debian.org`` or .. [3] ITS is shorthand for *"Intend to Salvage"* + +.. [4] + Though, if a package still is in the in the upload queue and hasn't + been moved to Incoming yet, it can be removed. (see + :ref:`upload-ftp-master`) -- 2.25.1 signature.asc Description: This is a digitally signed message part.
Bug#953608: nm.debian.org: Some data belonging to legacy processes is no longer shown on the site
> Could you give me an example of a legacy process which doesn't show > mails for you? One of your recent mailbox fixes also fixed that issue, so no longer :) signature.asc Description: This is a digitally signed message part.
Bug#953608: nm.debian.org: Some data belonging to legacy processes is no longer shown on the site
Package: nm.debian.org
Severity: minor
Some data belonging to legacy processes is no longer shown on the site
- Mailbox view (https://nm.debian.org/legacy/display-mail-archive/$PNR)
doesn't show any mails
- On the process page (https://nm.debian.org/legacy/process/$PNR)
-- "Personal information"
advocates are not shown and neither the former graphic for Mailbox stats.
-- "Process log"
"Changed by" does not show uids
- On pages of Persons and AMs (https://nm.debian.org/person/$uid)
Old style process tables are also missing advocates
added a patch for the advocates and "Changed by" parts.>From 9bfbcd607d8e233302d9f0fe20c468117a825afd Mon Sep 17 00:00:00 2001
From: Judit Foglszinger
Date: Wed, 11 Mar 2020 05:39:13 +0600
Subject: [PATCH] fix some references to uid (now person.ldap_fields.uid)
---
legacy/templates/legacy/process.html | 4 ++--
public/templates/public/person_process_table.html | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/legacy/templates/legacy/process.html b/legacy/templates/legacy/process.html
index 61c63f9..63c171f 100644
--- a/legacy/templates/legacy/process.html
+++ b/legacy/templates/legacy/process.html
@@ -17,7 +17,7 @@
{% trans "Advocate" %}{{process.advocates.count|pluralize}}
{% for a in process.advocates.all %}
-{{a.uid}}{% if not forloop.last %},{% endif %}
+{{a.person.ldap_fields.uid}}{% if not forloop.last %},{% endif %}
{% endfor %}
@@ -103,7 +103,7 @@
{% endif %}
{{l.logdate|date:"Y-m-d"}}
-{{l.changed_by.uid}}
+{{l.changed_by.person.ldap_fields.uid}}
{{l.progress|desc_progress}}
{% if visitor.am %}
diff --git a/public/templates/public/person_process_table.html b/public/templates/public/person_process_table.html
index 91a965c..9aa9f30 100644
--- a/public/templates/public/person_process_table.html
+++ b/public/templates/public/person_process_table.html
@@ -30,7 +30,7 @@
{% for a in p.advocates.all %}
-{{a.uid}}{% if not forloop.last %},{% endif %}
+{{a.person.ldap_fields.uid}}{% if not forloop.last %},{% endif %}
{% endfor %}
--
2.25.1
signature.asc
Description: This is a digitally signed message part.
Bug#952940: nm.debian.org: show sender/subject/date of current mail at the top of full screen mail view
Package: nm.debian.org Severity: wishlist At the top of the full screen mail view one could show sender/subject/date of the current mail, maybe instead of the text "Mail Archive". signature.asc Description: This is a digitally signed message part.
Bug#952939: nm.debian.org: some templates in process/templates/ use blocktrans with variables that get ignored
Package: nm.debian.org
Severity: minor
Tags: patch
Text for approved requirements is incomplete:
It shows "This requirement has been approved by ago.",
when it should eg. show
"This requirement has been approved by Housekeeping Robot
7 months, 2 weeks ago."
Added a patch for using '{% blocktrans with variable_name=something %}' syntax
for requirement_status_widget.html and for a few other templates from process/
templates/process/
>From 34caf407ea85b6042490c761e191a5d045f261cb Mon Sep 17 00:00:00 2001
From: Judit Foglszinger
Date: Mon, 2 Mar 2020 08:01:14 +0600
Subject: [PATCH] use 'with' in blocktrans for variable substitution
---
process/templates/process/cancel.html | 11 ++-
.../templates/process/requirement_status_widget.html | 6 +++---
process/templates/process/show.html | 1 +
process/templates/process/statement_create.html | 2 +-
4 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/process/templates/process/cancel.html b/process/templates/process/cancel.html
index 755843d..8ef2d9a 100644
--- a/process/templates/process/cancel.html
+++ b/process/templates/process/cancel.html
@@ -1,4 +1,5 @@
{% extends "process/nm2-base.html" %}
+{% load nm %}
{% load i18n %}
{% block content %}
@@ -14,12 +15,12 @@ system. Follow the link for instructions.{% endblocktrans %}
{% else %}
{% if process.applying_for == "dd_e" %}
- {% blocktrans %}On {{process.started|date:"F d, Y"}} the
+ {% blocktrans with started_on=process.started|date:"F d, Y" person_ldap_uid=process.person.ldap_fields.uid %}On {{started_on}} the
https://wiki.debian.org/qa.debian.org/MIATeam";>Missing In Action
-team sent a "Where Are Thou?" ping message to {{process.person.ldap_fields.uid}}
+team sent a "Where Are Thou?" ping message to {{person_ldap_uid}}
communicating the intention of closing the account after some time.{% endblocktrans %}
- {% blocktrans %}If you are {{process.person.fullname}} and consider
+ {% blocktrans with person_fullname=person.fullname %}If you are {{person_fullname}} and consider
yourself still active, you can use this page to let the MIA team know.{% endblocktrans %}
{% if not process.person.fpr %}
@@ -34,8 +35,8 @@ in the Debian keyring.{% endblocktrans %}
what you do or are going to do in Debian. The text will only be visible to
Front Desk / MIA team unless you tick the box to make it public.{% endblocktrans %}
{% else %}
- {% blocktrans %}By submitting this form you can cancel the process for
-becoming {{ process.applying_for|desc_status }} started on {{process.started|date:'F d, Y'}}.{% endblocktrans %}
+ {% blocktrans with applying_for=process.applying_for|desc_status started_on=process.started|date:'F d, Y' %}By submitting this form you can cancel the process for
+becoming {{ applying_for }} started on {{started_on}}.{% endblocktrans %}
{% endif %}
diff --git a/process/templates/process/requirement_status_widget.html b/process/templates/process/requirement_status_widget.html
index acc8dde..9469195 100644
--- a/process/templates/process/requirement_status_widget.html
+++ b/process/templates/process/requirement_status_widget.html
@@ -1,9 +1,9 @@
{% load i18n %}
{% if requirement.approved_by %}
- {% blocktrans %}This requirement has been approved by
-{{requirement.approved_by}}
-{{requirement.approved_time|timesince}} ago.{% endblocktrans %}
+ {% blocktrans with req_approved_by_absolute_url=requirement.approved_by.get_absolute_url req_approved_by=requirement.approved_by requirement_approved_time=requirement.approved_time|timesince%}This
+requirement has been approved by {{req_approved_by}}
+{{requirement_approved_time}} ago.{% endblocktrans %}
{% else %}
{% if status.satisfied %}
{% trans "This requirement looks ready for approval, but has not been approved yet." %}
diff --git a/process/templates/process/show.html b/process/templates/process/show.html
index 27835ef..042faa0 100644
--- a/process/templates/process/show.html
+++ b/process/templates/process/show.html
@@ -187,6 +187,7 @@ but not frozen for review.{% endblocktrans %}
{% comment %} TODO: Requires porting stats backend to new Process
+ NOTE: blocktrans needs to be adjusted to use syntax {% blocktrans with name=something%} {{name}}...
{% if mbox_stats %}
{% trans "Mailbox stats" %}
{% blocktrans %}{{mbox_stats.date_first_py|date:"Y-m-d"}} to {{mbox_stats.date_last_py|date:"Y-m-d"}},
diff --git a/process/templates/process/statement_create.html b/process/templates/process/statement_create.html
index a7ad20d..175db73 100644
--- a/process/templates/process/statement_create.html
+++ b/process/templates/process/statement_create.html
@@ -28,7 +28,7 @@ a need of manual validation of its content:{% endblocktrans %}
{% endif %}
-{% blocktrans %}Use gpg
Bug#952888: nm.debian.org: Don't accept mails for NM mailboxes a while after processes are closed
Package: nm.debian.org Severity: wishlist Since at one point spammers start to target mailboxes, it might make sense to not accept more emails a while after a process has been closed, maybe one or two months. comment from enrico: "The mail processing script isn't very smart unfortunately at the moment, to avoid bringing up django every time a mail arrives, although it could just enqueue the mails, and the ping django for actually injecting them" signature.asc Description: This is a digitally signed message part.
Bug#940944: nm.debian.org: activity ping should mention what's missing
Hi, added a patch to make the ping messages for stuck processes more informative. - list missing requirements - for the case of a missing advocate mention, that a process can be reopened - for the case of keychecks, mention in the first ping, that this isn't taken in account for the ping. The messages would look like the below, depending on what exactly is missing. First ping: Hello, the process at https://example.com/process/40 looks stuck. This message was triggered because the following requirements aren't fulfilled: - Advocate - Declaration of intent - SC/DFSG/DMUP agreement If nothing happens, the process will be automatically closed a week from now. -> Don't worry about Key consistency checks - it's not taken into regard here, because it needs manual approval. -> If you have an advocate that just needs some more time to react, the process can be reopened. If you need help with anything, please mail n...@debian.org. Housekeeping Robot for Front Desk -- second ping: Hello, the process at https://example.com/process/40 looks stuck. This message was triggered because the following requirements aren't fulfilled: - Advocate - Declaration of intent - SC/DFSG/DMUP agreement A week has passed from the last ping with no action, I'll now close the process. Feel free to reapply in the future. -> If you have an advocate that just needs some more time to react, the process can be reopened. If you need help with anything, please mail n...@debian.org. Housekeeping Robot for Front Desk>From 9fbabb4e9e16b2f1d7161bbcdd7b5e53353eb6e0 Mon Sep 17 00:00:00 2001 From: Judit Foglszinger Date: Sun, 1 Mar 2020 11:04:37 +0600 Subject: [PATCH] make ping messages more informative. --- process/maintenance.py | 58 +++--- 1 file changed, 54 insertions(+), 4 deletions(-) diff --git a/process/maintenance.py b/process/maintenance.py index 6e0821e..206ddc7 100644 --- a/process/maintenance.py +++ b/process/maintenance.py @@ -15,21 +15,71 @@ def ping_stuck_processes(stuck_cutoff, audit_author, logdate=None): if entry.logdate > stuck_cutoff: continue +# get missing requirements for process in order +# to be able to issue a more meaningful ping message + +missing_requirements = [] +# additional information appended to ping mail - +# keycheck does not count as missing requirement here, but is often misinterpreted, +# so append a message, if it is not approved yet. +keycheck_message = "" +# an advocate might take longer than one week to react +# and the applicant might not be able to influence that, +# so append a message, that a closed process can be reopened. +advocate_message = "" + +for r in process.requirements.all(): +if r.type == "advocate" or r.type == "intent" or r.type == "sc_dmup": +if r.approved_by == None: +missing_requirements.append(r) +# add additional messages for missing advocate and keycheck +if r.type == "keycheck" and r.approved_by == None: +keycheck_message = "-> Don't worry about "+str(r)+\ +""" - + it's not taken into regard here, because it needs manual approval. +""" +if r.type == "advocate" and r.approved_by == None: +advocate_message = \ +"""-> If you have an advocate that just needs some more time to react, + the process can be reopened. +""" +# not having any missing requirements here would be an error, +# but let's don't have it look weird in the mail and omit the additional text +if len(missing_requirements) <= 0: +msg_str = "" +else: +# differentiating singular/plural +s = "" if len(missing_requirements) < 2 else "s" +be_form = "is" if len(missing_requirements) < 2 else "are" +msg_str = \ +""" +This message was triggered because the following requirement"""+s+" "+be_form+"n't"+\ +""" fulfilled: + +""" +for r in missing_requirements: +msg_str = msg_str + "- "+str(r)+"\n" + if not already_pinged: # Detect first instance of processes stuck early: X days from # last log, no previous ping message -ping_process(audit_author, process, message=""" +msg_str = msg_str +\ +""" If nothing happens, the process will be automatically closed a week from now. -""") +"""+keycheck_message+advocate_me
Bug#950763: ITP: braillefont -- Prints a bitmapped version of a text using Unicode Braille symbols
Version : 0~20161007~14b2b1a signature.asc Description: This is a digitally signed message part.
Bug#950763: ITP: braillefont -- Prints a bitmapped version of a text using Unicode Braille symbols
s/Version : git/Version : 0.0.20161007~14b2b1a/ signature.asc Description: This is a digitally signed message part.
Bug#950763: ITP: braillefont -- Prints a bitmapped version of a text using Unicode Braille symbols
Package: wnpp Owner: Judit Foglszinger Severity: wishlist * Package name: braillefont Version : git Upstream Author : Adam Borowski * URL : https://github.com/kilobyte/braillefont * License : Public Domain (CC0) Programming Lang: C Description : Prints a bitmapped version of a text using Unicode Braille symbols braillefont runs interactively on the console - one can enter a (short) text, that will be converted into a bitmapped version and printed using the Braille range of Unicode. I consider the package to be useful, because it's fun to play around with it and it can make nice mail signatures. I use it. Not every day, considered the limited scope, but from time to time, if I get bored. For now, I plan to maintain it alone. It's a very small package needing nothing outside the standard C library, so should be doable by one person. signature.asc Description: This is a digitally signed message part.
Bug#946662: nm.debian.org: Attempting to import nm-mock.json throws exceptions
Hi, > mhh. In this case, shouldn't we directly change the email to be the > same of the lookup_key? Or anyway fix the original data. > Or teach the importer to reverse the mangling. Indeed. Changing nm-mock.json is rather a workaround to be able to proceed. Didn't look into that yet, also not sure why email is needed for looking up someone at all, would have expected, that only lookup key is used for that. > Doesn't this error reports tha the fpr wasn't previously .save()'d? Yes, but saving didn't help either, because that ended up with an IntegrityError due to fingerprint objects missing person_id, guess because of the not expected double import of fingerprints. signature.asc Description: This is a digitally signed message part.
Bug#946662: nm.debian.org: Attempting to import nm-mock.json throws exceptions
Attached a patch for importing processes in a second step after fingerprints
are imported.
From 3c99d71d91a54efcc229c86db87ac81fc0ccd366 Mon Sep 17 00:00:00 2001
From: Judit Foglszinger
Date: Thu, 26 Dec 2019 06:20:48 +0600
Subject: [PATCH] Importing processes separately in a second step
When importing processes, access to fingerprints of all persons is needed.
---
backend/export.py | 30 ++
1 file changed, 30 insertions(+)
diff --git a/backend/export.py b/backend/export.py
index 49ec8ff..71a07b0 100644
--- a/backend/export.py
+++ b/backend/export.py
@@ -140,6 +140,32 @@ class ImporterV1:
for lp in legacy_processes:
person._rels["legacy_processes"].append(self.import_legacy_process(person, lp))
+return person
+
+def import_person_processes(self, data):
+s = bserializers.PersonExportSerializer(data=data, context=self.context)
+if not s.is_valid():
+raise RuntimeError("Invalid Person record {}: {}".format(data, s.errors))
+
+am = s.validated_data.pop("am")
+fprs = s.validated_data.pop("fprs")
+audit_log = s.validated_data.pop("audit_log")
+legacy_processes = s.validated_data.pop("legacy_processes")
+processes = s.validated_data.pop("processes")
+
+lookup_key = data["lookup_key"]
+person = self.people.get(lookup_key)
+
+if person is None:
+person = bmodels.Person(**s.validated_data)
+person._rels = {
+"am": None,
+"fprs": [],
+"audit_log": [],
+"legacy_processes": [],
+"processes": [],
+}
+
for pr in processes:
person._rels["processes"].append(self.import_process(person, pr))
@@ -365,6 +391,10 @@ class ImporterV1:
self.import_person(person, shallow=True)
for person in data["people"]:
self.import_person(person, shallow=False)
+# Importing processes separately, since this requires fingerprints of
+# all people to be imported
+for person in data["people"]:
+self.import_person_processes(person)
for apikey in data["apikeys"]:
pass # TODO
--
2.24.0
signature.asc
Description: This is a digitally signed message part.
Bug#946662: nm.debian.org: Attempting to import nm-mock.json throws exceptions
Package: nm.debian.org
Severity: wishlist
While attempting to import nm-mock.json, several exceptions are raised.
1) for legacy processes it's assumed, that "manager" cannot be null,
but for example emeritus processes have no AM.
Attached a patch for that.
2) key errors when looking up people with an email address as lookup_key;
in most cases this affects the house keeping robot closing processes,
but also also (currently) two people with @users.alioth.debian.org
as username, who uploaded statements.
---
File "/tmp/nm.debian.org/backend/export.py", line 144, in import_person
person._rels["processes"].append(self.import_process(person, pr))
File "/tmp/nm.debian.org/backend/export.py", line 231, in import_process
"closed_by": self.people[closed_by] if closed_by else None,
KeyError: 'nm AT debian.org'
---
As a workaround in the json-file, one can replace the
redacted (@example.org) email field with the value from the lookup_key:
{
"username": "__housekeeping__",
...
"lookup_key": "nm AT debian.org",
- "email": "nm_debian@example.org",
+ "email": "nm AT debian.org",
3) key errors when looking up fingerprints for statements
in non legacy processes
File "/tmp/nm.debian.org/backend/export.py", line 263, in import_requirement
req._rels["statements"].append(self.import_statement(req, stm))
File "/tmp/nm.debian.org/backend/export.py", line 278, in import_statement
"fpr": self.fprs[fpr] if fpr else None,
KeyError: '1234567891234567891234567891234567891234'
At the time those statements are imported,
only fingerprints, that belong to people earlier in the json-file
are available in the fpr object.
(For example, if I move myself to the top of the file,
fpr only consists of my fingerprint).
Importing all fingerprints already in the first (shallow) run
of import_person() only apparently solves the problem by
having all fingerprints available and being able to import the whole file.
But in the end the attempt fails with
---
File "/tmp/nm.debian.org/backend/export.py", line 418, in save
st.save()
File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 764, in
save
"unsaved related object '%s'." % field.name
ValueError: save() prohibited to prevent data loss due to unsaved related
object 'fpr'.
---
As a rather ugly workaround, that leads to wrongly signed statements,
but finally allows importing nm-mock.json,
one can use the first fingerprint from fpr for each statement:
--- a/backend/export.py
+++ b/backend/export.py
@@ -275,7 +275,7 @@ class ImporterV1:
stm = pmodels.Statement(**s.validated_data)
stm._rels = {
"uploaded_by": self.people[uploaded_by] if uploaded_by else None,
-"fpr": self.fprs[fpr] if fpr else None,
+"fpr": self.fprs[list(self.fprs.keys())[0]] if fpr else None,
}
return stm
From 5b8695569d691fb3836630a7aeab0b9f19e57b3b Mon Sep 17 00:00:00 2001
From: Judit Foglszinger
Date: Thu, 12 Dec 2019 08:07:03 +0600
Subject: [PATCH 1/2] manager for legacy processes can be null
this is the case for eg. emeritus processes
---
backend/export.py | 2 +-
backend/serializers.py | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/backend/export.py b/backend/export.py
index 94ffddf..49ec8ff 100644
--- a/backend/export.py
+++ b/backend/export.py
@@ -191,7 +191,7 @@ class ImporterV1:
p = bmodels.Process(**s.validated_data)
p._rels = {
"person": person,
-"manager": self.ams[manager],
+"manager": self.ams[manager] if manager else None,
"advocates": [self.people[x] for x in advocates],
"log": [self.import_legacy_process_log(p, x) for x in log]
}
diff --git a/backend/serializers.py b/backend/serializers.py
index 1d0d0ca..4b32dff 100644
--- a/backend/serializers.py
+++ b/backend/serializers.py
@@ -54,7 +54,7 @@ class LogExportSerializer(serializers.ModelSerializer):
class LegacyProcessExportSerializer(serializers.ModelSerializer):
log = LogExportSerializer(many=True)
advocates = PersonKeyField(many=True)
-manager = AMKeyField()
+manager = AMKeyField(allow_null=True)
class Meta:
model = bmodels.Process
--
2.24.0
signature.asc
Description: This is a digitally signed message part.
Bug#884857: developers-reference: clarify process on retirement/improve wording
Updated both descriptions. From 72725a668cf8e8783f21503368b56df697a6a4c0 Mon Sep 17 00:00:00 2001 From: Judit Foglszinger Date: Mon, 23 Sep 2019 00:29:33 +0700 Subject: [PATCH 1/2] fix description for retiring --- source/developer-duties.rst | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/source/developer-duties.rst b/source/developer-duties.rst index 0502029..a163ffb 100644 --- a/source/developer-duties.rst +++ b/source/developer-duties.rst @@ -240,12 +240,21 @@ the following steps: - Orphan all your packages, as described in :ref:`orphaning`. Remove yourself from uploaders for co-maintained packages. +- If you received mails via a @debian.org e-mail alias (e.g. + pr...@debian.org) and would like to get removed, open a RT ticket for + the Debian System Administrators. Just send an e-mail to + ``ad...@rt.debian.org`` with "Debian RT" somewhere in the subject + stating from which aliases you'd like to get removed. + - Use the link https://nm.debian.org/process/emeritus to log in to - nm.debian.org [2]_, request emeritus status and write a goodby + nm.debian.org, request emeritus status and write a goodbye message that will be automatically posted on debian-private. - This also automatically notifies the MIA team, so that they can - check if some of your packages still need orphaning. + Authentification to the NM site requires an SSO browser certificate. + You can generate them on https://sso.debian.org. + + In the case you run into problems opening the retirement process + yourself, contact NM front desk using ``n...@debian.org`` It is important that the above process is followed, because finding inactive developers and orphaning their packages takes significant time -- 2.23.0 From bdb946330d97c26bca42fa8032dd45b9e5f4b3cc Mon Sep 17 00:00:00 2001 From: Judit Foglszinger Date: Mon, 23 Sep 2019 00:38:53 +0700 Subject: [PATCH 2/2] fix description for returning from retirement --- source/developer-duties.rst | 14 ++ 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/source/developer-duties.rst b/source/developer-duties.rst index a163ffb..ff544b8 100644 --- a/source/developer-duties.rst +++ b/source/developer-duties.rst @@ -270,8 +270,12 @@ in :ref:`s3.7` is followed, and "removed" otherwise. Retired developers with an "emeritus" account can get their account re-activated as follows: -- Use the link https://nm.debian.org/wizard/process/return to log in to - nm.debian.org [2]_ and request to return from emeritus status. +- Get access to an alioth account (either by remembering the + credentials for your old guest account or by requesting a new one as + decribed at `SSO Debian wiki page + <https://wiki.debian.org/DebianSingleSignOn#If_you_ARE_NOT_.28yet.29_a_Debian_Developer>`__. + +- Mail ``n...@debian.org`` for further instructions. - Go through a shortened NM process (to ensure that the returning developer still knows important parts of P&P and T&S). @@ -282,9 +286,3 @@ again. .. [1] This is so that the message can be easily filtered by people who don't want to read vacation notices. - -.. [2] - Login on nm.debian.org requires an SSO browser certificate. - (you can generate them on https://sso.debian.org) - If you cannot access SSO, the recommended way of action is to - mail NM frontdesk using ``n...@debian.org``. -- 2.23.0 signature.asc Description: This is a digitally signed message part.
Bug#884857: developers-reference: clarify process on retirement/improve wording
Hi, > Can I recommend we keep the alternative available (with a somewhat lower > precedence, as retirment through nm.d.o are a tad easier to process for > everybody involved). Wouldn't it be more advisable to write something like "in case you fail to authenticate to the NM site or have other issues to open the retirement/return process yourself, contact front desk" instead of keeping the former more cumbersome way of retirement alife? That also would adress "not advertise NM as the SSO support team". > This is still true. Nobody is actually checking the aliases to see if > any need updating in the retirement/removal process, so really if > somebody is receiving mails from an alias it needs to be updated > manually. Ok. Also, what about the gpg key? Are people asked to prove they still control their key? If so, in which way? signature.asc Description: This is a digitally signed message part.
Bug#884857: developers-reference: clarify process on retirement/improve wording
tags 884857 +patch quit Added patch for updating retirement/return description to new process. From 63c8e928cc877fe310276876e09b13c9337b00d3 Mon Sep 17 00:00:00 2001 From: Judit Foglszinger Date: Sat, 21 Sep 2019 16:25:29 +0700 Subject: [PATCH] describe new process for emeritus --- source/developer-duties.rst | 37 + 1 file changed, 17 insertions(+), 20 deletions(-) diff --git a/source/developer-duties.rst b/source/developer-duties.rst index 1a20790..0502029 100644 --- a/source/developer-duties.rst +++ b/source/developer-duties.rst @@ -237,21 +237,15 @@ Retiring If you choose to leave the Debian project, you should make sure you do the following steps: -1. Orphan all your packages, as described in :ref:`orphaning`. +- Orphan all your packages, as described in :ref:`orphaning`. + Remove yourself from uploaders for co-maintained packages. -2. Send an gpg-signed email announcing your retirement to - ``debian-priv...@lists.debian.org``. +- Use the link https://nm.debian.org/process/emeritus to log in to + nm.debian.org [2]_, request emeritus status and write a goodby + message that will be automatically posted on debian-private. -3. Notify the Debian key ring maintainers that you are leaving by - opening a ticket in Debian RT by sending a mail to - ``keyr...@rt.debian.org`` with the words "Debian RT" somewhere in the - subject line (case doesn't matter). - -4. If you received mails via a @debian.org e-mail alias (e.g. - pr...@debian.org) and would like to get removed, open a RT ticket for - the Debian System Administrators. Just send an e-mail to - ``ad...@rt.debian.org`` with "Debian RT" somewhere in the subject - stating from which aliases you'd like to get removed. + This also automatically notifies the MIA team, so that they can + check if some of your packages still need orphaning. It is important that the above process is followed, because finding inactive developers and orphaning their packages takes significant time @@ -263,22 +257,25 @@ Returning after retirement A retired developer's account is marked as "emeritus" when the process -in :ref:`s3.7` is followed, and "disabled" otherwise. Retired +in :ref:`s3.7` is followed, and "removed" otherwise. Retired developers with an "emeritus" account can get their account re-activated as follows: -- Contact ``da-mana...@debian.org``. +- Use the link https://nm.debian.org/wizard/process/return to log in to + nm.debian.org [2]_ and request to return from emeritus status. - Go through a shortened NM process (to ensure that the returning developer still knows important parts of P&P and T&S). -- Prove that they still control the GPG key associated with the - account, or provide proof of identify on a new GPG key, with at least - two signatures from other developers. - -Retired developers with a "disabled" account need to go through NM +Retired developers with a "removed" account need to go through full NM again. .. [1] This is so that the message can be easily filtered by people who don't want to read vacation notices. + +.. [2] + Login on nm.debian.org requires an SSO browser certificate. + (you can generate them on https://sso.debian.org) + If you cannot access SSO, the recommended way of action is to + mail NM frontdesk using ``n...@debian.org``. -- 2.23.0 signature.asc Description: This is a digitally signed message part.
Bug#926691: python-rsa: Missing manpages for binaries
Hi, attached a version, that does not scribble my name into each manpage. python-rsa-manpages.tar.gz Description: application/tgz
Bug#926691: python-rsa: Missing manpages for binaries
Source: python-rsa Version: 4.0-2 Severity: minor Tags: patch Hi, attached manpages for the binaries in this package. (python2 versions are just generated from the corresponding python3 versions) python-rsa-manpages.tar.gz Description: application/tgz
Bug#923622: packaging-tutorial: Typo in Slide 49
tags 923622 +patch
Added patch for fixing typo (and unfuzzy translations).
diff -Naur 0packaging-tutorial-0.22/packaging-tutorial.tex packaging-tutorial-0.22/packaging-tutorial.tex
--- 0packaging-tutorial-0.22/packaging-tutorial.tex 2019-02-21 19:06:36.0 +0600
+++ packaging-tutorial-0.22/packaging-tutorial.tex 2019-03-02 02:10:04.957742853 +0600
@@ -1228,7 +1228,7 @@
\begin{itemize}
\item You do not need any official status to get your package into Debian
\begin{enumerate}
- \item Submit an \textbf{ITP} bug (\textbf{I}ntend \textbf{T}o \textbf{P}ackage) using \texttt{reportbug wnpp}
+ \item Submit an \textbf{ITP} bug (\textbf{I}ntent \textbf{T}o \textbf{P}ackage) using \texttt{reportbug wnpp}
\hbr
\item Prepare a source package
\hbr
diff -Naur 0packaging-tutorial-0.22/po4a/po/de.po packaging-tutorial-0.22/po4a/po/de.po
--- 0packaging-tutorial-0.22/po4a/po/de.po 2019-02-21 18:30:33.0 +0600
+++ packaging-tutorial-0.22/po4a/po/de.po 2019-03-02 02:54:38.001852437 +0600
@@ -5,7 +5,7 @@
msgid ""
msgstr ""
"Project-Id-Version: packaging-tutorial 0.16\n"
-"POT-Creation-Date: 2019-02-21 13:26+0100\n"
+"POT-Creation-Date: 2019-03-02 02:40+0600\n"
"PO-Revision-Date: 2019-02-21 13:30+0100\n"
"Last-Translator: Helge Kreutzmann \n"
"Language-Team: de \n"
@@ -2985,11 +2985,11 @@
#. type: enumerate
#: packaging-tutorial.tex:1249
msgid ""
-"Submit an \\textbf{ITP} bug (\\textbf{I}ntend \\textbf{T}o \\textbf{P}"
+"Submit an \\textbf{ITP} bug (\\textbf{I}ntent \\textbf{T}o \\textbf{P}"
"ackage) using \\texttt{reportbug wnpp}"
msgstr ""
"Reichen Sie mit \\texttt{reportbug wnpp} einen \\textbf{ITP}-Fehler "
-"(\\textbf{I}ntend \\textbf{T}o \\textbf{P}ackage) ein"
+"(\\textbf{I}ntent \\textbf{T}o \\textbf{P}ackage) ein"
#. type: enumerate
#: packaging-tutorial.tex:1249
diff -Naur 0packaging-tutorial-0.22/po4a/po/es.po packaging-tutorial-0.22/po4a/po/es.po
--- 0packaging-tutorial-0.22/po4a/po/es.po 2019-02-21 18:31:15.0 +0600
+++ packaging-tutorial-0.22/po4a/po/es.po 2019-03-02 02:40:48.915500691 +0600
@@ -30,7 +30,7 @@
msgid ""
msgstr ""
"Project-Id-Version: packaging-tutorial 0.6\n"
-"POT-Creation-Date: 2019-02-21 13:26+0100\n"
+"POT-Creation-Date: 2019-03-02 02:40+0600\n"
"PO-Revision-Date: 2019-02-21 13:31+0100\n"
"Last-Translator: Omar Campagne \n"
"Language-Team: Debian l10n Spanish \n"
@@ -3128,7 +3128,7 @@
#. type: enumerate
#: packaging-tutorial.tex:1249
msgid ""
-"Submit an \\textbf{ITP} bug (\\textbf{I}ntend \\textbf{T}o \\textbf{P}"
+"Submit an \\textbf{ITP} bug (\\textbf{I}ntent \\textbf{T}o \\textbf{P}"
"ackage) using \\texttt{reportbug wnpp}"
msgstr ""
diff -Naur 0packaging-tutorial-0.22/po4a/po/fr.po packaging-tutorial-0.22/po4a/po/fr.po
--- 0packaging-tutorial-0.22/po4a/po/fr.po 2019-02-21 19:11:05.0 +0600
+++ packaging-tutorial-0.22/po4a/po/fr.po 2019-03-02 02:55:02.125499497 +0600
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: po 4a\n"
-"POT-Creation-Date: 2019-02-21 13:26+0100\n"
+"POT-Creation-Date: 2019-03-02 02:40+0600\n"
"PO-Revision-Date: 2019-02-21 14:11+0100\n"
"Last-Translator: YOUR NAME \n"
"Language-Team: French \n"
@@ -2124,7 +2124,8 @@
"You need to learn \\textsl{quilt} \\url{https://perl-team.pages.debian.";
"net/howto/quilt.html}"
msgstr ""
-"Vous devez apprendre \\textsl{quilt} \\url{http://perl-team.pages.debian.net/howto/quilt.html}";
+"Vous devez apprendre \\textsl{quilt} \\url{http://perl-team.pages.debian.";
+"net/howto/quilt.html}"
#. type: itemize
#: packaging-tutorial.tex:849
@@ -2592,8 +2593,8 @@
"release}; \\draw[arr,migrations,->] (spu) to (sn); \\draw[arr,migrations,->] "
"(spu) -- (su); \\draw[arr,migrations,->] (st) -- (os); \\draw[arr,"
"migrations,->] (os) -- (ar); \\coordinate (legend) at (-2,-1); \\draw[arr,"
-"uploads,->] (legend) -- ($(legend) + (0.7,0)$) node [right,legend] {envoi de paquets"
-"}; \\coordinate[node distance=1.1em,below=of legend] (legend2); "
+"uploads,->] (legend) -- ($(legend) + (0.7,0)$) node [right,legend] {envoi de "
+"paquets}; \\coordinate[node distance=1.1em,below=of legend] (legend2); "
"\\draw[arr,migrations,->] (legend2) -- ($(legend2) + (0.7,0)$) node [right,"
"legend] {migrations de paquets entre les suites}; \\coordinate[node "
"distance=1.5em,below=of legend2] (legend3); \\draw node[right,suite,devel,"
@@ -2603,9 +2604,9 @@
"\\draw node[node distance=0.1cm,right=of lint,suite,prod,legend] (lprod) "
"{production}; \\draw ($(legend.north west) + (-0.1,0.25)$) rectangle "
"($(lprod.south east) + (0.1,-0.1)$); \\draw node[font=\\bf,red!70!white,"
-"align=center] (tnext) at ($(te.east) + (2,-0.1)$) {préparation de la prochaine "
-"release}; \\draw node[font=\\bf,green!70!black,align=center] (tsrm) at "
-"($(sec.north east) + (1,1)$) {gestion des releases stables}; "
+"align=center] (tnext) at ($(te.east) + (2,-0.1)$) {préparation de la "
+"prochaine release}; \\draw node[font=\\bf,green!70!black,align=center] "
+"
Bug#913359: xkbcomp.pc requires libxkbfile-dev as dependency
tags 913359 -patch thanks > x11-xkb-utils should very much not depend on any -dev package. Ok. Then the patch tag doesn't apply anymore.
Bug#913359: xkbcomp.pc requires libxkbfile-dev as dependency
tags 913359 +patch
user debian-rele...@lists.debian.org
usertag 913359 + bsp-2019-02-de-berlin
thanks
Added a patch.
diff -Nru x11-xkb-utils-7.7+4/debian/changelog x11-xkb-utils-7.7+4+nmu1/debian/changelog
--- x11-xkb-utils-7.7+4/debian/changelog 2018-04-30 11:51:31.0 +0600
+++ x11-xkb-utils-7.7+4+nmu1/debian/changelog 2019-02-10 20:24:51.0 +0600
@@ -1,3 +1,9 @@
+x11-xkb-utils (7.7+4+nmu1) unstable; urgency=low
+
+ * NMU; add dependency to libxkbfile-dev. Thanks, Mike Gabriel. (Closes: #913359)
+
+ -- Judit Foglszinger Sun, 10 Feb 2019 20:24:51 +0600
+
x11-xkb-utils (7.7+4) unstable; urgency=medium
[ Julien Cristau ]
diff -Nru x11-xkb-utils-7.7+4/debian/control x11-xkb-utils-7.7+4+nmu1/debian/control
--- x11-xkb-utils-7.7+4/debian/control 2018-04-30 11:33:03.0 +0600
+++ x11-xkb-utils-7.7+4+nmu1/debian/control 2019-02-10 20:24:51.0 +0600
@@ -27,7 +27,7 @@
Package: x11-xkb-utils
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, libxkbfile-dev
Replaces: xbase-clients (<= 1:7.2.ds2-3)
Multi-Arch: foreign
Description: X11 XKB utilities
Bug#890416: Leafpad over ssh erases file content upon saving
tags 890416 +moreinfo user debian-rele...@lists.debian.org usertag 890416 + bsp-2019-02-de-berlin thanks Behaves differently to me. When connecting with caja over ssh to localhost and opening a file, an empty file with title 'Untitled' is opened. When klicking on the save button, the location where to save to is asked for. versions: caja - 1.20.3-1+b1 leafpad - 0.8.18.1-5
Bug#614800: (no subject)
Upstream fixed an issue quite similar to this: http://bugs.gw.com/view.php?id=151 If no one claims, that this bug is still valid in file_5.11-2, it will be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680021: Please add support for Access 2010 files
Thanks, added the patch to vcs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680021: Please add support for Access 2010 files
> .accdb file are not recognised as Micro$oft Access files. > They changed "Standard JET DB" by "Standard ACE DB" at byte 4. > Trivial patch included. > Thanks! Could you provide a sample .accdb file? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649858: file(1) incorrectly identifies Z-machine binaries
found 649858 5.09-2 thanks I get the the same results with both upstream and Debian version of file 5.09 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649858: file(1) incorrectly identifies Z-machine binaries
Hi, can you provide samples of the misidentified files or point, where to find them? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641012: /usr/bin/file command identifies incorrectly as a "DOS executable (COM)" starting with 0xE9.\
Cannot reproduce this bug with the given sample. (file_5.08-1) Did it originally use another encoding than UTF-8? $ file hungarian.txt hungarian.txt: UTF-8 Unicode text $ sha1sum hungarian.txt 3d1eba4eda2e8596f20f7321b3c36f9e22c18bca hungarian.txt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572465: e16: Please build-depend on autopoint
actually added the patch :) diff -Naur debian/control debian-new/control --- debian/control 2010-06-10 15:38:31.0 + +++ debian-new/control 2010-06-10 15:30:49.0 + @@ -2,7 +2,7 @@ Section: x11 Priority: optional Maintainer: Laurence J. Lane -Build-Depends: libxft-dev, libesd0-dev, libimlib2-dev, gettext, libdbus-1-dev, libsm-dev, libx11-dev, libxext-dev, libxrandr-dev, libxinerama-dev, libxxf86vm-dev, libxt-dev, xbitmaps, libxcomposite-dev, libxdamage-dev, libxrender-dev, libpango1.0-dev, pkg-config, debhelper (>=7.0.1), automake, autoconf, libtool, gettext, quilt, cvs +Build-Depends: libxft-dev, libesd0-dev, libimlib2-dev, gettext, libdbus-1-dev, libsm-dev, libx11-dev, libxext-dev, libxrandr-dev, libxinerama-dev, libxxf86vm-dev, libxt-dev, xbitmaps, libxcomposite-dev, libxdamage-dev, libxrender-dev, libpango1.0-dev, pkg-config, debhelper (>=7.0.1), automake, autoconf, libtool, gettext, quilt, autopoint Standards-Version: 3.8.2 Homepage: http://www.enlightenment.org/
Bug#572465: e16: Please build-depend on autopoint
tags 572465 + patch thanks Added build-depency on autopoint and removed the one on cvs, makes package build with pbuilder. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572464: ceferino: Please build-depend on autopoint
tags 572464 + patch thanks Added build-depency on autopoint and removed the one on cvs, makes package build with pbuilder. diff -Naur debian/control debian-new/control --- debian/control 2010-06-10 14:55:31.0 + +++ debian-new/control 2010-06-10 14:40:51.0 + @@ -5,7 +5,7 @@ Uploaders: Miriam Ruiz , Barry deFreese , Bas Wijnen Build-Depends: debhelper (>= 5.0.37.2), automake, autoconf (>= 2.53), - gettext, quilt, libsdl1.2-dev, libsdl-image1.2-dev, libsdl-mixer1.2-dev, cvs + gettext, quilt, libsdl1.2-dev, libsdl-image1.2-dev, libsdl-mixer1.2-dev, autopoint Standards-Version: 3.8.3 Homepage: http://www.losersjuegos.com.ar/juegos/ceferino/ceferino.php Vcs-Svn: svn://svn.debian.org/svn/pkg-games/packages/trunk/ceferino/
Bug#564923: Wrong option in cp / maintenance?
See attached a patch to deal with 1). source version manpages-de-0.5 was used for this. manpages3.patch.gz Description: GNU Zip compressed data
Bug#538997: manpage for rm is quite outdated
tags 538997 + patch thanks attached an updated version and the corresponding po-file rm.1 Description: Troff document de-rm.po Description: application/gettext
Bug#538997: manpage for rm is quite outdated
Package: manpages-de Version: 0.5-4.2 The translation of rm manpage contains the no longer supported option '-d' aka '--directory' and is missing the options --one-file-system --no-preserve-root --preserve-root --interactive[=WHEN] and '-I' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521012: [checks/deb-format] "debian-binary" is referred to as "debian-control"
Package: lintian Version: 2.2.8 Severity: minor When calling lintian with "lintian -i -C deb-format" over a malformed package, I get the following output: E: package: malformed-deb-archive second member data.tar.gz not control.tar.gz N: N:The binary package is not a correctly constructed archive. A binary N:Debian package must be an ar archive with exactly three members: N:debian-control, control.tar.gz, and data.tar.gz or data.tar.bz2 in N:exactly that order. The debian-control member must start with a single N:line containing the version number, with a major revision of 2. (...) I assume, "debian-control" should be "debian-binary", as stated in deb(5): "The first member is named debian-binary and contains a series of lines, separated by newlines. Currently only one line is present, the format version number, 2.0 at the time this manual page was written." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
