> (removing colord source package. It’s what is bringing argyll to main,
but it’s not the component targeted by the MIR itself).
Fair enough, but an update-excuse bug is useful for +1 maintainers to
track that this is already a diagnosed migration problem for colord. So
I've opened LP: #2003833
(removing colord source package. It’s what is bringing argyll to main,
but it’s not the component targeted by the MIR itself).
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to argyll in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
@Bryce, @RAOF: thanks for the notice! I feel we should then reuse this
MIR to file a new template with our modern MIR rules (Note that the
initial demand was made in 2011!)
I’m thus marking it as incomplete until this is DONE, feel free to redirect
this request directly to the team who will own
colord recently re-enabled argyll support. Unfortunately since argyll
is in universe and colord is in main, this is causing an 'impossible
depends' migration error for colord.
colord-sensor-argyll/amd64 in main cannot depend on argyll in universe
Impossible Depends: colord ->
** Also affects: colord (Ubuntu)
Importance: Undecided
Status: New
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to argyll in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
I have no further news about the package and for printing I do not see
any necessity for this package. We must ask the people working on
monitor calibration.
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to argyll in Ubuntu.
Matching
What is the status of this MIR? Is it still required to provide some
feature?
Changes were requested, they don't appear to be all done, but I wouldn't
necessarily block on needing to use something other than JAM if the
maintainability of the pacakge is good.
** Changed in: argyll (Ubuntu)
Current version is 2.0.1:
- Still uses JAM build system
- Finally switched to libusb 1.0.0
** Changed in: argyll (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to argyll in Ubuntu.
Matching
[Expired for argyll (Ubuntu) because there has been no activity for 60
days.]
** Changed in: argyll (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to argyll in Ubuntu.
Matching
Till, please could you update that for 2018?
** Changed in: argyll (Ubuntu)
Milestone: ubuntu-11.10-beta-1 => None
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to argyll in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
I had a look in current Argyll package in Ubuntu (1.6.3-4) and found
following:
GOOD:
- Packaging less complex as upstream build system is used now.
BAD:
- Exotic JAM build system used by upstream.
- Still uses deprecated libusb 0.1.x, needs to get ported to 1.0.x, preferably
by upstream.
--
** Changed in: argyll (Ubuntu)
Status: Triaged = Incomplete
** Changed in: argyll (Ubuntu)
Assignee: Didier Roche (didrocks) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to argyll in Ubuntu.
Matching
12 matches
Mail list logo
