Hello,
the following is a discussion from the Debian bugtracking system regarding
Debian Bug#751704 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751704).
It needs involvement from parted upstream, therefore I am forwarding it to
bug-par...@gnu.org.
Kind regards,
Karsten
- Forwarded
Hi,
I've upload the theme with the rescaled logo.
If everything is OK, I can start the others artworks to complete the theme.
Regards,
Juliette
- Mail original -
De: Cyril Brulebois k...@debian.org
À: Vincent Blut vincent.deb...@free.fr
Cc: Adrien Aubourg adrien.aubo...@gmail.com,
which is fine.
But what if people decide to later not use logind/systemd? In what
does it hurt that the first created user is *also* added to the audio
group?
When a user is added to the audio group. He will always see all sound
devices,
even when logind tries to hide the device from the
Package: installation-reports
Severity: normal
Jessie beta1 on Dell PowerEdge T410 installation was successful. I had to
manually copy bnx2 firmware files into /lib/firmware/ but that is to be
expected at this stage, I suppose.
-- Package-specific info:
Boot method: CD
Image version:
On Mon, Aug 18, 2014 at 03:24:50PM +0200, Floris wrote:
which is fine.
But what if people decide to later not use logind/systemd? In what
does it hurt that the first created user is *also* added to the audio
group?
When a user is added to the audio group. He will always see all sound
On Mon, Aug 18, 2014 at 02:52:34PM +0100, Steve McIntyre wrote:
And if we ignore the multi-seat stuff (which is going to be used by a
*tiny* minority of users) there is no down-side.
There are still likely going to be vastly more non-systemd users than
multi-seat users.
That sure sounds
On Mon, Aug 18, 2014 at 10:22:16AM -0400, Lennart Sorensen wrote:
That sure sounds likely.
Perhaps there can be a README.multiseat in the systemd package that
explains what changes to make for such a setup.
Just because systemd is default doesn't mean everything else should
stop working.
Op Mon, 18 Aug 2014 15:52:34 +0200 schreef Steve McIntyre
st...@einval.com:
On Mon, Aug 18, 2014 at 03:24:50PM +0200, Floris wrote:
which is fine.
But what if people decide to later not use logind/systemd? In what
does it hurt that the first created user is *also* added to the audio
On Mon, Aug 18, 2014 at 05:20:19PM +0200, Floris wrote:
how about users who will login remotely? They also have full access to
all the audio devices, even when they don't able to hear the music,
because the speaker is on the other side of the world.
Remote login might be from a computer
On Mon, Aug 18, 2014 at 12:40:13AM -0500, Christopher Chavez wrote:
2. Would it be a better idea to only have /boot/grub, instead of /boot, on a
separate partition? (I can confirm that it works both when installing and in
existing setups, i.e. grub-install and update-grub both work as
On Mon, Aug 18, 2014 at 08:19:17AM +0200, Karsten Merker wrote:
Hello,
the following is a discussion from the Debian bugtracking system regarding
Debian Bug#751704 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751704).
It needs involvement from parted upstream, therefore I am forwarding
Quoting Steve McIntyre (st...@einval.com):
On Mon, Aug 18, 2014 at 03:24:50PM +0200, Floris wrote:
which is fine.
But what if people decide to later not use logind/systemd? In what
does it hurt that the first created user is *also* added to the audio
group?
When a user is added to
Your message dated Mon, 18 Aug 2014 19:15:53 +0200
with message-id 20140818171553.gi3...@mykerinos.kheops.frmug.org
and subject line Re: Bug#758522: installation-reports: Jessie beta1 on Dell
T410 successful
has caused the Debian Bug report #758522,
regarding installation-reports: Jessie beta1 on
user-setup-apply is run in finish-install, so it can check if systemd is
installed or not.
The only downsides I see:
* Still need to add the groups in non-systemd installations, eg freebsd,
so this will be an point of difference that will need testing.
* If a user chooses to remove systemd
On Mon, 2014-08-18 at 00:40 -0500, Christopher Chavez wrote:
(Please let me know if there's a better venue for collecting feedback for this
idea, or additional ones I should solicit feedback from. I primarily use
Ubuntu,
but I assume this is as upstream as it gets.)
Background:
It has
Hi Debian fellows,
In fact I was on the point to upload various Debian 8 themes, unfortunately
I had a huge computing problem and I lost my recent works (and so my Debian
8 theme propositions).
So, I would like to know if it would be possible to wait until the 25th
August before closing
Your message dated Mon, 18 Aug 2014 21:28:06 +0200
with message-id 20140818212806.fd90fa36b2db83f2b9bc6...@mailbox.org
and subject line Re: Bug#758411: d-i manual: aptitude is no longer the
recommended package management tool
has caused the Debian Bug report #758411,
regarding d-i manual:
On Mon, Aug 18, 2014 at 09:59:49AM -0700, Brian C. Lane wrote:
On Mon, Aug 18, 2014 at 08:19:17AM +0200, Karsten Merker wrote:
Hello,
the following is a discussion from the Debian bugtracking system regarding
Debian Bug#751704
Hi,
Cyril Brulebois k...@debian.org wrote:
Holger Wansing hwans...@mailbox.org (2014-08-17):
That would lead to more changes to the d-i manual IMO.
Indeed, and since you were updating the manual already I thought it
might make sense to batch everything together.
At least:
booting of
Hi Holger,
and thanks for the proposed patch!
Holger Wansing hwans...@mailbox.org (2014-08-18):
Index: en/boot-installer/x86.xml
===
--- en/boot-installer/x86.xml (Revision 69238)
+++ en/boot-installer/x86.xml (Arbeitskopie)
@@
Cyril Brulebois, le Mon 18 Aug 2014 23:36:03 +0200, a écrit :
+notepara
+
+The graphical installer requires significantly more memory to run than
+the regular installer: minimum-memory-gtk;. If insufficient memory is
+available, it will automatically fall back to the regular
Helloo,
Holger Wansing, le Mon 18 Aug 2014 23:07:11 +0200, a écrit :
Basically I moved the chapter Appendix D.6. The Graphical Installer to
5.1.8 (at the end of Booting the installer on 32-bit PC), leaving the
content unchanged.
And I moved chapter Appendix D.6.1. Using the graphical
Package: debian-installer
Version: 20140802
Severity: serious
Justification: FTBFS
Hi,
I've noticed what $Subject says through the daily builds. Looking at
last successful build and today's (failing) one, a few things pops up:
| -Unpacking libdebian-installer4-udeb (0.94) ...
| +Unpacking
Cyril Brulebois k...@debian.org (2014-08-18):
Now, hurd-i386 doesn't need caring about; kfreebsd-* architectures are
looking quite badly already, so I won't change anything on those right
now. I expect arm* people to tell us whether any change is needed for
those, but since I see no menu
[ Adding -accessibility@ and -cd@ to the loop. ]
Steve McIntyre st...@einval.com (2014-08-17):
On Sun, Aug 17, 2014 at 01:25:28PM +0200, Cyril Brulebois wrote:
Control: tag -1 confirmed
Another issue is that it requires much more memory, but that IMO is not a
blocker. It does require
Cyril Brulebois, le Tue 19 Aug 2014 01:17:02 +0200, a écrit :
= debian-accessibility@: if we go from i386 to amd64 by default, is
there anything that needs to be done on your side (doc update etc.)
Normally, only the installer manual would need an update. I don't see
the multi-arch boot menu
[ I'm adding -release@ to the loop. I tried to refrain from mentioning
my concerns in the Jessie Beta 1 announce, that's why I used a quite
neutral wording, but let's be honest: kfreebsd-* is looking bad right
now. ]
Cyril Brulebois k...@debian.org (2014-08-14):
Steven Chamberlain
Processing control commands:
tags -1 + pending
Bug #758476 [installation-guide] d-i manual: part about bootloader installation
is missing in example preseed file 'preseed.txt'
Added tag(s) pending.
--
758476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758476
Debian Bug Tracking System
Control: tags -1 + pending
Holger Wansing, le Sun 17 Aug 2014 22:59:19 +0200, a écrit :
The relevant paragraph was set to arch=any-x86 with this commit:
http://anonscm.debian.org/viewvc/d-i/trunk/manual/en/appendix/preseed.xml?r1=65001r2=65009
This attribute works for building the manual
I installed Jessie using a Braille display.
Debian-Jessie-DI-b1-amd64-net inst.iso
I tried to get Orca going like this.
Open a text console and login as root:
aptitude instal gnome-orca
orca -t
Now it tells me no speech is available, so I do
aptitude install espeak
orca -t
Still no speech
Quoting Joey Hess (jo...@debian.org):
user-setup-apply is run in finish-install, so it can check if systemd is
installed or not.
Interesting suggestion, yes.
The only downsides I see:
* Still need to add the groups in non-systemd installations, eg freebsd,
so this will be an point of
Hoy,
Le mardi, 19 août 2014, 01.17:02 Cyril Brulebois a écrit :
The default is Install right now, which installs i386. The topic of
this bug report is switching to Graphical install by default, but
shouldn't we also promote amd64 by default while we're at it? This
would mean having 64 bit
32 matches
Mail list logo
