Karmic Koala open for development
Karmic Koala open for development
Posted Apr 29, 2009 23:13 UTC (Wed) by muwlgr (guest, #35359)In reply to: Karmic Koala open for development by sbergman27
Parent article: Karmic Koala open for development
LP:298085 - I had a system with Postfix as smtp MTA and Courier as pop3/imap server. Postfix was configured to use Courier's maildrop program as a local MDA for virtual domains. Having upgraded from Ubuntu 8.04 to 8.10, and from Courier maildrop 0.58 to 0.60, I found that maildrop was recompiled without Courier authlib support, thus losing the ability to deliver to the virtual domain mailboxes configured in Courier's userdb. This behaviour is still kept in Ubuntu 9.04.
LP:352622 - the fix is trivial. Just a recompile. But who would recompile this thing, me ? And how big is my chance to get an updated package during the lifetime of Ubuntu 9.04 ? And similar things happen not the first time, with other packages before. The simpler is the fix, the longer you have to wait for update from Ubuntu maintainers. The more you have to rely on your own mind and hands. Which defeats the whole purpose an benefit of distribution-making, I think.
LP:366967 - don't know if it is worth to copy the whole description here. All symptoms are visible. Mindless race to a faster boot. Undermaintainment of an once-critical subsystem. Who needs this ifupdown and interfaces(5), we solve everything with network-manager now, right ? (wrong, I have some complex server and router configs). I propose a working fix there, and would you guess my (and other's) chances to get an useful update during Jaunty lifetime ? Zero or more ?
Debian:513102 - the fix is trivial again. Just give some review to the bugs fixed in Debian after Debian-Import-Freeze happened in Ubuntu, and soon before your release. Just don't try to keep all Debian bugs frozen for about 5 months. I doubt heavily that Ubuntu adds any vaulable specific patches to 'squid' package, and that moving from version 2.7stable3 to 2.7stable6 would bring more breakage than keeping the bug 513102 unfixed.
I hope I have certain ground to state my griefs here and in the Launchpad.
Please correct me if I am anywhere wrong.
Posted Apr 30, 2009 0:51 UTC (Thu)
by sbergman27 (guest, #10767)
[Link] (4 responses)
#35622 is on pptpd. Which is, at least, an actual Canonical-maintained package. But the problem does not look major, and it's hardly an old bug. Just 29 days.
On #298085... I usually give serious consideration to using core packages for a given purpose when I am setting up a server. For Ubuntu, that would be Postfix and Dovecot, rather than Postfix and Courier. It's nice to have all those 21,000 packages available for easy installation. But it doesn't mean you can expect platinum service when some package in Universe has a minor problem.
Posted Apr 30, 2009 5:28 UTC (Thu)
by muwlgr (guest, #35359)
[Link] (1 responses)
"You are trying to report a bug in the package outside of Ubuntu-main.
So please prefer the following way of actions :
1. Install a Debian-unstable version of this package on your system
This would teach me (and many others) to do the right things very soon.
Posted May 8, 2009 14:32 UTC (Fri)
by zenaan (guest, #3778)
[Link]
Posted Apr 30, 2009 5:39 UTC (Thu)
by muwlgr (guest, #35359)
[Link] (1 responses)
Re LP:352622, is there a minimal age limit for such bugs ? How long should the bug in 'main' stay unresolved to deserve an action from Ubuntu side ?
Posted Apr 30, 2009 23:02 UTC (Thu)
by Yasumoto (guest, #42642)
[Link]
The important thing to note about freezes is that they are there for a reason. If a fix/patch is "trivial" (which is a very vague term) then there should be no problems applying it. However, it is difficult to decide whether to introduce new code without giving it ample testing, since it may also include new bugs. I think it was Mark Shuttleworth that recently stated "The bug you know is better than the one you don't". There's a responsibility to the millions of users to not introduce breakage into their systems.
I know it takes a lot of work, and in an ideal world, bugs would magically get fixed, but that's not the case. If these issues are important to you, get on IRC or a mailing list and get some communication flowing.
Karmic Koala open for development
Karmic Koala open for development
Ubuntu really does not have that much resources to handle your report quickly and efficiently enough.
(rebuild it from the source if needed);
2. If the bug persists, report it to Debian maintainers;
3. If you find it is fixed in Debian, please tell us."
Karmic Koala open for development
Karmic Koala open for development
Karmic Koala open for development