** Description changed:

+ The following issue is now fixed in Maverick but affects Lucid.
+ 
+ Backporting the entirety of gdebi 0.6.1 from Maverick won't do, but the
+ fix is a fairly simple one-line (one character!) change in lp:gdebi,
+ revision 314. I picked that revision specifically and pushed it to the
+ linked bzr branch.
+ 
+ This bug creates a crash that makes some packages impossible to install
+ for our users. For example, in directing a user to install the proposed
+ libusb package to fix a printer problem, I found that I could not give
+ him easy directions with gdebi because it crashed upon opening the
+ package. The issue can definitely harm the experience for our end users,
+ and it will be especially troublesome going forwards as developers
+ running newer systems will not recognize that packages they are sending
+ to Lucid users will create this crash.
+ 
+ There is, unfortunately, some regression potential because this is a string 
change. There are 40 translations based on (and, themselves, containing) the 
offending string:
+ https://translations.edge.launchpad.net/ubuntu/lucid/+source/gdebi/+pots/gdebi
+ 
+ Thankfully, we can change those really easily (a simple script would do
+ it, though even doing it by brute force wouldn't take _too_ long). The
+ only thing is I expect this would need some work to be timed right :)
+ 
+ Original bug report follows…
+ -----
+ 
  gdebi crashes when I try to install the package: liferea-
  data_1.7.4-2~llfsyncfix1+sikon8_all.deb from
  https://edge.launchpad.net/~sikon/+archive/liferea-libindicate/+packages
  
  This happens on a fully up-to-date Lucid x64 installation.  Even if
  there's something wrong with the package, it would be nice if gdebi
  would give some useful output instead of crashing.  Here's the trace:
  
- 
  mich...@michael-desktop:~/Downloads$ gdebi 
./liferea-data_1.7.4-2~llfsyncfix1+sikon8_all.deb
  Reading package lists... Done
- Building dependency tree        
+ Building dependency tree
  Reading state information... Done
- Building data structures... Done 
-   Traceback (most recent call last):
-   File "/usr/bin/gdebi", line 83, in <module>
-     if not debi.open(args[0]):
-   File "/usr/lib/python2.6/dist-packages/GDebi/GDebiCli.py", line 86, in open
-     if not self._deb.checkDeb():
-   File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 368, in 
checkDeb
-     if not self.checkBreaksExistingPackages():
-   File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 283, in 
checkBreaksExistingPackages
-     'depversion' : dep.version}
+ Building data structures... Done
+   Traceback (most recent call last):
+   File "/usr/bin/gdebi", line 83, in <module>
+     if not debi.open(args[0]):
+   File "/usr/lib/python2.6/dist-packages/GDebi/GDebiCli.py", line 86, in open
+     if not self._deb.checkDeb():
+   File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 368, in 
checkDeb
+     if not self.checkBreaksExistingPackages():
+   File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 283, in 
checkBreaksExistingPackages
+     'depversion' : dep.version}
  TypeError: not enough arguments for format string
  
- 
  Let me know if there's any more information that I can provide.

** Description changed:

  The following issue is now fixed in Maverick but affects Lucid.
  
  Backporting the entirety of gdebi 0.6.1 from Maverick won't do, but the
  fix is a fairly simple one-line (one character!) change in lp:gdebi,
- revision 314. I picked that revision specifically and pushed it to the
- linked bzr branch.
+ revision 314. I picked that revision specifically and pushed it to
+ lp:~dylanmccall/ubuntu/lucid/gdebi/bug-591470
  
  This bug creates a crash that makes some packages impossible to install
  for our users. For example, in directing a user to install the proposed
  libusb package to fix a printer problem, I found that I could not give
  him easy directions with gdebi because it crashed upon opening the
  package. The issue can definitely harm the experience for our end users,
  and it will be especially troublesome going forwards as developers
  running newer systems will not recognize that packages they are sending
  to Lucid users will create this crash.
  
  There is, unfortunately, some regression potential because this is a string 
change. There are 40 translations based on (and, themselves, containing) the 
offending string:
  https://translations.edge.launchpad.net/ubuntu/lucid/+source/gdebi/+pots/gdebi
  
  Thankfully, we can change those really easily (a simple script would do
  it, though even doing it by brute force wouldn't take _too_ long). The
  only thing is I expect this would need some work to be timed right :)
  
  Original bug report follows…
  -----
  
  gdebi crashes when I try to install the package: liferea-
  data_1.7.4-2~llfsyncfix1+sikon8_all.deb from
  https://edge.launchpad.net/~sikon/+archive/liferea-libindicate/+packages
  
  This happens on a fully up-to-date Lucid x64 installation.  Even if
  there's something wrong with the package, it would be nice if gdebi
  would give some useful output instead of crashing.  Here's the trace:
  
  mich...@michael-desktop:~/Downloads$ gdebi 
./liferea-data_1.7.4-2~llfsyncfix1+sikon8_all.deb
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Building data structures... Done
    Traceback (most recent call last):
    File "/usr/bin/gdebi", line 83, in <module>
      if not debi.open(args[0]):
    File "/usr/lib/python2.6/dist-packages/GDebi/GDebiCli.py", line 86, in open
      if not self._deb.checkDeb():
    File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 368, in 
checkDeb
      if not self.checkBreaksExistingPackages():
    File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 283, in 
checkBreaksExistingPackages
      'depversion' : dep.version}
  TypeError: not enough arguments for format string
  
  Let me know if there's any more information that I can provide.

** Description changed:

  The following issue is now fixed in Maverick but affects Lucid.
  
  Backporting the entirety of gdebi 0.6.1 from Maverick won't do, but the
  fix is a fairly simple one-line (one character!) change in lp:gdebi,
  revision 314. I picked that revision specifically and pushed it to
  lp:~dylanmccall/ubuntu/lucid/gdebi/bug-591470
  
- This bug creates a crash that makes some packages impossible to install
- for our users. For example, in directing a user to install the proposed
- libusb package to fix a printer problem, I found that I could not give
- him easy directions with gdebi because it crashed upon opening the
- package. The issue can definitely harm the experience for our end users,
- and it will be especially troublesome going forwards as developers
- running newer systems will not recognize that packages they are sending
- to Lucid users will create this crash.
+ This bug creates a crash that makes some packages impossible for our
+ users to install without resorting to a terminal. For example, in
+ directing a user to install the proposed libusb package to fix a printer
+ problem, I found that I could not give him easy directions with gdebi
+ because it crashed upon opening the package. The issue can definitely
+ harm the experience for our end users, and it will be especially
+ troublesome going forwards as developers running newer systems will not
+ recognize that packages they are sending to Lucid users will create this
+ crash.
  
  There is, unfortunately, some regression potential because this is a string 
change. There are 40 translations based on (and, themselves, containing) the 
offending string:
  https://translations.edge.launchpad.net/ubuntu/lucid/+source/gdebi/+pots/gdebi
  
  Thankfully, we can change those really easily (a simple script would do
  it, though even doing it by brute force wouldn't take _too_ long). The
  only thing is I expect this would need some work to be timed right :)
  
  Original bug report follows…
  -----
  
  gdebi crashes when I try to install the package: liferea-
  data_1.7.4-2~llfsyncfix1+sikon8_all.deb from
  https://edge.launchpad.net/~sikon/+archive/liferea-libindicate/+packages
  
  This happens on a fully up-to-date Lucid x64 installation.  Even if
  there's something wrong with the package, it would be nice if gdebi
  would give some useful output instead of crashing.  Here's the trace:
  
  mich...@michael-desktop:~/Downloads$ gdebi 
./liferea-data_1.7.4-2~llfsyncfix1+sikon8_all.deb
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Building data structures... Done
    Traceback (most recent call last):
    File "/usr/bin/gdebi", line 83, in <module>
      if not debi.open(args[0]):
    File "/usr/lib/python2.6/dist-packages/GDebi/GDebiCli.py", line 86, in open
      if not self._deb.checkDeb():
    File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 368, in 
checkDeb
      if not self.checkBreaksExistingPackages():
    File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 283, in 
checkBreaksExistingPackages
      'depversion' : dep.version}
  TypeError: not enough arguments for format string
  
  Let me know if there's any more information that I can provide.

-- 
Gdebi crashes while trying to install a deb package, TypeError: not enough 
arguments for format string
https://bugs.launchpad.net/bugs/591470
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to