Bug#1041095: Please drop installable-field-mirrors-source warning

Package: lintian Version: 2.116.3 Severity: normal Over the last couple of years I've received several MRs on salsa (via the Janitor) as a result of lintian's installable-field-mirrors-source. As an example see https://salsa.debian.org/utopia-team/libnma/-/merge_requests?scope=all=all I

Bug#1017094: false positive source-is-missing for gtk-doc generated html documentation

Package: lintian Version: 2.115.2 Severity: important lintian issues the following error for network-manager E: network-manager source: source-is-missing [docs/api/html/gdbus-org.freedesktop.NetworkManager.SecretAgent.html] E: network-manager source: source-is-missing

Bug#982456: lintian: systemd SystemCallArchitectures directive incompatible with M-A:foreign

Am 04.06.22 um 00:45 schrieb Michael Biebl: On Wed, 10 Feb 2021 13:42:59 +0100 Guillem Jover wrote: Package: lintian Version: 2.104.0 Severity: wishlist Hi! The systemd unit file directive SystemCallArchitectures is incompatible with Multi-Arch:foreign markings in a package, as that means

Bug#982456: lintian: systemd SystemCallArchitectures directive incompatible with M-A:foreign

On Wed, 10 Feb 2021 13:42:59 +0100 Guillem Jover wrote: Package: lintian Version: 2.104.0 Severity: wishlist Hi! The systemd unit file directive SystemCallArchitectures is incompatible with Multi-Arch:foreign markings in a package, as that means once you install such foreign package, systemd

Bug#996270: false positive custom-library-search-path

On 19.11.21 01:24, Felix Lechner wrote: Control: reopen -1 Hi, On Thu, Nov 18, 2021 at 3:51 PM Michael Biebl wrote: E custom-library-search-path RUNPATH /usr/lib/x86_64-linux- gnu/NetworkManager/1.32.12 [usr/lib/x86_64-linux- gnu/NetworkManager/1.32.12/libnm-device-plugin-bluetooth.so

Bug#996270: false positive custom-library-search-path

Looks like this is not fully fixed yet. Just saw this for the network- manager package [1] E custom-library-search-path RUNPATH /usr/lib/x86_64-linux- gnu/NetworkManager/1.32.12 [usr/lib/x86_64-linux- gnu/NetworkManager/1.32.12/libnm-device-plugin-bluetooth.so] E custom-library-search-path

Bug#945934: false positive udev-rule-missing-subsystem

Hi Felix On Thu, 4 Jun 2020 18:16:22 -0700 Felix Lechner wrote: > Hi Michael, > > On Sun, Dec 1, 2019 at 3:42 AM Michael Biebl wrote: > > > > Afaics, libmtp-common is affected by this as well. [That] maintainer decided > > to override lintian. > > I noticed y

Bug#996270: false positive custom-library-search-path

Package: lintian Version: 2.108.0 Severity: important Hi, running the latest lintian version against systemd, I get E: systemd: custom-library-search-path bin/loginctl RUNPATH lib/systemd/ N: E: systemd: custom-library-search-path bin/networkctl RUNPATH lib/systemd/ N: E: systemd:

Re: Correct location for systemd unit files

Am 26.09.21 um 18:09 schrieb Michael Biebl: Given that the changes in debhelper have been rolled back, I think the systemd-service-in-odd-location check in lintian should be reverted / postponed to bookworm+1 / demoted to pedantic. There is https://salsa.debian.org/lintian/lintian/-/commit

Re: Correct location for systemd unit files

Am 26.09.21 um 17:36 schrieb Micha Lenk: Dear maintainers of debhelper and systemd, Thank you for maintaining the both incredibly useful packages debhelper and systemd in Debian. I'm currently struggling with finding the correct location where systemd unit files are expected to be installed

Bug#992465: WARNING: dh_installsystemd is moving unit files to /usr/lib/systemd/system

Am 21.08.21 um 10:34 schrieb Niels Thykier: Also, before that, we will need a solution to the generators issue (#992554 comment #25 and below). Not only generators. For systemd we have to consider /lib/systemd/system-generators/ (24 packages) /lib/systemd/system-shutdown/ (6 packages)

Bug#992465: WARNING: dh_installsystemd is moving unit files to /usr/lib/systemd/system

Hi Nils, hi Peter Am 20.08.21 um 07:54 schrieb Niels Thykier: As people have concluded already, the change was intended and functional although lintian was not updated to match. Accordingly, I will close this bug against debhelper. I think we should start doing the same for udev files in

Bug#984678: Please add check for tmpfiles similar to systemd-service-file-pidfile-refers-to-var-run

Package: lintian Version: 2.104.0 Severity: wishlist Hi, we already have a check for .service files using /var/run in PIDFile systemd-service-file-pidfile-refers-to-var-run A similar check should be added for tmpfiles (i.e. files matching /usr/lib/tmpfiles.d/*.conf) to prevent tmpfiles from

Bug#972181: possible-gpl-code-linked-with-openssl tag/test can be retired

On Tue, 13 Oct 2020 23:08:44 +0200 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= wrote: > On Tue, Oct 13, 2020 at 01:56:40PM -0700, Felix Lechner wrote: > > Hi Moritz, > > > > On Tue, Oct 13, 2020 at 1:33 PM Moritz Muehlenhoff wrote: > > > > > > FTP masters are now treating OpenSSL as a system library,

Bug#966623: Please warn if User=nobody is used in service files

Package: lintian Version: 2.85.0 Severity: wishlist X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org Hi, according to [1], there are quite a few packages which use User=nobody (and Group=nogroup). This is discouraged, and systemd v246 will now log a warning about this. See

Re: Bug#966612: systemd-networkd failed to restart on upgrade to 246-1

Control: clone -1 -2 Control: reassign -2 lintian Control: severity -2 wishlist Control: retitle -2 "Please if Standard{Output,Error}=syslog is used" Hi Ansgar, thanks for testing the v246 package from experimental. Am 31.07.2020 um 14:45 schrieb Ansgar: > Package: systemd > Version: 246-1 >

Bug#961620: Way too many false positives for package-supports-alternative-init-but-no-init.d-script

Am 26.05.20 um 19:22 schrieb Michael Biebl: > Looking at package-supports-alternative-init-but-no-init.d-script ... ... at https://lintian.debian.org/tags/package-supports-alternative-init-but-no-init.d-script.html to be specific The first three packages being 389-ds-base, accountsserv

Bug#961620: Acknowledgement (Way too many false positives for package-supports-alternative-init-but-no-init.d-script)

I would like to add that the specific section of the debian policy (9.11) which triggered the addition of this lintian check, has been deleted in the mean time. signature.asc Description: OpenPGP digital signature

Bug#961620: Way too many false positives for package-supports-alternative-init-but-no-init.d-script

Package: lintian Version: 2.76.0 Severity: normal Looking at package-supports-alternative-init-but-no-init.d-script, it seems this lintian check triggers a lot of false positives. Just picking the first 3, already has 2 false positives. Imho that ratio is a sign that either it should be lowered

Bug#945934: Acknowledgement (false positive udev-rule-missing-subsystem)

Afaics, libmtp-common is affected by this as well. Hi maintainer decided to override lintian. SUBSYSTEM=="usb", GOTO="libmtp_usb_rules" GOTO="libmtp_rules_end" LABEL="libmtp_usb_rules" ... LABEL="libmtp_rules_end" -- Why is it that all of the instruments seeking intelligent life in the

Bug#945934: false positive udev-rule-missing-subsystem

Package: lintian Version: 2.39.0 Severity: normal Hi, the latest version of systemd (v244) ship a udev rule file /lib/udev/rules.d/60-autosuspend-chromiumos.rules which triggers the lintian warning: W: udev: udev-rule-missing-subsystem lib/udev/rules.d/60-autosuspend-chromiumos.rules:100

Bug#942493: lintian: Complain of too long header fields

Hi Felix Am 09.11.19 um 00:27 schrieb Felix Lechner: >> Given that systemd-tests-dbgsym is an autogenerated package, there isn't >> really something that can be done to reduce the number of characters, or >> is there? > > Unless there is a flag that indicates autobuilding, we could exempt > all

Bug#942493: lintian: Complain of too long header fields

Hi On Thu, 17 Oct 2019 09:51:39 +0200 =?utf-8?q?Rapha=C3=ABl_Hertzog?= wrote: > Package: lintian > Version: 2.27.0 > Severity: wishlist > > Based on the problem discovered in #942487 where a Provides line of more > than 256K slipped in the archive, I believe it would be nice if lintian > could:

Bug#944098: lintian: changelog-file-missing-explicit-entry false positive for changelog with: 2, 2+deb10u1, 2+deb10u2

tFlags=shared work again (Closes: #939551) * mount/generators: do not make unit wanted by its device unit. Among other things, this fixes StopWhenUnneeded=true being broken for mount units. (Closes: #941758) -- Michael Biebl Wed, 16 Oct 2019 15:24:54 +0200 systemd (241-7~deb10u1)

Bug#934982: latest-debian-changelog-entry-without-new-version triggered for buster/stable uploads

this: systemd (241-7~deb10u1) buster; urgency=medium * Rebuild for buster -- Michael Biebl Sat, 17 Aug 2019 11:00:59 +0200 systemd (241-7) unstable; urgency=medium ... This now triggers a warning from lintian: W: systemd: latest-debian-changelog-entry-without-new-version Looking

Bug#934166: Please add lintian warning for systemd system services using default.target

Am 07.08.19 um 18:22 schrieb Michael Biebl: > Package: lintian > Version: 2.17.0 > Severity: wishlist > > Hi, > > I noticed a couple of systemd system services > (files that match /lib/systemd/system/*.{service,socket,...}) > that use > > [Install] > Alias=d

Bug#934166: Please add lintian warning for systemd system services using default.target

Package: lintian Version: 2.17.0 Severity: wishlist Hi, I noticed a couple of systemd system services (files that match /lib/systemd/system/*.{service,socket,...}) that use [Install] Alias=default.target default.target is only an alias and should not be used for that. Instead services should

Bug#933109: package-supports-alternative-init-but-no-init.d-script produces too many false positives

Package: lintian Version: 2.16.0 Severity: normal Hi, this is a follow-up to #931889. This bug report has been marked as fixed by downgrading the severity from important to minor. The underlying issue is still, that this test is currently way too primitive and produces too many false positives

Bug#931847: Boggus package-supports-alternative-init-but-no-init.d-script test?

On 18.07.19 21:43, Michael Biebl wrote: > Hm, why the moreinfo tag? > This lintian check is clearly way too broad to be useful as-is. > At its current state, please demote it to pedantic (or reverting it > completely) until it actually is useful. Fwiw, I've only seen 100s of false

Bug#931847: Boggus package-supports-alternative-init-but-no-init.d-script test?

On Thu, 11 Jul 2019 11:39:28 -0300 "Chris Lamb" wrote: > block 931847 by 911165 > tags 931847 + moreinfo > thanks > > Ansgar Burchardt wrote: > > > > My understanding of the policy is that, if a package supports an > > > alternative init (other than systemd) it must also support sysvinit. > > >

Bug#931889: package-supports-alternative-init-but-no-init.d-script way too aggressive

Package: lintian Version: 2.16.0 Severity: normal Hi, in several of my packages I get a lintian error since a few days ago: package-supports-alternative-init-but-no-init.d-script All of them false positives. There are a lot of cases where a service ships a systemd service file but not a sysv

Bug#926823: executable-not-elf-or-script should consider PE binaries

Am 11.04.19 um 01:22 schrieb Felix Lechner: > It's just that the lintian tag is not > triggered when the bit is off. That much I figured :-) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP

Bug#926823: executable-not-elf-or-script should consider PE binaries

Am 10.04.19 um 23:46 schrieb Felix Lechner: > On Wed, Apr 10, 2019 at 2:33 PM Michael Biebl wrote: >> >> systemd ships EFI binaries which are PE executables. >> >> usr/lib/systemd/boot/efi/linuxia32.efi.stub [amd64, i386] >> usr/lib/systemd/boot/e

Bug#926823: executable-not-elf-or-script should consider PE binaries

Package: lintian Version: 2.12.0 Severity: normal Hi, systemd ships EFI binaries which are PE executables. This triggers lintian: executable-not-elf-or-script usr/lib/systemd/boot/efi/linuxia32.efi.stub [amd64, i386] usr/lib/systemd/boot/efi/linuxx64.efi.stub [amd64, i386]

Bug#922862: Please add a test for packages that are shipping a cron script/config file and not a .timer

Am 12.03.19 um 14:38 schrieb Chris Lamb: > Hi Michael, > >> Seeing that the new lintian is available since for almost 3 weeks, is it >> normal that >> https://lintian.debian.org/tags/missing-systemd-timer-for-cron-script.html >> only lists a couple of packages? > > No, see #890873. > >> Are

Bug#922862: Please add a test for packages that are shipping a cron script/config file and not a .timer

Seeing that the new lintian is available since for almost 3 weeks, is it normal that https://lintian.debian.org/tags/missing-systemd-timer-for-cron-script.html only lists a couple of packages? Are those results on lintian.d.o regularly updated when new lintian versions are uploaded (i.e. do you

Bug#922862: Please add a test for packages that are shipping a cron script/config file and not a .timer

On Sat, 23 Feb 2019 12:55:39 -0800 Russ Allbery wrote: > Laurent Bigonville writes: > > > So my idea was, we can either force the installation of anacron again (I > > wonder if we shouldn't do that for buster anyway) or we go forward and > > we move to use systemd timers instead of cron (which

Bug#913078: Please warn if PIDFile in a .service unit contains /var/run

Package: lintian Version: 2.5.111 Severity: wishlist Hi, debian introduced /run a couple of releases ago and nowadays /var/run is merely a symlink pointing to /run. I would consider it best practice nowadays that packages use /run directly instead of /var/run and would therefor like to see a

Bug#908185: False positive init.d-script-possible-missing-stop for rcS init scripts

Package: lintian Version: 2.5.100 Severity: normal I just updated the udev init script (which starts in runlevel S) to be stopped on shutdown and reboot. Now I get this lintian warning: W: udev: init.d-script-possible-missing-stop etc/init.d/udev 1 N: N:The given /etc/init.d script indicates

Bug#907845: Warn if compat level 11 is used and dh_system_* helpers are used

On Mon, 03 Sep 2018 06:19:28 +0200 Michael Biebl wrote: > Package: lintian > Version: 2.5.99 > Severity: wishlist > > Hi, > > in compat level 11, dh_systemd_start and dh_systemd_enable have been > deprecated in favour of dh_installsystemd. > dh will also no longe

Bug#907845: Warn if compat level 11 is used and dh_system_* helpers are used

On 9/3/18 06:19, Michael Biebl wrote: > Package: lintian > Version: 2.5.99 > Severity: wishlist > > Hi, > > in compat level 11, dh_systemd_start and dh_systemd_enable have been > deprecated in favour of dh_installsystemd. > dh will also no longer run the dh_systemd_{s

Bug#907845: Warn if compat level 11 is used and dh_system_* helpers are used

Package: lintian Version: 2.5.99 Severity: wishlist Hi, in compat level 11, dh_systemd_start and dh_systemd_enable have been deprecated in favour of dh_installsystemd. dh will also no longer run the dh_systemd_{start,enable} helpers during build. I've seen a couple of packages which have updated

Bug#870704: warn if native systemd service files only wrap existing SysV/LSB init scripts

Package: lintian Version: 2.5.52 Severity: normal Looking at https://codesearch.debian.net/search?q=Exec.*%3D%2Fetc%2Finit.d%2F there are quite a few native systemd .service file which simply use the existing SysV init script via ExecStart/ExecStop/... We should actively discourage that. For

Bug#864999: Please don't emit init.d-script-needs-depends-on-lsb-base if package ships native service file

Package: lintian Version: 2.5.50.4 Severity: normal Hi, lintian added a check which warns if a SysV init script uses the lsb init-functions but doesn't have a dependency on lsb-base. For a package which ships a native service file where the SysV init script is only used to support booting with

Bug#839861: lintian: init.d-script-needs-depends-on-lsb-base does not use strict enough lsb-base version for (eg.) status_of_proc

On Mon, 10 Oct 2016 19:37:30 +0200 Vincent Bernat wrote: > ❦ 5 octobre 2016 21:10 CEST, Chris Lamb  : > > >> here are more precise checks that could also be done; such as: > >> - any use of status_of_proc from /lib/lsb/init-functions needs > >> lsb-base

Bug#857194: Add check for obsolete systemd BindTo= option

/systemd.pm (from lintian package) >From d390729926ba5ae34fe2f7132ae7b10608f55ff1 Mon Sep 17 00:00:00 2001 From: Michael Biebl <bi...@debian.org> Date: Wed, 8 Mar 2017 20:26:21 +0100 Subject: [PATCH] c/systemd: Check for obsolete BindTo= option The BindTo= option has been deprecated

Bug#841475: False positive outdated-autotools-helper-file with dh compat 10

Package: lintian Version: 2.5.48 Severity: normal Hi, I use dh compat 10 with a package that has very old config.{sub,guess} files: W: libgnomecanvas source: outdated-autotools-helper-file config.guess 2009-11-20 W: libgnomecanvas source: outdated-autotools-helper-file config.sub 2009-11-20

Bug#838997: lintian: checks/init.d: Check for initscripts that source /lib/lsb/init-functions without declaring the corresponding dependency on lsb-base (>= 3.0-6).

Am 13.10.2016 um 12:26 schrieb Michael Biebl: > I would prefer having the version requirement dropped as well. It seem > rather pointless when even oldstable has a newer version. > > Aside from this issue: Should we handle packages differently which ship > native systemd servi

Bug#838997: lintian: checks/init.d: Check for initscripts that source /lib/lsb/init-functions without declaring the corresponding dependency on lsb-base (>= 3.0-6).

On Tue, 11 Oct 2016 08:44:57 +0200 Vincent Bernat wrote: > ❦ 8 octobre 2016 13:05 CEST, Evgeni Golov  : > > >> > > But all-in-all, what matters is the dependency, as there were no > >> > > changes > >> > > since 2013 (4.1+Debian10), and Jessie has

Bug#695345: Please add a check for gobject-introspection packages

Am 21.09.2016 um 20:00 schrieb Simon McVittie: > After getting this wrong in Flatpak, I have attached a proposed patch > for a new "gir" family of checks. Nice co-incidence. I've just uploaded a new version of gobject-introspection with a small update to policy.txt, mentioning that multiarch

Bug#835449: false positive: missing-build-dependency-for-dh_-command dh_autoreconf => dh-autoreconf

Package: lintian Version: 2.5.46 Severity: normal Hi, we have a package which uses debhelper compat level 10 (for automatic dh-autoreconf support) and for that the package has a versioned Build-Depends on debhelper (>= 9.20160403~). This should ensure that dh-autoreconf is pulled in by

Bug#821404: Falsse positive source-is-missing (for yelp-xsl)

Package: lintian Version: 2.5.43 Severity: normal Lintian reports many missing source files for yelp-xsl [1] If we look at one of them, like [2], those are the non-minified versions. So simply checking for line length doesn't seem to be a good enough indicator. [1]

Bug#723886: Don't flag pkg-config-multi-arch-wrong-dir reports as error

Package: lintian Version: 2.5.17 Severity: normal Hi Nils, this is a follow up on our IRC discussion. The following lintian error === E: libgmime-2.6-dev: pkg-config-multi-arch-wrong-dir usr/lib/pkgconfig/gmime-2.6.pc N: N:

Bug#723886: Don't flag pkg-config-multi-arch-wrong-dir reports as error

Am 20.09.2013 23:03, schrieb Russ Allbery: As we found out, pkg-config actually strips such library system search paths: $ pkg-config --static --libs gmime-2.6 -pthread -lgmime-2.6 -lnsl -lgpgme-pthread -lassuan -lgpg-error -lpthread -lgio-2.0 -lz -lresolv -lgmodule-2.0 -ldl -lgobject-2.0

Bug#721252: False positive: license-problem-gfdl-invariants for translation files in gtk-doc

Package: lintian Version: 2.5.17 Severity: normal Checking gtk-doc 1.19-1 with lintian, I get the following lintian errors E: gtk-doc source: license-problem-gfdl-invariants help/manual/de/de.po E: gtk-doc source: license-problem-gfdl-invariants help/manual/el/el.po E: gtk-doc source:

Re: libgtk-3-0: triggers ci file contains unknown directive `interest-noawait' on install (needs newer dpkg)

Am 29.06.2013 00:36, schrieb Jonathan Nieder: Michael Biebl wrote: Couldn't debhelper/dh_installdeb generate that Pre-Depends via ${misc:Pre-Depends} if debian/*.triggers contains noawait? That sounds better to me then hard-coding the dependency. I think that sounds reasonable

Re: Bug#714409: libgtk-3-0: triggers ci file contains unknown directive `interest-noawait' on install (needs newer dpkg)

Am 29.06.2013 00:51, schrieb Michael Biebl: Thinking about it, it might probably also be useful to have a lintian check for this. Sounds like it would be rather simple to implement. But then again, I dunno how wide-spread those noawait triggers are and if a lintian check would be worth

Bug#695345: Please add a check for gobject-introspection packages

Package: lintian Version: 2.5.10.2 Severity: wishlist Hi, packages shipping gobject-introspection files should follow the mini policy outlined at [1]. If they install the introspection files into the system paths, the .typelib file should go into a gir1.2-foo-X.Y package. The .gir file should

Bug#652123: Please add new sections (introspection/education/metapackages) to checks/fields

Package: lintian Version: 2.5.4 Severity: normal See http://lists.debian.org/debian-devel/2011/12/msg00051.html Would be great if those new sections would be added to checks/fields. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200,

Bug#604620: Acknowledgement (Please warn if LSB init header does not have a Description and Short-Description field)

In case you're interested, I did some statistics: We currently ship 1085 sysv init scripts in unstable. LSB header completely missing: 2 missing Description: 408 missing Short-Description: 121 missing Provides: 2 missing Required-Start: 7 missing Required-Stop: 7 missing Should-Start: 661

Bug#571280: false positive for init.d-script-missing-dependency-on-remote_fs /etc/init.d/rsyslog: required-stop

On 21.03.2010 00:37, Russ Allbery wrote: Michael Biebl bi...@debian.org writes: the rsyslog init script has the following LSB header ### BEGIN INIT INFO # Provides: rsyslog # Required-Start:$remote_fs $time # Required-Stop: umountnfs $time # X-Stop-After: sendsigs

Bug#571280: false positive for init.d-script-missing-dependency-on-remote_fs /etc/init.d/rsyslog: required-stop

Package: lintian Version: 2.3.3 Severity: normal Hi, the rsyslog init script has the following LSB header ### BEGIN INIT INFO # Provides: rsyslog # Required-Start:$remote_fs $time # Required-Stop: umountnfs $time # X-Stop-After: sendsigs # Default-Start: 2 3 4 5 #

Bug#466617: lintian: Wrong spelling-error-in-copyright for publically

Package: lintian Version: 1.23.45 Severity: normal Lintian warns about a mis-spelling in one of my packages: W: libsvnqt4: spelling-error-in-copyright publically publicly Imho, both spellings are correct [1] and the check is wrong. Cheers, Michael [1]

Bug#466617: Acknowledgement (lintian: Wrong spelling-error-in-copyright for publically)

I have to add, that I'm not a native speaker. So in case I'm wrong, please let me know. The lintian warning was not verbose enough to explain why it thinks publically is not correct. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed

Bug#463495: lintian should check doc-base files for old menu sections

Package: lintian Version: 1.23.42 Severity: normal Hi, lintian already warns, if menu files use old section names. doc-base files [1] should use the same section names as specified by the menu policy, so lintian should check the Section field in debian/*.doc-base files, too. Cheers, Michael

Bug#442709: lintian: complains about desktop-entry-invalid-category Applet although OnlyShowIn is set

Package: lintian Version: 1.23.34 Severity: normal Quoting the menu spec [1] The table below describes Reserved Categories. Reserved Categories have a specific desktop specific meaning that has not been standardized (yet). Desktop entry files that use a reserved category MUST also include an

Bug#375246: tar: *control: Not found in archive, pattern matching characters used in file names

Package: lintian Version: 1.23.21 Severity: grave lintian fails on all deb packages with the following output: lintian /home/michael/debian/build-area/kpowersave_0.6.2-1_i386.changes tar: Pattern matching characters used in file names. Please, tar: use --wildcards to enable pattern matching, or

Bug#315919: update on ~

The last post is from july 2005. Has there been progress in between to get ~ officially accepted by the Debian infrastructure? Is it safe to use it? Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc