Bug#973940: ezquake: Package is severely out of date (5+ years)

2020-11-07 Thread Dustin Glidden
Package: ezquake
Severity: important

Dear Maintainer,

The ezquake package is severely out of date, the current stable version
is 3.2 and testing is 3.6.  Please update this package as many users
understandably attempt to use this package and are then immediately told
to compile a much newer version.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ezquake depends on:
ii  libc62.31-4
ii  libcurl3-gnutls  7.72.0-1
ii  libexpat12.2.10-1
ii  libgl1   1.3.2-1
ii  libjansson4  2.13.1-1
ii  libpcre3 2:8.39-13
ii  libpng16-16  1.6.37-3
ii  libsdl2-2.0-02.0.12+dfsg1-4
ii  zlib1g   1:1.2.11.dfsg-2

ezquake recommends no packages.

Versions of packages ezquake suggests:
ii  game-data-packager  65



Bug#878929: libfreetype6: font rendering broken in electron applications

2017-10-17 Thread dustin glidden
Package: libfreetype6
Version: 2.8.1-0.1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Font rendering in electron applications is now broken (eg basic electron sample
applications/discord).  Building manually this problem does not exist:

apt-get source libfreetype6
cd freetype-2.8.1/
tar xfj freetype-2.8.1.tar.bz2
cd freetype-2.8.1
./configure --without-bzip2 --without-harfbuzz
make -j4
LD_PRELOAD=./objs/.libs/libfreetype.so ~/discordapp/Discord #or other electron
app



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)



Bug#715510: libvirt-bin: libvirtd locks up whenever touching storage storage pool when related to systems's harddrive.

2013-07-18 Thread Dustin Glidden
Upgraded to libvirt-bin to 1.1.0-3, problem still exists.

-- 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#715510: libvirt-bin: libvirtd locks up whenever touching storage storage pool when related to systems's harddrive.

2013-07-09 Thread Dustin Glidden
Package: libvirt-bin
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable

With libvirt-bin version 1.1.0-1, libvirtd locks up whenever touching storage 
storage pool when related to systems's harddrive.  virt-clone causes libvirtd 
to hang, attempting to clone a vm via virt-manager causes a hang, creating a 
new vm via virt-manager causes a hang (once you reach the step at which 
libvirt-bin would be creating the image).  Reverting back to 1.0.6 fixes the 
problem.  As of now all disk images in my storage pool used as hdd images are 
raw.  Attempted to upgrade kernel version from 3.9-1 to no avail.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-rc7-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages libvirt-bin depends on:
ii  adduser 3.113+nmu3
ii  gettext-base0.18.2.1-1
ii  libaudit0   1:1.7.18-1.1
ii  libavahi-client30.6.31-2
ii  libavahi-common30.6.31-2
ii  libblkid1   2.20.1-5.5
ii  libc6   2.17-7
ii  libcap-ng0  0.7.3-1+b1
ii  libdbus-1-3 1.6.12-1
ii  libdevmapper1.02.1  2:1.02.77-3
ii  libgcrypt11 1.5.2-3
ii  libgnutls26 2.12.23-5
pn  libnetcf1   none
ii  libnl-3-200 3.2.21-1
ii  libnl-route-3-200   3.2.21-1
ii  libnuma12.0.8-3
ii  libparted0debian1   2.3-13
ii  libpcap0.8  1.4.0-2
ii  libpciaccess0   0.13.1-2
ii  libreadline66.2+dfsg-0.1
ii  libsasl2-2  2.1.25.dfsg1-13
ii  libudev0175-7.2
ii  libvirt01.1.0-1
ii  libxenstore3.0  4.2.1-2
ii  libxml2 2.9.1+dfsg1-2
ii  libyajl22.0.4-4
ii  logrotate   3.8.5-1

Versions of packages libvirt-bin recommends:
ii  bridge-utils1.5-6
ii  dmidecode   2.12-1
ii  dnsmasq-base2.66-3
ii  ebtables2.0.10.4-3
ii  gawk1:4.0.1+dfsg-2.1
ii  iproute 1:3.9.0-5
ii  iptables1.4.18-1
ii  libxml2-utils   2.9.1+dfsg1-2
ii  netcat-openbsd  1.105-7
ii  parted  2.3-13
ii  pm-utils1.4.1-11
ii  qemu-system-x86 [qemu-kvm]  1.5.0+dfsg-4

Versions of packages libvirt-bin suggests:
pn  auditd   none
ii  policykit-1  0.105-3
pn  radvdnone
pn  systemtapnone

-- Configuration Files:
/etc/default/libvirt-guests changed [not included]
/etc/libvirt/libvirt.conf changed [not included]
/etc/libvirt/qemu-lockd.conf changed [not included]
/etc/libvirt/qemu-sanlock.conf changed [not included]

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#447518: mirror listing update for debian.crosslink.net

2007-10-25 Thread Dustin Glidden
Everything seems to be working fine (though it doesn't look like you're
pushing updates yet) except the mirror.  Is there another primary push I
could use that might be a bit faster?

Dustin

Josip Rodin wrote:
 On Sun, Oct 21, 2007 at 06:51:49PM -0400, Dustin Glidden wrote:
   
 Is the username 'debian' good for you, or do you have a standard one I
 should use instead?
 

 That's fine, whatever works for you.

 The key is attached. You should add it to your mirror account's
 ~/.ssh/authorized_keys, but adjust the 'command' setting to point to
 your existing script that mirrors Debian.

 We need to know the [EMAIL PROTECTED] to trigger, and whether there's
 also an IP-based access restriction in place for it.

   




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#447518: mirror listing update for debian.crosslink.net

2007-10-23 Thread Dustin Glidden
The box is up and running at thay.crosslink.net.  I created the user
debianpush for the updates.  Please let me know if there is anything
else I need to do.

Dustin

Josip Rodin wrote:
 On Sun, Oct 21, 2007 at 06:51:49PM -0400, Dustin Glidden wrote:
   
 Is the username 'debian' good for you, or do you have a standard one I
 should use instead?
 

 That's fine, whatever works for you.

 The key is attached. You should add it to your mirror account's
 ~/.ssh/authorized_keys, but adjust the 'command' setting to point to
 your existing script that mirrors Debian.

 We need to know the [EMAIL PROTECTED] to trigger, and whether there's
 also an IP-based access restriction in place for it.

   




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#447518: mirror listing update for debian.crosslink.net

2007-10-21 Thread Dustin Glidden
Package: mirrors
Severity: minor

Submission-Type: update
Site: debian.crosslink.net
Aliases: thay.crosslink.net
Type: leaf
Archive-architecture: ALL 
Archive-ftp: /debian/
Archive-http: /debian/
Archive-rsync: debian/
IPv6: no
Mirrors-from: 204.152.191.7
Maintainer: Dustin Glidden [EMAIL PROTECTED]
Country: US United States
Location: McLean Virginia
Sponsor: CrossLink.net http://www.crosslink.net



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#447518: mirror listing update for debian.crosslink.net

2007-10-21 Thread Dustin Glidden
Sounds good to me, I guess all I need is the key from the mirror then. 

Dustin

Josip Rodin wrote:
 On Sun, Oct 21, 2007 at 06:07:29PM -0400, Dustin Glidden wrote:
   
 Yeah I'm still working on it, didn't think I'd get a response this
 fast.  Everything seems to be working but I haven't put it on the
 production side of our network yet.
 

 We'll list it when we can reach it :)

   
 Not a problem, and yes I would like to receive push updates if you could
 let me know how I would go about doing that.
 

 For a general introduction by what we mean, please see
 http://www.debian.org/mirror/push_mirroring

 In short, we can make an ssh connection to a specified [EMAIL PROTECTED] of
 yours whenever the mirrors.kernel.org site finishes its update, and use a
 special SSH key for that. On your end, you configure SSH to run the Debian
 mirror update command when it receives that connection. After that, you no
 longer need a cron job.

 (Please keep the Cc: for all non-confidential messages.)

   




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#447518: mirror listing update for debian.crosslink.net

2007-10-21 Thread Dustin Glidden
Is the username 'debian' good for you, or do you have a standard one I
should use instead?

Dustin

Josip Rodin wrote:
 On Sun, Oct 21, 2007 at 06:07:29PM -0400, Dustin Glidden wrote:
   
 Yeah I'm still working on it, didn't think I'd get a response this
 fast.  Everything seems to be working but I haven't put it on the
 production side of our network yet.
 

 We'll list it when we can reach it :)

   
 Not a problem, and yes I would like to receive push updates if you could
 let me know how I would go about doing that.
 

 For a general introduction by what we mean, please see
 http://www.debian.org/mirror/push_mirroring

 In short, we can make an ssh connection to a specified [EMAIL PROTECTED] of
 yours whenever the mirrors.kernel.org site finishes its update, and use a
 special SSH key for that. On your end, you configure SSH to run the Debian
 mirror update command when it receives that connection. After that, you no
 longer need a cron job.

 (Please keep the Cc: for all non-confidential messages.)

   




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]