root@f:~# apt-cache policy libgps-dev gpsd
libgps-dev:
Installed: (none)
Candidate: 3.20-3
Version table:
3.20-3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
gpsd:
Installed: (none)
Candidate: 3.20-3
Version table:
3.20-3 500
500
This had too many dependencies yesterday.
But when I was looking for that today I found that Steve already added
commit 7193ff159faf338718240e3fb9c0ae90d91d3624
Author: Steve Langasek
Exclude gpsd-dbg along with libqgpsmm-dev to keep Qt out of main
- * Extra-Exclude: libqgpsmm-dev
+ *
On 2020-01-10 08:18, Christian Ehrhardt wrote:
> Great, thanks Alex.
> This is ready from MIR+Security POV now.
> => Set in progress according to our state chart
>
> The latest version is in Focal already:
> gpsd | 3.20-1 | focal/universe | source, amd64, arm64,
> armhf, ppc64el,
Great, thanks Alex.
This is ready from MIR+Security POV now.
=> Set in progress according to our state chart
The latest version is in Focal already:
gpsd | 3.20-1 | focal/universe | source, amd64, arm64, armhf,
ppc64el, s390x
=> There will be no change in e.g. chrony required to
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/377415
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790855
Title:
[MIR] gpsd
To manage
** Changed in: gpsd (Ubuntu)
Status: Triaged => 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/1790855
Title:
[MIR] gpsd
To manage notifications about this bug go to:
I reviewed gpsd 3.20-1 as checked into focal. This shouldn't be considered
a full audit but rather a quick gauge of maintainability. As noted in the
MIR description, this review only covers code and binaries which are
contained in the gpsd and libgps25 packages.
gpsd is a daemon (and associated
** Attachment added: "gpsd-coverity-scan-results"
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1790855/+attachment/5319032/+files/coverity.txt
** Changed in: gpsd (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification
FYI - server team now is already subscribed to this, that way we see
ahead of time how much traffic is on this package and we can't forget it
later on :-) Thanks Josh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I helped to get the lib transition done and 3.19-3 is not only on
proposed but in focal-release for real.
@Security - this was in your queues already, but now it is all yours -
no other known todo left except sec-review and then seeding+promotion.
--
You received this bug notification because
** Changed in: gpsd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790855
Title:
[MIR] gpsd
To manage notifications about this bug go to:
3.19-2 is now in Debian/unstable and will soon sync to Ubuntu.
That means the changes in 3.18 to resolve the packaging issues are in too.
Thanks Bernd for all the work.
In addition 3.19 has an apparmor profile and while 3.18 added py3 3.19
now dropped py2 which makes this a clear MIR ack now.
It
** Attachment added: "Coverity results"
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1790855/+attachment/5270648/+files/coverity.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790855
While I'll continue to work with Bernd to get the newer GPSD in (post
Buster) which will make it qualify for MAIN inclusion I wanted to share
that I just realized that it was already in main in precise - I thought
it is worth to share that nugget of information.
--
You received this bug
Over the last years, the gpsd upstream usually did a very good job on
ABI/API changes. This time its ... sad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790855
Title:
[MIR] gpsd
To manage
I've subscribed Eric S. Raymond on this bug so he can see whats going
on...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790855
Title:
[MIR] gpsd
To manage notifications about this bug go to:
I further found potential changes that need adaptations in:
- Savannah issue #53671: policy_t -> gps_policy_t. [7]
- ATT: centralize clearing of the attitude data. [8]
[7]:
https://git.savannah.gnu.org/cgit/gpsd.git/commit/?id=25edf0e836200ee4f6cf86fa4456635ee210484f
[8]:
Yeah I formerly checked only libgps.h, but the list is somewhat bigger
but still seems manageable:
API:
7.0 - add gps_fix_t.ecef (February 2018) [3]
changed prototype of gps_read() to add buffer parameters [1]
increased length of devconfig_t.subtype [2]
add gnssid:svid:sigid to
Wow, that diff is really gross. (And the "bump on incompatible changes"
define is even sitting there in the context.) Are we sure this is the
best tool for the job?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I didn't realize (or I forgot over Christmas?) that was the reason to make the
transition harder than usual :-/
Thanks for the Info Bernd!
Maybe I can make that part of my mission on the bug squashing party, too
late for a migration but since we want to resolve it sooner or later.
The main
Actually I do not want to wait, but given the fact that most reverse
dependencies do not build due to an undocumented API/ABI change, I just did not
have the time to figure out what the correct way to fix this for each reverse
dependency is.
The new main gpsd upstream developer was not willing
Hi,
all packaging quality issues are adressed in 3.18.1-1 which is in Debian
experimental.
The maintainer wants to wait to do the transition until Buster is released.
But we could continue our evaluation here.
1. I'd ask to re-evaluate the package at version 3.18.1-1
That has fixed all
Hi Alex, it was NAK'd from packaging issues.
Those are already split in the Debian repository [1][2] and only wait for an
upload to happen.
Since we knew this would resolve the security Team is assigned to do the
review already, so that we are ready when the packaging changes make
their way into
@cyphermox - this is assigned to the security team for security review
but is still marked Incomplete from your questions earlier - plus looks
like you also NAK'd it above - is this now ACK'd from your side or is it
still blocked - and hence should I un-assign it from the security team?
--
You
** Description changed:
FYI: We want to only seed the two binary packages:
- gpsd
- libgpsd23
But none of the others (further bindings, tools, ...)
- They will stay "only" a suggest from Chrony, so the seeding will pull them
into Main.
+ They will stay "only" a suggest from Chrony, but
That isn't necessary. You should just be clear that you just want to
seed it in the 'supported' seed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790855
Title:
[MIR] gpsd
To manage
On Tue, Oct 23, 2018 at 5:02 PM Mathieu Trudel-Lapierre <
mathieu...@gmail.com> wrote:
> You misunderstand, I think. Why put it in main at all, if you're not
> going to be installing it by default? There's just about no use; it's
> still only Suggested to install. People can install it from
You misunderstand, I think. Why put it in main at all, if you're not
going to be installing it by default? There's just about no use; it's
still only Suggested to install. People can install it from universe
when they want a hardware time source.
--
You received this bug notification because you
** Description changed:
+ FYI: We want to only seed binary packages:
+ - gpsd
+ - libgpsd23
+ But none of the others (further bindings, tools, ...)
+ They will stay "only" a suggest from Chrony, so the seeding will pull them
into Main.
+
Availability: GPSD is available since quite a while and
Hi,
I wanted to give an update on the current status.
First of all thanks Mathieu for the reivew.
1. Dependeny:
Yes we are only suggesting from chrony and don't "need" it in main for that (we
do not intent to depend/recommened there). Instead we want to seed gpsd to be
in main (no default
** Changed in: gpsd (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: gpsd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gpsd (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790855
Title:
[MIR] gpsd
To manage notifications
+1 for server team ownership of gpsd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790855
Title:
[MIR] gpsd
To manage notifications about this bug go to:
33 matches
Mail list logo
