Can you qualify that statement? Especially the "neutral" part, it is
not
obvious to me how a DE can be, or not be "neutral".
By "neutral" I've meant a DE without "dubious" solutions discussed in
gnome3 flame wars all over the web. I don't really think we should also
discuss it here, just beca
Hi,
I'm not a Debian developer, just a Debian user, and I want to say that I
was happy to see XFCE being the default DE. Just because it's small,
classic and neutral DE - which GNOME 3 definitely isn't. I think XFCE is
a better default... because I think it's not that uncommon for people to
r
1. Could some competent person tell me the right way to tell apt that
it
should fail an upgrade rather than installing systemd? I guess
I could make a dummy package that conflicts with systemd, but I'm
sure there's a better way.
I think you can just put
Package: systemd
Pin:
Because I want logs to be plaintext in my system, not binary.
Install syslog. Or maybe Debian will use both journal and syslog.
I dislike the idea of binary logs so much that I want to really and
totally disable journal.
And I don't see why a binary log format is needed to implement the
st
It is of course well-known that systemd developers like to make their
life more complicated and love to implement binary formats instead of
writing simple text parsers, just for the sake of having fun
programming
them, and absolutely not because they need things like indexing.
The same goes for
Our users shouldn't care what init system we use. It's an
implementation -- and purely technical -- detail of the OS.
Sorry to interfere with your discussion, but it really sounds like some
kind of proprietary software idea :)
I'm sure a big percent of GNU/Linux (and especially Debian GNU/Lin
Because it's work, for no apparent gain. I mean, the systemd people
didn't
just code up all that journal stuff for no good reason, but because
they
perceived a need to have it. And let's face it, the ability to just see
the
stderr output from $FAILED_JOB with "systemctl status" is a whole damn
- Debian has sent patches upstream
- Mageia is *much* smaller distribution, that packager has attended
*various* systemd hackfests
- Mageia package maintainer sent various patches upstream
- Patches are *not* accepted based on how many people you represent or
which company you work for (e.g. so
oh ;) thanks for your checking!
1 more note: scons doc states that if you want to install package in a
"sandbox" for packaging, you should better supply real PREFIX=/usr, and
then supply --install-sandbox=./debian/tmp option to 'scons
install'. Don't know if it actually affects something
Is a Debian security update expected to come out for it?
Yes. Nginx team has already submitted updated package to security team.
Thanks for the information! I've actually found the bug stating this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730012
And what's the Debian process for su
Hi!
There is a nginx security advisory here:
http://mailman.nginx.org/pipermail/nginx-announce/2013/000125.html
Is a Debian security update expected to come out for it?
--
With best regards,
Vitaliy Filippov
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
Also I did serf update as Bug#716793, please
dget
http://www.mithril-linux.org/~henrich/debian/package/temp/serf_1.3.2-0.1.dsc
and check it, too.
I've actually already seen it... But it was after I've built it by
myself... :)
It seems your package has cleaner debian/rules so I would prefer
Yes, someone needs to review it, but before that the package tests
need to be fixed so they a) run and b) pass, reliably and repeatably.
After that, either get the package maintainers to discuss the new
version, or find someone to take over the package if they no longer
want to or can maintain it
13 matches
Mail list logo
