-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to update ddccontrol-db? #43
Comments
There are no command line keys to do this. To update to the latest database you can run apt-get upgrade. |
I'm sorry, I may have been wrong. If you're running Ubuntu 17, then it isn't in the repositories. How did you install it? |
This package is soo ooold! Need key for fast update from github repo. |
Just follow steps provided in README of this repository, section Installation from sources. |
It's stupid way when i have regulary updated distro package! |
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. |
It's ok. But i think, update distro package need only if we have updates to an application code. |
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? |
key it's runtime argument |
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. |
Actually. 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: |
@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... |
@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. |
@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 |
well, there are backports in debian exactly for that. :) and for ubuntu as well... but yeah, that works too!
That's great!
hmm... yes, that is pretty slow. maybe i can help here: i am a debian developer myself and can perform reviews and uploads...
... so do let me know, here or by email (anarcat at debian) if you can't find another sponsor.
i am maintaining plenty of packages already, but thanks for the suggestion! :) |
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... |
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? |
@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? |
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
|
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.
Definitely makes sense. It's different to maintain few personal machines, and to maintain fleet of desktops (ie. for some company). |
Can't find any command line keys for update monitors database.
The text was updated successfully, but these errors were encountered: