Page MenuHomePureOS Tracker

evangelos.tzaras (Evangelos Ribeiro Tzaras)
User

Projects

User does not belong to any projects.

User Details

User Since
Jan 20 2021, 20:11 (38 w, 6 d)

Recent Activity

Thu, Oct 7

evangelos.tzaras added a comment to T1030: phosh: Vcs-Browse and Vcs-Git points to Debian.

With https://source.puri.sm/Librem5/debs/pkg-phosh/-/merge_requests/21 merged this can be closed (unless it's preferred to wait for a new release incorporating those changes reaches the archive)

Thu, Oct 7, 12:01 · Restricted Project, Restricted Project

Sun, Oct 3

evangelos.tzaras added a comment to T1030: phosh: Vcs-Browse and Vcs-Git points to Debian.

Since I just saw this issue on the byzantium board I've opened https://source.puri.sm/Librem5/debs/pkg-phosh/-/merge_requests/21
/cc @guido

Sun, Oct 3, 17:07 · Restricted Project, Restricted Project

Sep 8 2021

evangelos.tzaras added a comment to T1074: -dbgsym packages seem to be missing from byzantium.

This is probably a duplicate of https://tracker.pureos.net/T873 (see last comment by Guido).

Sep 8 2021, 03:22
evangelos.tzaras created T1074: -dbgsym packages seem to be missing from byzantium.
Sep 8 2021, 02:40

May 6 2021

evangelos.tzaras 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.

May 6 2021, 04:13

May 5 2021

evangelos.tzaras added a comment to T1049: pureos: unclear how to best update downstream forks.

When you do a git merge then changelog files are meshed, and when you follow "strategy b)" you don't. That seems rather consequential to me, not orthogonal.

May 5 2021, 04:54

May 3 2021

evangelos.tzaras renamed T1049: pureos: unclear how to best update downstream forks from pureos: best practice(s) is missing/undocumented to pureos: unclear how to best update downstream forks.
May 3 2021, 20:08
evangelos.tzaras added a comment to T1049: pureos: unclear how to best update downstream forks.

@evangelos.tzaras: Is the issue you reported here broadly about any and all best any practice(s) in PureOS missing or undocumented?

May 3 2021, 20:08

Apr 30 2021

evangelos.tzaras added a comment to T1049: pureos: unclear how to best update downstream forks.

I would love to have https://tracker.debian.org/ also link to PureOS patches - and I see how that is doable by parsing Debian Policy standards-compliant source packages and look for DEP-5 standards-compliant patches. Which standards should I follow to implement such feature for git branches/commits?

Apr 30 2021, 08:15

Apr 29 2021

evangelos.tzaras added a comment to T1049: pureos: unclear how to best update downstream forks.

I could've maybe worded it more clearly in the OP: I was mostly concerned with how to update packages - especially when we're a downstream of Debian.
The question arose because of T1048 and the discussion that ensued around how d/changelog should look like.

Apr 29 2021, 14:54
evangelos.tzaras added a comment to Packaging Overview.

I was mostly confused whether this would imply that we would have both pureos/latest and pureos/byzantium.

Apr 29 2021, 14:36 · Restricted Project, Restricted Project, Restricted Project

Apr 28 2021

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

For the record, this very issue report was not meant as "this package is totally WRONG" - which is the reason I marked it as severity normal.

Apr 28 2021, 23:39
evangelos.tzaras added a comment to T1049: pureos: unclear how to best update downstream forks.

I propose to reframe this issue to say "best practice(s) is missing/undocumented".

Apr 28 2021, 09:18
evangelos.tzaras added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

I opened https://tracker.pureos.net/T1049 for the meta discussion and will leave this open until the meta-issue has been clarified (as you suggested)

Apr 28 2021, 03:07
evangelos.tzaras created T1049: pureos: unclear how to best update downstream forks.
Apr 28 2021, 03:07
evangelos.tzaras added a comment to T1048: gnome-calls: changelog has parent Debian changes interleaved with PureOS changes.

Rebasing? In the git sense of the word? Wouldn't that imply having to always force push to our packaging repositories (which would destroy/rewrite the git history)?

Apr 28 2021, 02:05
evangelos.tzaras added a comment to Packaging Overview.

So would that be pureos/latest (instead of pureos/byzantium) and pureos/amber or pureos/amber-phone then?
Confusing!

Apr 28 2021, 00:42 · Restricted Project, Restricted Project, Restricted Project

Apr 25 2021

evangelos.tzaras added a comment to Packaging Overview.

Feel free to delete my draft which arouse out of confusion around the Uploaders: field ;)

Apr 25 2021, 09:04 · Restricted Project, Restricted Project, Restricted Project

Mar 3 2021

evangelos.tzaras published a new version of Uploading Packages to PureOS.
Mar 3 2021, 10:17
evangelos.tzaras changed the visibility for Uploading Packages to PureOS.
Mar 3 2021, 10:00
evangelos.tzaras changed the visibility for Uploading Packages to PureOS.
Mar 3 2021, 09:56

Feb 15 2021

evangelos.tzaras added a comment to Uploading Packages to PureOS.

i was just wondering under which circumstances i would use dput?
my understanding was that when pushing a signed tag in the packaging repos (those which are pointed to from deb-build-jobs (?)) that the build server would automagically start the build.

Feb 15 2021, 01:30