Hi
I'm responsible for this error (as you can see in the po file).
But I'll have to correct you: The problem here isn't the bad ss/ß
orthography, but the fact that I misnamed the translation de.po
instead of de_CH.po.
I don't know anything about the sharp s rules, as it's not taught/
used
Package: python-renpy
Version: 6.15.7-1
Severity: important
Tags: patch
Dear Maintainer,
renpy 6.15.7-1, as built for and installed under Debian jessie, is almost
unusable to play games. This has been tested with Katawa Shoujo and some Winter
Wolves games.
It produces tons of error messages on
Sorry, the patch was bogus. I missed a comma.
A corrected patch is attached.
diff --git a/debian/changelog b/debian/changelog
index 8771a73..48372d4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+renpy (6.15.7-2) unstable; urgency=low
+
+ [ Gregor Riepl ]
+ * Added
Package: renpy
Version: 6.15.7-1
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
I recently submitted a tiny patch to fix a libavresample problem (#732333).
While testing the changes, I discovered that a build
Package: beignet
Version: 0.3-1
Severity: wishlist
Tags: upstream
Dear Maintainer,
beignet is still under heavy development and new releases are provided in quick
succession, fixing many bugs and implementing missing functionality.
The current version in Debian jessie and sid (0.3) does work for
On 08/04/14 18:32, Kurt Roeckx wrote:
jessie is still vulnerable at 1.0.1f-1.
jessie has 1.0.1g-1 already, which should fix it.
Thank you, it just took a little longer for the package to hit my mirror.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Package: chirp
Version: 0.3.1-3
Severity: wishlist
Dear Maintainer,
There is a new version of chirp available on the project homepage: 0.4.0,
released on 24 March 2014.
Please update the Debian package.
Thank you.
-- System Information:
Debian Release: jessie/sid
APT prefers stable
APT
It seems the feature is broken again in 24.5.0esr-1~deb7u1.
I have all the packages suggested above(*) and some more installed, but
Youtube reports no H.264 support. It worked before the last update.
lib264-123 and libx264-142 are installed as well, but I'm almost certain
they don't help. libx264
I found the reason why it's not working any more:
Should I report this as a new bug, a regression to be precise, or keep
it here and hope that gstreamer support will be fixed/updated and
re-enabled in the future?
iceweasel (24.5.0esr-1) unstable; urgency=medium
* New upstream release.
*
Package: iceweasel
Version: 24.5.0esr-1~deb7u1
Severity: normal
Dear Maintainer,
According to the package changelog
(http://metadata.ftp-master.debian.org/changelogs//main/i/iceweasel/iceweasel_24.5.0esr-1_changelog),
gstreamer0.10 support was disabled in iceweasel 24.5.0esr-1. The reason given
Package: libjgrapht0.8-java
Version: 0.8.3-4
Severity: normal
Dear Maintainer,
In December 2013, a new version of JGraphT was released: 0.9
Please create a package for the new version.
At the same time, I'd also like to request the removal of the dependency on
libjgraph-java (JGraph), which is
Is there an update on the packaging status of alsa-firmware, or integration
into linux-firmware-nonfree?
This RFP was reported more than 3 years ago, yet firmware images for certain
audio devices are still missing in Debian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Package: kicad-common
Version: 0.20131208+bzr4024-1
Severity: important
Dear Maintainer,
KiCAD has undergone a lot of changes lately, and the format of footprint files
was changed.
From what I can tell, the old .mod format is still supported, but it is
suggested to migrate to the new .pretty
Package: gdb
Version: 7.7.1+dfsg-5
Severity: important
Tags: upstream
Dear Maintainer,
I noticed a bug in the C++ demangler of GDB 7.7, that causes it to segfault
when debugging certain binaries. GDB 7.4 in wheezy does not have this bug, so
downgrading helps in my case.
The bug is known
I think this bug should be reopened and not closed as WONTFIX.
The suggested workaround with /etc/kernel-img.conf doesn't seem to work, and
implementing some extra logic to support filesystems without hardlinks
shouldn't be too difficult.
Why not just create a copy instead if hardlinking fails?
It seems avr-libc 1.8.1 will not build with gcc 4.8.1, but vanilla gcc 4.9.1
works fine. I rolled my own .debs from the regular Debian gcc-4.9.1 sources
and vanilla 1.8.1 from the project website.
As I understand, the AVR toolchain on Debian is built from Atmel sources, but
these are currently
However, there is a version 3.4.5 release of the Atmel sources which
we should upgrade to. It's still based on gcc 4.8.1 though.
Yes, I tried to build avr-libc 1.8.1 with that first, but it doesn't contain
some vital patches that are in gcc 4.9.1. Those patches actually come from
Atmel
Package: avr-libc
Version: 1:1.8.0+Atmel3.4.4-1
Severity: wishlist
Dear Maintainer,
The version of avr-libc currently available in Debian testing/unstable is quite
old (from 2011) and lacks certain features.
Please upgrade the package to 1.8.1, which was released in 2014.
Thank you.
--
Package: libfont-freetype-perl
Version: 0.03-2+b1
Severity: wishlist
Dear Maintainer,
Please upgrade the Perl package to the current version, 0.05.
0.04 and 0.05 were released recently (Dec 2014 and Jan 2015 respectively),
after a long break.
Thank you.
-- System Information:
Debian
Actually, that was the easy part. Except for a custom built
grub-efi-i386 and some manual fiddling to find the install disc, I
didn't need to do anything.
Right, OK. Not exactly a common trail, then. :-)
Well, brand new hardware that just works is relatively rare.
I just happen to value
So, after a weekend of playing with this device[1], I conclude:
- Debian 8 multiarch DVD includes everything necessary for a working OS
installation.
- To install a full Desktop environment (i.e. Gnome), an internet connection
is still required.
- Installing a 64bit OS with 32bit Grub is
Package: grub-efi-ia32-bin
Version: 2.02~beta2-22
Severity: important
Tags: d-i
Dear Maintainer,
When installing Debian 8 on a system with a x86_64 CPU, but with a 32bit UEFI,
debian-installer correctly identifies the system as requiring a 32bit EFI Grub,
and thus tries to install
Hi Steve
This is actually the responsibility of the debian-cd package,
reassigning.
I did not know that, thank you.
reportbug has a debian-installer flag, I assumed it was for this purpose.
I'm the guy who's done the work for the mixed-EFI case here. How did
you get the amd64 installer DVD
Package: plasma-workspace
Version: 4:5.4.2-1
Severity: grave
File: /usr/bin/plasmashell
Justification: renders package unusable
Dear Maintainer,
After the latest KDE version bump (4:15.08.2-1), some critical KDE components,
including plasmashell, segfault on startup, making KDE almost completely
I see the same crash since my last package upgrade (today).
And it affects not just kate, but _all_ of KDE 5: plasmashell, sddm, konsole,
you name it. The crashes produce different backtraces sometimes, but in
general, it happens after xcb_intern_atom or XInternAtoms. konsole still uses
KDE
It looks like downgrading qt5x11extras as described in #802811 fixed the crash
for all affected KDE applications in my case.
If Kyanos confirms, I think this bug can be closed.
> Sorry, I rephrase: Kicad 4.0.0~rc1 is *not* installable in a Jessie
> environment now, as long as you want to keep other packages qui depend on
> libc prior to gcc-5.
Ah, that makes more sense.
I was only testing on stretch, where things are (mostly) settled in favor of
gcc5 AFAIK. Does jessie
Package: wnpp
Severity: wishlist
* Package name: steamcmd
Version : unknown
Upstream Author : unknown
* URL : https://developer.valvesoftware.com/wiki/SteamCMD
* License : Proprietary
Programming Lang: unknown
Description : CLI version of Valve's Steam
> I shall upload the fixed revision soon, and include your hints.
Ok, so I got kicad-4.0.0~rc1 from the package server today.
There's one thing I noticed: Version information seems to be missing.
The project window title shows "no-vcs-found-product".
I believe there's a script that generates
Hi Georges and everyone else.
I'm sorry that I left the discussion, I didn't see that it was moved to a
different bug report (which I wasn't subscribed to). Sorry.
> Also, where are your latest scripts located? Someone linked
> https://github.com/onitake/kicad.debian at one time on the list, but
Hi Bas
>> - UI plugins (_cvpcb.kiface, _eeschema.kiface, _gerbview.kifacem
>> _pcb_calculator.kiface, _pcbnew.kifacem _pl_editor.kiface) are currently
>> installed to /usr/bin. Should I report this upstream and request they be
>> installed to /usr/lib/kicad instead? Or write a patch specifically
>>> Yes, both. Report upstream and patch it in Debian until they fix it.
>>> /usr/bin should only contain executables, nothing else.
>
>> I reported the problem upstream, but it looks like it will be addressed
>> post-release as it's not a critical issue.
>
> I agree. But it should be fixed in
>> I had kde-full installed, however.
>> Shouldn't libkf5wallet-bin be a dependency of that?
>>
>> In any case, thanks. kwallet is working now, except that I'm struggling
>> with
>> the wallet migration wizard. But that's a different story.
>
> That answers if it's packaging or upstream.
>
> Do
> The protocol definitions for Xinput are incomplete and buggy in 1.11.
> That's why it is disabled by default.
I see. I thought that XCB-Xinput has matured well enough and was made
available to the general public (tm) by now. Guess I was wrong.
> In the next major release (1.12), the Xinput
Package: kicad
Severity: wishlist
According to https://lists.launchpad.net/kicad-developers/msg20319.html a new
stable release of KiCAD is imminent, and release candidate work will happen on
https://code.launchpad.net/~stambaughw/kicad/4.0
As far as I can tell, there a number of important
> - Documentation and Libraries: Both were previously moved to their separate
> projects, but they don't seem to be built/installed as part of the regular
> kicad build procedure any more. It may be necessary to write explicit
> installation rules or build them as separate packages.
I have to
I am currently on stretch, and beignet-opencl-icd is not installable without
removing a bunch of other packages, as reported for sid here.
However, I noticed that it's possible to build beignet against libclang1-3.5
from sid, as that links against libllvm3.5v5. libclang1-3.5 version 1:3.5.2-1
Hi Georges
> many people are eager to have a package of the so long awaited stable
> version of Kicad in Debian. I am currently the maintainer of this
> package.
>
> unfortunately, this event happens when I have an increase of business: I
> work as a teacher in France, and now is a tought
stretch is currently lacking a package for kde-config-tablet, as wacomtablet
is still being ported to KF5. I tried building the package from git, but was
hit by a missing xcb-xinit.
Please add --enable-xinput to the libxcb build settings and create
libxcb-xinput and libxcb-xinput-dev packages.
Package: kde-runtime
Version: 4:15.08.0-2
Severity: important
Dear Maintainer,
kwallet-kf5 seems to be mostly unusable due to a lack of the corresponding
service file. Both kde-runtime and kwalletmanager are installed, but trying to
use any application that uses the wallet results in the
> If you're running pure stretch (not a stretch+sid mix), that probably *isn't*
> this bug, as stretch only has the non-v5 version of libllvm3.5/libclang1-3.5,
> and packages using the v5 version (e.g. new versions of mesa) are hence not
> allowed to enter stretch.
>
> #797917 occurs on using
> If you're running pure stretch (not a stretch+sid mix), that probably *isn't*
> this bug, as stretch only has the non-v5 version of libllvm3.5/libclang1-3.5,
> and packages using the v5 version (e.g. new versions of mesa) are hence not
> allowed to enter stretch.
Thanks for pointing me in the
> kde-runtime has only the KDE4 version of kwallet (kwalletd). The Plasma 5
> version is in libkf5wallet-bin. Do you have that installed?
Nope, I didn't.
I had kde-full installed, however.
Shouldn't libkf5wallet-bin be a dependency of that?
In any case, thanks. kwallet is working now, except
Thanks to the latest patches by the kicad-doc team, both parallel builds and
installation into the correct destination of the docs are now working.
I also fixed two problems with my debian/rules that prevented parallel builds.
And, most importantly, I updated get-kicad.sh to fetch and build a
Oh, and I forgot something:
- File a bug report upstream to fix this when building against external boost:
dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/kicad/usr/bin/_pcb_calculator.kiface debian/kicad/usr/bin/eeschema
debian/kicad/usr/bin/_pcbnew.kiface
I created a public repository to track my packaging effort:
https://github.com/onitake/kicad.debian
You can use the updated get-kicad.sh to fetch the various source repos.
The package build scripts work too, but there still some open questions.
Will post a list later.
Package: ffmpegthumbs
Version: 4:15.07.90-1
Severity: important
Dear Maintainer,
The ffmpegthumbs (and also mplayerthumbs) packages used to provide thumbnails
for video files in Dolphin.
With the transition to KDE Frameworks 5 in progress, they stopped working,
apparently because they are only
Did you make any progress on packaging calendarserver?
I saw that 5.2.2 is in sid, but neither jessie nor stretch have it.
Your git server seems to be down, by the way.
Can you post your (packed) debian/ here instead?
> The doc source is available at https://github.com/kicad/kicad-doc
>
> It takes quite some time to build with asciidoc, so you might want to
> fetch the precompiled docs from http://docs.kicad-pcb.org/
Thanks, Nick.
I'm not strongly familiar with the DFSG rules concerning documentation, but I
>> More importantly, how do all these sub-packages tie into the build process?
>> I assume that the main kicad CMakeFiles will only build kicad itself, and not
>> pick up additional subdirectories like kicad-i18n, kicad-doc, kicad-library
>> or
>> library-repos. The current Debian packaging
>> The existing build process is slightly quirky.
>> First, it executes cmake, make and make install in the main kicad source
>> tree.
>> This will build kicad for a /usr/local/bin prefix (I want to change that
>> later), then install it into a temp dir.
>
> Why don't you use
Package: sddm
Version: 0.12.0-1
Severity: important
Dear Maintainer,
since switching from kdm to sddm, I get a "Authentication is required to
suspend the system" dialog whenever I close the lid of my laptop, press the
suspend button or execute suspend/hibernate from the KDE menu.
This prevents
> Just for your information. The old kicad doc bzr repo,
> https://code.launchpad.net/~kicad-developers/kicad/doc is not to be
> used any more. The translations have moved to
> https://github.com/KiCad/kicad-i18n/
Thanks, I'll use that.
But the repository only contains the .po files.
Where can I
Hi Matt
> Going by the current blockages due to the GCC5 transition, even if you
> had it packaged now, it wouldn't be available!
>
> Thanks for letting us know that you hope to start work on it soon. Let
> us know if there is testing or other things we could do to help.
It looks like the
I tested the new features of KiCad 4.0 quite extensively and found some
problems with the avoid & shove code. It crashes quite frequently when there
are lots of obstacles.
To debug these, it would be great to have kicad-dbg package with debugging
symbols.
I tried to build one myself, but the
Package: plasma-nm
Version: 4:5.6.4-2
Severity: normal
Tags: upstream
Dear Maintainer,
After enabling my mobile broadband modem (Ericsson H5321gw) from the plasma-nm
checkbox, the connections tied to it are not shown in the "Networks" popup and
disabled (i.e. can't connect from there, but
> There has not been any activity on the upstream bug[2] in the last three
> months, so I wonder whether a "proper upstream fix" actually exists yet.
It seems there's still no fix, but Michael reverted the change in the latest
package version (2.40.13-3): [1]
* Restore
Package: kio
Version: 5.16.0-1
Severity: important
Tags: newcomer
Dear Maintainer,
kioexec from kio 5.16 has a bug that causes Dolphin to freeze when opening
remote files in an external editor.
The bug was fixed in kio 5.17, according to the upstream bug report:
Package: plasma-workspace
Version: 4:5.6.5.1-1
Severity: important
Dear Maintainer,
After the last KDE package upgrade in Debian stretch (about a week ago), right
click on the workspace has suddenly stopped working.
Most applications and certain notification area icons still respond, but the
Package: firmware-ipw2x00
Version: 20160110-1
Severity: important
Tags: newcomer
Dear Maintainer,
The firmware-ipw2x00 package in Debian stretch contains firmware for
Intel Wireless Pro 2100/2200 devices, but the firmware does not match
what the driver in kernel 4.6 requires.
The package has
Package: kdelibs5-dev
Version: 4:4.14.21-1
Severity: normal
Tags: patch
Dear Maintainer,
The cmake script FindQCA2.cmake does not detect the Qt5 version of libqca2.
This patch (against a different package, but the content is the same, AFAICT)
should fix this:
Are you certain this is the same bug?
Control: merge -1 818971
818971 discusses general compatibility issues and talks about other crashes.
This one specifically concerns the bad_alloc crash, which isn't mentioned in
818971, as far as I can tell.
I'm suggesting an un-merge.
Also,
I forgot one thing:
- libArcus carries the same version as the rest of the packages, but it
actually uses a different versioning scheme. The shared library is named
libArcus.so.1.0.0, with the SONAME = libArcus.so.2. This may or may not be
correct. A bug report was filed upstream:
Package: wnpp
Followup-For: Bug #706656
Owner: Gregor Riepl <onit...@gmail.com>
Hello, I've been using Cura (new Cura, not the legacy one) for a while, and
decided that it would be a good idea to package it up for Debian.
Upstream does not make this particularly easy, but thanks to t
Hi Bas,
> Thanks for taking this on! I've been meaning to do that for quite some
> time, but didn't get to it so far.
>
> Would you be interested in maintaining it inside the 3-D printer team?
Thanks for your comments!
Working with others will certainly speed up things.
I also got pointed to
Package: wnpp
Severity: wishlist
* Package name: krita
Version : 3.0
Upstream Author : Boudewijn Rempt and others
* URL : https://krita.org
* License : GPL2+, LGPL2+
Programming Lang: C++
Description : Krita is a professional FREE and
Package: calligra-gemini
Version: 1:2.9.11+dfsg-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
calligra-gemini will not launch due to the following error:
"The Calligra Qt Quick components were not found. This means your installation
is broken."
On the console, the
Package: xul-ext-kwallet5
Version: 1.0-2
Followup-For: Bug #850773
It doesn't look like manually updating to the current version
of the addon (1.3) helps either.
Have you tried that?
Hi Alvaro,
I'm sorry it took me this long to start reviewing your work. I was about to
try to build your packages but I haven't been able to figure out how to do it.
How do you build your packages? Do you use git-buildpackage? I'm missing a
branch named "upstream" or something similar. A
> Yesterday krita was finally accepted in the archive, from the NEW queue,
> and it's currently in experimental.
> It will be in unstable soon.
Awesome!
Thank you very much.
Hi Rock,
Here are my comments, I must say I don't use the software so I only
checked the building and the packaging. I trust you are testing that
once installed all four packages perform as expected :).
Thanks for the review!
I'll comment below.
> libArcus
>
>
> debian/changelog
>
And here's my (updated) response to Rock's comments:
> libArcus
>
>
> debian/changelog
>
>
> * There seems to be a line in the changelog that is too long, it'd be
>nice to split it into two so it fits into the "80 character limit".
Done.
> * Typically, new
Hello, I'd like to help bringing Open Sans into Debian.
I'm working on packages for Cura (the 3D slicer) at the moment, and the
upstream sources includes Open Sans as part of its GUI package.
It would make a lot of sense to provide Open Sans in a separate fonts-
package, instead of purely
Hi,
> It looks like this has been forgotten? I would like to get Cura into Debian,
> so if there's anything I can do to help, let me know.
I'm sorry for the lack of action on my part, progress was stalled since some
of the criticised points are a bit difficult to fix, and I've been too busy to
> - Since this package is maintain by Debian Fonts Task Force, you can
> change your Vcs-* to https://anonscm.debian.org/git/pkg-fonts so that
> other members can help to maintain the git repo.
Thanks for your feedback!
That would indeed make sense. However, no such repo exists currently.
Is
Hi,
it seems AVR has finally updated the avr-libc in their GNU Toolchain:
http://distribute.atmel.no/tools/opensource/Atmel-AVR-GNU-Toolchain/3.5.4/
Even better, they include 2.0.0 now.
Would it be possible to update the Debian packages accordingly?
Thanks!
Hello again,
my packaging repository is here:
https://github.com/onitake/fonts-open-sans
I uploaded the package to Debian mentors as well:
https://mentors.debian.net/package/fonts-open-sans
Could a Debian maintainer take a look and sponsor my package?
Thank you!
>> I'll probably settle for debian-2.3.1 (branches) and debian-2.3.1-1
>> (tags).
>
> Ah, I see. I think you should use upstream's releases anyway; if you need
> to make changes for the packaging, they should just be part of the package,
> not a fork from upstream. Especially if the only change
> Ah yes, clipper has weird and annoying naming. I talked to upstream about it,
> but they don't want to change it. I think it had something to do with a
> package naming conflict in Red Hat. In any case, the package is called
> libpolyclipping. There is a pkg-config file with it, but it's
> Any reason you took this off-list? I'm not sending your mail back to it
> without your permission, but if it was a mistake, feel free to post any of my
> replies back to the list as well.
I'm sorry, that wasn't my intention. I believe one of your responses was
addressed to me personally, so I
> I agree this is the best way; my point was that you should not have a
> repository on github with a copy of the source, and the watch file should
> point
> to Ultimaker's github. Having a repository with the packaging is good. You
> can also host that in our team repository on Alioth. You
Package: ansible
Version: 2.2.1.0-1
Severity: wishlist
Dear Maintainer,
Ansible 2.2 includes a new feature that allows filtering data structures
with sophisticated filters and is much more useful than alternatives like
selectattr, rejectattr, etc.
The filte is called json_query and it relies on
Hello again,
I've since reviewed ChangZhuo's comments and made the requested changes.
Including a short version of the license seems to be common practice in
Debian, so I added it as well.
Concerning the Vcs lines:
Could somebody create the repository
Hi,
> Please request membership in the group on Alioth, so I can add you
> immediately.
Thank you.
The repository is here:
https://anonscm.debian.org/cgit/pkg-fonts/fonts-open-sans.git/
And a new package with the requested changes:
https://mentors.debian.net/package/fonts-open-sans
I
Hi Fabian,
> This looks all good to me!
>
> I like your README.Source file. It is really very informative!
Thanks! :)
> Maybe you could prefix lines that are supposed to get called from the
> shell with a '$' sign. And in line 28, when you present the script to
> check for new font versions,
Package: ansible
Version: 2.2.1.0-2
Severity: important
Dear Maintainer,
Due to upstream bug https://github.com/ansible/ansible/issues/20494 it is
currently not advisable to upgrade python-jinja2 to version 2.9 when using
Ansible. There seem to be other incompabilities with Jinja2 2.9 as well.
> Which version of Firefox are you using? I cannot confirm this problem with
> 52.2.0 (64-Bit). I deleted and re-added a password. The entry is present in
> the KWallet Manager and in Firefox, and used at the next login.
Interesting.
I see the problem in firefox-esr (52.2) and firefox (54.0),
Hi sandro
> 1.3 now entered testing, it would be nice if you can give a status update, if
> that version fixes your issue with the usage with icedove.
1.3 did indeed help against the memory allocation bug. Thunderbird doesn't
crash any more.
Unfortunately, the addon seems to be incompatible
Hi,
I just found a few more packages to build:
https://github.com/Ultimaker/cura-build/tree/master/projects
fdm_materials seems relatively important, I packaged it and added it as a
"Recommends" dependency to Cura. Cura will work without the definitions, but
having them makes it much more
In case upgrading the package is too much work, here's a quilt patch you can
apply on top of the Debian git repository.
>From d2fdbd805683183d92586160445207963712d6af Mon Sep 17 00:00:00 2001
From: Gregor Riepl <onit...@gmail.com>
Date: Mon, 26 Jun 2017 09:00:24 +0200
Subject: [PATCH 1
The upstream patch is contained in 1.0.0-rc3.
Please update the package as soon as possible.
Thank you!
Hi,
after going through another series of revisions and some cleanup, here is the
set of Cura 2.5 packages for review:
https://mentors.debian.net/package/libarcus
https://mentors.debian.net/package/libsavitar
https://mentors.debian.net/package/uranium
Hi,
the Debian 3dprinter team is preparing a release of the new CuraEngine and the
rest of the Cura packages:
https://anonscm.debian.org/cgit/3dprinter/packages/cura-engine.git/
https://anonscm.debian.org/cgit/3dprinter/packages/cura.git/
We're still working on 2.5, but 2.7 or 3.0 will be
>> Uranium and Cura are both ready for review.
>
> Very good. I'll have a look, and hope we can coordinate any fixes on
> IRC.
>
> Btw, are you aware of http://dep.debian.net/deps/dep3/ >?
Partially. I know the guidelines for patches, but wasn't aware of this DEP.
I'll look at it.
> I've just uploaded libsavitar to NEW, after giving the d/copyright file a
> close
> look. I am aware of the several proposals for improvements, but concluded
> that those can be uploaded next time, and decided it was more important
> to get a slot in the NEW queue for now.
>
> The only
It looks like Ultimaker dropped official 32 bit support:
https://github.com/Ultimaker/CuraEngine/issues/547
@pere fixed a few obvious bugs, but testing and more patches (if required) are
welcome.
cura-engine 2.5.0 is available in sid.
Note that it's currently missing libArcus for integration
Hi Petter
> So, libarcus is uploaded and in NEW, and cura-engine is ready to be
> uploaded but held off until its build dependency libarcus is in
> unstable (what about uploading without arcus support for now?)
CuraEngine is not of much use without libArcus, I'm afraid...
I'm not sure if it even
> So, libarcus is uploaded and in NEW, and cura-engine is ready to be
> uploaded but held off until its build dependency libarcus is in
> unstable (what about uploading without arcus support for now?)
Before you upload cura-engine, please pull again.
I forgot to change the Maintainer to the list.
According to https://bugzilla.mozilla.org/show_bug.cgi?id=1357323 ,
this bug should no longer affect Firefox 55 and 56, as the gonk code was
removed from the tree.
Please confirm.
Package: wnpp
Severity: wishlist
* Package name: python-hvac
Version : 0.2.17
Upstream Author : Ian Unruh
* URL : https://github.com/ianunruh/hvac
* License : Apache-2.0
Programming Lang: Python
Description : Python 2/3 client for HashiCorp Vault
1 - 100 of 394 matches
Mail list logo