Domain: debian.org
Stories and comments across the archive that link to debian.org.
Comments · 7,134
-
Does it actually change anything ?
Does it actually change anything ?
The widely recognized ("official") logo was already the open one, while nobody uses the "restricted" logo.
The new trademark policy states: You cannot use Debian trademarks in any way that suggests an affiliation with or endorsement by the Debian project or community, if the same is not true.
But the official logo doesn't imply endorsement, that's what the restricted logo does. Or isn't the logo part of Debian's trademark ?Or is it newspeak for an actual restriction of rights ?
-
Does it actually change anything ?
Does it actually change anything ?
The widely recognized ("official") logo was already the open one, while nobody uses the "restricted" logo.
The new trademark policy states: You cannot use Debian trademarks in any way that suggests an affiliation with or endorsement by the Debian project or community, if the same is not true.
But the official logo doesn't imply endorsement, that's what the restricted logo does. Or isn't the logo part of Debian's trademark ?Or is it newspeak for an actual restriction of rights ?
-
Ruby vs Node.JS
Skillset momentum aside, why would anyone choose Ruby over Node.JS?
Node is *significantly* faster right out of the box (while Ruby JIT is still in its infancy). With so many well-funded implementations (Google, Mozilla, Opera, Microsoft) competing to be a tiny bit faster in any way possible, JavaScript is very likely to remain the fastest dynamically-typed language. Node is also built with a specific emphasis on scalability / parallel performance.
Node.JS also has the advantage of using the same language on the server that you inevitably have to use on the client end of Web-based applications. This avoids the overlap where you end up writing the same thing in different languages, adding complexity to the project. JavaScript / EcmaScript is also the preferred language of browser extensions, many desktop / mobile widget kits, GNOME apps, QtScript, etc. By focusing on one language instead of several (in a finite amount of time), you'd gain more expertise with that one language and be able to accomplish more things with it.
Of course JS syntax leaves much to be desired, but that will be revised some time in the future. CoffeeScript's syntax is even more intuitive and compact that Ruby's!
--libman
-
Re:Quite actual - Not!
Well, have a better look before spreading lies. For kernel, web browser and libreoffice
Kernel:
Stable - 2.6
Testing - 3.2
Unstable - 3.2 (released July, 2012)
Current version - 3.8
Those 3.6/3.7 files seen in your link? Experimental. Yeah you could make it work, but then you aren't running Sid anymore. Not entirely. And if you run too much experimental for too long, something is going to end up horribly broken.Firefox/Iceweasel:
Stable - 3.5
Testing - 10esr
Unstable - 10esr (released March 2012)
Current Version - 19.0Libreoffice:
Stable - 3.5
Testing - 3.5
Unstable - 3.5 (released February 2012)
Current version - 4.0YOU DO have very recent packages available, even right now, during the freeze of testing. I haven't checked DE and X, since I don't know what you run (eg: which graphic card, and which environment you like).
I run XFCE on testing, not that it matters.
XFCE:
Stable - 4.6
Testing - 4.8
Unstable - 4.8 (released Jan 2011)
Current Version - 4.10 (released April 2012)Like I said, Sid isn't bleeding edge. Of the packages here, the newest in Sid is the kernel: 7 months old.
It's also worth noting that drivers receive unblock from the release team so that they can enter stable.
Well that's great (and I genuinely mean that), but a bleeding-edge enthusiast would only see that 3.2 != 3.8.
-
Re:Quite actual - Not!
Well, have a better look before spreading lies. For kernel, web browser and libreoffice
Kernel:
Stable - 2.6
Testing - 3.2
Unstable - 3.2 (released July, 2012)
Current version - 3.8
Those 3.6/3.7 files seen in your link? Experimental. Yeah you could make it work, but then you aren't running Sid anymore. Not entirely. And if you run too much experimental for too long, something is going to end up horribly broken.Firefox/Iceweasel:
Stable - 3.5
Testing - 10esr
Unstable - 10esr (released March 2012)
Current Version - 19.0Libreoffice:
Stable - 3.5
Testing - 3.5
Unstable - 3.5 (released February 2012)
Current version - 4.0YOU DO have very recent packages available, even right now, during the freeze of testing. I haven't checked DE and X, since I don't know what you run (eg: which graphic card, and which environment you like).
I run XFCE on testing, not that it matters.
XFCE:
Stable - 4.6
Testing - 4.8
Unstable - 4.8 (released Jan 2011)
Current Version - 4.10 (released April 2012)Like I said, Sid isn't bleeding edge. Of the packages here, the newest in Sid is the kernel: 7 months old.
It's also worth noting that drivers receive unblock from the release team so that they can enter stable.
Well that's great (and I genuinely mean that), but a bleeding-edge enthusiast would only see that 3.2 != 3.8.
-
Re:Quite actual - Not!
Well, have a better look before spreading lies. For kernel, web browser and libreoffice
Kernel:
Stable - 2.6
Testing - 3.2
Unstable - 3.2 (released July, 2012)
Current version - 3.8
Those 3.6/3.7 files seen in your link? Experimental. Yeah you could make it work, but then you aren't running Sid anymore. Not entirely. And if you run too much experimental for too long, something is going to end up horribly broken.Firefox/Iceweasel:
Stable - 3.5
Testing - 10esr
Unstable - 10esr (released March 2012)
Current Version - 19.0Libreoffice:
Stable - 3.5
Testing - 3.5
Unstable - 3.5 (released February 2012)
Current version - 4.0YOU DO have very recent packages available, even right now, during the freeze of testing. I haven't checked DE and X, since I don't know what you run (eg: which graphic card, and which environment you like).
I run XFCE on testing, not that it matters.
XFCE:
Stable - 4.6
Testing - 4.8
Unstable - 4.8 (released Jan 2011)
Current Version - 4.10 (released April 2012)Like I said, Sid isn't bleeding edge. Of the packages here, the newest in Sid is the kernel: 7 months old.
It's also worth noting that drivers receive unblock from the release team so that they can enter stable.
Well that's great (and I genuinely mean that), but a bleeding-edge enthusiast would only see that 3.2 != 3.8.
-
Re:Quite actual - Not!
Well, have a better look before spreading lies. For kernel, web browser and libreoffice
Kernel:
Stable - 2.6
Testing - 3.2
Unstable - 3.2 (released July, 2012)
Current version - 3.8
Those 3.6/3.7 files seen in your link? Experimental. Yeah you could make it work, but then you aren't running Sid anymore. Not entirely. And if you run too much experimental for too long, something is going to end up horribly broken.Firefox/Iceweasel:
Stable - 3.5
Testing - 10esr
Unstable - 10esr (released March 2012)
Current Version - 19.0Libreoffice:
Stable - 3.5
Testing - 3.5
Unstable - 3.5 (released February 2012)
Current version - 4.0YOU DO have very recent packages available, even right now, during the freeze of testing. I haven't checked DE and X, since I don't know what you run (eg: which graphic card, and which environment you like).
I run XFCE on testing, not that it matters.
XFCE:
Stable - 4.6
Testing - 4.8
Unstable - 4.8 (released Jan 2011)
Current Version - 4.10 (released April 2012)Like I said, Sid isn't bleeding edge. Of the packages here, the newest in Sid is the kernel: 7 months old.
It's also worth noting that drivers receive unblock from the release team so that they can enter stable.
Well that's great (and I genuinely mean that), but a bleeding-edge enthusiast would only see that 3.2 != 3.8.
-
Re:Quite actual - Not!
Well, have a better look before spreading lies. For kernel, web browser and libreoffice
Kernel:
Stable - 2.6
Testing - 3.2
Unstable - 3.2 (released July, 2012)
Current version - 3.8
Those 3.6/3.7 files seen in your link? Experimental. Yeah you could make it work, but then you aren't running Sid anymore. Not entirely. And if you run too much experimental for too long, something is going to end up horribly broken.Firefox/Iceweasel:
Stable - 3.5
Testing - 10esr
Unstable - 10esr (released March 2012)
Current Version - 19.0Libreoffice:
Stable - 3.5
Testing - 3.5
Unstable - 3.5 (released February 2012)
Current version - 4.0YOU DO have very recent packages available, even right now, during the freeze of testing. I haven't checked DE and X, since I don't know what you run (eg: which graphic card, and which environment you like).
I run XFCE on testing, not that it matters.
XFCE:
Stable - 4.6
Testing - 4.8
Unstable - 4.8 (released Jan 2011)
Current Version - 4.10 (released April 2012)Like I said, Sid isn't bleeding edge. Of the packages here, the newest in Sid is the kernel: 7 months old.
It's also worth noting that drivers receive unblock from the release team so that they can enter stable.
Well that's great (and I genuinely mean that), but a bleeding-edge enthusiast would only see that 3.2 != 3.8.
-
Re:Quite actual - Not!
Well, have a better look before spreading lies. For kernel, web browser and libreoffice, YOU DO have very recent packages available, even right now, during the freeze of testing. I haven't checked DE and X, since I don't know what you run (eg: which graphic card, and which environment you like). But I know that the latest Nouveau driver went in for Wheezy. It's also worth noting that drivers receive unblock from the release team so that they can enter stable.
Please stop repeating the bul**hit that everyone tells without taking the time to check. -
Re:Quite actual - Not!
Well, have a better look before spreading lies. For kernel, web browser and libreoffice, YOU DO have very recent packages available, even right now, during the freeze of testing. I haven't checked DE and X, since I don't know what you run (eg: which graphic card, and which environment you like). But I know that the latest Nouveau driver went in for Wheezy. It's also worth noting that drivers receive unblock from the release team so that they can enter stable.
Please stop repeating the bul**hit that everyone tells without taking the time to check. -
Wheezy / Toy Story reference
No need to assume anything here. It's explained nicely in this FAQ: The Debian GNU/Linux FAQ - section 6.2
-
219 to go
And counting. Wake me up when http://bugs.debian.org/release-critical/ hits under 20.
-
Re:Copyfree alternatives
That benchmark uses non-JIT implementations of all dynamic languages except JavaScript V8. LuaJIT is much faster than regular Lua, and I've been told that it's even faster than V8. So, thanks to Lua and JS, the performance argument for using Scheme as a scripting language is no longer valid.
Also note that Racket is almost 2x as verbose (and Lisp 3x as verbose) as other scripting languages! That, combined with its relative obscurity and the fact that many (most?) programmers don't have any experience with functional languages, makes it an extremely poor choice for an embedded scripting language.
--libman
-
Copyfree alternatives
Copyleft-only languages have no chance, particularly among languages intended to be embedded in applications. Permissively licensed alternatives to Guile among Scheme implementations seem to include: Gauche, Ypsilon, TinyScheme, Scheme 48, Owl, and the SCheme SHell (scsh).
And of course Scheme itself is dwarfed, in terms of both popularity and performance by other languages. Haskell seems to be the best overall functional language at the moment, and, when choosing a scripting / macro-language without a commitment to functional languages, better alternatives would be Lua (made faster than Scheme by LuaJIT), JavaScript / CoffeeScript (V8), and Ruby (Topaz).
--libman
-
lua vs perl stats
http://benchmarksgame.alioth.debian.org/u32/benchmark.php?test=all&lang=perl&lang2=lua
In some tests, one is faster than the other, but by no more than 4x to 1/9th each way.
At least they didnt choose ruby.
-
Re:Not in Debian
Afaik hurd-i386 has never been an official port. The only official non-Linux ports are kfreebsd-i386 and kfreebsd-amd64. -- http://www.debian.org/ports/
-
Re:GCC
RMS is the seed of all of this.
His contributions should be remembered with gratitude. I personally think that GCC was the most important single thing RMS did for us. As you noted, the existence of GCC was very helpful for Linux.
Don't knock him or his values.
I am grateful for what he has done for us, but I want to hold the modern RMS out at arms length. I like being paid to write software; RMS would have stern words for me, as I am writing proprietary software. I have released open source code as BSD license, that would earn me a scolding as well. I have installed Linux that doesn't call itself GNU/Linux, has binary blob proprietary drivers, all bad bad bad.
I believe that if he had the power to do so, RMS would require all software to have GPLv3 license. (During the "Freedom Zero" debate, Tim O'Reilly said that the developer has the freedom to choose a license for any software the developer writes; RMS rejected this idea forcefully, calling it "Power Play Zero". That's right, if you choose the license you want when you write software, you are imposing power over your poor defenseless users; shame on you! When Eric Raymond publicly called out RMS on whether he would require GPL if he had the power to do so, RMS did not reply, and I believe he did not reply because the answer is "yes" and RMS didn't want to say so in public but also didn't want to deny the truth.) I think GPLv2 is one of the greatest things ever, and we owe RMS for it, but GPLv3 is an overreach and I want no part of it. RMS has floated the IMHO insane idea that the government could collect a special tax and use it to pay some software developers, so they can earn a nice living while writing nothing but wholly free software. RMS refuses to recommend Debian GNU/Linux, even though they are the only Linux distribution in the top ten on DistroWatch that actually calls themselves "GNU/Linux" as RMS wishes... he refuses this because the Debian project has a server called "nonfree" with software that has non-fully-free licenses. Note that it is trivial to install Debian without any nonfree software, in fact I think you don't get the "nonfree" stuff by default, but that's not good enough for RMS and he turns a cold shoulder to the distro that has tried to live up to his ideals. And RMS has pushed some really bizarre licensing for documentation, with restrictions that make GNU documentation considered "nonfree" according to the Debian Free Software Guidelines. (I guess having GNU documentation branded "nonfree" by Debian didn't do much to make RMS happy about them either, but the DFSG date back to long before the problematic license changes.)
Also, RMS somewhat bastardized the design of GCC. He was worried that proprietary companies would "take advantage" of the free compiler by writing new front-ends and just using the GCC back-end, so he weirdly entangled the front end and back end. As a result of this, Clang is winning hearts and minds, as it was designed simply to be a very good compiler, and it has a nice clean design between front end and back end. (I haven't looked at the sources for GCC, but my understanding is that the weirdly entangled design is why GCC sometimes prints errors like "you have a problem somewhere in this line" while Clang indicates a specific line and column for the error.)
TL;DR We owe RMS a debt of gratitude for things he has done, but we don't owe him an uncritical ear for his current ideas.
-
Re:Wheezy?
I wonder why they picked that name since it is already what the Raspberry PI's version of Debian [Raspbian] is called.
Because "wheezy" is the codename for the upcoming Debian release, for all architectures, not just a specific system like the Raspberry Pi.
-
Not in Debian
they hope for the Debian 'Jessie' release their micro-kernel in Debian will make it as part of some official CDs.
Sorry, but Hurd is being demoted to a second-class (ie, unofficial) port. The rules say that a port that fails to be included in two subsequent releases, gets moved to the debian-ports ghetto, with shining neighbours like hppa (long dead) or sh4 (never has been).
In some ways, that's a pity -- like, improving other code by forcing removal of buffer overflows/asinine truncations related to PATH_MAX. In others, well, it's Hurd...
-
Minitube does not use the Flash Player
http://flavio.tordini.org/minitube
Linux, Mac OS X, Windows
"Light on your computer. By consuming less CPU, Minitube preserves battery life and keeps your laptop cool. That's because Minitube does not use the Flash Player.
High Definition. Minitube plays HD videos up to 1080p. Go full-screen and watch them play smoothly.
1-Click Downloads. Download your favorite clips to your computer and put them on your portable device. Downloaded files are in MPEG4 format which is compatible with most devices, including Apple ones.
Stop fiddling. Just search for something. Minitube automatically plays videos one after another. Sit back and enjoy."
http://packages.ubuntu.com/quantal/minitube
http://packages.debian.org/sid/minitube -
Yes, I do use use SPF and tumgreyspf even
Not only I use SPF, but I also maintain the tumgreyspf package in Debian, which does both SPF and greylisting.
And for those who have bad SPF records, and send email from the wrong IP? Well too bad, they wont be able to write to me. But as well to so many other persons (gmail, hotmail, etc.) that it's not really a huge concern, and that I don't feel like I should be the one having to spend the time explaining how to configure things. -
Re:Giggle
You'd like to think so, but when things like this happen, you can see that having thousands of unqualified people looking at code and sometimes modifying it is not really any benefit to security at all.
-
Re:Decade old GNOME bug not fixed
For something that's more completely considered a bug, check the long and sorry history of bug 108951. Only about 6 years old, but one of the more irritating ones. Sad to see such an issue bounced from distro to project to DE and back again, then finally closed because the feature it affects is removed.
-
Re:Enough Already
Java has a very small memory footprint by default.
Erm. No. Just no.
class Main { public static void main(String[] args) { while (true); } }
(jdk 1.7.0.6 x86_64 linux)
17M resident for that. 0.5G of virtual address space. The only other class referenced is java.lang.String.
The equivalent Perl is 1.7M. Node.js is 9M. Python is 4M. TCL is 1.9M.
EVERYTHING uses less RAM than bleeping Java. A lot less. And this isn't some fail test where Java gets better as applications scale. Go look over here and observe how almost every other language consumes less memory across a wide variety of algorithms. Anecdotal evidence from any app server admin will corroborate this.
Java is a RAM pig and it always has been. The problem, at least regarding initial memory footprint (and start-up time), is excessive class loading. This is not opinion. There has been a project to correct it on the books for almost four years.
Like everything else with Java, it has been neglected. Supposedly the results will appear in JDK 9..... sometime in 2015.
And don't cite Android as some exception. Dalvik isn't JRE.
-
Re:How do we stop them?
install linux (i prefer debian stable, but that's just me)
closed all uncessary ports
that's usually a function of your router, but linux can also be used for routing functions using an iptables script... here's an example that you can execute from
/etc/rc.local (on a debian machine anyway):#!/bin/bash
echo -n "Loading iptables firewall..."
iptables -F
iptables -P OUTPUT ACCEPT
iptables -P FORWARD DROP
iptables -P INPUT DROP
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A INPUT -j DROP
echo "done."
exit 0not the most locked down firewall that you can make with iptables, but its probably a similar configuration to what you would find in most off-the-shelf routers by default. you only need to add more exceptions if you run servers of sorts (ports 80 and 443 for httpd, 25 and 110 for mail, 53 for dns, etc). you can also nat between networks with iptables.
edit
/etc/hosts.deny and make the only non-commented line ALL:ALL, and make sure there is nothing (except comments) in /etc/hosts.allowalso be sure to configure all users except human users and root so that shell is
/bin/false in /etc/passwd and /etc/passwd-also, don't install any programs from sources other than official repositories (except for things like flash from adobe website) and don't install garbage apps and avoid torrrent clients which are a breeding ground for malware for all operating systems. i tend to favor stable repositories (with auto security repos update), with many vulnerabilities being due to inadequately tested updates. despite the hype, the testing aspects of both waterfall and extreme programming methodologies are rarely followed in open source projects, with the most common being the "code and test" or (derogative) "cowboy coding" methodology.
use shields up @ https://www.grc.com/x/ne.dll?bh0bkyd2 to verify if you have any exposed ports
also, to protect your wifi network(s), only use wpa2 (don't use wep) and set up an access list so that only registered mac addresses will be able to connect
always use https for online banking and make sure the top and 2nd level domains are what you expect (most modern browsers highlight them)
some of this stuff is less to do with asio and more to do with security in general. no doubt other
/. users will chime in if i've said something wrong or if i've missed something obvious. there's also other security things like wheel group, and there are hardening tutorials for most major distros out there. debian has a good one here: http://www.debian.org/doc/manuals/securing-debian-howto/ but for controlling remote access, the best way is to harden your browser settings (uninstall/disable any unneccesary plugins, disable java, etc), tighten up your wifi security and make sure no router ports are openthe internet is a scary place, but most viruses and malware is unintentionally installed by users from a web browser or email client (in windows). hacking is a problem, but its only serious if you're hosting. look up how a router works and that may help cool some of your fears. grc has a good info page here: http://www.grc.com/nat/nat.htm
summary: think of a nat router as sort of being like a one-way valve, so you can make requests out but only responses to your requests can come back in (ininvited requests are dropped)
if your computer is part of a botnet, there's a good chance that you unintentionally installed software from your web browser or email (or junkware/shareware) that caused it. malware rarely if ever gets onto your pc on its own, and also having malware or virus infected files on your machine is ok as long as they aren't op -
Re:WinUAE
Ah, thanks for the additional background. Yes, a pointer to the problems would probably be appreciated by the ARAnyM developers.
The d-i will not work right now, not with the normal mirrors at least, due to debootstrap being unable to cope with needing to pull packages from *two* distributions (unstable and unreleased), we think. We're working on it.
https://wiki.debian.org/M68k/Installing in the meantime has an ext2fs image you can use / boot into, and kernels.
-
Re:WinUAE
cbmuser already issued an Intent To Package FS-UAE to Debian, which makes use of WinUAE's "accurate emulation".
I believe that you should be able to use wouter's d-i build from http://people.debian.org/~wouter/d-i/ to install an m68k system from unstable (with the usual caveats, i.e. installing or debootstrapping unstable does not always work). Note that the build is still "fresh" and nobody has tested it yet, so a failure would not mean an emulation problem.
Once FS-UAE is in Debian, I'll likely publish a disc image for starters like https://wiki.debian.org/Aranym/Quick for the emulated Atari. (Today, I'll make updated
.tar.gz archives of a debootstrap result, which helps people already running etch-m68k or sarge (the image you linked is Debian 3.1 = sarge) to quickly install a fresh system, or at least the user space part.)Watch the debian-68k@lists.d.o mailing list, and/or the Debian Wiki, for progress.
-
Re:WinUAE
cbmuser already issued an Intent To Package FS-UAE to Debian, which makes use of WinUAE's "accurate emulation".
I believe that you should be able to use wouter's d-i build from http://people.debian.org/~wouter/d-i/ to install an m68k system from unstable (with the usual caveats, i.e. installing or debootstrapping unstable does not always work). Note that the build is still "fresh" and nobody has tested it yet, so a failure would not mean an emulation problem.
Once FS-UAE is in Debian, I'll likely publish a disc image for starters like https://wiki.debian.org/Aranym/Quick for the emulated Atari. (Today, I'll make updated
.tar.gz archives of a debootstrap result, which helps people already running etch-m68k or sarge (the image you linked is Debian 3.1 = sarge) to quickly install a fresh system, or at least the user space part.)Watch the debian-68k@lists.d.o mailing list, and/or the Debian Wiki, for progress.
-
Re:Anybody using Ada?
The TIOBE language popularity index says Ada is holding steady in 16th place - actually up from 24th place 5 years ago, but down from being the second most popular language (after C) 25 years ago.
According to The Great Programming Language ShootOut (recently renamed to The Benchmarks Game), Ada is almost as fast as C (then again, so are Pascal and Fortran), but it's also the most verbose language in the comparison!
Unsurprising, given how much them lazy overpaid government contract moochers hate efficiency...
Also note that there doesn't seem to be a genuinely free implementation of Ada... (Note that LLVM DragonEgg is still based on GPLv3'ed GCC, puke.)
The only thing to like about that language is its name!
--libman
-
Re:Anybody using Ada?
The TIOBE language popularity index says Ada is holding steady in 16th place - actually up from 24th place 5 years ago, but down from being the second most popular language (after C) 25 years ago.
According to The Great Programming Language ShootOut (recently renamed to The Benchmarks Game), Ada is almost as fast as C (then again, so are Pascal and Fortran), but it's also the most verbose language in the comparison!
Unsurprising, given how much them lazy overpaid government contract moochers hate efficiency...
Also note that there doesn't seem to be a genuinely free implementation of Ada... (Note that LLVM DragonEgg is still based on GPLv3'ed GCC, puke.)
The only thing to like about that language is its name!
--libman
-
lintian warnings
There's few issues in this package. First, it seems to be i386 only. Then, it's setting-up a repository in
/etc/apt/source.list.d without warning the users... Then, it's full of lintian warnings:
# lintian -Ii -E --pedantic steam.deb
W: steam: debian-changelog-line-too-long line 3
N:
N: The given line of the latest changelog entry is over 80 columns. Such changelog entries may look poor in terminal windows and mail messages and be annoying to read. Please wrap changelog entries at 80 columns or less where possible.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: changelog-file, Type: binary
N:
W: steam: debian-changelog-line-too-long line 4
W: steam: copyright-without-copyright-notice
N:
N: The copyright file for this package does not appear to contain a copyright notice. You should copy the copyright notice from the upstream
N: source (or add one of your own for a native package). A copyright notice must consist of Copyright, Copr., or the Unicode symbol of C in a circle followed by the years and the copyright holder. A copyright notice is not required for a work to be copyrighted, but Debian requires the copyright file include the authors and years of copyright, and including a valid copyright notice is the best way to do that. Examples:
N:
N: Copyright YYYY Firstname Lastname
N: Copr. YYYY-YYYY Firstname Lastname
N: © YYYY,YYYY Firstname Lastname
N:
N: If the package is in the public domain rather than copyrighted, be sure to mention "public domain" in the copyright file. Please be aware that this is very rare and not the same as a DFSG-free license. True public domain software is generally limited to such special cases as a work product of a United States government agency.
N:
N: Refer to http://ftp-master.debian.org/REJECT-FAQ.html for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: copyright-file, Type: binary
N:
E: steam: malformed-deb-archive found 4 members instead of 3
N:
N: The binary package is not a correctly constructed archive. A binary Debian package must be an ar archive with exactly three members: debian-binary, control.tar.gz, and one of data.tar.gz, data.tar.bz2 or data.tar.xz in exactly that order. The debian-binary member must start with a single line containing the version number, with a major revision of 2.
N:
N: Refer to the deb(5) manual page for details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: deb-format, Type: binary, udeb
N:
W: steam: extended-description-line-too-long
N:
N: One or more lines in the extended part of the "Description:" field have been found to contain more than 80 characters. For the benefit of users of 80x25 terminals, it is recommended that the lines do not exceed 80 characters.
N:
N: Refer to Debian Policy Manual section 3.4.1 (The single line synopsis)
N: for details.
N:
N: Severity: normal, Certainty: certain
N:
N: Check: description, Type: binary, udeb
N:
W: steam: extended-description-line-too-long
E: steam: description-contains-tabs
N:
N: The package "Description:" must not contain tab characters.
N:
N: Refer to Debian Policy Manual section 5.6.13 (Description) for details.
N:
N: Severity: important, Certainty: certain
N:
N: Check: description, Type: binary, udeb
N:
W: steam: extended-description-line-too-long
W: steam: extended-description-line-too-long
W: steam: extended-description-line-too-long
W: steam: extended-description-line-too-long
W: steam: extended-description-line-too-long
W: steam: extended-description-line-too-long
W: steam: extended-description-line-too-long
W: steam: extended-description-line-to -
Re:What driver revolution?
A revolution would be if one needed no proprietary firmware to fully use AMD video cards. Just look at all those Radeon blobs http://packages.debian.org/squeeze/firmware-linux-nonfree
It is possible however to use most such cards in basic 2D operations without those blobs...
-
Re:Somebody's got to say it
How can someone who is such an advocate for freedom support denying freedom to others?
In fairness, Bruce is hardly a disinterested party, having had a bit of a problem with people who have a problem with "gun control": http://lists.debian.org/debian-user/1999/04/msg00623.html
-
Re:Look at the patch.
Same thing when firefox removed PPC [...] support.
-
Re:Dammit
Debian dropped 386 support way back when 3.1 came out. Here are the reasons.
Your link is from 2003. Didn't 3.1 come out in 2011?
-
Re:Dammit
Debian dropped 386 support way back when 3.1 came out. Here are the reasons.
-
Re:Time to fork
See: http://packages.debian.org/search?keywords=linux-image
Debian dropped i386 kernel images a very long time ago; the lowest you can go is 486.
Annoying for me is, that they also dropped i686 without pae. Meaning for my AMD Geodes I either have to roll my own or install 486. -
Or *are* we?
I say, declare your independence.
-
Re:NFS + ZFS
I don't see any indication that a) this has any relation to the size of the directory
The cited bug points out a problem with readdir(). This manifests itself as failures with other software, including dovecot (where maildir is used) and bonnie++. Some of those other bugs were reported and marked as duplicates, some weren't.
Ultimately it boiled down to a flaw in Linux NFS that was fixed by Trond Myklebust and was still perculating through distributions over a year later.
Never in years has it given me one problem, but hey, that's just me.
Yeah, that's just you. Me? I've been watching hapless administrators discover NFS flaws since the 90's and I have long since abandoned NFS as a serious tool for production operations. It's fine in most cases as a file share for interactive use (/home and ad hoc shares) and not much else. Under certain conditions with extremely good NFS implementations (netapp, for example) you can pull it off. The other 99% of the time it's just a mistake.
-
Re:openSUSE
Yes, I know. MATE and Cinnamon aren't in the official repositories yet, but that's only a matter of getting a bigger hammer.
To be fair, there is a big difference between having a desktop environment and window manager which run on a system and having all of its features fully integrated and supported. I can quite happily run FVWM on my desktop, but things start getting awkward when I run an application which expects to find a dock or notification area from Gnome.
-
Re:Canonical vs. Red Hat
http://wiki.debian.org/systemd
http://en.gentoo-wiki.com/wiki/SystemdStrange, last I heard was that Debian added it as an *alternative*. Gentoo's had their own initsystem (they switched to openrc right about when I left 'em), but, to be honest, the average Gentoo user could probably boot his PC just by flicking the power randomly to clock the bits into RAM.
-
Re:How much money goes to Debian.org?
Probably more than what Ubuntu derivatives are giving to Canonical, Amazon to Anroid developement, BLAG to Fedora, or Debian to various sub-projects...
I fear Debian is not getting much money from (commercial) derivatives. I think they use the money in some other way.
What would be Ubuntu without Debian? A Gentoo or Fedora or Slackware derivative?
Probably yes. With the same issues and my very same question! -
Re:Hmm
Quick summary of the java situation on raspbian:
Oracle java doesn't currently work on armv6 hard float.
Openjdk with zero works but is SLOW
Openjdk with jamvm works and seems to be the most workable option right now
Openjdk with cacao is broken on all arm hardfloat platforms at the moment*.
I haven't tried openjdk with shark or avian. -
Re:Hmm
Quick summary of the java situation on raspbian:
Oracle java doesn't currently work on armv6 hard float.
Openjdk with zero works but is SLOW
Openjdk with jamvm works and seems to be the most workable option right now
Openjdk with cacao is broken on all arm hardfloat platforms at the moment*.
I haven't tried openjdk with shark or avian. -
Re:I don't get it.
-
Re:Not required to use every package manager
It is a sin to say "debian-multimedia" and Stefano Zacchiroli will come and strangle your children if you do it again. http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-May/thread.html#26678
-
Re:And that will also mark
It should die just because you aren't interested? Mate does use gtk2 right now (just like Xfce, etc.) which is stable rather than unsupported, and continues to receive small updates and bug fixes. As for the other libraries, here's a comment from one of the developers:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658783#95
"MATE team is working hard to do this and we are in a good point. Migration to gsettings/dbus (and deletion of obsolete libs like bonobo, gconf, gnome-vfs, libgnome, libgnomeui and libgnomecanvas) is almost complete, and GNOME developers helped us on this too."
-
Re:No platform is 100 percent secure?
No, the "open source" myth is not true. See e.g. http://www.debian.org/security/2012/
I'd bet that more holes are created than fixed, per day.
-
Re:Don't call it Linux
I meant all userland software written to work on Linux
Then Google Maps for Android is definitely a userland software written to work on Android/Linux. If here you say Android/Linux is not Linux, this would be circular argument : by assuming Android is not Linux you will be arguing Android is not Linux.
All distribution kernels work the same way to userland as the mainline kernel of the same version
No, read the debian policy. Running "rpm -qpl kernelxxxx.src.rpm" on a Centos kernel usually returns quite a number of patches.
Moreover, they work the same way with third-party modules
Not possible to be exactly the same if code patches have been applied.
-
Re:Did he already heard about integrated debugger
C++ lacking in expressiveness? You have got to be joking,
Well, how might you add "operator#" to C++? Adding new language features to C++ basically requires a new C++ compiler; lexical closures, for example, only became possible with C++11 (previously, Boost's lambda expressions library got you halfway there). That is a result of a lack of expressive power.
your right there are a lot of poorly defined areas in C++, but many of them stem from the fact that there are 100 different ways syntactically to solve any given problem.
It is mostly due to the standard being written for compiler writers and language implementors, rather than for programmers.
Of course some ways tend to be better than others, hence I'm confused about your problems with constructor error handling. You handle errors in constructors with "throw", combined with good RAII style, you get the benefit of fast code, that is robust to memory errors
Except when your objects are global, in which case throwing the exception means your program aborts, since there is no standard way to write a global catch (set_terminate won't work if the exception is thrown before the entry to main -- which is what will happen if the constructor of a global object throws the exception).
Destructors aren't as clear cut, but the easy answer is not to have fatal errors in the destructor
In other words, destructors should have trivial bodies. Why even have destructors if that is how things have to be done?
One of C++'s strong points (vs C) is that you can create a domain specific environment by careful class design and operator overloading
Unless you want to add a new kind of operator or a new kind of syntax.
As far as debug-ability, or a programmers ability to focus on the problem at had rather than the language, I suspect that is all just a matter of experience.
- Experienced C++ gurus make mistakes with pointer mechanics sometimes.
- In the real world, your team will have people with varying levels of experience; the least experienced person will be the bottleneck when it comes to things like undefined behavior, dangling pointers, etc.
In a lot of languages you learn how to do things, in C++ you tend to learn how _NOT_ to do things
Which is precisely the problem here. In C++, you need to know what valid C++ expressions, statements, or programs should simply not be written. Rather than rule such things out in C++11, the standards committee just added more things that you are supposed to know not to do.
Those results have re2, and it beats all the normal regular expression parsers only loosing to a lisp specific parsing/matching system. I don't call that a win for LISP, if you move the goal posts (we were comparing regex) then its not apples to apples. Its not hard to imaging a dozen ways of creating a searching sorting system faster than regex if your willing to wiggle the requirements.
Like I said, this is not a good benchmark; on the other hand, RE2 is not average twice the speed of libpcre (unless you count an outlier):
http://lh3lh3.users.sourceforge.net/reb.shtml
CL-PPCRE does average twice the speed of libpcre/Perl (unless you pick examples that libpcre can handle well):
http://cl-debian.alioth.debian.org/repository/rvb/cl-ppcre-sarge/doc/#bench
I would not draw too many conclusions from the benchmarks alone (there is no direct comparison between CL-PPCRE and RE2), but CL-PPCRE does do something that neither libpcre nor RE2 do: it compiles your regex into a callable function that does not traverse a pointer structure. With a good compiler (n