Re: Bug#1014908: ITP: gender-guesser -- Guess the gender from first name

[Jonathan Carter (highvoltage)]

On 2022/07/14 14:52, Steve McIntyre wrote:

IMHO there are 2 points to an ITP:

  * to save effort in case two people might be working on the same
package
  * to invite discussion on debian-devel / elsewhere

If people post an ITP and upload iummediately, then I don't think that
helps on either count.


I believe an ITP is even helpful in that case. It's happened on many 
packages before that the package had an issue and not accepted by FTP 
team, and then eventually the ITP got renamed to an RFP. Also, if I want 
to package something, I (and tools like reportbug) check whether there 
are ITPs/RFPs filed. I /don't/ check whether the package is in NEW.


So, in short, I think that filing ITPs is still a good practice and the 
times where it should be left out are really some edge / special cases.


-Jonathan

[Artwork] Survey for the default artwork for Bullseye (Debian 11)

[Jonathan Carter (highvoltage)]

Hello Debianites o/

Freeze is coming, and it's that time of the development cycle to choose
the desktop artwork to be used in the next Debian release.

All the fine submissions can be perused at:

https://wiki.debian.org/DebianDesktop/Artwork/Bullseye

Thank you to everyone who have put work into these so far!

To vote for your favourite theme, visit the following website and click
on the "Bullseye Artwork Survey" button. From there, you can rank your
choices from the available options to the My Choices section from most
preferred to least preferred.

https://surveys.debian.net/

The survey is now open and closes on 2020-11-10 23:59 UTC.

Please be nice and vote only once. If you require assistance, you can
find the desktop team on #debian-desktop on the oftc IRC network.

-Jonathan


pgpE6DZ33FBoX.pgp
Description: OpenPGP digital signature

[Artwork] Survey for the default artwork for Bullseye (Debian 11)

[Jonathan Carter (highvoltage)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Debianites o/

Freeze is coming, and it's that time of the development cycle to choose
the desktop artwork to be used in the next Debian release.

All the fine submissions can be perused at:

https://wiki.debian.org/DebianDesktop/Artwork/Bullseye

Thank you to everyone who have put work into these so far!

To vote for your favourite theme, visit the following website and click
on the "Bullseye Artwork Survey" button. From there, you can rank your
choices from the available options to the My Choices section from most
preferred to least preferred.

https://surveys.debian.net/

The survey is now open and closes on 2020-11-10 23:59 UTC.

Please be nice and vote only once. If you require assistance, you can
find the desktop team on #debian-desktop on the oftc IRC network.

- -Jonathan
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAl+W2fQACgkQsB0acqyN
yaH+ug/+JESJqpU7xW7XYL3F2bGyvsRfOVO2SYkp8klyEW4tXYAJltYoF/ab9FS5
5VI9VK0vIYovW3gC1lVXk0+K5WCFxu79BkMj48iIWJ16ODoPi3P0AYupDj+a1Jsq
wfFpvZ+B2mJtFxpXlINrPLFJeGihKvk6NzYJrw4n/EPEjIlQpS2gEyn63f1w86tW
xF8Re1GUmp5+0U52P4hakK3axVl3P+gli8e31LKQS3CS7T942qriR5LxmnhD1XEt
IALxlEu4Vld5c138NUILRD2HXetn5KMSGCucbUuRA7jj4Axl8zQOCPm/GQSFN0DG
IIcgoRcpOzldMgsoAW2/mx+OGCF47G6g0cZ5ZXjGLlsvFOzEEBwY6LJcdFzMQY1i
e5/6K3prwAjlpUKBp0gRyYKWo51F2mvxqt49mrYEVQG4QlENoFg9VzQBZcxIp1xN
2PLI5kJWp/XPrs09x+MsgXlUfMZevIZL7Of1XcLUZwz1xX0fRbDw9+l0HG3jUKPC
8oWt3+/dbLFO4eI1iR+XC07Q2MOJUEI1Xr03WhW3joaieH4OHbSKYCydjYA4j7y6
aL/mWfQm0rxg8xP/dLpwqKNj7WLplqe+I3SUWaI0r2gPQUgmtGiWqQs5MUA83e48
8ROjlq3Td+xIeVzfFRMbXKPQJWiRyoYPB2LsWLQzw49Y0/gmGcM=
=xo7v
-END PGP SIGNATURE-

Re: Urging for solution to the slow NEW queue process

[Jonathan Carter (highvoltage)]

On 2018-04-11 16:04, Andreas Tille wrote:

On Wed, Apr 11, 2018 at 07:08:21AM +, Lumin wrote:
Briefly speaking, if a DD was told that "Thank you for your 
contribution

to Debian but please wait for at least 2 months so that your package
can enter the archive.", will the DD still be motivated working on NEW
packages??? Please convince me if you think that doesn't matter.


The fact that the NEW queue is continuely growing is a sign that DDs 
are

continuosely motivated to fill it up. ;-)  As Mattia said in his
response patience is a feature you learn as DD and it is not a bad
feature.


When I sponsor packages on mentors.debian.net, I often try to 
emotionally prepare the uploaders for an extended wait. The last few 
times I did, their packages were accepted in unstable within 24 hours, 
that's really fantastic!



I'm only a DM and I tried to apply for FTP assistant but got
nothing in reply from ftp-master. Now what I can do is just
repeating this topic again and urge for a solution.


I have not seen any applause in this thread for your offer to help.  I
hereby do this and thank you explicitly.  I have learned that e-mails 
to

ftp-master work way worse than IRC via #debian-ftp.  May be you repeat
your offer there.

I personally admit that getting no response to e-mails is more draining
on the patience than waiting for getting a package acceptet.  Thus
knowing this alternative channel helped me a lot.


I had a similar experience. It didn't help that the one ftp-master 
member made a comment about laughing off requests to join the ftp team. 
If they didn't want my help I'd rather get a "sorry, we don't think 
you're experienced enough yet" rather than just nothing.


-Jonathan

--
  ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
  ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
  ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
  ⠈⠳⣄  xmpp:j...@debian.org ring:highvoltage

Re: A few questions about building Debian-Based Distro

[Jonathan Carter (highvoltage)]

On 20/02/2018 08:05, Jonathan Carter (highvoltage) wrote:
> https://wiki.debian.org/Derivatives/Guidelines may be of help, as would
> the other pages on https://wiki.debian.org/Derivatives

PS: As Pabs pointed out to me on IRC, the debian-blends list might be
more appropriate for blends (more about that on
https://wiki.debian.org/DebianPureBlends)

-Jonathan

Re: A few questions about building Debian-Based Distro

[Jonathan Carter (highvoltage)]

On 19/02/2018 19:25, Project Echo wrote:
> Hey Debian Developers!

Hi! This list is for the development of Debian, please rather use a more
appropriate list, like debian-derivatives for questions regarding
derivatives, custom spins, pure blends, etc.

> I have a few questions about making a Debian-Based Distro
> 
> 1.Do you make a ISO of Debian without anything installed?, Just the base
> Operating System, I need this as I want to make my Debian-Based Distro
> 
> 2.While Rebranding Debian, What are the files I have to re brand?. Also
> will I fall under any issues if I distribute it for free? (Of course I
> will be crediting Debian and it's creators)
> 
> 3.If I did rebrand Debian, Will the Operating system have errors
> installing .Deb files?

https://wiki.debian.org/Derivatives/Guidelines may be of help, as would
the other pages on https://wiki.debian.org/Derivatives

Good luck!

-Jonathan

-- 
  ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
  ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
  ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
  ⠈⠳⣄  Be Bold. Be brave. Debian has got your back.

Re: What can Debian do to provide complex applications to its users?

[Jonathan Carter (highvoltage)]

Hi Raphael

On 16/02/2018 17:11, Raphael Hertzog wrote:
> Dolibarr is not alone:
> 
> - while gitlab is packaged in Debian, its packaging took years and the
>   result is brittle because it can break in many ways whenever one the 
>   dozens of dependencies gets updated to some new upstream version
>   (BTW salsa.debian.org does not use the official package)
> 
> - I have the Debian packaging of distro-tracker (the code behind
>   tracker.debian.org) available in the git repository for years
>   but I never released it into Debian because it embeds a few javascript
>   libraries (bootstrap, jquery) and I don't want to validate that
>   it does work with the versions currently in Debian
> 
> I'm sure we are missing lots of good applications due to our requirements.
> What can we do to avoid this?

How can we avoid upstream not making source available for their
binaries? Because this is fundamentally the issue with shipping only
minified javascript without any sources or reference of where it comes
from. This also isn't a problem in Debian, it's a broken JavaScript
ecosystem that's driven by very poor software developers who tend to
want to smack together anything that will work for a little while so
that they can get paid for their work and move on to the next bad project.

> I don't have any definite answers although there are ideas to explore:
> 
> - we could relax our requirements and have a way to document the
>   limitations of those packages (wrt our usual policies)

Which requirements are you referring to? If it's relaxing the need for
source for minified javascript, then no thanks.

> - we could ship those applications not as .deb but as container
>   and let them have their own lifecycle

What would this solve and how will it solve it?

> What do you think? Do you have other ideas? Are there other persons
> who are annoyed by the current situation?

As someone who intends to package software that contains some embedded
low-quality JavaScript code, yes, certainly frustrated. But with the
JavaScript community and their underdeveloped ideas of how software
works, not with Debian.

-Jonathan

-- 
  ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
  ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
  ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
  ⠈⠳⣄  Be Bold. Be brave. Debian has got your back.

Re: Accepted fonts-noto-color-emoji 0~20170913-2 (source) into unstable

[Jonathan Carter (highvoltage)]

On 28/11/2017 18:31, Jonathan Carter (highvoltage) wrote:
> Ooh, very nice, thanks!

(sorry I wasn't paying attention and thought I was sending that to
Jeremy directly)

-Jonathan

Re: Accepted fonts-noto-color-emoji 0~20170913-2 (source) into unstable

[Jonathan Carter (highvoltage)]

Ooh, very nice, thanks!

On 28/11/2017 02:33, Jeremy Bicha wrote:
> Format: 1.8
> Date: Mon, 27 Nov 2017 18:57:13 -0500
> Source: fonts-noto-color-emoji
> Binary: fonts-noto-color-emoji
> Architecture: source
> Version: 0~20170913-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Fonts Task Force 
> Changed-By: Jeremy Bicha 
> Description:
>  fonts-noto-color-emoji - color emoji font from Google
> Changes:
>  fonts-noto-color-emoji (0~20170913-2) unstable; urgency=medium
>  .
>* Install font to correct subdirectory
> Checksums-Sha1:
>  68c6754f277a7a5f24ca90bea7ba443bbcf51981  
> fonts-noto-color-emoji_0~20170913-2.dsc
>  51e674ddd9e6ab2be5ad617c62c095f020d4c479 3860 
> fonts-noto-color-emoji_0~20170913-2.debian.tar.xz
>  23014e1f2b1493edecbc5bc6aae0fceb018fafb0 13958 
> fonts-noto-color-emoji_0~20170913-2_source.buildinfo
> Checksums-Sha256:
>  5652a2232515aef8e33e198e713235df5189d2ee5c2875ef3e55318c40950c67  
> fonts-noto-color-emoji_0~20170913-2.dsc
>  0eb57c144126ee5fd59ad89606b39481a04144e6eb98bc440961a56fe9c24f36 3860 
> fonts-noto-color-emoji_0~20170913-2.debian.tar.xz
>  a2860febfb70644bc9f1feeabcf57561a46b839bfd30ac742d5a00a364a8c690 13958 
> fonts-noto-color-emoji_0~20170913-2_source.buildinfo
> Files:
>  65e57014fd623445e1c62c8aa771  fonts optional 
> fonts-noto-color-emoji_0~20170913-2.dsc
>  417dbed6e99a3089ea08689ccbafab6d 3860 fonts optional 
> fonts-noto-color-emoji_0~20170913-2.debian.tar.xz
>  7a227ce3cb918a0853a43773f14d7f6b 13958 fonts optional 
> fonts-noto-color-emoji_0~20170913-2_source.buildinfo
> 
> 

Re: How to start a new packaging team now?

[Jonathan Carter (highvoltage)]

Hey Jeremy

On 15/09/2017 18:39, Jeremy Bicha wrote:
> I have been thinking for a while of starting a new packaging team for
> desktop themes (especially GTK+ and GNOME themes since so many
> desktops can use them).

Great! I've also thinking about started a team for all the gnome-shell
extensions we have in Debian. The Debian Qt/KDE team has a complementary
Debian KDE Extras team (see https://pkg-kde.alioth.debian.org/ for more
information), I wonder if it might be worth while considering having a
GNOME Extras team for all the GNOME related stuff that isn't part of
upstream GNOME?

> Now that Alioth is beginning to close down and its replacement is not
> yet ready, how would I start this team now?

Well, it's not official yet of course but salsa.debian.org is running
GitLab and it seems like the likely Alioth replacement. I think it would
be less disruptive to use a project on gitlab.org and get used to its
tools, which should make it easier to move the project onto Debian
infrastructure than from Launchpad.net. Although, Launchpad.net would be
preferable to Github, at least Launchpad.net is now free software.

-Jonathan

Re: Call for volunteers: FTP Team

[Jonathan Carter (highvoltage)]

On 17/08/2017 20:11, Joerg Jaspert wrote:
> it has been quite a while since the last call for volunteers, so here is
> an update: Yeah, we still need people, and we want you. Well, that is,
> if you are a Debian Developer, for this. If you are not and want to
> help, read the last paragraph please.

If someone hypothetically joins, are they allowed to rename the FTP team
to something that doesn't include "FTP"?

-Jonathan

Re: What's a safe way to have extensions in chromium in Debian?

[Jonathan Carter (highvoltage)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey Enrico

On 22/03/2017 13:03, Enrico Zini wrote:
> Now, suppose I need an extension, what is the proper way to have it in
> Debian, so that it gets upgraded when needed? With that proper way, wh
at
> amount of phoning home is going to happen?

Seems like it's at least possible to install system-wide plugins:

https://developer.chrome.com/extensions/external_extensions#preferences

Those instuctions cover chrome but seems easily adaptable to chromium.

The problem with any ad blocker is that it needs up to date block lists
and related data which is usually stored upstream and opens up a door
for phoning back home.

I'm taking a look at https://github.com/gorhill/uBlock since it's gpl-3
and has proper releases (I would expect that a lot of chromium
extensions are a licensing nightmare).

You mention that this is going to be a huge deal for stretch users, and
I agree with you, but we're deep into freeze so these won't be able to
go into stretch, so what's going to be the best way to make these
available to Debian stable users?

- -Jonathan
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAljSv24ACgkQsB0acqyN
yaEu2w/9EO/iZiQMDvULU+hyegJqfDM359Kwp0S0IGyXcrMlBRguTtqqM6henWmL
h3zt64cPfASCViYlOnYWiWiNh1OCMur1dDACi1qfE+ZPDFSF47IvrG2IKjt3UE5Z
2GvC6ig5GO6Pbt/jL9GSAUMFEoE8qicSmfb6CyHwtduw/fqA5LvEx0z3ME70cVVX
AFiCxonWg4pXjw0hVmiLsf6ZessZ6b/ObBnzRQosMg6nJFtFnosHKB1bQkMIRUdS
gyu2HWxoAiXJCG0Yb8xXYrs7M90UlYw33M1OlAvUMmUHKHt5mZQZpCJjSjLziOo9
VQzvLgVoHpJcG9GiD7JKOUcyMbSY1gSoY/Xzuevxtai+Uct8JU2FKrCXGjIxGJu0
5sCBFjntTIMR4ciKBPCUtMT8VNiBWvqRNHylQsVo+Hidlj5jg/QWR7D+ummt3kTC
Ckmjf/t/oXXZmthhO+rPXgCfdAQtItNepF3oImIyIBB61pMKAQQ+C58bvBsugqXP
I5jIE1VB7f+dOqyg5s7zbxycZNI0iU/HWJmHeMNF+dhGhd6TYXuUGLt2fVK/F9eI
PndhA2TKT7hkmKLEYNkrFImIME6DxGOISfXm+HM+AM1D47ClLuIm/fXIWmAnQLXL
KJdShEIzwnmRMw/9DHQ+XD854rW4xY0e9+vbum1BJG+vJtYSoZI=
=SqvO
-END PGP SIGNATURE-

ITP: gnome-shell-extension-move-clock -- move clock extension for GNOME shell

[Jonathan Carter (highvoltage)]

Package: wnpp
Severity: wishlist
Owner: Jonathan Carter 

* Package name: gnome-shell-extension-move-clock
  Version : 1.0.0
  Upstream Author : 2011-2013 Ron Yorston 
2016 Jonathan Carter 
* URL :
https://git.bluemosh.com/highvoltage/gnome-shell-extension-move-clock
* License : GPL-2+
  Programming Lang: JavaScript
  Description : move clock extension for GNOME shell

This extension will, when enabled, move the clock on your GNOME shell panel
from the middel to the right.
.
GNOME is an intuitive and attractive desktop. This is an add-on to
GNOME, and will likely not be useful on its own.

Re: Debian default desktop environment

[Jonathan Carter (highvoltage)]

On 08/04/2014 20:35, Paul Tagliamonte wrote:
 Remember all the hype that arose when Beryl was announced, with
 per-window transparency settings, the rotating cube, wobbly windows,
 and all that. It was flashy, and I do think it made some heads turn to
 Linux, previously perceived as plainly fugly.

 Beryl and its ideas came and went. Yes, some ideas stuck and became
 useful. But I'm very glad that did not become the standard for desktop
 interaction.
 
 It was the standard -- for a while -- and for that while it was the
 golden years of the Linux desktop (in my mind)
 
 We had features no one else did, people were pushing the bounds of what
 we thought were posible and having a great time doing it. Yeah, a lot of
 it was silly, but a lot of really good stuff came out of it that I can't
 get these days.
 
 After the KDE4 and GNOME3 rewrites (which are hugely important and vital
 to our success) I don't mind Compiz died, but for a *long* time this was
 the standard, and it was the most advanced window manager.
 
 Someone remind me; is Unity still a Compiz plugin, or did that die too?

Unity 7 (as used up until Ubuntu 14.04) still uses Compiz, Unity 8 uses
Qt's compositing for all its fanciness.

-Jonathan


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53444843.9080...@ubuntu.com

Re: Tired of my fellow SysV supporters

[Jonathan Carter (highvoltage)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/02/2014 22:45, Dominik George wrote:
 I do not know how many of them are trolls, but the content I had to read
 on this mailing list in the last days is clearly intolerable.
 
 systemd, be it as one init system or as the only init system, will not
 make me leave Debian, but what I had to learn about parts of the
 community could easily do so.
 
 Please, whoever cares about that, do not hesitate to remove those people
 from the project!

*hugs* and +1

Perhaps the list admins can block the topic and create a new list for
people who want to re-hash the same old details over and over and over
again until they get old, fat and bald and wonder what they've done with
their lives.

- -Jonathan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBAgAGBQJS+pBgAAoJELAdGnKsjcmh2LMP/3cPe8z/Vs6Yr05Tfii/AoZ8
sSB1qKcA4ItZTeoRDfjWyG6DNvfrYu4oDHHpUh/1ofUS4lEdGLGImfMz5SSzuh23
yjMaleCS/uH3Y/nzvpWb0HBkzLmyqHy/jp92ZBVcPRLKOJ0k8fpmHE7inK+vBc1t
jCYZ1DHb5eAYm5HJKHpa+4N236UbNNMWfGvWdRO9ZjnYI/IBF90VJRQuOIwYbYWD
MNCaTKbHHMxieR9DZzcW92ZJU4cCC/GBmrNyQ9iYxIRDP4nk/N9ITShSGER9z8SE
jivw/3N7/oaKk0Re+bszIDH2cLBOwJiVtfpzF2XwCcGFnNttFMtvDfZPrtPxo4+5
1fq7OgfT8xCkjVTjO6+HWMWEiiP4nvLewpk6kcajW0An8rLSsZABSDecYcIHqvGS
m2nH31acE3hijkXfCOmCAKGo5f6Tesm66hebZ3zx/XhtAIiu/Yd4llM/Y8X1mCDh
nva7hq6jluBnHFD66rgQwByZBk2qJ0wm54ulSzmP9Ay1L4oGxpBZYYtxCM4AHtQi
5fHSbdONt/jyvA6jr46gmqvWdnbDHVZphDx1GJNzE6TxRkT1Tq4bDvltLoi2cusK
yrKYSjLPUcPhUgyhNWzJAx4LQF9NoZs4c59JWuTSGH+NDzNMEF37O2jbQ9ipa5pF
+zJlguDW8jgM14R/pD77
=3QFb
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52fa9063.8080...@ubuntu.com

Re: Bug#727708: Fsck SystemD and its developers and its users. GR to override this please.

[Jonathan Carter (highvoltage)]

Hi John

On 10/02/2014 20:41, John Paul Adrian Glaubitz wrote:
 On 02/10/2014 06:47 PM, Clint Byrum wrote:
 Neglecting reliability and maintainability for the sake of being
 able to choose such a core component is a bad idea. I do not
 think it's really feasible to maintain several init systems, it
 just affects too many components of the system.
 
 We don't even manage to maintain two versions of ffmpeg (the original
 and the fork) even though many users actually prefer the original. How
 should this even work with the init system then?

I recommend reading all the previous discussions on the topic. Over the
last year, it's become clear that in the short-term at least, a very
minimum of 2 different init systems would need to be supported. At least
sysvinit, because there are so many packages that ship with
configuration and it won't be possible to convert them all in one
release, and also because the alternative operating systems that Debian
ship with won't work with Upstart or systemd.

sysvinit has hit its limit with it's dependency-based nature, and the
only way to fix many outstanding bugs is by switching to an event-based
system.

So, supporting at least 2 init systems in the short-term will be
necessary. Upstart is pretty cheap to support, since it's Ubuntu's
default init system and a very large amount of packages have Upstart
scripts already. systemd has a very enthusiastic community and it's
likely that many packages will have systemd configuration files by the
time Jessie is released.

There are so many possibilities going forward. It's possible that
Canonical might give up on Upstart since the rest of the world has
pretty much gone with systemd on Linux. Or, it's possible that Upstart
would better support the niche systems / toy ports which would make it a
good candidate for replacing sysvinit on those systems. Or perhaps in
hindsight it might just turn out that Upstart was a better, more
logical, sane, level-headed, secure, unixy and unpoetered solution and
the technical committee will ask themselves what were we thinking!?.

Historically though, it seems like it has consistently been beneficial
for Debian to support all the available options and let things evolve.
Maybe it's just better accepting the choice and move on even if you
don't like the choice.

When I saw the announcement this morning I thought Oh well, at least we
can have debian-devel back now. I think if anything has been said
before it doesn't have to be re-hashed to infinity. This is one of those
things that you just have to learn to let it slide a bit.

-Jonathan


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52f9282e.3090...@ubuntu.com

Re: Valve games for Debian Developers

[Jonathan Carter (highvoltage)]

On 23/01/2014 05:03, Wouter Verhelst wrote:

On Thu, Jan 23, 2014 at 01:00:10AM +0100, Michael Banck wrote:

On Thu, Jan 23, 2014 at 03:26:26AM +0330, ?? ?? wrote:

Hey, this looks more like an anti-Valve trap for DDs aimed to slow down
development of Debian as base of Steam OS by steering their time spending
from developing Debian to playing Valve games. ... OK, I was joking, or at
least _mostly_ joking. ;-)


We made this mistake with frozen-bubble once, I am sure everybody has
learnt from history...


You're forgetting tetrinet.


+1 for tetrinet. If Debian decisions should be based on the outcome of 
games, it should really be a free software game ;)


-Jonathan


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52e0b88b.60...@ubuntu.com

Re: Linux 3.2 in wheezy

[Jonathan Carter (highvoltage)]

Hi Russell

On 02/02/2012 03:21, Russell Coker wrote:

However, a low profile container/virtualization solution is needed, and I
know there is quite some demand for it: both some larger scale
organisations and several smaller/non-profit organisations I am acquainted
with use either OpenVZ or linux-vserver and some of them will be in
trouble if there is no equivalent and not at least a rough migration path.


Are there many users who need root containment but who won't have the
resources to run Xen or KVM when the support for Squeeze ends?


Just to give you a use case, the company I work for has a bunch of 
clients where we run more than 400 VZ's per server. Those servers are 
already packed with RAM and are using most of it and even swapping. 
Switching to KVM/Xen would probably kill those machines :)


We're really dependent on contextualization so we considered the following:
 * LXC
 * Using VZ on CentOS
 * Getting the 2.6.32 VZ kernel from the openvz project and check if 
that works with our current user space


LXC kind of works but has it's issues. We really want to move to it.

I'm personally strongly against CentOS (they had months without security 
updates last year, I find the quality of rpm packaging poor compared to 
those found in Debian) and I don't think it's a good idea to have yet 
another system to support.


We tried the 2.6.32 VZ kernel on squeeze / wheezy / lucid / precise - 
and it works. We have a PPA[1] for our experimental packages too. We 
might run into bugs with some userspace things needing a newer kernel, 
but we haven't found anything yet. The big downside is also that we rely 
on the VZ project to release security updates and we have to be vigilant 
to update regularly.


All the work that the above is causing (and to an extent the risk) makes 
me quite eager to move to LXC. If distributions like Debian and Ubuntu 
could continue supporting it it would be a different story, but it 
sounds like OpenVZ is a borderline hostile upstream who isn't interested 
in working with anyone, and that makes me want to move away even more.


-Jonathan

[1] https://launchpad.net/~revolution-linux/+archive/openvz


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f2a3b74.1030...@ubuntu.com

Re: Launch of Debian 6.0

[Jonathan Carter (highvoltage)]

Hi

On 10-11-21 07:52 AM, Martin Lisicki wrote:
 wann wird Squeeze stable werden? Wann kann man ungefähr damit rechnen?

wenn es fertig ist.

 when is Squeeze going to be stable? When can I expect this?

when it's ready.

See also: http://bugs.debian.org/release-critical/

-Jonathan


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ce93d4c.1050...@ubuntu.com

Re: Thank you, Debian project, for working to make a free software operating system (was: Is tabular data in binary format acceptable for Debian ?)

[Jonathan Carter (highvoltage)]

On Fri, Jan 22, 2010 at 1:11 AM, Ben Finney ben+deb...@benfinney.id.au wrote:
 I've often expressly, and in public, thanked the specific people who put
 forth efforts to ensure free software in the Debian operating system. I
 encourage anyone else to do this too; it's a good way to increase the
 likelihood such work continues to be done.

 If you need it, consider this message yet another message of thanks for
 the work everyone does to make a free-software operating system, often
 in the face of indifference or hostility from upstream developers
 regarding the practice of free software.

+1

Debian FTW!

-Jonathan


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

Re: Copyright infringement on www.rossbea zley.co.uk — Overreacting?

[Jonathan Carter (highvoltage)]

Gunnar Wolf wrote:
 Now... I am surprised this is seen so harshly. This is not the first
 site I see that syndicates Planet Debian. What I can understand is

There's a big difference between aggregating posts and claiming that
their yours. The heading of the site says that the site is the blog, and
the posts link back to entries on the site (not the original author
sites). It gives the (wrong) impression that the entries were
specifically written for the site. If you scroll down all the way there
are Google ads at the bottom. He's clearly abusing the planet's content
for his own gain.

-Jonathan


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