[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#935900: marked as done (RFS: z3/4.8.4-0.1 -- theorem prover from Microsoft Research)

Your message dated Wed, 4 Sep 2019 10:24:40 +0000 (UTC)
with message-id <91655504.3484560.1567592680388@mail.yahoo.com>
and subject line Re: Bug#935900: RFS: z3 4.8.4-0.1 [NMU]
has caused the Debian Bug report #935900,
regarding RFS: z3/4.8.4-0.1 -- theorem prover from Microsoft Research
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

935900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935900
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: mt@debian.org
X-Debbugs-CC: locutusofborg@debian.org

Dear mentors,

I am looking for a sponsor for a non-maintainer upload of the z3 package.

The z3 package is several years out of date (see #909494), and it is maintained in a packaging team anyways, so I think a NMU is warranted here to finally get the package back into shape.

My changes are summarized in the latest changelog entry:

  z3 (4.8.4-0.1) unstable; urgency=medium

    * Non-maintainer upload.
    * New upstream release (Closes: #909494).
    * Add debian/gbp.conf.
    * Update and reorganize patches.
    * Upgrade to debhelper compat level 12.
    * Upgrade to Standards-Version 4.4.0 (no changes).
    * Remove trailing whitespace from debian/control.
    * Build-Depend on libnum-ocaml-dev (Closes: #934048).

   -- Fabian Wolff <fabi.wolff@arcor.de>  Tue, 27 Aug 2019 14:30:11 +0200

My changes can be found on Salsa, and I will create a Merge Request referencing this RFS soon: https://salsa.debian.org/wolff-guest/z3

The package is also available on Mentors: https://mentors.debian.net/package/z3

Thanks for your help!

Best regards,

--- End Message ---
--- Begin Message ---
git was already correct, I sponsored it!

lets hope it migrates fast in testing, I also added some tweak in rules file and changed a little bit changelog

thanks for your contribution to Debian!


Il martedì 3 settembre 2019, 16:27:25 CEST, Gianfranco Costamagna <locutusofborg@debian.org> ha scritto:

control: owner -1 !
control: tags -1 moreinfo
Hello Fabian,

I tried many times to update it, would you mind pushing your work directly on the pkg-llvm repository?

In the meanwhile I'm having a look at your work

Il martedì 27 agosto 2019, 19:39:28 CEST, Matthew Fernandez <matthew.fernandez@gmail.com> ha scritto:

On Aug 27, 2019, at 08:48, Fabian Wolff <fabi.wolff@arcor.de> wrote:

On 8/27/19 4:00 PM, Matthew Fernandez wrote:
z3 (4.8.4-0.1) unstable; urgency=medium

I am not a z3 dev, but the latest z3 release is 4.8.5. Is there a
particular motivation for uploading a 4.8.4-based release?

Thanks for pointing this out; I did not notice this, because I was
using uscan, and upstream suddenly changed the tag format on Github for
tagging new releases:


Ah, I was not aware of this either, so we both learned something :)

In the last hour or so, I have tried to import version 4.8.5, but they
apparently changed something in the build system so that building with
Mono no longer works (it fails with 'dotnet: Command not found', and I
don't know what the Mono equivalent of the dotnet command is, or if one
exists at all).

I’ve built 4.8.5 before, but not the .net bindings which I guess is what you’re dealing with. I can attempt this but unfortunately won’t have time in the short term.

So, I'd say having version 4.8.4 is still better than 4.4.1, and if
someone else wants to give 4.8.5 another try in the future, they can do
so after this upload.

Agreed. Having 4.8.4 available would be a significant improvement. Thanks!

--- End Message ---

Reply to: