/srv/irclogs.ubuntu.com/2020/04/22/#launchpad.txt

=== diddledan9 is now known as diddledan
=== cpaelzer__ is now known as cpaelzer
seb128hey there13:21
seb128is there a way to upload a translation template for a package which hasn't imported one yet? or does that require a source upload?13:21
seb128I can't find a link on e.g https://translations.launchpad.net/ubuntu/focal/+source/memtest86+/+translations13:21
seb128ilasc, ^ do you know?13:29
ilascseb128: i don't unfortunately, trying to get you some answers now13:31
seb128ilasc, thanks13:31
cjwatsonseb128: I am reasonably sure it requires a source upload in the case where there's no template yet13:39
cjwatsonlp.translations.browser.productseries has a ProductSeriesUploadView for that but there's no equivalent for source packages13:39
seb128cjwatson, ok, that's what it looks like, thanks13:39
cjwatsonilasc: ^-13:39
seb128it's not important for release, I will wait and do a no change upload SRU13:40
seb128(or maybe just accept/then reject)13:40
seb128other translation related question14:20
seb128any idea why when I do an export on https://translations.launchpad.net/snap-store/trunk14:20
seb128(using https://translations.launchpad.net/snap-store/trunk/+export)14:20
seb128I get a tarball (https://launchpadlibrarian.net/475716490/launchpad-export.tar.gz)14:20
seb128with the po split in 2 subdirs, po/ and snap-store/14:20
seb128there is only one domain, I would expect to have one subdir14:21
cjwatsonNo idea at the moment - could you file a bug?14:22
seb128sure14:23
seb128https://bugs.launchpad.net/launchpad/+bug/187426914:26
ubot5Ubuntu bug 1874269 in Launchpad itself "Translations export from a project give a tarball with split directories" [Undecided,New]14:26
EickmeyerWhat do we do about users who insist on using profanity in the bug report and/or in comments? bug 186238316:54
ubot5bug 1862383 in gimp (Ubuntu) "GIMP Crashes when pasted image copied from it into another app" [Undecided,Confirmed] https://launchpad.net/bugs/186238316:54
oerhekshe changed topic, but his last comment is not helpfull16:59
EickmeyerI'm considering closing the bug as "won't fix" because of the attitude (he's not even running latest version of GIMP)17:00
cjwatsonI've written a warning to the bug17:00
EickmeyerI wrote one too, cjwatson.17:00
cjwatsonIn the sense of a formal warning before account-ban-type action17:01
EickmeyerRight.17:01
Eickmeyercjwatson: Thanks for looking into the matter. :)17:02
hggdhthey are repeat offenders. I have had issues with them on our mailing lists as well, and on other LP bugs19:39
cjwatsonI can indeed see a problematic history, but I think this is the first time we've given them a formal warning19:48
hggdhoh, certainly. I am a firm believer in giving out more chances for redemption20:19
sim590How does one know the version number of the package that is associated with the patch that someone links on a report page? https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996 I'm on Debian and I would like to import the patches that are listed there, but they don't all apply on the version that I downloaded from Debian.21:42
ubot5Ubuntu bug 1867996 in libappindicator (Arch Linux) "Segfault in app_indicator_set_icon_full [patch attached]" [Undecided,New]21:42
cjwatsonsim590: Patch files are just text, so the only things even theoretically available are (a) indications in the patch file itself or (b) maybe contextual clues like the time the patch was created21:46
cjwatsonsim590: The top of the patches there seems to have at least part of the version number.  But if it doesn't apply even given that, then you'll just have to work out how to resolve the differences - no magic bullet for that21:46
sim590The thing is that the version number on Ubuntu seems all wrong and I don't understand why. It syas 12.10.0, but the version of the package is clearly not above 1. On Debian, it is 0.4.92. So It seems like it is really irrelevant number...21:51
cjwatsonsim590: The package originated in Ubuntu, so it's more likely that Debian chose a different versioning scheme21:54
cjwatsonOr didn't move forward to newer versions from Ubuntu21:55
cjwatsonsim590: You can find the full Ubuntu history on https://launchpad.net/ubuntu/+source/libappindicator/+publishinghistory21:55
cjwatsonsim590: Looking at https://launchpad.net/ubuntu/+source/libappindicator it seems likely that Debian just didn't take later updates from Ubuntu21:55
sim590The Ubuntu package version number just doesn't make any reference to the project upstream version number.... How can I /upstream,22:11
sim590Well.. I didn't want to write that last message just yet..................22:12
sim590Event the .orig tarballs don't include the version number of the upstream project....22:14
cjwatsonI don't know, sorry.  All I can do is give those pointers above22:17
sim590OK. Well. I guess I will just recreate the patches because version numbers just make this impossible. Plus, it seems like debian and ubuntu have diverged on the version they both use, or may be I don't understand.23:49
cjwatsonIt does seem as though there has been divergence, yes.23:55

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