date:20220927

Bug#1019446: kde-config-cron: Binary missing

2022-09-27 Thread Aurélien COUDERC

Hi,

Le samedi 24 septembre 2022, 10:31:26 CEST c.bu...@posteo.jp a écrit :
> Dear Bernhard,
> 
> thanks for the reply.
> 
> On 2022-09-24 10:09 Bernhard Übelacker  wrote:
> > I guess the kcm_cron.so is really just like a module
> > loaded by systemsettings5.
> 
> "systemsettings" and "systemsettings5" does not exist on my system and
> not in the repos (via "apt-cache search").

That’s incorrect :

$ apt-file search bin/systemsettings
systemsettings: /usr/bin/systemsettings   
systemsettings: /usr/bin/systemsettings5

> It seems to me that the package "kde-config-cron" has some missing
> dependencies.

Yes indeed, it’s missing a dependency on the systemsettings package, I’ll add 
it in the next upload.


Happy hacking,
--
Aurélien

Bug#1020895: whatmaps: postinst fails in clean chroot/container

2022-09-27 Thread Gioele Barabucci


Package: whatmaps
Version: 0.0.12-3
Severity: serious

Dear whatmaps maintainer,

whatmaps' postinst maintscript fails when run in a newly created 
unstable system, as used by autopkgtest.


Setting up whatmaps (0.0.12-3) ...
sed: can't read /etc/apt/apt.conf.d/20services: No such file
or directory
dpkg: error processing package whatmaps (--configure):
 installed whatmaps package post-installation script
 subprocess returned error exit status 2

A full log can be found at .

As of 2022-09-28, this can be reproduced using autopkgtest and lxc:

$ sudo autopkgtest-build-lxc debian sid
$ autopkgtest . -- lxc --sudo autopkgtest-sid

Regards,

--
Gioele Barabucci

Bug#1020894: glibc: Firefox 88 broken after glibc upgrade

2022-09-27 Thread программист некто

Source: glibc
Version: 2.36-1
Severity: important

Hello. Tabs in Firefox 88 stop working after upgrade glibc to 2.36-1 from 
2.33-8. Every new opened tab immediately crashes.
I try to install old version glibc and found that 2.34 and 2.35 also breaks 
Firefox 88.
There is a regression in glibc.
In log file .xsession-errors I found this:

###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0039,name=PContent::Msg_UpdateSharedData) Channel error: cannot 
send/recv
[Parent 1123, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed 
descriptors: file 
./ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0039,name=PContent::Msg_UpdateSharedData) Channel error: cannot 
send/recv
[Parent 1123, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed 
descriptors: file 
./ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0039,name=PContent::Msg_UpdateSharedData) Channel error: cannot 
send/recv
[Parent 1123, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed 
descriptors: file 
./ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0039,name=PContent::Msg_UpdateSharedData) Channel error: cannot 
send/recv
[Parent 1123, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed 
descriptors: file 
./ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel error: cannot send/recv
[Parent 1123, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed 
descriptors: file 
./ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0074,name=PContent::Msg_RegisterBrowsingContextGroup) Channel 
error: cannot send/recv
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel 
error: cannot send/recv
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0003,name=PContent::Msg_ConstructBrowser) Channel error: cannot 
send/recv
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel 
error: cannot send/recv
###!!! [Parent][MessageChannel] Error: 
(msgtype=0xB8000E,name=PWindowGlobal::Msg_SetContainerFeaturePolicy) Channel 
error: cannot send/recv
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x3A0143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel 
error: cannot send/recv
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x230071,name=PBrowser::Msg_InitRendering) Channel error: cannot 
send/recv
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x2300A2,name=PBrowser::Msg_SafeAreaInsetsChanged) Channel error: 
cannot send/recv
###!!! [Parent][MessageChannel] Error: 
(msgtype=0x23009B,name=PBrowser::Msg_LoadRemoteScript) Channel error: cannot 
send/recv

Bug#1020865: ntpsec-ntpdate: ntpdate-debian doesn't work due to missing dependency

2022-09-27 Thread Richard Laager

On 9/27/22 14:00, Dima Kogan wrote:

root@shorty:/home/dima# ntpdate-debian
sed: can't read /etc/ntpsec/ntp.conf: No such file or directory

Yep, I see the issue. I'll upload a fix.

The missing file is in the "ntpsec" package, which is not in the
Depends, and maybe should be there. If I install this package I see
this:

root@shorty:/home/dima# ntpdate-debian
ntpdig: socket error on transmission: [Errno 99] Cannot assign requested
address
ntpdig: socket error on transmission: [Errno 99] Cannot assign requested
address
ntpdig: socket error on transmission: [Errno 99] Cannot assign requested
address
ntpdig: socket error on transmission: [Errno 99] Cannot assign requested
address

{"time":"2022-09-27T11:54:36.227571-0700","offset":-0.001772,"precision":0.073811,"host":"0.debian.pool.ntp.org","ip":"79.133.44.139","stratum":1,"leap":"no-leap","adjusted":false}

This is probably the ipv6 bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971523

The console output doesn't tell me if the errors were fatal or not. Were
they actually warnings? It should tell me.

These are not fatal. I've submitted a patch upstream to suppress those
messages except in debug mode, since they are clearly confusing:

https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1288

Debian bug #971523 probably should have been marked fixed already once
the upstream change to make them non-fatal was uploaded to Debian. But
given I'm submitting another patch, I'll leave it open.

If you have further commentary on this part, let's discuss in 971523.

Also, the output is qualitatively different from what it used to be not
very long ago. It used to be human-readable text

...

Now it's JSON

Yeah, I'll disable that JSON.

--
Richard
--
Richard

OpenPGP_signature
Description: OpenPGP digital signature

Bug#971523: ntpsec-ntpdate: ntpdate fail if DNS name for server resolve to IPv6

2022-09-27 Thread Richard Laager

I've submitted a patch upstream to suppress those messages except in 
debug mode, since they are clearly confusing:


https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1288

This bug probably should have been marked fixed already once the 
upstream change to make them non-fatal was uploaded to Debian. But given 
I'm submitting another patch, I'll leave it open.


--
Richard



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020893: lsb-release: lsb_release command said 'No LSB modules are available.'

2022-09-27 Thread Yukiharu YABUKI

Package: lsb-release
Version: 12.0-1
Severity: important
X-Debbugs-Cc: yyab...@debian.org

Dear Maintainer,

lsb_release command says

```
$ lsb_release -cs
No LSB modules are available.
n/a

$ lsb_release
No LSB modules are available
```

I'd like to get infomation from lsb_release command.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

2022-09-27 Thread Soren Stoutner

On Tuesday, September 27, 2022 8:29:30 PM MST Andres Salomon wrote:
> The "team" would just be me (wanna join? :),

Currently my interests lie elsewhere, but I may reconsider that in the future.

> and I had to do some
> security uploads today and haven't had the chance to look further into
> this. Unfortunately, there's a few other high-priority things I need to
> deal with before I can take a look.

That’s fine.  This is a low priority, so it can wait until whenever you have 
time to look at it.

-- 
Soren Stoutner
so...@stoutner.com

signature.asc
Description: This is a digitally signed message part.

Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

2022-09-27 Thread Andres Salomon

The "team" would just be me (wanna join? :), and I had to do some 
security uploads today and haven't had the chance to look further into 
this. Unfortunately, there's a few other high-priority things I need to 
deal with before I can take a look.


On Tue, Sep 27, 2022 at 20:27, Soren Stoutner  
wrote:
Does anyone from the Chromium team have any insights into the 
feasibility of Chromium using a system-wide directory for .bdic files?




--

Soren Stoutner

so...@stoutner.com

Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

2022-09-27 Thread Soren Stoutner

Does anyone from the Chromium team have any insights 
into the feasibility of Chromium using a system-wide 
directory for .bdic files?


-- 
Soren Stoutner
so...@stoutner.com 


signature.asc
Description: This is a digitally signed message part.

Bug#1020892: cinnamon: Square icon on the title bar is too small

2022-09-27 Thread Green

Source: cinnamon
Version: 4.8.6
Severity: normal

Dear Maintainer,

Square icon on the title bar is too small

"Square icon" means the icon that can make a default window into a full screen 
mode.
Please compare it with other default themes of GNOME, MATE, or Windows.

The problem is that there is no preference in System > Windows > Titlebar > 
Buttons in Desktop Menu.

Icons inside title bar are too small to use. They should be made larger that 
every can easily tell at just one look.

Thank you,

Green

Bug#1020891: ltrace: enable arm/aarch64 builds

2022-09-27 Thread Dominique Martinet

Source: ltrace
Version: 0.7.3-6.3
Severity: normal

Dear Maintainer,

Using https://gitlab.com/cespedes/ltrace that you seem to maintain arm
and aarch64 versions of ltrace compile and work.

Would it be possible to consider cutting a new release and updating the
package in sid/bookworm for these archs?

Thank you

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.145-0-at (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Bug#1020783: init-system-helpers 1.65.2 broke cdebootstrap

2022-09-27 Thread Luca Boccassi

Control: retitle -1 libdebian-installer: cannot parse dependencies with 
multiarch qualifier
Control: reassign -1 libdebian-installer4 0.123
Control: tags -1 patch

On Mon, 26 Sep 2022 18:05:39 +0200 Ansgar  wrote:
> On Mon, 2022-09-26 at 17:54 +0200, Holger Levsen wrote:
> > Sadly I've only enabled verbose bootstrapping today, but at least I
> > did that now
> > so you can look at
> >
https://jenkins.debian.net/job/reproducible_cdebootstrap_unstable/40/consoleFull
> > and maybe actually understand the problem:
> 
> There is this warning:
> 
> +---
> | W: resolver (perl:any): package doesn't exist
> +---
> 
> Which looks like cdebootstrap doesn't handle the multi-arch qualifier
> (in usrmerge's Depends field), then fails to install usrmerge (as
> dependency of init-system-helpers) and thus init-system-helpers.
> 
> I guess the last one missing causes this:
> 
> > (
> >
https://jenkins.debian.net/job/reproducible_cdebootstrap_bullseye/30/c
> > onsole
> > is a verbose build too.)
> > 
> > So I *guess* this is the place it breaks:
> > 
> > /var/lib/dpkg/info/dpkg.postinst: 115: deb-systemd-helper: not
found
> > /var/lib/dpkg/info/dpkg.postinst: 118: deb-systemd-helper: not
found
> > /var/lib/dpkg/info/dpkg.postinst: 125: deb-systemd-helper: not
found
> > P: Configuring package dpkg
> 
> We had a similar problem with base-installer (used as an
implementation
> detail of debootstrap in d-i):
> 
> https://bugs.debian.org/1020426
> 
> Which has a patch available:
> 
>
https://salsa.debian.org/installer-team/base-installer/-/merge_requests/9

Yeah it's the same problem, this time in libdebian-installer which
provides the di_packages_resolve_dependencies() API used by
cdebootstrap.

I've done a quick and superficial test of a similar change to ignore
the qualifier and it fixes the issue:

https://salsa.debian.org/installer-team/libdebian-installer/-/merge_requests/4

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#903999: ITP: php-doc -- Documentation for PHP

2022-09-27 Thread Paul Wise

On Mon, 2022-09-26 at 16:23 -0300, Athos Ribeiro wrote:

> As mentioned in the original report (RFP), this package was
> originally removed from the archive due to Bug #821695, when it was
> not updated during the PHP 7 transition.

If you weren't already aware, please note the extra steps needed when
reintroducing packages that were removed from Debian (e.g. bug reopen):

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#1020890: rust-ipfs-unixfs - depends on old version of multihash.

2022-09-27 Thread Peter Green


Package: rust-ipfs-unixfs
Version: 0.2.0-2
Severity: important
X-debbugs-cc: d...@jones.dk
Control: block 1020418 by -1
Control: block 1020419 by -1

rust-ipfs-unixfs depends on version 0.11 of the multihash crate which was 
superseeded nearly 2 years ago
and depends on an old version of the rustcrypto hash packages. Currently we 
have two versions of some of
the rustcrypto packages in Debian while others are still on old versions.

Jonas recently requested updates of two more rustcrypto packages block-buffer 
and block-padding, on the
one hand I think these should be updated, on the other hand I don't really want 
to further increase the
number of packages for which we are carrying multiple versions in Debian.

So I started looking to see if I could update ipfs-unixfs to use the new 
version of multihash, the good
news is I managed to get it to build, the bad news is I still have several test 
failures, I may take
another look at this later, but feedback from someone who actually understands 
the code would be
appreciated.Index: ipfs-unixfs/Cargo.toml
===
--- ipfs-unixfs.orig/Cargo.toml
+++ ipfs-unixfs/Cargo.toml
@@ -24,8 +24,9 @@ repository = "https://github.com/rs-ipfs
 name = "ingest-tar"
 harness = false
 [dependencies.cid]
-version = "0.5"
+version = "0.8"
 default-features = false
+features = ["std"]
 
 [dependencies.either]
 version = "1.5"
@@ -36,8 +37,9 @@ version = "0.2.12"
 optional = true
 
 [dependencies.multihash]
-version = "0.11"
+version = "0.16"
 default-features = false
+features = ["sha2","multihash-impl"]
 
 [dependencies.quick-protobuf]
 version = "0.7"
@@ -45,7 +47,7 @@ features = ["std"]
 default-features = false
 
 [dependencies.sha2]
-version = "0.9"
+version = "0.10"
 default-features = false
 [dev-dependencies.criterion]
 version = "0.3"
Index: ipfs-unixfs/src/dir/builder/custom_pb.rs
===
--- ipfs-unixfs.orig/src/dir/builder/custom_pb.rs
+++ ipfs-unixfs/src/dir/builder/custom_pb.rs
@@ -71,7 +71,7 @@ impl<'a> MessageWrite for WriteableCid<'
 use cid::Version::*;
 use quick_protobuf::sizeofs::*;
 
-let hash_len = self.0.hash().as_bytes().len();
+let hash_len = self.0.hash().to_bytes().len();
 
 match self.0.version() {
 V0 => hash_len,
@@ -99,7 +99,7 @@ impl<'a> MessageWrite for WriteableCid<'
 
 self.0
 .hash()
-.as_bytes()
+.to_bytes()
 .iter()
 // while this looks bad it cannot be measured; note we cannot use the
 // write_bytes because that is length prefixed bytes write
Index: ipfs-unixfs/src/dir/builder/iter.rs
===
--- ipfs-unixfs.orig/src/dir/builder/iter.rs
+++ ipfs-unixfs/src/dir/builder/iter.rs
@@ -4,6 +4,7 @@ use super::{
 use cid::Cid;
 use core::fmt;
 use std::collections::HashMap;
+use multihash::MultihashDigest;
 
 /// Constructs the directory nodes required for a tree.
 ///
@@ -141,7 +142,7 @@ impl PostOrderIterator {
 
 buffer.truncate(size);
 
-let mh = multihash::wrap(multihash::Code::Sha2_256, ::digest());
+let mh = multihash::Code::Sha2_256.wrap(::digest()).unwrap();
 let cid = Cid::new_v0(mh).expect("sha2_256 is the correct multihash for cidv0");
 
 let combined_from_links = links
Index: ipfs-unixfs/src/symlink.rs
===
--- ipfs-unixfs.orig/src/symlink.rs
+++ ipfs-unixfs/src/symlink.rs
@@ -35,6 +35,7 @@ mod tests {
 use cid::Cid;
 use core::convert::TryFrom;
 use sha2::{Digest, Sha256};
+use multihash::MultihashDigest;
 
 #[test]
 fn simple_symlink() {
@@ -45,7 +46,7 @@ mod tests {
 // `foo_directory/b`.
 serialize_symlink_block("b",  buf);
 
-let mh = multihash::wrap(multihash::Code::Sha2_256, ::digest());
+let mh = multihash::Code::Sha2_256.wrap(::digest()).unwrap();
 let cid = Cid::new_v0(mh).expect("sha2_256 is the correct multihash for cidv0");
 
 assert_eq!(
Index: ipfs-unixfs/src/test_support.rs
===
--- ipfs-unixfs.orig/src/test_support.rs
+++ ipfs-unixfs/src/test_support.rs
@@ -2,6 +2,7 @@ use cid::Cid;
 use core::convert::TryFrom;
 use hex_literal::hex;
 use std::collections::HashMap;
+use multihash::MultihashDigest;
 
 #[derive(Default)]
 pub struct FakeBlockstore {
@@ -29,7 +30,7 @@ impl FakeBlockstore {
 sha.update(block);
 let result = sha.finalize();
 
-let mh = multihash::wrap(multihash::Code::Sha2_256, [..]);
+let mh = multihash::Code::Sha2_256.wrap([..]).unwrap();
 let cid = Cid::new_v0(mh).unwrap();
 
 assert!(
Index: ipfs-unixfs/src/file/adder.rs
===
---

Bug#1016811: libwebkit2gtk-4.0-37: bullseye backport crashes a lot on arm64

2022-09-27 Thread Dominique MARTINET

Hello,

Dominique MARTINET wrote on Tue, Sep 27, 2022 at 01:58:40PM +0900:
> I will rebuild the package again without the patch, to check if I can
> reproduce the issue without it in my build environment.
> 
> That takes quite a while, so will probably only report back tomorrow.

So I can confirm the same package as sid's 2.38.0-2 without any extra
patch works just fine if I recompile it -- so it must be a difference in
our build environment.

Happy to send you the list of packages I have installed or anything else
that might be useful to track this down further!


(As a side note, it turns out that even when this does works, gdk opengl
context creation fails on my system because it apparently always try to
initialize the context as opengl first regardless of GLES setting so
this isn't as good as I was hoping... In particular the fallback code
rotates the rendered pixels by 180° for some reason so it's upside down,
but removing that as well is perfect if just a bit slow.
Hopefully I can figure that out next... Did I already say I hate closed
drivers?
But anyway that's unrelated to this bug: epiphany (and MiniBrowser) work
just fine at this point; and I'll open a bug upstream directly for the
fallback code)

-- 
Dominique

Bug#1020189: still failing with dh-elpa 2.0.12

2022-09-27 Thread David Bremner



This looks like a real bug though, unrelated to native compilation

Searched 1/1 files
   passed  19/87  helpful--display-implementations (0.122235 sec)
   passed  20/87  helpful--docstring (0.44 sec)
Test helpful--docstring-advice backtrace:
  signal(ert-test-failed (((should (equal (helpful--docstring #'test-f
  ert-fail(((should (equal (helpful--docstring #'test-foo-advised t) "
  (if (unwind-protect (setq value-47 (apply fn-45 args-46)) (setq form
  (let (form-description-49) (if (unwind-protect (setq value-47 (apply
  (let ((value-47 'ert-form-evaluation-aborted-48)) (let (form-descrip
  (let* ((fn-45 #'equal) (args-46 (condition-case err (let ((signal-ho
  (let ((lexical-binding t)) (let* ((fn-45 #'equal) (args-46 (conditio
  (closure (t) nil (let ((lexical-binding t)) (let* ((fn-45 #'equal) (
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name helpful--docstring-advice :documentat
  ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
  ert-run-tests(t #f(compiled-function (event-type  event-args) #
  ert-run-tests-batch(nil)
  ert-run-tests-batch-and-exit()
  command-line-1(("-l" "package" "--eval" "(setq native-compile-target
  command-line()
  normal-top-level()
Test helpful--docstring-advice condition:
(ert-test-failed
 ((should
   (equal
(helpful--docstring ... t)
"Docstring here too."))
  :form
  (equal "Docstring here too.\n\nThis function has :around advice: 
`ad-Advice-test-foo-advised'." "Docstring here too.")
  :value nil :explanation
  (arrays-of-different-length 84 19 "Docstring here too.\n\nThis function 
has :around advice: `ad-Advice-test-foo-advised'." "Docstring here too." 
first-mismatch-at 19)))
   FAILED  21/87  helpful--docstring-advice (0.000165 sec)
   passed  22/87  helpful--docstring-keymap (0.000490 sec)

Bug#1020249: PipeWire?

2022-09-27 Thread Jeremy Bicha

On Tue, Sep 27, 2022 at 5:36 PM Herbert Snorrason  wrote:
>
> I'm guessing this is why a.) my system removed pulseaudio in favour of 
> pipewire
> and b.) removed gnome and gnome-core when I reinstalled pulseaudio to get
> working sound again.
>
> Do I understand correctly that I need to figure how to get pipewire working
> before the gnome and gnome-core packages can be installed again? Pipewire
> completely fails to start, and I really don't see how it's unreasonable to
> prefer continuing to use the sound system that, you know, works. :)

Did you restart your computer after installing pipewire?

If you still have issues, please file a new bug, probably against pipewire.

Generally, the GNOME metapackages are provided by the Debian GNOME
team to give users a complete working set of packages without allowing
arbitrary substitutions. It's possible to have a system without
gnome-core and gnome installed, but then you're on your own.

Thank you,
Jeremy Bicha

1 2 >

1 - 100 of 185 matches

Mail list logo