Bug#479502: libcommandline-ruby1.8 and open4.rb
On Thu, May 08, 2008 at 04:52:13PM +0200, Daniel Leidert wrote: > Hi, > > Esteban Manchado Velázquez wrote: > > > I don't understand. The new libcommandline-ruby1.8 *doesn't* include > > open4.rb anymore, it *depends* on libopen4-ruby now: > > > > http://packages.debian.org/sid/all/libcommandline-ruby1.8/filelist > > http://packages.debian.org/sid/libcommandline-ruby1.8 > > That's one side of the problem, that you solved. > > > If you just upgrade everything, you should get the new > > libcommandline-ruby1.8, which doesn't include open4.rb, and everything > > should work, right? > > > > Do you have the new libcommandline-ruby1.8 installed? > > No I did not update it first, because it was hold back and I manually > installed > libopen4-ruby1.8 first (to examine, which packages are hold back for Perl 5.10 > transition). So I did run into the problem, because libopen4-ruby1.8 missed to > declare the open4.rb replacement accordingly to section 7.5(.1) of the Debian > policy. > > Package: libopen4-ruby1.8 > [..] > Replaces: libcommandline-ruby1.8 (<< 0.7.10-10) > > should solve this finally. > Is a replaces really the right relationship? In reality, libopen4-ruby does not completely supersed libcommandline-ruby. Perhaps a conflicts would be more appropriate? Conflicts: libcommandline-ruby1.8 (<< 0.7.10-10) Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Bug#479502: libcommandline-ruby1.8 and open4.rb
Hi, Esteban Manchado Velázquez wrote: > I don't understand. The new libcommandline-ruby1.8 *doesn't* include > open4.rb anymore, it *depends* on libopen4-ruby now: > > http://packages.debian.org/sid/all/libcommandline-ruby1.8/filelist > http://packages.debian.org/sid/libcommandline-ruby1.8 That's one side of the problem, that you solved. > If you just upgrade everything, you should get the new > libcommandline-ruby1.8, which doesn't include open4.rb, and everything > should work, right? > > Do you have the new libcommandline-ruby1.8 installed? No I did not update it first, because it was hold back and I manually installed libopen4-ruby1.8 first (to examine, which packages are hold back for Perl 5.10 transition). So I did run into the problem, because libopen4-ruby1.8 missed to declare the open4.rb replacement accordingly to section 7.5(.1) of the Debian policy. Package: libopen4-ruby1.8 [..] Replaces: libcommandline-ruby1.8 (<< 0.7.10-10) should solve this finally. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479502: libcommandline-ruby1.8 and open4.rb
Hi Daniel, I don't understand. The new libcommandline-ruby1.8 *doesn't* include open4.rb anymore, it *depends* on libopen4-ruby now: http://packages.debian.org/sid/all/libcommandline-ruby1.8/filelist http://packages.debian.org/sid/libcommandline-ruby1.8 If you just upgrade everything, you should get the new libcommandline-ruby1.8, which doesn't include open4.rb, and everything should work, right? Do you have the new libcommandline-ruby1.8 installed? -- Esteban Manchado Velázquez <[EMAIL PROTECTED]> EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es Help spread it through the Net in signatures, webpages, whatever! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
