Doh. With word wrap:
Packages that use debconf automatically get a postrm fragment for
purge that sources confmodule. This breaks if the maintainer has a
custom postrm that can write to stdout before the #DEBHELPER# line,
because the redirection of stdout to stderr does not occur until the
#DEBHEL
Package: debconf
Version: 1.5.51
Severity: normal
Packages that use debconf automatically get a postrm fragment for purge that
sources confmodule. This breaks if the maintainer has a custom postrm that can
write to stdout before the #DEBHELPER# line, because the redirection of stdout
to stderr
retitle 774175 RFS: libgaminggear/0.6.0-1 [ITP]
thanks
Uploaded 0.6.0-1 with new upstream revision.
On Thu, Jan 22, 2015 at 8:10 AM, Tristan Schmelcher
wrote:
> I've uploaded a new revision that fixes the issues Riley pointed out and more.
>
> FYI, I am pretty sure the harden
Sorry for the lack of line breaks. Here is the same text with line breaks added:
dpkg-shlibdeps supports multiple -S options, which dh_shlibdeps wraps as -L. But
dh_shlibdeps does not support multiple -L options. The last one is the only one
that has an effect. This means that a source package tha
Package: debhelper
Version: 9.20150101
Severity: normal
dpkg-shlibdeps supports multiple -S options, which dh_shlibdeps wraps as -L.
But dh_shlibdeps does not support multiple -L options. The last one is the only
one that has an effect. This means that a source package that ships private
shared
I've uploaded a new revision that fixes the issues Riley pointed out and more.
FYI, I am pretty sure the hardening-no-fortify-functions is a false
positive since the build is blhc-clean.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
I've uploaded a new revision that fixes the issues Riley pointed out and more.
FYI, I am pretty sure the hardening-no-fortify-functions is a false
positive since the build is blhc-clean.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
On Jan 1, 2015 4:37 PM, "Riley Baird" <
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch> wrote:
>
> Hi, I'm not a DD, so I can't sponsor your package, but I looked at your
> package and here are some things that I noticed:
>
> * You should add DEP-3 headers to your patches:
> http://dep.debian.
ternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/libg/libgaminggear/libgaminggear_0.5.0-1.dsc
Regards,
Tristan Schmelcher
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsub
I am working on packaging roccat-tools, starting with its dependency,
libgaminggear. I've opened bug 773402 for packaging libgaminggear. I'm
not a DD so I'm going to find a sponsor. The libgaminggear package is
pretty much done.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.o
Package: wnpp
Severity: wishlist
Owner: Tristan Schmelcher
* Package name: libgaminggear
Version : 0.5.0
Upstream Author : Stefan Achatz
* URL : https://sourceforge.net/projects/libgaminggear/
* License : GPL2
Programming Lang: C
Description
+1 to not launching kwallet by default.
FYI, the Ubuntu bug report is
https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/819473
On Fri, Sep 2, 2011 at 3:29 PM, Tristan Schmelcher
wrote:
> Package: vnc4
> Version: 4.1.1+X4.3.0-37
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: ori
Yup, upgrading fixed it. Thanks for the quick reply!
On Fri, 2007-11-09 at 21:24 +0100, Josselin Mouette wrote:
> Hi,
>
> Le vendredi 09 novembre 2007 à 01:35 -0800, Tristan Schmelcher a écrit :
> > Package: metacity
> > Version: 1:2.14.5-4
>
> > Versions of packag
Package: metacity
Version: 1:2.14.5-4
Severity: important
Within the last month or so, my desktop has started regularly hanging
when I click on window buttons such as the minimize button or close
("X") button. The cursor still moves, but thereafter both mouse clicks
and keyboard input are ignor
Negative; still happening to me on 2.6.22-2-amd64.
On Sun, 2007-14-10 at 15:35 +0200, Luca Bruno wrote:
> Hi,
> On my machine, this bug seems to be gone after a kernel upgrade.
> Now, with a 2.6.22-2-686, wodim is working fine (at least here).
> All kernel versions refers to the prepacked ones sh
I have upgraded to 0.6.5-1 and tested, and the behaviour has changed,
but for the worse.
When switching networks, NM no longer permanently shuts down the
interface (and thus there is no need for my keep-up.sh work-around).
However, it only occasionally will successfully connect to the new
network.
Occurs for me too on both 2.6.18-5-amd64 and 2.6.22-1-amd64 with same
package version. It does not occur with package version 9:1.1.2-1.
I previously opened a bug with GnomeBaker about the freeze that this
causes (see
https://sourceforge.net/tracker/?func=detail&atid=708499&aid=1781535&group_id=12
I have also experienced this problem on 2.6.18 through 2.6.22 (amd64). I
have an internal SATA drive with my Debian installation on it and an
external eSATA drive with documents and such. The eSATA drive was
incorrectly chosen as /dev/sda on approximately 75% of boots, which
resulted in the kernel
Package: xserver-xorg-core
Version: 2:1.3.0.0.dfsg-6
Severity: important
I just upgraded my Lenny system and found that the X server was broken.
It fails to start, complaining that the nvidia driver module does not
exist, which is bogus:
[EMAIL PROTECTED]:~$ ls -al /usr/lib/xorg/modules/d
x27;m not too surprised that you can't reproduce this--it has the smell of
a hardware-dependent bug. Perhaps I should strace the NM processes?
On Tue, 2007-12-06 at 23:13 +0200, Michael Biebl wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Tristan Schmelcher wrot
First of all, I should mention that I have tested version 0.6.4-8 and
the behaviour is no different.
Now, for other users that are having this problem, I have written a
simple shell script that automates my work-around. It is attached. You
can run it from a shell as follows:
sudo keep-up.sh e
I too can confirm this bug. Please incorporate the patch soon. The
offending package version is already in testing.
I can confirm this. I am running Debian unstable and I did what James
did (downloaded the compiz-gtk .deb from experimental, unpacked it into
a directory and reconstructed the DEBIAN subdirectory, removed the
"Conflicts" line from the control file, remade it with dpkg-deb, and
installed with dpkg)
Package: linux-image-2.6.18-3-xen-amd64
Version: 2.6.18-7
The packaged amd64 Xen kernel (and perhaps others) in etch does not have
the /dev/snapshot node or underlying char device, and so is unable to do
userspace suspend. (The non-Xen kernel includes it.) Observe:
(in /var/log/hibernate.log)
Sta
25 matches
Mail list logo
