/srv/irclogs.ubuntu.com/2013/04/08/#ubuntu-devel.txt

lifelesswhy isn't there a linux-image-generic package on armhf ?02:30
mwhudsonlifeless: what would that be?02:39
mwhudsonlifeless: currently kernels are soc-specific02:39
lifelessmwhudson: maybe a placeholder.02:42
lifelessmwhudson: I thought the Linaro project was to make the soc-specificness go away?02:42
mwhudsonit's working on it02:42
mwhudsonfar from done yet aiui02:42
mwhudsonand will probably never make a kernel that boots on all boards currently supported by ubuntu afaik02:44
mwhudsonmore future focused02:44
cpatrick08 I was wondering if there has any new info on the rolling development, how to activate it.03:37
=== LoganCloud_ is now known as LoganCloud
=== mmrazik is now known as mmrazik|afk
pittiGood morning06:08
ionthat06:16
dholbachgood morning06:44
ionthat06:46
=== ttx` is now known as ttx
=== smb` is now known as smb
=== henrix_ is now known as henrix
=== Guest80225 is now known as panda|x201
=== tkamppeter__ is now known as tkamppeter
=== mmrazik is now known as mmrazik|afk
mlankhorstcould someone approve xorg-server?09:47
mlankhorstin raring09:48
pittitjaalton: FYI, PPA mesa has run here since the morning09:48
mlankhorst\o/09:49
pittitjaalton: I didn't notice any regression yet, except that bringing up the dash is very slow09:49
pittibut TBH I don't remember how slow it was with the current raring mesa09:49
mlankhorstit's slow on llvmpipe too09:49
pittislow == I see about 5 "slides" which last ~ 0.2 s each09:49
pittiso it's far from a proper fading effect09:50
smbYou won't know how slow until you try llvmpipe on an atom... :-P09:50
pittismb: oh, I do09:50
pittiI'm talking about my X201 here (intel arrandale)09:50
smbpitti, but that is i915 isn't it? That would not be llvmpipe?09:50
mlankhorstsmb: which I did? :P09:51
pittismb: yes; I meant that I know how unity feels on llvmpipe on an arm or netbook as well09:51
smbmlankhorst, Yeah, me too ... unfortunately did not realize the new poulsbro trap09:51
mlankhorstsome old asus eee with pineview graphics, i tried software fallback for giggles09:52
smbpitti, Ah yeah09:52
smbmlankhorst, That box is an Intel Atom with gma500 (2D only integrated). By the time anything happens one already things the keypress/mouseclick did not get accepted. There is not really a way around the slowness but having fad-in and -outs for everything does not help either. ;-P09:55
mlankhorstyeah unity needs to disable whatever is causing the slowness (blur, I guess?) for llvmpipe and slower laptops09:56
seb128mlankhorst, it does disable it09:58
seb128on llvmpipe at least09:58
=== doko_ is now known as doko
smbNot sure it would be visible there, in ccsm it "dash blur" was set. But disabling it did not change anything either.10:01
tjaaltonpitti: thanks for testing!10:07
tjaaltonpitti: about the slowness; is it any worse than before?10:07
pittitjaalton: would it be helpful to downgrade to raring again, and compare?10:07
pittiah, snap :)10:07
tjaaltonyeah10:07
pittitjaalton: ok, will do10:07
tjaaltonlibgl1-mesa-dri, -glx should do10:07
tjaaltonhmm or not10:08
pittiI'll just use ppa-purge10:08
tjaaltonah, right10:08
mptA crash in apport-retrace? That must mean I win a prize of some sort.10:31
mptNow, will that crash itself be retraced...10:31
=== ubott2 is now known as ubottu
pittimpt: no need to retrace Python crashes :)10:32
=== ckpringle_ is now known as ckpringle
=== security is now known as fire
=== statik_ is now known as statik
pittitjaalton: dash reveal/hide is a lot faster with raring's mesa10:41
tjaaltonpitti: bah10:43
tjaaltonso it's gen5 too..10:43
tjaaltongen6%7 got fixed10:43
tjaaltonthe regression that is10:44
mitya57pitti: any news about https://code.launchpad.net/~mitya57/debian/sid/calibre/remove-embedded-libraries/+merge/157195 ?10:58
pittimitya57: still on my list; last week was too short (holidays) and too busy (psql security update), sorry11:00
mitya57thanks pitti!11:02
mitya57Maybe I'll look at some of the "Known issues" this week11:02
=== geser_ is now known as geser
tjaaltonpitti: do you think the performance is so bad that it would block the update? anholt isn't online so can't ask how long it would take to get fixed11:05
=== MacSlow is now known as MacSlow|lunch
Riddelljtaylor: you added a patch to pyqt?11:36
pittitjaalton: it's certainly bearable, but it looks quite ugly11:36
Riddelljtaylor: I think it's making pykde fail11:36
dpmHi all, I don't seem to be able to properly boot my laptop anymore on raring: I get this error - "mountall: could not mount filesystem: /boot"12:13
dpmAny ideas on what I could do or look at to fix it?12:14
dpmI've ran fsck and it complains about "ext2" filesystem not recognized12:14
cjwatsonext2 might be modular and for some reason missing or unloaded12:16
dpmcjwatson, I'm not sure. For some reason, if I skip the prompt to load /boot, the system boots to lightdm, I can then log in, but there is no network12:18
=== MacSlow|lunch is now known as MacSlow
dpmI've now removed the hard disk, plugged it into my desktop, and after entering the encryption passphrase nautilus tells me it cannot mount it due to an unrecognized file system12:21
=== highvolt1ge is now known as highvoltage
dpmdoes anyone know how I can mount the encrypted volume from the command line? That might give me more of a clue what the error is12:25
pittidpm: udisksctl unlock -b /dev/sdXXX; udisksctl mount -b /dev/mapper/XXX ?12:41
dpmlet me try12:44
pittidpm: oh, this won't work in an initramfs shell, if you meant that12:45
pitti(just read some backscroll)12:45
=== _salem is now known as salem_
dpmpitti, I've got the disk attached to my desktop PC now, I thought I'd run fsck over it. I've tried to mount it with nautilus and it fails after entering the encryption passphrase. I'm trying to mount it manually now. I tried these instructions: http://askubuntu.com/a/63598/9781 but the "sudo mount /dev/mapper/my_encrypted_volume /media/my_device" step fails with "mount: unknown filesystem type 'LVM2_member'"12:51
dpmso shall I try your commands now, as in "udisksctl unlock -b /dev/sdb5; udisksctl mount -b /dev/mapper/5" (where sdb5 is the encrypted partition)12:51
dpmpitti, I'm poking a bit in the dark here, so I'm not sure I did it right, but here's what I did: http://paste.ubuntu.com/5689323/12:56
=== ckpringle_ is now known as ckpringle
pittidpm: what does sudo blkid -p /dev/mapper/luks-9cf37a83-e84a-4b85-9bba-7bcbaba8058e say?13:01
dpmpitti, $ sudo blkid -p /dev/mapper/luks-9cf37a83-e84a-4b85-9bba-7bcbaba8058e13:03
dpm/dev/mapper/luks-9cf37a83-e84a-4b85-9bba-7bcbaba8058e: UUID="d7SXgb-eMNG-0jiA-E3EA-L0M2-VsSJ-3r5Xmo" VERSION="LVM2 001" TYPE="LVM2_member" USAGE="raid"13:03
mlankhorstcan some sru admin approve xserver-xorg-video-nouveau in quantal-proposed?13:03
dpmI believe it trips on the LVM2_member bit, which is where the other instructions I tried where failing13:03
pittidpm: oh, so it's partition-on-lvm-on-luks13:03
pittiI had expected our dmsetup/udev rules to automatically create the LVs for those13:04
dpmpitti, I've no idea what it is, that's what the installer created when I installed (I think) quantal on that hard disk13:05
dpmis there a way to mount it, so that I can try to recover my data?13:05
pittidpm: is that your only PV?13:06
dpmwhat's a PV?13:06
pittidpm: recent dmesg output might help to see what went on13:06
pitti"physical volume", i. e. the bits a VG (volume group) is built from13:06
pittidpm: wait, /dev/mapper/ubuntu-root, was that created by the udisksctl unlock command, or is that your desktop's LVM?13:08
xnoxdholbach: can you RT my twitter status to ubuntudev and collect answers? =) https://twitter.com/tdlk/status/32124821395906969613:10
xnoxdholbach: webteam is pondering how to convey the answers to those questions in less than 140 characters ;-)13:10
xnox(as that's the space we have on the website for such text)13:10
dholbachxnox, I collect answers?13:10
xnoxdholbach: just retweet it on the @ubuntudev to get exposure.  I will monitor the replies =)13:11
dholbachah ok - sure :)13:11
dpmpitti, to the first question: here's what the laptop disk I'm trying to recover looks like partitionwise: http://pastebin.ubuntu.com/5689356/13:11
xnoxdholbach: I'm not "popular" on twitter =)13:11
dholbachxnox, we could do the same on G+? there might be even more replies there13:12
pittidpm: I meant, are you using full disk encryption on your desktop (i. e. the machine you just plugged this in)?13:12
pittidpm: i. e. is /dev/mapper/ubuntu-root from your current host, or actually from the plugged in device?13:12
pittidpm: it might be that /dev/mapper/ubuntu-root is just the one you want to mount13:13
=== ckpringle_ is now known as ckpringle
pittidpm: sorry, back in 45 mins; I hope someone else can jump in in the meantime13:13
dpmpitti, I don't use full encryption on my desktop, just home directory encryption IIRC13:13
xnoxdholbach: sure =) but please add "In less than 3 sentences." Cause G+ allows one to write essays......13:13
pittidpm: otherwise, I'll need the contents of /dev/mapper/ before "unlock" and dmesg after13:13
dpmpitti, no worries, thanks for all your help13:13
dpmok13:13
pittidpm: ok, so udisksctl mount -b /dev/mapper/ubuntu-root it is13:13
dpmpitti, it worked! \o/13:14
dpmpitti, ok, now I'll save all data first, and then will try to find out what's going on. Is there any extra step I need to do to unmount the encrypted volume?13:15
PjotrHello, I have a question about the Ubuntu download page13:50
PjotrPerhaps it's a good idea to present the LTS version as the primary eye-catching download option. Not as a "mere"second option. So that beginners with Ubuntu, will usually pick the LTS.13:51
PjotrReason: as we know, starting with Raring, support for intermediate ("standard") releases will be halved to nine months.13:51
PjotrAs Mark Shuttleworth said: "Our working assumption is that the latest interim release is used by folks who will be involved, even if tangentially, in the making of Ubuntu, and LTS releases will be used by those who purely consume it." http://www.markshuttleworth.com/archives/124613:51
PjotrThe main issue here is support period, I think. It's not nice for a beginner to be forced to upgrade very quickly...13:51
PjotrWhat do you think?13:51
=== mogri is now known as kaniini
jcastroI believe there's a bug open to change the page to default to LTS13:54
jcastroI know I've seen it, I just don't have it handy13:54
=== fginther` is now known as fginther
stokachuis there a "mentor" irc channel for someone like bug 116592714:05
ubottubug 1165927 in Ubuntu "List with CRITICAL tons of bugs, dont have the time to add them seperately" [Undecided,Invalid] https://launchpad.net/bugs/116592714:05
dobeystokachu: #ubuntu-bugs maybe? (is that even a channel?)14:07
stokachuah looks to be the closest thing14:08
stokachuthanks dobey14:08
pittidpm: \o/14:09
dobeyi'd mark it invalid with a note that they need to be filed separately. if one doesn't have the time to file bugs separately, i haven't got time to sort through the crap and fix them either :)14:09
pittidpm: eject it in nautilus, or udisksctl unmount -b /dev/mapper/14:09
stokachudobey: agreed14:09
=== Simira_ is now known as Simira
dpmpitti, thanks!15:00
dpmdobey, sorry it took a while, approved the e-mail now15:00
=== ckpringle_ is now known as ckpringle
dobeydpm: thanks15:04
=== mbiebl_ is now known as mbiebl
dholbachbarry, thanks15:16
barrydholbach: sure thing15:18
=== stgraber_ is now known as stgraber
dokoDktrKranz, could you have a look at https://launchpadlibrarian.net/136234437/buildlog_ubuntu-raring-armhf.pyexiv2_0.3.2-5ubuntu1_FAILEDTOBUILD.txt.gz ? looks like scons does add the arch specific include path only15:34
dokojodh, cking: $ apt-cache -n search smatch15:41
doko$15:41
DktrKranzdoko: probably not before the weekend, unfortunately15:42
jodhdoko: it's not in the archive, apparently as it specifies no license.15:49
stokachudobey: hopefully these new patches dont suck15:49
zaytsevcjwatson: hi colin, could you please be so kind to tell me if scripts/casper-bottom/25adduser runs with set -e or set +e? there is nothing at the top of the script. the reason why i'm asking is that i'd like to know whether everything will break if i just delete /usr/share/applications/ubiquity-gtkui.desktop or it will work still15:50
zaytsevcjwatson: the reason why i'm looking for a solution as simple as deleting the file is that i want to avoid rebuilding the ram disk if at all possible15:51
stokachudobey: didn't see your attachment until now :\15:51
stokachudobey: fortunately it is the same as yours15:51
dobeystokachu: it is not the same :)15:52
dobeystokachu: you applied my changes to the packages from the wrong pocket15:53
stokachui pulled from whats out in the archive15:54
dobeyyou pulled from the release pocket, not from proposed15:54
stokachudamnit15:55
cjwatsonzaytsev: +e, although you do need to make sure that the last command in the script exits 015:56
cjwatsonzaytsev: (but that should be fine here)15:56
zaytsevcjwatson: thank you very much! it seems to work15:57
infinityBenC: *nudge*16:05
infinityBenC: I can haz linux-ppc rebase?16:06
stokachudobey: do you mind looking over my precise debdiff now?16:12
zygaxnox: ping16:13
zygaxnox: I've got most of the data now ready, I will probably have the first version of the new data file for raring x86 amd64 this evening16:14
xnoxawesome.16:14
zygaxnox: if my mirror is not finished on time I will have evetything by tomorrow16:14
zygaxnox: I had a look at the new data16:14
zygaxnox: I will need to go through some manual cases (currently about 200 of them) to manually extract alternative updates16:14
zygaxnox: but it looks better than old data already16:15
xnoxhmmm...16:15
xnoxzyga: if it has upstart-monitor in it, I will be happy =)16:15
zygaxnox: with the exception of certain packages that are in the manual section (like vim or emacs)16:15
zygaxnox: let me check :)16:15
zygaxnox: althouh u- is far in the mirror, I'm earlier than that :)16:15
zygaxnox: unlike the old solution this one is very correct16:16
zygaxnox: and should have no false positives16:16
xnoxcool.16:16
zygaxnox: and absolutely no missing items16:16
zygaxnox: I wrote a post about c-n-f just now, it's on planet ubuntu16:16
zygaxnox: so maybe there will be more interest in fixing the actual user experience for remote uers16:16
zygausers16:17
xnox=)16:17
=== danjared_ is now known as danjared
t1mpmhall119: ping16:21
=== salem_ is now known as _salem
jbichahi, could someone from the SRU team take a look at bug 1128804? it's been sitting in the quantal queue for 6 weeks now16:28
ubottubug 1128804 in mutter (Ubuntu Quantal) "Update mutter/gnome-shell to 3.6.3" [Medium,In progress] https://launchpad.net/bugs/112880416:28
infinityjbicha: Can you do me a favour and nudge me about that again in ~3h?  I have a series of poking and prodding appointments to get to today, but will be SRUy when I get back.16:37
jbichainfinity: sure, thanks16:39
mhall119t1mp: pong16:40
t1mpmhall119: I was just reading http://mhall119.com/2013/04/building-an-ubuntu-sdk-app-rev-1/16:40
t1mpmhall119: nice post. But I noticed something with the header that I though I might help with16:40
t1mpmhall119: the spacing between the header and first list item is a bit too big. If you do not set anchors for Page/PageStack/Tabs, it should all be automatic for you.16:41
t1mpmhall119: but since I pinged you I noticed 2 things: 1. You use a custom header in newer revisions, and 2. In raring archives is 0.1.38 of the ui-toolkit and I fixed some header behavior/spacing in 0.1.39.16:41
ckingdoko, you're most welcome to package up smatch ;-)16:42
t1mpt1mp: so my comments may not be that valid anymore.  But if you want to use the SDK header you can always ping me if there are issues with it. :)16:44
t1mpmhall119: ^16:44
BenCinfinity: Yep, will do within some hours16:46
mhall119t1mp: reading and eating at the same time, I'll be a bit slow16:47
t1mpmhall119: ok :)16:47
mhall119t1mp: yeah, the header's behavior changed between when I wrote that code and when I went back for a screenshot16:47
t1mpmhall119: if you want to try stuff with the SDK header, make sure you have qtdeclarative5-ubuntu-ui-toolkit-plugin version 0.1.40 because since 0.1.38 some issues were fixed.16:48
mhall119t1mp: ok, do we have updated docs I can push to developer.u.c/api/?16:49
mhall119some things there look out of date too16:49
t1mpyes! we have updated docs.16:49
t1mpit is out of date, but I don't know the process to get it from our bazaar repository to the website16:50
mhall119where?16:50
t1mpthe documentation is automatically generated from the source with qdoc.16:50
t1mpmhall119: if you check out lp:ubuntu-ui-toolkit there is a documentation/generate_html.sh that creates the html.16:51
mhall119dpm: ^^ can we automate that on developer.u.c?16:51
t1mpmhall119: there are big changes with a bunch of new examples for pagestack, page, mainview, tabs16:52
t1mp^+ToolbarActions16:53
mhall119t1mp: and there are all in the PPA for quantal, as well as the archives for raring?16:53
t1mpmhall119: no, I just discovered that they are not.16:55
t1mpmhall119: they are in our ppa https://launchpad.net/~ubuntu-sdk-team/+archive/ppa/+packages but not in the raring archives16:55
t1mpmhall119: but I'll check with Mirv tomorrow to figure out how to get it in the raring archives automatically16:55
dpmt1mp, mhall119, yeah, we can automate it when the Ubuntu theme is integrated into the documentation for the SDK. I've got a merge proposal I sent quite a while ago for that. If someone could help with getting that in, it'd be a lot less painful to update the documentation on d.u.c -> https://code.launchpad.net/~dpm/ubuntu-ui-toolkit/developer-style-api-docs/+merge/15256416:56
t1mpgreyback: you were reviewing that. Is there still something that needs to be fixed?16:57
greybackt1mp: see the last comment I made. Those were my thoughts at the time16:59
t1mpdpm: I get the same warnings as greyback mentioned.16:59
t1mpdpm: some css files are missing16:59
t1mpgreyback: ok thanks16:59
dpmt1mp, greyback I haven't looked at that branch in a while, let me do it now17:00
t1mpdpm: thanks17:00
greybackdpm: I'm still not liking that you integrate the whole theme into the SDK's repo. I'm surprised there isn't some server-side magic to add standard headers & footers to a bunch of HTML17:01
t1mpdpm: can you bzr merge lp:ubuntu-ui-toolkit to avoid problems with merging?17:01
greybackdpm: it'll do, of course. It just means lots of duplicate code spread around17:01
dpmt1mp, greyback, how are you getting those warnings? I'm running the generate_html.sh script and it does not give me any warnings17:01
t1mpdpm: maybe you need to add the css files to bzr because we don't have them.17:02
dpmtimp, I've just checked out the branch to /tmp, they are in bzr17:02
greybackdpm: run the 'qmake' command. It's the build system we're using. Some file paths specified in the qdoconf files are not correct17:02
* t1mp otp17:02
t1mpbrb17:03
dpmgreyback, from the top of the source tree, or on the documentation/ folder?17:03
greybackdpm: top17:03
=== _salem is now known as salem_
dpmok, trying that now17:03
mhall119greyback: in the future I would like to import qdoc output into a Django site that will add the theming17:03
dpmgreyback, in terms of server magic, I don't know of any way, so I'm open to any suggestions. In the future, as Mike is saying, we want to generate documentation differently17:04
greybackmhall119: sounds great!17:04
greybackdpm: ok17:04
mhall119greyback: but I'm going to need some qdoc expert help17:05
greybackmhall119: we'll be happy to help17:05
mhall119cool, thanks17:06
jtaylorRiddell: re pyqt, yes how does pyqt fail?17:10
jtaylorRiddell: I doubt its the patch but the change that forced as to add the patch17:11
dobeystokachu: better :)17:14
Riddelljtaylor: it was the patch, I've fixed it now17:14
jtaylorRiddell: have you forwarded it then?17:14
jtaylorRiddell:  its a patch from upstream17:14
Riddelljtaylor: yes, fix from upstream17:17
jtaylorgood17:18
jtaylorsomewhat bad that we have 4.10 in raring as it so buggy :/17:19
jtaylor+ the usual 10 version issues in other softare17:19
tedgIf I've got a binary package that another package has a build dep on it.  Will that package stick around until that build dep is changed?  Or does the non-purge only happen for binary deps?17:20
bdmurrayWhere does software-properties get the list of mirrors from?17:24
=== deryck is now known as deryck[afk]
=== salem_ is now known as _salem
=== _salem is now known as salem_
cjwatsontedg: it'll stick around in general, although if the package *version* changes such that the build-dep isn't satisfied any more then we probably won't notice that until the next test rebuild17:38
cjwatsonremovals are all manual though and we check both runtime and build dependencies for those17:38
dobeydoh, dpm is gone already?17:52
* dobey wonders if anyone else has moderator access to ubuntu-translators@17:53
stokachudobey: cool thanks man17:56
tedgcjwatson, Ah, cool.  We were curious about API transitions, how quickly we have to update.  For instance if the next branch landed has to have the update.  It sounds like no, which makes our lives easier.  Thank you.18:06
stokachujodh: ping18:07
stokachujodh: unping, roaksoax: ping18:08
jtaylordoko: we should update numpy in raring, it has some bad bugs, I can probably do so this weekend18:22
jtaylorto 1.7.1 bugfix release18:22
dokojtaylor, will this include a scipy update?18:29
jtaylorwhy?18:30
jtaylorthere is no bugfix release for scipy in raring so far I know18:30
jtaylorwe don't want 0.12 yet18:30
jtaylorit has major changes = high regression change18:30
dokoplease check that the scipy inraring builds with the updated numpy18:30
jtaylorit does18:31
jtaylorits only a bugfix release, no api changes18:31
jtayloralso we got autopkgtests for scipy18:31
dokook18:32
tjaaltonpitti: can you open a new bug about the arrandale mesa regression upstream on bugs.fd.o?18:33
tjaaltonor maybe just lp, I can forward it18:34
=== james_ is now known as Guest53945
cjwatsontedg: it has to be soon after; by default, a transition that involves changing library names won't land in raring (as opposed to -proposed) until all reverse-(build-)dependencies have transitioned20:12
cjwatsontedg: so the "no automatic removal" thing doesn't mean that this is something that can be put off - incomplete transitions become blockers for other people's work20:13
=== salem_ is now known as _salem
tedgcjwatson, So what gets blocked?  New versions of the lib or new versions of the apps using the lib?20:15
=== deryck[afk] is now known as deryck
=== _salem is now known as salem_
cjwatsontedg: yes20:20
cjwatsonsets of packages entering raring must form a coherent whole that doesn't regress installability; by default (though it can be forced with a very good excuse), this includes assuming that all no-longer-built-from-source binary packages are removed from the archive20:20
tedgcjwatson, Okay, so if someone was developing the package they'd still have the old versions until the trunk of their package updated.  So that works for my use-case.20:21
bdmurrayslangasek: any ideas about bug 1163920?20:41
ubottubug 1163920 in update-notifier (Ubuntu) "update-notifier doesn't go away when you press the close button" [Medium,Confirmed] https://launchpad.net/bugs/116392020:41
slangasekbdmurray: hmm, nope.20:44
slangasekbdmurray: if update-notifier didn't also generate a traceback, then I think the only way to debug it is to get a reproducer case first20:45
=== francisco is now known as Guest87879
Ploujhi22:27
=== salem_ is now known as _salem
PloujHow can I check if a package in my personal repository is signed correctly?22:28
PloujAlso, what kind of a check can I perform on my repository if I get a BADSIG error all the time, like this: http://askubuntu.com/questions/1877/what-is-the-easiest-way-to-resolve-apt-get-badsig-gpg-errors ?22:28
sarnoldPlouj: from that question, the answers that show how to delete the lists and remove those lists from any cachers you may be using, looked the most useufl22:33
Ploujsarnold: that doesn't work for me because I've tried those steps, and it actually happens on a clean Lucid install22:35
Plouj_and_ I'm the owner of the repo in question so I'm sure it's my fault, not some caching funkyness22:35
PloujI don't use any cachers that I know of22:36
sarnoldPlouj: aha.. hrm. I think you ought to be able to compare the md5/sha1 sums of packages against that in the package lists using standard md5sum and sha1sum programs...22:39
sarnoldPlouj: I _think_ only sources actually get signed; the binary packages are protected by having their hashes in the lists, and then the lists are signed22:39
sarnoldPlouj: perhaps your list signing operation is broken? is that key expired?22:40
cjwatsonwhile source packages are signed for the purposes of upload, as far as apt etc. is concerned they're verified in exactly the same way as binary packages, not by checking the signature on the .dsc22:42
Ploujhumm, the files listed in Release have the right md5sum sums22:48
Ploujand I don't see an expiration on the key22:51
cjwatsonProbably best to check all the sums, not just md5 - I'd hope apt would prefer the stronger ones22:51
cjwatsonAlso check the downloaded versions in /var/lib/apt/lists/22:51
cjwatson(Sorry, don't have time to debug this fully, just a few suggestions in passing)22:51
sarnoldcjwatson: re: apt and md5 and other hashes, It's Complicated: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/109873822:52
ubottuLaunchpad bug 1098738 in apt (Ubuntu) "apt-get source only checks md5 hashes in Sources files" [High,In progress]22:52
cjwatsonSources isn't likely to be relevant here22:53
sarnoldcjwatson: thanks for filling in some of my weaker understanding with the source packages handled the same as the binaries22:53
cjwatsonI mean, unless we're specifically talking about source packages rather than that being something that came up in passing22:54
sarnoldhrm, I thought that bug had grown to include more than just Sources22:54
cjwatsonAh, didn't read it I'm afraid :)22:54
sarnoldit's been a while for me, too :) hehe22:54
PloujI don't get why, after running 'do-release-upgrade', which fails with: Error authenticating some packages and apt-get update starts showing "W: GPG error: ... The following signatures were invalid: BADSIG..."23:07
Ploujno such problems before apt-get update23:07
Ploujthat's the main problem I'm trying to solve here23:09
sarnoldPlouj: can you validate the listst manually, using something like this? for f in *.gpg ; do gpg --verify $f ${f%.gpg}; done23:13
Ploujsarnold: do you mean in /var/lib/apt/lists/ ?23:39
PloujI don't seem to have a Release.gpg for my particular repo in that directory23:39
sarnoldPlouj: hrm. does your archive have the .gpg files?23:40
PloujI do have Release.gpg in /var/lib/apt/lists/partial/ ...23:41
Ploujsarnold: yes, the repo serves Release.gpg among others23:42
sarnoldPlouj: can you verify the files from the repo?23:43
Ploujyup, it verifies23:43
sarnoldPlouj: how about the one in partial/ ?23:44
Ploujit currently doesn't verify on the client because of: gpg: Can't check signature: public key not found23:45
Ploujbut sudo apt-key list shows the key....23:45
sarnoldPlouj: wget the file and diff them?23:46
Ploujwhere is apt's truststore?23:47
=== cinerama_ is now known as cinerama
PloujI mean keyring23:47
Ploujfound it23:48
sarnoldI think /var/lib/apt/keyrings23:48
Ploujyeah, it say bad signature23:48
=== rickspencer3_ is now known as rickspencer3
Ploujhumm, so Release.gpg matches what's on the server, but Release doesn't23:50
Ploujumm23:52
Ploujdiff shows:23:52
Plouj+-----BEGIN PGP SIGNED MESSAGE-----23:52
Plouj+Hash: SHA123:52
Plouj+23:52
PloujI wonder if gpg was upgraded on the server causing it to put the signature into the file itself...23:53
PloujI might have something to go on. Thanks sarnold23:55
sarnoldPlouj: good luck :)23:55
slangasekarges: ping23:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!