Mehdi Dogguy writes:
> [ Dropped CC to -release and replaced it by 667...@bugs.debian.org ]
>
> On 16/04/12 11:26, Sébastien Villemot wrote:
>> Hi,
>>
>> As part of the octave transition, the following hints should be
>> added to allow testing migration of a bu
Sébastien Villemot writes:
> A bug still needs to be filed against libsml, we’ll
> do it shortly.
Sorry, double mistake here: first, it is libsBml; second, no need to
file an Octave-related bug, the problem is an FTBFS on s390x.
Thanks,
--
Sébastien Villemot
Researcher in Economics &a
Joachim Breitner writes:
> Am Montag, den 16.04.2012, 11:51 +0200 schrieb Mehdi Dogguy:
>> [ Dropped CC to -release and replaced it by 667...@bugs.debian.org ]
>>
>> On 16/04/12 11:26, Sébastien Villemot wrote:
>> > Hi,
>> >
>> > As part of the
ated packages in
Debian.
Best,
[1] http://wiki.debian.org/Teams/DebianOctaveGroup
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgpi4l11Ee24C.pgp
Description: PGP signature
Hi,
I encountered the same problem.
My / is luks-encrypted with aes in mode xts-plain64:sha256.
It turns out that dracut doesn't include the xts module in the
initramfs, thus cryptsetup hangs.
It seems it's already fixed upstream :
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/htm
ckages in sid, your package failed to build on
> amd64.
This bug won't be fixed since the removal of octave3.2 has been
requested.
Thanks,
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A75
ication: FTBFS on amd64
>
> Time to remove it from the archives, then? ;-)
Already requested, see #672751.
The removal is currently blocked by a reverse dependency of
pfstools. This should hopefully be fixed soon.
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://
Package: src:fsl
Version: 4.1.9-4
Severity: important
Dear Maintainer,
The fsl package Build-Depends on octave3.2-headers, whose removal has been
requested (see #672751). You should instead Build-Depend on the new
liboctave-dev package. The ${octave:Depends} field could just be replaced by
"octav
Julien Cristau writes:
> On Sun, Jun 10, 2012 at 19:07:38 +0200, Sébastien Villemot wrote:
>
>> What is clear is that the atlas binaries built on the amd64 buildds
>> should not have the problem that is affecting the current amd64 binary
>> (for example I tested the bina
OMMON_MAKE_OPTIONS) $(DYNAMIC_ARCH_ARG) $(TARGET_GENERIC_ARG); \
fi
if test "$(TARGET)" = "custom"; then \
Description: Fix profile for generic CPU
The macros have been renamed for all CPU except the generic one. This patch
fixes this.
Author: Sébastien Villemot
Last
Package: gnome-shell-timer
Version: 0.0.20120103+gitc7b8d8f-1
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
The extension refuses to load under Gnome Shell 3.4, because it is marked as
compatible with Gnome 3.2 only.
The fix seems as simple as this upstream
ake sure that they are consistent:
sudo update-alternatives --config libblas.so.3
sudo update-alternatives --config liblapack.so.3
Best,
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgpKDJyl1Afmi.pgp
Description: PGP signature
Laurent Bonnaud writes:
> this bug is still there in this package version:
Sorry, you are right (I was confusing two bugs).
This bug is still present, and it is the reason why it is not yet
closed…
If you have any idea on how to solve this, it is very welcome.
--
Sébastien Ville
s and not a Depends, we are not
preventing the user from using gnuplot-nox if he really wants. We are
just giving sane defaults.
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgpPbFrEs9Kig.pgp
Description: PGP signature
Sébastien Villemot writes:
> Package: octave-java
> Version: 1.2.8-4
> Severity: grave
>
> This version of octave-java completely breaks octave.
Note that this does not appear to be a GCC 4.7 bug. I tried with gcc
4.6.3-1 (in testing as of today) and with gcc 4.7.1-1 (in unsta
And setting -O0 (tested with both GCC 4.6 and 4.7) does not help either.
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgpoUT8p8PkFk.pgp
Description: PGP signature
t; mkdir tmp
> (cd tmp && ar x /usr/lib/liblapack_pic.a);
> ar: /usr/lib/liblapack_pic.a: No such file or directory
Is the liblapack-pic package installed on your system?
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgpEpfvymZGsK.pgp
Description: PGP signature
264cb0166f5324677bf2615252fda8e3
Also, /usr/lib/jvm/default-java points to OpenJDK 6 on my Debian sid
system. If you want to select OpenJDK 7, you need to set the JAVA_HOME
variable to:
export JAVA_HOME = /usr/lib/jvm/java-7-openjdk-amd64
(this is done in debian/rules of the octave-ja
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Dear Release Team,
The libiml0 package is in an unusable state in sid:
$ ldd /usr/lib/libiml.so
[...]
libcblas.so.3gf => not found
libatlas.so.3gf => not found
The reason is a SONAME c
Package: ftp.debian.org
Severity: normal
The package octave-time is now obsolete. All its functionalities have been
merged into the octave-financial package as of version 0.4.0-1 (see
/usr/share/doc/octave-financial/NEWS.gz).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.or
Package: release.debian.org
Followup-For: Bug #667863
User: release.debian@packages.debian.org
Usertags: transition
The octave transition is well under way, but it is still blocked by a few
packages which have not yet adapted to the new octave packaging scheme. The
goal of the Debian Octave Gr
Package: ftp.debian.org
Severity: normal
The author of this package has passed away, and nobody took up its maintenance
upstream. The upstream package is no longer distributed on a public website.
Note that even though I am not listed in the Uploaders field of semidef-oct, I
am an active member o
Package: ftp.debian.org
Severity: normal
The testsuite of this packages crashes randomly, see [1] and [2]. In
particular, this is blocking the octave transition [3].
Also, the (upcoming) octave-openmpi-ext package [4] provides similar
functionality using the more mature MPI interface.
We may rei
7;t fall back on mrxvt because it does not support UTF-8.
I would be really delighted if you could correct this bug.
Thanks in advance.
Sébastien
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Package: src:lapack
Version: 3.4.1-1
Severity: minor
The suject says it all.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU core
Package: libatlas3-base
Version: 3.8.4-4
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
After upgrading to version 3.8.4-4 of the package, I get errors such as:
octave: error while loading shared libraries: liblapack.so.3gf: cannot open
shared object file:
r/lib/openblas-base/libopenblas.so.0 - priority 40
slave libblas.so.3gf: /usr/lib/openblas-base/libopenblas.so.0
Current 'best' version is '/usr/lib/openblas-base/libopenblas.so.0'.
As you can see, there is a slave alternative providing libblas.so.3gf.
--
Sébastien Villemot
Res
Package: octave-java
Version: 1.2.8-4
Severity: grave
Tags: sid
This version of octave-java completely breaks octave.
For example, if octave-io is also installed, octave miserably fails at launch
time:
octave: lex.ll :2420 : void handle_number(): L'assertion « nread == 1 » a
échoué.
panic: Aba
Package: release.debian.org
Followup-For: Bug #667863
User: release.debian@packages.debian.org
Usertags: transition
All source uploads/NMUs concerning this transition have been done, and the
octave3.2 package has been removed from unstable.
The only thing left is to have testing in sync.
--
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
The package for amd64 has apparently been built with a too recent and specific
CPU architecture, leading to "Illegal instructions" on many recent Intel Core
CPUs. A rebuild fixes the problem.
Philipp Kern writes:
> On Sun, Jun 10, 2012 at 02:34:56PM +0200, Sébastien Villemot wrote:
>> The package for amd64 has apparently been built with a too recent and
>> specific
>> CPU architecture, leading to "Illegal instructions" on many recent Intel Core
>&
preferred option.
Making gnucash depend on yelp is not an option, since gnucash-docs is
only recommended. Making gnucash recommending yelp in addition to
recommending gnucash-docs basically adds nothing, since gnucash-docs
already recommends yelp.
What are your thoughts on this?
--
Sébastien Villem
severity 645773 minor
tags 645773 + confirmed
thanks
Celejar writes:
> On Tue, 18 Oct 2011 16:32:57 +0200
> Sébastien Villemot wrote:
>
>> If you disagree with this view, I see only two solutions:
>>
>> - make gnucash-docs depend on yelp rather than just recommend
Package: matlab-support
Version: 0.0.16
Severity: wishlist
Dear Maintainer,
It would be very useful to have a desktop launcher for MATLAB, following
the FreeDesktop specification. [1]
It could reside in the `/usr/share/applications/MATLAB.desktop' file,
with a content like:
->8-
found 464587 2.4.1-2
thanks
The bug was fixed in version 2.4.1-2 when used in conjunction with Yelp
2.30.
But since the introduction of Yelp 3.2, the bug has reappeared.
Therefore reopening this bug.
--
Sébastien Villemot
Researcher in Economics at CEPREMAP & Debian Maintainer
achine on which you had this problem? It is unlikely that you got this
because gconfd-2 was uninstalled, since it is a dependency of gnucash.
Also, I am lowering the severity of this bug since the problems that you
describe do not prevent GnuCash from functionning (though they are
frustrating for a user w
o
reproduce this bug. But I am able to reproduce it with version 2.24.6-2.
So I think this bug is fixed now.
Nils: can you please confirm this after installing the latest packages
for gtk+2.0?
Best,
--
Sébastien Villemot
Researcher in Economics at CEPREMAP & Debian Maintainer
http://www.dynar
I had the same issue than the submitter and installing the non-free
Linux firmware solved the problem.
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgp8LPPKOxpLY.pgp
Description:
Any hint?
[1]
https://buildd.debian.org/status/fetch.php?pkg=octave-miscellaneous&arch=s390x&ver=1.0.11-2&stamp=1331510586
[2] https://buildd.debian.org/status/package.php?p=octave-miscellaneous
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/s
delay the migration of the package for
no good reason. On average I am not sure this is a net gain.
But maybe you had other cases in mind?
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgplVIZTaP72p.pgp
Description: PGP signature
;octave" package (version 3.6.1) and let me know if
the problem persists?
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgpW2JsCmgDfI.pgp
Description: PGP signature
(cc:ing the bug)
Xiangyu Liu writes:
> You mean that you can imread and imshow these JPEG pictures in
> Octave3.2 ?
Yes indeed, I have tried with both octave 3.2 and 3.6, and I could read
and display the JPEG that you attached.
> 2012/4/5 Sébastien Villemot
>
>
Package: pcsxr
Version: 1.9.92-4
Severity: important
Tags: upstream
Dear Maintainer,
on my system, pcsxr can't be launched with 4.1.* kernel.
I got this output:
ALSA lib pcm.c:7905:(snd_pcm_recover) underrun occurred
Intel Open Source Technology Center
Mesa DRI Intel(R) Haswell Mobile
pcsx: ../l
Le 2015-09-12, Sébastien Dufromentel a écrit :
> Tags: upstream
Oops, this was a mistake due to a clumsy clic on reportbug. I don't know if
it's upstream or not. Sorry.
In addition, the output trace for launching the emulator on 4.0 kernel is just:
Intel Open Source Technology Ce
s other than amd64 and i386?
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: This is a digitally signed message part
benefit… Or am I missing
something?
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
Le jeudi 17 septembre 2015 à 18:36 +0200, Graham Inggs a écrit :
> On 17/09/2015 17:38, Sébastien Villemot wrote:
> > I don't understand why this would be better. It seems to me that it
> > would just eat buildd resources, with no clear benefit… Or am I
> > missing
.
Cheers,
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.org/sebastien
`- GPG Key: 4096R/381A7594
signature.asc
Description: Digital signature
Hi,
mitmproxy builds fine in an up-to-date sid amd64 chroot here. How can I
reproduce your problem ?
Cheers,
--Seb
On Nov/08, Chris Lamb wrote:
> Source: mitmproxy
> Version: 0.18.1-2
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian
On Nov/09, Chris Lamb wrote:
> > mitmproxy builds fine in an up-to-date sid amd64 chroot here. How can I
> > reproduce your problem ?
>
> How up-to-date? :) I've just updated mine (again) and it fails with the same
> error.
tag 843687 + confirmed
You're right, I just tried it this morning, and
share/update-notifier/notify-reboot-required
Thanks,
Sébastien
This was assigned CVE-2017-9058.
On Mar/28, Markus Koschany wrote:
> apparently logback < 1.2.0 is vulnerable to a deserialization issue.
> They announced it on February 8th 2017 but it appears no CVE has been
> assigned yet. [1] Fixing commit is at [2] The bug reporter claims it is
> the same issue as CVE-2015-6420 but I cannot v
On Mar/10, Sébastien Delafond wrote:
> I meant a debdiff specifically targetting jessie-security. Please
> change jessie to jessie-security, set severity to high, and upload to
> security-master (no source-only upload).
Hi Petter,
are you still planning to upload this ?
Cheers,
--Seb
On Mar/18, Holger Levsen wrote:
> I've done all this now.
>
> Will you write and send the DSA? I guess the text should basically
> just be something like what we wrote in debian/changelog:
>
> * Adjust sitesummary-upload to use CRLF (\r\n) line endings to be compliant
> with apache 2.4.25 s
Hi Kevin,
those 4 security issues were fixed via DSA-3798-1 in jessie-security, by
backporting the appropriate upstream changes (thanks to Thorsten for
doing that).
I've verified 1.4.13 only contains those security fixes, and no new
major evolution or feature, so could you please prepare and uplo
Package: libsigsegv2
Version: 2.10-5
Severity: normal
Dear Maintainers,
The homepage for this package is defined to be
http://libsigsegv.sourceforge.net/
Actually the page has moved to
http://www.gnu.org/software/libsigsegv/
On Mar/09, Holger Levsen wrote:
> Dear security team,
>
> On Thu, Mar 09, 2017 at 07:20:40PM +, Adam D. Barratt wrote:
> > On Thu, 2017-03-02 at 09:50 +, Holger Levsen wrote:
> > > On Thu, Mar 02, 2017 at 09:12:34AM +0100, Petter Reinholdtsen wrote:
> > > > Usertags: pu
> > > >
> > > > Th
On Mar/10, Petter Reinholdtsen wrote:
> The debdiff for jessie is in bts already.
I meant a debdiff specifically targetting jessie-security. Please change
jessie to jessie-security, set severity to high, and upload to
security-master (no source-only upload).
Cheers,
--Seb
Dear Release Managers,
the Security Team has reviewed the diff related to this security
problem, and we support the unblock request.
Cheers,
--Seb
On Feb/16, Henri Salo wrote:
> Shouldn't this be closed AFTER the fix is available? Especially since this is
> a
> security issue.
Yes. Bastien, can you please reopen this ?
Cheers,
--Seb
I'll take care of packaging this.
Cheers,
--Seb
.
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: PGP signature
could take
> months
> until I actually need this...
I would be happy to co-maintain this package with you.
I guess the first step is to create a repository on collab-maint, and
start populating it if you already have something.
Cheers,
--
.''`.Sébastien Villemot
: :&#
Le vendredi 05 mai 2017 à 22:06 +0100, James Cowgill a écrit :
> On 05/05/17 12:10, Graham Inggs wrote:
> > Control: reassign -1 src:openblas 0.2.19-2
> > Control: retitle -1 openblas: random segfaults on mips64el
> > Control: affects -1 src:julia
> >
> > Hi
/0.2.19-3
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
diff -Nru openblas-0.2.19/debian/changelog openblas-0.2.19/debian/changelog
--- openblas-0.2.19/debian/changelog 2017-01-23 15:0
nnot open shared object file: No such file or directory
I have uploaded to DELAYED/10 an NMU that fixes the issue. The debdiff
is attached.
Don’t hesitate to tell me if I should delay it longer (or instead
shorten the delay).
Best,
--
.''`.Sébastien Villemot
: :' :Debian Develope
[resending with the bug in CC]
Hi Lev,
Le dimanche 05 février 2017 à 20:03 +0500, Lev Lamberov a écrit :
> 05.02.2017 18:37, Sébastien Villemot пишет:
> > On Sat, 28 Jan 2017 09:27:37 +0100 Lucas Nussbaum > >
> >
> > wrote:
> > > Source: swi-prolog
> &
Hence, it is not possible to enforce the dependency of libblacs-openmpi
on one or the other without breaking this flexibility.
By the way, does this bug really warrant a serious severity? I could not
find anything in the Policy mandating proper linking of shared libraries
within the same package.
Le mercredi 08 février 2017 à 17:48 +0500, Andrey Rahmatullin a écrit :
> On Wed, Feb 08, 2017 at 01:21:13PM +0100, Sébastien Villemot wrote:
> > By the way, does this bug really warrant a serious severity? I could not
> > find anything in the Policy mandating proper linking of s
discussion in
https://lists.debian.org/debian-science/2017/02/msg00047.html).
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: PGP signature
discussion in
https://lists.debian.org/debian-science/2017/02/msg00047.html).
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: PGP signature
Package: src:atlas
Severity: wishlist
Everything is in the subject…
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: PGP signature
. If you are unsure
about this, you may want to contact the Debian Security Team.
Cheers,
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: This is a digitally signed message part
Package: src:gegl
Version: 0.3.6-4
Severity: normal
Dear Maintainer,
gegl FTBFS if either libtiff5-dev or libwebp-dev is installed.
You should therefore add these to Build-Conflicts (or alternatively add them to
Build-Depends and fix the FTBFS).
Cheers,
--
.''`. Sébastie
Package: src:freefem++
Version: 3.46+dfsg1-2
Severity: serious
Dear Maintainer,
freefem++ FTBFS on most release arches (only armel was successful on build
daemons).
The build timeouts during the testsuite.
I have a similar issue on a local amd64 chroot.
Best,
--
.''`. Sébastie
release, upstream commits to ABI tracking. Hence the
shorter SONAMEs.
All reverse deps build fine (except two which FTBFS for unrelated reasons:
freefem++/#824256, elmerfem/#754713).
Best,
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemo
Le mardi 17 mai 2016 à 15:54 +0200, Emilio Pozuelo Monfort a écrit :
> Control: tags -1 confirmed
>
> On 14/05/16 10:33, Sébastien Villemot wrote:
> >
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
>
5280
Cheers,
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: PGP signature
).
Cheers,
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: PGP signature
nner alternatives were dropped the package description was not
> altered to match
Indeed it used to depend on xulrunner, but the latter was dropped (and
you should ask the Mozilla maintainers if you are interested in the
underlying reasons).
Cheers,
--
.''`.Sébastien Villemot
: :
aracters
I've got some proxy-related environment variables. Unsetting them fixes the
issue :
$ HTTP_PROXY= HTTPS_PROXY= http_proxy= https_proxy= npm view keybase
[No more error]
Sébastien
epro_user.db:
Permission
> denied
> Oct 26 19:51:41 debian repro[3713]: REPRO:APP | 140335355619136 |
> ReproRunner.cxx:973 | Failed to open configuration database
>
> The install log is attached. There was no log file in /var/log/repro.
I confirm this. In /etc/repro/repro.config, the Database1
Package: nautilus
Version: 3.18.3-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
The situation happens after upgrading from nautilus 3.14 to 3.18.3
In version 3.14 the ownCloud remote folder integration worked fine right after
setting my ownCloud account (self hosted serve
oon.
Cheers,
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.org/sebastien
`- GPG Key: 4096R/381A7594
signature.asc
Description: This is a digitally signed message part
tag 758733 pending
thanks
Date: Thu Aug 21 22:10:37 2014 +0200
Author: Sébastien Villemot
Commit ID: 3847d6f7e338766d1a3692012a197cb08208de72
Commit URL:
http://anonscm.debian.org/gitweb/?p=pkg-octave/octave-communications.git;a=commitdiff;h=3847d6f7e338766d1a3692012a197cb08208de72
Patch URL:
Le vendredi 22 août 2014 à 10:03 +0200, Gilles Filippini a écrit :
> = binNMU required =
> octave-communications
Note that this binNMU needs to be done after octave's binNMU.
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.
On Aug/06, Gianfranco Costamagna wrote:
> I opened an issue about python-passlib, since it is good to update it anyway.
I don't think the blocking of 789782 by 794752 is correct: Aldo Cortesi
confirmed that 1.6.1 would do the job fine, so the only thing left to
get updated in sid is python-urwid (
On Aug/04, Nicholas Luedtke wrote:
> Is this still an ongoing issue?
>
> As I am looking at bringing the MITRE Oval Interpreter (ovaldi) up to speed
> for Debian (by modifying and packaging) I am noticing that there have been
> no OVAL Definitions from Debian for quite some time. I can put forth s
On Aug/11, Gianfranco Costamagna wrote:
> >I don't think the blocking of 789782 by 794752 is correct: Aldo Cortesi
>
> >confirmed that 1.6.1 would do the job fine, so the only thing left to
> >get updated in sid is python-urwid (#789767).
>
>
> Please note that I will need at least 0.13 version
nux bug. Before
25bfb1dd4ba3b2d9a49ce9d9b0cd7be1840e15ed downing the iface only causes
2/3s of packet loss on the IPMI side.
The Maintainers have been contacted.
So if the issue is confirmed and fixed by the maintainers, it would be
great to backport the fix to Jessie's kernel.
--
Sébastien Bocahu
IT infrastruc
Le mercredi 23 mars 2016 à 20:29 +, Adam D. Barratt a écrit :
> On Wed, 2016-01-13 at 11:07 +0100, Sébastien Villemot wrote:
> >
> > I'd like to push a new upstream release of gnome-shell-extension-
> > weather in jessie.
[...]
> Assuming that the resulting pack
By default ~/.local seems to be 700, so I don't think you're correct in
assuming anyone can read ~/.local/share/clipit/history. Am I missing
something ?
Cheers,
--Seb
4242/8042" default ports
* Apply the "Generic replication" procedure [1]
This upgrade problem should not occur again in the future, as I think that the
database schema has reached its final state since Orthanc 1.0.0.
Sorry for the inconvenience,
Sébastien-
[1]
https://orthanc.chu.ulg.ac.be/book/users/replication.html#generic-replication
Hello,
Thanks for reporting this issue. It has been fixed in the following
changelist:
http://anonscm.debian.org/cgit/debian-med/orthanc.git/commit/?id=99f77dccb144c029899feabdedddfdaa6a5250fe
A new version of the package will soon be uploaded by the Debian-Med team.
Regards,
Sébastien-
On
lt;<<
Could someone give me a hint? Is it because, as Ralf says at the end of his
report, the packages are slightly out of sync?
TIA,
Sébastien-
- Mail original -
> De: "Ralf Treinen"
> À: sub...@bugs.debian.org
> Envoyé: Mardi 5 Avril 2016 08:44:44
> Objet:
x) this bug by myself.
Andreas (Tille), would it be possible that there was a problem when you
uploaded the package last Monday?
I definitely need someone else to solve this bug. Otherwise, Orthanc will soon
disappear from Debian testing.
Sorry again,
Sébastien-
tag 823353 + moreinfo
It certainly works fine here, with the following list of dependencies
(provided by reportbug):
Versions of packages mitmproxy depends on:
ii python-blinker 1.3.dfsg2-1
ii python-click 6.2-2
ii python-configargparse 0.10.0-2
ii python-construc
experimental.
All reverse deps seems to build fine with the new version.
Best,
--
.''`. Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
signature.asc
Description: PGP signature
Hi Mathias,
any chance you can your full list of dependencies like I asked in the
previous message ? Otherwise I'll close this bug, as I really cannot
reproduce it.
Cheers,
--Seb
701 - 800 of 2299 matches
Mail list logo
