10 @@
+xbindkeys (1.8.6-2) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild towards guile-2.2 (Closes #885239).
+
+ -- Martin Samuelsson Wed, 06 Nov 2019 21:14:49 +0100
+
xbindkeys (1.8.6-1) unstable; urgency=medium
* New upstream version
diff -ur xbindkeys-1.8.6/debian/contr
Martin Samuelsson skrev:
Has anything happened on this topic, which isn't included in the bug
report?
For what it's worth...
I now noticed that the linux-image packages now contains ipw2100.ko,
which works just as well as compiling custom kernels with third party
modules. Donno i
Daniel Baumann skrev:
Steinar H. Gunderson wrote:
This was about a month ago -- any progress?
[...]
Well, the "problem" is, that the kernel-team will prepare a modules
package to conglomerate all oot-modules.
>[...]
Google came up with the following thread:
http://lists.debian.org/de
Package: sylpheed-claws-gtk2
Version: 1.9.100-2
Severity: critical
When composing a message in s-c-gtk2, it adds the full contents of the
last message read when sending it.
Steps to reproduce:
1. Start sylpheed-claws-gtk2
2. Read a message
3. Compose a message
Now, the message at the receiving
fabian linzberger @ 2006-01-12 (Thursday), 14:40 (+0100)
> usually ratpoison is launched via "exec ratpoison" in ~/.xsession, however
> after
> the recent upgrade to 1.4.0-beta4-4 it immediately terminates.
> ~/.xsession-errors
> does not seem to contain useful information.
>
> downgrading to 1.
reopen 347023
thank you,
Jonathan Walther @ 2006-01-09 (Monday), 10:32 (-0800)
>* Adding Mike O'Connor's suggested Build-Depends.
> Closes: #347023
Building on the autobuilders failed again. Adding libxtst-dev to the
build depends would solve this last issue. Sorry about blaming configur
reopen 347023
thank you,
I would say the bug fix didn't get all the way, based on that building
now failes for all architectures on the autobuilders.
http://buildd.debian.org/build.php?pkg=ratpoison
"
...
checking for X... no
configure: error: *** Can't find X11 headers and libs
make: *** [build
Dirk Eddelbuettel @ 2005-12-30 (Friday), 07:22 (-0600)
> | The compilation has finished, but it seems like the build process did
> | not honour DEB_BUILD_OPTIONS. (Debian Policy 10.1 [1])
> |
> [zap]
> |
> | Unless someone tells me how to easily produce a debugable debian
> | package, I'm not spe
Martin Samuelsson @ 2005-12-30 (Friday), 09:23 (+0100)
> I just started rebuilding octave again with DEB_BUILD_OPTIONS set to
> "nostrip noopt". Hopefully that will give some clues.
The compilation has finished, but it seems like the build process did
not honour DEB_BUILD_OPTIONS
Martin Samuelsson @ 2005-12-29 (Thursday), 22:35 (+0100)
> After upgrading octave today, it no longer starts at all. Reverting back
> to octave2.1_2.1.72-5_i386.deb makes it work again.
I tried rebuilding 2.1.72-5 locally to see if something in the packaging
breaks the package, or if it
Package: octave2.1
Version: 2.1.72-6
Severity: grave
Justification: renders package unusable
After upgrading octave today, it no longer starts at all. Reverting back
to octave2.1_2.1.72-5_i386.deb makes it work again.
This happens on at least two different machines. I have not done any
further b
tags 338920 + patch
thanks,
Jason Hoover @ 2005-11-13 (Sunday), 15:26 (-0500)
> Migrationtools leaves insecure temporary files containing information from
> /etc/shadow.
Attached is a patch that calls mktemp at appropriate places. I took the
liberty to change the variable names used from TMPDIR
Kurt Roeckx @ 2005-06-12 (Sunday), 23:05 (+0200)
> You should be using something like dpkg --print-architecture or
> dpkg-architecture instead.
Would this patch do the trick?
--
/Martin
diff -ur checkinstall-1.5.3/checkinstall checkinstall-patched-1.5.3/checkinstall
--- checkinstall-1.5.3/checkins
13 matches
Mail list logo
