Bug 31212 - collecting the distribution of someone else doesn't save it to the owners $HOME
collecting the distribution of someone else doesn't save it to the owners $HOME
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Distribution
UCS@school 3.1
Other Linux
: P3 normal (vote)
: UCS@school 3.x
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-26 13:50 CEST by Ingo Steuwer
Modified: 2019-02-05 21:27 CET (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Steuwer univentionstaff 2013-04-26 13:50:24 CEST
Following the documentation (http://docs.univention.de/ucsschool-lehrer-handbuch-3.1.html#lehrerdoku:material:einsammeln), collected projects are stored in the $HOME of the project owner. But if user A collects a project owned by user B, it is stored in $HOME of user A.

This Bug might need no fix if the behaviour descrbed in Bug #30139 is changed.
Comment 1 Alexander Kläser univentionstaff 2013-05-03 12:23:01 CEST
(In reply to comment #0)
> ...
> This Bug might need no fix if the behaviour described in Bug #30139 is changed.

Should be Bug 30319 instead.
Comment 2 Florian Best univentionstaff 2017-06-28 14:56:55 CEST
There is a Customer ID set so I set the flag "School Customer affected".
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:27:17 CET
This issue has been filled against UCS@school 3.2. The maintenance with
bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.