Bug#996442: src:aspell-hr: fails to migrate to testing for too long: uploader built arch:all

[Paul Gevers]

Source: aspell-hr
Version: 0.51-5
Severity: serious
Control: close -1 0.51-6
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:aspell-hr 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 bookworm, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=aspell-hr




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:aspell-hr: fails to migrate to testing for too long: uploader built arch:all

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.51-6
Bug #996442 [src:aspell-hr] src:aspell-hr: fails to migrate to testing for too 
long: uploader built arch:all
Marked as fixed in versions aspell-hr/0.51-6.
Bug #996442 [src:aspell-hr] src:aspell-hr: fails to migrate to testing for too 
long: uploader built arch:all
Marked Bug as done

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

Processing of aspell-hr_0.51-6.1_source.changes

[Debian FTP Masters]

aspell-hr_0.51-6.1_source.changes uploaded successfully to localhost
along with the files:
  aspell-hr_0.51-6.1.dsc
  aspell-hr_0.51-6.1.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#996483: mp3blaster FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[Helmut Grohne]

Source: mp3blaster
Version: 1:3.2.6-2
Severity: serious
Tags: ftbfs

mp3blaster fails to build from source in unstable due to ncurses having
gained format string annotations. A non-parallel build now ends as
follows:

| g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/ncurses -I. -I/usr/include  
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 
 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu++98 -c -o nullmixer.o nullmixer.cc
| nmixer.cc: In member function ‘void NMixer::DrawScrollbar(short int, int)’:
| nmixer.cc:219:26: error: format not a string literal and no format arguments 
[-Werror=format-security]
|   219 | mvwprintw(mixwin, my_y - 1, my_x, (char*)source);
|   | ~^~~
| cc1plus: some warnings being treated as errors
| make[3]: *** [Makefile:445: nmixer.o] Error 1
| make[3]: Leaving directory '/<>/nmixer'
| make[2]: *** [Makefile:457: all-recursive] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:355: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j8 returned exit code 2
| make: *** [debian/rules:9: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Helmut

Bug#995624: pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[Sven Joachim]

Control: tags -1 + patch

Am 03.10.2021 um 12:00 schrieb Helmut Grohne:

> Source: pktstat
> Version: 1.8.5-7
> Severity: serious
> Tags: ftbfs
>
> pktstat fails to build from source in unstable on amd64. A non-parallel
> build ends as follows:
>
> | gcc -DHAVE_CONFIG_H -I.  -DPATH_PKTSTATRC=\"/etc/pktstatrc\" -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
> -D_BSD_SOURCE -c -o display.o display.c
> | In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
> |  from /usr/include/stdio.h:27,
> |  from display.c:17:
> | /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
> |   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
> |   |   ^~~
> | display.c: In function ‘display_update’:
> | display.c:499:33: warning: field width specifier ‘*’ expects
> | argument of type ‘int’, but argument 2 has type ‘long unsigned int’
> | [-Wformat=]
> |   499 |  attron(A_UNDERLINE); printw("%-*s",
> |   |   ~~^~
> |   | |
> |   | int
> | display.c:552:13: warning: field precision specifier ‘.*’ expects
> | argument of type ‘int’, but argument 2 has type ‘long unsigned int’
> | [-Wformat=]
> |   552 |   printw("%.*s\n", MIN(maxx - LLEN, sizeof flows[i].tag - 1),
> |   |   ~~^~
> |   | |
> |   | int
> | display.c:566:15: warning: field precision specifier ‘.*’ expects
> | argument of type ‘int’, but argument 2 has type ‘long unsigned int’
> | [-Wformat=]
> |   566 |printw(" %.*s\n", MIN(maxx - LLEN - 2,
> |   | ~~^~
> |   |   |
> |   |   int
> | display.c:285:21: warning: variable ‘x’ set but not used 
> [-Wunused-but-set-variable]
> |   285 |  int maxx, maxy, y, x;
> |   | ^
> | display.c: In function ‘printhelp’:
> | display.c:672:3: error: format not a string literal and no format arguments 
> [-Werror=format-security]
> |   672 |   printw((char *)h->name + 1);
> |   |   ^~
> | cc1: some warnings being treated as errors
> | make[2]: *** [Makefile:483: display.o] Error 1
> | make[2]: Leaving directory '/<>'
> | make[1]: *** [Makefile:339: all] Error 2
> | make[1]: Leaving directory '/<>'
> | dh_auto_build: error: make -j1 returned exit code 2
> | make: *** [debian/rules:11: build] Error 25
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
>
> This is likely due to ncurses including format string annotations.

Indeed.  The fix for the error is quite simple, add "%s" as first
argument in the printw call.  Patch for that attached, although the
warnings might also be worth a look.

From f3368493fe0365f7f37064fb0ae5fd1fba50fc36 Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Thu, 14 Oct 2021 19:40:32 +0200
Subject: [PATCH] Fix format string error with recent ncurses

---
 display.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/display.c b/display.c
index 2ff4c11..16b1b68 100644
--- a/display.c
+++ b/display.c
@@ -669,7 +669,7 @@ printhelp()
 			attron(A_REVERSE);
 		printw("%c", h->name[0]);
 		attroff(A_UNDERLINE);
-		printw((char *)h->name + 1);
+		printw("%s", (char *)h->name + 1);
 		attrset(0);
 		printw(" ");
 	}
--
2.33.0

Processed: Re: Bug#995624: pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #995624 [src:pktstat] pktstat FTBFS: error: format not a string literal and 
no format arguments [-Werror=format-security]
Added tag(s) patch.

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

Bug#994424: marked as done (spice-vdagent FTBFS: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Thu, 14 Oct 2021 17:54:31 +
with message-id 
and subject line Bug#994424: fixed in spice-vdagent 0.20.0-3
has caused the Debian Bug report #994424,
regarding spice-vdagent FTBFS: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' 
instead [-Werror=deprecated-declarations]
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.)


-- 
994424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spice-vdagent
Version: 0.20.0-2
Severity: serious
Tags: ftbfs

spice-vdagent fails to build from source in unstable. A non-parallel
build ends as follows:

| gcc -DHAVE_CONFIG_H -I. -I./src   -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/libdrm  -I/usr/include/spice-1 -pthread 
-I/usr/include/gio-unix-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/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/harfbuzz -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/libpng16 -I/usr/include/x86_64-linux-gnu -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  -I./src -DUDSCS_NO_SERVER  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -Wp,-D_FORTIFY_SOURCE=2 
-fno-strict-aliasing -fstack-protector --param=ssp-buffer-size=4 -c -o 
src/vdagent/spice_vdagent-x11-randr.o `test -f 'src/vdagent/x11-randr.c' || 
echo './'`src/vdagent/x11-randr.c
| src/vdagent/x11-randr.c: In function ‘vdagent_x11_set_monitor_config’:
| src/vdagent/x11-randr.c:1007:21: error: ‘g_memdup’ is deprecated: Use 
'g_memdup2' instead [-Werror=deprecated-declarations]
|  1007 | g_memdup(mon_config, 
config_size(mon_config->num_of_monitors));
|   | ^~~~
| In file included from /usr/include/glib-2.0/glib.h:82,
|  from src/vdagent/x11-randr.c:25:
| /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
|   257 | gpointer  g_memdup (gconstpointer mem,
|   |   ^~~~
| cc1: all warnings being treated as errors
| make[1]: *** [Makefile:1184: src/vdagent/spice_vdagent-x11-randr.o] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:18: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: spice-vdagent
Source-Version: 0.20.0-3
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated spice-vdagent 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: Thu, 14 Oct 2021 20:30:48 +0300
Source: spice-vdagent
Architecture: source
Version: 0.20.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 994424
Changes:
 spice-vdagent (0.20.0-3) unstable; urgency=medium
 .
   * QA upload.
   * Add patch for autoconf 2.71 compatibility. (Closes: #994424)
Checksums-Sha1:
 37f4967a5b797c8034e2e9fb568ce24abcc56bd7 2450 spice-vdagent_0.20.0-3.dsc
 d923243bd2c2d81996d1e7833f2d29b013bf9396 21556 
spice-vdagent_0.20.0-3.debian.tar.xz
Checksums-Sha256:
 3eec040059f76a8c5491cdc4ecab466fadce9661e1610401d89345e91a77 2450 
spice-vdagent_0.20.0-3.dsc
 174d7e886cdccc7452c281526f0958384519662a3733646fc2338155ec399e54 21556 
spice-vdagent_0.20.0-3.debian.tar.xz
Files:
 792fda03271afa853ae913

Processing of spice-vdagent_0.20.0-3_source.changes

[Debian FTP Masters]

spice-vdagent_0.20.0-3_source.changes uploaded successfully to localhost
along with the files:
  spice-vdagent_0.20.0-3.dsc
  spice-vdagent_0.20.0-3.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

spice-vdagent_0.20.0-3_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Oct 2021 20:30:48 +0300
Source: spice-vdagent
Architecture: source
Version: 0.20.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 994424
Changes:
 spice-vdagent (0.20.0-3) unstable; urgency=medium
 .
   * QA upload.
   * Add patch for autoconf 2.71 compatibility. (Closes: #994424)
Checksums-Sha1:
 37f4967a5b797c8034e2e9fb568ce24abcc56bd7 2450 spice-vdagent_0.20.0-3.dsc
 d923243bd2c2d81996d1e7833f2d29b013bf9396 21556 
spice-vdagent_0.20.0-3.debian.tar.xz
Checksums-Sha256:
 3eec040059f76a8c5491cdc4ecab466fadce9661e1610401d89345e91a77 2450 
spice-vdagent_0.20.0-3.dsc
 174d7e886cdccc7452c281526f0958384519662a3733646fc2338155ec399e54 21556 
spice-vdagent_0.20.0-3.debian.tar.xz
Files:
 792fda03271afa853ae913335364ef89 2450 x11 optional spice-vdagent_0.20.0-3.dsc
 9a5418fe0bc4b8563d1f892b31fddf25 21556 x11 optional 
spice-vdagent_0.20.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmFoadMACgkQiNJCh6LY
mLGG1A/8DoW0TCRIFrjNTQr5v1dxtjOaIo5V/vmMJBAQfUUmXK1Hnz/V9dHSc33F
TtlPw3leOUuARcry+xz1DXRnDQ8EdYAPj8xmFgB0sJJv/w5Z4nlN4lkLvwE2LoxS
F6C12C3AWRjello7dQPW5tPIuGIdQW3qNnodzgoOO8JBaBWiac1ut8Z7vtNHoNoc
77AugZ+3i18/CFlqSS4RuwrZifTRCgs/dcnzGV1mX47ybUzAABpV5Pp0RU0MgLPQ
lTIwDIUKg5LeFSlfjPLH5QmRlsorNEU4ZL9BT7e8qD+iWlQNHhwDCWaDwucaZAu9
2C0G8n5Ct4tABhCwle+DTrWOsdQ15Wg40imrThNOEZyuanWAUiGcgmYrSTI3WuYi
gipn7UdCByzU9GJV/ncFf/6TzJNgf68+3JuAEP8ZmBWqNeGPql4SrsJbT+D+Oc8C
HdyctMzOrO2oCnMh5k/qeCoJ8yKxWUrsavRS2lBz6H74fStKpDvy36vyoZ7MIpOn
xQ5n1uU/4IUf4CEy1sEdHxLUuheU0vTksPITYvYy8bX0AC+XNPVDdZwSyp3v6eE4
DFHzMQFpp05EBqkS9EUkmk5z+vu1RntUU5fZpjw3IcJpwADk+sPP7mGU8Yswoe4C
E01c8qsyaN2xlTgrLpluGqf4/qEA3beMQeEfY20ev15zLlGN9RM=
=xoHU
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of mpack_1.6-18_source.changes

[Debian FTP Masters]

mpack_1.6-18_source.changes uploaded successfully to localhost
along with the files:
  mpack_1.6-18.dsc
  mpack_1.6-18.debian.tar.xz
  mpack_1.6-18_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

mpack_1.6-18_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 14 Oct 2021 16:21:33 -0300
Source: mpack
Architecture: source
Version: 1.6-18
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Fabio Augusto De Muzio Tobich 
Changes:
 mpack (1.6-18) unstable; urgency=medium
 .
   * QA upload.
   * Set Debian QA Group as maintainer. (see #996492)
   * debian/control:
   - Bumped Standards-Version to 4.6.0.
   - Removed Homepage field since it doesn't exist anymore.
   * debian/copyright:
   - Removed Upstream-Contact and Source fields since they don't exist
 anymore.
   - Updated my email and years in packaging block.
   * debian/salsa-ci.yml: updated to use Debian recipe for salsa CI.
   * debian/upstream/metadata: removed since there's no upstream info anymore.
   * debian/watch: removed since there's no upstream repository anymore.
Checksums-Sha1:
 d1764a3d396b16862d57c3d4dd3588b93e29e915 1766 mpack_1.6-18.dsc
 d2ae0359b28f09126e37649df191f754ddc94400 12516 mpack_1.6-18.debian.tar.xz
 754124f140d474b233cc4eabcd8d08cecb53db13 5700 mpack_1.6-18_source.buildinfo
Checksums-Sha256:
 9f9aa2b8e934a6736b0c7d884b1b83083f7df2a73ea91704a099eac0cfeaff56 1766 
mpack_1.6-18.dsc
 fb8950f4f854a09259745459f80d8d12702dc7b382ac05a8ba703bfc9467e1dc 12516 
mpack_1.6-18.debian.tar.xz
 113b4e2dcaae36635ae02ec48176af29feccf2f486526ec68ad867e49a02c9ef 5700 
mpack_1.6-18_source.buildinfo
Files:
 19abd2486fa5b7ae204a57f626351d8e 1766 mail optional mpack_1.6-18.dsc
 7dbfef6d02abd2ce34d368663dc27944 12516 mail optional mpack_1.6-18.debian.tar.xz
 eb9d1c88554348b13890b31e201a3762 5700 mail optional 
mpack_1.6-18_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEElzBAZuWu+sImg9A9T7O00372Oy4FAmFog34ACgkQT7O00372
Oy6PPg/8C0HPoEupUJ3Avk3FFaQCzOQcfnJRn8CKeHH+eG1FBz2B79DWcht6Qy7p
bUN9g+PjdzWiL6rnYlcIT5GnRIbQfzkDKr1SguRL8gtfVJpgJuCKyUZWH+pqbOz2
MiUXt1bPLoAVJ5lbzwj9balzKSdN+iGJ465AeT0UUvFDZQ0J/BokcDFoyl8mLHMb
EdeIVxM7YCwX5IscTXrdJdDpN5E+03EvA4a2CNInsm2/eLq9RpvIFkWNEmnr5f2K
Gk+tnHHzvNBMw7lLKeUlQqF5/fWRLYomBsoyvEw+CyuCT6IUlkm61gl5gPPipR8I
9A1ae5GkRELYxKKeyF45blSQ/JA0jJmciKOpO7X7xqixMmbhYl6bE5FiRvWsfva4
GYdrjHwPkXiaK+9Kk1gXuIeM0CVj7I8CDke5nPF7/67O63ERD8Dk7+pVKpisJ1gW
np7nAsFBviegyCftgnPmQrUhu7rfUAOPyyJbbCTpjXedCPL6F2XcW+xNeHL9SRPv
8142gqnuvR+cfPLK7lwtiU6q6KLGyVI3hFZ5k3aBxdV3nAsehfSE7F9jvon19BFO
2/aGK0/0YvsqoEYuR4PdsYkjDGA+k/ijrG+f95NS+5FkVZIvqWtg26xFvg7odu1Q
5di+SWodKhVj0WoDoh6ILIa0RfJsXCGugJvljTh5EjndduHiRws=
=IF1g
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#996534: netkit-telnet: Specifying a port in telnetrc is not working

[Dongho Chang]

Source: netkit-telnet
Version: 0.17
Severity: normal

Dear Maintainer,



# What expected to happen

 - 1. Specify a port in telnetrc ( $HOME/.telnetrc) as follows
 * DEFAUT:8023 mode character
 - 2. telnet a host with specific port
 * telnet 192.168.1.1 8023
 - The expected is that "mode character" command is executed as soon as server 
is connected, according to "man telnet"

# What happened instead
  - The command in telnetrc specifying a port is not executed
  - But If not specifying a port, the command is executed as expected

# Cause of Bug
  - telnetrc parsing routine ( readrc() function in telnet/command.cc ) has a 
flaw in comparing the port number of command-line with that of telnetrc
  - To proceed command processing, the result of string compare MUST not negated
  - The patch is as follows
--- a/telnet/commands.cc
+++ b/telnet/commands.cc
@@ -2135,7 +2135,7 @@ static void readrc(const char *m1, const char *m2, const 
char *port,
continue;
 while (fgets(line, sizeof(line), rcfile)) {
...
if (gotmachine == 0) {
...

if (line[0] == ':') {
- if (!strncasecmp(&line[1], port, lport))
+ if (strncasecmp(&line[1], port, lport))
continue;
strncpy(line, &line[lport + 1], sizeof(line) - lport - 1);
}
   ...
}
...
process_command(&cmdtab, margc, margv);

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0-36-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#996534: netkit-telnet: Specifying a port in telnetrc is not working

[Dongho Chang]

Package: netkit-telnet
Followup-For: Bug #996534
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu  ubuntu-patch

Dear Maintainer,


*** /tmp/tmpn1vxgjaz/bug_body

In Ubuntu, the attached patch was applied to achieve the following:


  * Description: Fix Bug-Specifying a port in telnetrc is not working
 telnetrc parsing routine ( readrc() function in telnet/command.cc ) 
 has a flaw in comparing the port number of command-line with that 
 of telnetrc To proceed command processing, the result of string 
 compare MUST not negated


Thanks for considering the patch.


-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0-36-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru netkit-telnet-0.17/debian/patches/port-telnetrc 
netkit-telnet-0.17/debian/patches/port-telnetrc
--- netkit-telnet-0.17/debian/patches/port-telnetrc 1970-01-01 
09:00:00.0 +0900
+++ netkit-telnet-0.17/debian/patches/port-telnetrc 2021-10-15 
11:36:04.0 +0900
@@ -0,0 +1,32 @@
+Description: Fix Bug-Specifying a port in telnetrc is not working
+ telnetrc parsing routine ( readrc() function in telnet/command.cc )
+ has a flaw in comparing the port number of command-line with that
+ of telnetrc To proceed command processing, the result of string
+ compare MUST not negated
+ .
+ netkit-telnet (0.17-41.2ubuntu2) UNRELEASED; urgency=medium
+ .
+
+Author: Dongho Chang 
+
+---
+Bug-Debian: https://bugs.debian.org/996534
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1891021 
+Last-Update: 2021-10-15
+
+--- netkit-telnet-0.17.orig/telnet/commands.cc
 netkit-telnet-0.17/telnet/commands.cc
+@@ -2135,7 +2135,7 @@ static void readrc(const char *m1, const
+   continue;
+ 
+   if (line[0] == ':') {
+-  if (!strncasecmp(&line[1], port, lport))
++  if (strncasecmp(&line[1], port, lport))
+   continue;
+   strncpy(line, &line[lport + 1], sizeof(line) - lport - 1);
+   }
diff -Nru netkit-telnet-0.17/debian/patches/series 
netkit-telnet-0.17/debian/patches/series
--- netkit-telnet-0.17/debian/patches/series2019-02-24 22:25:14.0 
+0900
+++ netkit-telnet-0.17/debian/patches/series2021-10-15 11:36:04.0 
+0900
@@ -14,3 +14,4 @@
 142-numeric_hosts.diff
 use-cmake-as-buildsystem.patch
 use-cmake-as-buildsystem-debian-extras.patch
+port-telnetrc

Bug#185099: marked as done (aewm: resize outline displays in black even on black backgrounds)

[Debian Bug Tracking System]

Your message dated Fri, 15 Oct 2021 06:01:50 +
with message-id 
and subject line Bug#989005: Removed package(s) from unstable
has caused the Debian Bug report #185099,
regarding aewm: resize outline displays in black even on black backgrounds
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.)


-- 
185099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aewm
Version: 1.2.0-1

When I resize a window in aewm (middle-click on the box on the right
end of the title bar) aewm displays an outline of the new window size
as I drag the mouse around, plus an x-y-width-height string. However,
it seems to display both of these things in black, which is a bit
unhelpful given that my backdrop is mostly also black.

(I had a quick look at the source and it looks as if it's trying to
draw these in inverse video, but it doesn't work for me).

It would be nice to be able to set the colour used (eg to 
something like luminous green), but I don't know if this is
against your principles :->

-- PMM

--- End Message ---
--- Begin Message ---
Version: 1.3.12-7+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#967244: marked as done (aewm: depends on deprecated GTK 2)

[Debian Bug Tracking System]

Your message dated Fri, 15 Oct 2021 06:01:50 +
with message-id 
and subject line Bug#989005: Removed package(s) from unstable
has caused the Debian Bug report #967244,
regarding aewm: depends on deprecated GTK 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.)


-- 
967244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aewm
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Version: 1.3.12-7+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#224336: marked as done (problems with menus.)

[Debian Bug Tracking System]

Your message dated Fri, 15 Oct 2021 06:01:50 +
with message-id 
and subject line Bug#989005: Removed package(s) from unstable
has caused the Debian Bug report #224336,
regarding problems with menus.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: aewm
Version: 1.2.3-2


I have these setting in my X-resources:

AePanel.geometry:   1280x31-0-0
AePanel.overrideRedirect:   True
AePanel*orientation:Horizontal
AePanel*showGrip:   True

But that causes problems with aepanel-xaw: Lower parts of long menus are
hidden.

In addition, I hate this: Only way to close some menu is to click some
name of program on it. How about making it disappear with Esc-key?


-- 
Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv
"Rakkaudesta ruikuttajat, halusta ulvojat kiertää kaupungin sydäntä vaanien
verta. Omiin synkkiin linnoihinsa vallitusten taa pelokkaammat piilee
hautomaan haamujaan."CMX

--- End Message ---
--- Begin Message ---
Version: 1.3.12-7+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#715621: marked as done ([Mayhem] Bug report on aewm: aedesk crashes with exit status 139)

[Debian Bug Tracking System]

Your message dated Fri, 15 Oct 2021 06:01:50 +
with message-id 
and subject line Bug#989005: Removed package(s) from unstable
has caused the Debian Bug report #715621,
regarding [Mayhem] Bug report on aewm: aedesk crashes with exit status 139
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.)


-- 
715621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aewm
Version: 1.3.12-3
Severity: normal
User: may...@forallsecure.com
Usertags: mayhem

aedesk crashes with exit status 139. We confirmed the crash by
re-running it in a fresh debian unstable installation.

The attachment [1] contains a testcase (under ./crash) crashing the
program. It ensures that you can easily reproduce the bug. Additionally,
under ./crash_info/, we include more information about the crash such as
a core dump, the dmesg generated by the crash, and its output.

Regards,
The Mayhem Team (Alexandre Rebert, Thanassis Avgerinos, Sang Kil Cha, David 
Brumley, Manuel Egele)
Cylab, Carnegie Mellon University

[1] 
http://www.forallsecure.com/bug-reports/0af6fef2f23c922dafd2e3def7547f2c8a3ec55a/full_report


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.9-1-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages aewm depends on:
ii  libc6 2.17-6
ii  libglib2.0-0  2.36.3-2
ii  libgtk2.0-0   2.24.18-1
ii  libx11-6  2:1.6.0-1
ii  libxext6  2:1.3.1-2+deb7u1
ii  libxft2   2.3.1-1

aewm recommends no packages.

Versions of packages aewm suggests:
pn  menu  

-- no debconf information


aedesk-report.tar.bz2
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1.3.12-7+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#974436: marked as done (aewm: autopkgtest must be marked superficial)

[Debian Bug Tracking System]

Your message dated Fri, 15 Oct 2021 06:01:50 +
with message-id 
and subject line Bug#989005: Removed package(s) from unstable
has caused the Debian Bug report #974436,
regarding aewm: autopkgtest must be marked superficial
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.)


-- 
974436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aewm
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest

Dear Maintainer,

It has been noticed that the autopkgtest in aewm is running a
trivial command that does not provide significant test coverage:

- xvfb-run -a aewm &

Executing that command is considered to be a trivial test, which
does not provide significant coverage for a package as a whole.
But these tests are a useful way to detect regressions in dependencies
and prevent them from breaking your package.

However, it is important that we are realistic about the level of
test coverage provided by these commands: most regressions cannot be
detected in this way. So it is not appropriate for packages with only
superficial tests to have the reduced migration time to migrate from
unstable to testing as that means less opportunity for testing by users
compared to the package with no tests.

To support this, the keyword "Restrictions: superficial" has been
defined [1]. Packages where all tests are marked with this keyword are not
considered for the reduced migration age from unstable to testing, and
will not be allowed to migrate automatically in later stages of the
freeze [2].

Its always better to have more extensive testing than having
superficial testing, which again is better than having no test.

Please consider i) Adding a non-trivial test, and/or ii) Mark the
trivial test with "Restrictions: superficial", similar to
[3] or [4].

The Release Team has listed this issue in the list of Release Critical
Issues for bullseye [5] and has mentioned that the test must be marked
superficial if it is not testing one of its own installed binary
packages in some way. As a result, the severity of this bug report might
be increased to serious in future.

[1] 
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions
[2] https://release.debian.org/bullseye/freeze_policy.html
[3] 
https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468
[4] 
https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3
[5] https://release.debian.org/bullseye/rc_policy.txt


--
Regards
Sudip
--- End Message ---
--- Begin Message ---
Version: 1.3.12-7+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#989074: marked as done (Ship upstream-dead aewm with bullseye?)

[Debian Bug Tracking System]

Your message dated Fri, 15 Oct 2021 06:01:50 +
with message-id 
and subject line Bug#989005: Removed package(s) from unstable
has caused the Debian Bug report #989074,
regarding Ship upstream-dead aewm with bullseye?
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.)


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

Hi,

aewm has not seen a new upstream release since 2007, and upstream
seems to have stopped working on it long long time ago.
Furthermore:
- the upstream website is not available anymore
- I cannot find anywhere a potential repository that continues the
  development
- it has been "maintained" in Debian with NMUs/QA uploads since 2011
- uses old tech/libs (GTK+ 2)
- it has a very low popcon count (38 at the time I'm writing this)
- plenty of alternatives ("minimalist/lightweights" WMs) exist

Hence, it looks to me it would be a better idea to simply remove aewm
from Debian.

Thanks,
-- 
Pino
--- End Message ---
--- Begin Message ---
Version: 1.3.12-7+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#228993: marked as done (nwrite complains about X logins unnecessarily)

[Debian Bug Tracking System]

Your message dated Fri, 15 Oct 2021 06:11:59 +
with message-id 
and subject line Bug#992595: Removed package(s) from unstable
has caused the Debian Bug report #228993,
regarding nwrite complains about X logins unnecessarily
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.)


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

nwrite will complain if you try to write to a user logged into
X-windows on the local machine:

nwrite: couldn't stat /dev/:0.
writing to jim on pts/0
nwrite: could not open jim.:0

It should instead ignore special names like :0, as they're not valid
terminals anyway.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux neurosis 2.6.1 #1 Sun Jan 18 18:37:52 EST 2004 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages nwrite depends on:
ii  dpkg1.10.18  Package maintenance system for Deb
ii  libc6   2.3.2.ds1-10 GNU C Library: Shared libraries an

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.9.2-21+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#450016: marked as done (nwrite: debian/watch fails to report upstream's version)

[Debian Bug Tracking System]

Your message dated Fri, 15 Oct 2021 06:11:59 +
with message-id 
and subject line Bug#992595: Removed package(s) from unstable
has caused the Debian Bug report #450016,
regarding nwrite: debian/watch fails to report upstream's version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
450016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nwrite
Version: 1.9.2-20
Severity: minor
Usertags: dehs-no-upstream

Hello maintainer,

The debian/watch file of your package on the unstable distribution fails to 
report upstream's version.
Uscan's message follows:


uscan warning: In watchfile /tmp/nwrite_watchb2ZTBL, reading webpage
  http://ftp.csua.berkeley.edu/pub/nwrite/ failed: 500 Can't connect to 
ftp.csua.berkeley.edu:80 (connect: Connection refused)


Please note that this message is auto-generated by extracting the information
 from the Debian External Health Status (a.k.a. DEHS) no_upstream page[1].
At the moment of running the package version found is the one indicated in the 
report.
If you have already fixed this issue please ignore and close this report.

If you belive this message can be improved in any way don't hesitate to contact 
me
 by replying to n-submit...@bugs.debian.org (where N is the number of 
this bug report).

If you wish not to be notified in the future contact me so I add you to the 
ignore list.

[1] http://dehs.alioth.debian.org/no_upstream.html

Kind regards, Raphael Geissert.


--- End Message ---
--- Begin Message ---
Version: 1.9.2-21+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#989005: Removed package(s) from unstable

[Debian FTP Masters]

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

  aewm |   1.3.12-7 | source, amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; dead upstream; unmaintained; very low popcon
--

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)

Bug#989005: Removed package(s) from unstable

[Debian FTP Masters]

Version: 1.3.12-7+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)

Bug#992595: Removed package(s) from unstable

[Debian FTP Masters]

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

nwrite |   1.9.2-21 | source, amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; obsoleted over time; unmaintained
--

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)

Bug#992595: Removed package(s) from unstable

[Debian FTP Masters]

Version: 1.9.2-21+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)