[Bug 1315342] [NEW] Stop appending 3rd party PPA names with warnings
Lee Hyde
1315342 at bugs.launchpad.net
Fri May 2 11:07:36 UTC 2014
Public bug reported:
Greetings Developers,
This isn't exactly a bug report in as much as it is a request to cease
utterly unneccissary and counter productive proceedures during a in-
place upgrade. Specifically the practice of appending the words
'disabled on upgrade to…' to any third-party PPA disabled during the
upgrade.
I realise of course that there is a geniune need to disable all third-
party PPAs, but the process of re-enabeling them is arduous enough with
the tools provided (namely software-properties-gtk) without having to
also remove these ammendments. For reasons that I won't go into, I keep
a stable of nearly 100 PPAs (although that includes source PPAs) and
software-properties-gtk is woefully ill designed for managing large
numbers of PPAs (e.g. enabeling via the tick box takes a good 4-5
seconds, thereafter the display resets to the top of the list, one
cannot both enable a PPA and edit it's name in the same action, etc…).
If you really must add a warning message, could you not patch software-
properties-gtk to display a warning pop-up the first time software-
properties-gtk is opened post upgrade? Although personally, the pop-up
which appears during the in-place upgrade process warning users about
the fact that these third-party PPA's are to be disabled is warning
enough for me.
Regards,
Lee.
P.S. I realise that there is likely a way to automate the process of
enabeling disabled PPA's and scrubing your 'disabled on upgrade to…'
ammendments. Alas, every script and software package I've tried thus far
has failed to do either. I'll no doubt investigate writing a working
script from scratch, but I really don't see why I should be in the
situation where I *need* to in the first place. The type of Ubuntu user
confident enough to use third-party PPAs isn't the kind of Ubuntu user
that *needs* or *wants* hand holding to this extent.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Tags: ppa repository software-properties-gtk
** Description changed:
Greetings Developers,
This isn't exactly a bug report in as much as it is a request to cease
utterly unneccissary and counter productive proceedures during a in-
place upgrade. Specifically the practice of appending the words
'disabled on upgrade to…' to any third-party PPA disabled during the
upgrade.
- I realise of course that there is a geniune need to disable any third
+ I realise of course that there is a geniune need to disable all third-
party PPAs, but the process of of re-enabeling them is arduous enough
with the tools provided (namely software-properties-gtk) without having
to also remove these ammendments. For reasons that I won't go into, I
keep a stable of nearly 100 PPAs (although that includes source PPAs)
and software-properties-gtk is woefully ill designed for managing large
numbers of PPAs (e.g. enabeling via the tick box takes a good 4-5
seconds, thereafter the display resets to the top of the list, one
cannot both enable a PPA and edit it's name in the same action, etc…).
If you really must add a warning message, could you not patch software-
properties-gtk to display a warning pop-up the first time software-
properties-gtk is opened post upgrade? Although personally, the pop-up
which appears during the in-place upgrade process warning me about the
fact that these third-party PPA's are to be disabled is warning enough
for me.
Regards,
Lee.
P.S. I realise that there is likely a way to automate the process of
enabeling disabled PPA's and scrubing your 'disabled on upgrade to…'
ammendments. Alas, every script and software package I've tried failed
to do either. I'll no doubt investigate writing a working script from
scratch, but I really don't see why I should be in the situation where I
*need* to in the first place. The type of Ubuntu user confident enough
to use third-party PPAs isn't the kind of Ubuntu user that *needs* or
*wants* hand holding to this extent.
** Description changed:
Greetings Developers,
This isn't exactly a bug report in as much as it is a request to cease
utterly unneccissary and counter productive proceedures during a in-
place upgrade. Specifically the practice of appending the words
'disabled on upgrade to…' to any third-party PPA disabled during the
upgrade.
I realise of course that there is a geniune need to disable all third-
- party PPAs, but the process of of re-enabeling them is arduous enough
- with the tools provided (namely software-properties-gtk) without having
- to also remove these ammendments. For reasons that I won't go into, I
- keep a stable of nearly 100 PPAs (although that includes source PPAs)
- and software-properties-gtk is woefully ill designed for managing large
+ party PPAs, but the process of re-enabeling them is arduous enough with
+ the tools provided (namely software-properties-gtk) without having to
+ also remove these ammendments. For reasons that I won't go into, I keep
+ a stable of nearly 100 PPAs (although that includes source PPAs) and
+ software-properties-gtk is woefully ill designed for managing large
numbers of PPAs (e.g. enabeling via the tick box takes a good 4-5
seconds, thereafter the display resets to the top of the list, one
cannot both enable a PPA and edit it's name in the same action, etc…).
If you really must add a warning message, could you not patch software-
properties-gtk to display a warning pop-up the first time software-
properties-gtk is opened post upgrade? Although personally, the pop-up
which appears during the in-place upgrade process warning me about the
fact that these third-party PPA's are to be disabled is warning enough
for me.
Regards,
Lee.
P.S. I realise that there is likely a way to automate the process of
enabeling disabled PPA's and scrubing your 'disabled on upgrade to…'
ammendments. Alas, every script and software package I've tried failed
to do either. I'll no doubt investigate writing a working script from
scratch, but I really don't see why I should be in the situation where I
*need* to in the first place. The type of Ubuntu user confident enough
to use third-party PPAs isn't the kind of Ubuntu user that *needs* or
*wants* hand holding to this extent.
** Description changed:
Greetings Developers,
This isn't exactly a bug report in as much as it is a request to cease
utterly unneccissary and counter productive proceedures during a in-
place upgrade. Specifically the practice of appending the words
'disabled on upgrade to…' to any third-party PPA disabled during the
upgrade.
I realise of course that there is a geniune need to disable all third-
party PPAs, but the process of re-enabeling them is arduous enough with
the tools provided (namely software-properties-gtk) without having to
also remove these ammendments. For reasons that I won't go into, I keep
a stable of nearly 100 PPAs (although that includes source PPAs) and
software-properties-gtk is woefully ill designed for managing large
numbers of PPAs (e.g. enabeling via the tick box takes a good 4-5
seconds, thereafter the display resets to the top of the list, one
cannot both enable a PPA and edit it's name in the same action, etc…).
If you really must add a warning message, could you not patch software-
properties-gtk to display a warning pop-up the first time software-
properties-gtk is opened post upgrade? Although personally, the pop-up
- which appears during the in-place upgrade process warning me about the
- fact that these third-party PPA's are to be disabled is warning enough
- for me.
+ which appears during the in-place upgrade process warning users about
+ the fact that these third-party PPA's are to be disabled is warning
+ enough for me.
Regards,
Lee.
P.S. I realise that there is likely a way to automate the process of
enabeling disabled PPA's and scrubing your 'disabled on upgrade to…'
ammendments. Alas, every script and software package I've tried failed
to do either. I'll no doubt investigate writing a working script from
scratch, but I really don't see why I should be in the situation where I
*need* to in the first place. The type of Ubuntu user confident enough
to use third-party PPAs isn't the kind of Ubuntu user that *needs* or
*wants* hand holding to this extent.
** Description changed:
Greetings Developers,
This isn't exactly a bug report in as much as it is a request to cease
utterly unneccissary and counter productive proceedures during a in-
place upgrade. Specifically the practice of appending the words
'disabled on upgrade to…' to any third-party PPA disabled during the
upgrade.
I realise of course that there is a geniune need to disable all third-
party PPAs, but the process of re-enabeling them is arduous enough with
the tools provided (namely software-properties-gtk) without having to
also remove these ammendments. For reasons that I won't go into, I keep
a stable of nearly 100 PPAs (although that includes source PPAs) and
software-properties-gtk is woefully ill designed for managing large
numbers of PPAs (e.g. enabeling via the tick box takes a good 4-5
seconds, thereafter the display resets to the top of the list, one
cannot both enable a PPA and edit it's name in the same action, etc…).
If you really must add a warning message, could you not patch software-
properties-gtk to display a warning pop-up the first time software-
properties-gtk is opened post upgrade? Although personally, the pop-up
which appears during the in-place upgrade process warning users about
the fact that these third-party PPA's are to be disabled is warning
enough for me.
Regards,
Lee.
P.S. I realise that there is likely a way to automate the process of
enabeling disabled PPA's and scrubing your 'disabled on upgrade to…'
- ammendments. Alas, every script and software package I've tried failed
- to do either. I'll no doubt investigate writing a working script from
- scratch, but I really don't see why I should be in the situation where I
- *need* to in the first place. The type of Ubuntu user confident enough
- to use third-party PPAs isn't the kind of Ubuntu user that *needs* or
- *wants* hand holding to this extent.
+ ammendments. Alas, every script and software package I've tried thus far
+ has failed to do either. I'll no doubt investigate writing a working
+ script from scratch, but I really don't see why I should be in the
+ situation where I *need* to in the first place. The type of Ubuntu user
+ confident enough to use third-party PPAs isn't the kind of Ubuntu user
+ that *needs* or *wants* hand holding to this extent.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1315342
Title:
Stop appending 3rd party PPA names with warnings
Status in “ubuntu-release-upgrader” package in Ubuntu:
New
Bug description:
Greetings Developers,
This isn't exactly a bug report in as much as it is a request to cease
utterly unneccissary and counter productive proceedures during a in-
place upgrade. Specifically the practice of appending the words
'disabled on upgrade to…' to any third-party PPA disabled during the
upgrade.
I realise of course that there is a geniune need to disable all third-
party PPAs, but the process of re-enabeling them is arduous enough
with the tools provided (namely software-properties-gtk) without
having to also remove these ammendments. For reasons that I won't go
into, I keep a stable of nearly 100 PPAs (although that includes
source PPAs) and software-properties-gtk is woefully ill designed for
managing large numbers of PPAs (e.g. enabeling via the tick box takes
a good 4-5 seconds, thereafter the display resets to the top of the
list, one cannot both enable a PPA and edit it's name in the same
action, etc…).
If you really must add a warning message, could you not patch
software-properties-gtk to display a warning pop-up the first time
software-properties-gtk is opened post upgrade? Although personally,
the pop-up which appears during the in-place upgrade process warning
users about the fact that these third-party PPA's are to be disabled
is warning enough for me.
Regards,
Lee.
P.S. I realise that there is likely a way to automate the process of
enabeling disabled PPA's and scrubing your 'disabled on upgrade to…'
ammendments. Alas, every script and software package I've tried thus
far has failed to do either. I'll no doubt investigate writing a
working script from scratch, but I really don't see why I should be in
the situation where I *need* to in the first place. The type of Ubuntu
user confident enough to use third-party PPAs isn't the kind of Ubuntu
user that *needs* or *wants* hand holding to this extent.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1315342/+subscriptions
More information about the foundations-bugs
mailing list