Bug#1062983: Additional Information

2024-02-04 Thread Sebastian Geiger

The corresponding option to adjust this is already present in conf.py
but its currently not being set by the build system:

https://salsa.debian.org/debian/developers-reference/-/blob/master/source/conf.py?ref_type=heads#L162



Bug#1062983: Developers Reference in A4 instead of US Letter

2024-02-04 Thread Sebastian Geiger (Lanoxx)

Package: developers-reference
Version: 13.4

I just downloaded the developers-reference from
https://www.debian.org/doc/devel-manuals and I noticed that it is being
formatted in US Letter. While this may be the preferred format for US
users, the rest of the world is using A4 sized pages. I am not sure if
there is any recommendation in Debian to choose a paper size for
documentation.

I went over some common Debian user and developer manuals and noticed
that there is a mix of paper sized, but the A4 format seems to be most
common:

* https://www.debian.org/doc/manuals/debian-faq/debian-faq.en.pdf (A4)
* https://www.debian.org/doc/manuals/refcard/refcard.en.pdf (A4)
*
https://www.debian.org/doc/manuals/debian-reference/debian-reference.en.pdf
(A4)

*
https://www.debian.org/doc/manuals/hamradio-maintguide/hamradio-maintguide.en.pdf
(letter)
* https://www.debian.org/doc/debian-policy/policy.pdf (letter)

* https://www.debian.org/doc/manuals/debmake-doc/debmake-doc.en.pdf (A4)
* https://www.debian.org/doc/manuals/maint-guide/maint-guide.en.pdf (A4)

May I request, that:

a) We switch to A4 as the default format for the developers-reference
since that is the format used by most of the world.
b) We consider offering both formats on the Debian manuals page, so that
users can choose their preferred format.

In general it would be nice to have a consistent solution for all
documents. I often like to print the manuals and then its a bit odd to
see the large US letter margins on an A4 page.

Given that all PDFs are build automated pipelines, its probably possible
that we automatically build both formats and introduce a general
mechanism on https://www.debian.org/doc/
that allows users to choose their preferred format?

Kind Regards
Sebastian Geiger



Bug#1059796: tilda: fails to respond to show/hide command depending on active application

2024-01-14 Thread Sebastian Geiger

This is a known issue that will be resolved once the D-Bus enabled
update of tilda will reach the distribution. I am planning a new upload
in the next weeks that will ship a new tilda version.

In the mean time, there are two workarounds:

* one is to build tilda from source if you are on Wayland as the current
master branch of tilda already has the D-Bus support.
* another one is to use an Xorg session instead of Wayland.


On 1/1/24 15:48, activityworkshop wrote:

Package: tilda
Version: 1.5.4-1
Severity: normal
X-Debbugs-Cc: deb...@activityworkshop.net

Dear Maintainer,

After upgrade from old-stable to stable, Tilda no longer reliably responds to 
the show/hide shortcut (in my case F12).
If Firefox is running and currently has the focus, then pressing F12 pulls down 
Tilda as expected.  Note that Firefox
would also like to intercept the F12 key but Tilda receives it and acts 
correctly.
If Firefox is running but minimized (no active application), then pressing F12 
does nothing.  Presumably Tilda does not receive the keypress.
If Firefox is running and visible but gedit has the focus, then pressing F12 
does nothing.
If Tilda is pulled-down but gedit has the focus, then pressing F12 does not 
close Tilda as expected.
Changing the configuration to use F2 has no effect on this behaviour, it's not 
specific to F12.
Other applications behave the same as gedit so that Tilda won't open (for 
example Calculator, Files, Meld);
some applications behave the same as Firefox so that Tilda correctly opens (for 
example Gimp, VLC).
Deleting the configuration file(s) under ~/.config/tilda/ and re-setting the 
key has no effect.
All of this worked fine before the upgrade.

Desktop is standard Gnome, using a single monitor which is identified by Tilda as "0 
(XWAYLAND0)".


-- System Information:
Debian Release: 12.4
   APT prefers stable
   APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-15-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tilda depends on:
ii  libc62.36-9+deb12u3
ii  libconfuse2  3.3-3
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.38-2~deb12u1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libvte-2.91-00.70.6-2~deb12u1
ii  libx11-6 2:1.8.4-2+deb12u2

tilda recommends no packages.

tilda suggests no packages.

-- no debconf information




Bug#964785: Package accepted

2022-02-20 Thread Sebastian Geiger (Lanoxx)

Hi all,

the shutter 0.99.2-3 package was accepted into unstable [1]. Thanks to
everyone who helped to make this possible. If I am not mistaken, then
packages automatically migrate to testing after 7 days in unstable. We
might just barely miss the Debian Import Freeze for Ubuntu 22.04 which
starts on 24.02 [2]. I think once the package has migrated to testing we
could ask for a freeze exception on the Ubuntu side [3] and then shutter
would finally be back to both Debian and Ubuntu.

[1]:
https://packages.debian.org/search?suite=all=names=shutter

[2]: https://discourse.ubuntu.com/t/jammy-jellyfish-release-schedule/23906

[3]: https://wiki.ubuntu.com/FreezeExceptionProcess



Bug#964785: ITP: shutter -- feature-rich screenshot program

2022-01-04 Thread Sebastian Geiger

The package is currently in the Debian NEW queue (for two month) and
waiting to be processed. I have asked a few times in #debian-ftp but it
seems none of the maintainers had time to process the package yet. The
package is at around rank 60 and slowly moving up the queue.

The package should eventually be processed and accepted into unstable
(unless the package is rejected). So at this point it seems we can just
wait until the package is processed by the FTP team.



Bug#955619: openjdk-11-jre-headless: failure to install due to non-existant /usr/share/man/man1/ directory

2021-11-08 Thread Sebastian Geiger (Lanoxx)

Hello all,

here is some additional context. I think this bug is present in all
openjdk versions, not only openjdk-11. It was [recently fixed][1] for
openjdk-8 which is [maintained separately][2] from the [repository in
salsa][3] which includes openjdk-11 and above.

The affected source of the [post install script][7] for openjdk and
later can be found in the salsa repository.

The issue is that this script does not check if man1 exits. The FSH
standard [requires /usr/bin/man to exists (see FSH 4.11.2)][6], [but not
subfolders such as man1 (see FSH 4.11.6 and footnote 32)][5]. This means
the openjdk package is not compatible with the FSH. In a docker image
this folder does not exists causing the update-alternatives call to fail.

A patch has been created recently for openjdk-8 and can be found in
commit cfae7df8a6f6710ae97c582a42785c136b0e6f73 of [2].

That commit fixes the issue by adding this line to the post install script:

  test -d /usr/share/man/man1 || mkdir -p /usr/share/man/man1

I raised a [merge request][4] to port the fix to the salsa repository,
so it can be applied to openjdk-11 and later. I hope that helps to fix
this issue.

Kind Regards
Sebastian

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863199#23
[2]: https://evolvis.org/anonscm/git/alioth/openjdk-8.git/
[3]: https://salsa.debian.org/openjdk-team/openjdk
[4]: https://salsa.debian.org/openjdk-team/openjdk/-/merge_requests/1
[5]:
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s11.html#idm236091735088
[6]: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s11.html
[7]:
https://salsa.debian.org/openjdk-team/openjdk/-/blob/master/debian/JB-jdk-headless.postinst.in



Bug#964785: ITP: shutter -- feature-rich screenshot program

2021-11-01 Thread Sebastian Geiger

Hello Michael,

thanks for the quick response. I can confirm that libgtk3-imageview-perl
10-1 is part of testing. I have updated my Merge Request to bump the
version dependency to 10-1.

Here are a few additional notes. As mentioned in [Reintroducing
Packages][3], we need to look through closed bugs. I had a look at all
archived shutter bugs and the following list contains all bugs which are
referenced as +rm in the version. These issues need to be reopened or
marked as fixed via the changelog file to close them properly with the
next upload.

Can anybody summarize which of these are fixed in the new version and
which need to be reopend? I think that for those that are fixed, we then
need to update the change log file to add a corresponding '(Closes:
#nn)' entry.


= SERIOUS =

shutter: Depends on obsolete libgnome2-vfs-perl that will go away during
the Buster cycle:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870418

= IMPORTANT =

When you restart the program shutter, change the destination folder for
saving:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686550

shutter: Will be removed with todays update within Debian/testing:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724871

shutter: Ram usage:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755278

shutter: Shutter hangs gnome desktop environment when capture:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872855

shutter: Edit button disabled:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909269

= NORMAL =

shutter: Cannot capture from multi-monitor:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551891

shutter is placed in utilities menu instead of graphics
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588277

shutter: Fails to open images in external viewers:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691559

shutter: Text is readable under Pixelizer (has less than 100% opacity):
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717220

shutter: GLib-CRITICAL **: Source ID 29 was not found when attempting to
remove it at /usr/bin/shutter line 7247:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761058

fails to capture with Unexpected short read from authority file:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764011

shutter: fails to properly minimize to system tray:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820341

window no longer disappears after taking a screenshot and clicking the
systray icon:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854380

shutter: Crashes when running multiple instances:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867582

shutter: SIGSEGV in strlen ():
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897069

= MINOR =



= WHISHLIST =

shutter: The Shutter windows lack distinguishing X roles and instance names:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782181

shutter: Make it harder to move the base picture:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717219


[1]: https://packages.debian.org/bookworm/libgtk3-imageview-perl
[2]:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;dist=unstable;package=shutter
[3]:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-packages

On 1/11/21 05:58, Michael Kogan wrote:

Hi Sebastian!

Great, thanks for moving this forward! Could you please change the
minimal required libgtk3-imageview-perl version to >=10? Also, please
let us know, if we can do anything from upstream to help get it done in
time for Ubuntu 22.04.

All the best,
Michael from the Shutter team




Bug#964785: ITP: shutter -- feature-rich screenshot program

2021-10-31 Thread Sebastian Geiger

Hi,

(resending previous message as plain text)

I just had a look at this issue and the current state of the shutter
package. Based on jiho lee's commented I updated the control file and
changed the package dependency to depend on
gir1.2-ayatanaappindicator3-0.1. I also updated the package for upstream
version 0.99.2.

I have forked the sala packaging repository for shutter into [my own
repo][1], added the above mentioned changes and raised a [merge request][2].

I was able to build the package and install it on Debian Testing and
take a screenshot. On gnome-panel (with gnome-flashback-session) I was
also able to the see tray icon (but not in gnome-shell, not sure why).

One more thing that I noticed. The shutter package depends on
[libgoocanvas2-cairotypes-perl][4] which does [not exist on any of the
current Ubuntu versions][3]. If we keep the dependency on this package
and expect it to be synced into Ubuntu 22.04, then
libgoocanvas2-cairotypes-perl also needs to migrate to the next Ubuntu
version. I am not sure if this package will migrate into Ubuntu 22.04
automatically when they sync from Debian Testing.

The next Ubuntu version to be released in April will be an LTS version,
it would be great if we could complete the shutter packaging until the
feature freeze and ensure that the shutter package is automatically
imported into Ubuntu.

Kind Regards
Sebastian

[1]: https://salsa.debian.org/lanoxx/shutter
[2]:
https://salsa.debian.org/perl-team/modules/packages/shutter/-/merge_requests/3
[3]:
https://packages.ubuntu.com/search?suite=all=names=libgoocanvas2-cairotypes-perl
[4]:
https://packages.debian.org/search?suite=all=names=libgoocanvas2-cairotypes-perl



Bug#964785: ITP: shutter -- feature-rich screenshot program

2021-10-31 Thread Sebastian Geiger

  
  
Hi,
I just had a look at this issue and the current state of the
  shutter package. Based on jiho lee's commented I updated the
  control file and changed the package dependency to depend on gir1.2-ayatanaappindicator3-0.1.
  I also updated the package for upstream version 0.99.2.

I have forked the sala packaging repository for shutter into [my
  own repo][1], added the above mentioned changes and raised a
  [merge request][2].

I was able to build the package and install it on Debian Testing
  and take a screenshot. On gnome-panel (with
  gnome-flashback-session) I was also able to the see tray icon (but
  not in gnome-shell, not sure why).

One more thing that I noticed. The shutter package depends on
  [libgoocanvas2-cairotypes-perl][4] which does [not exist on any of
  the current Ubuntu versions][3]. If we keep the dependency on this
  package and expect it to be synced into Ubuntu 22.04, then
  libgoocanvas2-cairotypes-perl also needs to migrate to the next
  Ubuntu version. I am not sure if this package will migrate into
  Ubuntu 22.04 automatically when they sync from Debian Testing.

The next Ubuntu version to be released in April will be an LTS
  version, it would be great if we could complete the shutter
  packaging until the feature freeze and ensure that the shutter
  package is automatically imported into Ubuntu.

Kind Regards
  Sebastian

[1]: https://salsa.debian.org/lanoxx/shutter
  [2]:
https://salsa.debian.org/perl-team/modules/packages/shutter/-/merge_requests/3
  [3]:
https://packages.ubuntu.com/search?suite=all=names=libgoocanvas2-cairotypes-perl
  [4]:
https://packages.debian.org/search?suite=all=names=libgoocanvas2-cairotypes-perl

  




Bug#904309: tilda: diff for NMU version 1.4.1-2.1

2019-05-11 Thread Sebastian Geiger
Hi Niels,

Thanks for the upload. It looks good to me. I think you can push that to the 
repository. 

Best Regards
Mit freundlichen Grüßen
Dipl. Ing. Sebastian Geiger

> On 11. May 2019, at 15:04, Niels Thykier  wrote:
> 
> Control: tags 904309 + patch
> Control: tags 904309 + pending
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for tilda (versioned as 1.4.1-2.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.
> 
> diff -Nru tilda-1.4.1/debian/changelog tilda-1.4.1/debian/changelog
> --- tilda-1.4.1/debian/changelog2018-02-18 20:08:42.0 +
> +++ tilda-1.4.1/debian/changelog2019-05-11 13:04:23.0 +
> @@ -1,3 +1,15 @@
> +tilda (1.4.1-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Import patch from upstream to set ensure tilda is run
> +under the X11 backend.  This prevents crashes when the
> +window manager uses Wayland by default.
> +(Closes: #904309)
> +  * Ret Rules-Requires-Root to no as tilda does not need
> +(fake)root for building the debs.
> +
> + -- Niels Thykier   Sat, 11 May 2019 13:04:23 +
> +
> tilda (1.4.1-2) unstable; urgency=medium
> 
>   [ Sebastian Geiger ]
> diff -Nru tilda-1.4.1/debian/control tilda-1.4.1/debian/control
> --- tilda-1.4.1/debian/control2018-02-18 19:46:04.0 +
> +++ tilda-1.4.1/debian/control2019-05-11 11:30:38.0 +
> @@ -5,6 +5,7 @@
> Build-Depends: debhelper (>= 11), autopoint, pkg-config, libgtk-3-dev, 
> libvte-2.91-dev, libconfuse-dev
> Standards-Version: 4.1.3
> Homepage: http://github.com/lanoxx/tilda
> +Rules-Requires-Root: no
> Vcs-Git: https://salsa.debian.org/debian/tilda.git
> Vcs-Browser: https://salsa.debian.org/debian/tilda
> 
> diff -Nru tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch 
> tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
> --- tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
> 1970-01-01 00:00:00.0 +
> +++ tilda-1.4.1/debian/patches/02_set_supported_backend_to_X11.patch
> 2019-05-11 11:29:06.0 +
> @@ -0,0 +1,25 @@
> +From 606b655d8d811f880d610dead7d6943a33199deb Mon Sep 17 00:00:00 2001
> +From: Roman Hoellen 
> +Date: Mon, 30 Apr 2018 09:18:49 +0200
> +Subject: [PATCH] Set supported backend to X11
> +Upstream-Commit: 
> https://github.com/lanoxx/tilda/commit/606b655d8d811f880d610dead7d6943a33199deb.patch
> +Forwarded: Not-needed
> +
> +---
> + src/tilda.c | 3 +++
> + 1 file changed, 3 insertions(+)
> +
> +diff --git a/src/tilda.c b/src/tilda.c
> +index 8aa69828..92ce46c4 100644
> +--- a/src/tilda.c
>  b/src/tilda.c
> +@@ -686,6 +686,9 @@ int main (int argc, char *argv[])
> + g_log_set_default_handler (tilda_log_handler, NULL);
> + #endif
> + 
> ++/* Set supported backend to X11 */
> ++gdk_set_allowed_backends ("x11");
> ++
> + tilda_window tw;
> + /* NULL set the tw pointers so we can get a clean exit on 
> initialization failure */
> + memset(, 0, sizeof(tilda_window));
> diff -Nru tilda-1.4.1/debian/patches/series tilda-1.4.1/debian/patches/series
> --- tilda-1.4.1/debian/patches/series2018-02-18 19:48:15.0 +
> +++ tilda-1.4.1/debian/patches/series2019-05-11 11:30:38.0 +
> @@ -1 +1,2 @@
> 01_install_metadata_in_new_location.patch
> +02_set_supported_backend_to_X11.patch



Bug#788023: tilda: Uses obsolete vte3 which is going away

2015-11-17 Thread Sebastian Geiger (Lanoxx)

Hi,

I uploaded tilda 1.3.0 today to mentors, its pending upload to unstable 
from my sponsor.


Please hold removing tilda from testing until the new package has arrived.

Cheers
Lanoxx (Sebastian)

On Mon, 9 Nov 2015 18:25:21 +0100 Emilio Pozuelo Monfort 
 wrote:

> Control: block 796907 by -1
> Control: severity -1 serious
>
> On Mon, 08 Jun 2015 18:46:01 +0200 Rodolphe PELLOUX-PRAYER 


> wrote:
> > Package: tilda
> > Followup-For: Bug #788023
> >
> > Upstream bug : https://github.com/lanoxx/tilda/issues/94
>
> vte 2.90 won't be in Stretch, this bumping the severity of this bug 
to serious.

>
> Cheers,
> Emilio
>
>



Bug#767476: Tilda 1.2.2-1

2014-11-03 Thread Sebastian Geiger

Hi Jonathan,

its only two more days until the Freeze. Did you read my answer? Please 
let me know what other information you need for the decision to unblock 
tilda.


Cheers
Sebastian


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#767476: transition: tilda

2014-10-31 Thread Sebastian Geiger

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertrags: transition

Dear Release Team,

please transition tilda 1.2.2-1 from unstable to testing. The current 
version in testing is 1.1.12-1 and the 1.2 release introduces a number 
of improvements that I would like to see in testing. Unfortunately with 
the 10 day transition time, the upload happend too late for the package 
to be automatically transitioned to testing.


Tilda is a small program which no other programs or libraries depend on 
and thus its transition should not have any impact on other programs.


If you need additional information, please let me know.

Thanks for your time.
Sebastian


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#767476: transition: tilda

2014-10-31 Thread Sebastian Geiger


On 31/10/14 12:33, Jonathan Wiltshire wrote:

Your changelog says:

+tilda (1.2.2-1) unstable; urgency=low
+  * New packaging version 3.9.6
+  * Add debian/tilda.docs

but does not mention that this includes a new upstream release as well.
Did your sponsor not pick up on that?
Anton told me the debian/changelog file is for packaging related things 
only, so I removed all other entries. The complete changelog can be 
found directly in the package's ChangeLog file [1]


Therefore, with

  43 files changed, 6007 insertions(+), 5111 deletions(-)

after removing translation changes, I'm not comfortable reducing the
migration delay for tilda without better understanding the fixes.

In summary, there are many bug fixes a few new options in the user 
interface, some cleanups in the build system and then some new color 
themes. Nothing which is particularaly complex. But all in all it makes 
tilda more usable and more configurable.



[1] https://github.com/lanoxx/tilda/blob/master/ChangeLog


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#702072: RFS: tilda/1.1.4-1 [ITA] New upload

2013-03-19 Thread Sebastian Geiger
I just uploaded the package again. I have added a comment explaining 
that I have run blhc to confirm that the hardening warning override in 
lintian is justified and also removed some commented out lines from 
debian/rules to make it more clean. Also I have commited all the changes 
to the git repository, to get it in sync with the actual source package. 
I would say the package is ready to be uploaded to experimental.


Kind Regards
Sebastian


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#552505: Fixed upstream

2013-02-23 Thread Sebastian Geiger

This is fixed in the upstream repository,

the current default browser is x-www-browser.

Regards
Lanoxx


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#665619: Fixed upstream

2013-02-21 Thread Sebastian Geiger
Hi,

this has been fixed upstream in the new version 1.1.0, which uses GTK+3.

Regards
Lanoxx


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#601784: Upstream bugtracker

2010-12-12 Thread Sebastian Geiger
Hi,

this bug is being tracked at:
https://bugzilla.gnome.org/show_bug.cgi?id=625552

You also find additional inforamtion there.
Regards Sebastian



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org