=== Amaranth_ is now known as Amaranth
=== yofel_ is now known as yofel
[02:50] <ari-tczew> could someone open task on maverick in bug 669066 ?
[02:50] <ubottu> Launchpad bug 669066 in fetchmail (Ubuntu) "fetchmailconf: fetchmailconf.py': [Errno 2] No such file or directory" [Undecided,Confirmed] https://launchpad.net/bugs/669066
=== v is now known as stalcup
[06:28] <c2tarun> i create a group name admin in my chroot environment and added a "admin ALL=(ALL) ALL" to /etc/sudoers file. then i created a user account and added this account to admin group. now when i m executing any command with sudo privileges i m getting the error that tarun is not in sudoer list??? can anyone please help
[06:30] <ebroder> c2tarun: That's really more about using Ubuntu than developing Ubuntu. #ubuntu might be a little more appopriate. But you want %admin, not admin to refer to a group
[06:35] <c2tarun> sorry for asking here and thanks a lot.
=== stalcup is now known as vorian
[07:16] <lucas> geser: not easy to add it to the cgi, but you can get it from one of the logs' header
=== Quintasan_ is now known as Quintasan
[10:01] <geser> lucas: I somehow missed to spot the date in the log header as I usually jump to the end of the log
[10:49] <danielrichter200> Hi, I want to upload my new application grub-customizer to revu. Everything seems to be ok (no dput errors), but grub-customizer didn't appear in the list. Uploading to my launchpad ppa is no problem. Do I have to upload gpg keys to devu too (they are allready at launchpad)?
[10:53] <danielrichter200> this is my dput.conf:
[10:53] <danielrichter200> [revu]
[10:53] <danielrichter200> fqdn = revu.ubuntuwire.com
[10:53] <danielrichter200> incoming = /incoming
[10:53] <danielrichter200> login = anonymous
[10:53] <danielrichter200> progress_indicator = 2
[10:53] <danielrichter200> allow_unsigned_uploads = 0
[12:52] <c2tarun> i have an issue with chroot. this comes under ubuntu operations (so i know that this is not the place to ask) but no one is able to solve my problem can i ask it here
[14:33] <pqatsi> a question about package naming:
[14:33] <pqatsi>   wireshark-common: Depends: libwireshark0 (>= 1.4.2-1) but 1.4.2-1~exp2 is to be installed.
[14:33] <pqatsi>   wireshark: Depends: libwireshark0 (>= 1.4.2-1) but 1.4.2-1~exp2 is to be installed.
[14:34] <pqatsi> i cant understand why apt cant see the version number is the same
[14:34] <pqatsi> even with ~exp2
[14:35] <pqatsi> ok i use to make packet names like 1.4.2-1ppa1 as example
[14:35] <pqatsi> but i think apt should recognize this notation. what is wrong?
[14:36] <jcfp> pqatsi: 1.4.2-1~exp2 is smaller than 1.4.2-1, you depend on >= so it won't work
[14:36] <jcfp> >= 1.4.2-1~ might work, not sure though
[14:36] <pqatsi> jcfp: what passed me by i cant see
[14:36] <pqatsi> ?
[14:37] <jcfp> that the tilde lowers the version
[14:37] <pqatsi> hmmm
[14:37] <jcfp> i.e. 1.0-1~foo is smaller than 1.0-1
[14:37] <pqatsi> just tilde do this?
[14:37] <jcfp> afaik
[14:37]  * pqatsi think its weird....
[14:38] <jcfp> that's why it's used with ppa, makes ppa lower than official repository
[14:38] <coolbhavi> jcfp, exactly
[14:38] <pqatsi> jcfp: but this case something conflicts
[14:38] <coolbhavi> pqatsi, are you installing from PPA?
[14:39] <pqatsi> coolbhavi: this package, yes.
[14:39] <pqatsi> but i didnt realize ~lower the version even for =
[14:39]  * pqatsi think it will repackage this
[14:40] <coolbhavi> pqatsi, thats how ppa's are named as jcfp mentioned
[14:40] <pqatsi> coolbhavi: i know, but i didnt realized tilde breaks =
[14:40] <pqatsi> if the version is the same number
[14:41] <pqatsi> (major and minor)
[14:41] <coolbhavi> pqatsi, hmm
[14:41] <pqatsi> i used to think tilde brokes only if version is +1 bigger
[14:41] <pqatsi> and if version is equal and have both packages in repos, the priority of ppa got lowered
[14:42] <pqatsi> anyway
[14:42] <pqatsi> i think the packager made a mistake
[14:45] <pqatsi> Version: 1.4.2-1~exp2 // Depends: libc6 (>= 2.7), libgdk-pixbuf2.0-0 (>= 2.21.6), libglib2.0-0 (>= 2.24.0), libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.14.0), libpcap0.8 (>= 0.9.8), libportaudio2 (>= 19+svn20100220), libwireshark0 (>= 1.4.2-1), libwiretap0, zlib1g (>= 1:1.1.4), wireshark-common (= 1.4.2-1~exp2)
[14:45] <pqatsi> coolbhavi: the packager forgot to satisfy the libwireshark0 dep.
[14:46] <coolbhavi> hmm what do you exactly want to do?
[14:47] <coolbhavi> as i see new version of wireshark was uploaded to natty just a while back
[14:47] <pqatsi> coolbhavi: before, install wireshark from this ppa
[14:47] <pqatsi> now, ill fix this deps
[14:47] <pqatsi> coolbhavi: suggesting backport?
[14:47] <coolbhavi> pqatsi, reason?
[14:48] <pqatsi> coolbhavi: no reason, i just need wireshark, and i dont know why this repo are here, but if i have this error, i want to fixit
[14:48]  * pqatsi want to improve packaging skills
[14:49] <coolbhavi> pqatsi, okay but unless you have a strong reason no need of a backport request
[14:49] <pqatsi> coolbhavi: i do just for me
[14:50] <pqatsi> coolbhavi: my main backport project now is backport emdebian tools from debian unstable to stable (for a job) and after, to ubuntu
[14:50] <coolbhavi> pqatsi, then its fine but officially you need to have a valid reason
[14:50] <pqatsi> coolbhavi: i know. oficially dont need a backport
[14:50] <pqatsi> just for me
[14:51] <coolbhavi> pqatsi, okay :)
[14:51] <pqatsi> but if the emdebian job finish well, i will try submit for revu
[15:01] <coolbhavi> hey ari-tczew
[15:01] <coolbhavi> how are you doing?
[15:01] <ari-tczew> hello coolbhavi
[15:01] <ari-tczew> I'm quite fine, thanks. how about you?
[15:03] <coolbhavi> ari-tczew, I m fine too mate shall I take a look at enna ftbfs now?
[15:05] <ari-tczew> coolbhavi: do you ask me to do it?
[15:06] <coolbhavi> ari-tczew, if you have no issues ll take a look so
[15:06] <ari-tczew> coolbhavi: go ahead
[15:06] <coolbhavi> ari-tczew, thanks!
[15:12] <ari-tczew> you're welcome
[15:45] <pqatsi> Rejected:
[15:45] <pqatsi> Not permitted to upload to the RELEASE pocket in a series in the 'CURRENT' state.
[15:45] <pqatsi> and just this error, have no another issue in the mail
[15:45] <pqatsi> ive used maverick as series
[15:45] <pqatsi> after this ive tried to change to stable, but said series dont exist
[15:46] <ari-tczew> pqatsi: use natty - current development cycle.
[15:46] <pqatsi> eeven if the package ill send to ppa is specifically for maverick
[15:46] <pqatsi> ?
[15:47] <ari-tczew> !sru | pqatsi
[15:47] <ubottu> pqatsi: Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[15:48] <pqatsi> ari-tczew: im building for ppa, and must to be available for maverick
[15:49] <ari-tczew> pqatsi: so I guess that problem is with version in debian/changelog
[15:49] <ari-tczew> add to version ~maverick1
[15:50] <pqatsi> and keep maverick?
[15:50] <ari-tczew> pqatsi: yes
[15:51] <pqatsi> Last: (20070115-14) unstable; urgency=low // Now:  (20070115-15~maverick1) maverick; urgency=low
[15:51] <pqatsi> this way?
[15:51] <ari-tczew> pqatsi: no no no! please don't change Debian revision
[15:51] <ari-tczew> please keep -14
[15:52] <pqatsi> even if im patching souce?
[15:53] <ari-tczew> pqatsi: let use: (20070115-14ubuntu1~maverick1)
[15:54] <pqatsi> ok
[16:03] <pqatsi> dont work
[16:03] <pqatsi> Rejected:
[16:03] <pqatsi> Not permitted to upload to the RELEASE pocket in a series in the 'CURRENT' state.
[16:03] <pqatsi> aiccu (20070115-15ubuntu1~maverick1) maverick; urgency=low
[16:04] <pqatsi> aff, now i saw i didnt reverted
[16:04] <pqatsi> sry
[16:04] <ari-tczew> [;
[16:15] <pqatsi> aiccu (20070115-14ubuntu1~maverick1) maverick; urgency=low
[16:15] <pqatsi> again, same error ari-tczew
[16:15] <pqatsi> this never happened with me, i cant understand why
[16:17] <ari-tczew> pqatsi: could you give me a link to your PPA?
[16:18] <pqatsi> https://launchpad.net/~leleobhz/+archive/ppa
[16:19] <mr_pouit> pqatsi: are you sure you're uploading to your ppa? (and not the ubuntu archive)
[16:19] <pqatsi> ill run dput verbatin
[16:19] <pqatsi> let me see
[16:19] <ari-tczew> that's what I wanted to ask
[16:19] <ari-tczew> what is the command which you use pqatsi?
[16:20] <pqatsi> use dput directly, but use .dputrc
[16:20] <pqatsi> ill recreate the . file
[16:20] <ari-tczew> it should be: dput ppa:leleobhz/ppa *.changes
[16:25] <pqatsi> something with my dputrc are wrong... forcing repo in commandline appeared to work
[18:06] <wolfrage> Hi I want to confirm a few things. One you can not make blueprints for a PPA in launch pad correct?
[18:08] <ari-tczew> wolfrage: -> #launchpad
[18:09] <wolfrage> but the question relates to development
[18:09] <wolfrage> just trying to get the process for Ubuntu down.
[18:09] <wolfrage> With that in mind is it ok to create a project for a patch that I am creating. The patch is actually a feature plugin. It is for Empathy/Telepathy in order to support OTR.
[18:10] <wolfrage> I basicly want this because i want to be able to share blueprints and allow others to help me, as I have gotten a few people together that have offered to help.
[18:18] <wolfrage> #launchpad is not answering my second question, so as the MOTU, what do you say? Is it ok to use Luanch Pad in this way?
[18:30] <wolfrage> I got an answer now.
=== emma is now known as em
[21:56] <ari-tczew> gilir: how is going progress of sync lxpanel and lxde-common?
=== paultag_ is now known as paultag
[23:34] <gilir> ari-tczew, I'm on it, changes for lxpanel are already in Ubuntu, lxde-common needs changes with the new pcmanfm
[23:34] <ari-tczew> gilir: so, can we sync lxpanel?
[23:35] <gilir> ari-tczew, no, there are specific Ubuntu changes that can't be sync with Debian
[23:36] <ari-tczew> gilir: and these changes are not forwardable?
[23:36] <gilir> ari-tczew, no
[23:37] <ari-tczew> ok, so package needs merging then
[23:37] <gilir> ari-tczew, I can upload to Debian LXDE packaging, so I have no interest to maintain delta with Ubuntu when it's not necessary
[23:38] <ari-tczew> gilir: would be nice
=== em is now known as emma