** Tags added: patch
--
"pound" postinst breaks during dapper to edgy dist-upgrade
https://bugs.launchpad.net/bugs/67913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
I've ubsubscribed ubuntu-ubiverse-sponsors from this bug, as I cannot
find nything that requires upload or approval yet. Please resubscribe
ubuntu-universe-sponsors when there is a patch to apply or a sync to
approve. Thank you.
--
"pound" postinst breaks during dapper to edgy dist-upgrade
http
** Changed in: pound (Ubuntu)
Status: Needs Info => Unconfirmed
--
"pound" postinst breaks during dapper to edgy dist-upgrade
https://bugs.launchpad.net/bugs/67913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-b
I've seen that this bug is still in state "needs info". Do you still
miss some beyond the ones I've given???
--
"pound" postinst breaks during dapper to edgy dist-upgrade
https://launchpad.net/bugs/67913
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
>From what I understand I'd say it's a shortcoming because it kills the
upgrade and leaves the user with a potentially unstable system. I would
expect that the upgrade would acknowledge it couldn't process a given
package and give the user the option to exclude/remove the package and
finish the upg
** Tags added: edgy-upgrade
--
"pound" postinst breaks during dapper to edgy dist-upgrade
https://launchpad.net/bugs/67913
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for this added information.
This is really no shortcoming of the ubuntu packaging tools in use, but
a bug in the package itself.
--
"pound" postinst breaks during dapper to edgy dist-upgrade
https://launchpad.net/bugs/67913
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Wow, that's a change of syntax!
I can understand that the package scripts cannot change this file
automatically. But then, why not showing the end-user a screen with the
new default config file and asking whether this new file should replace
the old one. (Maybe I'm expecting too much but I must ad
Here is my pound config file.
Having tried to launch it manually from the command-line and in verbose mode,
it seems that pound has problem parsing it. Looking in the pound man page, I've
found that the configuration file syntax has change.
I'll modify it until Pound can be started and then I'll
I tried to reproduce this on a stock pound install/upgrade and was
unable to reproduce it. Is this maybe releated to some customization in
pounds config?
** Changed in: pound (Ubuntu)
Status: Confirmed => Needs Info
--
"pound" postinst breaks during dapper to edgy dist-upgrade
https://lau
** Summary changed:
- unable to install pound during dapper to edgy dist-upgrade
+ "pound" postinst breaks during dapper to edgy dist-upgrade
--
"pound" postinst breaks during dapper to edgy dist-upgrade
https://launchpad.net/bugs/67913
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
11 matches
Mail list logo