Control: tag -1 pending
Hello,
Bug #972262 in ocamlviz reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ocaml-team/ocamlviz/-/commit/d2a599e56e82e14a1284fbb6c5e2
Control: tag -1 pending
Hello,
Bug #980309 in opam reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ocaml-team/opam/-/commit/c6686267c0a384112dfa7b0c406c0f6f7d1b
hi,
on jessie, after upgrade to libssh2-1_1.4.3-4.1+deb8u2, the following PHP
code doesn't work anymore.
could it be related to this fix?
https://github.com/libssh2/libssh2/commit/ca2744483eac4e707084df5fc55cc69d57571dde
PHP Warning: ssh2_auth_pubkey_file(): Authentication failed for test
usin
Control: tag -1 pending
Hello,
Bug #897774 in infinipath-psm reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/hpc-team/infinipath-psm/commit/c5a458aa4ebfe64fa7f
Sure, but it is still an improvement over the current situation and is simple
enough to minimize its impact. Of course, it should be considered as a
wrkaround, until upstream releases a fixed version.
Le 29 octobre 2018 19:41:06 GMT+01:00, Brian Smith
a écrit :
>Hi Mehdi,
>
>
>On
issue for users
(and reverse dependencies) while giving upstream more time to
investigate it.
--
Mehdi
the code didn't change at all. I was able to
reproduce the issue, but I am not actually sure yet from where the
regression is coming.
--
Mehdi
Hi Jonas,
On 2018-10-15 19:54, Lippuner, Jonas wrote:
I'm having the same issue with libpsm2-2 version 11.2.68-1. Downgrading
to 10.3.58-2 fixes it for me.
Can you please explain how you experienced the bug? I've understood
Drew's
case, but maybe yours is slightly different.
--
Mehdi
Control: tag -1 pending
Hello,
Bug #909086 in opam reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/ocaml-team/opam/commit/8fa9d29ba36d98f349516f0101a5593fbbe51
Control: tag -1 pending
Hello,
Bug #907431 in cppo reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/ocaml-team/cppo/commit/416abc291f17f06e40d0bbc9e2d3cd6ba20e2
Hi nico,
On 2018-08-23 16:53, Nicolas Braud-Santoni wrote:
Hi Mehdi,
On Thu, Aug 23, 2018 at 03:00:22PM +0200, Mehdi Dogguy wrote:
> [...]
> It makes opam unusable for jessie users: already initialised ones can't
> install new compilers nor update packages, and with a fresh ins
emoval, or document in this bugreport how to point
their
installation to a frozen working mirror?
In the meantime, I'll work on a {sloppy-,}backport of 1.2.2.
--
Mehdi
Control: reopen -1
Hi Roland,
If I am not mistaken, your last upload moves files across binary
packages but doesn't add necessary Breaks/Replaces. In the current
state, upgrades are broken because older libfabric1 and newer
libfabric-dev are not co-installable.
Regards,
--
Mehdi
Control: tag -1 pending
Hello,
Bug #901191 in libfabric reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/hpc-team/libfabric/commit/1bd5e81a6e6d958ccffc208e0e0f8
build fail later in
the process (can't generate manpages and test-suite doesn't succeed).
Do you confirm this on your side as well?
--
Mehdi
Package: courier-imap
Version: 4.15-1.6
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
apt-get update
apt-get -y -V upgrade
apt-get -V -y install ntpdate wget sudo dnsutils aptitude apt-utils
lsb-release bash-complet
It's based on the discussion with upstream at
https://discuss.ocaml.org/t/the-forever-beta-issue/1779/6
Thanks for the pointer.
Cheers,
--
Mehdi
Package: opam
Version: 1.2.2-6+b1
Severity: serious
opam fails to build from source using latest cmdliner which was uploaded
to Debian/Sid a few days ago:
File "client/opamArg.ml", line 384, characters 25-29:
Error: This expression has type
?docv:string ->
(string -> ('a, [ `Msg
pstream asking whether bytecode architectures are still supported.
I didn't want to patch Frama-C to make it build again there is there is no
will from upstream to support those architectures (It is trivial to fix but
might a useless effort). I am still waiting for their reply.
--
Mehdi
On 06/11/2016 10:19, Adrian Bunk wrote:
> On Sun, Nov 06, 2016 at 09:59:20AM +0100, Mehdi Dogguy wrote:
>> I've tried a rebuild on harris with pic_code set to true for arm. The build
>> succeeded and all tests passed fine. Do you want to run more tests or should
>
Salut Ralf,
On 06/11/2016 08:27, Ralf Treinen wrote:
> Salut Mehdi,
>
> On Sat, Nov 05, 2016 at 06:36:06PM +0100, Mehdi Dogguy wrote:
>> Hi Ralf,
>>
>> On Tue, Oct 25, 2016 at 09:08:34AM +0200, Ralf Treinen
>> wrote:
>>> Hi Chris,
>>>
>&
ent to fix this, and already requested.
>
The binNMU has been scheduled and the only missing issue is to do with PIC on
armhf. The issue needs to be fixed in OCaml only. Hence, I am reassigning the
bug. Once OCaml is fixed on armhf, ocamlgraph could be given back to build.
Regards,
--
Mehdi
figure out how to make Cflags.pic_code true,
> which shouldn't be too hard. I will try this tomorrow when I'm less tired.
>
I've tried a rebuild on harris with pic_code set to true for arm. The build
succeeded and all tests passed fine. Do you want to run more tests or should
I upload this change?
Regards,
--
Mehdi
rovide libsexplib-camlp4-dev.
>
libsexplib-camlp4-dev is gone for good. So, there is nothing to fix in sexplib
and reverse dependencies have to be fixed. Hence, closing this bugreport
and opening required new bugreports.
Regards,
--
Mehdi Dogguy
;
Did you understood what actually makes it fail? It builds fine in a clean
chroot on my machine (dunno by which miracle).
The errors orginally reported by Chris are also not the same seen on the
buildds.
Regards,
--
Mehdi Dogguy
g on
a backward compatible patch to make it work with both OpenSSL 1.0 and
1.1.
So I'd wait until he is ready. In the worst case scenario, we can still
fallback to OpenSSL 1.0 to give us more time to work on the patch.
Regards,
--
Mehdi
tried to rebuild parmap in a clean Sid chroot and I am unable
to reproduce the build failure. You can find attached my build log.
Does it still fail for you?
Regards,
--
Mehdi
dpkg-buildpackage: info: source package parmap
dpkg-buildpackage: info: source version 1.0~rc7-1
dpkg-buildpackage: in
... but why not requesting a rebuild of the package
instead of opening this bug? Is there anything else to do besides doing the
binNMU?
--
Mehdi
anymore. Similar fixes have been
applied to other softs.
Another way to avoid the bug in Debian is to use OpenSSL 1.0 by choosing
libssl1.0-dev in the Build-Depends line. It doesn't fix the issue but prevents
the system from removing it from testing.
Regards,
--
Mehdi
From: Mehdi Dogguy
Da
On 06/10/2016 00:32, John Paul Adrian Glaubitz wrote:
> On 10/06/2016 12:21 AM, Mehdi Dogguy wrote:
>> I have read your message, and I can understand it can be difficult at
>> time to deal with recurrent bugreports. But, I do not feel comfortable
>> with the way you expressed
utors and users, to be able to interact in
a safe and pleasant environment. We are all here to make fun! So
please, let's make it enjoyable the best we can.
[1] https://www.debian.org/code_of_conduct
All best,
--
Mehdi Dogguy
or target 'AAC.vo' failed
>> make[4]: *** [AAC.vo] Error 1
>> make[4]: Leaving directory '/<>'
>
This looks like a duplicate of #813459.
Regards,
--
Mehdi
Control: reassign 812178 camlp5
Control: severity 812178 important
Control: found 812178 camlp5/6.14-1
Control: fixed 812178 camlp5/6.14-2
On 21/01/2016 09:25, Mehdi Dogguy wrote:
> Trying to build matita with a fixed camlp5 package that includes upstream
&g
Package: matita
Version: 0.99.1-3
Severity: serious
Dear Maintainer,
Trying to build matita with a fixed camlp5 package that includes upstream
fix (caca3dd0643ec5aae9df4399fa73eb280808ef18) fails with the following
error:
OCAMLC hExtlib.ml
File "hExtlib.ml", line 463, characters 10-23:
War
Hi Enrico,
On 20/01/2016 11:15, Enrico Tassi wrote:
> On Sun, Oct 18, 2015 at 11:03:35PM +0200, Mehdi Dogguy wrote:
>> Package: src:matita
>> Version: 0.99.1-3
>> Severity: serious
>>
>> Dear Maintainer,
>
> This bugs is due to camlp5 and fixed in
>
ntering an issue that is not covered by what I've described, please
do share it with us so that we can try to help you.
>
> Have fun.
>
Likewise.
Kind regards,
--
Mehdi
on't work with OCaml >=4.02.3.
For now, we've requested the removal of Unison 2.40 and 2.32 from
Stretch and we are looking for a solution to make 2.48 also work
in stable.
Regards,
--
Mehdi
ersion in Stretch.
If you need a working Unison setup across multiple systems based on different
versions, you may copy needed Unison binary around, for now.
Regards,
--
Mehdi
On 2016-01-04 17:24, Stéphane Glondu wrote:
Le 22/12/2015 00:38, Mehdi Dogguy a écrit :
The change done in unison 2.48 to overcome this looks pretty big...
I'm
not sure I'll be able/willing to provide a unison2.40.102 any more.
Moreover, this package was created to provide compatib
Control: tags 805456 = moreinfo unreproducible
Control: severity 805456 important
Indeed. Works for me too. I am downgrading the severity of this bug and
tagging it as "unreproducible", waiting for a reaction by the submitter.
--
Mehdi
ble with recent OCaml version.
This is now fixed in Unison 2.48... hence the backport of Unison 2.48. But
there is nothing to fix in Stable...
My only doubt right now (about the backport) is about #805456. It would
be great to hear about the submitter before exposing Unison 2.48 to users
of stable.
Regards,
-- Mehdi
Hello,
On 29/12/2015 12:44, Hendrik Tews wrote:
> Mehdi Dogguy writes:
>
>> Can you give us a hint on how to work out a real fix for this issue?
>
> I am looking at it now. There is quite a bit new syntax in 4.02,
> yielding quite a few warnings about incomplete patter
that's a design flaw in Unison that cannot be easily fixed.
>
A possible way out for stable (and old-stable) users could be to use 2.48
from backports, when 2.48 will be packaged and migrated to testing.
My 2 cents,
--
Mehdi
Hi,
The cause of this build failure may be fixed in OCaml 4.03 according to:
http://caml.inria.fr/mantis/view.php?id=6517
--
Mehdi
nd since it introduces
a new bug in otags. The function to fix is:
http://anonscm.debian.org/cgit/pkg-ocaml-maint/packages/otags.git/tree/tags.ml#n361
Can you give us a hint on how to work out a real fix for this issue?
Or, do you plan to release a new version of otags fixing this?
Regards,
--
Mehdi
g cd tmp/buildd/*/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin"
dpkg-buildpackage -us -uc -v0.6.0-2~ -Zxz -v0.6.0-2~ -Zxz -rfakeroot
dpkg-buildpackage: source package cduce
dpkg-buildpackage: source version 0.6.0-2
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage:
l build logs can be found here:
https://buildd.debian.org/status/package.php?p=botch&suite=unstable
Regards,
--
Mehdi
variables are undefined : ppterm ppsubst ppobj
ppmetasenv ppcontext
../Makefile.common:102: recipe for target 'nCic.cmx' failed
make[3]: *** [nCic.cmx] Error 2
A full build log is attached.
Regards,
--
Mehdi -> Copying COW directory
forking: rm -rf /var/cache/pbuilder/buil
is doesn't seem to be a regression though.
Regards,
--
Mehdi Dogguy
reopen 768112
reassign 768112 sinfo 0.0.47-3
close 768112 0.0.47-4
thanks
reopen 768112
reassign 768112 sinfo/0.0.47-3
close 768112 0.0.47-4
thanks
s package is affected just like src:yaml-cpp. A proposed patch is
available from:
https://launchpad.net/ubuntu/+source/yaml-cpp0.3/0.3.0-1.1ubuntu1
Regards,
--
Mehdi Dogguy
Uses of std::string are exposed in the public API. A proposed patch is available
from:
https://launchpad.net/ubuntu/+source/wfmath/1.0.2+dfsg1-0.3ubuntu1
Regards,
--
Mehdi Dogguy
library uses std::list and std::string in its public API. A proposed patch
is available from:
https://launchpad.net/ubuntu/+source/siscone/2.0.6-1ubuntu1
http://ubuntudiff.debian.net/q/package/siscone
Regards,
--
Mehdi Dogguy
ses a use of std::string in public API. A proposed patch is available
from:
https://launchpad.net/ubuntu/+source/shiboken/1.2.2-1ubuntu3
Regards,
--
Mehdi Dogguy
Exposes std::string in the public API. A proposed patch is available from:
https://launchpad.net/ubuntu/+source/scalc/0.2.4-4ubuntu1
http://ubuntudiff.debian.net/q/package/scalc
Regards,
--
Mehdi Dogguy
libgcu0
(= ${binary:Version})" though.
In any case, there are some uses of std::string exposed in the public
API. So this package needs fixing.
Regards,
--
Mehdi Dogguy
>
It has only one reverse dependency (viva) which has low popcon.
Regards,
--
Mehdi Dogguy
;
It seems that there are no reverse dependencies.
--
Mehdi Dogguy
even has std::list exposed in the public API. So it definitely
needs renaming libopenrpt1. A proposed patch is available from:
https://launchpad.net/ubuntu/+source/openrpt/3.3.7-1ubuntu1
Regards,
--
Mehdi Dogguy
the
>library.
>
std::string is used and exposed in public API. A proposed patch is available
from:
https://launchpad.net/ubuntu/+source/openlayer/2.1-1ubuntu1
Regards,
--
Mehdi Dogguy
the
>library.
>
Renaming is needed since std::string is used and exposed in public API.
A proposed patch is available from:
https://launchpad.net/ubuntu/+source/usbprog/0.2.0-2.1ubuntu1
Regards,
--
Mehdi Dogguy
:string used in multiple places, exposed in the public API. This, this
packge
needs renaming. A proposed patch is available from:
https://launchpad.net/ubuntu/+source/relion/1.3+dfsg-2ubuntu1
Regards,
--
Mehdi Dogguy
ring exposed in public API. Packages needs a renaming.
Regards,
--
Mehdi Dogguy
e is an "msg" of type std::string exposed publicly in a class which is part
of the API. So vtk will need a rename. The version in experimental already
bumped
from 8 to 10 though, but I don't think we should mix the two transitions
together.
Regards,
--
Mehdi Dogguy
Control: severity -1 normal
Le 2015-07-19 16:23, gregor herrmann a écrit :
Builds fine for me in an amd64 unstable + g++-from-experimental
cowbuilder chroot.
Same here. Attached a buildlog (tested with g++ 5_5.2.1-11 from exp).
I am adjusting the bug's severity accordingly, but not closing i
subprocess paste was killed by signal (Broken pipe)
> Errors were encountered while processing:
>/var/cache/apt/archives/slurm-client_14.03.9-3_amd64.deb
>
This bug applies to both slurm-llnl and sinfo.
Regards,
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs-rc-re
dule it in DELAYED/0.
Thanks again!
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
s the program
will just kill itself?
Why not just setting _has_statsmodels=False when statsmodels version
is older than 0.6?
Regards,
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
d strength/time later today and otherwise tomorrow
> it would get plunged from jessie.
>
Any news? Should we add a removal hint for seaborn?
Regards,
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
added for libhtp.
Thank you. Could somebody please decide about #777042 ("unblock:
suricata/2.0.6-1")?
It was unblocked.
Regards,
--
Mehdi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Le 2014-11-28 11:47, Francois Marier a écrit :
I've taken the liberty to fix this via an NMU in the delayed/5days
queue.
I've taken the liberty to cancel it. Can you please test Matt's patch?
--
Mehdi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
wi
it can be no way an argument to make
this bug RC since all features of the package are not broken, on
the contrary.
And, fwiw, I am absolutely against upgrading the package _now_ to
0.45. I'll look more closely at the package instead to see if some
smaller fix can be found.
--
Mehdi
necessary data to measure that.
Regards,
--
Mehdi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
e freeze
but still)
So, is it acceptable to keep this workaround for Jessie and work on a
better
one for Jessie+1? That way, we hope to find time enough time to work
this
in coordination with both upstreams.
Kind regards,
--
Mehdi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@list
Le 2014-10-12 22:59, Gaudenz Steinlin a écrit :
Hi
Mehdi Dogguy writes:
Control: reassign 764441 sinfo
Control: fixed 764441 0.0.47-2
Le 2014-10-11 23:58, Gaudenz Steinlin a écrit :
Hi
Mehdi Dogguy writes:
Le 2014-10-09 22:55, Gaudenz Steinlin a écrit :
I will certainly update the
Control: reassign 764441 sinfo
Control: fixed 764441 0.0.47-2
Le 2014-10-11 23:58, Gaudenz Steinlin a écrit :
Hi
Mehdi Dogguy writes:
Le 2014-10-09 22:55, Gaudenz Steinlin a écrit :
I will certainly update the Conflict if we can't agree on a better
solution in the next few days. B
n a better solution to implement in Jessie+1.
Regards,
--
Mehdi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
's conflict to
> slurm-client with appropriate versioning.
>
Since your package had a Conflicts, can you please update it? If you agree
on that, can you also reassign this bug to src:sinfo so that it is tracked
properly?
Cheers.
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs-
Control: severity 752945 important
Le 2014-08-09 11:39, Mehdi Dogguy a écrit :
If I don't have a way to reproduce this bug, I guess I'll downgrade
the severity to important.
I tried to run some more tests in different contexts but wasn't able
to reproduce the described fail
de Jenkins
and directly using cowbuilder or pbuilder? Or, provide us the produced
log files to be able to
investigate further? Or, better, the full build directory.
My full build log is attached.
If I don't have a way to reproduce this bug, I guess I'll downgrade the
severity to impor
n uploaded
yesterday.
So the binNMU is indeed all that is needed (if the
ocaml-deriving-ocsigen's
API didn't change, of course). I'll let Stéphane handle them though,
maybe
he has more changes to implement in the affected packages.
Best,
--
Mehdi
--
To UNSUBSCRIBE, ema
import order is important. I have to admit that I didn't pay
attention to
how quilt import works. It seems that "quilt import 1.patch; quilt
import 2.patch"
puts 2 before 1. Adding a "sort -r" upon import is enough to fix this
build failure.
Thanks for your bug re
back?
Yes. Thanks for the notice. I just did that now.
Regards,
--
Mehdi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Control: reopen 745307
Control: reassign 745307 ocamlgraph 1.8.4-1
Control: close 745307 1.8.5-1
This bug is due to an API change appeared in OCamlgraph 1.8.4 and then
reverted
back in 1.8.5. OCamlgraph 1.8.3 (present testing's version) is not
affected.
--
To UNSUBSCRIBE, email to debian-bu
Le 2014-04-27 12:41, Ralf Treinen a écrit :
On Sun, Apr 27, 2014 at 11:19:40AM +0200, Mehdi Dogguy wrote:
Le 2014-04-20 13:13, Stéphane Glondu a écrit :
Source: dose3
Version: 3.1.3-7
Severity: serious
Dear Maintainer,
dose3 fails to build with the latest version of ocamlgraph (1.8.4).
It
build just fine now using the newly
released ocamlgraph 1.8.5, which I just uploaded.
I'll close this bug later, when ocamlgraph/1.8.5 will be available on
all archs.
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe&quo
Hi,
The upstream bug report:
https://bugs.launchpad.net/pyopenssl/+bug/1266521
It has a fix attached that wait to be merged.
Cheers,
--
Mehdi Abaakouk
mail: sil...@sileht.net
irc: sileht
signature.asc
Description: Digital signature
solution is to use testing's packages.
Regards,
--
Mehdi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Le 2013-11-13 21:58, gregor herrmann a écrit :
Please feel free to tell me if I should delay it longer.
You should really not ;) Feel free to reschedule it in delayed/0.
Thanks for your work!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe
on2.7
>
> Ah, you're right. Thanks for the heads-up. I'll be there with a debdiff
> showing my suggested NMU.
>
Any news here?
Regards,
--
Mehdi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
,
--
Mehdi Abaakouk
mail: sil...@sileht.net
irc: sileht
signature.asc
Description: Digital signature
dency
relation for an optional dependency. Things could be improved (as you
duly noted) by changing the default, detecting available dependencies
or adding recommends to the package but this still doesn't justify an
RC severity. I'm lowering the severity to "important&quo
present before launching the daemon?
Regards,
--
Mehdi Dogguy مهدي الدڤي
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 07/10/2012 19:07, Thomas Goirand wrote:
> On 10/08/2012 12:19 AM, Mehdi Dogguy wrote:
>> tags 689894 - patch thanks
>>
>> On 07/10/2012 17:06, Thomas Goirand wrote:
>>>
>>> Please fix your package. I have attached what I believe is a good
>>> f
time should be
> added. Please make sure to test before applying the patch blindly.
>
Can you please explain how your patch fixes the problem? AFAICS, you
don't re-create /var/run/jabberd2 anywhere.
Regards,
--
Mehdi Dogguy مهدي الدڤي
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@l
fore using it.
Regards,
--
Mehdi Dogguy مهدي الدڤي
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
hanged, 49485 insertions(+), 13745 deletions(-)
>
> [0]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678979
>
> [1]: http://packages.qa.debian.org/s/slony1-2.html
Kind regards,
- --
Mehdi Dogguy مهدي الدڤي
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/L
xrdb. So, afaics, it needs to depend on x11-xserver-utils. I guess
setting "-e" helps...
I can file those issues seperately if preferred (and they would have
severity "serious").
I didn't inspect the package further. There might be more issues.
Regards,
--
Mehdi Dogguy
On 03/10/2012 06:40, Ian Wienand wrote:
On Tue, Oct 2, 2012 at 8:35 AM, gregor herrmann wrote:
Ian, if your busy I'm happy to upload the fix (if Mehdi is ok with
the diff).
Many thanks for looking into this. I'd be glad if you can upload; I
would only upload the same thing anyway.
1 - 100 of 492 matches
Mail list logo
