Bug#410172: version missing on libnet-server-perl dependency
Package: amavisd-new Version: 2.4.2-5 While trying to update amavisd failed to restart: Setting up amavisd-new (2.4.2-5) ... Creating/updating amavis user account... Starting amavisd: Net::Server version 0.87 required--this is only version 0.85 at /usr/sbin/amavisd-new line 6405. BEGIN failed--compilation aborted at /usr/sbin/amavisd-new line 6405. (failed). invoke-rc.d: initscript amavis, action start failed. libnet-server-perl version was 0.85-3 Upgrading libnet-server-per to new version (apt-get install libnet-server-perl ; version installed 0.94-1) fixed the problem. Therefore, I think that amavisd-new dependency on libnet-server-perl should include version (= 0.87) i guess. -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410172: version missing on libnet-server-perl dependency
severity 410172 wishlist tag 410172 wontfix thanks On Thu, 08 Feb 2007, Aidas Kasparas wrote: libnet-server-perl version was 0.85-3 Sarge has libnet-server-perl 0.87-3 (in fact, 0.87-3sarge1), according to packages.qa.debian.org/libnet-server-perl. Direct upgrades from releases earlier than Sarge to Etch are not supported, so I am downgrading this bug to a wishlist request. Since the depends in libnet-server-perl are currently unversioned, I will not add a version to it unless it is necessary. Therefore, this request won't be addressed at this time. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410172: version missing on libnet-server-perl dependency
Henrique de Moraes Holschuh wrote: severity 410172 wishlist tag 410172 wontfix thanks On Thu, 08 Feb 2007, Aidas Kasparas wrote: libnet-server-perl version was 0.85-3 Sarge has libnet-server-perl 0.87-3 (in fact, 0.87-3sarge1), according to packages.qa.debian.org/libnet-server-perl. Direct upgrades from releases earlier than Sarge to Etch are not supported, so I am downgrading this bug to a wishlist request. Since the depends in libnet-server-perl are currently unversioned, I will not add a version to it unless it is necessary. Therefore, this request won't be addressed at this time. Henrique, please help me understand reasons of such decision (and don't repeat mistake I did by reporting this bug)? Why dependency without version is better than dependency with version? If uplink cared to code: use Net::Server 0.87; # need Net::Server::PreForkSimple::done he has very good reason to indicate that version 0.87 will not work. So why should debian package? And regarding from releases earlier than Sarge... am I the last person, who upgrades packages from testing just when he need some new feature or sees security report? I tought, if dependency was versioned, some person like me would be saved from trouble while upgrading. So, where my tought are wrong? -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410172: version missing on libnet-server-perl dependency
On Thu, 08 Feb 2007, Aidas Kasparas wrote: Why dependency without version is better than dependency with version? Versioned dependencies give a lot more work for apt to resolve dependency trees, and a misfeature of the apt system is that it does not support versioned provides, so if something ever provides a package, it won't meet any versioned depends. In other words, it is not good for apt to add them unless you do need them. he has very good reason to indicate that version 0.87 will not work. So why should debian package? Because a Etch debian package is supposed to work on Sid (pre-etch), Etch itself, and upgrade well from Sarge. And in those configurations, you *cannot* have a libnet-server-perl 0.87. If the apt cost for versioned deps was *zero*, I would have added the versioned depends a long time ago. And regarding from releases earlier than Sarge... am I the last person, who upgrades packages from testing just when he need some new You held out on upgrades of libnet-server-perl for more than 3 years? And you didn't ever upgraded to the latest *STABLE* Debian version? What Debian version are you running? I think I am missing some important detail here. Either that, or packages.qa.debian.org is lying, or someone did a very uncommon thing and added a new upstream version to Debian stable (I will check for this one right now). -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410172: version missing on libnet-server-perl dependency
On Thu, 08 Feb 2007, Aidas Kasparas wrote: And regarding from releases earlier than Sarge... am I the last person, who upgrades packages from testing just when he need some new feature or sees security report? I tought, if dependency was versioned, some person like me would be saved from trouble while upgrading. libnet-server-perl (0.85-3) unstable; urgency=low * debian/control: depends on libio-multiplex-perl (closes: #192921) -- Luca Filipozzi [EMAIL PROTECTED] Sat, 17 May 2003 16:00:32 -0700 Please explain to me how you had the above package installed in a Debian Sarge system. Sarge was released on 2005, and has version 0.87. It should have been upgraded at that time, when Sarge was made the Debian Stable release. This is what I don't understand. Did you upgrade from something that was not a pure, official Debian install at some time in the past? -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410172: version missing on libnet-server-perl dependency
Henrique de Moraes Holschuh wrote: On Thu, 08 Feb 2007, Aidas Kasparas wrote: And regarding from releases earlier than Sarge... am I the last person, who upgrades packages from testing just when he need some new feature or sees security report? I tought, if dependency was versioned, some person like me would be saved from trouble while upgrading. libnet-server-perl (0.85-3) unstable; urgency=low * debian/control: depends on libio-multiplex-perl (closes: #192921) -- Luca Filipozzi [EMAIL PROTECTED] Sat, 17 May 2003 16:00:32 -0700 Please explain to me how you had the above package installed in a Debian Sarge system. Sarge was released on 2005, and has version 0.87. It should have been upgraded at that time, when Sarge was made the Debian Stable release. This is what I don't understand. Did you upgrade from something that was not a pure, official Debian install at some time in the past? Well, that box was installed about 4 years ago (hardware was produced 2003-02). I guess it was installed from [Debian GNU/Linux 3.0 r0 _Woody_ - Official i386 Binary-1 (20020718)] (commented line in sources.list). Then packages from testing were added. And later it was upgraded on package by package basis as needed. No upgrade to some formal stable release was made (reasons it should?). -- Aidas Kasparas IT administrator GM Consult Group, UAB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410172: version missing on libnet-server-perl dependency
On Thu, 08 Feb 2007, Aidas Kasparas wrote: package by package basis as needed. No upgrade to some formal stable release was made (reasons it should?). That would do it, indeed. Yes, you have to upgrade to every stable distro in the way, think of it as a checkpoint. Debian guarantees updates only from one stable distro to the next one. There is nothing wrong with using testing and upgrading in a need-for-an-update basis (other than that you need to keep a *really* close eye for security problems), but you need to change that to a full update of everything at least once, right after a new stable is released. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
