Just a thought, but does the file conflict actually produce the exact same
files? I.e. can we just disablethese files from either mypaint-data or
libmypaint-common (probably from mypaint-data as this lookslike the older
package, and then have it depend on the other to ensure that those files ex
Package: lxpanel
Version: 0.9.2-1
Severity: grave
Dear Maintainer,
Listing this as grave because this prevents users from locking the screen, a
security issue.
Not 100% sure where the problem lies, so I go to the package where the problem
starts...
When clicking on the ScreenLock button in LxP
Hi Vincent
I just tried the following on 38.2.1 and I can extend upon this
further... the steps to accomplish
1. Open a webpage from my local virtual host
2. Disable Apache without reloading page
3. Save As Complete HTML
I could then open the the page I saved, even though it no longer existed
Any news on this bug? It looks like quite a simple fix, I would do it
myself but I don't know how to use the debian git system (I have only
ever used github before).
Best,
Jack
Package: ruby-compass
Version: 0.12.2~dfsg-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After a recent upgrade, I get the following error message while trying to run
compass compile --sass-dir --css-dir
--output-style compressed
/usr/lib/ruby/2.0.0/rubygems/core_
5 matches
Mail list logo