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:
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:
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:
Mon, Oct 29, 2018 at 4:48 AM Mehdi Dogguy wrote:
>>
>> Sorry for not replying sooner.
>>
>> On 2018-10-20 17:54, Brian Smith wrote:
>> > The change is in psm2_hal.c. It is a brand new file. Reference the
>> > initialization loop at line 246.
>> >
Sorry for not replying sooner.
On 2018-10-20 17:54, Brian Smith wrote:
The change is in psm2_hal.c. It is a brand new file. Reference the
initialization loop at line 246.
Indeed. The solution described in the github issue looks very fine.
Why not uploading it in Debian? It will solve a real
On 2018-10-19 19:53, Brian Smith wrote:
The problem occurs when the OFI psm2 provider invokes psm2_init() when
there are no hfi1 devices present on the system. The call chain
eventually invokes hfi1_wait_for_device() with a timeout of 0. That is
interpreted as 15000ms.
Actually, that part of
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:
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:
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
On 2018-08-23 13:36, rjbou wrote:
Package: opam
Version: 1.2.0-1+deb8u1
Severity: grave
Justification: renders package unusable
Tags: jessie
Dear Maintainer,
On jessie, opam 1.2.0 is packaged but it is officially deprecated since
a year [1][2].
It makes opam unusable for jessie users: already
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
Hi Andy,
On 2018-05-25 08:40, Andy Li wrote:
I've a patch:
https://github.com/ocaml/opam/compare/1.2.2...andyli:1.2.2-fix.patch
It's based on the discussion with upstream at
https://discuss.ocaml.org/t/the-forever-beta-issue/1779/6
In fact, the patch introduces a bug and makes the build fail
Hi Andy,
On 2018-05-25 08:40, Andy Li wrote:
I've a patch:
https://github.com/ocaml/opam/compare/1.2.2...andyli:1.2.2-fix.patch
That's great!
FWIW, I've opened this bug report so that Opam doesn't migrate to
testing before being fixed or updated to a newer version. I have
the feeling that
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, [
Hi,
Thank you for this report.
On 12/08/2017 09:33, Adrian Bunk wrote:
> configure: ***
> configure: * CONFIGURE TOOLS AND LIBRARIES USED BY SOME PLUG-INS *
> configure: ***
> Ocamlfind ->
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 <trei...@free.fr>
>> wrote:
>>> Hi C
Control: reassign -1 src:ocaml
Control: merge 837359 -1
Control: affects -1 src:ocamlgraph
Hi,
On 24/10/2016 19:04, Adrian Bunk wrote:
> Control: rassagn -1 src:ocamlgraph
> Control: affects -1 src:frama-c
> Control: retitle -1 ocamlgraph needs PIE binNMU
>
> A binNMU is sufficient to fix this,
Hi,
On 02/11/2016 03:22, Ximin Luo wrote:
>
> let emit_load_symbol_addr dst s = if !Clflags.pic_code then begin [..] end
> else if !arch > ARMv6 && not !Clflags.dlcode && !fastcode_flag then begin `
> movw {emit_reg dst}, #:lower16:{emit_symbol s}\n`; ` movt{emit_reg dst},
>
explib-ocaml-dev provide 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
from experimental.
>
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
Hi,
On 2016-11-03 01:32, Karl Kornel wrote:
Unfortunately, I don’t think your patch would be able to work
directly, because the quilt build process requires that the original
code be untouched; all of the changes to source have to be Quilt
patches. So, I’ve taken your patch and converted it
ource distribution unstable
dpkg-buildpackage: info: source changed by Mehdi Dogguy <me...@debian.org>
dpkg-source --before-build parmap
dpkg-source: info: applying 0001-Update-version-number-in-various-places.patch
fakeroot debian/rules clean
dh --with ocaml clean
dh: Compatibility levels
Hi Johannes,
On 01/11/2016 08:04, Johannes Schauer wrote:
> Package: libdose3-ocaml-dev
> Version: 5.0.1-6
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> libdose3-ocaml-dev in unstable depends on
> libocamlgraph-ocaml-dev-i0qi0:amd64. This is provided by
>
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 <me
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 expre
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
Control: forcemerge 813459 818331
Hi,
On 16/03/2016 02:13, Martin Michlmayr wrote:
> Package: aac-tactics
> Version: 0.4-5
> Severity: serious
>
> This package fails to build in unstable:
>
>> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
> ...
>> make[4]: Entering
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:
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
>
Bonjour,
On 11/01/2016 08:39, Nathael Pajani wrote:
> Hi !
>
> What a nice way to resolve a bug or segfault. None of my students
> ever tried this one yet.
>
> Should remember it next time someone requests tech support for one of
> my products.
>
I am not sure this message helps anything in
Hi,
On 10/01/2016 02:19, Ashley Hooper wrote:
>
> Is there any reason the Jessie versions couldn't be retained in
> Stretch instead of the broken unison2.32.52 version?
>
We do not support multiple OCaml versions in the archive. As long
as that holds true, Unison <2.48 won't work with OCaml
Hello,
On 09/01/2016 03:31, Ashley Hooper wrote:
> Is it at all feasible to downgrade the installed version of ocaml
> 4.01.x on Stretch? I am reliant on Unison 2.32 (due to that being the
> most recent version available for another device I use).
>
> I'm only seeing the 4.02 version available
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 compatibility
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
Hi,
On 29/12/2015 11:13, Alexander Wirt wrote:
> On Tue, 29 Dec 2015, Alexandre Rossi wrote:
>
>> Hi,
>>
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
Hello,
On 29/12/2015 12:44, Hendrik Tews wrote:
> Mehdi Dogguy <me...@dogguy.org> 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 warnin
Hi Hendrik,
On 08/11/2015 20:58, Hendrik Tews wrote:
> Hi,
>
> it's a pattern matching failure in tag_module_type, which means
> the file stdLabels.mli contains some module type that I didn't
> know about when I wrote tag_module_type.
>
> As a quick solution you can add a catch-all line
>
>
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
Hi,
On 07/12/2015 16:23, Stéphane Glondu wrote:
>
> 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 compatibility with
> previous Debian releases, but
Package: src:matita
Version: 0.99.1-3
Severity: serious
Dear Maintainer,
Your package fails to build from source. Here is an excerpt from the
build
log:
OCAMLOPT nCic.ml
File "nCic.ml", line 142, characters 11-460:
Error: This class type should be virtual.
The following variables
Package: src:botch
Version: 0.16-2
Severity: serious
Dear Maintainer,
Your package fails to build from source. Here is an excerpt from the
build
log:
-Provides: myspell-dictionary, myspell-dictionary-en,
myspell-dictionary-en-za
-Depends: dictionaries-common (>= 0.10) |
/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: source changed by Mehdi Dogguy <me...@debian.org>
d
missing.
This doesn't seem to be a regression though.
Regards,
--
Mehdi Dogguy
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
.
This 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
::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
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
.
std:string exposed in public API. Packages needs a renaming.
Regards,
--
Mehdi Dogguy
::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
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
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
case, there are some uses of std::string exposed in the public
API. So this package needs fixing.
Regards,
--
Mehdi Dogguy
.
This 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
.
There 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
that there are no reverse dependencies.
--
Mehdi Dogguy
has std::liststd::string 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
low popcon.
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
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-requ...@lists.debian.org
with a subject
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
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
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
Le 2015-02-16 23:09, Hilko Bengen a écrit :
* Julien Cristau:
1. Override upstream's decision to change the SONAME with every
release.
I am not entirelysure how stable libhtp's API/ABI should be
considered -- looking at changes and deciding on compatibility
issues
making those
Hi Adam,
Thanks for adding the tag and for the unblock!
Le 2014-11-26 20:08, Adam D. Barratt a écrit :
I'm not sure acceptable is really the right word, and I've argued
with
myself a bunch over this, particularly given that sinfo+slurm-llnl is
basically a closed set for dependency purposes,
Le 2014-11-27 12:25, Francois Marier a écrit :
Package: develock-el
Version: 0.39-1
Severity: grave
Justification: renders package unusable
This package completely breaks the standard emacs c++ mode.
I can agree that the package can be of no interest for you when
it breaks the C++ mode, but
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
with a subject of
Le 2014-11-08 10:53, Adam D. Barratt a écrit :
Control: reopen -1
On 2014-11-06 10:21, Gennaro Oliva wrote:
Source: slurm-llnl
Source-Version: 14.03.9-4
We believe that the bug you reported is fixed in the latest version
of
slurm-llnl, which is due to be installed in the Debian FTP archive.
Control: reassign 764441 sinfo
Control: fixed 764441 0.0.47-2
Le 2014-10-11 23:58, Gaudenz Steinlin a écrit :
Hi
Mehdi Dogguy me...@dogguy.org 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
Le 2014-10-12 22:59, Gaudenz Steinlin a écrit :
Hi
Mehdi Dogguy me...@dogguy.org 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 me...@dogguy.org writes:
Le 2014-10-09 22:55, Gaudenz Steinlin a écrit
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. But as the Conflict was a workaround
from
the begining I'd prefer a solution where we agree on different names
for
the commands instead.
I very
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-rc-requ...@lists.debian.org
with a subject of unsubscribe
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 failures. Thus, I'm
Hi,
Le 2014-06-28 02:01, Michael Tautschnig a écrit :
Package: oasis
Version: 0.4.4-2
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using
cowbuilder
and pbuilder) the build failed with the following error.
[...]
expected: Exited with code
Le 2014-06-15 18:58, Michael Tautschnig a écrit :
It seems that those depended-on packages don't even exist anymore.
Maybe a
BinNMU is all that is needed, but I'm quite surprised how these
dependencies
ever came about.
A new upstream release of ocaml-deriving-ocsigen has been uploaded
Control: tag 749863 + pending
Hi,
Le 2014-05-30 12:10, Michael Tautschnig a écrit :
Presumably the ocaml sources have changed? (The buildds used ocaml
4.01.0-3, but
the archive now has 4.01.0-4.)
It seems that the last patch from OCaml depends on an another patch (in
the queue).
So, the
Le 2014-05-07 21:51, Peter Michael Green a écrit :
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.
Am I correct in thinking that means that the binnmus for dose3 should
be given back?
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
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. Trouble? Contact
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
Le 2013-11-26 08:01, Johan Gronqvist a écrit :
* What led up to the situation?
The package frama-c was updated to a new upstream version in
sid, but the versioned dependency in frama-c was not updated, which
makes the package why uninstallable in sid on amd64 (and others).
* What
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
On 03/29/2013 03:41 PM, John Paul Adrian Glaubitz wrote:
On 03/29/2013 03:38 PM, Christoph Egger wrote:
Because in unstable/wheezy python depends on python2.7 not python2.6. if
you depend on python you can assume /usr/bin/python but not either of
python2.6 and python2.7
Ah, you're right.
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.
Best,
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ
-fhs-run
[...] Packages must not include files or directories under /run, or
under the older /var/run and /var/lock paths. [...]
It is not RC though. And concerning its init script, it takes care of
creating /var/run/icinga if not present before launching the daemon?
Regards,
--
Mehdi Dogguy
://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/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
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
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...@lists.debian.org
with a subject
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
fix the problem, however, I haven't tried it, and I haven't
-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
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
anyway.
Thanks for both of you. You can go ahead with the upload. It will
probably be better to use 7.2~alpha5+cvs20101124-1+deb7u0 as version
number.
Regards,
--
Mehdi Dogguy مهدي الدڤي
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe
uploaded, no?
See [1] for the relevant change.
[1]
http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gnome-shell/debian/gnome-shell.gsettings-override?r1=35528r2=35762
Regards,
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
:) It seems that #632604 and sid's
libatomic-ops cannot be unblocked for Wheezy (due to very large changes
in its codebase). Could you please prepare an upload targetting
testing-proposed-updates?
Regards.
--
Mehdi Dogguy مهدي الدڤي
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ
seem all working yet. Since we cannot accept large
changes anymore, I think the best option is to postpone this bug for
Jessie. (Note: Moritz (CC'ed) said on IRC that he is okay with this plan).
Regards,
--
Mehdi Dogguy مهدي الدڤي
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
On 27/09/2012 14:15, Mehdi Dogguy wrote:
… was uploaded to stable-security-updates.
err, in stable-security.
--
Mehdi Dogguy مهدي الدڤي
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
,
--
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 19/09/2012 16:29, gregor herrmann wrote:
- a binary package libgdal-ruby (meta package depending on
libgdal-ruby1.8)
Hmpf… Sorry, I missed this point. I checked the list of packages on the
PTS and didn't try to analyze inter-packages relations further.
Regards,
--
Mehdi Dogguy
On 17/09/2012 15:49, Ritesh Raj Sarraf wrote:
Given the freeze, I am not hopeful of it getting in for Wheezy.
Doesn't look so awful to not be unblocked. Why do you think the
contrary? (It still needs to be acked by -boot folks though)
--
Mehdi Dogguy
--
To UNSUBSCRIBE, email to debian-bugs
1 - 100 of 461 matches
Mail list logo
