johnraff
commented
9 years ago My personal opinion is only one of many, but I also like the basic idea of making the BunsenLabs identity more clear.
However is this not a fairly major step? The relationship of BunsenLabs with Debian is perhaps something that needs to be discussed among all involved, and, in particular, needs the agreement of the project leader @pvsage . ( I have just been re-reading the Debian Wiki: https://wiki.debian.org/Derivatives/Guidelines ) Is BunsenLabs to be a Debian Derivative, or simply Debian with some configurations? How are bug reports to be dealt with? How will our users expect to be treated if they raise questions on the Debian Forums? What resources and manpower can we reasonably expect to have in relation to the tasks and responsibilities we will be expected to take on? And probably other questions...
Actually, there are also some possible technical issues. I remember problems when CrunchBang set a lsb-release file and the package software-properties-gtk misbehaved. SPG is not a standard #! or BL package but it is a useful GUI for adjusting repositories and finding a fast mirror which integrates into Synaptic and which some users might want to install.
I have just done a test on a virtual BL system - installing SPG, which worked correctly. After also installing bunsen-os-release, gksu software-properties-gtk after receiving the password returns immediately, displaying no error messages. After purging bunsen-os-release, SPG works again.
To try to get round the lack of error messages I installed strace and ran these commands:
strace gksu /usr/bin/software-properties-gtk > strace_spg_without_bor 2>&1
sudo apt-get install bunsen-os-release
strace gksu /usr/bin/software-properties-gtk > strace_spg_with_bor 2>&1The files are here:
https://dl.dropboxusercontent.com/u/10808732/strace_spg_without_bor
https://dl.dropboxusercontent.com/u/10808732/strace_spg_with_bor
They are long (over 7000 lines) but if you search for mypassword you'll see the section after inputting the gksu p/w, which is quite short, especially in the case with BOR. I don't know if you'll spot the problem there. It seems to be in this section, right at the end:
nanosleep({0, 100000000}, NULL) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=19484, si_uid=0, si_status=1, si_utime=2, si_stime=0} ---
restart_syscall(<... resuming interrupted call ...>) = 0
waitpid(19484, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], WNOHANG) = 19484
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLIN|POLLOUT}])
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\34\0r\0168\0\340\3(\0\0\0\216\33\3\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 896
writev(3, [{"\1\30\n\0\257\0\340\3p\1\0\0\234\377\234\377\1\0\1\0\0\0\0\0!\0\0\0\0\n\0\0"..., 224}], 1) = 224
unlink("/tmp/libgksu-Wy5AJs/.Xauthority") = 0
rmdir("/tmp/libgksu-Wy5AJs") = 0
exit_group(1) = ?
+++ exited with 1 +++If there are any other tests I can try on this system please let me know.
So if there is a resolution for this problem then all is fine on the tech front - otherwise we are faced with a tradeoff between enhancing users' perception of BunsenLabs along with easy access to the correct support and bug report links, vs possible breakage of some other packages.
ghost
@johnraff