| === dviererbe1 is now known as dviererbe | ||
| Skia | doko: big_packages changes is merged :-) | 10:03 |
|---|---|---|
| toabctl | I realized that squid-deb-proxy is no longer available in plucky. looks like it got also removed from debian (#1081589) . is there a good replacement for squid-deb-proxy? | 10:04 |
| JackFrost | apt-cacher-ng is pretty much it...not that it works well. | 10:06 |
| doko | Skia: ta! | 10:19 |
| adrien | doh! apt-cacher-ng also has issues, and especially with ubuntu you can easily get it stuck | 10:30 |
| adrien | well, easily: not every day but once a month if you make moderate use of the proxy | 10:30 |
| Skia | do you have tips on how to unstuck it, while you're here? | 10:34 |
| JackFrost | Delete the cache, or aspects of it, restart. Sometimes restart does it. :P | 10:35 |
| Skia | yeah, okay, nothing more than what I already do :-) | 10:35 |
| adrien | I don't have better solutions. :/ | 10:54 |
| adrien | there's a bug report about it on bugs.d.o but the only thing it did was give me bad vibes from apt-cacher-ng maintenance and convince me that rolling your own caching instead of relying on a well-known cacher like squid was probably a bad idea | 10:55 |
| adrien | I think the way forward would be to get debug symbols for apt-cacher-ng and gdb -p into it when it get stuck but it gets stuck at the worst times by definition | 10:56 |
| cjwatson | Mm, OTOH using squid means you have to roll your own rules for cache retention of mutable metadata files, so it's kind of swings and roundabouts | 10:56 |
| adrien | that's a fair point but IIRC the discussion was about the potential effects of HTTP pipelining which is a non-trivial topic | 10:58 |
| adrien | especially wrt inter-implementation compliance | 10:58 |
| JackFrost | Oh, and I am using an older version because it seemed to suck less? | 11:00 |
| JackFrost | 3.7.5+really3.6.4-1vanir1 | 11:00 |
| adrien | unrelated: I'm preparing a change for python3.12 and update-maintainer says "XSBC-Original is managed by 'rules' file. Doing nothing." which seems fine but then dpkg-source complains that "Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address" (dpkg-source is called by sbuild --source); what is the solution there? | 11:05 |
| === gurupras- is now known as guruprasad | ||
| liushuyu | tsimonq2: Do you have a tracking bug for libgit2 1.9 transition somewhere on Launchpad? | 17:09 |
| tsimonq2 | liushuyu: Not at the moment. | 17:42 |
| liushuyu | I see | 17:42 |
| tsimonq2 | If you want to create one, go for it :) | 17:43 |
| tsimonq2 | Still haven't heard back from Utkarsh on the bug. | 17:43 |
| tsimonq2 | (Debian-side.) | 17:43 |
| liushuyu | tsimonq2: I have created one https://bugs.launchpad.net/ubuntu/+source/libgit2/+bug/2093205 | 17:54 |
| -ubottu:#ubuntu-devel- Launchpad bug 2093205 in rustc-1.83 (Ubuntu) "libgit2: libgit2 1.9 update and migration" [Undecided, New] | 17:54 | |
| tsimonq2 | liushuyu: Thanks! | 18:03 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!