Re: Content Rating System in Debian

Bagas Sanjaya writes: > Regarding freedom, yes it can be affected by CRS because CRS can limit > freedom to use programs for some users > (particularly non-adults). But CRS limit such freedom in order to protect > psychology users for long term from negative > impacts of programs they used.

Re: Content Rating System in Debian

Dear Bagas, On 26.06.19 04:50, Bagas Sanjaya wrote: > 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 rat

Re: Content Rating System in Debian

On 25/06/19 20.19, Matthias Klumpp wrote: 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 f

Re: getting rid of "testing"

Adam Borowski writes: > 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

Re: getting rid of "testing"

Michael Stone writes: > 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 poi

Re: getting rid of "testing"

Hi, On Wed, Jun 26, 2019 at 03:10:27PM +0200, Philip Hands wrote: > The version numbers are also showing up on login and desktop backgrounds > so I'd guess the bulk of users know exactly which number they're up to, > but a pretty vague about which codename goes with that. > > Oh, and for me that

Re: getting rid of "testing"

Andreas Tille writes ("Re: getting rid of "testing""): > I never really understood why we need these codenames. Simon McVittie wrote: | Back when the release team decided on a per-release basis whether | this was a "major" or "minor" release, we had the excuse that we had | to use a codename for

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

Where do I find kFreeBSD-amd64 isos, from testing or unstable? Em sex, 12 de abr de 2019 17:49, Joerg Jaspert escreveu: > Hi > > back in August 2018 we discussed architecture inclusion into > unstable/experimental. > > Today we had our regular FTPMaster meeting and discussed hurd and both > kfre

Re: Content Rating System in Debian

Am Mi., 26. Juni 2019 um 10:40 Uhr schrieb Bagas Sanjaya : > > On 25/06/19 20.19, Matthias Klumpp wrote: > > [...] > > So APT need to do what you mention, that is determining age rating not > only based on AppStream metadata, but also on system locale? Yes. Since the things that determine age rati

Re: Content Rating System in Debian

ГI'd say that we should never be touching anything like this. вт, 25 июн. 2019 г., 7:57 Bagas Sanjaya : > In order to inform to users, especially parents, about potentially > objectionable content in Debian packages, Content > Rating System (CRS) can be deployed to Debian. With CRS, users can ch

Re: getting rid of "testing"

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. >

Re: getting rid of "testing"

On Wed, Jun 26, 2019 at 09:01:03AM +0800, Paul Wise wrote: I also should mention that I use all of stable stable-updates proposed-updates and the equivalents for old/oldold. I have them in the apt sources of a chdist so I can easily look up old versions, do apt-file searches on old versions, look

Re: getting rid of "testing"

On Wed, Jun 26, 2019 at 04:13:00PM +0100, Ian Jackson wrote: Andreas Tille writes ("Re: getting rid of "testing""): I never really understood why we need these codenames. Simon McVittie wrote: | Back when the release team decided on a per-release basis whether | this was a "major" or "minor" r

Re: getting rid of "testing"

On Wed, Jun 26, 2019 at 01:29:44PM -0300, Antonio Terceiro wrote: As a data point, having "stable" and "testing" stay around is very useful for CI purposes. For example on ci.debian.net all our setup uses "stable" and "testing" instead of the release codenames, and it's useful to have a system th

Re: getting rid of "testing"

On Wed, Jun 26, 2019 at 03:10:27PM +0200, Philip Hands wrote: I'm perfectly capable of typing slink when I meant stretch. The coming era of b* releases is going to be a right pain for me. FWIW, I still confuse bo and buzz. :)

Re: getting rid of "testing"

Only a last thought: Didn't we have really important problems to solve? It might be only me, but i see the discussion as a minor variation of bike shedding. To sum it up: Some people like codenames, some not, same for numbers - the real question is: Does it really matters? Over and out Alf

Re: getting rid of "testing"

On Wed, Jun 26, 2019 at 02:23:40PM -0500, Andrej Shadura wrote: On Wed, 26 Jun 2019 at 14:13, Michael Stone wrote: On Wed, Jun 26, 2019 at 03:10:27PM +0200, Philip Hands wrote: >I'm perfectly capable of typing slink when I meant stretch. The coming >era of b* releases is going to be a right p

Re: getting rid of "testing"

On 26/06/2019 19:58, Michael Stone wrote: > On Wed, Jun 26, 2019 at 02:23:40PM -0500, Andrej Shadura wrote: >> On Wed, 26 Jun 2019 at 14:13, Michael Stone wrote: >>> >>> On Wed, Jun 26, 2019 at 03:10:27PM +0200, Philip Hands wrote: >>> >I'm perfectly capable of typing slink when I meant stretch. 

Re: getting rid of "testing"

> "Michael" == Michael Stone writes: Michael> On Wed, Jun 26, 2019 at 09:01:03AM +0800, Paul Wise wrote: >> I also should mention that I use all of stable stable-updates >> proposed-updates and the equivalents for old/oldold. I have them >> in the apt sources of a chdist so I

Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On Wed, 2019-06-26 at 12:14 -0300, elementar wrote: > Where do I find kFreeBSD-amd64 isos, from testing or unstable? > > Em sex, 12 de abr de 2019 17:49, Joerg Jaspert > escreveu: > > Hi > > > > back in August 2018 we discussed architecture inclusion into > > unstable/experimental. > > > > Toda

Re: Content Rating System in Debian

чт, 27 июн. 2019 г. в 03:32, Bagas Sanjaya : > > > On 26/06/19 23.09, Dmitry Eremin-Solenikov wrote: > > ГI'd say that we should never be touching anything like this. > > вт, 25 июн. 2019 г., 7:57 Bagas Sanjaya : >> >> In order to inform to users, especially parents, about potentially >> objection

Re: Content Rating System in Debian

On 26/06/19 23.09, Dmitry Eremin-Solenikov wrote: ГI'd say that we should never be touching anything like this. вт, 25 июн. 2019 г., 7:57 Bagas Sanjaya >: In order to inform to users, especially parents, about potentially objectionable content in Debian packa

Re: getting rid of "testing"

On Wed, 2019-06-26 at 14:54 -0400, Michael Stone wrote: > Wouldn't it be nicer to have a reliable and simple source of version > ordering rather than relying on ugly names and symlinks? As a bonus, it > would be useful for a lot more things and for more than n-2 > calculations. That doesn't se

Re: Content Rating System in Debian

On 2019-06-27 07:32:04, Bagas Sanjaya wrote: > > On 26/06/19 23.09, Dmitry Eremin-Solenikov wrote: > > ГI'd say that we should never be touching anything like this. > > вт, 25 июн. 2019 г., 7:57 Bagas Sanjaya : > > In order to inform to users, especially parents, about potential