Bug#988462: Thank you
Ah, thank you, that's very helpful - I will try nspawn or docker. I look forward to 1.6 in Debian 12! Chris
Bug#988462: Apologies
Sorry, the second copy of my previous email was actually sent first, from a defunct email account, I had accidentally set the From field wrong. Apologies for the duplication.
Bug#988462: A little more info please?
Hi, Please could you expand on this slightly. I just upgraded my server from buster to bullseye, and was very unpleasantly surprised to discover that trac has been removed. I've been using it for 11 years, I run my whole life with it. It's never caused me any problems at all - please could you explain why it is not suitable for inclusion in bullseye? What is it that I am not seeing or experiencing in my daily use of it? Also, please could you recommend an alternative ticket management package that is included in bullseye. Preferably one that will import my trac db so I don't have to re-enter 11 years of history. Thanks Chris
Bug#988462: A little more info please?
Hi, Please could you expand on this slightly. I just upgraded my server from buster to bullseye, and was very unpleasantly surprised to discover that trac has been removed. I've been using it for 11 years, I run my whole life with it. It's never caused me any problems at all - please could you explain why it is not suitable for inclusion in bullseye? What is it that I am not seeing or experiencing in my daily use of it? Also, please could you recommend an alternative ticket management package that is included in bullseye. Preferably one that will import my trac db so I don't have to re-enter 11 years of history. Thanks Chris
Bug#793668: there would be an attempt to have an updated angband build with SDL2
Thank you! I've been thinking it's high time I got back to this and fixed a few bugs. I'll take a look at this when the more pressing ones are closed and 4.x is in testing. CC On Sat, 22 Sep 2018 at 15:09, shirish शिरीष wrote: > Dear Andreas, > > There are attempts being made at angband forums to have an updated > SDL2 frontend . > > http://angband.oook.cz/forum/showthread.php?t=9076 > > your expertise may prove to be invaluable as you know about Debian > more than me. > > Just giving you a heads-up in case you become interested. > > > -- > Regards, > Shirish Agarwal शिरीष अग्रवाल > My quotes in this email licensed under CC 3.0 > http://creativecommons.org/licenses/by-nc/3.0/ > http://flossexperiences.wordpress.com > EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 >
Bug#837394: Better fix for the angband PIE FTBFS
Thank you. The plan is to update to new upstream 4.x but this should still work. On 10 Nov 2016 9:09 a.m., "Adrian Bunk" wrote: > A fix for the angband PIE FTBFS that does not disable PIE is attached. > > cu > Adrian > > -- > >"Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. >"Only a promise," Lao Er said. >Pearl S. Buck - Dragon Seed > >
Bug#775065: dpkg --configure -a results in "Hangup" after first package
On 11/01/2015 20:02, Michael Biebl wrote: Am 11.01.2015 um 20:54 schrieb Chris Carr: I still cannot start gdm3: chrisc@tony:~$ sudo invoke-rc.d gdm3 start [] Starting GNOME Display Manager: gdm3[ 1094.663256] systemd-logind[9907]: Failed to enable subscription: Launch helper exited with unknown return code 1 [ 1094.669994] systemd-logind[9907]: Failed to fully start up daemon: Input/output error Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 failed! That somehow sounds like something with your dbus installation is broken. What is the output of $ ls -al /usr/lib/dbus-1.0/dbus-daemon-launch-helper Attached as dbus.txt invoke-rc.d: initscript gdm3, action "start" failed. chrisc@tony:~$ There seem to be two problems there: one is gdm3 not starting, and the other is logind complaining about not being fully started. Is the dbus package installed? What's the output of "systemctl status dbus.socket dbus.service"? Failed to get D-Bus connection: Unknown error -1 You might consider attaching the full output of the systemd state via "systemd-analyze dump" Failed issue method call: Launch helper exited with unknown return code 1 I will try booting using systemd tomorrow and address your other points. Thank you again for your time, CC -rwsr-xr-- 1 root messagebus 358576 Jan 5 15:53 /usr/lib/dbus-1.0/dbus-daemon-launch-helper*
Bug#775065: dpkg --configure -a results in "Hangup" after first package
On 11/01/2015 19:25, Michael Biebl wrote: Is your system fully booted or did systemd drop you into emergency shell? How are you logged into your system? The default boot drops me into an emergency shell. It was not fully booted. Assuming, the sysvinit is still installed (which should be the case on upgrades), please select the sysvinit option from the grub extended menu. If it's not available, boot with init=/lib/sysvinit/init Does that change anything? Yes! Thank you, thank you. Selecting the (sysvinit) option from the grub extended menu results in a full boot: gdm3 doesn't start but I do get a login prompt. After logging in, sudo dpkg --configure -a actually worked. This meant that I could complete a sudo apt-get dist-upgrade. All packages are now fully configured except gkrellmd (which I removed to ensure everything is clean). I still cannot start gdm3: chrisc@tony:~$ sudo invoke-rc.d gdm3 start [] Starting GNOME Display Manager: gdm3[ 1094.663256] systemd-logind[9907]: Failed to enable subscription: Launch helper exited with unknown return code 1 [ 1094.669994] systemd-logind[9907]: Failed to fully start up daemon: Input/output error Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 failed! invoke-rc.d: initscript gdm3, action "start" failed. chrisc@tony:~$ There seem to be two problems there: one is gdm3 not starting, and the other is logind complaining about not being fully started. So, now that I can boot using sysvinit, what tests should I do to try and debug what is going on with the systemd boot? I can now produce logfiles, run reportbug etc. etc. Thanks to all for helping me recover my system, CC -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775065: dpkg --configure -a results in "Hangup" after first package
On 11/01/2015 17:11, Guillem Jover wrote: Control: reassign -1 systemd Control: severity -1 serious Hi! On Sun, 2015-01-11 at 09:03:34 +, Chris Carr wrote: On 11/01/2015 05:13, Guillem Jover wrote: Please run «dpkg -D7 --configure -a 2>&1 | tee dpkg.log», and attach the output. We can check from there It is attached, but it terminates before the output on the screen terminated. The last output on the screen was D01: process queue pkg libsane:i386 queue.len 56 progress 10, try 1 D40: checking dependencies of libsane:i386 (- ) D000400: checking group [... a few more D000400: lines ...] D000400: checking possibility -> adduHangup Ok then this looks like someone is either forcibly hanging up the terminal or sending a SIGHUP to dpkg? Which indicates that whoever is managing it is messing this up, my assumption is either systemd or plymouth. I've reassigned to the former and also CCed the latter, so they can investigate further, and reassign if necessary. [snip] On mounting, the root filesystem mounts ok (/dev/dm-2) and contains all the linux directories including /usr, /home, /usr/local etc. etc. The filesystems which fail to mount are all Windows ones, which are obviously irrelevant at this stage. Ok. Maybe as a wild guess, try booting w/o the splash kernel option if you've got it enabled (see bug #602331)? If that fixes the issue then it would need to be reassigned to plymouth. No, I can confirm that adding the "nosplash" parameter to the grub kernel line does not fix the problem. dpkg still receives the Hangup as before. Very grateful for any further advice from systemd or plymouth folks. The system is not fixable until I can run dpkg successfully and configure/install/remove packages. Thanks, Chris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#647437: angband-data fails to install, trying to overwrite files in existing version of angband
On Wed, 2011-11-02 at 10:55 -0700, Josh Triplett wrote: > Package: angband-data > Version: 1:3.3.2-1 > Severity: serious > > Unpacking angband-data (from .../angband-data_1%3a3.3.2-1_all.deb) ... > dpkg: error processing > /var/cache/apt/archives/angband-data_1%3a3.3.2-1_all.deb (--unpack): > trying to overwrite '/usr/share/angband/help/command.txt', which is also in > package angband 1:3.2.0-1 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > > > angband-data needs to conflict with and replace older versions of > angband. > > - Josh Triplett Thank you. I don't understand how piuparts said "all tests passed" and let this through, but I assume this is an edge case of a new package conflicting with an existing package. We live and learn. I'm building 3.3.2-2 now, and if my mentor forgives this error it should be uploaded shortly ;-) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#568001: Any progress on this?
This bug is still showing as a critical blocker when I try to apt-get upgrade my Sid box. It doesn't seem like much is happening - if it's safe for most users, can it be downgraded in severity? If it's not safe for most users, when can we expect a fixed version? Thanks, CC -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#557425: Same problem as #518835
Hi folks, Just wanted to chime in and say I reported this same bug several months ago as #518835, and was brushed off with "run grub-install to fix the problem". Not particularly helpful once the system was unbootable. I have subsequently had three separate machines rendered unbootable due to poor handling of GRUB upgrades to GRUB2. Let us hope these bugs are fixed before Squeeze is released to the world as stable, or a lot of servers are going to stop booting. CC -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
