Package: sysfsutils
Followup-For: Bug #729434
Sorry, I take my words back, everything works. After manually change the
governors (ondemand->powersave and back)
you need to restart syfsutils.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-proposed-updates
APT policy: (
tags 724058 patch
tags 727380 patch
thanks
Hi there,
please find attached a debdiff for a QA upload that fixes these issues:
freewnn (1.1.1~a021+cvs20130302-4) unstable; urgency=low
* QA upload.
* debian/patches/fix-parallel-build.patch: (Closes: #724058)
- Add patch from upstream to fi
Processing commands for cont...@bugs.debian.org:
> tags 724058 patch
Bug #724058 [src:freewnn] freewnn: FTBFS in parallel mode
Added tag(s) patch.
> tags 727380 patch
Bug #727380 [src:freewnn] freewnn: update config.{sub,guess} for the AArch64
port
Bug #727861 [src:freewnn] freewnn: update config
Processing commands for cont...@bugs.debian.org:
> forcemerge 727380 727861
Bug #727380 [src:freewnn] freewnn: update config.{sub,guess} for the AArch64
port
Bug #727380 [src:freewnn] freewnn: update config.{sub,guess} for the AArch64
port
Marked as found in versions freewnn/1.1.1~a021+cvs201003
You are probably right. However, the non-upgrade was not done
intentional, and the situation may cause a user a lot of headache.
Don't know how to fix that.
Regards,
Claus
--
Claus Fischer
http://www.clausfischer.com/
signature.asc
Description: Digital signature
Hi,
Mario J. Barchéin Molina wrote:
> > On you https://github.com/intelligenia/mssh you declare this to be
> > version 1.2.1. Do you intend to continue development of mssh in
> > general?
>
> I'm not experienced in C or GTK+ so I don't think I can take this project,
> sorry.
Same here.
> I bump
2013/11/18 Axel Beckert
> tag 729881 + confirmed
> kthxbye
>
> Hi Mario,
>
> Mario J. Barchein Molina wrote:
> > Port number can't be specified when connecting to any host and it's
> > always fixed to port 22 (ssh).
>
> Yes and no. You can connect to hosts with SSHd listening on a
> different hos
Processing commands for cont...@bugs.debian.org:
> tag 729881 + confirmed
Bug #729881 [mssh] mssh: port number is always fixed to 22
Added tag(s) confirmed.
> kthxbye
Stopping processing here.
Please contact me if you need assistance.
--
729881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=7
tag 729881 + confirmed
kthxbye
Hi Mario,
Mario J. Barchein Molina wrote:
> Port number can't be specified when connecting to any host and it's
> always fixed to port 22 (ssh).
Yes and no. You can connect to hosts with SSHd listening on a
different host by adding the according entry to your ~/.ss
Package: mssh
Version: 1.2-4
Severity: normal
Dear Maintainer,
Port number can't be specified when connecting to any host and it's always
fixed to port 22 (ssh). This can't be done:
mssh myserver1:2221 myserver2:64322
I have fixed this bug. The code with fix included is available in
https://git
tags 729813 + patch
tags 729813 + upstream
thanks
hi again,
it seems opensuse ships a way more recent version of the module, fixing this
bug aswell as some others. Apparently this one has been around for quit a
while...
2011-05-11 Thorsten Kukuk
* release version 2.8
* configure.
Processing commands for cont...@bugs.debian.org:
> tags 729813 + patch
Bug #729813 [libpam-unix2] jessie/testing pam_unix2 (2.6-1) module is compiled
without blowfish support
Added tag(s) patch.
> tags 729813 + upstream
Bug #729813 [libpam-unix2] jessie/testing pam_unix2 (2.6-1) module is compile
On 18.11.2013 14:36, Claus Fischer wrote:
[...]
> Unfortunately I don't know that, and I can't downgrade this computer
> again.
Ok. I believe you didn't upgrade both packages. The file
/etc/sane.d/gt68xx.conf slightly differs in older version of libsane.
Since you had installed the i386 and amd64
hi there,
i think this happens because of:
checking for xcrypt_gensalt_r... no
checking the source reads:
#if defined(HAVE_XCRYPT_GENSALT_R)
[ do stuff ]
#else
__write_message (pamh, flags, PAM_ERROR_MSG,
_("No support for blowfish included"));
I guess md5 is broken a
Hi,
please keep the bug report in CC.
did you perform an upgrade from version 1.0.22-7.4 in wheezy? What was
the version of libsane:i386 before you purged it?
Looking at the dpkg output, it appears to me that libsane:amd64 was
upgraded but libsane:i386 wasn't.
Can you reproduce the dpkg error m
On Mon, Nov 18, 2013 at 02:24:28PM +0100, Markus Koschany wrote:
> Hi,
>
> please keep the bug report in CC.
>
> did you perform an upgrade from version 1.0.22-7.4 in wheezy? What was
> the version of libsane:i386 before you purged it?
Before, I was on wheezy; I upgraded on the 12th; from this,
16 matches
Mail list logo
