alkisgHi, where would I file a request to change the development iso names from e.g. jammy-desktop-amd64.iso to e.g. ubuntu-mate-jammy-20211020-amd64.iso?07:56
alkisgThe main point is for the flavor to appear in the iso name; now we can't test/zsync many flavors without manually renaming them...07:56
toabctlcould somebody point me to the livefs build in launchpad for https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/  please?08:01
RikMillsalkisg: zsync -o ubuntu-mate-jammy-amd64.iso http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/jammy-desktop-amd64.iso.zsync08:02
RikMillsthat will read from a named seed file and write back to it08:02
seb128toabctl, https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/impish/ubuntu-server ?08:03
seb128toabctl, sorry, wrong serie, replace 'impish' :)08:03
RikMills"This live filesystem has not been built yet. "08:04
toabctlseb128, for jammy, there are no builds but there are files under cdimage.ubuntu.com08:04
seb128I guess that's the wrong one then, sorry08:05
seb128there is also an ubuntu-server-live08:06
alkisgRikMills: indeed, and wget -O file would also work for those that don't use zsync, but wouldn't it be nicer if they already had appropriate names?08:06
RikMillsseb128: snap08:06
seb128checking https://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-server that's the correct one08:07
RikMillsalkisg: guess I am just used to it being the way it is08:08
alkisgRikMills: I'd like to file the request somewhere for discussion, even if it's just going to be closed; is that OK? And if so, ...where?08:08
RikMillsalkisg: I would guess the people in #ubuntu-release who look after the ISO builds08:10
alkisgThank you!08:10
=== cpaelzer_ is now known as cpaelzer
schopinI'm looking at merging sshfs-fuse, but the MoM field has a comment stating that fuse3 breaks Kubuntu/Studio iso builds. ANyone knows if it's still the case? ( ginggs perhaps? )09:11
ginggsschopin: best is to speak to the person who TIL (touched it last) = RikMills09:13
ginggsi'm only tracking main packages for the fuse2 -> fuse3 transition09:14
schopinSure, but I figured you'd be aware of fuse3 breaking ISO builds though ;)09:15
ginggsi was not :)09:15
RikMillsit is still the case AFAIK. if the 2 -> 3 transition completes this cycle, we can pull in the sshfs-fuse that needs fuse309:15
seb128schopin, it's because other components try to pull the other version of fuse in and those are not co-installable09:15
seb128could we start this transition now?09:16
RikMillsthere is a bug for it ginggs?09:16
ginggsRikMills: LP: #193451009:17
ubottuLaunchpad bug 1934510 in fuse3 (Ubuntu) "[MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps" [Undecided, Incomplete] https://launchpad.net/bugs/193451009:17
ginggsI've just marked it new so the MIR approval team can have a look again09:18
RikMillshmmm. I thought there was a bug tracking the multiple packages needing porting09:19
seb128RikMills, there is a mailing list discussion which reference the packages and corresponding bug ids09:21
RikMillsaha, I am probably think of that. thanks09:21
schopinadded the MIR bug to the MoM comment so that other wandering contributors have more info :)09:21
cpaelzerRikMills:  https://lists.ubuntu.com/archives/ubuntu-devel/2021-July/041530.html09:22
ginggsas far as I can see we have patches for everything09:26
seb128cpaelzer, re fuse3, if we are confident we will transition during the cycle do you see any objection in promoting the new version and start using it? then we have the cycle to demote the previous one10:42

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