Bug 29004 - ucc-image-toolkit: partner-Repository kann nicht eingebunden werden
ucc-image-toolkit: partner-Repository kann nicht eingebunden werden
Status: CLOSED DUPLICATE of bug 30035
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Image management
unspecified
Other Linux
: P5 normal
: ---
Assigned To: UCC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-31 16:06 CET by Moritz Muehlenhoff
Modified: 2023-06-28 10:33 CEST (History)
1 user (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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2012-10-31 16:06:53 CET
Setze ich 

partner: true

in der Konfigurationsdatei, dann erscheint folgende Fehlermeldung:

Get:47 http://ubuntu.knut.univention.de precise-backports/universe Translation-en [11.3 kB]
Fetched 7060 kB in 4s (1635 kB/s)
W: Failed to fetch http://ubuntu.knut.univention.de/ubuntu/dists/precise/Release  Unable to find expected entry 'partner/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.
warning: failed to read mtab
umount: /proc: not mounted
Started "/usr/sbin/ucc-image -c jmm.cfg" at 2012-10-31 04:03:05
Traceback (most recent call last):
  File "/usr/sbin/ucc-image", line 256, in <module>
    _run_cmd(cmd_block, logfile_fd)
  File "/usr/sbin/ucc-image", line 56, in _run_cmd
    raise RuntimeError(msg)
RuntimeError: The command "/usr/sbin/chroot /tmp/tmpes0F4D/bootstrap apt-get update" failed with the error code 100
Comment 1 Stefan Gohmann univentionstaff 2013-04-11 06:46:35 CEST

*** This bug has been marked as a duplicate of bug 30035 ***