Public bug reported:
Found iPXE image is followed by a space, while other GRUB script
fragments are not. The attached patch fixes this, in addition to
packaging issues e.g. Lintian warnings.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: grub-ipxe (not installed)
ProcVersionSignature:
** Attachment added: Debdiff
https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/990378/+attachment/3111675/+files/ipxe_debdiff.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipxe in Ubuntu.
** Summary changed:
- grub-ipxe: updatte-grub script fragment's prompt inconsistent with other GRUS
scripts' format
+ grub-ipxe: update-grub fragment inconsistent with other GRUB scripts' format
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/907250
Title:
Please merge Debian into Precise - libkrb5-3: Breaks: libsmbclient (=
2:3.6.1-2)
To manage notifications about this bug
Public bug reported:
The libkrb5-3 that entered Precise today Breaks libsmbclient (=
2:3.6.1-2), which in turn breaks gvfs-backends. Fixing this requires
merging a newer Samba from Debian (Precise currently has 2:3.5.11~dfsg-
4ubuntu3).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package:
Subscribed Ubuntu Server Team as this is an issue that prevents remote
servicing of Lucid hosts.
--
apt-check hangs, preventing login via SSH
https://bugs.launchpad.net/bugs/525674
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
This problem has already been reported for at least some of the packages
involved.
The real issue is changes in the Linux kernel security model which, in
turn, require a slightly different syntax for AppArmor rules. Those
rules are not 100% compatible with those needed for 2.6.28 kernels used
** Changed in: dhcp3 (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
broken AppArmor profile
https://bugs.launchpad.net/bugs/414507
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Thierry, anything to add?
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in ubuntu.
--
Ubuntu-server-bugs mailing list
This issue is still present in Karmic alpha 4:
$ LC_ALL=C sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
lxde-settings-daemon
The following packages
$ LC_ALL=C date
Tue Aug 18 04:43:21 EEST 2009
$ LC_ALL=C lsb_release -d
Description:Ubuntu karmic (development branch)
$ LC_ALL=C apt-cache policy libsasl2-2
libsasl2-2:
Installed: 2.1.23.dfsg1-1ubuntu1
Candidate: 2.1.23.dfsg1-1ubuntu2
Version table:
2.1.23.dfsg1-1ubuntu2 0
Seems that the only way to succeed at upgrading these packages is to add
the following line to /etc/apt/apt.conf
APT::Immediate-Configure false;
Two observations:
Seems that the logic for this APT option was recently reverted, if
Google results for immediate-configure is any indication. Could
Thierry, the output already is attached above.
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in ubuntu.
--
Ubuntu-server-bugs
I utilize an APT front-end called 'upgrade-system' to perform my
upgrades.
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in ubuntu.
And if you look at the dependencies, libsasl2-modules and libsasl2-2
indeed depend upon one another, which creates a cycle.
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
Server Team,
Thank you for assigning this bug to someone. Is there any other info I
should provide?
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2
Kees, what do you use to perform the installation? Here, both APT and
aptitude fail as shown above, during an upgrade. This behavior is
verified on both Debian and Ubuntu, using APT and aptitude.
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You
...and still present in Karmic alpha 2.1.23.dfsg1-1ubuntu1. Could
someone please look into this? Thanks!
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This issue is *still* present in 2.1.22.dfsg1-23ubuntu3.1 (Jaunty).
Could someone please fix this before Karmic releases?
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
Server Team,
Now that Intrepid is finally released, I notice that the bug is still
present and yet it was reported 9 months ago. What's going on?
--
Dependency cycle prevents upgrade of libsasl2-2
https://bugs.launchpad.net/bugs/194140
You received this bug notification because you are a member of Ubuntu
20 matches
Mail list logo
