How to update ddccontrol-db?

[ddccontrol]

How to update ddccontrol-db?

[larstobi]

There are no command line keys to do this. To update to the latest database you can run apt-get upgrade.

[larstobi]

I'm sorry, I may have been wrong. If you're running Ubuntu 17, then it isn't in the repositories.
https://packages.ubuntu.com/search?section=all&arch=any&keywords=ddccontrol&searchon=names

How did you install it?

[itJunky]

This package is soo ooold! Need key for fast update from github repo.

[kravemir]

Just follow steps provided in README of this repository, section Installation from sources.

[itJunky]

It's stupid way when i have regulary updated distro package!
Now, i'm just download files of DB and move it to folder where db locate by package.

[kravemir]

Process to get packages into official Debian / Ubuntu is very complicated, and there are many requirements, which have to be met in order to get package accepted. We're working on it,..

We have already managed to get latest version to Fedora. Updated Debian / Ubuntu packages are on the way. Expect it in one to three weeks.

[itJunky]

It's ok. But i think, update distro package need only if we have updates to an application code.
But if we have update of database, we need key in application to do it in any time.

[kravemir]

What do you mean by key? Because, key could be key on the keyboard, license key, door key,... How is any key related to open-source tool?

[itJunky]

key it's runtime argument

[larstobi]

I suspect you mean a "ddccontrol db-update" command line parameter? I agree that it makes a lot of sense. They're doing that for updating the PCI-IDs database (http://pciids.sourceforge.net) and I believe a similar thing for USB IDs.

[kravemir]

Actually. Package ddccontrol-db contains locale files, which are generated during build. To update DB, it is needed to build the package.

Also, package managers are made especially to maintain software installations. You're using Ubuntu, which is standard release distribution. To have latest package version, you can use this PPA: https://launchpad.net/~kravemir/+archive/ubuntu/ddccontrol

We will create official PPA for the ddccontrol project, once we manage to get new packages accepted by into debian. Then these packages will be available in development(unstable) version of distribution, and the ddccontrol PPA would offer the same ddccontrol packages for previous Ubuntu versions. Then with that PPA, all you have to do is: sudo apt update && sudo apt upgrade

[anarcat]

@kravemir with all due respect, i think you got this backwards: you can definitely create an official PPA before the package gets officially in Debian. in fact, it's a great way to provide packages while you wait for Debian to merge the updates in. i think it's great you already have a PPA and that should be advertised more widely. for example, the SourceForge website should point to github and the README should point to the PPA. :)

now, as a Debian maintainer, I can help with getting stuff in Debian. the status over there is that the package was orphaned (or "abandoned") in 2008 because of upstream inactivity. you could already update that bug report with current progress by email there... you could also ask for sponsorship if you want to maintain the package yourself, otherwise some generous soul would need to come up and update the package when they have time.

i take it the reference code is now on github? i might give it a shot if you wish...

[kravemir]

@anarcat I know, that it's possible to do it in reverse order. I wanted to make PPA as "backports" from debian testing/unstable for Ubuntu. Actually, I would like to make debian packages, as I have already invested a lot of time, and have studied a lot about debian packaging.

There's already latest ddccontrol-db package in debian sid, and ddccontrol package is prepared at mentors. It just needs a sponsor, I'm in touch with a debian developer, which sponsored ddccontrol-db package upload. But sometimes, his reactions are really slow, like a month or two response time.

[kravemir]

@anarcat if you're looking for an opportunity to make a debian package by yourself, check: editorconfig/editorconfig-gedit#16

As for ddccontrol, I have submitted RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888246

[anarcat]

I wanted to make PPA as "backports" from debian testing/unstable for Ubuntu.

well, there are backports in debian exactly for that. :) and for ubuntu as well... but yeah, that works too!

Actually, I would like to make debian packages, as I have already invested a lot of time, and have studied a lot about debian packaging.

That's great!

It just needs a sponsor, I'm in touch with a debian developer, which sponsored ddccontrol-db package upload. But sometimes, his reactions are really slow, like a month or two response time.

hmm... yes, that is pretty slow. maybe i can help here: i am a debian developer myself and can perform reviews and uploads...

As for ddccontrol, I have submitted RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888246

... so do let me know, here or by email (anarcat at debian) if you can't find another sponsor.

@anarcat if you're looking for an opportunity to make a debian package by yourself, check: editorconfig/editorconfig-gedit#16

i am maintaining plenty of packages already, but thanks for the suggestion! :)

[anarcat]

i added a review of the debian package in the RFS, let me know when you have a new version ready for review, and i'll be happy to upload the changes.

do you also need help for an update of the ddccontrol-db package? it seems there was an upload in late 2017 so that seems more up to date...

[anarcat]

so I have just updated ddccontrol in the Debian repositories. it will take 10 days to trickle down in testing and, if people really need it (i actually doubt it), it can be backported to stretch.

what people may need here (and it's the topic of this original post) is to update the ddccontrol-db package (not ddccontrol, which is a distinct source package). there has been an update of that package in unstable/testing about a month ago, but there was no backport.

are there enough changes in the -db package to warrant such a backport?

[kravemir]

@anarcat there have been added support for many monitors in latest two versions, details are in the changelog: https://github.com/ddccontrol/ddccontrol-db/blob/master/ChangeLog

Is it common to do regular backports for such packages? I guess, that this tool is mostly used by Ubuntu users (there will be PPA set-up, once I will find time for it), and Debian desktop users probably use testing/unstable. Or, is it common to use Debian stable for desktop?

[anarcat]

On 2018-01-26 15:51:49, Miroslav Kravec wrote: @anarcat there have been added support for many monitors in latest two versions, details are in the changelog: https://github.com/ddccontrol/ddccontrol-db/blob/master/ChangeLog

I see.. not sure it's really worth it, i see about... 20 monitors there?

Is it common to do regular backports for such packages?

I guess it's a good reason to do it... There's no way we could keep up with hardware renewal otherwise...

I guess, that this tool is mostly used by Ubuntu users (there will be PPA set-up, once I will find time for it), and Debian desktop users probably use testing/unstable. Or, is it common to use Debian stable for desktop?

I can't speak for others, but I am still on Debian stretch (stable) for my desktop right now. I use backports for some stuff I'm missing; when that becomes too much trouble, I upgrade to testing to help with shaking off RC bugs from there, and that becomes stable soon after. It's a nice working cycle I got... So yes, there are definitly stable desktops out there. In fact, back when I was maintaining a fleet of such desktops, we were running either stable or oldstable on the desktops. Otherwise it means you have constant (daily!) upgrades to keep track of and we don't want to submit our users to that... A.

…

-- Brief is this existence, as a fleeting visit in a strange house. The path to be pursued is poorly lit by a flickering consciousness. - Albert Einstein

[kravemir]

I can't speak for others, but I am still on Debian stretch (stable) for my desktop right now. I use backports for some stuff I'm missing; when that becomes too much trouble, I upgrade to testing to help with shaking off RC bugs from there, and that becomes stable soon after. It's a nice working cycle I got...

I tried it once, it didn't work out for me. I was running Arch, but Arch would break once a month (or two) after upgrades. So, I've moved to Ubuntu, stable and short release cycle (half-year). Now, I'm running Debian Unstable, because it makes development and testing of packages easier. And, ddccontrol is HW related software, so it doesn't make sense to test in virtual machine.

So yes, there are definitly stable desktops out there. In fact, back when I was maintaining a fleet of such desktops, we were running either stable or oldstable on the desktops. Otherwise it means you have constant (daily!) upgrades to keep track of and we don't want to submit our users to that...

Definitely makes sense. It's different to maintain few personal machines, and to maintain fleet of desktops (ie. for some company).