Re: [arch-projects] [netctl] news draft
On 08/03/2018 02:10 PM, Jouke Witteveen wrote: > On Fri, Aug 3, 2018 at 7:57 PM Eli Schwartz via arch-projects > wrote: >> >> On 08/03/2018 01:48 PM, Jouke Witteveen via arch-projects wrote: >>> Hello all, >>> >>> I cannot send to arch-dev-public and don't know where to post this >>> otherwise, so I'll just put this out here. >>> >>> With systemd 239, a deprecation message is printed in the journal for >>> enabled netctl profiles (FS#59494). This currently has no effect on >>> the functionality of either systemd or netctl. Nevertheless, the next >>> version of netctl, which is not yet released, will move away from the >>> deprecated features. However, the warnings are caused by unit files >>> generated by netctl, so an update will not simply make the warnings go >>> away. >>> Here is a draft for a news post to accompany the next version of >>> netctl down the line. >>> >>> Regards, >>> - Jouke >>> >>> Title: netctl 1.18 may require manual intervention >>> >>> In response to the explicit deprecation of .include statements in >>> systemd units, netctl has modified its unit management. This change >>> only affects individually enabled netctl profiles. To use the new >>> management scheme, all enabled profiles must be reenabled after >>> updating netctl. This can be done through `netctl reenable `. >>> No action is needed for the automatic netctl services. >> >> Why would it need manual intervention? Does netctl not work if you use >> the old format? From systemd's side, the whole reason it is a >> deprecation warning is because it will continue to work for some time >> until they finally ditch it entirely. >> >> I would assume that existing netctl profiles which aren't reenabled >> would continue to successfully use the old, deprecated unit files? > > Indeed, I expect the generated units to continue to work for a little > longer, but at https://github.com/systemd/systemd/pull/8530 there is > already a suggestion to proceed the deprecation further. I think it is > nice to tell people what to do if they are bothered by the deprecation > warning in their logs. Maybe in a different wording, stressing that > nothing will break (for now) if you don't reenable your profiles? I'm not sure I understand the suggestion to mark it as tainted, what exactly is "tainted" about using deprecated stuff? I think systemd's builtin deprecation policies are probably sufficient for now, especially as nothing actually breaks for now. In this case I would not use a news post, but I might consider a post_upgrade function in an install script for netctl itself which runs once for the upgrade from 1.17 to (unreleased) 1.18, warning users to refresh their profiles. News posts are usually for things which require manual intervention *before* updating. And as long as 1.18 isn't released yet, I guess it makes no sense at all to warn people about something they cannot do yet. :D -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-projects] [netctl] news draft
On Fri, Aug 3, 2018 at 7:57 PM Eli Schwartz via arch-projects wrote: > > On 08/03/2018 01:48 PM, Jouke Witteveen via arch-projects wrote: > > Hello all, > > > > I cannot send to arch-dev-public and don't know where to post this > > otherwise, so I'll just put this out here. > > > > With systemd 239, a deprecation message is printed in the journal for > > enabled netctl profiles (FS#59494). This currently has no effect on > > the functionality of either systemd or netctl. Nevertheless, the next > > version of netctl, which is not yet released, will move away from the > > deprecated features. However, the warnings are caused by unit files > > generated by netctl, so an update will not simply make the warnings go > > away. > > Here is a draft for a news post to accompany the next version of > > netctl down the line. > > > > Regards, > > - Jouke > > > > Title: netctl 1.18 may require manual intervention > > > > In response to the explicit deprecation of .include statements in > > systemd units, netctl has modified its unit management. This change > > only affects individually enabled netctl profiles. To use the new > > management scheme, all enabled profiles must be reenabled after > > updating netctl. This can be done through `netctl reenable `. > > No action is needed for the automatic netctl services. > > Why would it need manual intervention? Does netctl not work if you use > the old format? From systemd's side, the whole reason it is a > deprecation warning is because it will continue to work for some time > until they finally ditch it entirely. > > I would assume that existing netctl profiles which aren't reenabled > would continue to successfully use the old, deprecated unit files? Indeed, I expect the generated units to continue to work for a little longer, but at https://github.com/systemd/systemd/pull/8530 there is already a suggestion to proceed the deprecation further. I think it is nice to tell people what to do if they are bothered by the deprecation warning in their logs. Maybe in a different wording, stressing that nothing will break (for now) if you don't reenable your profiles? Regards, - Jouke
Re: [arch-projects] [netctl] news draft
On 08/03/2018 01:48 PM, Jouke Witteveen via arch-projects wrote: > Hello all, > > I cannot send to arch-dev-public and don't know where to post this > otherwise, so I'll just put this out here. > > With systemd 239, a deprecation message is printed in the journal for > enabled netctl profiles (FS#59494). This currently has no effect on > the functionality of either systemd or netctl. Nevertheless, the next > version of netctl, which is not yet released, will move away from the > deprecated features. However, the warnings are caused by unit files > generated by netctl, so an update will not simply make the warnings go > away. > Here is a draft for a news post to accompany the next version of > netctl down the line. > > Regards, > - Jouke > > Title: netctl 1.18 may require manual intervention > > In response to the explicit deprecation of .include statements in > systemd units, netctl has modified its unit management. This change > only affects individually enabled netctl profiles. To use the new > management scheme, all enabled profiles must be reenabled after > updating netctl. This can be done through `netctl reenable `. > No action is needed for the automatic netctl services. Why would it need manual intervention? Does netctl not work if you use the old format? From systemd's side, the whole reason it is a deprecation warning is because it will continue to work for some time until they finally ditch it entirely. I would assume that existing netctl profiles which aren't reenabled would continue to successfully use the old, deprecated unit files? -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-projects] [netctl] News draft
On Sun, Apr 7, 2013 at 9:27 PM, Florian Pritz bluew...@xinu.at wrote: On 27.03.2013 10:44, Jouke Witteveen wrote: I have tagged version 0.8 of netctl and based on Florians usual response times, it will hit [testing] soon. If no major bugs pop up in the coming week (or two), I would like this to be the first version to make it to [core]. I don't see any bugs on the tracker. Good to move? I am very happy with this one. Lets move! Don't forget that openresolv needs to move as well if we aim for [core] (which I think we do). When will we drop netfg? No one has expressed any interest in maintaining it. CC'ed arch-dev-public for comments on the news draft below: I've got a small thing to add, as people tend to overlook wifi-menu. The updated version (one added sentence) is below. Thanks all, - Jouke ---netctl is now in [core]--- Meet netctl: a profile based networking CLI using systemd. In the near future, the old netcfg will be removed from [core]. Anyone using it is urged to move to netctl. Migration is a manual process during which you might not have access to the Internet, so take care and read the man pages (netctl(1), netctl.profile(5) and netctl.special(7)). The design of netctl is so that systemd enthusiasts will appreciate its usage and netcfg users will be familiar with its profile files. As you install netctl, netcfg will be removed, but the enabled systemd services will remain until manually disabled. The [wiki:netctl wiki] holds some additional information on migrating from netcfg. -- ---netctl is now in [core]--- Meet netctl: a profile based networking CLI using systemd. In the near future, the old netcfg will be removed from [core]. Anyone using it is urged to move to netctl. Migration is a manual process during which you might not have access to the Internet, so take care and read the man pages (netctl(1), netctl.profile(5) and netctl.special(7)). The design of netctl is so that systemd enthusiasts will appreciate its usage and netcfg users will be familiar with its profile files. Shipped with netctl comes a ncurses-based wifi connection assistant called wifi-menu. As you install netctl, netcfg will be removed, but the enabled systemd services will remain until manually disabled. The [wiki:netctl wiki] holds some additional information on migrating from netcfg. --
