On 10/5/21 1:48 PM, Simon Ruderich wrote:
> Could you test the attached patch and tell me if this works for
> you for real builds?
Thankfully, I still had the full log file lying around in which I
originally discovered this issue, and I am indeed no longer getting
any false positives with your pat
-1.2.1/debian/changelog 2021-05-31 15:14:50.0 +0200
@@ -1,3 +1,10 @@
+backintime (1.2.1-3) unstable; urgency=medium
+
+ * Cherry-pick patch for #946349 from upstream Git repository
+(Closes: #946349).
+
+ -- Fabian Wolff Mon, 31 May 2021 15:14:50 +0200
+
backintime (1.2.1-2) unstable
-10-30 22:35:50.0 +0100
+++ backintime-1.2.1/debian/changelog 2021-05-31 15:14:50.0 +0200
@@ -1,3 +1,10 @@
+backintime (1.2.1-3) unstable; urgency=medium
+
+ * Cherry-pick patch for #946349 from upstream Git repository
+(Closes: #946349).
+
+ -- Fabian Wolff Mon, 31 May 2021 15:
Control: found -1 2.8.4-1
I've encountered a similar issue today:
Setting up linux-image-5.10.0-2-amd64 (5.10.9-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-1-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-1-amd64
I: /vmlinuz is now a symlink to boot
On 1/11/21 3:45 AM, Stuart Prescott wrote:
>> In any case, I've changed my upload to a QA upload now and reuploaded
>> it to Salsa and Mentors.
>
> I see bartm beat me to uploading it.
Are you sure? I didn't receive any emails about an upload, and the
tracker doesn't say anything about a recent u
Hi Stuart,
thanks for having a look at the package!
But no, I do not currently intend to adopt this package. I just
thought I'd try and help with the freeze preparation by fixing the RC
bug in this package.
The reason I created the repository in the Science Team area is that I
have write access
Package: sponsorship-requests
Severity: important
X-Debbugs-CC: woj...@gmail.com
Dear mentors,
I am looking for a sponsor for a non-maintainer upload for the 'xylib'
package.
The package currently suffers from RC bug #975672; in the bug
discussion, the current package maintainer has pointed out
On 11/28/20 10:47 PM, Eriberto wrote:
> Thanks Fabian and Simon!
>
> Considering that some false positives can't be fixed in blhc source
> code, could I close this bug?
I think it would make more sense to close this bug with the next
upstream release, given that some changes in blhc have been app
On 11/28/20 12:28 PM, Simon Ruderich wrote:
> blhc uses a few heuristics to detect lines with (possible)
> compiler commands to prevent false negatives. Lines containing
> `gcc` and similar are flagged. In this case the CC= environment
> variable triggers this. Then blhc looks for the actual build
Hi Eriberto,
thanks for your quick reply!
On 11/24/20 5:59 PM, Eriberto wrote:
> Since 0.12 version, blhc is able to ignore false positives spotted by
> line(s) "injected" inside .build file via debian/rules. See more
> details in blhc(1) manpage. There are examples in
> /usr/share/doc/blhc/READM
Package: sponsorship-requests
Severity: normal
Dear Mentors,
I am looking for a sponsor for a QA upload of the 'smlnj' package.
The Debian package has not been updated in four years except for minor
maintenance work. I have now packaged the latest upstream version,
110.98.1, which, most notably,
Package: blhc
Version: 0.12-2
Severity: normal
X-Debbugs-CC: si...@ruderich.org
Dear maintainer,
consider the following warnings emitted by blhc (line breaks are mine;
see the attached "test.log" file for an input that reproduces this
problem):
LDFLAGS missing (-Wl,-z,relro): make VERSION="v-am
And while we're at it, even though this is technically an unrelated
problem, it also has something to do with SMT solver versions: In the
autopkgtests control file [0], you have the following code:
Tests: why3+z3
Depends:why3, z3 (<< 4.8.7)
Restrictions: skip-not-installable
This is not a b
Source: cvc4
Version: 1.8-1
Severity: important
CVC4 1.8-1 fails to build on several release architectures due to a
few test case failures [0]. I have reported the issue upstream [1].
I am going to reupload the cvc4 package soon with the test cases in
question disabled, as a temporary solution, a
Package: why3
Severity: important
Dear maintainer,
this seems to be the same issue as #942344, just this time it's cvc4
instead of z3: share/provers-detection-data.conf lists CVC4 versions
up to 1.7, but the current version is 1.8, so the autopkgtests for
why3 fail.
Best regards,
Fabian
Hi,
so after four and a half years, the same issue still exists - when
building a package that uses CMake, I got a cache hit rate of zero.
After some investigation (I wasn't aware of this bug report), it
turned out that the issue was caused by the differing build paths, as
described in this bug re
Control: tags -1 + patch pending upstream confirmed fixed-upstream
On 6/19/20 6:51 PM, David Anderson wrote:
> I too reproduce the error.
>
> The relocation used was -not- one I was aware of.
> This diff fixes the problem. it should be on sourceforge
> in a day or two. I hope to create a new fu
Hi Nick,
thanks for reporting this; indeed, I could reproduce the error, and
llvm-dwarfdump
doesn't produce a similar error (unsurprisingly, if the file was generated with
LLVM in the first place).
I'm hereby forwarding your report to libdwarf's upstream developer - David,
could
you have a look
Hi Roland,
I totally understand your need for a more recent version of the FOX
toolkit. There has been very little upstream activity on the 1.6
("stable") branch in the last few years, and honestly, I don't know
why the 1.7 branch isn't yet considered stable or if/when this will
ever happen.
Howe
Hi Benjamin,
sorry for the very late reply, I kept putting it off...
Anyway, I have now set up a stable sbuild chroot and built z3 there, and, almost
surprisingly (and embarrassingly, because I waited so long to give it a try), it
built immediately, without me having to change anything, and the a
On 3/30/20 7:19 PM, Muammar El Khatib wrote:
> Does it seem you already got access?
>
> https://salsa.debian.org/debian/pulseaudio-dlna/-/commit/61d6ee13c13eb76cb6b70b6b50c2fb5efe04dc7f
Yeah, somebody (probably Adam -- thanks!) created the repository and gave
me the necessary access permissions t
Hi Adam and Muammar,
thanks for your quick replies! Adam, thank you for looking over my changes and
sponsoring the upload.
One more thing: As I said in my original email, I have a Git repository set up
for this package, but I don't have the necessary permissions to create a
repository in the "Deb
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: muam...@debian.org, sergi...@debian.org
Dear mentors,
I am looking for a sponsor for a NMU of the 'pulseaudio-dlna' package.
The package has been removed from testing because it's still using Python 2,
and there seems to be no recent u
Package: debci
Dear debci maintainers,
it seems to me that the information on ci.debian.net is often confusingly
out of date. For instance, I recently uploaded a new version of the z3
package, 4.8.7-4, which at the time of writing this bug report has already
migrated to testing:
https://web.ar
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: bba...@mit.edu, sergi...@debian.org
Dear mentors,
I am looking for a sponsor for an upload of the 'dafny' package.
There have been new upstream releases, I have fixed the two open RC
bugs for this package, enabled autopkgtest package t
Source: z3
Severity: wishlist
X-Debbugs-CC: hel...@subdivi.de
[discussion continued from #948763]
On 1/13/20 7:30 PM, Helmut Grohne wrote:
> Why is the libz3-java package "Architecture: any" (long list actually)
> instead of "Architecture: all"? Many lib*-java packages are
> "Architecture: all" i
Control: tags -1 pending
Hi Steve,
thanks for your patch! I have applied it in the Salsa repository:
https://salsa.debian.org/wolff-guest/dwarfutils/commit/ef186156885aef96d600c9c5c5d43eaba143ffb0
Since this issue doesn't look very urgent to me, I would simply wait
for the next regular uploa
On Mon, 13 Jan 2020 06:21:56 +0100 Helmut Grohne wrote:
> Source: z3
> Version: 4.8.7-3
> Severity: serious
>
> z3 cannot be built on buildds, because its Build-Depends cannot be
> satisfied on buildds. Failing to build on buildds is a serious problem.
It builds now on all but three architecture
On 1/11/20 12:02 PM, Aurelien Jarno wrote:
> I have just tried to build the current master branch natively on
> riscv64, it builds fine.
Great! I just pushed z3 4.8.7-3 to unstable, so let's hope everything
goes well.
Thanks again to all of you for your help with this!
On 1/10/20 6:50 PM, Ximin Luo wrote:
> Sorry. I changed it to -headless because it *usually* is sufficient for a
> java package, and it avoids installing extra unnecessary X libraries during
> the build. I tested this with version -2 and it worked fine before switching
> to cmake, so I don't kno
On 1/9/20 5:22 PM, Aurelien Jarno wrote:
> On 2020-01-09 14:18, Ximin Luo wrote:
>> So setting CMAKE_USE_PTHREADS might work.
>
> Yep, I confirm that works. In short with the following patch, z3 builds
> natively on riscv64:
Thanks for checking!
I was planning to upload the changes today, but bu
Thank you for your MR, Ximin!
Do you need anything else? I see you haven't added -pthread anywhere yet; is
this not necessary with CMake (maybe CMake adds it automatically?), and have
you tried building on/for riscv64 again to verify that it works now?
I've mostly finished porting the package to the CMake build system now, so
to avoid further confusion as to which parts of which patches should be
applied, what I would suggest is for you to just have a look at the Salsa
repository and port your patches so that I know precisely what changes you
nee
Thank you all for your patches and the ensuing discussion.
I am currently working on porting the z3 Debian package to use the
CMake build scripts; I think this will simplify things for all parties
involved now and in the future. In the process, I will drop the OCaml
bindings; they are currently br
Package: lintian
Severity: minor
The no-dh-sequencer tag should not be marked "certain", especially not
the way the check is implemented right now.
For instance, it breaks even for simple examples like this one:
%:
if [ $(WITH_JAVA) = yes ]; then \
dh $@ --with python3,ja
On 11/24/19 7:13 PM, Benjamin Barenblat wrote:
> As the current maintainer, I definitely do not object to this NMU (or
> any other NMUs associated with this package). Sponsors, please feel free
> to upload without delay.
Thanks. One more question: Upstream has switched to the Expat ("MIT/X11")
li
Thanks for reporting this bug.
It appears to me that the issue you're referring to might have been fixed by
this commit:
https://github.com/bit-team/backintime/commit/7795b40772c821805037664a559d96642b768391
Could you check again and confirm this, please? Then we could close this bug.
On We
bian/rules to make the new version build.
* Enable autopkgtest package testing, and add mccarthy-{91,92} tests.
* Update Vcs-Git and Vcs-Browser fields in debian/control.
-- Fabian Wolff Sat, 16 Nov 2019 19:16:48 +0100
The current maintainer is looking for someone to adopt the packag
On Mon, 30 Sep 2019 15:35:36 +0200 =?UTF-8?B?RnLDqWTDqXJpYw==?= Bonnard
wrote:
> Dear maintainer,
> is there any reason that cvc4 isn't build on "any" ?
> I tested ppc64 and ppc64el and it worked well.
Thanks for bringing this to my attention. Yes, there is a reason:
https://buildd.debian.org
19 9:48 PM, Dmitry Shachnev wrote:
> Hi Fabian!
>
> On Sun, Oct 27, 2019 at 06:28:26PM +0100, Fabian Wolff wrote:
>> Dear mentors,
>>
>> I am looking for a sponsor for an upload of the 'backintime' package.
>> [...]
>
> I would be happy to sponsor t
ate debian/copyright (Closes: #941984, #942155).
* Upgrade to Standards-Version 4.4.1 (no changes).
* Add additional backintime-qt_polkit.1.gz symlink to backintime.1.gz
to silence the binary-without-manpage Lintian warning.
-- Fabian Wolff Sat, 19 Oct 2019 23:21:22 +0200
The
Hi Ralf,
since I don't have an arm64 machine available to try this out myself: Could you
check whether this problem still exists in the current version of z3?
Your bug report refers to a quite old version of z3, so I'd say there is a good
chance that the issue has been fixed since then. If not, t
Package: why3
Severity: important
X-Debbugs-CC: pkg-llvm-t...@lists.alioth.debian.org
Dear maintainer,
in share/provers-detection-data.conf (in the why3 source tree), only z3 versions
up to 4.8.4 are listed as "version_ok". But the 4.8.4 release of z3 was almost
two years ago and has since been s
ld be better to unpackage said package version.
> Given that 4.8.6 is ready to be packaged thanks to the work of
> Fabian Wolff, it may be good to proceed with that.
thanks for pointing this out to me.
4.8.6 is ready and uploaded, but because it introduced the new python3-z3
package,
it's sti
rcor.de --allow z3
> Uploading commands file to ssh.upload.debian.org (incoming:
> /srv/upload.debian.org/UploadQueue/)
> Picking DM Fabian Wolff with fingerprint
> 4C22AB203E83493607A16E4480AD73734275BDAF
> SCP is deprecated. Please consider upgrading to SFTP.
> Uploading locutus-1
non-superficial test cases.
* Add -fPIC to DEB_CXXFLAGS_MAINT_APPEND in an attempt to fix #940266.
* Try to make the build more reproducible.
-- Fabian Wolff Sun, 29 Sep 2019 18:21:54 +0200
In particular, I've introduced the new python3-z3 package, so whoever decides to
spon
On 9/25/19 9:52 AM, Sylvestre Ledru wrote:
>
> Le 24/09/2019 à 16:41, Roman Lebedev a écrit :
>> On Tue, Sep 24, 2019 at 5:39 PM Fabian Wolff wrote:
>>>
>>> What are your thoughts on this?
>> I personally would not see dumping libz3-cil and libz3-ocaml-dev a
age prevents me from porting
>>> some other python2 software to python3.
>>
>> Thanks to the work of Fabian Wolff, we have a better version of z3.
> I'm a little bit out of context here, of *z3* or of z3 packaging?
> Also, link?
The z3 *package* was several years be
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for a QA upload of the eqonomize package.
The only change I made has been the introduction of a new upstream version.
The package can be found on Mentors, and my changes are also in the Git
repository on Sa
e, because upstream moved from
Qt 4 to Qt 5. Make backintime-qt4 a transitional package.
* Drop the transitional backintime-{gnome,kde} packages
(Closes: #939139, #939140).
-- Fabian Wolff Sat, 14 Sep 2019 14:36:13 +0200
The package is available on Mentors, and I have put my
Great, thank you!
Yes, I'm also hoping that the package will migrate quickly and smoothly. But
the results so far (e. g. it builds on all release architectures) look
promising!
On 9/4/19 12:24 PM, Gianfranco Costamagna wrote:
> git was already correct, I sponsored it!
>
> lets hope it migrates
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
/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 Tue, 27 Aug 2019 14:30:11
On 8/27/19 12:20 AM, Sergio Durigan Junior wrote:
> On Monday, August 26 2019, Fabian Wolff wrote:
>
>> Dear mentors,
>>
>> I am looking for a sponsor for a QA upload of the dbacl package.
>>
>> This upload attempts to fix a FTBFS bug (#916182), and I have also
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for a QA upload of the dbacl package.
This upload attempts to fix a FTBFS bug (#916182), and I have also performed
some standard package maintenance tasks.
I will push to the proper repository (in the Debia
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for a QA upload of the ffe package.
I have mainly imported a new upstream version and performed some standard
package maintenance tasks.
I will push to the proper repository (in the Debian group on Salsa) a
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for a QA upload of the aj-snapshot package.
I have mainly imported a new upstream version and performed some standard
package maintenance tasks.
I will push to the proper repository (in the Debian group on
maintenance tasks (Ondřej Nový pushed one commit to the Salsa
repository a while ago, so I've kept him in the changelog):
eqonomize (1.4.1-1) unstable; urgency=medium
* QA upload.
[ Ondřej Nový ]
* d/control: Fix wrong Vcs-*
[ Fabian Wolff ]
* New upstream re
upstream release.
* Upgrade to Standards-Version 4.4.0 (no changes).
* Upgrade to debhelper compat level 12.
-- Fabian Wolff Sun, 25 Aug 2019 23:56:47 +0200
These changes can be found on Salsa: https://salsa.debian.org/debian/doclifter
And I've also uploaded the package to Me
nformation of 02-sphinx-ext.patch.
+
+ -- Fabian Wolff Wed, 20 Mar 2019 20:37:02 +0100
+
+squirrel3 (3.1-6) unstable; urgency=medium
+
+ * Update Vcs-Git and Vcs-Browser fields in debian/control.
+ * Add patch 02-sphinx-ext.patch to disable the pngmath Sphinx
+extension (Closes: #923012).
Hi Andreas,
thanks so much for uploading those changes! I prepared them some time
ago, but unfortunately really didn't get around to uploading the
package, so I'm glad you took the initiative.
This is to let the Release Team know that I, as the package
maintainer, fully endorse this upload (in ca
Package: scala
Version: 2.11.12-4
Severity: important
Dear maintainer,
consider the following Scala script test.scala:
println("Hello, world!")
If I try to run
$ scala test.scala
I get the following output:
error: Compile server encountered fatal condition:
javax/tools/DiagnosticListe
Control: tags -1 + upstream
Dear Tj,
thanks for reporting this problem. I am hereby forwarding it to dwarfdump's
upstream developer, David Anderson.
David, could you have a look at this? Thank you!
Best regards, and happy holidays,
Fabian
On 12/20/18 10:18 PM, Tj wrote:
> Package: dwarfdump
>
Hi Jonathan,
On Fri, 29 Jun 2018 22:21:54 +0100, Jonathan Wiltshire wrote:
> Would you like to co-maintain? If so, please add yourself to uploaders and
> prepare a maintainer upload (rather than NMU). I added you to the
> repository members in anticipation.
Thanks. In principle, I'd be interested
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Dear Release Team,
I would hereby like to request a transition slot for libantlr3c.
The current version of libantlr3c in experimental, 3.4+dfsg-1,
includes a patch for the RC bug #90060
Hi,
since there has not been any progress on this for a while now, I have
decided to prepare a non-maintainer upload myself, including the
latest upstream release, 1.1.24, as well as some minor maintenance
work.
Jonathan, could you have a look at this? Of course I won't upload a
NMU without your
On Mon, May 14, 2018 at 08:10:24PM +0200, Tobias Frost wrote:
> On Mon, May 14, 2018 at 05:33:03PM +0200, Fabian Wolff wrote:
> > On Mon, May 14, 2018 at 11:03:58AM -0400, Sergio Durigan Junior wrote:
> > > Thanks! And yeah, I'd say it's OK to just start fro
On Mon, May 14, 2018 at 11:03:58AM -0400, Sergio Durigan Junior wrote:
> Thanks! And yeah, I'd say it's OK to just start from scracth in this
> case.
I have imported every version I found on snapshot.debian.org into the
repository, so at least some history is available now.
> Done:
>
> https:
On Sun, May 13, 2018 at 08:38:41PM -0400, Sergio Durigan Junior wrote:
> Have you considered moving this package to salsa? It'd be a shame to
> not have a VCS for it.
Sure, I can do that. The only problem is that since the Bazaar
repository is no longer reachable, I don't have the commit history.
changes).
* Upgrade debian/copyright to the machine-readable format.
* Delete trailing whitespace from debian/changelog in order to
silence the file-contains-trailing-whitespace Lintian tag.
* Add xmlto as a build dependency in debian/control.
-- Fabian Wolff Sun, 13 May 2018 15:38
ox-1.6-dev in
debian/control.
* Update debian/copyright.
* Remove trailing whitespace from debian/changelog and debian/control
in order to silence the file-contains-trailing-whitespace Lintian
tag.
-- Fabian Wolff Mon, 23 Apr 2018 21:32:14 +0200
The package is av
On Mon, Apr 30, 2018 at 08:27:02PM -0400, Sergio Durigan Junior wrote:
> Hm, I think you forgot to push the upstream/pristine-tar branches,
> because I can't rebuild the tarball here. Could you do that, please?
Are you sure? The upstream/5.5.0 tag seems to be available in the
Salsa repository:
On Mon, Apr 30, 2018 at 01:16:04PM -0400, Sergio Durigan Junior wrote:
> Thank to everybody who replied. Really appreciated.
>
> Fabian, I think it's OK if you just update the upstream project's
> copyright info, so I agree with the proposed modification you suggested
> above.
>
> Please let me
On Mon, Apr 30, 2018 at 12:24:42PM +0200, Steve Langasek wrote:
> I don't think you should be taking it upon yourself to add copyright
> statements regarding debian/ contents where authors have not asserted their
> copyright up front. There is precious little in debian/, outside of
> debian/patche
On Fri, Apr 27, 2018 at 12:47:12PM -0400, Sergio Durigan Junior wrote:
> I've uploaded the package now.
Great, thank you!
On Tue, Apr 24, 2018 at 10:55:00PM -0400, Sergio Durigan Junior wrote:
> Or you can also move the package under the Debian Python Modules Team
> umbrella, if it makes more sense. Packaging Python modules with the
> DPMT is the preferred way nowadays, but that's really up to you (and
> just to be c
/control and Source field in
debian/copyright to use HTTPS.
* Remove incorrect Multi-Arch fields in debian/control.
-- Fabian Wolff Fri, 27 Apr 2018 15:35:36 +0200
I have to admit that I'm not entirely sure about the Multi-Arch fields
that I removed. The link-grammar binary pa
On Mon, Apr 23, 2018 at 08:58:30PM -0400, Sergio Durigan Junior wrote:
> Hi Fabian,
>
> I can help with it, but there are two things I'd like to see first.
Thank you for your review!
> 1) There are no Vcs-* fields, and it's unclear to me where the git
> repository for the package is located (I c
uite field to debian/control.
* Upgrade to Standards-Version 4.1.4 (no changes).
* Upgrade to debhelper compat level 11 (no changes).
-- Fabian Wolff Mon, 23 Apr 2018 18:30:09 +0200
The package is available on Mentors:
https://mentors.debian.net/package/python-picklable-itertool
On Fri, Apr 13, 2018 at 09:19:41PM +0200, Tobias Frost wrote:
> Hi Fabian,
>
> LGTM, Uploading!
Great, thanks!
> (The only thing you could do is to file those patches upstream to get
> them included.)
Done. I probably should have done this right away.
Best regards,
Fabian
-fix-spelling.patch.
-- Fabian Wolff Mon, 02 Apr 2018 18:39:00 +0200
The package is available on Mentors:
https://mentors.debian.net/package/apparix
https://mentors.debian.net/debian/pool/main/a/apparix/apparix_11-062-1.dsc
Thank you!
Best regards,
Fabian
ntrol.
* Mark eqonomize-doc as Multi-Arch: foreign.
-- Fabian Wolff Mon, 02 Apr 2018 14:43:28 +0200
The package is available on Mentors:
https://mentors.debian.net/package/eqonomize
https://mentors.debian.net/debian/pool/main/e/eqonomize/eqonomize_1.2.0-1.dsc
Thank you!
Best regards,
Fabian
Lintian tag.
-- Fabian Wolff Sun, 01 Apr 2018 21:15:13 +0200
The package is available on Mentors:
https://mentors.debian.net/package/ffe
https://mentors.debian.net/debian/pool/main/f/ffe/ffe_0.3.8-1.dsc
Thank you!
Best regards,
Fabian
).
* Upgrade to Standards-Version 4.1.3 in debian/control (no changes).
* Add build dependency on libncurses-dev (Closes: #646734).
-- Fabian Wolff Sat, 31 Mar 2018 21:59:24 +0200
The package is available on Mentors:
https://mentors.debian.net/package/dbacl
https://mentors.debian.net
debian/control (no changes).
* Remove fixman.patch (fixed upstream).
* Add 00-fix-long-options.patch (Closes: #715625).
-- Fabian Wolff Sat, 31 Mar 2018 15:09:03 +0200
The package is available on Mentors:
https://mentors.debian.net/package/aj-snapshot
https://mentors.debian.net
Control: tags -1 + fixed-upstream
On Tue, Mar 27, 2018 at 10:02:25AM -0700, David Anderson wrote:
> code/dwarfdump/configure and code/libdwarf/configure
> now support cross building. see code/README.
That's good to hear.
Thank you very much for the effort you put into this!
tag 892053 pending
thanks
On Sun, Mar 04, 2018 at 04:24:57PM +, Matthew Lugg wrote:
> Dear Maintainer,
>
>When attempting to use a project which makes use of libtcod, I
>encountered the error `external/pstdint.h: No such file or
>directory`. This is an issue in libtcod_portability
tag 886989 pending
thanks
On Fri, Jan 12, 2018 at 03:38:31PM +0530, Chris Lamb wrote:
> Hi,
>
> Whilst working on the Reproducible Builds effort [0], we noticed
> that fox1.6 could not be built reproducibly.
>
> This is because the date call in debian/rules (which does use
> SOURCE_DATE_EPOCH -
-9998
+(Closes: #866968).
+
+ -- Fabian Wolff Tue, 11 Jul 2017 15:33:51 +0200
+
dwarfutils (20161124-1) unstable; urgency=medium
* New upstream release.
diff -Nru dwarfutils-20161124/debian/patches/02-fix-CVE-2017-9052.patch
dwarfutils-20161124/debian/patches/02-fix-CVE-2017-9052.patch
I am really sorry that this is taking so long, but I am still working
on this. In particular, at the recommendation of the upstream
developers, I have been waiting for version 1.5 of CVC4, which has
finally been released yesterday:
http://cvc4.cs.stanford.edu/web/2017/07/10/cvc4-1-5-released/
R
On Sun, Nov 20, 2016 at 05:31:40PM +0100, Daniel Stender wrote:
> I haven't discussed this yet with the ITP holder (busy), but as foreseeable
> sponsor and
> reporter of this bug I say that's all right. We could name the source package
> that way,
> no problem.
Sorry for the delay. Yes, of cours
On Sun, Oct 23, 2016 at 06:02:05PM +, Gianfranco Costamagna wrote:
> just a question, why aren't you packaging the Python2 version?
> (the question is that I would like to avoid another binNEW queue in case some
> other people asks for it)
In this document
https://www.debian.org/doc/packagi
one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/libt/libtcod/libtcod_1.6.1+dfsg-1.dsc
Regards,
Fabian Wolff
ols_0.1.1-1.dsc
Regards,
Fabian Wolff
Package: wnpp
Severity: wishlist
Owner: Fabian Wolff
* Package name: python-picklable-itertools
Version:: 0.1.1
Upstream Author : David Warde-Farley
* URL : https://github.com/mila-udem/picklable-itertools
* License:: Expat
Programming Lang: Python
Control: tags -1 + upstream patch fixed-upstream
Hi,
the following patch fixes this issue:
--- a/src/util/mpz.cpp
+++ b/src/util/mpz.cpp
@@ -134,7 +134,7 @@
#endif
mpz one(1);
-set(m_two64, UINT64_MAX);
+set(m_two64, static_cast(UINT64_MAX));
add(m_two64, one, m_two64);
Control: tags = patch fixed-upstream
Hi,
the issue here is that GCC 6 defaults to -std=gnu++14. Since C++11,
std::basic_ios no longer provides an implicit void* operator but only
an explicit bool operator. Therefore, the problem can be fixed with
this patch:
--- a/src/util/debug.cpp
+++ b/src/ut
x CVE-2016-5038.
+ * Add patch CVE-2016-5039.patch to fix CVE-2016-5039.
+ * Add patch CVE-2016-5042.patch to fix CVE-2016-5042.
+
+ -- Fabian Wolff Tue, 16 Aug 2016 15:27:35 +0200
+
dwarfutils (20120410-2) unstable; urgency=low
* Fix FTBFS on Debian GNU/Hurd by Barry deFreese
di
Control: owner -1 !
>From http://cs.nyu.edu/~mdeters/:
The Department of Computer Science regrets to inform you that
Morgan Deters passed away on Saturday, January 17, 2015.
To ensure progress with this package, I'm claiming this ITP. I am
already in contact with the upstream developers, s
Hi everybody,
On Sat, Jul 23, 2016 at 08:19:33AM +, Gianfranco Costamagna wrote:
> let me explain, we (Fabian to be honest) had to restrict the built binary
> packages only to some
> architectures, because -1 revision was failing somewhere.
Yes, the main issue was that mono, required to buil
1 - 100 of 120 matches
Mail list logo
