[04:02] <kklimonda> hmm.. LP died?
[04:02] <kklimonda> ah, it's back again
[04:10] <lifeless> kklimonda: what happened ?
[04:12] <kklimonda> lifeless: hmm.. something like "Couldn't connect to Launchpad, please wait and try again"
[04:12] <lifeless> please file a bug
[04:12] <lifeless> that was an edge update, which is meant to be zero-downtime.
[04:13] <kklimonda> lifeless: hmm, "a zero-downtime update wasn't zero-downtime"? :)
[04:14] <lifeless> kklimonda: 'got error page when using edge during an edge update'
[04:16] <kklimonda> lifeless: k, done
[04:16] <kklimonda> bug 631262
[04:16] <lifeless> jjthanks
[04:16] <lifeless> kklimonda: thanks
[04:21] <Laibsch> Is there anything wrong with the targets http://paste.debian.net/88062/ in ~/.dput.cf?  Whenever I upload a particular package to them it is refused with "The source apt-cacher-ng - 0.5.4-1 is already accepted in ubuntu/lucid and you cannot upload the same version within the same distribution."
[04:21] <Laibsch> that's strange for two reasons.  1) I'm uploading to maverick 2) even the lucid source in that ppa has been deleted a couple of days ago
[04:21] <Laibsch> 0.5.4-1 is in none of the official releases, yet.
[09:45] <madoman> Hi all ... I noticed that update "linux-image-2.6.32-24-generic" for 10.04 from update manager  makes my Dell E6510 boot to the "black" screen. I suppose this is a know bug? With "linux-image-2.6.32-23-generic" it works just fine. Seems that "black" screen boot is some know issue. But should this be reported as a new bug? Because it was delivered by the update manager.
[10:01] <statik> hi voidspace
[10:01] <voidspace> attempting to add a new email to my launchpad account fails - is this a known issue?
[10:01] <voidspace> statik: hi
[10:01] <voidspace> (Error ID: OOPS-1710E559)
[10:05] <lifeless> voidspace: hi.
[10:05] <voidspace> lifeless: hey - hi
[10:05] <voidspace> lifeless: which team are you on?
[10:06] <lifeless> voidspace: all of them :P
[10:06] <voidspace> lifeless: ha :-)
[10:06] <voidspace> lifeless: I just joined ISD
[10:06] <lifeless> voidspace: (it feels like that sometimes - I get /lots/ of mail - and my account (due to a bug) triggered 330 DB lookups on bug pages :P)
[10:06] <lifeless> voidspace: I'm the technical architect for launchpad at the moment
[10:06] <voidspace> :-)
[10:06] <voidspace> ah right, cool
[10:07] <lifeless> voidspace: I started in the roll, oh, 3 months back.
[10:07] <lifeless> voidspace: remember when I said 'thats nice, I promise I'll look but -boy- am I busy right now' ?
[10:07] <lifeless> that was ~ half way through week 1
[10:07] <voidspace> hehe
[10:07] <voidspace> so now you're three times as busy...
[10:07] <lifeless> actually, if things like up right for this release
[10:07] <lifeless> (thursday)
[10:08] <lifeless> we'll have vastly improved data in our OOPSes; won't be proxying massive files via the zope appservers...
[10:08] <lifeless> I should be able to sit back and look at the landscape a bit more.
[10:08] <voidspace> as in "the landscape"
[10:08] <lifeless> yes, not 'landscape' the product
[10:09] <lifeless>  Module lp.registry.browser.person, line 4631, in validate_action_add_email
[10:09] <lifeless>     owner_name = urllib.quote(owner.name)
[10:09] <lifeless> AttributeError: 'NoneType' object has no attribute 'name'
[10:09] <voidspace> ah
[10:09] <voidspace> so launchpad thinks I am a nobody, a None
[10:09] <voidspace> that makes me sad :-(
[10:09] <voidspace> ;-)
[10:09] <lifeless> try on edge
[10:09] <voidspace> edge?
[10:10] <lifeless> voidspace: oh, and welcome :)
[10:10] <voidspace> I got an interesting email from Ubuntu One on Saturday - I setup the iPhone integration and got an email with the repr of a Python object as my username :-)
[10:10] <voidspace> (thanks)
[10:10] <voidspace> thankfully I also got *another* email with my real username
[10:10] <voidspace> what do you mean by "try on edge"?
[10:10] <lifeless> voidspace: join this team
[10:11] <lifeless> https://edge.launchpad.net/~launchpad-beta-testers
[10:12] <lifeless> voidspace: edge is a thing we're about to delete :) - its 'get the latest changes and unreleased features' for launchpad
[10:12] <voidspace> lifeless: ah, cool - joined
[10:13] <lifeless> voidspace: we're moving to a single version deployed model, but we'll keep the latest-changes and unreleased features thing
[10:13] <lifeless> just via code switches instead.
[10:13] <voidspace> (Error ID: OOPS-1710EA751)
[10:13] <voidspace> (that's on edge.launchpad.net)
[10:17] <lifeless> voidspace: #launchpad-dev is a channel you might like
[10:17] <voidspace> lifeless: freenode?
[10:17] <lifeless> while in ISD you'll be on different stuff, the lp development channel is pretty active & we use many of the same toolchain
[10:17] <lifeless> yes
[10:18] <voidspace> ok - thanks
[10:18] <voidspace> I'm going through the new starter guys for Canonical / ISD team at the moment
[10:25] <voidspace> lifeless: sorry - computer issues...
[10:25] <lifeless> heh
[10:25] <lifeless> running Ubuntu yet ?
[10:26] <voidspace> lifeless: no :-) but hardware issues I think - or a video driver issue, not sure
[10:26] <voidspace> lifeless: once every few days I get hard crashes
[10:26] <voidspace> lifeless: I installed Ubuntu into a VM over the weekend and played with it
[10:26] <voidspace> lifeless: impressed :-)
[10:26] <voidspace> brb
[10:34] <noodles775> voidspace: fwiw, I've added a comment on bug 576757 for the registry guys.
[10:39] <lucidfox> How does the release pattern work?
[10:40] <lucidfox> I've just moved a project from Google Code to Launchpad - what would be the easiest way to import its old release tarballs?
[10:45] <voidspace> noodles775: thanks
[10:45] <voidspace> noodles775: would it be possible for an admin to delete the unused account - or should I do it?
[10:50] <noodles775> voidspace: yeah, it should be possible. Best way would be to create a question similar to the following, and reference that one (as the launchpad administrators solved it there): https://answers.edge.launchpad.net/launchpad/+question/109891
[11:04] <voidspace> noodles775: thanks - I'll do that
[11:08] <voidspace> noodles775: For the record: https://answers.edge.launchpad.net/launchpad/+question/124297
[11:17] <noodles775> voidspace: great, I've just assigned it to the losas (Launchpad admins)
[12:18] <AlanBell> hi all
[12:18] <AlanBell> is it possible to do a kind of read-only link to a launchpad bug?
[12:20] <AlanBell> so a bug could be referenced in a news publication as something interesting, but there would be an extra step for readers to jump through if they wanted to comment on the bug itself and would prevent accidental status changes etc.
[12:27] <voidspace> issue with setting location on launchpad (and edge.launchpad): "The google maps API server rejected your request. THe "client" parameter specified in the request is invalid"
[12:27] <lucidfox> How do I give someone else commit access to my project's bzr brunch?
[12:27] <nigelb> lucidfox: what is your branch named as?
[12:28] <nigelb> i.e. if its lp:~lucidfox, only you have access
[12:28] <lucidfox> lp:<projectname>
[12:28] <nigelb> if you make it lp:~teamfoo-dev, everyone will have access
[12:29] <nigelb> err. everyone in the team
[12:29] <lucidfox> Well, for example, here is one of my projects: https://code.edge.launchpad.net/~sikon/qink/trunk
[12:29] <lucidfox> its primary branch, that is
[12:29] <lucidfox> If I click "Set branch reviewer" and change it to a team, will it give the entire team commit rights?
[12:30] <nigelb> ~sikon/qink/trunk => the first bit says who has commit acces
[12:30] <ricotz> please, could someone restart https://launchpad.net/~xorg-edgers/+archive/ppa/+build/1945560 which is stuck!
[12:30] <nigelb> generally most folks on lp create a team to administer commit access
[12:30] <lucidfox> or will I need to manually create a branch for the team and import it?
[12:30] <nigelb> lucidfox: just rename? isn't it possible to rename the branch?
[12:30] <maxb> lucidfox: No, that only affects who does reviews. You need "Change branch details", and change the owner to a team
[12:30] <bigjools> ricotz: noted
[12:30] <nigelb> voidspace: known issue
[12:31] <lucidfox> maxb> Rightio! Thanks
[12:31] <voidspace> nigelb: cool
[12:31] <ricotz> bigjools, thanks
[12:31] <lucidfox> I've just migrated that project from Google Code, what would be the fastest way to import its old downloads?
[12:32] <lucidfox> there are 5 releases left to import, each with a .tar.gz and a .tar.bz2
[12:36] <lucidfox> Okay, guess I'll just upload them manually
[12:46] <MichealH> Hello Can someone tell me how I log into launchpad for bzr
[12:47] <nigelb> MichealH: can you clarify further?
[12:48] <MichealH> How do I make my whoami correct so I can login to lauchpad on bzr
[12:49] <bilalakhtar> MichealH: bzr whoami Micheal Harker <e-mail>
[12:49] <bilalakhtar> MichealH: and also bzr launchpad-login michealh
[12:50] <MichealH> Okay bilalakhtar
[12:50] <MichealH> I got told to pust to branches I needed a SSH key?
[12:51] <MichealH> *push
[12:58] <nigelb> gah, he left
[12:59] <nigelb> wgrant: Is this possible currently? https://answers.launchpad.net/launchpad/+question/124309
[12:59] <nigelb> (getting a url that shows the bug and comments, but no box to add comments)
[12:59] <wgrant> Not at the moment, no.
[13:00] <nigelb> hm, thanks :)
[14:13] <Laibsch> Is there anything wrong with the targets http://paste.debian.net/88062/ in ~/.dput.cf?  Whenever I upload a particular package to them it is refused with "The source apt-cacher-ng - 0.5.4-1 is already accepted in ubuntu/lucid and you cannot upload the same version within the same distribution."
[14:13] <Laibsch> that's strange for two reasons.  1) I'm uploading to maverick 2) even the lucid source in that ppa has been deleted a couple of days ago.  FWIW, 0.5.4-1 is in none of the official releases, yet.
[14:15] <bigjools> Laibsch: https://answers.edge.launchpad.net/soyuz/+faq/990
[14:17] <Laibsch> bigjools-lunch: thank you.  but please read my question more carefully.  I know generally how LP and uploading works.
[14:17] <Laibsch> if it's any help, I am official Debian maintainer of a number of packages.
[14:17] <Laibsch> I think LP is misbehaving here.
[14:17] <Laibsch> but I just want to see if I am doing something stupid.
[14:18] <Laibsch> again, I am specifically uploading to maverick, yet get a rejection message for lucid.  and even there the source has been deleted days ago.
[14:24] <soren> Laibsch: Does that PPA depend on your "stable" ppa?
[14:24] <Laibsch> lemme check
[14:25] <Laibsch> nope
[14:25] <soren> Laibsch: If it does, that explains why it's rejected. Not so much why it says lucid, but..
[14:25] <Laibsch> but that certainly was a good guess
[14:25] <soren> ok.
[14:26] <soren> Laibsch: Does it have any dependencies?
[14:26] <Laibsch> no
[14:26] <Laibsch> none at all
[14:26] <soren> ok
[14:27] <Laibsch> only ubuntu default dependencies
[14:27] <soren> ok
[14:37] <Laibsch> I guess maybe I should open a ticket against soyuz and let the devs sort out what is happening here.
[14:44] <maxb> Laibsch: apt-cacher-ng - 0.5.4-1   	 (changes file)   	2010-09-03  	Deleted  	Lucid  	Net  	 All builds were built successfully.
[14:44] <maxb> It's already there, you can't upload it again
[14:44] <Laibsch> that's three days ago
[14:44] <Laibsch> why is it still there?
[14:44] <Laibsch> that's the first question
[14:44] <Laibsch> second question is why the upload goes to lucid
[14:45] <Laibsch> although I upload to maverick
[14:45] <maxb> Well, first question, it's functioning as designed. You can delete packages, but not the metadata that records they once existed.
[14:46] <Laibsch> ?
[14:47] <Laibsch> so far I was always able to reupload a deleted package with the same version number
[14:47] <Laibsch> and again, why the problem with the lucid/maverick mixup
[14:47] <maxb> Huh. Really? I thought that was impossible
[14:47] <Laibsch> doesn't look lik "functioning as designed" to me
[14:47] <Laibsch> sure, did that a couple of times already
[14:47] <tgm4883> Can you specify the release (maverick) when you upload a source package? I thought you had to do it in the changelog?
[14:48] <Laibsch> usually it takes about 15-30 minutes for the cronjob to delete the files
[14:48] <Laibsch> tgm4883: you can force the upload to a particular release
[14:48] <tgm4883> hmm, neat
[14:48] <persia> It's *supposed* to be impossible to upload the same version number to the same PPA (regardless of target).  Any case of it working was accidental exploitation of a bug, and the bug was probably fixed.
[14:48] <Laibsch> persia: even if that file was removed?
[14:48] <maxb> Yes, even if.
[14:49] <Laibsch> sorry, but that would be terribly stupid
[14:49] <maxb> No, it's terribly sensible
[14:49] <Laibsch> and IMO that would be a real bug
[14:49] <tgm4883> why would you want to?
[14:49] <Laibsch> how do I upload the original debian version, then?
[14:49] <tgm4883> that would surely cause issues for upgrades
[14:49] <persia> It is designed to allow PPAs to be first-class archives for distribution.  This makes them somewhere between painful and useless for learning, or staging stuff.
[14:50] <Laibsch> tgm4883: ^^^ for example
[14:50] <persia> The two alternatives were discussed at length in several bugs, and the decision was to support distribution over staging.
[14:50] <Laibsch> OK
[14:50] <Laibsch> so the feature of allowing unchanged sources was deliberately broken, then
[14:51] <Laibsch> Cause I don't see how to upload that package to my PPA now
[14:51] <Laibsch> withouth creating a new PPA
[14:51] <Laibsch> and to request a sync I need to show a build log
[14:51] <Laibsch> which I haven't been able to produce for almost a week now
[14:51] <Laibsch> :-/
[14:51] <Laibsch> sorry, I stand by my word that this is stupid
[14:51] <Laibsch> I don't see the benefit
[14:51] <Laibsch> a deleted source and binary should be deleted for good
[14:53] <persia> `apt-get install sbuild ubuntu-dev-tools; mk-sbuild --arch=i386 maverick; sbuild -A -d maverick-i386 foo.dsc` will generate a build log.
[14:53] <Laibsch> tgm4883: https://help.launchpad.net/Packaging/PPA/Uploading#Using%20packages%20from%20other%20distributions
[14:53] <Laibsch> that's where that forced release is documented
[14:53] <persia> launchpad PPAs have been adjusted to not usefully support what you seek to accomplish, intentionally.  I happen to agree that it would be nice to use them for that, but it's not how it works today.
[14:54] <Laibsch> persia: I already see a dev asking me for a buildlog from a PPA at some time in the future
[14:54] <Laibsch> because they will be my comfortable than me uploading a build log
[14:54] <Laibsch> plus now I need to set up a maverick pbuilder
[14:54] <persia> send them here.  The decision was made a couple years ago, and isn't likely to be revisited.
[14:54] <Laibsch> boooooh!
[14:55] <Laibsch> couple of years?
[14:55] <tgm4883> Laibsch, ah I see now, however there is still "Important: Version numbers must be unique. This has implications if you want to provide packages for multiple Ubuntu series at once:", which is usually why I append +ppa# on the end
[14:55] <Laibsch> doubt that
[14:55] <Laibsch> rather a couple of months
[14:55] <tgm4883> that way I can bump a build number in LP
[14:55] <Laibsch> I've still been using that feature or bug depending on where you stand recently
[14:55] <Laibsch> tgm4883: I don't think you fully understand what I am doing
[14:56] <Laibsch> I'm intentionally not fiddling with changelog
[14:56] <tgm4883> Laibsch, I probably don't. But i'm not a LP person, so I can't do much to help you anyway
[15:00] <wgrant> Laibsch: You can still use the series override.
[15:00] <wgrant> Laibsch: You just can't upload it multiple times.
[15:00] <Laibsch> wgrant: what is the series override?
[15:00] <wgrant> 23:53:41 < Laibsch> that's where that forced release is documented
[15:00] <Laibsch> OK
[15:00] <Laibsch> wasn't sure that's what you meant
[15:00] <Laibsch> well, trust me, I'm stuck with this one
[15:01] <wgrant> How?
[15:01] <Laibsch> I incorrectly uploaded this one to lucid first
[15:01] <Laibsch> kaboom
[15:01] <Laibsch> that PPA is now forever dead for this package 0.5.4-1
[15:01] <Laibsch> IMHO that's not good
[15:01] <wgrant> It's as it should be.
[15:01] <wgrant> PPAs are not test build platforms.
[15:02] <Laibsch> ask the bugs-people
[15:02] <wgrant> Hm?
[15:02] <Laibsch> I think they would disagree
[15:02] <wgrant> Bugs-people?
[15:02] <Laibsch> a buildlog from a PPA is a common request
[15:02] <wgrant> That is odd.
[15:02] <Laibsch> for a sync request
[15:02] <Laibsch> and possibly others
[15:02] <tgm4883> Laibsch, just because the bugs people are using the PPA as a staging area doesn't mean that is what it is for
[15:03] <wgrant> But what's stopping you from doing a no-change rebuild?
[15:03] <maxb> huh? I don't even provide logs usually for sync requests, I just say I did it
[15:03] <Laibsch> tgm4883: I'm just trying to achieve whatever I feel is important for Ubuntu.
[15:03] <wgrant> maxb: FFEs require build logs
[15:03] <Laibsch> I don't care how that is done
[15:03] <wgrant> Or did back in my day.
[15:03] <Laibsch> but some consistency and common sense would be nice
[15:03] <wgrant> Laibsch: Why can't you upload with a different version number, then sync?
[15:03] <wgrant> That is, submit a build log for a slightly different version.
[15:03] <wgrant> But still sync the original.
[15:03] <Laibsch> why should I upload with a different version number?
[15:03] <Laibsch> wgrant: just a sec
[15:03] <wgrant> Because it's going to have different binaries.
[15:04] <tgm4883> because you can't use the same version :)
[15:04] <wgrant> And using the same version number for two different sets of packages is insane.
[15:04] <Laibsch> I only want one set of packages
[15:04] <wgrant> Right.
[15:04] <wgrant> But you asked for two.
[15:04] <Laibsch> but even deleting all packages, I can't do that anymore now
[15:05] <Laibsch> nope
[15:05] <Laibsch> I didn't
[15:05] <wgrant> You uploaded to Lucid.
[15:05] <wgrant> Then you tried to upload to Maverick.
[15:05] <Laibsch> wgrant: http://oss.leggewie.org/dsc-upload-hardy is the reason
[15:05] <tgm4883> I stand by my statement of appending +ppa# on the end. That should show that it is still the same version number, but the build number was bumped.
[15:05] <wgrant> tgm4883: Exactly.
[15:05] <tgm4883> I'm assuming you need to rebuild it for a packaging issue
[15:05] <Laibsch> I can upload an unmodified dsc from anywhere with a single command
[15:05] <Laibsch> tgm4883: and I stand by my statement that you don't understand what I'm doing, OK?
[15:06] <wgrant> Laibsch: And that's not necessarily a good thing.
[15:06] <wgrant> PPAs are not, primarily, a test build platform.
[15:06] <Laibsch> your opinion
[15:06] <wgrant> They are designed to behave like a sane distribution archive.
[15:06] <tgm4883> Laibsch, you are trying to produce build logs for a sync request to get a newer version of apt-cacher-ng into maverick from debian?
[15:06] <wgrant> And sane distribution archives do not reuse versions.
[15:07]  * Laibsch suggest for wgrant to read https://help.launchpad.net/Packaging/PPA/Uploading#Using%20packages%20from%20other%20distributions
[15:07] <wgrant> I'm well aware of it.
[15:07] <Laibsch> I'm just doing what's intentionally supported there
[15:07] <Laibsch> for years
[15:07] <wgrant> Laibsch: that hasn't changed for a very long time.
[15:07] <wgrant> Which bit are you referring to?
[15:08] <Laibsch> the "unchanged" bit
[15:08] <Laibsch> that obviously includes the changelog
[15:08] <wgrant> You can upload it.
[15:08] <wgrant> Just not multiple times.
[15:08] <tgm4883> wgrant, I would have to agree that it would be nice to have the same version number on multiple releases. As it stands now, we have to add hte ppa# if we build for more than 1 release
[15:08] <wgrant> tgm4883: Oh yes, that would certainly be nice.
[15:09] <wgrant> But Debian repositories (and indeed package managers) don't work that way.
[15:09] <tgm4883> yep
[15:13] <Laibsch> thanks for helping me understand what the issue was
[15:13] <Laibsch> let's agree to disagree on the sensibility of completely disallowing from now uploading the unmodified source to my PPA
[15:14] <Laibsch> I'm barred from that for life now
[15:14] <Laibsch> IMHO not sensible
[15:14] <wgrant> Given how archives work, it is quite sensible.
[15:14] <wgrant> It's not sensible for a test build platform, however.
[15:14] <wgrant> Which is what some use PPAs for.
[15:15] <tgm4883> Sounds like the PPA team and the bug team need to have a chat
[15:16] <bigjools> Laibsch: you are not barred from anything, you can do a simple no-change version bump.  All the other PPA users do this.  Ubuntu uploaders do this.
[15:17] <tgm4883> It would seem however that you aren't allowed to upload packages that haven't been changed from the version that is in debian or ubuntu
[15:17] <bigjools> with respect, PPAs are not a package build testing service, they are a package publishing service
[15:17] <tgm4883> from https://help.launchpad.net/Packaging/PPA/Uploading
[15:17] <bigjools> tgm4883: yes, you can upload them with no change, provided you've not already uploaded them to the same PPA
[15:18] <tgm4883> bigjools, well technically you can, i was just reading the help pages
[15:18] <wgrant> The rule has been there from day 1.
[15:18] <wgrant> It's never been enforced.
[15:18] <tgm4883> Note: We will not accept uploads of packages that are unmodified from their original source in Ubuntu or Debian, only packages that include your own changes.
[15:18] <tgm4883> wgrant, yea, I figured
[15:18] <wgrant> I'm not sure it actually has any purpose.
[15:18] <bigjools> tgm4883: that's a policy, not a rule
[15:19] <tgm4883> wgrant, sounds like they don't want to over burden the build servers. No need to duplicate work
[15:19] <tgm4883> but yea, never enforced
[15:19] <tgm4883> On a different note, is it possible to have publishing dependencies on other packages in the same PPA? eg. I have a package that depends on another package (not build depends). If that first package fails to build, and the second package publishes, then users get broken software
[15:20] <Laibsch> bigjools: how many times do I have to repeat myself?  "unchanged" is the keyword, OK?
[15:20] <bigjools> Laibsch: I'm trying to catch up the backscroll so sorry if I missed anything.  I'm happy to listen to you and explain why the service works as it does.
[15:20] <maxb> Laibsch: If 0.5.4-1 built successfully in maverick, the resulting binaries would not be "unchanged" from the binaries formerly built in lucid
[15:21] <Laibsch> maxb: the first build was for lucid, it failed
[15:21] <Laibsch> and now I can't retry for maverick
[15:22] <maxb> Laibsch: that is not true, it succeeded
[15:22] <bigjools> and you can also copy the package internally to maverick
[15:22] <bigjools> (provided you don't need a rebuild specifically for maverick)
[15:22] <tgm4883> bigjools, he needs a build log for it
[15:23] <bigjools> for maverick specifically?
[15:23] <maxb> bigjools: Laibsch does - the use case is using a PPA as a sync request build-tester
[15:23] <tgm4883> yea
[15:23] <bitdancer> OK, how do I log in to launchpad.net?  I get 'Invalid OpenID transaction'.  I've googled. I've cleared my cache and cookies.  I've made sure javascript is enabled for launchpad.net.  I still get that error and can't log in.
[15:23] <tgm4883> bigjools, apparently because the bug team told him he needed a PPA build log
[15:24] <bigjools> Laibsch: append ~ppa1 to your version, upload to Maverick and profit.
[15:24] <Laibsch> bigjools: please read what I already wrote
[15:24] <Laibsch> I don't want to state my position 10 times
[15:24] <Laibsch> I already said "agree to disagree"
[15:24] <bigjools> Laibsch: please repeat it, there's over a hundred lines of backscroll and I have no idea what you're referring toi
[15:24] <tgm4883> he wants it completly unchanged.
[15:25] <Laibsch> yes
[15:25] <bigjools> Laibsch: the bottom line is that PPAs are not a build testing service.  If you want to build repeatedly then you need to upload newer versions.  It has been like that for 3 years.
[15:25] <tgm4883> but IMHO, it's a build version bump, so it's still unchanged. But I might just think that because of how i've built things on a PPA before
[15:25] <Laibsch> which I think is clearly the intention of allowing something like https://help.launchpad.net/Packaging/PPA/Uploading#Using%20packages%20from%20other%20distributions
[15:26] <Laibsch> why else would you even need that
[15:26] <Laibsch> ?
[15:26] <Laibsch> if you force people to touch changelog?
[15:26] <tgm4883> "You may be able to use your PPA to build sources from other distributions that use .deb packages"
[15:26] <Laibsch> or if supposedly you are not allowed to upload unchanged sources as some have been saying is not supported
[15:26] <bigjools> I really don't see the big deal about a version bump - it takes 10 seconds to do and re-upload.
[15:27] <tgm4883> Important: Version numbers must be unique. This has implications if you want to provide packages for multiple Ubuntu series at once:
[15:27] <Laibsch> bigjools: I've until very recently never had a problem deleting a package and reuploading that shortly afterwards
[15:27] <bigjools> Laibsch: sorry that is not true
[15:27] <Laibsch> but I understand the #launchpad position
[15:27] <bigjools> we've *never* allowed that
[15:27] <Laibsch> no need to go in circles
[15:27] <Laibsch> bigjools: nonsense
[15:27] <bigjools> and you are free to look through the code history
[15:27] <Laibsch> I know it was possible
[15:27] <bigjools> no, it was not
[15:27] <tgm4883> Laibsch, seems that page lets you know you can pull it from another another source (ie. a debian repo) and build it for another disto (ie. maverick) without changing the sources
[15:28] <Laibsch> bigjools: you believe whatever you believe
[15:28] <Laibsch> I know what I know
[15:28] <tgm4883> Laibsch, it does not say (in fact, it specifically says you cannot) have the same version numbers in the same PPA
[15:28] <bigjools> Laibsch: I am the lead developer on Soyuz, I've been there since day one of PPAs.  I *know*.
[15:28] <bitdancer> no one has a clue, eh?
[15:29]  * bigjools gives up trying to help
[15:29] <bitdancer> Doesn't look like I can even file a bug report.
[15:29] <bigjools> please, ask someone else
[15:29] <tgm4883> bitdancer, sorry, my question got lost in this other issue as well
[15:29] <bitdancer> :)
[15:31] <tgm4883> bigjools, I'll redirect at you, can you set publishing dependencies? I have a package that depends on another package (not build depends). If that first package fails to build, and the second package publishes, then uses get broken software.
[15:31] <tgm4883> and we use the PPA's to get newer builds to users every day :)
[15:32] <wgrant> There's no way to do that automatically.
[15:32] <bigjools> tgm4883: yeah that's a known issue around PPAs, because the old version gets superseded
[15:32] <wgrant> Your best bet may be to set up a staging PPA.
[15:32] <bigjools> what he said
[15:32] <wgrant> And use an API script to watch for successful builds, then copy both across to the proper PPA.
[15:32] <bigjools> tgm4883: but ideally you'd test the build locally first ;)
[15:32] <tgm4883> hmm, API might be the way to go
[15:32] <tgm4883> bigjools, we literally build every day for both trunk and from a fixes branch
[15:33] <tgm4883> pulling from upstream sources
[15:33] <bigjools> tgm4883: is it a daily build?
[15:33] <tgm4883> I don't think we will be doing local builds first, although yea, that would be ideal
[15:33] <tgm4883> bigjools, yep
[15:33] <bigjools> have you tried recipes yet?
[15:33] <tgm4883> 2 daily builds actually, one for trunk, one for fixes
[15:33] <tgm4883> we haven't yet, but have talked about it
[15:33] <bigjools> it won't solve you problem but I thought I'd ask :)
[15:33] <tgm4883> we have it set up on a build server right now
[15:34] <tgm4883> builds only if there are changes upstream
[15:34] <tgm4883> which for trunk, usually means every day
[15:34] <tgm4883> I'll look into the API, see if we can't do something with that
[15:35] <bigjools> tgm4883: the other way of doing it is to include the version in the package name. That's a little horrbile though :(
[15:35] <tgm4883> oh yea, thats not fun times
[15:36] <tgm4883> I've thought about setting hard dependencies on the version number, but that can get problematic
[15:36] <bigjools> there's a bug somewhere about supporting configurable numbers of concurrent versions
[15:36] <tgm4883> yea, theres a few bugs I have found that would be helpful to have
[15:37] <tgm4883> apparently you are supposed to be able to have multiple releases in the changlog and build for all
[15:37] <tgm4883> ie, maverick, lucid, jaunty
[15:37] <tgm4883> all for the same entry
[15:37] <wgrant> Sort of.
[15:37] <wgrant> The changelog format supports it.
[15:37] <wgrant> But no archive tools that I know of do.
[15:38] <tgm4883> yea, apparently debian doesn't support that either :/
[15:38] <bigjools> we might be implementing that in the near-ish future
[15:38] <tgm4883> ohh nice
[15:38] <bigjools> it's needed for Bin NMUs
[15:38] <wgrant> It may have been implemented in Debian before package pools.
[15:38] <wgrant> But they were introduced nearly a decade ago, which makes it impossible without mangling binary versions.
[15:38] <tgm4883> cause our build script builds 3 packages for all ubuntu supported distros from 2 branches
[15:39] <tgm4883> usually that means around 18 uploads?
[15:39] <wgrant> Do you need to build separately for each?
[15:39] <bigjools> which package(s) are you working on?
[15:39] <wgrant> Or do the eg. Hardy binaries work all the way up to Maverick?
[15:39] <wgrant> If so, you can copy the binaries from Hardy upwards.
[15:39] <tgm4883> wgrant, nope, hardy doesn't work on maverick
[15:40] <tgm4883> technically we don't build for hardy anymore though
[15:40] <tgm4883> bigjools, mythtv
[15:40] <tgm4883> bigjools, and mythplugins and myththemes
[15:40] <bigjools> ah cool, I am a myth user
[15:40] <tgm4883> bigjools, sweet deal
[15:41] <tgm4883> we build 2 packages for each ubuntu release
[15:41] <tgm4883> whatever was shipped with that version, and +1
[15:41] <tgm4883> so hardy doesn't get builds anymore because there are no upstream changes for 0.21 anymore
[15:41] <tgm4883> current version is 0.23
[15:42] <tgm4883> well, 0.23.1
[15:42] <tgm4883> karmic will stop getting builds soon tool
[15:42] <tgm4883> too
[15:43] <bigjools> I would have thought that daily builds only really make sense on the most recent LTS, non-LTS and dev version
[15:44] <tgm4883> bigjools, that is usually how it ends up based on the upstream release schedule
[15:44] <bigjools> great
[15:44] <tgm4883> but with mythtv, users tend to try and stick with what works
[15:44] <tgm4883> and update from the fixes branch
[15:44] <tgm4883> karmic will stop getting builds once 0.24 gets released, probably in about a month
[15:45] <tgm4883> karmic was released with 0.22, and also gets builds for 0.23 (per our policy of building 2 mythtv releases for each ubuntu release)
[15:46] <tgm4883> so if upstream doesn't release 0.24 for 18 months, we will build keep the karmic builds going until either karmic isn't supported anymore, or 0.24 gets released
[15:47] <tgm4883> but this is all way off topic. I'll go check out the LP API and see if we can do what we need. bigjools if you have any mythtv questions, stop by #ubuntu-mythtv
[15:47] <boracasli> Can I use google translate in launchpad translations?
[15:48] <bigjools> tgm4883: sure thing - I've been using it for ~6 years now and stuff still confuses me :)
[15:48] <vagrale> Hi! How can i rename project in launchpad?
[15:48] <boracasli> Launchpad Translations prefer only to translate in their mother tongue to users?
[15:48] <bigjools> jtv ^
[15:49] <boracasli> Launchpad Translations prefer only to translate in their mother tongue to users?
[15:49] <jtv> boracasli: I'm not sure what it is you want to do
[15:49] <dpm> hi boracasli, as we told you when you asked using the answers system, there is no integration between Launchpad and Google Translate. We also recommend only to translate in the languages the translator knows
[15:49] <jtv> Google Translate is definitely _not_ good enough to produce translations…
[15:49] <jtv> Maybe this is about translating the user interface?
[15:50] <boracasli> David Planella, auto-translated strings are deleted?
[15:50] <boracasli> in Ubuntu etc.
[15:50] <jtv> They should not be approved.
[15:50] <boracasli> David Planella (dpm), auto-translated strings are deleted?
[15:50] <jtv> There are two reasons:
[15:50] <boracasli> why?
[15:50] <jtv> boracasli: I just answered you
[15:50] <boracasli> what reasons
[15:50] <dpm> boracasli, jtv is already answering the question
[15:51] <jtv> Because Google Translate is not good enough, as I already said, and has no knowledge of a project's or translation team's translation guidelines.
[15:51] <boracasli> and
[15:51] <jtv> It's also not very consistent.
[15:52] <dpm> boracasli, furthermore, you need to join a translation team to submit translations to Ubuntu. I don't think any translation team would allow you to join them if you are not fluent in their language
[15:53] <boracasli> Are the strings translated with automatic translators such as Google Translate in ubuntu will be deleted? And I joint to any translation team.
[15:54] <boracasli> Are the strings translated with automatic translators such as Google Translate in ubuntu will be deleted? And I joint to any translation team. please answer
[15:54] <dpm> boracasli, we have already answered that question, please read it.
[15:54] <jtv> boracasli: stop shouting please
[15:55] <boracasli> Is Google Translate banned?
[15:55] <jtv> boracasli: please do not submit any google translate translations.
[15:55] <tgm4883> google isn't exactly a little known operation. I think it's safe to say that if google translate worked well enough for ubuntu translations, that canonical would already be using it on a mass scale
[15:55] <boracasli> Will you say "Stop doing this."?
[15:56] <boracasli> If yes, say "Stop doing this."
[15:56] <jtv> boracasli: we're already saying that, and you're just not listening
[15:56] <boracasli> I'm submitting google translations
[15:56]  * tgm4883 smacks head
[15:56] <boracasli> Will you say "Stop doing this."?If yes, say "Stop doing this."
[15:56]  * dpm ignores further comments
[15:56] <tgm4883> "Stop doing this."
[15:57] <boracasli> Launchpad accounts can banned?
[15:57] <jtv> boracasli: if you don't speak enough english to understand our answers, you probably shouldn't be translating
[15:58] <boracasli> I can speak enough.
[15:58] <boracasli> Is Launchpad has got a twitter?
[15:58] <boracasli> or canonical
[15:58] <jtv> lol
[15:58] <jtv> okay, that was a good joke—who are you really?
[15:59] <boracasli> Is Launchpad or Canonical has got a Twitter account?
[15:59] <boracasli> In Soviet Russia, Launchpad buys Canonical!
[15:59] <tgm4883> Ubuntu çeviriler için google çevirmen kullanmayın
[15:59] <bigjools> boracasli: launchpadstatus is the twitter accont
[15:59] <bigjools> account, even
[16:00] <tgm4883> yes, I realize the irony in my above translated statement :)
[16:00] <boracasli> niye ubuntu çevirileri için google translate kullanmamı istemiyorsunuz
[16:01] <boracasli> I'm translated Moovida to Georgian with Google Translate
[16:02] <tgm4883> yeterli Ubuntu çeviriler için iyi değil çünkü. Ayrıca Ubuntu politikasına karşı kullanmaktır.
[16:02] <boracasli> tgm4883? Türk müsün
[16:02] <tgm4883> nope
[16:02] <boracasli> where are you from?
[16:02] <tgm4883> USA
[16:02] <boracasli> hmm
[16:03] <boracasli> really do you know turkish?
[16:03] <tgm4883> no, ironically, I was using google translate
[16:03] <boracasli> yeterli Ubuntu çeviriler için iyi değil çünkü. Ayrıca Ubuntu politikasına karşı kullanmaktır. please translate to english
[16:03] <boracasli> but no gtranslate
[16:03] <tgm4883> But this is why you shouldn't use google translator  ( Türk müsün ==   Do Turkey  )
[16:04] <boracasli> yes
[16:04] <tgm4883> so ^^ was ( because it is not good enough for Ubuntu translations. It is also against Ubuntu policy
[16:05] <tgm4883> I think this proves why not to use google translations for ubuntu
[16:05] <boracasli> Çünkü o, Ubuntu çevirileri için yeterince iyi değildir. Ayrıca Ubuntu ilkesine de aykırıdır.
[16:05] <boracasli> my translation
[16:05] <boracasli> no gtranslate
[16:07] <boracasli> but "canonical" is Canonical Ltd.
[16:07] <tgm4883> true, which is probably translated incorrectly
[16:08] <tgm4883> then there is also subtle differences. ie. trash isn't even universal between US english and UK english
[16:22] <boracasli> https://translations.launchpad.net/moovida/1.0/+lang/ka
[16:23] <boracasli> my georgian moovida
[16:40] <walton> hi
[16:41] <walton> i have a question about building packages with launchpad: if i have a bzr branch with a debian directory and a watch file, can i make launchpad automatically use the watch file to build new upstream releases?
[16:43] <idnar> hmm, I proposed a branch for review 17 minutes ago, and it's still "updating diff..."
[16:43] <idnar> are there delays in branch scanning or something?
[16:43] <idnar> (it's a private branch, if that matters)
[16:56] <nhandler> I know there was some interest in this script the last time I mentioned it. Here is a small python script that will subscribe a team/person to a specified list of packages. A couple of Debian pkg-* teams are using it to monitor bugs for their packages in Ubuntu: http://www.43-1.org/tmp/lp-mass-subscribe
[17:37] <dholbach> hiya
[17:38] <dholbach> Could anyone imagine giving a session about using code review/bzr/launchpad at Ubuntu App Developer Week? :)
[18:18] <esteve> hi guys
[18:18] <esteve> we bought a subscription and our bzr repos are private now
[18:18] <esteve> however, I can't seem to make bug reports private by default
[18:19] <esteve> is there an option for doing so or do I have to post a question on launchpad answers?
[18:33] <salgado> bac, can you help esteve?
[18:34] <esteve> salgado bac: thanks, I posted a question on launchpad bugs https://answers.launchpad.net/malone/+question/124343
[18:35] <esteve> but I don't know if that's the right place
[18:45] <salgado> esteve, don't need to worry about that; someone will get to it soon
[18:45] <esteve> salgado: thanks!
[21:03] <lvh> Hey
[21:03] <lvh> is it normal that the branding icon isn't used as a favicon
[21:42] <Nightrose> hi
[21:42] <Nightrose> launchpad is giving me an error telling me to try again when submitting a bug report
[21:42] <Nightrose> "Sorry, there was a problem connecting to the Launchpad server."
[21:43] <Nightrose> can someone help?
[21:43]  * Nightrose waves at mneptok
[22:30] <thumper> Nightrose: what project were you trying to file a bug report on?
[22:30] <Nightrose> thumper: linux
[22:31] <Nightrose> using the command line tool
[22:31] <thumper> Nightrose: ubuntu-bug
[22:31] <thumper> ?
[22:31] <Nightrose> yes
[22:31] <thumper> did it work a subsequent time?
[22:32] <Nightrose> i got redirected to the website to fill out the rest of the info and submitted it then got the error
[22:32] <Nightrose> tried reloading with resubmitting the data multiple times
[22:32] <Nightrose> same error
[22:32] <Nightrose> didn't try going through ubuntu-bug again
[22:34] <thumper> hmm..
[22:34] <thumper> Nightrose: so the error was from the webbrowser after adding more info?
[22:35] <Nightrose> yes
[22:35] <Nightrose> final step
[22:35] <Nightrose> well error text was from launchpad
[22:35] <thumper> Nightrose: was it on edge?
[22:35] <Nightrose> yes
[22:35] <thumper> Nightrose: it is possible that you hit the daily edge update...
[22:35] <thumper> maybe
[22:36] <thumper> would you care to try it again?
[22:36] <Nightrose> ok
[22:36] <thumper> thanks
[22:36] <Nightrose> can do after i had food yes
[22:36] <thumper> if you are still getting an error we should file a bug
[22:36] <Nightrose> ok
[22:47] <Snorlax> anyone alive here?
[22:47] <thumper> Snorlax: yes
[22:47] <thumper> maybe
[22:47] <thumper> need more coffee though
[22:47] <Snorlax> Ha, I can understand that.
[22:49] <Snorlax> The website sent me here. I'm setting up a private launchpad machine and ran into an unusual error.
[22:49] <thumper> what do you mean a private launchpad machine?
[22:50] <Snorlax> I'm testing launchpad, deployed on an internal machine.
[22:50] <lifeless> #launchpad-dev would be a better channel for this
[22:52] <Snorlax> I see...
[23:02] <Nightrose> thumper: getting the same error again
[23:05] <lifeless> Nightrose: do you get an OOPS code?
[23:05] <lifeless> !oops
[23:05] <Nightrose> lifeless: no
[23:05] <lifeless> can you pastebin the error text / take a screen shot please
[23:05] <Nightrose> k
[23:07] <Nightrose> lifeless: http://lydiapintscher.de/tmp/launchpad.png
[23:08] <lifeless> Nightrose: do you get that immediately
[23:08] <lifeless> or after filling in the summary ?
[23:09] <Nightrose> i filled in the summary and then get to the page where it asks me if it is a dupe of some others or if i want to really file it any fill in more details
[23:09] <Nightrose> i say it's not a dupe and fill in the next page
[23:09] <Nightrose> then click submit again to finish filing it
[23:09] <Nightrose> then get that error
[23:10] <lifeless> Nightrose: thats very strange
[23:10] <lifeless> try hitting refresh
[23:11] <lifeless> your browser may prompt to resubmit
[23:11] <lifeless> - say yes
[23:11] <Nightrose> same error - also happened when i first tried filing the bug before
[23:19] <lifeless> Nightrose: try retrying - sorry.
[23:19] <lifeless> Nightrose: really not sure whats up - that page indicates a down appserver, which isn't meant to happen
[23:19] <lifeless> losa ping
[23:20] <Nightrose> lifeless: reloaded - same :(
[23:20] <lifeless> Nightrose: take the url, take edge out of it, and then hit enter
[23:20] <Nightrose> k
[23:21] <Nightrose> takes me back to the summary part of the wizard
[23:21]  * Nightrose fills in again
[23:22] <Nightrose> lifeless: same
[23:23] <Nightrose> oh no wait
[23:23] <Nightrose> i'm redirected to edge again
[23:23] <lifeless> there is alink on the bottom right of the page
[23:23] <lifeless> 'disable edge' - click it
[23:23] <Nightrose> k
[23:23] <lifeless> now try
[23:25] <Nightrose> lifeless: success
[23:25] <Nightrose> \o/
[23:25] <lifeless> thanks
[23:25] <lifeless> I'll try to get a handle on the issue when a sysadmin is around
[23:25] <Nightrose> ok
[23:25] <Nightrose> thx
[23:27] <Nightrose> lifeless: not sure if that is something for you to look into too but i said it was a graphics related bug in ubuntu-bug and it got tagged with resume suspend
[23:27] <lifeless> thats done by some distro tools not launchpad itself
[23:27] <Nightrose> k
[23:28] <lifeless> #ubuntu-bugs may be able to give some information
[23:28] <Nightrose> ok


[04:57] <vysakh0> I was just thinking of deploying my app(rails) in amazon aws and I saw about maas today, sounds cool. I have too many doubts, can i shoot it now?
[19:04] <sartas> where i can download maas ephemeral images?
[19:04] <sartas> https://maas.ubuntu.com/images - pade not found
[19:04] <sartas> *page
[19:36] <AskUbuntu> can't download maas ephemeral images | http://askubuntu.com/q/240471
[21:25] <alperkanat> hey there.. i ran maas-import-isos command but when it tries to fetch https://maas.ubuntu.com/images/query/precise/ephemeral/released-dl.current.txt it fails and the text on /MAAS never goes away
[21:25] <alperkanat> any ideas?
[21:26] <alperkanat> this fails: https://maas.ubuntu.com/images/


[01:44] <Viper550> Just gotta make the makefile for my splash theme and it will be all ready!
[02:03] <Viper550> anyone still here?
[02:05] <kwwii> me
[02:05] <kwwii> but I do not count
[02:05] <kwwii> :-p
[02:06] <Viper550> Did I make this usplash theme right? http://www.gnome-look.org/content/show.php?content=46645
[02:09] <Viper550> As you may have heard, I was porting Dapper's Usplash theme to Edgy
[02:26] <nysosy1> hi
[02:26] <nysosy1> anybody out there? :D
[02:26] <nysosy1> Viper550: ?
[02:27] <Viper550> hello
[02:27] <nysosy1> i have created a little preview of my emblems for the human theme
[02:27] <nysosy1> will u see it? :D
[02:28] <nysosy1> please tell me your mind
[02:28] <nysosy1> http://img509.imageshack.us/my.php?image=emblemspreviewiw2.png
[02:29] <Viper550> I will...if you also look at the Edgy Usplash theme I made for fun... http://www.gnome-look.org/content/show.php?content=46645
[02:29] <Viper550> Interesting...
[02:30] <nysosy1> hey, very nice ussplash, i will try it soon :)
[02:30] <Viper550> It's for Edgy
[02:31] <nysosy1> i know ;)
[02:31] <Viper550> I assume you use Edgy
[02:33] <Viper550> So, try compiling it
[02:37] <Viper550> (you know, for best experience, turn on text
[02:48] <Viper550> still there nysosyl?
[02:50] <nysosy1> hmm i will recreate my icons first
[02:50] <nysosy1> (other colors ect.)
[02:51] <Viper550> (but first, maybe you could just compile my splash to make sure it will work?)
[02:51] <nysosy1> ok
[02:54] <nysosy1> make: Circular throbber_back.png <- throbber_back.png.c dependency dropped.
[02:54] <nysosy1> pngtousplash throbber_back.png > throbber_back.png.c
[02:54] <nysosy1> /bin/sh: pngtousplash: not found
[02:54] <nysosy1> make: *** [throbber_back.png.c]  Error 127
[02:54] <nysosy1> rm throbber_back.png.c
[02:54] <nysosy1> nysosym@hannelore:~/dapperport$
[02:54] <nysosy1> i cant compile them
[02:54] <Viper550> uh, sudo apt-get install usplash-dev
[02:56] <nysosy1> usplash_1024_768.png.c:30861: warning: large integer implicitly truncated to unsigned type
[02:57] <Viper550> what does that mean?
[02:57] <nysosy1> the package works
[02:57] <nysosy1> mom
[02:57] <nysosy1> i will reboot
[02:58] <nysosy1> wish luck ^^
[03:00] <nysosym> re
[03:00] <Viper550> hello
[03:00] <nysosym> the package doesn`t work
[03:00] <Viper550> what happened?
[03:00] <nysosym> only the "old" bootsplash
[03:00] <Viper550> only the "puke background" one?
[03:01] <nysosym> the normal edgy bootlogo
[03:01] <Viper550> yeah
[03:01] <Viper550> just the brown background with the gloss logo
[03:01] <nysosym> yes
[03:02] <Viper550> So, it made the .so file?
[03:03] <Viper550> I think there may be more steps other than compiling it
[03:04] <nysosym> yes
[03:05] <nysosym> the .so file is here
[03:07] <Viper550> Okay, on Dapper, you make a new directory (/usr/local/lib/usplash/), copy the file there as root, and run some sort of sudo alternatives command
[03:08] <Viper550> Okay, and all the packages for alternate themes on the repos copy it to usr/lib/usplash
[03:19] <troy_s> ping
[09:43] <nysosym> hi all
[10:31] <AnAnt> how do I install a splash screen ?
[10:32] <AnAnt> Viper550 made a splash screen & I compiled it using usplash-dev
[10:32] <AnAnt> the result is an .so file
[10:32] <AnAnt> what should I do with it ?
[11:01] <lapo> hi
[11:04] <effraie> ho
[11:21] <nysosym> re
[11:22] <nysosym> i have created some new emblems, please tell me your critic! http://img228.imageshack.us/my.php?image=screenshothumanemblemsfilebrowserpp5.png :)
[11:36] <effraie> nysosym: ther are quite better!
[11:36] <effraie> can you send them to the art-list?
[11:39] <nysosym> effraie: well, but they aren`t complete at moment
[11:40] <effraie> if you can complete them, that's cool, but in order to have directions, and maybe be included in default artwork, you have to submit them to the list
[11:46] <nysosym> ok, i have sent it to the mailing list :D
[12:00] <nysosym> hi andreasn :)
[12:00] <andreasn> nysosym: hi there
[12:02] <nysosym> how are u?
[12:02] <andreasn> just fine, a bit tired...need to get something to eat and then get some work done
[12:02] <andreasn> have a deadline creeping closer :)
[12:02] <andreasn> what about you?
[12:10] <nysosym> yes, i feel fine too :)
[12:10] <nysosym> thx for question
[12:39] <AnAnt> is there a way to install a compiled usplash.so ?
[01:06] <ppd> 56
[01:06] <AnAnt> 56 ?
[01:06] <AnAnt> what's that ?
[02:04] <fschoep> Hello everyone!
[02:08] <AnAnt> hello
[02:08] <AnAnt> how do I install a usplash.so ?
[02:08] <AnAnt> Viper550 ported Dapper splash to Edgy
[02:08] <AnAnt> I compiled it (after installing usplash-dev)
[02:08] <AnAnt> and I got a usplash.so
[02:08] <AnAnt> so how do I install it ?
[02:08] <fschoep> Copy it to /usr/share/usplash
[02:08] <fschoep> Or something like that
[02:08] <fschoep> Does that exist?
[02:08] <fschoep> Then use update-alternatives
[02:09] <fschoep> See https://help.ubuntu.com/community/USplashCustomizationHowto
[02:09] <nysosym> hi fschoep :)))))
[02:09] <fschoep> At least. that's how we did it back in the old days :)
[02:09] <fschoep> Hi nysosym I saw you did some emblems!
[02:09] <nysosym> jop ^^
[02:09] <AnAnt> fschoep: no /usr/share/usplash
[02:09] <nysosym> i was a little bit bored yesterday evening.. ^^
[02:10] <fschoep> AnAnt: /usr/local/lib/usplash then?
[02:10] <fschoep> AnAnt it should be in the HowTo, sorry to be terse :0
[02:10] <AnAnt> fschoep: yeah, right
[02:10] <AnAnt> fschoep: without the local/ though
[02:11] <fschoep> AnAnt: OK, no problem
[02:11] <AnAnt> thanks
[02:11] <fschoep> You need some magic after that though
[02:11] <fschoep> Type in the following rune:
[02:11] <AnAnt> huh ?
[02:11] <fschoep> sudo dpkg-reconfigure linux-image-$(uname -r)
[02:12] <fschoep> I'm not really at home with those runes, but it should rebuild the initramfs
[02:12] <nysosym> hmm, i will wait for the official usplash :D
[02:12] <AnAnt> k, the howto is fine, thanks
[02:15] <nysosym> fschoep: how do you think about my icons?
[02:15] <fschoep> nysosym: need to take a closer look and try them in real life first, first impression is good though
[02:16] <fschoep> nysosym: I'm not sure if I can shuffle them in right now, but it's something we can address for Edgy +1 definitely
[02:18] <AnAnt> rebooting
[02:18] <nysosym> fschoep: k, thx :)))
[02:18] <fschoep> nysosym: k :)
[02:21] <nysosym> fschoep: my first idea was, all emblems in orange (only white and orange), but in IRC nobody want them ^^
[02:21] <fschoep> Hehe :)
[02:21] <fschoep> I think you took the right choice in using color
[02:22] <nysosym> sure, but i like me "one-color" version too :D
[02:22] <fschoep> nysosym: well, try sending it the ML as well, maybe Mark will pick up on it
[02:23] <fschoep> nysosym: the Human icon set uses orange badges throughout so it might not be a bad idea after all
[02:23] <nysosym> http://img101.imageshack.us/my.php?image=emblemspreviewjl5.png << here is it :D
[02:23] <nysosym> (a very first version) ^^
[02:23] <fschoep> Not bad, not bad at all :)
[02:23] <fschoep> One thing I noticed is the gloss
[02:24] <fschoep> Could you try to take another look at the Human folder icon and try matching the gloss line with it? I'm not quite sure if it fits in right now
[02:24] <nysosym> , sure i will try it :)
[02:24] <fschoep> Great!
[02:26] <nysosym> np ^^
[02:29] <AnAnt> fschoep: it worked, thanks
[02:29] <fschoep> AnAnt: you're welcome
[02:31] <AnAnt> fschoep: the problem is that text messages don't appear, how do I make it appear ? I got the source code
[02:31] <fschoep> AnAnt: maybe ask Viper? I have no idea what he has done to make it work :)
[02:31] <AnAnt> k
[02:31] <fschoep> AnAnt: I'm sorry but I have other matters to attend to :)
[02:32] <AnAnt> np
[02:32] <fschoep> AnAnt: once the heat is off I'll gladly help you out
[02:32] <fschoep> Hi effraie, how are you?
[02:33] <effraie> fine, thanks
[02:33] <effraie> i just have a problem with my email server...
[02:34] <fschoep> effraie: oh dear, anything small I can help with?
[02:34] <effraie> did you receuved my email about your adress book?
[02:34] <fschoep> No
[02:34] <fschoep> You can PM it to me if you want
[02:35] <effraie> no, franck, it's a mutualized mailserver, and we have been spammed..
[02:35] <fschoep> effraie: BTW thanks so much again for the moderation sprint :)
[02:35] <fschoep> effraie: I see, that's unfortunate
[02:35] <effraie> the situation is now under control, but the spamm queue is big..
[02:35] <effraie> so, i've a big lag...
[02:36] <fschoep> effraie: I see, I'm very patient though
[02:36] <nysosym> fschoep: better? http://img100.imageshack.us/my.php?image=newhumanglossai5.png
[02:36] <fschoep> nysosym: the top one is the new one?
[02:36] <nysosym> yes
[02:37] <fschoep> nysosym: then yes, it's a LOT better :D
[02:37] <nysosym> ok
[02:37] <fschoep> nysosym: really, it fits in so much more
[02:37] <nysosym> i will make the rest with the "new gloss" :)
[02:37] <fschoep> Great, be sure to let the mailing list know, maybe Mark will pick it up
[02:38] <nysosym> yes, mark although like the "old" one :D
[02:39] <fschoep> I'm sure he'll love the new ones then
[02:39] <effraie> fschoep: what does mean 'BTW'
[02:39] <effraie> ?
[02:39] <fschoep> effraie: it's an abbreviation for By The Way
[02:39] <effraie> ok, thanks
[02:39] <fschoep> you're welcome
[02:39] <effraie> i've got to improve my english...
[02:39] <fschoep> there's a lot of those around on the internet: you probably know most ones already
[02:40] <fschoep> If you're ever in doubt use Google:
[02:40] <fschoep> http://www.google.nl/search?hl=nl&q=define%3Abtw&btnG=Google+zoeken&meta=
[02:40] <fschoep> just type define:BTW or something else and it'll list you the possibilities, then you can just choose the one that fits in most
[02:41] <effraie> eh, that's a great trick
[02:41] <fschoep> nysosym: those new ones are definitely good, watch out for the overlap though
[02:41] <fschoep> nysosym: in the example you sent, the gloss doesn't run all the way through on the left side
[02:43] <nysosym> fschoep: sure, i will fix this, only a short make preview :D
[02:43] <fschoep> nysosym: I see, that's what I thought - just giving a tip for the final version :)
[02:45] <nysosym> hey nooooo problem, critic make work better and i have no problem with critic :)
[02:46] <fschoep> nysosym: OK, good to hear you won't flip out :)
[02:46] <nysosym> give me 15min and all i new :D
[02:46] <nysosym> *is
[02:47] <fschoep> The timer is counting down, I'm watching you!
[02:47] <fschoep> ;)
[02:48] <nysosym> hehe :D
[02:50] <nysosym> hmmmm
[02:50] <nysosym> a big failure....
[02:50] <nysosym> please give me 10min more ^^
[02:50] <fschoep> Take your time, quality over quantity!
[02:52] <nysosym> hehe, i know, it`s only funny ^^
[02:53] <nysosym> btw. is it okay that i spam the mailing list with my releases? :-/
[02:54] <fschoep> nysosym: well, not really
[02:54] <fschoep> nysosym: maybe you'd better try sending it in tomorrow
[02:55] <nysosym> ok, no problem :)
[02:55] <fschoep> nysosym: also, try to mention my name in your mail
[02:55] <nysosym> sure :)
[02:55] <nysosym> my lovely little sunshine ^^
[02:56] <fschoep> Can I PM you nysosym ?
[02:56] <nysosym> sure :)
[02:56] <cbx33> hey all
[02:56] <fschoep> nysosym: can you read my PMs I sent already?
[02:56] <cbx33> ping pign ping fschoep
[02:56] <fschoep> Hi cbx33 right man right time
[02:57] <cbx33> what have I done this time ;)
[02:57] <fschoep> cbx33: how are you doing, brother?
[02:57] <cbx33> I'm doing great fschoep
[02:57] <nysosym> hi cbx33
[02:57] <cbx33> can't wait till I get my new sound card
[02:57] <cbx33> 10ins/10 outs
[02:57] <cbx33> w00000t
[02:57] <fschoep> cbx33: I can't wait either ;)
[02:57] <nysosym> fschoep: yes i can
[02:57] <cbx33> I know wsorry for the delay
[02:57] <fschoep> cbx33: did you reply to Mark already about the request
[02:57] <cbx33> All I can do now is to wait
[02:57] <cbx33> I did
[02:58] <fschoep> nysosym: OK, great
[02:58] <fschoep> cbx33: thanks
[02:58] <cbx33> fschoep, np
[02:58] <cbx33> I didnt really expect them to anyway
[02:58] <cbx33> just hoped
[02:58] <fschoep> cbx33: as you probably saw I put in a good word for you
[02:58] <cbx33> and in light of the techincal problems I was having it was in dire straights
[02:58] <cbx33> heheh
[02:58] <cbx33> tahnks Frank
[02:59] <fschoep> cbx33: did you get my e-mail reply about dropping shutdown sound and shortening login?
[02:59] <cbx33> yes :(
[02:59] <fschoep> cbx33: what did you think of it?
[02:59] <cbx33> if it must then it must
[02:59] <cbx33> :p
[02:59] <cbx33> can we not just have a really shot logout
[02:59] <cbx33> :S
[03:00] <fschoep> cbx33: problem is, my machine and Keybuk's and several others' all shut down in like one or two seconds
[03:00] <fschoep> ALSA gets stopped almost right away
[03:00] <cbx33> really
[03:00] <cbx33> then drop it it is then
[03:00] <fschoep> cbx33: there is no way we can guarantee any sound to play for any given time
[03:00] <cbx33> I mean we did have soe problems
[03:00] <cbx33> with it from a composition POV
[03:00] <cbx33> so if you guys want to drop it
[03:00] <cbx33> that's fine with me
[03:01] <fschoep> cbx33: OK
[03:01] <fschoep> cbx33: and shortening login?
[03:02] <cbx33> I'll do my best
[03:02] <fschoep> Great, as I suggested maybe doing only one drum loop would make sense
[03:03] <fschoep> cbx33: I'm sorry we need to cut and drop sounds
[03:03] <fschoep> cbx33: but I think it'll make the distro better
[03:03] <cbx33> fschoep, it's fine
[03:03] <cbx33> just sad from my POV
[03:03] <cbx33> but that's just me being selfish ;)
[03:03] <fschoep> cbx33: I can understand
[03:04] <fschoep> cbx33: you know, I have a short story
[03:04] <fschoep> cbx33: two months ago when recording my bands new CD
[03:04] <fschoep> cbx33: our "producer" cut up songs, rearranged parts and shortened them
[03:05] <fschoep> cbx33: I felt bad at that time, but when I listen to the takes now, it makes a lot of sense to make more compact versions of songs and sounds
[03:05] <cbx33> yeh I knopw
[03:05] <cbx33> hehe
[03:05] <fschoep> cbx33: so I hope the shortened login sound will make this really nice impression as that's its purpose
[03:06] <cbx33> fschoep, that'll be fine
[03:06] <cbx33> edgy + 1 will enable a much broader range of sounds to be created
[03:06] <fschoep> cbx33: Indeed, and we can focus on sound from the start as well
[03:07] <effraie> eh, fschoep, your musician?
[03:07] <fschoep> cbx33: r'you going to California?
[03:07] <fschoep> effraie: yes indeed
[03:07] <fschoep> effraie: well, I try to be anyway - I can play the guitar
[03:07] <effraie> if it where not a working channel...
[03:08] <cbx33> I'm hoping so fschoep
[03:08] <cbx33> still waiting to hear
[03:08] <cbx33> I thought it was supposed to be yesterday
[03:08] <fschoep> effraie: if you know The Edge from U2 - that's about the style I play
[03:08] <effraie> ok
[03:08] <effraie> i see
[03:09] <fschoep> Our new EP with four new tracks is out next week, I'll make sure you guys can listen to it then
[03:09] <cbx33> brb
[03:09] <effraie> cool! (even if i'm jazz addict)
[03:09] <fschoep> effraie: Oh, we (mostly our singer) put in some detuned notes now and then and call it freeform jazz, so you'll like it :)
[03:10] <effraie> ;)
[03:14] <fschoep> effraie: http://video.google.nl/videoplay?docid=7716505373128409451
[03:14] <fschoep> That's from our early days, we're a lot different nowadays
[03:15] <effraie> eheheh.. i'll see in later.. on ubuntu/ppc, only free things
[03:15] <fschoep> Right ;)
[03:18] <fschoep> I'm going away for a moment now, see you later today!
[06:18] <Viper550> Guess what, I ported Dapper's Usplash Artwork to Edgy!
[08:31] <nysosym> hi all :))
[08:32] <PingunZ> hey nysosym
[08:51] <nysosym> hmm sooo silent ^^
[09:06] <PingunZ> True :
[09:06] <PingunZ> *:)
[09:09] <nysosym> hi PingunZ  :)
[09:10] <nysosym> !seen fschoep
[09:23] <nysosym> anyone here?
[09:23] <PingunZ> yes :)
[09:24] <nysosym> i have here 300kb of date for the mailing list, is this allowed?
[09:25] <PingunZ> date ?
[09:25] <nysosym> actually
[09:25] <nysosym> i will upload them
[09:25] <nysosym> thats my package ^^
[09:25] <PingunZ> ok
[09:26] <nysosym> is this okay?
[09:26] <PingunZ> Dunno .. I'm pretty new .. but I guess it is
[09:26] <nysosym> okay thx :)
[09:29] <PingunZ> nysosym: Are you the emblems guy ? :)
[09:30] <nysosym> jep
[09:30] <PingunZ> nysosym: They rock .. your emblems .. I suggest you put them on the wiki
[09:30] <nysosym> hmm i don't know how :(
[09:31] <nysosym> *shame*
[09:31] <PingunZ> Hmm ..
[09:31] <nysosym> and thx :D
[09:31] <PingunZ> No, thank you ! :) I really hope they get included in edgy ;)
[09:32] <nysosym> hmm i think they would be integrated in edgy+1 ;)
[09:32] <PingunZ> ping troy_s
[09:33] <PingunZ> Ask him to put it on the wiki :) He knows his way around ;)
[09:33] <nysosym> good to know, thx a lot :)
[10:00] <Viper550> Did I do this usplash theme for Edgy properly? http://www.gnome-look.org/content/show.php?content=46645
[10:02] <nysosym> i think so
[10:02] <Viper550> (you got it to work?)
[10:06] <nysosym>  no, but i haven`t try it again
[10:26] <ppd> troy_s are you here?
[11:07] <fschoep> Hello everyone
[11:07] <ppd> hi
[11:08] <fschoep> Hi ppd how are you doing?
[11:08] <ppd> very well. you too?
[11:08] <fschoep> Yes, thanks
[11:08] <fschoep> ppd: Are you following the artwork team or interested in what we're doing?
[11:09] <ppd> yes I'm interested in what you're doing and for the moment especially in troy_s's wallpapers for edgy ;)
[11:10] <fschoep> ppd: right, we're creating some new designs based on Mark's directions
[11:10] <fschoep> ppd: do you like the current wallpaper by Troy?
[11:10] <ppd> is the default one by troy?
[11:11] <fschoep> ppd: yes, it is
[11:12] <ppd> yes. very much. much better than the old one
[11:12] <fschoep> ppd: right, we're going to make some new designs which will please Mark a bit more than the current one
[11:13] <fschoep> ppd: I might try to keep the current wallpaper by Troy in there though
[11:15] <ppd> cool
[11:17] <ppd> I like that style with glossiness and that plastic feel
[11:18] <fschoep> ppd: we're going to make some new designs based on gloss, so you'll probably like them as well
[11:19] <ppd> fschoep: some with brighter colors would be nice too
[11:19] <ppd> but in general I think you're doing great work
[11:19] <ppd> :)
[11:19] <fschoep> ppd: watch Edgy the next few days, there will be three new community wallpapers to enjoy
[11:20] <fschoep> ppd: if all goes well, you get three new fully customized themes ranging from GDM to GTK theme
[11:20] <ppd> how many wallpapers will you ship with the final release?
[11:20] <fschoep> ppd: I advise you to check out "Blubuntu" when it's in there
[11:20] <ppd> I will
[11:20] <fschoep> ppd: probably eight
[11:21] <fschoep> ppd: Dawn of Ubuntu, Simple Ubuntu, Wave, Blubuntu, Peace, Tropic, Default and Default Widescreen
[11:21] <cbx33> hey fschoep
[11:21] <fschoep> Hi cbx33
[11:22] <cbx33> guess what a rrived a little while ago
[11:22] <fschoep> cbx33: you're not kidding, right :)
[11:22] <cbx33> nope
[11:22] <cbx33> :D
[11:22] <cbx33> it's in and has been tested
[11:22] <fschoep> cbx33: this chat is useless without pics ;)
[11:22] <cbx33> we're talking like 0 noise
[11:22] <cbx33> fschoep, I have pics
[11:22] <cbx33> will be going on blog tinight or tomorrow
[11:22] <fschoep> cbx33: great
[11:22] <fschoep> cbx33: does it work with your software already?
[11:23] <cbx33> http://www.m-audio.com/products/en_us/Delta1010LT-main.html
[11:23] <cbx33> fschoep, yup
[11:23] <fschoep> cbx33: good to hear, great news man
[11:23] <cbx33> yup I hope to start on the sounds tomorrow
[11:23] <cbx33> got to goto the doctor first
[11:23] <fschoep> cbx33: that would be awesome, I'm looking forward to it
[11:23] <cbx33> :(
[11:23] <fschoep> cbx33: nothing bad I hope?
[11:24] <cbx33> well....the fact that I seem to be suffering from hypersomnia for the past 2 years
[11:24] <cbx33> I've finally had enough
[11:24] <cbx33> I can fall asleep anywhere....it's not as bas as narcolepsy
[11:24] <cbx33> but I can fall asleep mid conversation with someone sometimes ;)
[11:24] <fschoep> cbx33: I see, I'm sorry to hear that - I hope there is a proper cure
[11:24] <cbx33> it worries me
[11:25] <cbx33> it's ok
[11:25] <cbx33> as long as I'm front of a PC
[11:25] <cbx33> i never sleep whilst on a pc
[11:25] <fschoep> cbx33: so you carry a laptop around ;) ?
[11:25] <cbx33> yup
[11:25] <cbx33> :p
[11:26] <fschoep> cbx33: ping me on IRC or mail tomorrow if you've got news
[11:26] <cbx33> ok
[11:26] <fschoep> cbx33: I'm going to log off now
[11:26] <cbx33> seriously there is like 0 noise
[11:26] <fschoep> That is awesome
[11:26] <cbx33> just nothing
[11:26] <cbx33> it's scary
[11:26] <fschoep> I never had any equipment that good
[11:26] <cbx33> my mixer makes much more noise than the card
[11:26] <cbx33> I took some samples
[11:26] <cbx33> and normalised them
[11:27] <cbx33> they were at like 40% before
[11:27] <cbx33> after no noise
[11:27] <cbx33> I mean nothing
[11:27] <fschoep> cbx33: amazing
[11:27] <cbx33> heheheh
[11:27] <cbx33> indeed
[11:27] <cbx33> I'll let you get off
[11:27] <cbx33> I'm off to bed too
[11:27] <fschoep> cbx33: OK, thanks :) See you tomorrow I hope!
[11:27] <cbx33> yup
[11:27] <fschoep> Good night everyone


[15:52] <Sarvatt> ricotz: are you using edgers on utopic by any chance?
[15:53] <Sarvatt> if so can you let me know if the xserver 1.16 transition went ok? anything get removed besides glamoregl? looks fine on a fresh install at least
[16:25] <ricotz> Sarvatt, will upgrade and restart in a bit
[16:34] <ricotz> Sarvatt, looks good :)
[16:34] <Sarvatt> ricotz: thanks a ton for checking!
[16:35] <Sarvatt> not using utopic on any real machines here
[16:41] <ricotz> Sarvatt, utopic works fine, except for some praying before upgrading systemd/upstart/kernel ;)


[04:13] <timtootin> hey everyone
[10:36]  * sresu 100th
[13:03] <venilsurya> Hey!
[22:53] <palhmbs> hggdh, I'm keen to get started with bug triaging - could you help assign me a mentor?
[22:54] <hggdh> palhmbs: let's move to #ubuntu-bugs, a better channel for your question


[08:30] <ubotu> New bug: #134523 in linux-restricted-modules-2.6.22 (restricted) "Xorg crashes when running glxgears (dup-of: 130325)" [Undecided,New]  https://launchpad.net/bugs/134523
[08:50] <ubotu> New bug: #38260 in linux-restricted-modules-2.6.15 (restricted) "random crashes with nvidia drivers using kubuntu" [Medium,New]  https://launchpad.net/bugs/38260
[01:30] <ubotu> New bug: #23117 in linux-restricted-modules-2.6.15 (restricted) "errlor loading fglrx module" [Medium,Invalid]  https://launchpad.net/bugs/23117
[01:41] <ubotu> New bug: #27610 in linux-restricted-modules-2.6.15 (restricted) "Breezy's fglrx driver freezes computer when enabled" [Medium,Fix released]  https://launchpad.net/bugs/27610
[01:56] <ubotu> New bug: #33792 in linux-restricted-modules-2.6.15 (restricted) "fonts not rendered correctly with nvidia driver (amd64)" [Medium,Invalid]  https://launchpad.net/bugs/33792
[02:50] <ubotu> New bug: #17550 in xkeyboard-config (main) "[xk-c]  new logitech layout" [Medium,Invalid]  https://launchpad.net/bugs/17550
[03:36] <ubotu> New bug: #135062 in xserver-xorg-input-mouse (main) "mouse pointer moves cursor while typing" [Undecided,New]  https://launchpad.net/bugs/135062
[04:37] <tormod> hi, will somebody package ati 6.7.192-1 today?
[04:37] <tepsipakki> it's already in debian
[04:38] <tepsipakki> all you need to do is to ease the xserver dependancy
[04:38] <tepsipakki> my pbuilder box is out-of-order :/
[04:38] <tepsipakki> so I'm unable to build it before tomorrow (since I had to stay home today)
[04:52] <tormod> tepsipakki: thanks
[04:53] <ubotu> New bug: #135077 in gnome-panel (main) "screen resolution has changed to 800x600 max." [Undecided,Incomplete]  https://launchpad.net/bugs/135077
[05:06] <tormod> tepsipakki, if I use a gutsy pbuilder I don't get your newer xserver-xorg-dev. Is it important to build against the newer xserver version? I guess I'll wait till I get to my gutsy machine...
[05:07] <tepsipakki> hmm, that should be in gutsy
[05:08] <tepsipakki> but I don't think that's important anyway
[05:08] <tormod> the ubuntu12  ? maybe I need to update my pbuilder.
[05:10] <tepsipakki> 12ubuntu2 actually, there was an update already :)
[05:10] <tepsipakki> but not by me
[05:12] <tormod> yes I just had to update the pbuild base.tar.gz
[05:16] <ubotu> New bug: #135080 in xorg (main) "Black screen on Inspiron 6400 Desktop Install" [Undecided,New]  https://launchpad.net/bugs/135080
[06:15] <ubotu> New bug: #135093 in xserver-xorg-video-intel (main) "xserver-xorg-video-intel does not work with 845G" [Undecided,New]  https://launchpad.net/bugs/135093
[06:40] <bryce> morning
[06:47] <tepsipakki> hey bryce
[07:11] <ubotu> New bug: #134982 in xserver-xorg-input-synaptics (main) "Mouse pointer freezes after opening up a new gdm login" [Undecided,Confirmed]  https://launchpad.net/bugs/134982
[07:25] <ubotu> New bug: #135107 in xorg (main) "Gutsy > Tribe 5 X.org fails to detect proper resolution" [Undecided,New]  https://launchpad.net/bugs/135107
[11:12] <bryce> I started recording some of my thoughts regarding what should be done for solving bug 3731 - https://wiki.ubuntu.com/X/AutodetectMonitorFrequency
[11:12] <ubotu> Launchpad bug 3731 in xorg "Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect" [Critical,Confirmed]  https://launchpad.net/bugs/3731
[11:24] <tepsipakki> bryce: exactly
[11:25] <tepsipakki> the current way of things is quite error-prone


[05:16] -queuebot:#ubuntu-release- New binary: usbutils [amd64] (noble-proposed/main) [1:017-3] (core, i386-whitelist)
[05:26] -queuebot:#ubuntu-release- Unapproved: cockpit (jammy-backports/universe) [306-1~bpo22.04.1 => 308-1~bpo22.04.1] (no packageset)
[05:26] -queuebot:#ubuntu-release- Unapproved: cockpit (mantic-backports/universe) [303-1~bpo23.10.1 => 308-1~bpo23.10.1] (no packageset)
[05:26] -queuebot:#ubuntu-release- Unapproved: cockpit (lunar-backports/universe) [303-1~bpo23.04.1 => 308-1~bpo23.04.1] (no packageset)
[08:16] -queuebot:#ubuntu-release- New: accepted bifrost [amd64] (noble-proposed) [1.3.0-1]
[08:16] -queuebot:#ubuntu-release- New: accepted bifrost [ppc64el] (noble-proposed) [1.3.0-1]
[08:16] -queuebot:#ubuntu-release- New: accepted bifrost [s390x] (noble-proposed) [1.3.0-1]
[08:16] -queuebot:#ubuntu-release- New: accepted bifrost [arm64] (noble-proposed) [1.3.0-1]
[08:16] -queuebot:#ubuntu-release- New: accepted usbutils [amd64] (noble-proposed) [1:017-3]
[08:16] -queuebot:#ubuntu-release- New: accepted bifrost [riscv64] (noble-proposed) [1.3.0-1]
[08:31] <vorlon> tsimonq2: rejecting the usbio-drivers upload you sponsored; upstream source says GPL-2 only (not 'or any later version'), debian/copyright uses the correct GPL-2.0 license identifier tag, but the text says "or any later version"
[08:35] -queuebot:#ubuntu-release- New: rejected usbio-drivers [source] (noble-proposed) [0~git202308242005.c349315-0ubuntu1]
[09:06] -queuebot:#ubuntu-release- New: accepted intel-lpmd [source] (noble-proposed) [0.0.2-0ubuntu1]
[09:10] -queuebot:#ubuntu-release- New binary: intel-lpmd [amd64] (noble-proposed/none) [0.0.2-0ubuntu1] (no packageset)
[09:11] -queuebot:#ubuntu-release- Unapproved: heimdal (mantic-proposed/universe) [7.8.git20221117.28daf24+dfsg-3ubuntu1 => 7.8.git20221117.28daf24+dfsg-3ubuntu<IP_ADDRESS>] (i386-whitelist)
[09:19] -queuebot:#ubuntu-release- New: accepted intel-lpmd [amd64] (noble-proposed) [0.0.2-0ubuntu1]
[09:46] <LocutusOfBorg> please ubuntu SRU reject the older heimdal in unapproved queue ^^
[09:46] <LocutusOfBorg> also please ubuntu-archive kick fpc 3.2.2+dfsg-30 *out*
[09:46] <LocutusOfBorg> context is chicken and egg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059950
[09:46] -ubottu:#ubuntu-release- Debian bug 1059950 in fp-utils-3.2.2 "fp-utils-3.2.2: same man page in fp-utils-3.2.2 and fp-units-rtl-3.2.2" [Serious, Open]
[12:58] <rbasak> LocutusOfBorg: please ubuntu SRU reject the older heimdal> have you coordinated that with mirespace please? Looks like she's out until Monday though.
[14:00] <tjaalton> bah, I rejected the older one just now
[14:00] -queuebot:#ubuntu-release- Unapproved: rejected heimdal [source] (mantic-proposed) [7.8.git20221117.28daf24+dfsg-3ubuntu1.1]
[14:12] <enr0n> ubuntu-sru: can someone please look at systemd in the unapproved queue for focal and jammy? TIA!
[14:19] -queuebot:#ubuntu-release- Unapproved: accepted ethtool [source] (mantic-proposed) [1:6.5-1ubuntu0.1]
[14:21] -queuebot:#ubuntu-release- Unapproved: accepted ethtool [source] (lunar-proposed) [1:6.1-1ubuntu0.1]
[14:22] -queuebot:#ubuntu-release- Unapproved: accepted ethtool [source] (jammy-proposed) [1:5.16-1ubuntu0.1]
[14:30] -queuebot:#ubuntu-release- Unapproved: accepted mirage [source] (mantic-proposed) [0.11.1-1ubuntu<IP_ADDRESS>]
[14:31] -queuebot:#ubuntu-release- Unapproved: accepted mirage [source] (jammy-proposed) [0.11.1-1ubuntu<IP_ADDRESS>]
[14:36] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (mantic-proposed) [23.10.58]
[16:56] <tsimonq2> vorlon: ack, in hindsight I should not have been as permissive. I still have notes from the previous rejects that I'd like to address sometime before Feature Freeze. I apologize, for both the continual delay in following up on this set, and my mistakes here.
[16:58] <tsimonq2> vorlon: The solution for lubuntu-update-notifier in Noble seems to be "let's rewrite the entire thing from scratch, in Qt/C++ rather than using PyQt5, for efficiency." arraybolt3 has been working hard on that, and it's almost ready. That being said, it's on my desk for this week to follow up more thoroughly on the SRU. I also apologize for my delay in responding to you there.
[16:59] <tsimonq2> Given the nature of the update and the impact on the user story, my tentative list is Focal, Jammy, Lunar, Mantic, and of course, inherently Noble.
[17:00] <tsimonq2> If you decided you made the same mistake as me in respect to permissiveness, you're welcome to request additional justification.
[17:01] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (mantic-proposed/main) [253.5.2 => 253.5.3] (no packageset)
[17:02] <tsimonq2> <3 systemd-hwe
[17:02] <arraybolt3> tsimonq2: SRU link? Not sure what you're referring to
[17:03] -queuebot:#ubuntu-release- Unapproved: systemd-hwe (jammy-proposed/main) [249.11.4 => 249.11.5] (no packageset)
[17:05] <tsimonq2> arraybolt3: https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/2038958
[17:05] -ubottu:#ubuntu-release- Launchpad bug 2038958 in lubuntu-update-notifier (Ubuntu Mantic) "[SRU] Add support for release upgrading" [Medium, In Progress]
[17:06] <arraybolt3> ah
[17:15] -queuebot:#ubuntu-release- New binary: gtksheet [amd64] (noble-proposed/none) [4.3.12+dfsg-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: gtksheet [ppc64el] (noble-proposed/none) [4.3.12+dfsg-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: gtksheet [arm64] (noble-proposed/none) [4.3.12+dfsg-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: gtksheet [s390x] (noble-proposed/none) [4.3.12+dfsg-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: gtksheet [armhf] (noble-proposed/none) [4.3.12+dfsg-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: condor [amd64] (noble-proposed/none) [23.2.0+dfsg-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: condor [arm64] (noble-proposed/none) [23.2.0+dfsg-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: condor [ppc64el] (noble-proposed/none) [23.2.0+dfsg-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: condor [s390x] (noble-proposed/none) [23.2.0+dfsg-1] (no packageset)
[18:13] -queuebot:#ubuntu-release- New binary: condor [armhf] (noble-proposed/universe) [23.2.0+dfsg-1] (no packageset)
[18:26] -queuebot:#ubuntu-release- New binary: gtksheet [riscv64] (noble-proposed/universe) [4.3.12+dfsg-1] (no packageset)
[19:16] <bdmurray> vorlon: Do you have any plans to look at the systemd SRU? If not I will as I'd like to get the tests going over the weekend.
[19:17] <vorlon> bdmurray: I haven't yet started SRU shift today but am planning to put in time this afternoon
[19:17] <bdmurray> enr0n: Is it systemd-hwe and not systemd?
[19:18] <enr0n> bdmurray: my earlier request was about systemd. I also uploaded systemd-hwe today
[19:19] <bdmurray> enr0n: Oh from November?
[19:19] <enr0n> bdmurray: yes indeed
[19:20] <bdmurray> Okay, looking.
[19:20] <vorlon> from November> uh
[19:22] <bdmurray> vorlon looked at bug 2035122 in December fwiw
[19:22] -ubottu:#ubuntu-release- Bug 2035122 in systemd (Ubuntu Jammy) "Under ubuntu core/core-desktop, /etc/default/locale is not modifiable" [Medium, New] https://launchpad.net/bugs/2035122
[19:29] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (jammy-proposed) [249.11-0ubuntu3.12]
[19:37] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (focal-proposed) [245.4-4ubuntu3.23]
[20:00] <enr0n> bdmurray: thanks!
[20:05] -queuebot:#ubuntu-release- Unapproved: rejected budgie-desktop [source] (mantic-proposed) [10.8-2ubuntu3.1]
[20:08] <vorlon> tsimonq2: LP: #2038958 blocked for 2 months now by the lack of a fix for noble...
[20:08] -ubottu:#ubuntu-release- Launchpad bug 2038958 in lubuntu-update-notifier (Ubuntu Mantic) "[SRU] Add support for release upgrading" [Medium, In Progress] https://launchpad.net/bugs/2038958
[20:10] <tsimonq2> vorlon: That's the one.
[20:10] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [source] (mantic-proposed) [2.29.0-0ubuntu2.1]
[20:11] <vorlon> "the one"?
[20:11] <vorlon> ah, sorry, I managed to miss your earlier comments today
[20:11] <tsimonq2> need to hop into a meeting, sec
[20:13] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools-signed [source] (mantic-proposed) [2.29.0-0ubuntu2.1]
[20:19] -queuebot:#ubuntu-release- Unapproved: rejected zfs-linux [source] (mantic-proposed) [2.2.2-0ubuntu1~23.10]
[20:21] -queuebot:#ubuntu-release- Unapproved: s390-tools (mantic-proposed/main) [2.29.0-0ubuntu2 => 2.29.0-0ubuntu2.1] (core)
[20:24] -queuebot:#ubuntu-release- New binary: condor [riscv64] (noble-proposed/universe) [23.2.0+dfsg-1] (no packageset)
[21:06] <vorlon> Eickmeyer: Debian has removed foo-yc20 (it's gtk2) and ubuntustudio-audio-plugins Recommends it.  Do you want to drop the reference, or adopt the package in Ubuntu?
[21:07] <Eickmeyer> vorlon: I'll likely drop the reference, but let me look first.
[21:08] <vorlon> ack
[21:11] <Eickmeyer> vorlon: Yeah, no release in nearly 9 years, no work on dropping gtk2 upstream, no actual commit for 3 years. Stale as moldy bread, dropping.
[21:13] <vorlon> coreycb: your SRU bug #2046359 says the SRU process you followed was 'https://wiki.ubuntu.com/OpenStackUpdates' which is a wiki page containing no SRU process, only a reference to https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates WITHOUT automatic redirect, and the SRU template on that current wiki page does not refer to the stale URL :P
[21:13] -ubottu:#ubuntu-release- Bug 2046359 in nova (Ubuntu Mantic) "[SRU] bobcat stable releases" [High, Triaged] https://launchpad.net/bugs/2046359
[21:14] <vorlon> coreycb: and it was you that obsoleted the old wiki page in 2019
[21:15] <vorlon> coreycb: anyway, please fix your SRU, because currently you are asserting that the SRU exception process you followed is "nothing".  I am not going to fix the URL for you, this is an assertion from you as the submitter about what process was followed
[21:23] <Eickmeyer> vorlon: foo-yc20 gone, meta uploaded.
[21:23] <vorlon> Eickmeyer: cheers
[21:24] <vorlon> Eickmeyer: next is vocproc, same exact situation ;)
[21:24] <Eickmeyer> vorlon: looking
[21:27] <vorlon> mfo: do you care about fixing the spelling of 'd/p/u/zed-fix-typo-ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT.patch'
[21:27] <vorlon> oh
[21:27] <vorlon> the spelling is the point :-)
[21:31] <coreycb> vorlon: done
[21:33] <LocutusOfBorg> rbasak, I was mirespace sponsor, and I posted on the bug the reason for what a transition on stable should be avoided
[21:33] <LocutusOfBorg> dropping symbols on stable is PITA
[21:35] <vorlon> Eickmeyer: I accidentally hit 'y' to delete vocproc already; so if you want it restored let me know
[21:35] <Eickmeyer> vorlon: I noticed. XD
[21:35] <vorlon> I tried to ^C it but too late :P
[21:35] <Eickmeyer> Still looking, but I'm leaning toward 86-ing it anyway.
[21:40] <Eickmeyer> vorlon: TL;DR: That plugin is about 14 years old and bitrotted to dust. Not even a place to check if there's any recent commits or development. I'm good with letting it vanish into oblivion; there's other plugins that do the same thing.
[21:41] <vorlon> gtkpod> oh Lord, this still exists?
[21:41] <Eickmeyer> My mouth, open agape, shocked.
[21:42] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (mantic-proposed) [2.2.0-0ubuntu1~23.10.1]
[21:43] -queuebot:#ubuntu-release- Unapproved: accepted designate [source] (mantic-proposed) [1:17.0.1-0ubuntu1]
[21:44] <vorlon> coreycb: oops I didn't read as closely on LP: #2046376 before I started accepting, but same thing
[21:45] -ubottu:#ubuntu-release- Launchpad bug 2046376 in neutron (Ubuntu Jammy) "[SRU] yoga stable releases" [High, Triaged] https://launchpad.net/bugs/2046376
[21:45] -queuebot:#ubuntu-release- Unapproved: accepted designate [source] (jammy-proposed) [1:14.0.4-0ubuntu1]
[21:50] -queuebot:#ubuntu-release- Unapproved: accepted manila [source] (mantic-proposed) [1:17.1.0-0ubuntu1]
[21:53] <Eickmeyer> vorlon: vocproc gone, YAMUL (Yet Another Meta UpLoaded).
[22:01] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (mantic-proposed) [3:28.0.1-0ubuntu1]
[22:04] -queuebot:#ubuntu-release- Unapproved: accepted magnum [source] (mantic-proposed) [17.0.1-0ubuntu1]
[22:08] <coreycb> vorlon: I've updated that one as well. thanks for taking a look.
[22:36] <vorlon> Removing packages:
[22:36] <vorlon> 	linux-wlan-ng 0.2.9+dfsg-6 in noble
[22:36] <vorlon> "linux-wlang-ng" - doesn't *quite* overlap in time with Star Trek: TNG, but the current upstream version was released in 2008
[22:38] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (mantic-proposed) [2:23.1.0-0ubuntu1]
[22:45] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (jammy-proposed) [2:20.5.0-0ubuntu1]
[22:47] <vorlon> doko: you apparently removed gnuradio NBS binaries by hand, not when https://ubuntu-archive-team.ubuntu.com/nbs.html showed they were ready for removal, and made gnss-sdr uninstallable?
[22:48] <vorlon> doko: similar story with cctbx source removed, making libobjcryst0 uninstallable
[22:56] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (mantic-proposed) [2.29.0-0ubuntu2.1]
[23:15] -queuebot:#ubuntu-release- New binary: apt-verify [amd64] (noble-proposed/none) [2.0-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: rust-rustix-openpty [amd64] (noble-proposed/none) [0.1.1-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: rust-h3-quinn [amd64] (noble-proposed/none) [0.0.4-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: swift-tools [amd64] (noble-proposed/none) [0.0.1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: cc-cedict [amd64] (noble-proposed/none) [0.0~repack20231203-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: rust-tikv-jemalloc-sys [amd64] (noble-proposed/none) [0.5.4-1] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: rust-concat-idents [amd64] (noble-proposed/none) [1.1.4-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: kdsingleapplication [amd64] (noble-proposed/none) [1.0.0-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: rust-vsort [amd64] (noble-proposed/none) [0.2.0-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: rust-powerfmt-macros [amd64] (noble-proposed/none) [0.1.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: g-golf [amd64] (noble-proposed/none) [0.8.0~rc1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: kclock [amd64] (noble-proposed/none) [23.08.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: kdsingleapplication [armhf] (noble-proposed/none) [1.0.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: rust-rockusb [amd64] (noble-proposed/none) [0.1.3-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: kalk [amd64] (noble-proposed/none) [23.08.3-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: rust-gstreamer-gl-sys [amd64] (noble-proposed/none) [0.21.2-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: kclock [arm64] (noble-proposed/none) [23.08.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: rust-sys-locale [amd64] (noble-proposed/none) [0.3.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: g-golf [arm64] (noble-proposed/none) [0.8.0~rc1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: rust-concat-idents [ppc64el] (noble-proposed/none) [1.1.4-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: rust-gstreamer-gl-sys [ppc64el] (noble-proposed/none) [0.21.2-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: kclock [armhf] (noble-proposed/none) [23.08.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: rust-rustix-openpty [arm64] (noble-proposed/none) [0.1.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: rust-gix-prompt [amd64] (noble-proposed/none) [0.8.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: fheroes2 [amd64] (noble-proposed/none) [1.0.9+dfsg-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-h3-quinn [ppc64el] (noble-proposed/none) [0.0.4-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-vsort [armhf] (noble-proposed/none) [0.2.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: g-golf [armhf] (noble-proposed/none) [0.8.0~rc1-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-vsort [ppc64el] (noble-proposed/none) [0.2.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-powerfmt-macros [ppc64el] (noble-proposed/none) [0.1.0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: rust-gix-prompt [ppc64el] (noble-proposed/none) [0.8.0-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: kdsingleapplication [ppc64el] (noble-proposed/none) [1.0.0-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: rust-gix-prompt [armhf] (noble-proposed/none) [0.8.0-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: rust-concat-idents [armhf] (noble-proposed/none) [1.1.4-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: rust-sys-locale [armhf] (noble-proposed/none) [0.3.1-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- Unapproved: rejected fsvs [source] (mantic-proposed) [1.2.9-2ubuntu<IP_ADDRESS>]
[23:21] -queuebot:#ubuntu-release- New: accepted kdsingleapplication [ppc64el] (noble-proposed) [1.0.0-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-sys-locale [armhf] (noble-proposed) [0.3.1-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-concat-idents [armhf] (noble-proposed) [1.1.4-1]
[23:21] -queuebot:#ubuntu-release- New: accepted fheroes2 [amd64] (noble-proposed) [1.0.9+dfsg-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-concat-idents [ppc64el] (noble-proposed) [1.1.4-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-gix-prompt [ppc64el] (noble-proposed) [0.8.0-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-h3-quinn [ppc64el] (noble-proposed) [0.0.4-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-rustix-openpty [arm64] (noble-proposed) [0.1.1-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-vsort [ppc64el] (noble-proposed) [0.2.0-1]
[23:21] -queuebot:#ubuntu-release- New binary: rust-vsort [arm64] (noble-proposed/none) [0.2.0-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New: accepted g-golf [armhf] (noble-proposed) [0.8.0~rc1-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-gstreamer-gl-sys [ppc64el] (noble-proposed) [0.21.2-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-vsort [armhf] (noble-proposed) [0.2.0-1]
[23:21] -queuebot:#ubuntu-release- New: accepted rust-gix-prompt [armhf] (noble-proposed) [0.8.0-1]
[23:21] -queuebot:#ubuntu-release- New binary: kalk [armhf] (noble-proposed/none) [23.08.3-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New: accepted rust-powerfmt-macros [ppc64el] (noble-proposed) [0.1.0-1]
[23:22] -queuebot:#ubuntu-release- New: accepted g-golf [amd64] (noble-proposed) [0.8.0~rc1-1]
[23:22] -queuebot:#ubuntu-release- New: accepted kalk [amd64] (noble-proposed) [23.08.3-1]
[23:22] -queuebot:#ubuntu-release- New: accepted kclock [arm64] (noble-proposed) [23.08.0-1]
[23:22] -queuebot:#ubuntu-release- New: accepted kdsingleapplication [amd64] (noble-proposed) [1.0.0-1]
[23:22] -queuebot:#ubuntu-release- New: accepted rust-gix-prompt [amd64] (noble-proposed) [0.8.0-1]
[23:22] -queuebot:#ubuntu-release- New: accepted rust-powerfmt-macros [amd64] (noble-proposed) [0.1.0-1]
[23:22] -queuebot:#ubuntu-release- New: accepted rust-sys-locale [amd64] (noble-proposed) [0.3.1-1]
[23:22] -queuebot:#ubuntu-release- New binary: kdsingleapplication [arm64] (noble-proposed/none) [1.0.0-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: rust-h3-quinn [arm64] (noble-proposed/none) [0.0.4-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: rust-rustix-openpty [ppc64el] (noble-proposed/none) [0.1.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New: accepted g-golf [arm64] (noble-proposed) [0.8.0~rc1-1]
[23:22] -queuebot:#ubuntu-release- New: accepted kclock [armhf] (noble-proposed) [23.08.0-1]
[23:22] -queuebot:#ubuntu-release- New: accepted rust-gstreamer-gl-sys [amd64] (noble-proposed) [0.21.2-1]
[23:22] -queuebot:#ubuntu-release- New binary: kalk [ppc64el] (noble-proposed/none) [23.08.3-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: rust-rustix-openpty [armhf] (noble-proposed/none) [0.1.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: rust-sys-locale [ppc64el] (noble-proposed/none) [0.3.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New: accepted kclock [amd64] (noble-proposed) [23.08.0-1]
[23:22] -queuebot:#ubuntu-release- New: accepted rust-rockusb [amd64] (noble-proposed) [0.1.3-1]
[23:22] -queuebot:#ubuntu-release- New binary: rust-sys-locale [arm64] (noble-proposed/none) [0.3.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New: accepted kdsingleapplication [armhf] (noble-proposed) [1.0.0-1]
[23:22] -queuebot:#ubuntu-release- New binary: rust-gix-prompt [arm64] (noble-proposed/none) [0.8.0-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New: accepted apt-verify [amd64] (noble-proposed) [2.0-1]
[23:22] -queuebot:#ubuntu-release- New: accepted condor [arm64] (noble-proposed) [23.2.0+dfsg-1]
[23:22] -queuebot:#ubuntu-release- New: accepted condor [ppc64el] (noble-proposed) [23.2.0+dfsg-1]
[23:22] -queuebot:#ubuntu-release- New: accepted condor [s390x] (noble-proposed) [23.2.0+dfsg-1]
[23:22] -queuebot:#ubuntu-release- New: accepted rust-concat-idents [amd64] (noble-proposed) [1.1.4-1]
[23:22] -queuebot:#ubuntu-release- New: accepted rust-rustix-openpty [amd64] (noble-proposed) [0.1.1-1]
[23:22] -queuebot:#ubuntu-release- New: accepted rust-vsort [amd64] (noble-proposed) [0.2.0-1]
[23:22] -queuebot:#ubuntu-release- New binary: rust-powerfmt-macros [armhf] (noble-proposed/none) [0.1.0-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New: accepted cc-cedict [amd64] (noble-proposed) [0.0~repack20231203-1]
[23:22] -queuebot:#ubuntu-release- New: accepted condor [riscv64] (noble-proposed) [23.2.0+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New: accepted rust-h3-quinn [amd64] (noble-proposed) [0.0.4-1]
[23:23] -queuebot:#ubuntu-release- New: accepted swift-tools [amd64] (noble-proposed) [0.0.1]
[23:23] -queuebot:#ubuntu-release- New: accepted condor [armhf] (noble-proposed) [23.2.0+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New: accepted rust-tikv-jemalloc-sys [amd64] (noble-proposed) [0.5.4-1]
[23:23] -queuebot:#ubuntu-release- New: accepted gtksheet [riscv64] (noble-proposed) [4.3.12+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New binary: rust-tikv-jemalloc-sys [ppc64el] (noble-proposed/none) [0.5.4-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New: accepted condor [amd64] (noble-proposed) [23.2.0+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New: accepted gtksheet [arm64] (noble-proposed) [4.3.12+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New: accepted gtksheet [ppc64el] (noble-proposed) [4.3.12+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New binary: g-golf [ppc64el] (noble-proposed/none) [0.8.0~rc1-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New: accepted gtksheet [amd64] (noble-proposed) [4.3.12+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New: accepted gtksheet [s390x] (noble-proposed) [4.3.12+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New: accepted gtksheet [armhf] (noble-proposed) [4.3.12+dfsg-1]
[23:23] -queuebot:#ubuntu-release- New binary: rust-rockusb [ppc64el] (noble-proposed/none) [0.1.3-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: rust-h3-quinn [armhf] (noble-proposed/none) [0.0.4-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: rust-tikv-jemalloc-sys [arm64] (noble-proposed/none) [0.5.4-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: kdsingleapplication [s390x] (noble-proposed/none) [1.0.0-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: rust-concat-idents [s390x] (noble-proposed/none) [1.1.4-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: rust-concat-idents [arm64] (noble-proposed/none) [1.1.4-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: rust-tikv-jemalloc-sys [armhf] (noble-proposed/none) [0.5.4-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: fheroes2 [ppc64el] (noble-proposed/none) [1.0.9+dfsg-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: kclock [s390x] (noble-proposed/none) [23.08.0-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: rust-gix-prompt [s390x] (noble-proposed/none) [0.8.0-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: massxpert2 [amd64] (noble-proposed/none) [8.3.0-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- Unapproved: accepted color-picker [source] (mantic-proposed) [1.0.3-2ubuntu<IP_ADDRESS>]
[23:28] -queuebot:#ubuntu-release- New binary: amberol [ppc64el] (noble-proposed/none) [0.10.3-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: rust-gstreamer-gl-sys [s390x] (noble-proposed/none) [0.21.2-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- Unapproved: accepted color-picker [source] (lunar-proposed) [1.0.3-2ubuntu<IP_ADDRESS>]
[23:29] -queuebot:#ubuntu-release- New binary: fheroes2 [armhf] (noble-proposed/none) [1.0.9+dfsg-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: rust-h3-quinn [s390x] (noble-proposed/none) [0.0.4-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: rust-rockusb [arm64] (noble-proposed/none) [0.1.3-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: rust-vsort [s390x] (noble-proposed/none) [0.2.0-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: kalk [s390x] (noble-proposed/none) [23.08.3-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: rust-rustix-openpty [s390x] (noble-proposed/none) [0.1.1-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: rust-powerfmt-macros [s390x] (noble-proposed/none) [0.1.0-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- Unapproved: accepted color-picker [source] (jammy-proposed) [1.0.3-2ubuntu<IP_ADDRESS>]
[23:30] -queuebot:#ubuntu-release- New binary: g-golf [s390x] (noble-proposed/none) [0.8.0~rc1-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: rust-sys-locale [s390x] (noble-proposed/none) [0.3.1-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: amberol [s390x] (noble-proposed/none) [0.10.3-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: rust-tikv-jemalloc-sys [s390x] (noble-proposed/none) [0.5.4-1] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: rust-rockusb [armhf] (noble-proposed/none) [0.1.3-1] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: rust-rockusb [s390x] (noble-proposed/none) [0.1.3-1] (no packageset)
[23:35] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (mantic-proposed) [45.2-0ubuntu3]
[23:35] -queuebot:#ubuntu-release- New binary: massxpert2 [ppc64el] (noble-proposed/none) [8.3.0-1] (no packageset)
[23:40] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (mantic-proposed) [2023d-0ubuntu0.23.10]
[23:41] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (lunar-proposed) [2023d-0ubuntu0.23.04]
[23:42] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (jammy-proposed) [2023d-0ubuntu0.22.04]
[23:43] -queuebot:#ubuntu-release- Unapproved: accepted tzdata [source] (focal-proposed) [2023d-0ubuntu0.20.04]
[23:46] <vorlon> blackboxsw: you have a cloud-init in the unapproved queue, and an unverified cloud-init in -proposed
[23:48] <falcojr> based on https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2045582/comments/9 , we probably need to reject both, but the one currently in proposed can definitely be rejected
[23:48] -ubottu:#ubuntu-release- Launchpad bug 2045582 in cloud-init (Ubuntu Mantic) "sru cloud-init (23.4 update) Focal, Jammy, and Lunar, Mantic" [Undecided, Fix Committed]
[23:48] <falcojr> sorry, wrong comment. I meant this https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2045582/comments/8
[23:50] -queuebot:#ubuntu-release- New binary: massxpert2 [armhf] (noble-proposed/universe) [8.3.0-1] (no packageset)
[23:51] <vorlon> falcojr: then should someone mark the existing bug 'verification-failed'?
[23:52] -queuebot:#ubuntu-release- New binary: massxpert2 [s390x] (noble-proposed/universe) [8.3.0-1] (no packageset)
[23:54] -queuebot:#ubuntu-release- Unapproved: rejected horst [source] (mantic-proposed) [5.1-3ubuntu<IP_ADDRESS>]
[23:56] -queuebot:#ubuntu-release- New binary: massxpert2 [arm64] (noble-proposed/universe) [8.3.0-1] (no packageset)
[23:59] -queuebot:#ubuntu-release- Unapproved: accepted heimdal [source] (mantic-proposed) [7.8.git20221117.28daf24+dfsg-3ubuntu<IP_ADDRESS>]