Processed: Re: Bug#821424: pulseaudio: Do not put normal users on group audio

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 user-setup
Bug #821424 [debian-installer] pulseaudio: Do not put normal users on group 
audio
Bug reassigned from package 'debian-installer' to 'user-setup'.
Ignoring request to alter found versions of bug #821424 to the same values 
previously set
Ignoring request to alter fixed versions of bug #821424 to the same values 
previously set

-- 
821424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#821424: pulseaudio: Do not put normal users on group audio

[Christian PERRIER]

Control: reassign -1 user-setup

Quoting Felipe Sateler (fsate...@debian.org):
> Control: reassign -1 debian-installer
> 
> On 18 April 2016 at 13:06, Corcodel Marian  wrote:
> 
> > Any way pulseaudio is default sound server on debian and suggest to do not 
> > put
> > users on audio group because cross interference with alsa programs, now 
> > alsa is
> > for power users and pulseaudio is on default.
> 
> Pulseaudio does not add the user to the audio group. I'm guessing the
> installer does, so I reassign there.


Adding the *first created* user to so-called "useful" groups is done
by user-setup.

We'll need a detaailed explanantion abou twhy this shouldn't be done
anymore, including all possible use cases of the installer.




signature.asc
Description: PGP signature

Bug#821341: debian-installer: unbootable, no gpt partition for uefi install

[josh]

Hi Steve,

thanks for your reply.

> It depends very much on the machine involved, to be honest - many will
> boot UEFI from appropriately partitioned MBR-partitioned disks. It
> depends very much on the firmware of the machine here.

hmmm...I didn't wade through the 1000+ page UEFI specs myself, but this
entry on superuser.com cites them and claims that according to the
specs, a UEFI boot partition /must/ reside on a gpt disk (this makes
some sense since gpt is part of the UEFI specs afaik...):

http://superuser.com/questions/563074/do-hard-drives-need-a-guid-partition-table-gpt-to-boot-in-uefi-mode

This MSDN article states the same
(https://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.aspx#gpt_faq_mixed_gpt_mbr):

"Systems that support UEFI require that boot partition must reside on a
GPT disk. Other hard disks can be either MBR or GPT."


> This is clearly difficult to do in some cases, e.g. if
> other OSes are on the system already.
>

I agree that if somebody's installing to drive that already has
something installed on it, than you can't just go and change the mbr to
a gpt without asking. I was doing a virgin install of a new machine
originally partitioning and formatting a new blank disk. In this case
you should definitely have at least the option of having a gpt and
probably a notification that this would be preferable.

As far as I remember, I /did/ select expert install and I didn't find an
option for choosing gpt. Are you saying there is one, and I missed it?
If so, it doesn't seem easily findable (or I'm blind, or didn't select
expert install after all...).

If it is the case that the UEFI specs actually require a gpt for efi
boot, than a gpt should be the *default* for an UEFI install imho. If
d-i detects another OS and the disk is mbr, than d-i should display a
message either asking whether the disk should be converted to mbr
stating the risks and/or state that the system likely won't be UEFI
bootable if a gpt is not selected. All this should be available even in
a non-expert install, again imho.

Also, if it is the case that the UEFI specs require a gpt for efi boot,
and some systems are uefi booting from mbrs, than those are the buggy
ones, and whether one hopes it or not, one might expect that more and
more mainboard chipsets will implement the specs correctly and not uefi
boot from non-gpt disks. I have an MSI mainboard, which I think are
pretty good, and it definitely refused to boot from an mbr disk with an
efi partition.

cheers,

Josh


On 18.04.2016 16:00, Steve McIntyre wrote:
> Control: merge -1 821340
> Control: reassign 821340 partman-efi
> Control: retitle 821340 partman-efi: add extra warning about preferring GPT 
> for USE installation
> 
> Hi Josh,
> 
> I'm merging this with your other bug report - they're clearly the same
> issue.
> 
> On Sun, Apr 17, 2016 at 10:37:53PM +0200, josh wrote:
>> Package: debian-installer
>> Severity: important
>>
>> After installation system was not bootable.
>>
>> During the installation it said that it had detected that I had UEFI
>> booted the installation CD and proposed to make an EFI boot partion
>> which I accepted. However, after installation, Debian wasn't bootable.
>>
>> I tracked the problem down to the fact that even though it said it was
>> installing a UEFI bootable system, the hard drive was still partitioned
>> with an MBR, which is not UEFI boot compatible. There seemed to be no
>> option for selecting/forcing gpt partitioning.
>>
>> Using a rescue cd and converting the MBR to a gpt and then reinstalling
>> grub-uefi solved the problem without having to reinstall the system.
>>
>> It would seem to me that if the installer detects an uefi booted system
>> and is installing an efi boot partition then it should automatically
>> partition with a gpt and not an mbr.
> 
> Again, it should be possible to do this (select GPT) using expert mode
> rather than having to restart. Maybe we should add a warning during
> partman-efi setup that some machines won't boot in MBR mode, and offer
> to switch. This is clearly difficult to do in some cases, e.g. if
> other OSes are on the system already.
> 

Bug#821424: pulseaudio: Do not put normal users on group audio

[asu]

On 04/18/2016 09:01 PM, Felipe Sateler wrote:

On 18 April 2016 at 14:59, asu  wrote:


On 04/18/2016 07:36 PM, Felipe Sateler wrote:

Control: reassign -1 debian-installer

On 18 April 2016 at 13:06, Corcodel Marian  wrote:


Any way pulseaudio is default sound server on debian and suggest to do
not put
users on audio group because cross interference with alsa programs, now
alsa is
for power users and pulseaudio is on default.

Pulseaudio does not add the user to the audio group. I'm guessing the
installer does, so I reassign there.



Pulseaudio  does not add users but can do erase all users from audio group.

We most certainly should not do that.


But on setup process pulseaudio add user pulse on audio group.

Bug#821424: pulseaudio: Do not put normal users on group audio

[asu]

On 04/18/2016 07:36 PM, Felipe Sateler wrote:

Control: reassign -1 debian-installer

On 18 April 2016 at 13:06, Corcodel Marian  wrote:


Any way pulseaudio is default sound server on debian and suggest to do not put
users on audio group because cross interference with alsa programs, now alsa is
for power users and pulseaudio is on default.

Pulseaudio does not add the user to the audio group. I'm guessing the
installer does, so I reassign there.



Pulseaudio  does not add users but can do erase all users from audio group.

Bug#821424: pulseaudio: Do not put normal users on group audio

[asu]

On 04/18/2016 09:01 PM, Felipe Sateler wrote:

On 18 April 2016 at 14:59, asu  wrote:


On 04/18/2016 07:36 PM, Felipe Sateler wrote:

Control: reassign -1 debian-installer

On 18 April 2016 at 13:06, Corcodel Marian  wrote:


Any way pulseaudio is default sound server on debian and suggest to do
not put
users on audio group because cross interference with alsa programs, now
alsa is
for power users and pulseaudio is on default.

Pulseaudio does not add the user to the audio group. I'm guessing the
installer does, so I reassign there.



Pulseaudio  does not add users but can do erase all users from audio group.

We most certainly should not do that.

Not only on debian-installer  , on all applications which use separate 
users like asterisk, lightdm and so.

Re: Bug#821424: pulseaudio: Do not put normal users on group audio

[Felipe Sateler]

On 18 April 2016 at 14:59, asu  wrote:
>
>
> On 04/18/2016 07:36 PM, Felipe Sateler wrote:
>>
>> Control: reassign -1 debian-installer
>>
>> On 18 April 2016 at 13:06, Corcodel Marian  wrote:
>>
>>> Any way pulseaudio is default sound server on debian and suggest to do
>>> not put
>>> users on audio group because cross interference with alsa programs, now
>>> alsa is
>>> for power users and pulseaudio is on default.
>>
>> Pulseaudio does not add the user to the audio group. I'm guessing the
>> installer does, so I reassign there.
>>
>>
> Pulseaudio  does not add users but can do erase all users from audio group.

We most certainly should not do that.

-- 

Saludos,
Felipe Sateler

Processed: Re: Bug#821424: pulseaudio: Do not put normal users on group audio

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 debian-installer
Bug #821424 [pulseaudio] pulseaudio: Do not put normal users on group audio
Bug reassigned from package 'pulseaudio' to 'debian-installer'.
No longer marked as found in versions pulseaudio/5.0-13.
Ignoring request to alter fixed versions of bug #821424 to the same values 
previously set

-- 
821424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#821424: pulseaudio: Do not put normal users on group audio

[Felipe Sateler]

Control: reassign -1 debian-installer

On 18 April 2016 at 13:06, Corcodel Marian  wrote:

> Any way pulseaudio is default sound server on debian and suggest to do not put
> users on audio group because cross interference with alsa programs, now alsa 
> is
> for power users and pulseaudio is on default.

Pulseaudio does not add the user to the audio group. I'm guessing the
installer does, so I reassign there.


-- 

Saludos,
Felipe Sateler

Processed (with 1 error): merging

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 821340 821341
Bug #821340 [partman-efi] partman-efi: add extra warning about preferring GPT 
for USE installation
Unable to merge bugs because:
package of #821341 is 'debian-installer' not 'partman-efi'
Failed to forcibly merge 821340: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821340
821341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#821341: debian-installer: unbootable, no gpt partition for uefi install

[Steve McIntyre]

Control: merge -1 821340
Control: reassign 821340 partman-efi
Control: retitle 821340 partman-efi: add extra warning about preferring GPT for 
USE installation

Hi Josh,

I'm merging this with your other bug report - they're clearly the same
issue.

On Sun, Apr 17, 2016 at 10:37:53PM +0200, josh wrote:
>Package: debian-installer
>Severity: important
>
>After installation system was not bootable.
>
>During the installation it said that it had detected that I had UEFI
>booted the installation CD and proposed to make an EFI boot partion
>which I accepted. However, after installation, Debian wasn't bootable.
>
>I tracked the problem down to the fact that even though it said it was
>installing a UEFI bootable system, the hard drive was still partitioned
>with an MBR, which is not UEFI boot compatible. There seemed to be no
>option for selecting/forcing gpt partitioning.
>
>Using a rescue cd and converting the MBR to a gpt and then reinstalling
>grub-uefi solved the problem without having to reinstall the system.
>
>It would seem to me that if the installer detects an uefi booted system
>and is installing an efi boot partition then it should automatically
>partition with a gpt and not an mbr.

Again, it should be possible to do this (select GPT) using expert mode
rather than having to restart. Maybe we should add a warning during
partman-efi setup that some machines won't boot in MBR mode, and offer
to switch. This is clearly difficult to do in some cases, e.g. if
other OSes are on the system already.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis

Processed (with 1 error): Re: Bug#821341: debian-installer: unbootable, no gpt partition for uefi install

[Debian Bug Tracking System]

Processing control commands:

> merge -1 821340
Bug #821341 [debian-installer] debian-installer: unbootable, no gpt partition 
for uefi install
Unable to merge bugs because:
severity of #821340 is 'normal' not 'important'
package of #821340 is 'installation-reports' not 'debian-installer'
Failed to merge 821341: Did not alter merged bugs.

> reassign 821340 partman-efi
Bug #821340 [installation-reports] debian installer bug: doesn't partition with 
gpt for uefi install
Bug reassigned from package 'installation-reports' to 'partman-efi'.
Ignoring request to alter found versions of bug #821340 to the same values 
previously set
Ignoring request to alter fixed versions of bug #821340 to the same values 
previously set
> retitle 821340 partman-efi: add extra warning about preferring GPT for USE 
> installation
Bug #821340 [partman-efi] debian installer bug: doesn't partition with gpt for 
uefi install
Changed Bug title to 'partman-efi: add extra warning about preferring GPT for 
USE installation' from 'debian installer bug: doesn't partition with gpt for 
uefi install'.

-- 
821340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821340
821341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#821340: debian installer bug: doesn't partition with gpt for uefi install

[Steve McIntyre]

On Sun, Apr 17, 2016 at 10:19:54PM +0200, josh wrote:
>Package: installation-reports
>
>Boot method: CD
>Image version: 8.3 amd64 netinstall
>Date: March 2016
>
>Machine: custom built
>Processor: amd A10 7850k
>Memory: 8gb
>Partitions: 
>
>After installation system was not bootable.
>
>During the installation it said that it had detected that I had UEFI
>booted the installation CD and proposed to make an EFI boot partion
>which I accepted. However, after installation, Debian wasn't bootable. I
>tracked the cause down to the fact that even though it said it was
>installing a UEFI bootable system, the hard drive was still formatted
>with an MBR, which is not UEFI boot compatible. There seemed to be no
>option for selecting/forcing gpt partitioning. Using a rescue cd and
>converting the MBR to a gpt and then reinstalling grub-uefi solved the
>problem without having to reinstall the system.
>
>  and ideas you had during the initial install.>
>
>Except for this, the installation was very smooth, but this one problem
>unfortunately cost my a couple hours of frustration and several
>re-installs until I figured out what was wrong.
>
>It would seem to me that if the installer detects an uefi booted system
>and is installing an efi boot partition then it should automatically
>partition with a gpt and not an mbr.

Hi Josh,

It depends very much on the machine involved, to be honest - many will
boot UEFI from appropriately partitioned MBR-partitioned disks. It
depends very much on the firmware of the machine here. d-i
deliberately will not *by default* change partition type. If you do
need to do this, expert mode should let you do it anyway.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
  note stuck to the mini-bar saying "Paul: This fridge and
  fittings are the correct way around and do not need altering"

Bug#771699: Provide A Preseed Option For Ignoring The Valid-Until Field of InRelease Files

[Raymond Burkholder]

> 
> Mostly "we take (working) patches"?
> 

Fair enough.  Would you be able give me push in the right direction and provide 
a hint as to which packages/files I should be looking at?

Bug#386055: marked as done (tasksel: Please add a GIS workstation task)

[Debian Bug Tracking System]

Your message dated Mon, 18 Apr 2016 09:58:08 +0200
with message-id <57149390.1090...@debian.org>
and subject line Done: tasksel: Please add a GIS workstation task
has caused the Debian Bug report #386055,
regarding tasksel: Please add a GIS workstation task
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
386055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: tasksel
Version: 2.54
Severity: wishlist

The Debian GIS subproject is working to package and integrated the
free GIS tools to make them easily available and ready for
professional use.  To make the tools easier to find, I believe it
would be useful if there were a GIS workstation task in tasksel.  Here
is a suggestion for such task.  It is based on the list of packages
available in the Debian GIS wiki,
, and a sanity
check on the Debian GIS mailing list.

Please include this task in a future version of tasksel.  I'm not
quite sure which relevance and section to use.  Please change it if
you know better values.  The package order is also fairly random.  If
it is better to keep it sorted, please sort it.

I'm sure we will adjust this list as the Debian GIS project advances,
but please accept it as an initial draft. :)

Task: gis-workstation
Relevance: 6
Section: user
Description: Geographic Information Systems (GIS) workstation
 This task sets up your system to be a GIS workstation to process
 geographical information and make maps.
Key:
 grass
 qgis
 qgis-plugin-grass 
Packages: task-fields
Packages-list:
 thuban
 mapserver
 gmt
 gpsbabel
 gpx2shp
 gpsd
 gpsdrive
 gpsman
 openjump
 earth3d
 openscenegraph
 proj
 postgis
 opencv
 kflog
 grace6
 gpstrans
 geoip
 gpsd-clients
 grass-doc
 php4-mapscript
 phppgadmin
 gpsmanshp

--- End Message ---
--- Begin Message ---
Hi,

when scanning though the tasksel bugs I found this one which is IMO
solved by blends-tasks 0.6.93. You should however rebuild the "gis-all"
package with the according blends-dev 0.6.93 package. This will create a
new binary package "gis-all" containing all GIS tasks. To exclude a task
from gis-all, put a "Install: false" into the tasks header. Exclusion
can be done for a whole task only; for individual packages it should be
adjusted with assigning "Depends" vs. "Suggests".

Best regards

Ole--- End Message ---