On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> Hi,
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
what do people think about getting rid of current suite names ("stable",
"testing", "unstable") for most purposes? We already recommend using
codenames instead as those don't change their meaning when a new release
happens.
Hi Ansgar,
Regarding suite names (stable, testing, and unstable),
Michael Kesper schrieb:
> On 18.06.19 22:55, Moritz M=C3=BChlenhoff wrote:
>> You may find https://phabricator.wikimedia.org/T148843/#5078403
>> (and later) interesting,=20
>
> This seems to require wikimedia authentication.
> Is there some information publicly available about it?
Ah, that's
On Tue, Jun 25, 2019 at 09:46:00AM +0200, Bastian Blank wrote:
> > Related to that I would like to be able to write something like
> > deb http://deb.debian.org/debian debian11 main
> > deb http://security.debian.org/debian-security debian11-security main
> > in sources.list as codenames
On 25/06/19 14.31, Philip Hands wrote:
Bagas Sanjaya writes:
Russ Allbery:
It sounds like a whole ton of work to get a useful amount of coverage (not
to mention bothering upstreams with questionnaires that I suspect many of
them would find irritating -- I certainly would with my upstream hat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 09:40:51 +0200
Source: neutron-dynamic-routing
Binary: neutron-bgp-dragent neutron-dynamic-routing-common
python3-neutron-dynamic-routing
Architecture: source all
Version: 2:14.0.0-1
Distribution: experimental
On Tue, 25 Jun 2019 at 13:11:09 +0500, Andrey Rahmatullin wrote:
> On Tue, Jun 25, 2019 at 09:46:00AM +0200, Bastian Blank wrote:
> > Can you please elaborate on the "confuse people"?
>
> I guess only (most?) Debian contributors and hardcore Debian users
> remember the order of the codenames and
On Tue, Jun 25, 2019 at 2:08 PM Ansgar wrote:
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
I use these
Am Di., 25. Juni 2019 um 10:15 Uhr schrieb Simon McVittie :
>
> On Tue, 25 Jun 2019 at 09:31:44 +0200, Philip Hands wrote:
> > Also, it seems clear to me that the same game in all Linux disros is
> > very likely to get the same rating, so this would be better done as a
> > distribution agnostic
On 2019-06-25 09:39, Paul Wise wrote:
On Tue, Jun 25, 2019 at 2:08 PM Ansgar wrote:
Related to that I would like to be able to write something like
deb http://deb.debian.org/debian debian11 main
Already kind of possible:
deb http://deb.debian.org/debian Debian9.9 main
With the caveat
Philip Hands writes:
> What is it going to cost us to get 'bison' rated PG? Why is this
> useful?
Erm, not 'PG' -- I meant whatever the "Anyone can watch this" label is.
Although, I guess one could perhaps argue PG for bison:
One could use it to build something that generates offensive
Philipp Kern writes:
> On 2019-06-25 09:31, Philip Hands wrote:
>>> Russ Allbery:
It sounds like a whole ton of work to get a useful amount of coverage
(not
to mention bothering upstreams with questionnaires that I suspect
many of
them would find irritating -- I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 11:09:04 +0200
Source: dkms
Binary: dkms
Architecture: source
Version: 2.7.1-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Dynamic Kernel Modules Support Team
Changed-By: Gianfranco Costamagna
Hi,
what do people think about getting rid of current suite names ("stable",
"testing", "unstable") for most purposes? We already recommend using
codenames instead as those don't change their meaning when a new release
happens.
Related to that I would like to be able to write something like
Russ Allbery:
It sounds like a whole ton of work to get a useful amount of coverage (not
to mention bothering upstreams with questionnaires that I suspect many of
them would find irritating -- I certainly would with my upstream hat on),
and I'm not clear on the benefit. Do you have some reason
On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
Even if
On 5/29/19 11:01 AM, Raphael Hertzog wrote:
> On Wed, 29 May 2019, Ansgar wrote:
>> On Wed, 2019-05-29 at 10:38 +0200, Raphael Hertzog wrote:
>>> On Wed, 29 May 2019, Andrey Rahmatullin wrote:
One of the popular answers to this and some other problems is "nobody sat
down and wrote the
On Ma, 25 iun 19, 08:08:22, Ansgar wrote:
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
AFAIK "unstable" is
Bagas Sanjaya writes:
> Russ Allbery:
>> It sounds like a whole ton of work to get a useful amount of coverage (not
>> to mention bothering upstreams with questionnaires that I suspect many of
>> them would find irritating -- I certainly would with my upstream hat on),
>> and I'm not clear on
Package: wnpp
Followup-For: Bug #914577
Owner: Alexandros Kosiaris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2019-06-25 09:46, Bastian Blank wrote:
> On related notes: For Azure we currently plan (yeah, still not
> finished as MS does not provide input, be we still need to change
> it): - debian-10 - debian-11 - debian-sid
And docker hub have some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:45:13 +0200
Source: dkms
Binary: dkms
Architecture: source
Version: 2.7.1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Dynamic Kernel Modules Support Team
Changed-By: Gianfranco Costamagna
On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> Hi,
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
On 2019-06-25 09:31, Philip Hands wrote:
Russ Allbery:
It sounds like a whole ton of work to get a useful amount of coverage
(not
to mention bothering upstreams with questionnaires that I suspect
many of
them would find irritating -- I certainly would with my upstream hat
on),
and I'm not
On Tue, 25 Jun 2019 at 09:31:44 +0200, Philip Hands wrote:
> Also, it seems clear to me that the same game in all Linux disros is
> very likely to get the same rating, so this would be better done as a
> distribution agnostic level
Appstream metadata, which is canonically provided by upstreams
Simon McVittie:
Appstream metadata, which is canonically provided by upstreams and is
distro- and package-type-agnostic (available in at least apt and Flatpak),
has this as an optional field for self-rating:
-15) experimental; urgency=medium
.
* Update to SVN 20190625 (r272643) from the gcc-8-branch.
- Fix PR middle-end/64242 (PARISC), PR fortran/90937, PR fortran/90744.
* Apply proposed fix for PR libgcc/90712 (ia64 only). Closes: #930119.
Checksums-Sha1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 25 Jun 2019 14:03:25 +0300
Source: qtsvg-opensource-src
Architecture: source
Version: 5.12.4-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Closes: 925815
On Tue, 2019-06-25 at 16:39 +0800, Paul Wise wrote:
> On Tue, Jun 25, 2019 at 2:08 PM Ansgar wrote:
> > what do people think about getting rid of current suite names ("stable",
> > "testing", "unstable") for most purposes? We already recommend using
> > codenames instead as those don't change
On Tue, Jun 25, 2019 at 08:03:49AM -0400, Michael Stone wrote:
> Having "stable" in sources.list is broken, because one day stuff goes from
> working to not working, which requires manual intervention, at which point
> someone could have just changed the name.
Once I had unattended-upgrades do
On Tue, Jun 25, 2019 at 02:38:43PM +0200, Bastian Blank wrote:
On Tue, Jun 25, 2019 at 08:03:49AM -0400, Michael Stone wrote:
Having "stable" in sources.list is broken, because one day stuff goes from
working to not working, which requires manual intervention, at which point
someone could have
On Tue, Jun 25, 2019 at 12:43:56PM +0200, Paride Legovini wrote:
> My question is: are we trying to solve an actual problem here?
No, and please note that the author is not even a Debian user:
https://lists.debian.org/debian-devel/2019/06/msg00376.html
--
WBR, wRAR
signature.asc
Description:
On Tue, Jun 25, 2019 at 8:04 PM Michael Stone wrote:
> Having "stable" in sources.list is broken, because one day stuff goes
> from working to not working, which requires manual intervention, at
> which point someone could have just changed the name. Having codenames
> in sources.list is broken,
~Ansgar writes ("getting rid of "testing""):
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
Others have pointed
On Tue, 25 Jun 2019 at 16:33:53 +0700, Bagas Sanjaya wrote:
> There are no age classifications, however. So based on content_rating tag on
> AppStream metadata, we can add logic to apt in order to determine age rating
> for our packages.
I think this would be unwise. We can never get this right,
Dzień dobry,
w związku z ciągłymi zmianami jakie zachodzą w social mediach, kontaktujemy się
z Państwem,aby zaproponować profesjonalne prowadzenie *FanPage na Facebook’u.
*
Dzięki zdobytemu doświadczeniu, możemy Państwu zapewnić:
-zwiększenie liczby fanów
-brak długoterminowych umów
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 25 Jun 2019 13:18:08 +0200
Source: ionit
Architecture: source
Version: 0.3.2+really0.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung
Changed-By: Benjamin Drung
Closes: 931060
Changes:
ionit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:11:12 +0100
Source: grub2
Architecture: source
Version: 2.02+dfsg1-20
Distribution: unstable
Urgency: medium
Maintainer: GRUB Maintainers
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 931038
Changes:
Hi,
On Tue, 2019-06-25 at 11:40 +0700, Bagas Sanjaya wrote:
> Based on above, what are your opinions/thoughts/positions about
> Content Rating System in Debian?
is this related to your other proposal involving giving "sudo"
permissions to teenagers to handle this age recommendation stuff for TV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 25 Jun 2019 13:05:58 +0200
Source: python-vertica
Binary: python-vertica python3-vertica
Architecture: source all
Version: 0.9.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 25 Jun 2019 21:03:42 +1000
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentynineteen
wordpress-theme-twentyseventeen wordpress-theme-twentysixteen
Architecture: source all
Version: 5.2.2+dfsg1-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 25 Jun 2019 15:17:52 +0300
Source: qtconnectivity-opensource-src
Architecture: source
Version: 5.12.4-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Changes:
Bagas Sanjaya wrote on 25/06/2019:
> Hello Debian Developers,
>
> Debian provides more than 51000 packages. From those packages, some are
> appropriate for every ages, and some others are
> only for specific age groups for some reasons.
>
> In order to inform to users, especially parents, about
On Tue, Jun 25, 2019 at 11:09:06AM +0100, Ian Jackson wrote:
~Ansgar writes ("getting rid of "testing""):
Related to that I would like to be able to write something like
deb http://deb.debian.org/debian debian11 main
deb http://security.debian.org/debian-security debian11-security main
in
On Tue, Jun 25, 2019 at 08:07:51PM +0800, Paul Wise wrote:
On Tue, Jun 25, 2019 at 8:04 PM Michael Stone wrote:
Having "stable" in sources.list is broken, because one day stuff goes
from working to not working, which requires manual intervention, at
which point someone could have just changed
Ian Jackson [2019-06-25 11:09:06+01:00] wrote:
> ~Ansgar writes ("getting rid of "testing""):
>> deb http://deb.debian.org/debian debian11 main
>> deb http://security.debian.org/debian-security debian11-security main
> Yes, please, absolutely. And this should be the default.
> The syntax
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:21:42 +0200
Source: ompl
Binary: libompl-dev libompl15 ompl-demos ompl-plannerarena
Architecture: source
Version: 1.4.2+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
On Tue, Jun 25, 2019 at 11:40:04AM +0700, Bagas Sanjaya wrote:
> Based on above, what are your opinions/thoughts/positions about Content
> Rating System in Debian?
just NO. please create a fork and leave Debian without this.
--
tschau,
Holger
Am Di., 25. Juni 2019 um 11:51 Uhr schrieb Bagas Sanjaya :
>
> Simon McVittie:
>
> Appstream metadata, which is canonically provided by upstreams and is
> distro- and package-type-agnostic (available in at least apt and Flatpak),
> has this as an optional field for self-rating:
>
>
Only a few remarks as former simple user and now maintainer:
* Please don't mix things: release names has a value, distribution names
like oldoldstable, oldstable, stable, testing, unstable has their value too
* the value is that they never change - they are convenient. Especially
if one use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 15:15:44 +0200
Source: r-bioc-biocgenerics
Binary: r-bioc-biocgenerics
Architecture: source
Version: 0.30.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 25 Jun 2019 17:04:53 +0300
Source: qt3d-opensource-src
Architecture: source
Version: 5.12.4+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Changes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 19 Jun 2019 03:32:47 +0200
Source: verilator
Binary: verilator
Architecture: source
Version: 4.016-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team
Changed-By: أحمد المحمودي (Ahmed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 25 Jun 2019 07:19:02 -0700
Source: debian-keyring
Binary: debian-keyring
Architecture: source all
Version: 2019.06.25
Distribution: sid
Urgency: medium
Maintainer: Debian Keyring Maintainers
Changed-By: Jonathan McDowell
On Tue, Jun 25, 2019 at 06:28:13PM +0200, Alf Gaida wrote:
> > oldoldstable has the value of demonstrating some of what's wrong with
> > the current system
>
> Can you please explain, i don't get it
That name is stupid.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Tue, Jun 25, 2019 at 12:40:01PM -0400, Michael Stone wrote:
> > and so on - i take the older releases only as reference.
>
> I just do something like look at https://packages.debian.org/ssh
> Or, if I'm really curious about versions, then something like
>
On Tue, Jun 25, 2019 at 09:43:02PM +0500, Andrey Rahmatullin wrote:
On Tue, Jun 25, 2019 at 12:40:01PM -0400, Michael Stone wrote:
> and so on - i take the older releases only as reference.
I just do something like look at https://packages.debian.org/ssh
Or, if I'm really curious about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:36:19 -0500
Source: sortedcontainers
Architecture: source
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Andrej Shadura
Closes: 888218
Changes:
Am Dienstag, den 25.06.2019, 11:48 -0400 schrieb Michael Stone:
> On Tue, Jun 25, 2019 at 05:01:48PM +0200, Alf Gaida wrote:
> > Only a few remarks as former simple user and now maintainer:
> > * Please don't mix things: release names has a value, distribution
> > names like oldoldstable,
On Tue, Jun 25, 2019 at 05:01:48PM +0200, Alf Gaida wrote:
Only a few remarks as former simple user and now maintainer:
* Please don't mix things: release names has a value, distribution
names like oldoldstable, oldstable, stable, testing, unstable has
their value too
oldoldstable has the
On Tue, Jun 25, 2019 at 06:06:55PM +0200, Benjamin Drung wrote:
Am Dienstag, den 25.06.2019, 11:48 -0400 schrieb Michael Stone:
On Tue, Jun 25, 2019 at 05:01:48PM +0200, Alf Gaida wrote:
> Only a few remarks as former simple user and now maintainer:
> * Please don't mix things: release names
On 25.06.19 17:48, Michael Stone wrote:
oldoldstable has the value of demonstrating some of what's wrong with
the current system
Can you please explain, i don't get it - maybe i to new at this. For me
file like /etc/apt/sources.lists.d/debian.list:
deb http://ftp.debian.org/debian/
On Tue, Jun 25, 2019 at 06:28:13PM +0200, Alf Gaida wrote:
On 25.06.19 17:48, Michael Stone wrote:
oldoldstable has the value of demonstrating some of what's wrong
with the current system
Can you please explain, i don't get it - maybe i to new at this. For
me file like
On 6/25/19 8:27 AM, Holger Levsen wrote:
> On Tue, Jun 25, 2019 at 11:40:04AM +0700, Bagas Sanjaya wrote:
>> Based on above, what are your opinions/thoughts/positions about Content
>> Rating System in Debian?
> just NO. please create a fork and leave Debian without this.
Hard but necessary
On 6/25/19 8:08 AM, Ansgar wrote:
> Hi,
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
>
> Related to that I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 18 Jun 2019 09:13:31 +0200
Source: pushpin
Architecture: source
Version: 1.22.0-1
Distribution: unstable
Urgency: medium
Maintainer: Jan Niehusmann
Changed-By: Jan Niehusmann
Changes:
pushpin (1.22.0-1) unstable;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 07:40:50 -1000
Source: php-phpseclib
Architecture: source
Version: 2.0.20-1
Distribution: experimental
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers
Changed-By: David Prévot
Changes:
php-phpseclib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:11:12 +0100
Source: grub-efi-ia32-signed
Binary: grub-efi-ia32-signed
Architecture: source
Version: 1+2.02+dfsg1+20
Distribution: sid
Urgency: medium
Maintainer: GRUB Maintainers
Changed-By: Debian signing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:11:12 +0100
Source: grub-efi-amd64-signed
Binary: grub-efi-amd64-signed
Architecture: source
Version: 1+2.02+dfsg1+20
Distribution: sid
Urgency: medium
Maintainer: GRUB Maintainers
Changed-By: Debian signing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:11:12 +0100
Source: grub-efi-arm64-signed
Binary: grub-efi-arm64-signed
Architecture: source
Version: 1+2.02+dfsg1+20
Distribution: sid
Urgency: medium
Maintainer: GRUB Maintainers
Changed-By: Debian signing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 17 Jun 2019 16:38:17 +0200
Source: igtf-policy-bundle
Binary: igtf-policy-classic igtf-policy-mics igtf-policy-slcs igtf-policy-iota
igtf-policy-unaccredited igtf-policy-experimental
Architecture: source all
Version: 1.101-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 25 Jun 2019 23:10:15 +0200
Source: ocaml-flac
Binary: libflac-ocaml libflac-ocaml-dbgsym libflac-ocaml-dev
Architecture: source amd64
Version: 0.1.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian OCaml
Package: wnpp
Severity: wishlist
Owner: Kyle Robbertze
* Package name: ocaml-ffmpeg
Version : 0.2.1
Upstream Author : Savonet Team
* URL : https://github.com/savonet/ocaml-ffmpeg
* License : LGPL
Programming Lang: OCaml
Description : OCaml interface
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 26 Jun 2019 00:04:32 +0200
Source: libpaper
Binary: libpaper-dev libpaper-utils libpaper-utils-dbgsym libpaper1
libpaper1-dbgsym
Architecture: source amd64
Version: 1.1.28
Distribution: unstable
Urgency: medium
Maintainer:
On Tue, Jun 25, 2019 at 4:39 PM Paul Wise wrote:
> On Tue, Jun 25, 2019 at 2:08 PM Ansgar wrote:
>
> > what do people think about getting rid of current suite names ("stable",
> > "testing", "unstable") for most purposes? We already recommend using
> > codenames instead as those don't change
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 17 Jun 2019 03:39:06 +0200
Source: sl-modem
Binary: sl-modem-dkms sl-modem-daemon
Architecture: source amd64 i386
Version: 2.9.11~20110321-16
Distribution: unstable
Urgency: medium
Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy)
Emmanuel Arias:
IMO this idea represent a big work. And if you want to involved
upstream, maybe will be a problem. Some upstream, could not be
interest on participate because could be a "extra" work. But if we
implement a content rating system, the freedom could be affected
because the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 26 Jun 2019 06:49:41 +0200
Source: warzone2100
Architecture: source
Version: 3.2.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Markus Koschany
Closes: 930942
Changes:
warzone2100
78 matches
Mail list logo
