apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1576536/+attachment/4651032/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1576536/+attachment/4651031/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1576536/+attachment/4651033/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1576536/+attachment/4651030/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1576536/+attachment/4651029/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1576536/+attachment/4651026/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bug
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1576536/+attachment/4651028/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://b
Hello LaMont, or anyone else affected,
Accepted sudo into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sudo/1.8.16-0ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Timo, or anyone else affected,
Accepted libdrm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.67-1ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Timo, or anyone else affected,
Accepted libdrm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.67-1ubuntu0.14.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Dan, or anyone else affected,
Accepted init-system-helpers into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/init-
system-helpers/1.29ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pack
Hello Shinjan, or anyone else affected,
Accepted network-manager into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.2.0-0ubuntu0.16.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this n
Hello Brad, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
Hello Martin, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.
** Changed in: apt (Ubuntu Xenial)
Status: New => In Progress
** Changed in: apt (Ubuntu Xenial)
Assignee: (unassigned) => Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
*** This bug is a duplicate of bug 1581535 ***
https://bugs.launchpad.net/bugs/1581535
** This bug has been marked a duplicate of bug 1581535
libnl upgrade breaks Network Manager
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
Downgrading libnl3 should no longer be required for people working
around this. Upgrading to the latest version in trusty-updates should
get them a working version again.
Alternately, upgrading network-manager should also work, and should work
with the libnl3 in trusty-proposed.
--
You received
*** This bug is a duplicate of bug 1511735 ***
https://bugs.launchpad.net/bugs/1511735
** This bug has been marked a duplicate of bug 1511735
libnl: fail to bind() netlink sockets
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
*** This bug is a duplicate of bug 1511735 ***
https://bugs.launchpad.net/bugs/1511735
** This bug has been marked a duplicate of bug 1511735
libnl: fail to bind() netlink sockets
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
For what it's worth, I reverted libnl3 to a known good state in trusty-
updates (so it's safe to upgrade without concern), and staged a
corrected version with Breaks in trusty-proposed.
** Changed in: libnl3 (Ubuntu Trusty)
Assignee: Ryan Harper (raharper) => Adam Conrad (adcon
*** This bug is a duplicate of bug 1511735 ***
https://bugs.launchpad.net/bugs/1511735
The crash dump clearly shows this has the upgraded libnl:
libnl-3-200 3.2.21-1ubuntu1
libnl-genl-3-200 3.2.21-1ubuntu1
libnl-route-3-200 3.2.21-1ubuntu1
Please upgrade again to pull in the newer libnl a
FWIW, despite the lateness in the cycle, I'm 100% supportive of moving
the HUD away from Alt. That was (as has been pointed out) a pretty poor
decision from the get-go, and it's the one key I've always had to remap
locally to fix.
What I'm not okay with is fixing ONE bad binding by moving TWO. A
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-de in
Ubuntu.
https://bugs.launchpad.net/bugs/1559646
Title:
Separating languages into more packages
** Changed in: python-setuptools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/bugs/1570587
Title:
[FFe] Please
Hello Dawid, or anyone else affected,
Accepted apt into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.10.2ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu
Hello Dawid, or anyone else affected,
Accepted apt into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.13 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
To expand on the verification-failed tag added above: This change breaks
debootstrap and, thus, d-i and image builds.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1572752
The verification of the Stable Release Update for llvm-toolchain-3.8 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
)
Status: New => Fix Released
** Changed in: hunspell-sv (Ubuntu)
Assignee: (unassigned) => Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hunspell-sv in Ubuntu.
https://bugs.launchp
Hello Jim, or anyone else affected,
Accepted klibc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu1.16.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Jim, or anyone else affected,
Accepted klibc into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/klibc/2.0.3-0ubuntu1.14.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Jim, or anyone else affected,
Accepted klibc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/klibc/2.0.3-0ubuntu1.15.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
This is a bug in either (or both) llvmpipe/qemu. Booting with a -cpu
that is slightly less broken than the qemu emulated CPU (ie: -cpu host
or -cpu core2duo) works around the issue.
** Package changed: lightdm (Ubuntu) => llvm-toolchain-3.6 (Ubuntu)
** Also affects: qemu (Ubuntu)
Importance:
So, this is definitely solved by swapping in the util-linux fdisk, just
tested locally. Will upload SRUs that sort out that takeover for trusty
and vivid. wily should be fine already.
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: util-linux (U
Verified that upgrading both packages causes util-linux to take over
/sbin/fdisk, which behaves a little better. Of course, fdisk in trusty
doesn't support GPT, so it's still sort of half useless, but that's true
on all architectures, and at least it tells you to use parted. :)
** Tags removed: v
The verification of the Stable Release Update for mac-fdisk has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1471213
Title:
[SKL] noise in unity dash, torcs
Status
** Changed in: tzdata (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1453545
Title:
Unit displayed (kB/MB) when downloading updates
** Also affects: tzdata (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: tzdata (Ubuntu)
Status
Changing the dbus triggers to interest-noawait before upgrade fixes
this, but now I need to sort out how to do that in the past. :P
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs
** Package changed: apt (Ubuntu) => dbus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1485970
Title:
apt-get dist-upgrade falied with a dbus trigger loop due to an
While I agree that the precise behaviour was probably slightly more
intuitive, I don't think coreutils is a place we want to diverge from
upstream. While you might argue that people who relied on the precise
behaviour in local scripts need to fix their scripts on upgrade to
trusty (true), I could
** Also affects: ntp (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
Public bug reported:
Since some time in vivid, apt's terminal handling changed to where (I
assume) it's now passing a controlling terminal to dpkg which, in turn,
means dpkg prints progress info when it didn't used to. This leads to
log explosion with:
(Reading database ...
(Reading database ..
Adding an ubuntu-cdimage task to make it support double-signing, so I
can go back and alter history.
** Also affects: ubuntu-cdimage
Importance: Undecided
Status: New
** Changed in: ubuntu-cdimage
Assignee: (unassigned) => Adam Conrad (adconrad)
--
You received this
** Tags removed: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
[SRU] segfault in log.c code causes phone reboot loops
Status in Canoni
Hello cliff, or anyone else affected,
Accepted apt into precise-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apt/0.8.16~exp12ubuntu10.25 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Public bug reported:
objcopy segfaults in precise when running the sbsigntool testsuite on
i386 with binutils >= 2.22-6ubuntu1.2
See the attachment for output and downgrade iterations to show that 1.1
works, while 1.2 and 1.3 don't.
** Affects: binutils (Ubuntu)
Importance: Undecided
Hello Andy, or anyone else affected,
Accepted iproute2 into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/iproute2/3.16.0-2ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
** Changed in: linux (Ubuntu Trusty)
Status: Invalid => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1470091
Title:
update for V3 kernel bits and impro
** Changed in: linux-lts-vivid (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-vivid (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: iproute2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ubuntu-fan (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-lts-vivid (Ubunt
** Also affects: linux-lts-utopic (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-lts-utopic (Ubuntu Vivid)
Status: New => Invalid
** Changed in: linux-lts-utopic (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux (Ubuntu Trusty)
Status: Won'
Hello Andy, or anyone else affected,
Accepted iproute2 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/3.12.0-2ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Andy, or anyone else affected,
Accepted ubuntu-fan into vivid-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubuntu-
fan/0.3.0~15.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Andy, or anyone else affected,
Accepted ubuntu-fan into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubuntu-
fan/0.3.0~14.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
The verification of the Stable Release Update for apt has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regr
Building trusty daily desktop ISOs with the new python3.4 causes
ubiquity to fail to start. I've saved two ISOs where the only delta is
the python version to show the issue:
http://people.canonical.com/~adconrad/lp1348954/
In the above directory, 20150728 is broken, while 20150728.1 works.
** T
Hello Matthias, or anyone else affected,
Accepted python3.4 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.4/3.4.3-1ubuntu1~14.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Matthias, or anyone else affected,
Accepted python3.4 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.4/3.4.3-1ubuntu1~14.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Matthias, or anyone else affected,
Accepted mysql-5.6 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mysql-5.6/5.6.19-0ubuntu0.14.04.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
The verification of the Stable Release Update for iproute2 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for dh-python has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
** Changed in: apt (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1429041
Title:
Autoremoval not working reliably
Status in ap
Public bug reported:
In current trusty, vivid, and wily, when you install ubuntu-minimal
(from the "metapackages" section) in a clean chroot, some 75ish packages
are installed. If you then "apt-get --purge autoremove ubuntu-minimal",
some large portion (between 20 and 40, depending on the target
Ah-ha, thanks for that pointer, David. We are, indeed, carrying that
broken patch, and I can infer from Raphaël's overreaching patch (and
followup discussion) what you're more likely to do as a conservative
stable update. So, if you don't get around to said stable update, I'll
cook up some SRUs f
The ubiquity cherry-pick resolved the issue mentioned in comment #18
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1348954
Title:
update Python3 for trusty
Stat
Looks like mesa should be pulling this in, if it's going to try loading
it unconditionally and explode when it can't. In vivid, we don't have
this problem, as a variety of low level libs (like gtk and sdl) link to
libwayland-egl directly, thus accidentally papering over the fact that
mesa itself d
Hello Jean-Baptiste, or anyone else affected,
Accepted apport into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.17.2-0ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
** Changed in: mesa-lts-vivid (Ubuntu Trusty)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu Vivid)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu Wily)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You recei
Okay, based on the conversation in the Debian bug, I have a patch that
fixes this regression, and doesn't regress the previous fix. SRUing to
trusty to fix my point release, and will cover the other releases and
maybe even write test cases for the testsuite when things calm down a
tiny bit.
--
Y
on the autoremoval list.
** Changed in: apt (Ubuntu Trusty)
Assignee: Michael Vogt (mvo) => Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1479207
-rootfs (Ubuntu Vivid)
Status: New => Invalid
** Changed in: livecd-rootfs (Ubuntu Wily)
Status: New => Invalid
** Changed in: livecd-rootfs (Ubuntu Trusty)
Milestone: None => ubuntu-14.04.3
** Changed in: livecd-rootfs (Ubuntu Trusty)
Assignee: (unassigned)
The verification of the Stable Release Update for livecd-rootfs has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encou
The verification of the Stable Release Update for gtk+3.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I'm incorrectly abusing the "verification-failed" tag on this for now,
as I don't think this has had enough testing for us to promote it next
week and land it only days before the 14.04.3 final ISOs are released.
After 14.04.3, people who've done sufficient testing and feel this is
ready can feel f
Next three comments are regression testing that the fix from #1429041
hasn't regressed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1479207
Title:
Never-MarkAuto-Sections n
(trusty-amd64)root@nosferatu:/home/adconrad/apt-test# dpkg -l apt apt-utils
libapt-inst1.5 libapt-pkg4.12 | awk '/^.i/ {print $2 "" $3}'
apt1.0.1ubuntu2.8
apt-utils1.0.1ubuntu2.8
libapt-inst1.5:amd641.0.1ubuntu2.8
libapt-pkg4.12:amd641.0.1ubuntu2.8
(trusty-amd64)root@nosferatu:
(trusty-amd64)root@nosferatu:/home/adconrad/apt-test# dpkg -l apt apt-utils
libapt-inst1.5 libapt-pkg4.12 | awk '/^.i/ {print $2 "" $3}'
apt1.0.1ubuntu2.8
apt-utils1.0.1ubuntu2.8
libapt-inst1.5:amd641.0.1ubuntu2.8
libapt-pkg4.12:amd641.0.1ubuntu2.8
(trusty-amd64)root@nosferatu:
Erm, and noticed my testing for bug #1429041 removed the wrong package
on the "-notbroken" pass. Redid it on all three versions with removing
meta instead of kernel, and it did correctly remove both packages, as
expected.
--
You received this bug notification because you are a member of Ubuntu
T
And the next three comments are regression testing for this current bug:
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1479207
Title:
Never-MarkAuto-Sections not working corr
(trusty-amd64)root@nosferatu:/home/adconrad/apt-test# dpkg -l apt apt-utils
libapt-inst1.5 libapt-pkg4.12 | awk '/^.i/ {print $2 "" $3}'
apt1.0.1ubuntu2.9
apt-utils1.0.1ubuntu2.9
libapt-inst1.5:amd641.0.1ubuntu2.9
libapt-pkg4.12:amd641.0.1ubuntu2.9
(trusty-amd64)root@nosferatu:
(trusty-amd64)root@nosferatu:/home/adconrad/apt-test# dpkg -l apt apt-utils
libapt-inst1.5 libapt-pkg4.12 | awk '/^.i/ {print $2 "" $3}'
apt1.0.1ubuntu2
apt-utils1.0.1ubuntu2
libapt-inst1.5:amd641.0.1ubuntu2
libapt-pkg4.12:amd641.0.1ubuntu2
(trusty-amd64)root@nosferatu:/home/ad
(trusty-amd64)root@nosferatu:/home/adconrad/apt-test# dpkg -l apt apt-utils
libapt-inst1.5 libapt-pkg4.12 | awk '/^.i/ {print $2 "" $3}'
apt1.0.1ubuntu2
apt-utils1.0.1ubuntu2
libapt-inst1.5:amd641.0.1ubuntu2
libapt-pkg4.12:amd641.0.1ubuntu2
(trusty-amd64)root@nosferatu:/home/ad
(trusty-amd64)root@nosferatu:/home/adconrad/apt-test# dpkg -l apt apt-utils
libapt-inst1.5 libapt-pkg4.12 | awk '/^.i/ {print $2 "" $3}'
apt1.0.1ubuntu2.9
apt-utils1.0.1ubuntu2.9
libapt-inst1.5:amd641.0.1ubuntu2.9
libapt-pkg4.12:amd641.0.1ubuntu2.9
(trusty-amd64)root@nosferatu:
For the record, it's really not recommended to run -proposed on a
development series. -proposed is pretty much guaranteed to be
inconsistent and broken at all times.
** Package changed: apt (Ubuntu) => apport (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touc
*** This bug is a duplicate of bug 1445239 ***
https://bugs.launchpad.net/bugs/1445239
** This bug has been marked a duplicate of bug 1445239
apt's lists/partial fills disk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Marking verification-done based on comments 31 and 35.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/14452
The verification of the Stable Release Update for apt has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regr
virtualbox from the Ubuntu archive for trusty has no dependency on
linux-headers. You're using a non-Ubuntu package, as can be seen from
your apt log above.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch s
This usually happens because your input buffer fed some garbage to apt
before the 'y'. Perhaps you accidentally hit twice on the
command, or a space, or any other random key, really. It's hard to say
exactly how or why, without having been there, but it aborts when it
can't parse the input (whic
This isn't a bug, unless your complaint is that the libgtk-*-bin
postinsts are overly verbose, in which case, reopen and reassign to
gtk+3.0.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Package changed: apt (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bu
The "leaves conffiles behind" complaint is entirely unrelated, and
solved by using "apt-get --purge autoremove"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1446269
Title:
a
As for the "single kernel" complaint, I'm a bit confused by your
description, since that shows three kernels installed, not one. I am
aware of situations on can get into that lead to only one kernel
installed, but I'm not sure you're describing a scenario I know of.
--
You received this bug not
*** This bug is a duplicate of bug 1445239 ***
https://bugs.launchpad.net/bugs/1445239
** This bug has been marked a duplicate of bug 1445239
apt's lists/partial fills disk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
[ SRU Justification ]
This is a regression caused by the previous SRU where, under some corner cases,
apt will segfault. See test case.
[ (Convoluted) Test Case ]
In a clean trusty chroot:
# apt-get update && apt-get dist-upgrade
# apt-get install xserver-xorg-lts-utopic li
y time we touch this line of
code, and we've done it 4 times now.
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu)
Status: New => Invalid
** Changed in: apt (Ubuntu Trusty)
Assignee: (unassigned) => Adam Conra
Regression test for bug #1480592 passed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1480592
Title:
SEGV in rare cases as a regression from the #1479207 fix
Status in apt
601 - 700 of 729 matches
Mail list logo
