Public bug reported:
For the same reasons as
https://bugs.launchpad.net/ubuntu/+source/bitcoin/+bug/1260602:
As explained in https://lists.ubuntu.com/archives/ubuntu-
release/2013-December/002675.html, the bitcoin package is not
supportable in a stable release because it requires arbitrary
Public bug reported:
See the mailing list discussions at https://lists.ubuntu.com/archives
/ubuntu-motu/2013-December/thread.html and
https://lists.ubuntu.com/archives/ubuntu-motu/2014-April/thread.html.
In short: old versions of Bitcoin Core (as it is now known) are broken,
not up to date on
What about 12.10? I know it EOLed a couple days ago, but 13.04 EOLed even
earlier, from what I understand, if I'm not mistaken...
On Monday, May 19, 2014, Scott Howard showard...@ubuntu.com wrote:
Following need to be done, I'll work on it
precise (12.04LTS) (utils): peer-to-peer network
Public bug reported:
Fresh install from the 12.04.5 desktop amd64 iso and then an
installation of updates through the GUI. After a reboot, clicked the
circuit board thing in the status bar, said yes, and then it failed.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package:
Confirmed that upon installation from -proposed bitcoind is not
installed, but rather, the error message is displayed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
(version installed was 0.3.24~dfsg-1ubuntu0.2 -- forgot that in my
previous comment)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314616
Title:
[SRU] bitcoin to be maintained upstream in PPA:
** Changed in: bitcoin (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314616
Title:
[SRU] bitcoin to be maintained upstream in PPA: Replace distro archive
*** This bug is a security vulnerability ***
Public security bug reported:
It doesn't really make sense that when using debootstrap to create an
Ubuntu chroot|container|directory|installation|whatever, old versions
of packages will be installed, rather than the latest versions from the
archives.
The attack scenario is as follows:
1. A user creates a new Ubuntu installation with debootstrap.
2. The user assumes that, because they're fetching all the packages online
from the server, they're getting the latest versions and don't need to
upgrade immediately.
3. The user is attacked via
Public bug reported:
During do-release-upgrade from 16.04 to 17.10.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1.2
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture:
** Patch added: "The patch linked for 1.10.2"
https://bugs.launchpad.net/ubuntu/+source/megatools/+bug/1872819/+attachment/5372944/+files/debian_patches_support-new-links_1.10.2.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: "The linked patch for 1.9.98"
https://bugs.launchpad.net/ubuntu/+source/megatools/+bug/1872819/+attachment/5372945/+files/debian_patches_support-new-links_1.9.98.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872819
Title:
newer links cannot be downloaded
To manage notifications about this bug go to:
The process for adding packages to Main is slightly more complex - there’s a
template that should be used and certain details that need to be included, as
well as specific steps to take in order to cause the right people to see it and
advance the process. This wiki page has all the details:
** Summary changed:
- move libnvidia-egl-wayland1 package from universe into main
+ [MIR] egl-wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] egl-wayland
To manage
Am I misunderstanding the MIR process/flow? I would have expected a
status change to Incomplete and the assignment to remain as ddstreet
from a reading of that page.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: egl-wayland (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] egl-wayland
To manage notifications about this bug go
As I understand the process, what remains now is for the package to be
pulled into main by dependency - I’m not familiar with the structure of
the graphics driver source packages and all the various binary packages
they produce, but perhaps xserver-xorg-video-nvidia-470 or nvidia-
driver-470 would
Also, I see 470 is in bionic, focal, hirsute and impish - does this need
to get SRUed back to those as well to avoid the performance penalty? I’m
not clear on how MIRs and SRUs intersect, but besides the dependency
change that nvidia-graphics-drivers-470 needs, ISTM that focal and
hirsute would
Ah, I see, thanks for the clarification. Are you able to prepare an
upload that adds the dependency?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] egl-wayland
To manage
** Changed in: egl-wayland (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] egl-wayland
To manage notifications about this
21 matches
Mail list logo
