| santa_ | good morning everyone | 07:33 |
|---|---|---|
| santa_ | RikMills: not a big drama, bu there's an extra test changelog entry in you last kglobalaccel (fw5) upload | 07:34 |
| RikMills | santa_: will look in a few mins | 07:35 |
| RikMills | santa_: fix uploaded and git pushed | 07:40 |
| santa_ | RikMills: nice! thank you | 07:45 |
| RikMills | santa_: I found an issue with ka-update-metadata. If I #comment #out a build dep in debian/control, ka-update-metadata appears to stop parsing or recognising build deps from then on in the file | 09:12 |
| santa_ | RikMills: I know, but that's a well known limitation of the python-debian library, in fact I had to remove your comments from purpose when packaging 6.4 | 09:13 |
| santa_ | RikMills: given that it's a limitation from python-debian, comments in control files also trigger wrap-and-sort malfunctioning | 09:14 |
| RikMills | santa_: ok, know I know then. thanks | 09:14 |
| santa_ | I'm really sorry about that | 09:14 |
| RikMills | *now | 09:14 |
| santa_ | I whish I had a solution | 09:14 |
| RikMills | don't be. it happens and I learned something | 09:14 |
| santa_ | furthermore, there's a snitize-debian-control program in KA, precisely to handle that | 09:15 |
| RikMills | had not spotted that | 09:16 |
| santa_ | there's also another tricky thing: consider a control file with a couple of paragraphs separated by a blank line | 09:16 |
| santa_ | imagine you put one one various spaces in that blank line | 09:17 |
| santa_ | that, at least back in the days would make wrap-and-sort and some KA programs go crazy | 09:18 |
| RikMills | urgh | 09:18 |
| santa_ | e.g. like wrap-and-sort removing one of the paragraphs | 09:18 |
| santa_ | I remember we hit both issues when the Plasma 4 -> Plasmna 5 upgrade happened here | 09:19 |
| RikMills | I came in at the tail end of a lot of that, so likely missed it | 09:20 |
| santa_ | I guess so, that sanitize-control-file programs must be one of the most ancient of the current programs of KA | 09:21 |
| * RikMills goes to specsavers | 09:22 | |
| sgmoore | morning | 10:38 |
| RikMills | sgmoore: hi | 11:37 |
| santa_ | sgmoore: hi (x2) | 11:42 |
| sgmoore | hi! | 11:42 |
| santa_ | RikMills: the thing you "workarounded" in purpose was missing from git, last time I checked :) | 11:44 |
| BluesKaj | Hi all | 11:49 |
| RikMills | santa_: have pushed the workarounded thing in git | 12:30 |
| RikMills | may change it at some point so the workaround is in the KF5 package instead | 12:31 |
| RikMills | which long term may be better | 12:31 |
| santa_ | RikMills: yes, perhabps we can add a separate package for the icons in kf6-purpose, then add a depend in the fw 5 counterpart | 12:34 |
| RikMills | perhaps. putting icons in a -bin package seems odd to start with | 12:38 |
| IrcsomeBot | <sgmoore> I don't understand how to do falkon. gbp-archive fetches the tar, but doesn't remove the files-excluded and so of course the patch fails. I have tried putting my own tar brought in by uscan —download-current-version that properly removes the files, but it is overwritten bad tar. @RikMills how did you successfully upload this darn thing? | 13:07 |
| IrcsomeBot | <RikMills> Is that in ocular or noble? (re @sgmoore: I don't understand how to do falkon. gbp-archive fetches the tar, but doesn't remove the files-excluded and so of course the patch fails. I have tried putting my own tar brought in by uscan —download-current-version that properly removes the files, but it is overwritten bad tar. @RikMills how did you successfully upload this darn thing?) | 13:08 |
| IrcsomeBot | <sgmoore> ocular | 13:08 |
| IrcsomeBot | <sgmoore> oracular too | 13:08 |
| santa_ | what they did with falkon is something terrible | 13:08 |
| IrcsomeBot | <sgmoore> I agree | 13:08 |
| santa_ | both in debian and ubuntu | 13:08 |
| santa_ | and worst of it, I bthered to fix it and the someone who tought he knows better synced the thing from debian | 13:09 |
| santa_ | * bothered | 13:09 |
| RikMills | santa_: yeah, I saw that :? | 13:09 |
| santa_ | sgmoore: if you have other things to do in the meantime please go ahead with them, I will have another look into it soon ;) | 13:10 |
| santa_ | I think the upstream tarball repacking is not actually needed, but I need to check better | 13:11 |
| santa_ | furthermore, they did the repacking in debian without adding a repack suffix | 13:11 |
| santa_ | what a disaster | 13:11 |
| IrcsomeBot | <RikMills> I did pull-lp-source and made changes in that and uploaded. than added those changes to git and tagged (re @sgmoore: I don't understand how to do falkon. gbp-archive fetches the tar, but doesn't remove the files-excluded and so of course the patch fails. I have tried putting my own tar brought in by uscan —download-current-version that properly removes the files, but it is overwritten bad tar. @RikMills how did you successfully uploa | 13:12 |
| IrcsomeBot | <RikMills> I did pull-lp-source and made changes in that and uploaded. then added those changes to git and tagged (re @sgmoore: I don't understand how to do falkon. gbp-archive fetches the tar, but doesn't remove the files-excluded and so of course the patch fails. I have tried putting my own tar brought in by uscan —download-current-version that properly removes the files, but it is overwritten bad tar. @RikMills how did you successfully uploa | 13:13 |
| IrcsomeBot | <sgmoore> Ok, I will try this method, thank you (re @RikMills: I did pull-lp-source and made changes in that and uploaded. then added those changes to git and tagged) | 13:13 |
| santa_ | and even worse: we don't have repacking support in KA yet because I have been busy with the fw6 + Attic dir support :) | 13:13 |
| RikMills | santa_: was it a repack? at one point they were using the tarball that kde or github (I forget which) automatically makes for a git tag | 13:15 |
| RikMills | *kde invents gitlab | 13:15 |
| santa_ | RikMills: yes, and also a repack if I'm not mistaken | 13:15 |
| RikMills | urgh^2 | 13:16 |
| RikMills | I was doing this before that person synced: https://launchpad.net/ubuntu/+source/falkon/23.08.0-1ubuntu1 | 13:18 |
| RikMills | santa_: there is a new upstream 24.05.2 falkon in gear, so we could do that with the correct tarball ;) | 13:23 |
| santa_ | oh yes, please | 13:23 |
| santa_ | in any case the falkon case it's interesting for whever I get into KA repack support | 13:24 |
| santa_ | previously I was checking if the tarball was repacked or not by checking the watch file | 13:25 |
| * RikMills hands santa_ a ghostwriter | 13:25 | |
| santa_ | now I know that's not good enough :) | 13:25 |
| IrcsomeBot | <sgmoore> hmm. falkon is qt6. guess that won't work on my jammy laptop. putting aside for now. | 13:43 |
| IrcsomeBot | <RikMills> Your change is in git? If so, I could add that to a new uptream release upload that uses the correct tarbal? | 13:46 |
| IrcsomeBot | <sgmoore> yeah, let me set to unreleaed and delete git tag | 13:46 |
| RikMills | sgmoore: santa_: https://launchpad.net/ubuntu/+source/falkon/24.05.2-0ubuntu1 | 14:57 |
| santa_ | ah, thanks a lot | 15:02 |
| santa_ | reading the changelog, now I understand what I did | 15:03 |
| santa_ | still, someone could argue that the tarball repacking is needed | 15:04 |
| IrcsomeBot | <sgmoore> yeah... skipping ghostwrite for now as is a repack | 15:05 |
| IrcsomeBot | <sgmoore> ghostwriter too | 15:05 |
| santa_ | but personally, once those js files come from source IMHO we could skip the repacking | 15:05 |
| IrcsomeBot | <sgmoore> that's what I don't understand. They are in source, we delete them, then patch them back in? It makes zero sense. | 15:06 |
| santa_ | it used to make sense | 15:11 |
| IrcsomeBot | <RikMills> @sgmoore I was also naughty and git a force push to git to clean things up, so you should delete you falkon clone and reclone if you want to have one still locally | 15:12 |
| santa_ | let me have a look so I can explain | 15:12 |
| IrcsomeBot | <RikMills> @sgmoore I was also naughty and did a force push to git to clean things up, so you should delete you falkon clone and reclone if you want to have one still locally | 15:12 |
| IrcsomeBot | <sgmoore> ok (re @RikMills: @sgmoore I was also naughty and did a force push to git to clean things up, so you should delete you falkon clone and reclone if you want to have one still locally) | 15:12 |
| santa_ | alright, so here it goes the explanation about the js files in falkon: | 15:17 |
| santa_ | these days falkon orig source tarball provide 4 js files in src/lib/data/html/ | 15:18 |
| santa_ | - jquery-ui.js and jquery-ui-1.12.1.js | 15:19 |
| santa_ | - jquery.js and jquery-1.12.4.js | 15:20 |
| santa_ | in both pairs the second is the source code of the first | 15:21 |
| santa_ | however, some time ago the falkon orig tarball provided only: | 15:21 |
| santa_ | - jquery-ui.js | 15:21 |
| santa_ | - jquery.js | 15:22 |
| santa_ | i.e. only the minified js without the source code | 15:22 |
| santa_ | so what they did is removing the minified files with Files-Excluded and add the non-minified files with the patch | 15:23 |
| santa_ | so that thing fits better with the DFSG | 15:24 |
| santa_ | but now, we have the source js files in the code, therefore, in my opinion, it's no longer needed to do that | 15:25 |
| santa_ | @sgmoore makes sense now? | 15:25 |
| IrcsomeBot | <sgmoore> yeah | 15:25 |
| santa_ | furthermore: | 15:25 |
| santa_ | now that I had a look at the debian/rules file, there's a few lines that we also should probably remove | 15:26 |
| RikMills | lets the apparmor fix migrate, then we can deal with any other changes | 15:28 |
| RikMills | *let | 15:28 |
| * RikMills is very tempted to add an epoch to prevent any more syncing ;) | 15:28 | |
| RikMills | but I resist | 15:28 |
| IrcsomeBot | <sgmoore> lol | 15:29 |
| santa_ | hahah | 15:33 |
| santa_ | in any case, when they did that they should have used a +dfsg prefix in the tarball | 15:34 |
| santa_ | and put the thing in the watch file | 15:34 |
| IrcsomeBot | <sgmoore> yup. also, why do they use github?! | 15:34 |
| santa_ | but what do you expect if they put a github link? | 15:35 |
| IrcsomeBot | <sgmoore> falkon is in release service.. | 15:35 |
| santa_ | sgmoore: here is my wild guess: | 15:35 |
| santa_ | the guy looked in download.kde.org, the he found that tarballs were separate in stable and unstable | 15:36 |
| IrcsomeBot | <RikMills> Why they have an upstream signing key in the packaging when they don't use the signed tars is bizarre | 15:36 |
| santa_ | so to have the pre-release versions he put the github thing, which covers both stable and unstable | 15:37 |
| RikMills | santa_: but you can have multiple watch line IIRC? | 15:37 |
| santa_ | but if you want to do that you can use a regex | 15:37 |
| santa_ | or put 2 lines | 15:38 |
| IrcsomeBot | <sgmoore> grumbles | 15:38 |
| santa_ | maybe the guy doesn't know | 15:38 |
| santa_ | maybe he doesn't know about download.kde.org | 15:38 |
| santa_ | who knows? | 15:38 |
| RikMills | I know he ignored the email I sent | 15:38 |
| santa_ | in any case, what do you expect from a linux distribution where the following happens to me: | 15:39 |
| santa_ | 1. I type man gcc | 15:39 |
| santa_ | 2. I find out theres no manpage | 15:40 |
| santa_ | 3. I try to install gcc-doc | 15:40 |
| santa_ | 4. wtf I can't find gcc-doc in the repos, what is going on? | 15:40 |
| santa_ | 5. I find out that gcc-doc is in the non-free repos. WTF THE GCC DOCS IN NON-FREE REALLY!? | 15:41 |
| IrcsomeBot | <sgmoore> hahaha | 15:42 |
| santa_ | 6. then I learn about this https://www.debian.org/vote/2006/vote_001 | 15:43 |
| santa_ | and that GR was vote by a majority of the people with the DD nobiliary title | 15:44 |
| RikMills | :facepalm | 15:44 |
| santa_ | go figure | 15:44 |
| santa_ | * was voted | 15:44 |
| IrcsomeBot | <sgmoore> omg | 15:45 |
| IrcsomeBot | <sgmoore> be back in an hour or so | 16:08 |
| santa_ | ack, good luck in whatever you are going to do | 16:09 |
| santa_ | ok, so... | 18:08 |
| santa_ | we have to post-pone the brefing about the fw 6.4 changes | 18:08 |
| santa_ | today, a new version of system arrived from -proposed to the normal release breaking all my autopkgtests containers | 18:09 |
| santa_ | so I had to do a workarounding session | 18:09 |
| santa_ | hopefully everything is fine now, and I'm rebuilding packages to test | 18:10 |
| * RikMills adds workarounding to local dictionary | 18:10 | |
| santa_ | but that's a derivative of the original one: workarounded | 18:10 |
| RikMills | spellcheckers don't know that | 18:11 |
| santa_ | I still have some brain fog today, even after having a night of normal sleep | 18:11 |
| Eickmeyer | That moment when I get an email that something broke, I have no idea what it is, and finally trace it to here. 😆 | 18:49 |
| arraybolt3 | Eickmeyer: heh, you got a reprepro build failure email too didn't you? :P | 18:57 |
| Eickmeyer | Yuuuuuuup! 😂 | 18:57 |
| arraybolt3 | I was like "Tritemio Maintainers... reprepro... BIONIC? What on earth did Launchpad eat this morning?" | 18:59 |
| arraybolt3 | "oh wait... ok nvm" | 18:59 |
| IrcsomeBot | <sgmoore> lol | 19:07 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!