yagf - fallback-depends on nonfree cunaiform
Closed, InvalidPublic

Description

Package yagf fallback-depends on nonfree package cuneiform

Rebuild with "Depends: cuneiform" removed.

mladen created this task.May 22 2017, 9:25 PM

I'll patch this one today.

zlatan.todoric closed this task as "Resolved".May 22 2017, 11:40 PM

Fixed.

mak lowered the priority of this task from "95" to "Freedom Issue".Aug 19 2017, 5:08 AM
jonas.smedegaard changed the title from "[FREEDOM ISSUE] yagf" to "yagf - fallback-depends on nonfree cunaiform".Nov 3 2017, 10:19 AM
jonas.smedegaard claimed this task.
jonas.smedegaard edited the task description. (Show Details)
jonas.smedegaard added a subscriber: hema.prathaban.
jonas.smedegaard removed a subscriber: hema.prathaban.
jonas.smedegaard reopened this task as "Open".

yagf does not fallback-depend on a non-free package, only a non-existent one.

@mak Please drop our fork of yagf and let in the Debian package which complies fine with GNU FSDG.

When addressed, this issue should be flaged as "invalid" (not "resolved").

jonas.smedegaard lowered the priority of this task from "Freedom Issue" to "Normal".Aug 23 2018, 11:23 AM
jonas.smedegaard removed a project: Freedom.
mak closed this task as "Invalid".Aug 23 2018, 2:14 PM

Done, but @jonas.smedegaard if the version number in PureOS is *higher* than the one in Debian, I can't sync stuff. In that case, an upload without the "pureos" version suffix has to be made to PureOS, which is a thing you can easily do as well and which doesn't need me.

Sorry, I don't follow.

Taking this package as an example: Debian has 0.9.3.2-1 and PureOS has (at least until a moment ago) 0.9.3.2-1pureos1.

I understand that only when Debian issues a new release will it enter PureOS. What I don't understand is a) what you have done now making you close this issue, and b1) if you are telling that I could have done it myself or b2) I need to do something myself now or b3) I can optionally do something alternative for other packages instead of what you did now, or...?

mak added a comment.Aug 23 2018, 6:22 PM

The archive generally doesn't support downgrades - versions can only ever go up, otherwise our users will not actually get the changes.
So, if we have a version 0.9.3.2-1+pureos1 in PureOS, I can not sync 0.9.3.2-1 from debian, because 0.9.3.2-1 << 0.9.3.2-1+pureos1.
The archive will also *never* override PureOS-specific changes.
So what I did just now make an 0.9.3.2-1+x1 upload[1], because 0.9.3.2-1+x1 >> 0.9.3.2-1+pureos1. Since there is no "pureos" in the version string anymore now, the next time Debian gets a higher version of this package, the archive will just override the package I uploaded and we will be fully in sync again.

So in general: If Debian version >> PureOS version, I can trigger an override-sync to fetch the Debian package (please file an issue and assign it to me in that case!). If the PureOS version >= Debian version, someone needs to make a dummy upload realigning the package with the one from Debian, replacing the "pureos" in the version string with something higher (I usually simply use "x"). The only difference of that dummy upload will be the changelog entry. In that case, the archive will do the right thing next time a new Debian version is found, and nobody needs to rely on be to solve this issue.

I hope that clears things up!

[1]: https://lists.puri.sm/pipermail/pureos-changes/2018-August/000331.html

Add Comment