[08:08] <elgaton> Hi everyone, anyone knows the procedure to request backports? The wiki (<https://wiki.ubuntu.com/UbuntuBackports>) mentions the requestbackports tool, but it isn't in the ubuntu-dev-tools package
[08:08] <micahg> elgaton: it's available in precise on
[08:08] <elgaton> micahg: Thanks
[08:08] <micahg> and it's called requestbackport
[08:08] <elgaton> Yes, sorry for the typo
[08:34] <vibhav> Should I merge or sync for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667320 ?
[08:34] <vibhav> (for Ubuntu)
[08:37] <geser> vibhav: what do you want to merge there? pdfedit has no Ubuntu delta
[08:38] <micahg> vibhav: no need to do anything, it'll come in the autosync next week (May 21)
[08:39] <vibhav> geser: I thought a minimal change might be better
[08:40] <geser> vibhav: as we are at the start of the development cycle, syncs are preferred
[08:41] <vibhav> ok
[11:57] <rokr1> indicator-datetime-service memory leak any solution ?
[12:56] <cjwatson> larsduesing: Those Architecture lines should work fine with Ubuntu, just as with Debian.
[14:27] <vibhav> Can https://bugs.launchpad.net/ubuntu/+source/sphinx/+bug/480913 be nominated for onerirc and lucid?
[15:10] <melodie> hi
[15:12] <melodie> I want to open a ppa at launchpad, I have signed the code of conduct, put my gpg key there and I would like to know what is best for the url : should I just put the name of the package I did as last directory name ?
[15:12] <melodie> I am also looking for someone who would try the package in an install using Openbox
[15:13] <melodie> anyone here using Openbox who would be willing to test openbox-menu package ? (it's at debian mentors repos since a few days)
[15:24] <melodie> I have also 2 questions : is it possible to add a post-install message in a package ? and is it possible to package a set of configuration files ?
[15:25] <Resistance> melodie:  the name for what you use for the PPA name can be the package / program you're putting there, or it can be descriptive of the package, for instance i have two PPAs for backports, one for staging/building and one for use
[15:26] <Resistance> as for testing, i'm not able to help you there.
[15:26] <melodie> Resistance, thanks
[15:26] <Resistance> and for adding messages into the installer post-install, you *can*, but i dont see it often done.  and for a set of configuration files, you should include default / template config files
[15:26] <Resistance> or a configuration tool to be run
[15:26] <Resistance> (which can be done post-install, and probably should only be done if confs dont already exist)
[15:28] <melodie> the problem is that once the config files installed, they can be tweaked by the user, hence the next install for update should not bring config files again. In another distro the problem has been solved by creating a separate package, send the files to /usr/share/the_program_name, with a post install message which explains what to do with it.
[15:29] <melodie> then each new set of configuration file uploaded can be an update too, if some improvements have been done.
[15:29] <melodie> and be a new version.
[15:29] <melodie> it's just that I don't know how to do that with deb packages
[15:31] <melodie> I would need advise from someone who would test the package and the config files. a dev who knows as well packaging as be an Openbox user
[15:33] <geser> melodie: have you already read the Debian Policy manual, especially http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
[15:35] <melodie> geser, I have not read everything for sure. I am a packager newbie. thanks for the link
[20:34] <broder> cjwatson: working on an in-queue backport verification tool. how much less useful is it if it can't automatically figure out where we're backporting *from*?
[20:34] <broder> (i.e. it's easy to extend queuediff to do this if you can give it a source release)
[21:29] <melodie> anyone on board ?
[21:29] <melodie> I am reading this page : http://www.debian.org/doc/debian-policy/ch-files.html# this chapter:  10.7 Configuration files" because I think I should make a package out of the following configuration files : http://meets.free.fr/debian/openbox-menu-configuration.tar.bz2
[21:29] <melodie> I am not sure if I should think of making a package which will copy the files under /etc as said in the page of the doc, or rather under /usr/share as I have seen in another distribution, and from where the user can get the files and copy them himself to his home.
[21:30] <melodie> there is exactly one line very necessary in the menu.xml file, the 3rd line.
[21:31] <melodie> and the rest of the files can allow to have a complete environment working as a real desktop, but only with Openbox, and a few programs such as tint2 or lxpanel, pcmanfm or any other file manager, feh...
[21:31] <melodie> and even some desktop effects with xcompmgr and xsnow which can be started or stopped on the fly from the menu.
[22:14] <melodie> could someone tell me what exactly can be put into /usr/share (concerning packages and their contents) and what can't go there ?
[22:14] <melodie> reading docs and docs and can't find my case
[22:15] <melodie> I mean can't find the one thing I want to do
[22:19] <geofft> melodie: are you packaging openbox itself, or a package to configure it, or?
[22:20] <melodie> hi geofft I have packaged openbox-menu which is a dynamic menu generator for openbox - think pipe-menu - and I would like to add configuration files as optional depends
[22:21] <melodie> I try to find a simple way to do that : have the files in /usr/share would be better than in /etc in order not to make the config wide, but just available in case of need
[22:21] <melodie> and I would also need to learn to write a post-install message (this was my first package)
[22:21] <geofft> I don't know anything about openbox, but one sensible thing might be to make a separate session type you can choose from the login menu that starts openbox with this config (and leave the default openbox config alone)
[22:22] <melodie> not really
[22:23] <melodie> you can have these configuration files in lxde and not use them, or xfce and so on... then it all depends if the user sets his desktop to display the menus of the wm or not
[22:23] <melodie> here is the package done : http://lists.debian.org/debian-mentors/2012/05/msg00088.html
[22:24] <melodie> if you have default configuration files, you will want to merge some parts eventually. then the message at post-install will just say : the files are there for you, read the readme, and save your original files then install these ones.
[22:25] <melodie> it is not too easy to merge xml files automatically I think. the possibilities are infinite and the user know their files (if not they will have the all made ones)
[22:26] <melodie> geofft, and what login menu would that be ? startx ? lightdm ? gdm ? kdm ?
[22:26] <melodie> so this does not talk much to me.
[22:26] <geofft> Every *dm package looks in the same place for login menus, I believe
[22:27] <melodie> where could I find a doc on how to make a package for providing configuration files for users ?
[22:27] <geofft> If this is per-user configuration (not global configuration), then you should just put defaults in /usr/share (maybe /usr/share/doc/openbox-menu/examples?) and not use /etc
[22:27] <melodie> geofft, do you think or are you sure ?
[22:27] <melodie> yes
[22:27] <melodie> geofft, I would like to put them to /usr/share/openbox-menu
[22:27] <geofft> (But if this is per-user, then a post-install message will only reach the one sysadmin doing the install)
[22:28] <melodie> geofft, this is right, only the sysadmin must administrate packages anyway.
[22:28] <melodie> he knows what is good for all.
[22:29] <melodie> if he wants he can install the files for all, or not, install them also under /etc/skel/.config if he thinks it relevant
[22:32] <geofft> by the way, you have seen update-menus, right? I can't tell if it's related, but I think it is.
[22:34] <melodie> I have seen openbox-xdgmenus
[22:34] <melodie> I have marked it as conflict
[22:34] <melodie> I look about the one you say
[22:35] <melodie> geofft, no result in precise
[22:35] <melodie> where did you see update-menus ?
[22:35] <geofft> sorry, that's a command, not a package. I think it's in the menu package
[22:36] <melodie> ok
[22:36] <melodie> I have been told menu uses debian-menus and that it is not nice
[22:37] <melodie> openbox-menu uses libmen-cache1 from the lxde project and the desktop files : the menus generated are compliant with the freedesktop.org specifications
[22:37] <melodie> and also it keeps them up to date automatically : nothing to do or redo once installed and the openbox-menu command line set in the menu.xml
[22:38] <melodie> the set of configuration files I have tarballed have been done along several years and contain additional things for the comfort
[22:38] <melodie> libmenu-cache1 (forgot a u)
[23:17] <melodie> gn