micahg | ScottK: would you be opposed to enabling internal libraries for something in -backports as long as the backports keep moving (not stalling on an old version)? | 03:17 |
---|---|---|
ScottK | Is this as an alternative to backporting a stack of depends too? | 03:18 |
micahg | yes (libreoffice) | 03:18 |
ScottK | Generically, that's fine, but isn't that a bit of a core package for backports? | 03:19 |
ScottK | Also, I don't think you can promise to keep it moving. It's pretty much a beast to get to build reliably, AIUI. | 03:19 |
micahg | I think the testing can be crowdsourced | 03:20 |
micahg | there seems to be a demand for it | 03:20 |
micahg | https://blueprints.launchpad.net/ubuntu/+spec/client-1308-rolling-libreoffice | 03:20 |
micahg | I'm trying to write up an in archive proposal that avoids SRUing newer major releases as that sounds like a larger nightmare | 03:20 |
micahg | and they already get it working on older releases, I'd like to make that work in archive instead of in a PPA | 03:21 |
ScottK | It's worth an experiment. | 03:39 |
ScottK | It can be removed if it doesn't work out. | 03:39 |
micahg | yep | 03:40 |
micahg | I plan to make it clear that it'll be removed if there are major issues or the backports stop happening | 03:40 |
dlynch | Hi! Is there anyone around at this time of night / day who could help me with hopefully an easy packaging question? | 04:29 |
RAOF | Sure; You'll get a better answer if you ask your question, though ;) | 04:29 |
dlynch | I am the developer of Rapid Photo Downloader, which is in Debian / Ubuntu; I also maintain a PPA. A user has submitted a .desktop file whose purpose is give the program a KDE Solid action. I have no idea how to incorporate it into the package! | 04:36 |
RAOF | dlynch: Ah, ok. You need to install that desktop where KDE expect it; I presume it expects it in /usr/share/applications, but it might want to be somewhere else. | 04:47 |
RAOF | dlynch: Either you should fold this in to your regular build/install mechanism, or you can use dh_install to... install it to the right place ☺ | 04:47 |
dlynch | is it ok that the package already has a .desktop file? It can have two of them? Or I should somehow merge them? | 04:47 |
RAOF | You can have multiple desktop files (as long as they've got different names, obviously). | 04:48 |
dlynch | the user is saying it should go into /usr/share/kde4/apps/solid/actions/ . Does it need a different name if one goes there and another into /usr/share/applications? | 04:51 |
ScottK | I have quite a number of desktop files installed there on my KDE system. | 04:58 |
ScottK | No, it doesn't need a different name I don't think. | 04:58 |
dlynch | My program has a setup.py - so I guess the code to install the KDE solid action could go there, assuming all distros put the KDE solid actions into /usr/share/kde4/apps/solid/actions/. Otherwise, the debian rules file has a brief override_dh_auto_install section, but I don't understand any of that... | 05:12 |
dlynch | thanks for your help everyone :) | 05:57 |
Noskcaj | Can someone please merge the branch for bug 985966 | 08:56 |
ubottu | bug 985966 in clipit (Ubuntu) "Drop-Down-Selection Propagates Wrong History for Pasting" [Medium,In progress] https://launchpad.net/bugs/985966 | 08:56 |
=== DrKranz is now known as DktrKranz | ||
ffio | what does this thing do ? "edit-patch 99-new-patch" | 15:14 |
Ampelbein | ffio: edit-patch is a wrapper that tries to automatically find out which patch system a package uses (quilt, dpatch etc) and simplifies creating patches. | 16:02 |
ffio | Ampelbein: in ubuntu packaging guide everywhere it's assume that you using bazaar. but what if if we are not using bazaar ? | 16:08 |
Ampelbein | ffio: Then adapt the commands to the VCS you are using. | 16:11 |
Ampelbein | ffio: Almost everything that you can do with bazaar you can also do with git, for example. Except for the merge proposals on launchpad, because lp doesn't support anything else. | 16:12 |
ffio | Ampelbein: i am simply using sudo apt-get source package_name | 16:12 |
Ampelbein | ffio: That works as well, of course. | 16:12 |
ffio | but some of the commands changes. | 16:12 |
ffio | and i can't get which command to get. | 16:13 |
Ampelbein | What part is causing you troubles? | 16:14 |
ffio | Ampelbein: right now bzr builddeb -- -S -us -uc doesn't work for me. | 16:15 |
ffio | to build the package. | 16:15 |
Ampelbein | ffio: By default, that calls "debuild" and adds the options ("-S -us -uc"), so calling debuild -S -us -uc will do practically the same. | 16:17 |
Ampelbein | ffio: The debian new maintainers guide is a pretty good start on packaging know how, see http://www.debian.org/doc/manuals/maint-guide/ | 16:17 |
ffio | great, checking that out :) | 16:18 |
=== dholbach_ is now known as dholbach | ||
=== dholbach_ is now known as dholbach | ||
jtaylor | does a core dev want to help out (= sponsoring) fixing pyparsing before the feature freeze? | 17:18 |
=== bschaefer_ is now known as bschaefer | ||
=== bschaefer_ is now known as bschaefer | ||
=== bschaefer is now known as bschaefer|lunch | ||
=== bschaefer|lunch is now known as bschaefer | ||
ockham | tumbleweed: would you kindly upload https://github.com/thinkle/gourmet/tree/ubuntu for me? | 23:42 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!