[Bug 1343656] Re: Unable to install crossbuild-essential-powerpc on x86_64 (amd64)
Okay, it didn't let me make that change, instead informing me that build-essential is the source package for crossbuild-essential-powerpc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1343656 Title: Unable to install crossbuild-essential-powerpc on x86_64 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1343656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1343656] Re: Unable to install crossbuild-essential-powerpc on x86_64 (amd64)
Changed defaulted package from build-essential to crossbuild-essential- powerpc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1343656 Title: Unable to install crossbuild-essential-powerpc on x86_64 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1343656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1343656] [NEW] Unable to install crossbuild-essential-powerpc on x86_64 (amd64)
Public bug reported: The Ubuntu 14.04LTS 64-bit is installed within a brand-new VM (using VirtualBox 4.3.12). The host machine and the VM are both x86_64 (amd64). I would like to get a powerpc-linux-gnu cross-toolchain up and running, and noticed that Ubuntu had a specific package for this. First, I executed "sudo apt-get install build-essential". Second, I executed "sudo dpkg --add-architecture powerpc". Third, I executed "sudo apt-get install crossbuild-essential-powerpc". I expected the third command to succeed. Instead, it failed while providing the following output: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: crossbuild-essential-powerpc : Depends: libc6-dev:powerpc but it is not installable E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: crossbuild-essential-powerpc (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Thu Jul 17 13:53:14 2014 InstallationDate: Installed on 2014-07-17 (0 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: build-essential UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: build-essential (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 crossbuild powerpc trusty x86-64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1343656 Title: Unable to install crossbuild-essential-powerpc on x86_64 (amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1343656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550023] Re: first boot after installation of lucid beta 1 from dvd iso fails when using encryption
The problem reported above was not particular to the dvd iso. Also, I have since found the daily snapshot iso files at cdimage.ubuntu.com. I have just installed the 20100401 amd64 server cd iso using the guided encryption+lvm option, with grub 1 (legacy). I am able to normally boot using this installation setup. I suspect that the fixing of https://bugs.launchpad.net/bugs/527666 is the reason that the boot process now succeeds. -- first boot after installation of lucid beta 1 from dvd iso fails when using encryption https://bugs.launchpad.net/bugs/550023 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550023] Re: first boot after installation of lucid beta 1 from dvd iso fails when using encryption
In the past I have set up a Karmic machine that used text only, and by specifying "bootwait" (or something like that) into /etc/fstab I was able to get a chance to enter multiple encrypted partition passphrases and to boot properly. Can I somehow instruct the installer to not use plymouth and xsplash, to just ask for passphrases in plain text on the console? I do recall there were other problems with entering multiple passphrases (e.g., keyboard input stealing by other processes), but the current situation is even worse. If there's something I can download as an .iso that is newer than beta 1, I'd appreciate a link to that also. -- first boot after installation of lucid beta 1 from dvd iso fails when using encryption https://bugs.launchpad.net/bugs/550023 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550023] [NEW] first boot after installation of lucid beta 1 from dvd iso fails when using encryption
Public bug reported:
Attempted amd64 lucid beta 1 install from dvd iso using two drives,
encryption, and lvm with two volume groups. The first time, I tried to
use encryption on both drives, and created lvm volume groups on top of
each encrypted partition. When I booted, I got the ubuntu logo screen
(even if I booted grub with nosplash!) and was prompted for the
passphrase to /dev/sda2 (/dev/sda1 = /boot). /dev/sda2's password is
accepted, and all normal system directories were on /dev/sda2, but
/dev/sdb1's was also encrypted and I got an [SM] prompt about it, No
matter whether I tried to type ('s', 'm', 'S', 'M', or the passphrase
for /dev/sdb1) I get nowhere -- the machine never fully boots.
So, I reinstalled and this time I did not encrypt the first drive, just
the second drive. I still used lvm in the same way. This time it goes
immediately to the [SM] prompt and I am again stuck no matter my
response.
I expected the system to fully boot so that I would reach a command prompt
(basic server install).
I also expected to not see the graphical ubuntu logo when I edited the grub
entry (interactively) to nosplash instead of splash.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: lucid
--
first boot after installation of lucid beta 1 from dvd iso fails when using
encryption
https://bugs.launchpad.net/bugs/550023
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515274] Re: [FFE] Latest Stable is 5.0.1
i386 proved to be unreliable; couldn't even complete the lucid install. Now have built an amd64 system, but am using full-disk encryption and cannot even boot the system to the point where I can attempt to install Chuck Short's PPA. Still trying... -- [FFE] Latest Stable is 5.0.1 https://bugs.launchpad.net/bugs/515274 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212075] Re: [hardy beta] encrypting partitions at installation should allow for single passphrase to unlock all
This is still a problem even through Karmic (9.10) and Lucid (10.04) beta 1: in various situations, input is eaten, or prompts for decryption of a second device are never received. -- [hardy beta] encrypting partitions at installation should allow for single passphrase to unlock all https://bugs.launchpad.net/bugs/212075 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545005] [NEW] rescue feature on lucid beta 1 alternate CD fails to find raid1 device that uses 1.02 metadata format
Public bug reported: I have two raid1 drive pairs, two of which comprise /dev/md0 and two of which comprise /dev/md/hitachi2Tb (sometimes with a third-party system rescue CD such as SystemRescueCD 1.5.0, the second raid1shows up as /dev/md1 or /dev/md127). The lucid-beta-1 alternate i386 CD's rescue feature detects the first raid1 (md0) and logical volumes present on md0 are shown as options for selecting as a root filesystem. However, the second raid1 device is not found and no logical volumes on it are available for selection as a root filesystem. I expected to see both and to be able to choose a root volume from either raid set. Further, when I unplugged the two md0 drives from the computer, the rescue feature was unable to see the single valid raid1 present, so it's not a case of simply not looking for more than one of them. Going to the command line and typing mdadm --assemble --scan yielded an error about how the raid1 set that wasn't automatically made available couldn't be loaded by default because /dev/md/hitachi2Tb did not exist. I went and made this file, then mdadm --assemble --scan did successfully find the raid. However, at this point when I exited the console to go and select which device to use as root, the list did not now expand to include any lvm logical volumes on the raid device that I had just mounted, so I was unable to attempt to try to repair my non-booting system in this fashion (and I am stuck). ** Affects: ubuntu Importance: Undecided Status: New ** Tags: alternate lvm metadata name raid rescue -- rescue feature on lucid beta 1 alternate CD fails to find raid1 device that uses 1.02 metadata format https://bugs.launchpad.net/bugs/545005 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515274] Re: [FFE] Latest Stable is 5.0.1
I haven't attempted to participate in testing a pre-release Ubuntu package before, so please bear with me. I'd very much like to see Bacula 5.0.x make it into Lucid. I have reformatted a machine with Lucid Alpha 3 to install Chuck Short's test package onto. This machine is i386 rather than amd64, though. When I looked earlier, I thought I only saw amd64 supported by his PPA build, but when I looked just now it seems like i386 support is also there? In any case, I will definitely give the Bacula 5 test package a try this weekend, so if there's not already i386 support, could someone please make whatever changes are necessary to add it in the next day or so? -- [FFE] Latest Stable is 5.0.1 https://bugs.launchpad.net/bugs/515274 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 426778] Re: Please upgrade calendarserver to version 2.3 from upstream
As part of the responses for bug 403349 (https://bugs.launchpad.net/ubuntu/+source/calendarserver/+bug/403349), Alex Dean gave a URL http://www.deanspot.org/content/installing-darwin- calendar-server-23-ubuntu-910 that points to his post on his workaround to get CalendarServer working under 9.10 (Karmic). I haven't (yet) tried his instructions myself. -- Please upgrade calendarserver to version 2.3 from upstream https://bugs.launchpad.net/bugs/426778 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182572] Re: Samba Fails to Split GECOS on Comma
I attempted to use the prescribed workaround (editing /etc/passwd to remove the ,,, after the name), but this did not work for me. I don't see any change (I still get "User Name,,," in the Start Menu under Windows XP. -- Samba Fails to Split GECOS on Comma https://bugs.launchpad.net/bugs/182572 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182572] Re: Samba Fails to Split GECOS on Comma
I wouldn't want to cause a worse problem than the annoyance I'd be solving. Would editing /etc/passwd to remove the three commas be an effective workaround for this problem? If not, what would be an effective workaround? -- Samba Fails to Split GECOS on Comma https://bugs.launchpad.net/bugs/182572 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500929] [NEW] console output during gcc-4.4-doc installation indicates a problem
Public bug reported:
Binary package hint: gcc-4.4-doc
I am using Karmic Koala (9.10), fully updated/upgraded.
During installation of the documentation package, the following output
is emitted:
Setting up gcc-4.4-doc (4.4.1-4ubuntu8) ...
Ignoring install-info called from maintainer script
The package gcc-4.4-doc should be rebuild with new debhelper to get trigger
support
Ignoring install-info called from maintainer script
The package gcc-4.4-doc should be rebuild with new debhelper to get trigger
support
Ignoring install-info called from maintainer script
The package gcc-4.4-doc should be rebuild with new debhelper to get trigger
support
There is also a language usage bug in the error message ("rebuild"
should be "rebuilt"), but the main issue is whatever is going on with
install-info.
P.S. I also observed similar behaviour when installing gcc-doc (two such
errors) and when installing diff-doc (one such error).
ProblemType: Bug
Architecture: amd64
Date: Sun Dec 27 19:05:31 2009
Dependencies: gcc-4.4-base 4.4.1-4ubuntu8
DistroRelease: Ubuntu 9.10
Package: gcc-4.4-doc 4.4.1-4ubuntu8
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: gcc-4.4
Uname: Linux 2.6.31-16-generic x86_64
** Affects: gcc-4.4 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug
--
console output during gcc-4.4-doc installation indicates a problem
https://bugs.launchpad.net/bugs/500929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182591] Re: [needs-packaging] Calendar Server
This package appears to exist in a broken form in Karmic, but is not installable because of a version more than 1.5 years old (version 1.2) that is currently bundled depends upon the python-xml package that was dropped after the Jaunty release: https://bugs.launchpad.net/ubuntu/+source/calendarserver/+bug/403349 There is another bug report requesting an upgrade from the ancient version bundled to the current release, 2.3. That would avoid the dependency upon python-xml: https://bugs.launchpad.net/debian/+source/calendarserver/+bug/426778 There is a package that exists, so that's an argument for closing out this bug, but because the package is more or less useless, it might be better to keep it open. -- [needs-packaging] Calendar Server https://bugs.launchpad.net/bugs/182591 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 426778] Re: Please upgrade calendarserver to version 2.3 from upstream
I should have mentioned that resolving this bug will also resolve #403349: https://bugs.launchpad.net/ubuntu/+source/calendarserver/+bug/403349 The current version of calendarserver, 1.2, cannot even be installed via apt on Karmic. -- Please upgrade calendarserver to version 2.3 from upstream https://bugs.launchpad.net/bugs/426778 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 426778] Re: Please upgrade calendarserver to version 2.3 from upstream
+1: AFAIK, DCS is the closest thing we have to a CalDAV server in Ubuntu. Bump!! -- Please upgrade calendarserver to version 2.3 from upstream https://bugs.launchpad.net/bugs/426778 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
