| === almaisan-away is now known as al-maisan | ||
| === al-maisan is now known as almaisan-away | ||
| TheLordOfTime | is there any way to force-ignore this error? since the package is heading to a PPA. dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address (and i'm not supposed to change the Maintainer: field) | 12:12 |
|---|---|---|
| tumbleweed | TheLordOfTime: I think persia is giving you pretty good advice in #ubuntu-packaging | 12:12 |
| TheLordOfTime | tumbleweed: which is going against what's already in palce on my system | 12:13 |
| TheLordOfTime | tumbleweed: i've had DEBEMAIL set for my @ubuntu.com email for the past 6 months. otherwise, the system can't ID what signing key to use. | 12:13 |
| tumbleweed | TheLordOfTime: there are only two solutions, and he's suggested both of them | 12:13 |
| === glebihan_ is now known as glebihan | ||
| Laney | mfisch: merci | 16:34 |
| cjwatson | TheLordOfTime: I set DEBSIGN_KEYID to an explicit key ID in ~/.devscripts, rather than having debsign work it out from my e-mail address. You could do that. | 18:02 |
| obounaim | Hello | 18:02 |
| TheLordOfTime | true, i'll have to set that next time i stab my .devscripts | 18:02 |
| TheLordOfTime | i'll do that later this evening, after i replace a few componetns in my system. | 18:03 |
| obounaim | Why http://qa.ubuntuwire.com/bugs/rcbugs/raring/ does not show http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23619677 | 18:03 |
| jtaylor | probably because its tagged kfreebsd | 18:05 |
| obounaim | jtaylor, thanks. | 18:48 |
| obounaim | To upload a source package to a ppa, does it have to be signed, I want to test if a debian source package builds correctly on amd64? | 18:49 |
| TheLordOfTime | obounaim, you still need to sign the package with a GPG key that is on launchpad. | 18:50 |
| TheLordOfTime | for it to work with PPAs. | 18:50 |
| TheLordOfTime | (even if the architecture is amd64 only) | 18:50 |
| obounaim | How can I do that without modifying the changelog | 18:52 |
| TheLordOfTime | out of curiosity, what "package" are you test-building? | 18:53 |
| obounaim | gfarm2fs | 18:54 |
| TheLordOfTime | this for a bugfix or something? | 18:54 |
| obounaim | I want to see if syncing the new version from Debian will fix an existing bug in Ubuntu #837317 | 18:56 |
| ubottu | Ubuntu bug 837317 in gfarm2fs (Ubuntu Oneiric) "gfarm2fs ftbfs in oneiric on all archs except i386" [High,Fix released] https://launchpad.net/bugs/837317 | 18:56 |
| obounaim | I have an i386 Ubuntu on my machine so I want to use a ppa to see if it builds correctly on amd64 | 18:56 |
| * TheLordOfTime checks something | 18:57 | |
| TheLordOfTime | https://launchpad.net/ubuntu/precise/+source/gfarm2fs/+builds | 18:58 |
| TheLordOfTime | looks like somewhere along the line it built for all archs | 18:58 |
| TheLordOfTime | any specific Ubuntu verison you're looking at? | 18:58 |
| TheLordOfTime | (also, that bug you posted, its "Fix Released" for Oneiric) | 18:59 |
| TheLordOfTime | s/posted/referenced/ | 18:59 |
| obounaim | I agree the current version in Ubuntu builds on all version, What I am trying to do is to see if the new version of the package in Debian fixes the #837317 bug | 19:01 |
| obounaim | in order to drop Ubuntu changes and sync the new version of Debian, or if the build fails do a merge | 19:02 |
| TheLordOfTime | ah. | 19:02 |
| TheLordOfTime | well i've done test-ports myself of $various_debian_packages, and modified thechangelogs for one of my testing PPAs. | 19:03 |
| TheLordOfTime | working on php5.4.x ports from Debian to Precise right now for a PPA of mine, same concept. | 19:04 |
| TheLordOfTime | just create a changelog entry saying no-changes build-test from Debian or something. | 19:04 |
| TheLordOfTime | unless the MOTUs say that's bad | 19:04 |
| TheLordOfTime | or someone who's higher up the food chain than me :P | 19:04 |
| obounaim | So there is now way to sign a source package without changing the changelog | 19:04 |
| TheLordOfTime | that's not what i said? | 19:04 |
| obounaim | sorry | 19:04 |
| TheLordOfTime | actually i misinterpreted you | 19:05 |
| TheLordOfTime | you might be able to reupload the debian source package, but... the PPAs might not accept it | 19:05 |
| TheLordOfTime | if i remember right the PPA builders check the signature... | 19:06 |
| obounaim | I tried "dput -u" but it didn't work | 19:06 |
| TheLordOfTime | what error(s)? | 19:06 |
| obounaim | I had no errors but the package didn't show up in the ppa | 19:06 |
| tumbleweed | personally, my signing is untirely disconnected from building | 19:06 |
| TheLordOfTime | tumbleweed, doesn't the PPA processor check PGP key signatures on uploads? | 19:07 |
| tumbleweed | I have DEBUILD_DPKG_BUILDPACKAGE_OPTS="-i -I -uc -us" so, it never signs when I build | 19:07 |
| tumbleweed | I sign with debsign before uploading | 19:07 |
| * TheLordOfTime reads the manpage for those commands. | 19:08 | |
| tumbleweed | (I build source packages at least 20x more often than I sign and upload them) | 19:08 |
| TheLordOfTime | s/commands/arguments/ | 19:08 |
| tumbleweed | err I should have said "in my ~/.devscripts" | 19:08 |
| TheLordOfTime | tumbleweed, he's testing amd64 builds, not i386 which is his system's architecture. | 19:08 |
| TheLordOfTime | tumbleweed, same difference? :P | 19:08 |
| tumbleweed | and the -i -I are unrelated to signing | 19:08 |
| * TheLordOfTime assumed it was in ~/.devscripts | 19:08 | |
| tumbleweed | to be clear, when I said bulid there, I meant build locally (debuld / dpkg-buildpackage) | 19:09 |
| TheLordOfTime | also assumed. | 19:10 |
| TheLordOfTime | having said this, i think what obounaim's goal is, is to use the PPAs to test whether amd64 builds in Ubuntu for the Debian version of the package they mentioned | 19:10 |
| tumbleweed | obounaim: do you not have amd64-capable hardware? | 19:11 |
| TheLordOfTime | but upload without signing it themselves or without makikng a changelog entry | 19:11 |
| tumbleweed | using PPAs for test-building is fairly painful, because PPA builds can take a while... | 19:11 |
| TheLordOfTime | tumbleweed, for the record: <obounaim> I have an i386 Ubuntu on my machine so I want to use a ppa to see if it builds correctly on amd64 | 19:11 |
| TheLordOfTime | (scrollbacks, i know) | 19:11 |
| TheLordOfTime | and i agree, amd64 builds are obscenely long wait times | 19:11 |
| tumbleweed | how does one still get i386 hardware? | 19:11 |
| * TheLordOfTime has run into this twice in three days | 19:11 | |
| TheLordOfTime | tumbleweed, some older netbooks >3 years old are i386 only | 19:11 |
| tumbleweed | that's true | 19:11 |
| obounaim | TheLordOfTime, That's true I don't have amd64-capable hardware. | 19:11 |
| TheLordOfTime | and of course ancient machines. | 19:12 |
| obounaim | I have amd64-capable hardware but I have a i386 of Ubuntu to be correct | 19:13 |
| TheLordOfTime | well there's the problem. | 19:13 |
| tumbleweed | you can install an amd64 kernel, and then you'll be able to have amd64 chroots | 19:13 |
| TheLordOfTime | what tumbleweed said. | 19:13 |
| obounaim | How can I do that? | 19:16 |
| tumbleweed | hrm, Ubuntu dosen't have -amd64 kernels, so I assume you'd do it with multiarch | 19:20 |
| obounaim | I have signed the .changes file with debsign and upload it to a ppa but it was rejected "Rejected:Unable to find distroseries: unstable: | 19:22 |
| tumbleweed | PPAs don't build for Debian | 19:22 |
| Laney | you can override the target suite at upload time | 19:24 |
| Laney | https://help.launchpad.net/Packaging/PPA/Uploading#Using_packages_from_other_distributions | 19:24 |
| bdrung | Quintasan_: poke | 21:59 |
| bdrung | Quintasan_: now it's your turn to sign my key | 22:00 |
| thedoctor | i have a question about a package i would like to see carry through | 23:27 |
| thedoctor | i would like to see the browser "Opera" come to the universe | 23:29 |
| thedoctor | is this a good endeavor? | 23:29 |
| jtaylor | its closed source | 23:31 |
| jtaylor | so not going to happen | 23:31 |
| jtaylor | opera provides an own repository which works fine | 23:31 |
| thedoctor | so how come other closed source software are on the universe? | 23:55 |
| jtaylor | example? | 23:56 |
| xnox | "Opera" can enter the extras repository or restricted, if Opera the vendor decides to distribute it there. | 23:56 |
| jtaylor | for restricted you'd have to deal with canonical or? | 23:57 |
| jtaylor | it could go into multiverse but I don't see the need | 23:57 |
| xnox | Opera needs to allow re-distribution. It's illegal to take software and redistribute it, unless you have permission to do so (which there is a permission to do so) | 23:57 |
| xnox | thedoctor: if you want Opera in Ubuntu, you need to ask/push Opera to do so. | 23:57 |
| jtaylor | I'm an opera user myself | 23:58 |
| jtaylor | I just use the repository opera themself provide | 23:58 |
| jtaylor | never had issues | 23:58 |
| xnox | jtaylor: no. restricted & multiverse are both component of Ubuntu. And both require permission to redistribute. | 23:58 |
| xnox | jtaylor: "partner" repository is via canonical. | 23:58 |
| thedoctor | Okay i was wondering why this hadnt happened yet, | 23:58 |
| thedoctor | makes sense | 23:58 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!