Page MenuHomePureOS Tracker

jonas.smedegaard (Jonas Smedegaard)
UserAdministrator

User Details

User Since
Jul 16 2017, 03:17 (198 w, 6 d)
Roles
Administrator

Recent Activity

Yesterday

jonas.smedegaard added projects to T1030: phosh: Vcs-Browse and Vcs-Git points to Debian: Restricted Project, Restricted Project.
Fri, May 7, 03:36 · Restricted Project, Restricted Project
jonas.smedegaard added projects to T1028: rust-xkbcommon: Vcs-Browser and Vcs-Git points to Debian: Restricted Project, Restricted Project.
Fri, May 7, 03:36 · Restricted Project, Restricted Project
jonas.smedegaard added a project to T1026: uefitool: Vcs-Browser and Vcs-Git not declared: Restricted Project.
Fri, May 7, 03:34 · Restricted Project
jonas.smedegaard added projects to T1025: util-linux: Vcs-Browse and Vcs-Git points to Debian: Restricted Project, Restricted Project.
Fri, May 7, 03:34 · Restricted Project, Restricted Project
jonas.smedegaard added projects to T1022: webkit2gtk: Vcs-Browse and Vcs-Git points to Debian: Restricted Project, Restricted Project.
Fri, May 7, 03:33 · Restricted Project, Restricted Project
jonas.smedegaard added projects to T1021: wlroots: Vcs-Browse and Vcs-Git points to Debian: Restricted Project, Restricted Project.
Fri, May 7, 03:31 · Restricted Project, Restricted Project
jonas.smedegaard added a project to T1020: wys: Vcs-Browse and Vcs-Git points to Debian: Restricted Project.
Fri, May 7, 03:30 · Restricted Project
jonas.smedegaard added a project to T1027: squeekboard: Vcs-Browser and Vcs-Git not declared: Unknown Object (Project).
Fri, May 7, 03:22 · Unknown Object (Project), Restricted Project
jonas.smedegaard added a project to T1027: squeekboard: Vcs-Browser and Vcs-Git not declared: Restricted Project.

Status update:

  • squeekboard 1.11.1 in amber is still missing Vcs-* hints
  • squeekboard 1.13.0-1pureos1 in byzantium is good
Fri, May 7, 03:17 · Unknown Object (Project), Restricted Project

Thu, May 6

jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

If you are interested, then I do have suggestions on how to try keep both qualities small - i.e. semi-automated routines - but they evolve around a core principle of treating the parent source (Debian) as the primary and PureOS getting applied on top.

I'd be more than interested ;)

Thu, May 6, 07:17
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

What i'm after is that the changelog content is not related to how the package is prepared. There's tools to aid certain workflows but for d/changelog itself doesn't know anything about that. (what you describe sounds more like frustration about tool failing).

Thu, May 6, 06:34

Wed, May 5

jonas.smedegaard added a comment to T1012: Please provide scripts to update downstream forks.

I have found that doing git merge <debian tag> on top of an already forked and deviated package leads to a package history which interleaves parent and fork-specific changes, which I have not found a way to automatically produce a (to me) comprehensible changelog from.

Wed, May 5, 12:34
jonas.smedegaard added a comment to T1011: Please provide scripts to create downstream forks.

See also https://source.puri.sm/-/snippets/1165 which contains above script + my notes on surrounding tasks that I have so far been unable to automate, because I have so far found to it too variable across packages.

Wed, May 5, 12:10
jonas.smedegaard added a comment to T1011: Please provide scripts to create downstream forks.

I am not fluent in Gitlab, but for the local repo part, I use this:

#!/bin/sh
Wed, May 5, 12:07
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I disagree that we should imply that meshed history is a good practice because I think it is incomprehensible to read a meshed history: It lead to my coming up with the "rebasing" strategy b) referenced in this issue report, and later lead me to file T1048 which triggered the creation of this issue report.

We need to find a balance of being comprehensible for you and workable for developers (most of which just merge in the current Debian *git* packaging into the PureOS packaging. Do you have good suggestion here?

Sorry, I have no suggestions on how to frame preparation routines which involves applying Debian changes on top of PureOS changes as "best practice" for maintaining packages forked from Debian.

Wed, May 5, 11:36
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

Any preparation style regardless of non-metadata contents of the changelog file is acceptable (obeys all "must" in Policy).

Except that this is PureOS and not Debian so while it's certainly a good idea to follow Debian policy we shoudn't simply imply that Debian Policy is the only policy and that we need to adhere to all policy points.

True that it might be bad, but until T1047 is solved Debian Policy is what we got for PureOS!
If you are aware of anything broken or incomplete or overzealous for PureOS then please file a separate report for each issue and link them to T1047.

Wed, May 5, 11:23
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

There are acceptable (obeys all "must" in Policy) and recommended (obeys all "must" and "should" in Policy) and suggested (follows best practices).

Wed, May 5, 05:57
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I'm not debating that debian/changelog could be improved.

No, but you are debating whether or not meshing changelogs makes them harder to understand.

Wed, May 5, 02:56

Tue, May 4

jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I don't think [having a rule of "changelog should be a log"] is a good idea though since merging changelogs keeps valuable information around [...] and i don't think this would make it any harder for Debian to look at the diffs.

Tue, May 4, 04:02
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

It would need to *become* a policy rule, it isn't one already.

Thanks for the clarification . sorry that I was unclear.

Tue, May 4, 03:43
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

Evangelos wrote:

this was specifically about updating downstream packages (which was the in the initial title btw ;) ).

Tue, May 4, 02:49

Mon, May 3

jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I am lost - I don't know what we are discussing here.
Possibly my own fault for a) speaking about things I find relevant before the scope of this issue report was properly established, and b) talking about things I explicitly stated previously that I find out of scope (notably requirements as opposed to best practices).

Mon, May 3, 08:11

Fri, Apr 30

jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

While that sounds like a cool feature, shouldn't the "responsibilities" be reversed? What I mean by that is: If we're carrying PureOS patches shouldn't we (by following the principle of upstream first) be the ones to propose upstreamable patches (to both the parent Debian packaging and/or the relevant upstream projects) instead of making the Debian maintainers having to go hunt for downstream patches?

Fri, Apr 30, 08:28
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

...or correction: I have seen one tool that lists downstream git branches/commits for cherry-picking - that tool is git itself and is mighty great when you know which packaging style is used. Sure, quite likely the style used by the Debian GNOME team happens to be same (or similar enough) to the one we end up deciding for our git streamlined preparation of Debian packages - but that is missing my kay point:

Fri, Apr 30, 08:16
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I think most Debian developers use https://tracker.debian.org/

Fri, Apr 30, 08:06
jonas.smedegaard added a comment to T1047: PureOS has no strict policy of mandated packaging requirements.

Ok, I will begin drafting a proposed PureOS Policy document, that we can then discuss.

Fri, Apr 30, 04:23
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I recommend to treat repo.pureos.net as essential and central for how we work in the PureOS team (i.e. not just an artifact store).

Fri, Apr 30, 03:46

Thu, Apr 29

jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

if this issue report is unrelated to T1048 then I apologize for spreading confusion, and will stand back until perhaps eventually more clear what it is about...

Thu, Apr 29, 12:37
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

@jeremiah.foster: Among the things you summarize, it seems that only "use appropriate git tag" relates to T1048 and only weakly:
How do those best practices help address T1048?

Thu, Apr 29, 12:32

Wed, Apr 28

jonas.smedegaard added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

This is about what ends up in the *changes* file for the upload, not the changelog entry.

Wed, Apr 28, 11:07
jonas.smedegaard renamed T1049: pureos: unclear how to best update downstream forks from Discussion: How to update downstream forks? to pureos: best practice(s) is missing/undocumented.
Wed, Apr 28, 10:36
jonas.smedegaard added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

I don't know rules for LTS, but the semi-official (i.e. officially .org hosted but officially unsupported) backports.debian.org seems to a) recomend including all changes compared to newest parent release in topmost changelog section(s):

It is recommended to include all changelog entries since the last version on debian-backports or since stable if it's the first version. You should do this by passing "-v" to dpkg-buildpackage. Eg: "debuild -v0.7.5-2", where "0.7.5-2" is the version in stable.

Wed, Apr 28, 07:39
jonas.smedegaard added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

So like

gnome-calls (0.3.2-1pureos1) byzantium; urgency=medium
gnome-calls (0.3.0-2pureos2) byzantium; urgency=medium
gnome-calls (0.3.0-2pureos1) byzantium; urgency=medium
gnome-calls (0.3.0-1pureos1) byzantium; urgency=medium
gnome-calls (0.3.2-1) experimental; urgency=medium
gnome-calls (0.3.0-2) experimental; urgency=medium
gnome-calls (0.3.0-1) experimental; urgency=medium

?

Wed, Apr 28, 06:36
jonas.smedegaard added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

Imagine we reach a conclusion to "find a criteria in the absence of any other authoritative source and to find consensus how to handle that" - does that mean we can close this issue report? No. That is my point.

Wed, Apr 28, 06:11
jonas.smedegaard added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

It's not meta.

Wed, Apr 28, 06:09
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

This issue says "let's discuss the seemingly 2 existing practices", and T1011 and T1012 says "we need the best practice automated".

Wed, Apr 28, 05:59
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I agree that (if we want to) we can mandate that package preparation must be done with git and must use gbp.
My point is that we cannot mandate "merging Debian tags", because that implies a parent Debian package prepared and tagged in a way compatible with gbp which is not always the case.

Wed, Apr 28, 05:21
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

sorry, didn't mean to discredit you, @guido - just appears to me as if this issue was filed by @evangelos.tzaras.

Wed, Apr 28, 05:15
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I find that issues work best when framed as something wrong - which can then be resolved either by disputing that the problem is real or by fixing it or by deciding that it exists but should not be fixed.

Wed, Apr 28, 03:41
jonas.smedegaard added a comment to T1049: pureos: unclear how to best update downstream forks.

I think it makes sense to distinguish between a) package style (i.e. how we want to compose our final .deb packages released into PureOS) and b) package preparation style (i.e. how we want to keep track of the source components used for our package releases).

Wed, Apr 28, 03:29
jonas.smedegaard added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

I see how my talking in git lingo is confusing here. Sorry!

Wed, Apr 28, 03:05
jonas.smedegaard added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

Can you define close here?

Wed, Apr 28, 02:55
jonas.smedegaard added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

I use git longo, yes, but I am talking about .deb packaging which at its core is not git-based: Git and onther VCSes are merely an aid in handling the file-based package maintenance - where it certainly is extra helpful when both Debian and PureOS preparations are done using compatible VCS tools and routines.

Wed, Apr 28, 02:39
jonas.smedegaard renamed T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes from gnome-calls: changelog has parent Debian changes and changes of local fork intertwined to gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.
Wed, Apr 28, 01:03
jonas.smedegaard triaged T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes as Normal priority.
Wed, Apr 28, 01:00

Tue, Apr 27

jonas.smedegaard added a comment to T1047: PureOS has no strict policy of mandated packaging requirements.

I consider the current document to represent the equivalent of a mixture of Debian Developers' Reference and Debian New Maintainers' Guide and the Debian wiki.

Tue, Apr 27, 01:22
jonas.smedegaard added a comment to T1047: PureOS has no strict policy of mandated packaging requirements.

@jeremiah.foster: If the current wiki page is as strict as it gets for PureOS and maintaining a more stable subset is considered overkill, then I guess simply close this issue report as wontfix.

Tue, Apr 27, 00:46
jonas.smedegaard triaged T1047: PureOS has no strict policy of mandated packaging requirements as Normal priority.
Tue, Apr 27, 00:37

Mon, Apr 26

jonas.smedegaard triaged T1009: rust-xkbcommon: Please drop 0.4.0-0pureos1 from landing as Normal priority.
Mon, Apr 26, 10:57
jonas.smedegaard renamed T1009: rust-xkbcommon: Please drop 0.4.0-0pureos1 from landing from Please drop rust-xkbcommon 0.4.0-0pureos1 from landing to rust-xkbcommon: Please drop 0.4.0-0pureos1 from landing.
Mon, Apr 26, 10:56
jonas.smedegaard added a comment to T1044: lollypop fails to start in PureOS byzantium (laptop) but not on Byzantium mobile..

It is not my impression that Lollypop wants to support opening videos - but that it wants to support audio (and probably also still images) in MPEG4 containers. But anyway since this issue seems to not be tied to how it is packaged for (Debian and) PureOS it makes better sense to discuss both issues upstream: Both the crashing bug and the potential idea for a feature request of limiting its scope (if its scope currently is loose and it tries to play not only audio but also video from multimedia files).

Mon, Apr 26, 10:33
jonas.smedegaard added a comment to T1044: lollypop fails to start in PureOS byzantium (laptop) but not on Byzantium mobile..

if you wanna change the issue from "lollypop fails to start in PureOS byzantium (laptop) but not on Byzantium mobile" then I suggest to close this issue report and file an issue upstream suggesting to change the scope of the application.

Mon, Apr 26, 10:08
jonas.smedegaard added a comment to T1044: lollypop fails to start in PureOS byzantium (laptop) but not on Byzantium mobile..

I am not well versed in reading debugger dumps, but this:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f5a43a0b995 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
[Current thread is 1 (Thread 0x7f5a77fff700 (LWP 19750))]

looks like the crash happens in the graphics driver, not in the application.

Mon, Apr 26, 08:59
jonas.smedegaard added a comment to T1034: network-manager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium.

@mladen Do I understand it correctly that this issue affects only byzantium (not amber)?

Mon, Apr 26, 06:08 · Restricted Project
jonas.smedegaard added a comment to T1034: network-manager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium.

network-manager-openvpn 1.8.14-1~pureos1 has now been queued for byzantium.
When it enters in landing it will be helpful if you could test and confirm that it works as expected, @mladen - thanks for the detailed investigation!

Mon, Apr 26, 05:58 · Restricted Project

Sun, Apr 25

jonas.smedegaard changed the status of T56: bumblebee - suggests nonfree nvidia driver, a subtask of T367: PureOS is not fully in sync with Debian, from Resolved to Invalid.
Sun, Apr 25, 09:33
jonas.smedegaard changed the status of T56: bumblebee - suggests nonfree nvidia driver from Resolved to Invalid.

Really the package suggests a non-existent package which is not an issue.
Some package exist outside of PureOS which happen to contain non-free code, but the relevant issue here is whether PureOS is encouraging the use of non-free code which is not the case.

Sun, Apr 25, 09:33 · Freedom-harm: suggests nonfree package, Freedom-harm: enhanced by nonfree code
jonas.smedegaard changed the status of T249: bumblebee: recommends non-existing package virtualgl, a subtask of T367: PureOS is not fully in sync with Debian, from Resolved to Invalid.
Sun, Apr 25, 09:28
jonas.smedegaard changed the status of T249: bumblebee: recommends non-existing package virtualgl from Resolved to Invalid.

it is not a bug to recommend a non-existent package.

Sun, Apr 25, 09:28 · Blend

Thu, Apr 15

jonas.smedegaard added a comment to T1045: matrix-mirage fails to start in PureOS Byzantium arm (L5), but not Byzantium amd64.

to me that sounds like there is no bug in the matrix-mirage package but instead a bug in the setup of the environment.

Thu, Apr 15, 09:05

Mon, Apr 12

jonas.smedegaard added a comment to T1044: lollypop fails to start in PureOS byzantium (laptop) but not on Byzantium mobile..

perhaps this? https://gitlab.gnome.org/World/lollypop/-/issues/2745

Mon, Apr 12, 07:29
jonas.smedegaard added a comment to T1023: PureOS guidelines should require (not only suggest) changing Maintainer.

I meant T1024.

Mon, Apr 12, 04:02
jonas.smedegaard added a comment to T1023: PureOS guidelines should require (not only suggest) changing Maintainer.

Strictly speaking, this issue is about Maintainer field. T1023 was about Vcs-* fields.

Mon, Apr 12, 02:40
jonas.smedegaard added a comment to T1023: PureOS guidelines should require (not only suggest) changing Maintainer.

Concretetely, I popose to replace this:

Mon, Apr 12, 02:09

Sun, Apr 11

jonas.smedegaard added a comment to T553: unspecified when a PureOS issue is truly "resolved".

The Debian bugtracker has a similar task of tracking issues potentially tied to multiple distro releases, and handles that like g).

Sun, Apr 11, 01:09 · Unknown Object (Project)

Sat, Apr 10

jonas.smedegaard added a comment to T553: unspecified when a PureOS issue is truly "resolved".

Taking T1027 as an example, I see several options here:
a) we track code project source: issue is done when solved at the code source of what is being packaged
b) we track code project release: issue is done when solved at the code source of what is being packaged and released (e.g. as tarball or git tag)
c) we track packaging project source: issue is done when solved at the packaging source
d) we track packaging project release: issue is done when solved at the packaging source and released (i.e. git tag and pushed to any queue)
e) we track any distribution: issue is done when package is available in any suite (e.g. landing)
f) we track development distribution: issue is done when package is available in testing suite (i.e. currently byzantium)
g) we track all distributions: issue is done when package is available in all supported suites (i.e. currently amber and byzantium)
h) we require explicitly defined scope: issue can only be done when clarified in issue itself where it is considered done.

Sat, Apr 10, 10:11 · Unknown Object (Project)
jonas.smedegaard added a comment to T1023: PureOS guidelines should require (not only suggest) changing Maintainer.

@jeremiah.foster I think this issue is making good progress but still not resolved: Packaging Overview now properly covers requirement to add maintainer address, but lack the detail of preserving older Maintainer field.

Sat, Apr 10, 08:53
jonas.smedegaard added a comment to T776: kodi-bin - outdated mariadb dependency.

It is now 13 days without migration - seems from https://master.pureos.net/migrations/excuse/6e70e037-1095-4e56-acae-4e854767fb5b that it "just" needs to be built on arm64.

Sat, Apr 10, 08:41
jonas.smedegaard changed the status of T1022: webkit2gtk: Vcs-Browse and Vcs-Git points to Debian from Open to Incomplete.

Thanks, @alexander.mikhaylenko, the pending changes look good to me.

Sat, Apr 10, 08:20 · Restricted Project, Restricted Project
jonas.smedegaard changed the status of T1027: squeekboard: Vcs-Browser and Vcs-Git not declared from Open to Incomplete.

hmm - let's try see if status "incomplete" is something similar to "pending" - i.e. appears as open but distinct from "Normal"...

Sat, Apr 10, 08:17 · Unknown Object (Project), Restricted Project
jonas.smedegaard added a comment to T1027: squeekboard: Vcs-Browser and Vcs-Git not declared.

...and thanks for working towards solving this issue.

Sat, Apr 10, 08:14 · Unknown Object (Project), Restricted Project
jonas.smedegaard reopened T1027: squeekboard: Vcs-Browser and Vcs-Git not declared as "Open".

This issue tracker tracks development of packages, whereas https://source.puri.sm/ tracks development of code projects (often used as basis for packages).

Sat, Apr 10, 08:13 · Unknown Object (Project), Restricted Project

Mar 27 2021

jonas.smedegaard added a comment to T908: How could I install Kodi?.

The (supported) way to install Kodi on PureOS is to use the package which is part of PureOS, *not* use external packages from Ubuntu or elsewhere.

Mar 27 2021, 10:00
jonas.smedegaard added a comment to T776: kodi-bin - outdated mariadb dependency.

This issue should be fixed since release 2:19.0+dfsg1-1pureos1 of kodi, which should appear in Debian Byzantium within a week.

Mar 27 2021, 09:52

Mar 17 2021

jonas.smedegaard added a comment to T960: Byzantium on the mini reports 404s for certain packages.

The Ubuntu issue referenced in that changelog section is this: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918112

Mar 17 2021, 19:23
jonas.smedegaard added a comment to T960: Byzantium on the mini reports 404s for certain packages.

apt 2.2.2 arrived in Debian testing now (so should soon enter PureOS landing) might fix this - judging from its changelog: https://tracker.debian.org/media/packages/a/apt/changelog-2.2.2

Mar 17 2021, 19:20

Mar 16 2021

jonas.smedegaard added a project to T1031: Please update dpkg in byzantium: Restricted Project.
Mar 16 2021, 11:41 · Restricted Project
jonas.smedegaard assigned T1031: Please update dpkg in byzantium to mak.
Mar 16 2021, 11:41 · Restricted Project
jonas.smedegaard merged task T1037: dpkg: out of sync with Debian by more than a year into T1031: Please update dpkg in byzantium.
Mar 16 2021, 11:40 · Restricted Project
jonas.smedegaard merged T1037: dpkg: out of sync with Debian by more than a year into T1031: Please update dpkg in byzantium.
Mar 16 2021, 11:40 · Restricted Project
jonas.smedegaard added a project to T1037: dpkg: out of sync with Debian by more than a year: Restricted Project.
Mar 16 2021, 11:29 · Restricted Project
jonas.smedegaard updated the task description for T1037: dpkg: out of sync with Debian by more than a year.
Mar 16 2021, 11:29 · Restricted Project
jonas.smedegaard triaged T1037: dpkg: out of sync with Debian by more than a year as High priority.
Mar 16 2021, 11:27 · Restricted Project
jonas.smedegaard closed T1036: rewrite VPN guideline to not use unavailable tool pipx as Invalid.

wrong issue tracker - moved to https://source.puri.sm/Purism/docs.puri.sm/-/issues/38

Mar 16 2021, 04:32
jonas.smedegaard triaged T1036: rewrite VPN guideline to not use unavailable tool pipx as High priority.
Mar 16 2021, 04:25
jonas.smedegaard closed T1035: pipx: not available in Byzantium as Wontfix.

pipx is a technical tool, not intended for regular users. It was packaged for Debian as it was requested for the _administration_ of Librem One services but explicitly *not* for general use.

Mar 16 2021, 04:23
jonas.smedegaard renamed T1035: pipx: not available in Byzantium from `pipx` not available in Byzantium to pipx: not available in Byzantium.
Mar 16 2021, 04:19
jonas.smedegaard renamed T1034: network-manager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium from networkmanager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium to network-manager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium.
Mar 16 2021, 04:14 · Restricted Project
jonas.smedegaard renamed T1034: network-manager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium from Librem Tunnel and some other OpenVPN services not working with networkmanager-openvpn-1.8.12 on byzantium to networkmanager-openvpn: fails to work with Librem Tunnel and some other OpenVPN services on byzantium.
Mar 16 2021, 04:12 · Restricted Project

Mar 15 2021

jonas.smedegaard closed T81: unp - suggests non-free packages unace unrar unarj, and treats missing tool as errors, a subtask of T225: [FREEDOM ISSUE] META - mentions FSDG-nonfree stuff, as Invalid.
Mar 15 2021, 08:53 · Freedom
jonas.smedegaard closed T81: unp - suggests non-free packages unace unrar unarj, and treats missing tool as errors as Invalid.

as previously noted, this is a non-issue: no non-free package is suggested because the suggested package is not registered in apt so it is neither free nor non-free, it is instead nonexistent.

Mar 15 2021, 08:53
jonas.smedegaard closed T79: [FREEDOM ISSUE] p7zip-full, a subtask of T367: PureOS is not fully in sync with Debian, as Invalid.
Mar 15 2021, 08:51
jonas.smedegaard closed T79: [FREEDOM ISSUE] p7zip-full as Invalid.

as previously noted, this is a non-issue: no non-free package is suggested because the suggested package is not registered in apt so it is neither free nor non-free, it is instead nonexistent.

Mar 15 2021, 08:51
jonas.smedegaard closed T80: xarchiver suggests nonfree package rar as Invalid.

as previously noted, this is a non-issue since the package cannot really suggest something that does not exist as a package registered with apt.

Mar 15 2021, 08:48
jonas.smedegaard closed T80: xarchiver suggests nonfree package rar, a subtask of T367: PureOS is not fully in sync with Debian, as Invalid.
Mar 15 2021, 08:48

Mar 12 2021

jonas.smedegaard triaged T1033: libhandy-1: Vcs-Browse and Vcs-Git URLs are broken as Normal priority.
Mar 12 2021, 16:31

Mar 9 2021

jonas.smedegaard triaged T1030: phosh: Vcs-Browse and Vcs-Git points to Debian as Normal priority.
Mar 9 2021, 13:07 · Restricted Project, Restricted Project
jonas.smedegaard added a comment to T1029: packaging guidelines should document how to stop forking from Debian, preferrably mandating specific suffix.

I have tested and can confirm that the use of suffix purge works to drop local fork:
https://lists.puri.sm/pipermail/pureos-changes/2021-March/001152.html shows the packages I uploaded, and https://software.pureos.net/search_pkg?term=zpb shows (at the time of writing this) that landing now contains the package from Debian.

Mar 9 2021, 11:30
jonas.smedegaard triaged T1029: packaging guidelines should document how to stop forking from Debian, preferrably mandating specific suffix as Normal priority.
Mar 9 2021, 11:22
jonas.smedegaard added a comment to T1023: PureOS guidelines should require (not only suggest) changing Maintainer.

Looks good.

Mar 9 2021, 08:37