Re: tarball types (was: [ANNOUNCE] xf86-input-libinput 1.2.1)
On Mon, Jan 24, 2022 at 03:53:23PM -0800, Alan Coopersmith wrote: > On 1/23/22 21:18, Peter Hutterer wrote: > > xf86-input-libinput 1.2.1 is now available. Primarily a few typos and misc > > minor fixes, the most visible change to distributions is that we now ship an > > xz tarball instead of bz2. Due to a global shortage of flying cars, you will > > have to accept that as your "welcome to the future" present. If you don't > > like > > the future (and who can blame you!), we still have gz tarballs, simply > > because I didn't realize we still generated those until I typed out this > > email. > > While I've been applying this change across the Xorg modules, I've followed > the lead of those who came before me, and just replaced "dist-bz2" with > "dist-xz". To get rid of the gzip files we'd also have to add "no-dist-gzip" > to our AM_INIT_AUTOMAKE() options. > > Since it's been a decade since GNOME switched to exclusively releasing xz > tarballs [1], I would expect there being no major headaches to us doing the > same now, we just hadn't thought much about it. Is this something we want to > do? Does anyone have a reason we shouldn't stop making .gz files? > (It looks like xwayland is already doing xz-only releases now.) anything that uses meson is .xz only, so that'd explain xwayland and will soon explain anything else that switches (e.g. xkeyboard-config is going to be meson-only too with the next release). Cheers, Peter
Re: tarball types (was: [ANNOUNCE] xf86-input-libinput 1.2.1)
On Mon, Jan 24, 2022 at 03:53:23PM -0800, Alan Coopersmith wrote: > On 1/23/22 21:18, Peter Hutterer wrote: > > xf86-input-libinput 1.2.1 is now available. Primarily a few typos and misc > > minor fixes, the most visible change to distributions is that we now ship an > > xz tarball instead of bz2. Due to a global shortage of flying cars, you will > > have to accept that as your "welcome to the future" present. If you don't > > like > > the future (and who can blame you!), we still have gz tarballs, simply > > because I didn't realize we still generated those until I typed out this > > email. > > While I've been applying this change across the Xorg modules, I've followed > the lead of those who came before me, and just replaced "dist-bz2" with > "dist-xz". To get rid of the gzip files we'd also have to add "no-dist-gzip" > to our AM_INIT_AUTOMAKE() options. > > Since it's been a decade since GNOME switched to exclusively releasing xz > tarballs [1], I would expect there being no major headaches to us doing the > same now, we just hadn't thought much about it. Is this something we want to > do? Does anyone have a reason we shouldn't stop making .gz files? > (It looks like xwayland is already doing xz-only releases now.) > > [1] > https://mail.gnome.org/archives/devel-announce-list/2011-September/msg3.html > > -alan- "Xz format inadequate for long-term archiving": https://www.nongnu.org/lzip/xz_inadequate.html
tarball types (was: [ANNOUNCE] xf86-input-libinput 1.2.1)
On 1/23/22 21:18, Peter Hutterer wrote: xf86-input-libinput 1.2.1 is now available. Primarily a few typos and misc minor fixes, the most visible change to distributions is that we now ship an xz tarball instead of bz2. Due to a global shortage of flying cars, you will have to accept that as your "welcome to the future" present. If you don't like the future (and who can blame you!), we still have gz tarballs, simply because I didn't realize we still generated those until I typed out this email. While I've been applying this change across the Xorg modules, I've followed the lead of those who came before me, and just replaced "dist-bz2" with "dist-xz". To get rid of the gzip files we'd also have to add "no-dist-gzip" to our AM_INIT_AUTOMAKE() options. Since it's been a decade since GNOME switched to exclusively releasing xz tarballs [1], I would expect there being no major headaches to us doing the same now, we just hadn't thought much about it. Is this something we want to do? Does anyone have a reason we shouldn't stop making .gz files? (It looks like xwayland is already doing xz-only releases now.) [1] https://mail.gnome.org/archives/devel-announce-list/2011-September/msg3.html -alan-
RE: Development branch to create MR
Hello Alan, Thanks for the pointer, I have created the MR https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/855 Regards Shashank -Original Message- From: Alan Coopersmith Sent: Thursday, January 20, 2022 5:35 PM To: Sharma, Shashank ; Povilas Kanapickas ; xorg-devel@lists.x.org Subject: Re: Development branch to create MR You need to create your own fork on gitlab.freedesktop.org and push the branch there to make a merge request from - you should not be pushing directly to the /xorg/ repository to do this. -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Engineering - https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblogs.oracle.com%2Fsolaris&data=04%7C01%7CShashank.Sharma%40amd.com%7Cdc8402f5199f4af428aa08d9dc32dee4%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637782934666994901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=eu4Wm%2F%2FK00L%2Bqgxy6H0sL4GFZQyXWnT4Erc%2B5Ke2GtE%3D&reserved=0 On 1/20/22 02:26, Sharma, Shashank wrote: > Hello Povilas, > Thanks for your reply, > > I am getting this error message while trying to push the branch: > > git push origin push-pci-hotplug > Username for > 'https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2F&data=04%7C01%7CShashank.Sharma%40amd.com%7Cdc8402f5199f4af428aa08d9dc32dee4%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637782934666994901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=1LJqCA4aLBxV2f1%2Fh0tnKmA95C0E7JGCF72fUjZiThA%3D&reserved=0': > contactshashanksha...@gmail.com Password for > 'https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcontactshashanksharma%3Acontactshashanksharma%2540gmail.com%40gitlab.freedesktop.org%2F&data=04%7C01%7CShashank.Sharma%40amd.com%7Cdc8402f5199f4af428aa08d9dc32dee4%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637782934666994901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=2VAJWW%2BGfcZglGz7uvGA9pmtlumfgdE%2FOZLGwc20siM%3D&reserved=0': > remote: You are not allowed to push code to this project. > fatal: unable to access > 'https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit > lab.freedesktop.org%2Fxorg%2Fxserver.git%2F&data=04%7C01%7CShashan > k.Sharma%40amd.com%7Cdc8402f5199f4af428aa08d9dc32dee4%7C3dd8961fe4884e > 608e11a82d994e183d%7C0%7C0%7C637782934666994901%7CUnknown%7CTWFpbGZsb3 > d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7 > C3000&sdata=UPALng1HoFqe4iZOipI1HSZUi9S0RkL6%2FUZzSyvBtLI%3D&r > eserved=0': The requested URL returned error: 403 > > Do I need to add some security checks before I can push for a MR ? > Please excuse me if this is some basic mistake in the setup. > > Regards > Shashank > -Original Message- > From: Povilas Kanapickas > Sent: Wednesday, January 19, 2022 5:25 PM > To: Sharma, Shashank ; xorg-devel@lists.x.org > Subject: Re: Development branch to create MR > > On 1/19/22 5:47 PM, Sharma, Shashank wrote: >> Hello Xorg community and maintainers, >> >> I am Shashank Sharma from AMD Linux graphics development team. >> >> >> >> I have some patches to be reviewed and pushed into Xserver code, >> which are related to the GPU hot-plug handling. >> >> May I know which branch should I target to create the MR and start >> the review request ? > > Use the master branch. > > Regards, > Povilas
