/srv/irclogs.ubuntu.com/2022/02/11/#ubuntu-devel.txt

mwhudsonwaveform: "Is it possible to "grep" the archive01:06
mwhudsonfor any package which mentions --no-restart-after-upgrade, --no-restart-01:06
mwhudsonon-upgrade, or --no-stop-on-upgrade in its d/rules" you want sarnold for that :)01:06
amurraymwhudson: you can use debian codesearch to get a rough approximation - https://codesearch.debian.net/search?q=--no-%28stop%7Crestart%29-%28on%7Cafter%29-upgrade&literal=001:17
amurraybut this also includes results from debian/changelog as well as debian/rules01:18
amurrayand if you want something a bit easier to parse - use the codesearch-cli snap01:18
sarnoldmwhudson, waveform, https://termbin.com/gjc202:19
=== klebers_ is now known as klebers
eoli3nHi08:01
eoli3nwith snap packages i randomly get "cannot open path of the current working directory: Permission denied"08:01
eoli3nwe mount nfs homes on /home/$user08:01
eoli3nubuntu 20.04 up to date with snap up to date08:02
eoli3nits pretty annoying08:02
eoli3nthe problem is related to the host08:02
eoli3nsome hosts work, some don't08:02
eoli3npermissions and owner are properly set on the homedir08:03
eoli3ncodium is installed with --classic08:04
eoli3ni have that problem with codium and sublime08:05
eoli3nwhere can I get help on snap packages09:22
seb128eoli3n, try asking your question maybe?09:23
eoli3ni just did09:24
eoli3nyou weren't connected09:24
eoli3nseb128 https://x0.at/Dz_i.txt09:24
eoli3nwe authenticate users with email adress, so home owner is that account, but we create groups dismatching the username, would it be related to this ?09:25
eoli3nhttps://x0.at/GxCy.txt09:25
seb128eoli3n, https://forum.snapcraft.io/ is probably the best place to ask such questions09:25
schopinmwhudson: vorlon: yup, I indeed volunteered. Since the tests fail on migration-reference/0 this won't block glibc09:33
waveformsarnold, excellent -- very useful, thanks!10:02
utkarsh2102lenavoytek, racb: can you please take a look at LP: #1960464, is it a similar bug that you've been working on? I saw some activities on similar bugs by Lena, so I'd rather have Lena take a look once, at least.10:08
ubottuLaunchpad bug 1960464 in mysql-5.7 (Ubuntu) "mysql breaks apt, system, can't even be uninstalled" [Undecided, New] https://launchpad.net/bugs/196046410:08
schopinanyone here knows common-lisp packaging? pgloader is broken because cl-plus-ssl doesn't support openssl 3.0. Sadly, CL is quite foreign to me so fixing it won't be trivial10:58
ricotzdoko, hi, please don't do no change builds of libreoffice, there is a 7.3.1~rc1 which I waited for :(11:35
ricotzdoko, I leaning torwards cancelling the remaing running builds11:36
ricotzdidrocks, seb128, hi, any thoughts? ^11:37
ricotzlibreoffice 7.3.1.1 got tagged a few minutes ago, and I am going to upload it later11:39
didrocksricotz: I would say indeed the new upload is better as the previous one will stay stuck in proposed due to its dep on universe11:45
LaibschHello, I just noticed that focal has a more recent package for samba than jammy.  The reason for the newer package in focal is among others CVE-2021-43566 to which jammy is still vulnerable.  That left me wondering what the security policy is for ubuntu+1.  No security support or would this be considered a bug?  I was just wondering if I should open a ticket.  Obviously, I didn't think I'd open myself up to security pro11:46
Laibschting out ubuntu+1 before it's release.11:46
ubottuAll versions of Samba prior to 4.13.16 are vulnerable to a malicious client using an SMB1 or NFS race to allow a directory to be created in an area of the server file system not exported under the share definition. Note that SMB1 has to be enabled, or the share also available via NFS in order for this attack to succeed. <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43566>11:46
ricotzdidrocks, doko, I will stop the remaining builds in favour of the upcoming 7.3.1~rc1 build11:49
ahasenackhi, I have a question for the MIR (Main Inclusion Request) team members,12:29
ahasenacknfs-utils upstream (src:nfs-utils in main) pulled in code from another upstream project, for which we have a package in universe: src:libnfsidmap-regex12:30
ahasenackwould this require another MIR review? I mean, in general, once a package is in main, we don't apply the MIR guidelines to it anymore, and they can usually change the code as the project seems fit12:30
ahasenackthe actual code is one .c file but I can't just ignore the fact that we have it as a src package in universe currently12:31
ahasenack(or can I?)12:31
ahasenackmy options are basically a) build src:nfs-utils as usual, and remove src:libnfsidmap-regex from the archive; or b) build src:nfs-utils, don't install the regex bit, and keep building src:libnfsidmap-regex and package the regex bit in there as is done today12:32
ahasenack(b) will incurr in delta with debian12:32
ahasenackdebian will eventually remove src:libnfsidmap-regex from their archive12:33
tjaaltonahasenack: btw, sssd 2.6.3-1 is now in debian12:55
ahasenackso it is12:55
ahasenackcan we sync? I briefly looked, looks like some of our delta was adopted12:55
tjaaltonI haven't looked at the delta12:56
ahasenackk12:56
tjaaltonwill check12:56
ahasenackhm, i386, lto12:57
tjaaltoncommitted lto to git13:03
tjaaltonbut no, it's not syncable13:03
dokoricotz, it's a bad idea to cancel the amd64 build, while there are already successful builds in the archive13:06
ricotzdoko, I known, still it is the same situation as usual that the ppc64el/s390x are finished a couple of hours before the other archs13:14
lenautkarsh2102: I took a look at the bug you sent to me. I haven't seen anything like it with the other bugs I've been working on, although I've only been working on mysql8.0 rather than mysql5.7. I'll see if I can reproduce it in Bionic14:25
utkarsh2102lena: hey, I couldn't reproduce.15:01
=== genii-core is now known as genii
lenautkarsh2102: neither can I. Although there are some error messages in the output that are similar to ones I have seen when working with mysql-8.0. So it may be related to some other bugs I haven't reproduced yet15:12
utkarsh2102lena: ah, gotcha! Do you think you can reply to the bug, please?18:12
sorenI'm building a package where the original tarball contains two separate libraries, liba and libb. libb depends on liba. I've installed liba into debian/tmp, but libb's configure checks for liba by building a lib with "gcc [...] -la" which obvs doesn't look in debian/tmp. Is there a common way to solve this?18:18
sorenShould I be setting a LD_LIBRARY_PATH when running libb's configure?18:19
sorenNo, wait, that's a runtime setting. Ugh.18:22
ahasenackyou mean it build-depends on itself?18:25
sorenahasenack: You could say that. In a sense. It doesn't specify it in d/control. Also, this is a new package, so I'd still have the bootstrapping challenge.18:29
ahasenacktricky18:31
sorenSurprisingly so.18:32
sergiodjusually upstream handles this themselves (i.e., a top-level configure which is responsible for building liba and then libb with -la and the proper linking incantation needed)18:33
sergiodje.g., some packages bundle gnulib and build things like this18:33
sorenI can force it, no problem. Like, say, adding "-I$(DESTDIR)$(includedir) -L$(DESTDIR)$(libdir)" in CFLAGS, etc., but it feels like there should be a straightforward way to do this.18:34
sorensergiodj: There wasn't a top-level configure. I'm writing one and I'm getting stuck on this one problem.18:35
sorenDESTDIR should only be a "make install" time setting, not a configure time one.18:36
lenautkarsh2102: done19:14
=== pizza is now known as pizzaiolo
=== pizzaiolo is now known as piz
utkarsh2102lena: thank you!20:57

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