Bug#732861: Openbox should not depend on GNOME or KDE.
Package: src:openbox Version: 3.5.2-5 Severity: serious The Openbox package now has recommended GNOME and KDE packages. This behavior violates Debian Policy 7.2: Recommends This declares a strong, but not absolute, dependency. The Recommends field should list packages that would be found together with this one in all but unusual installations. This is opposite in case of Openbox - only unusual installations will have either GNOME or KDE installed together with Openbox. This issue therefore has severity Serious and should be fixed ASAP. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722112: lxappearance-obconf: build problems
Hello! Mateusz Ĺukasik has written on Wednesday, 16 October, at 10:57: I made NMU patch to fix this bug, because I don't have now permit to upload in debian-lxde git repository. Well, at least you could tell me in IRC about your changes, make commit patches (as atomic as possible) and I would upload them, I'm there most of the time, just AFK sometimes. Your attached patch conflicts with the code in git repository so cannot be applied, and it also adds too many changes at once. And moreover, we highly avoid including any patches for LXDE packages but make required fixes in upstream instead. So there will be next lxappearance-obconf release shortly and as soon it is uploaded there will be no need in any of your changes except for one in regard of lxappearance-obconf-dbg. I'm sorry. Best regards, Andriy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722112: lxappearance-obconf: build problems
Hello! Bob Bib has written on Monday, 14 October, at 5:38: Well, we have here a new transition-related build failure, an this time a more real one: https://buildd.debian.org/status/package.php?p=lxappearance-obconf https://buildd.debian.org/status/fetch.php?pkg=lxappearance-obconfarch=amd64ver=0.2.0-4%2Bb1stamp=1381154559 It can't build against the fresh openbox-dev 3.5.2-3 due to some changes in '/usr/include/openbox/3.5/obrender/theme.h'. Fortunately, it looks like fixed upstream: http://sourceforge.net/tracker/?func=detailaid=3614951group_id=180858atid=894869 http://lxde.git.sourceforge.net/git/gitweb.cgi?p=lxde/lxappearance-obconf;a=commit;h=c8f0cd4270c140ad2b458b45df42ed44f08241ff I would rather avoid openbox 3.5.2, it has the behavior which many users would consider buggy - it places new windows always in the corner of screen, and old behavior (center of screen) isn't possible anymore. Let stay with 3.5.0 until they implement old behavior again (I hope it will be implemented in the next openbox release, they are working on it already). Best regards, Andriy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722112: lxappearance-obconf: build problems
Bob Bib has written on Monday, 14 October, at 21:35: openbox/3.5.2-3 is currently in unstable, not in NEW queue or experimental... By the way, I've unpacked the source package, and there's some patch there, 'fix_center_window.patch' in 'debian/patches' (I haven't tested it though). I haven't tested it too. I hope it contains all the fix, it needs testing yet I think. I've completely forgotten the fix already came in the debian package. I'm sorry. About mentioned build problem with new openbox: I'm adding gi...@ubuntu.com to recipients, and would ask to release new version of lxappearance-obconf (0.2.1 or 0.3.0 by your choice) so we can release fixed one into debian too. Thank you very much. Best regards! Andriy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722111: libmenu-cache1-dev should be removed from both src:lxappearance and src:lxappearance-obconf
The libmenu-cache1-dev should be removed from both lxappearance and lxappearance-obconf dependencies, sources of both those packages don't use libmenu-cache at all. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713328: The issue is fixed.
We believe this issue is completely fixed in 1.1.1 version of libfm and pcmanfm. Those versions will be available shortly in unstable repository of Debian. If you cannot afford using unstable repository but want to use stable instead then yet still are two options for you: 1. Download sources from Debian archive site, then build the packages yourself, then upgrade your packages. 2. Wait until upgrades come into wheezy-backports repository and then upgrade your packages. Thank you very much for your patience. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593607: pcmanfm wrongly deleted some files in a failed move operation
Hello! John Paul Adrian Glaubitz has written on Saturday, 5 January, at 21:10: I consider his proposal as the best solution for wheezy. May I NMU to unstable? Since no one has replied to your suggestion yet, I would suggest that you make an NMU and upload it into DELAYED/10 which will give the maintainers enough time for review. This bug is a serious issue and an RC bug and should therefore not be delayed too long. And remember that is not a solution but a workaround which breaks one of functions of pcmanfm and that breakage is another bug. Real fix will be upgrade to the 1.1.1 version which will be possible only after wheezy release (via backports). With best wishes. Andriy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593607: bug #593607: pcmanfm wrongly deleted some files in a failed move operation
Why not to reopen this bug if it hasn't been fixed yet? ;) In fact, it's fixed in upstream. The reporter confirmed it is fixed. And all commits for the fix are included in latest stable release of libfm and pcmanfm (1.1.0). If reopening this bug gives a possibility for 1.1.0 to come into Wheezy then why not? But I hardly doubt it is possible to gather all fixes for the subject and apply them on ancient libfm 0.1.17. If you ask me I would never try that, I don't know which side effects will that cause, because changing major number of upstream version sure was for reason, and the diff between 0.1.17 and 1.1.0 is near 4MB while unpacked libfm tarball takes near 7MB. May be it is still good for everyone to postpone fix to time after Wheezy release. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593607: (no subject)
As main developer of pcmanfm in meantime I can say this bug isn't fixed in any of 0.9.x series and will be fixed in next 1.0.2 release which is scheduled to late October. Last release of 1.0.x series will be 1.0.3 I think and that one should be the most featureful and bugfree version of 1.0.x series. 0.9.x series are unstable (there was few tens bugs in the upstream bug tracker about crashes, freezes, and memory leaks addressed 0.9.x series that are fixed in 1.0.x series) but 1.0.x are stable. It's too hard to get any of stable version into Wheezy at this stage, sorry. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593607: bug #593607: pcmanfm wrongly deleted some files in a failed move operation
forwarded 593607 https://sourceforge.net/tracker/?func=detailaid=3565792group_id=156956atid=801864 thank you This bug was a bit hard to reproduce as it didn't happen when moving just a bunch of files. It also happened when no space left on destination device. Fixed in upstream by commit f8441418b8c5087b266b60ed0bf02ee1645711f1 few moments ago. Thank you. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
