** Changed in: reseed (Ubuntu)
Status: In Progress => Fix Released
--
[can-not-install] maintainer script failure
https://bugs.launchpad.net/bugs/93721
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Here is another debdiff proposal using debconf for non-X systems +
update-notifier.
Cheers
** Attachment added: "reseed_1.1-3.3ubuntu1.debdiff"
http://librarian.launchpad.net/7058589/reseed_1.1-3.3ubuntu1.debdiff
--
[can-not-install] maintainer script failure
https://launchpad.net/bugs/93721
** Changed in: reseed (Ubuntu)
Assignee: (unassigned) => Albin Tonnerre
Status: Unconfirmed => In Progress
--
[can-not-install] maintainer script failure
https://launchpad.net/bugs/93721
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
Here is a debdiff proposal that could be a possible fix for that.
Let me know what you think about it
Cheers
** Attachment added: "reseed_1.1-3.3ubuntu1.debdiff"
http://librarian.launchpad.net/7046401/reseed_1.1-3.3ubuntu1.debdiff
--
[can-not-install] maintainer script failure
https://launchp
I disagree. A postinst script should not fail for reasons like this. It
may be run during a complex system operation (like a upgrade) and a
failing postinst will have consequences that go beyond the single
package. It should instead setup a debconf note or something like this
(or just do nothing).
According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=376670;msg=38,
it's not considered as a bug nor an issue in Debian as the whole package relies
on the network access.
Is it really worth merging it ?
Cheers
--
[can-not-install] maintainer script failure
https://launchpad.net/bugs/9
** Tags added: packaging
--
[can-not-install] maintainer script failure
https://launchpad.net/bugs/93721
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
