I can confirm that if I attempt to install openjdk-17-jre-headless I get
the following error:
Setting up openjdk-17-jre-headless:amd64 (17.0.12+7-2~deb12u1) ...
update-alternatives: using /usr/lib/jvm/java-17-openjdk-amd64/bin/java to
provide /usr/bin/java (java) in auto mode
update-alternative
On 2024-07-18 14:29:54, Clément Hermann wrote:
> Hi Micah,
>
>
>
>
>
> Le 11 juillet 2024 13:06:48 UTC, micah anderson a écrit :
>>
>>Hello,
>>
>>In April you had said that you were going to try and upload a new
>>version of torsocks, which
Hello,
In April you had said that you were going to try and upload a new
version of torsocks, which fixes the FTBFS, but you were trying to fix a
few lintian issues first.
Do you have any update on that? It looks like it is going to be removed
from testing soon if it is not fixed.
Thanks!
Mic
These issues are fixed upstream in main, but there is not a release.
The fix is in commit 1171bf2fd4e7a0cab02cf5fca59090b65af9cd29.
Clément would you pull that fix into the package to resolve this FTBFS?
I've tried the same thing, and get the same results. It appears that the
systemd support is there, the cryptsetup support is ithere, but just
cryptsetup-initramfs is not somehow there also.
It would be a shame to release bookworm with just the initramfs feature
missing, when all the other pieces
Package: www.debian.org
Severity: important
I wanted to install Debian stable, so I searched on the internet to find the
debian-installer, and I arrived on
https://www.debian.org/devel/debian-installer/ you click "the bullseye page"
and you get sent to https://www.debian.org/releases/bullseye/d
Package: python3-jinja2
Version: 3.0.3-2
Severity: important
Tags: upstream
Hello,
There is a bug in the version of the package that is in Bookworm that causes
Ansible templates to fail in frustrating ways (see
https://github.com/ansible/ansible/issues/77272), it has been fixed upstream
(https://
Package: unattended-upgrades
Version: 2.8
Severity: wishlist
When unattended-upgrades is run with the --dry-run flag, it still acquires a
cache lock (presumably from apt update?), and makes a pid file. These can
interfere with unattended-upgrade runs that are done without the --dry-run, and
can re
Package: ftp.debian.org
Severity: normal
Hi,
The upstream authors of deltachat-core have decided to re-implement the library
in Rust, and this package is no longer relevant. Upstream is not continuing to
maintain it, and it would just otherwise collect dust in the archive, so I'm
requesting remov
Tianon Gravi writes:
> On Sat, 2 May 2020 at 06:24, Micah Anderson wrote:
>> I'm not sure that this is the right place to file this issue, but I was
>> unable
>> to find a better place. Feel free to redirect to a more suitable place. I
>> talked
>> to t
Hi Balint,
I looked at the patch you link to
(https://github.com/mvo5/unattended-upgrades/pull/280) but the
unattended-upgrade code that is in the diff is fairly different from
what is in the version in Buster, specifically this chunk:
-if not marking_succeeded or \
- not chec
Package: mtail
Version: 3.0.0~rc19-2
Severity: important
Hi,
It seems the version of mtail that is in buster works for a short period of
time, but then gets into a strange state where it doesn't respond anymore. If
you attempt to curl the port it is listening on it will simply hang and never
resp
Package: debuerreotype
Version: 0.10-1
Severity: normal
Hello!
I'm not sure that this is the right place to file this issue, but I was unable
to find a better place. Feel free to redirect to a more suitable place. I talked
to the debian-cloud people and they didn't think that this was their purvi
Package: libquickfix-dev
Version: 1.15.1+dfsg-3
Severity: wishlist
Hello!
It would be nice if you could toggle the configure flag --with-openssl.
It doesn't impact people who want to use it without ssl, but makes it possible
to make TLS connections.
thanks!
-- System Information:
Debian Releas
Package: netbase
Version: 5.6
Severity: minor
Tags: patch
Hello,
It seems /etc/services has a typo for the 'time' service. Patch attached.
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Package: ftp.debian.org
Severity: normal
Hello, World
As the original packager for u1db, I'd like to request removal, as it is no
longer maintained upstream, nor is it needed.
Thank you!
Micah
Moritz Mühlenhoff writes:
> On Fri, Aug 30, 2019 at 07:57:06AM +, Matthias Klose wrote:
>> Package: src:u1db
>> Version: 13.10-6.4
>> Severity: normal
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2removal
>>
>> Python2 becomes end-of-live upstream, and Debian
Mattia Rizzolo writes:
> On Thu, Feb 14, 2019 at 07:58:13AM -0500, Daniel Kahn Gillmor wrote:
>> Could the dput or dput-ng maintainers weigh in on what is needed to make
>> this change?
>
> As the de-facto dput-ng maintainer, I won't do that until DMs can use
> it.
I think it is a good goal to g
"Todd H. Poole" writes:
> As for departing from prior behavior, I'll give you that: that's why there
> was so much messaging around the 4.x release and such a strong up-tick in
> the quality of the upstream docs around that time. If you were to change
> this now, I'd absolutely advocate doing so
Package: postfix
Version: 3.4.5-1
Severity: wishlist
Hello,
Upstream has collate.pl under auxiliary/collate/collate.pl in the upstream
source.
This is a very useful utility script, and would be lovely if the debian package
would include it so it would be installed on the system when the package
Thomas Goirand writes:
> Using puppet-master from both Stretch and Buster in production, I have found
> out that on each puppet run, a run report is saved under:
>
> /var/lib/puppet/reports//.yaml
>
> unfortunately, with a moderatly sized cluster (about 30 nodes), this fills-up
> very fast. For m
Antoine Beaupré writes:
> We've processed a bunch of the dependencies for this, and uploaded some
> to NEW (with related git repos in salsa). Some are not done yet, mostly
> because their license is unclear.
The packages indicated in this table as having unclear licenses have had
that issue reso
The unclear license on this package was resolved by upstream. I believe
that this can be packaged now.
--
micah
The unclear license situation has been resolved by upstream. I believe
that removes the remaining blocker for this package to be put into the
archive.
--
micah
I had the same problem, and I found this bug when searching for a
solution.
I downgraded to the previous jetty version from snapshots.debian.org and
it worked.
I'm unsure what changed in this version that causes it.
--
micah
Control tags -1 - moreinfo
Hi,
Niels Thykier writes:
> I am adding the Debian maintainer of Delta Chat in Debian as:
>
> * I do not know anything about Delta Chat nor its situation outside of
>Debian. In Debian, it has zero bugs.
Indeed, the upstream Delta Chat authors have requested tha
Daniel Kahn Gillmor writes:
> On Mon 2019-02-11 10:25:48 -0500, Daniel Kahn Gillmor wrote:
>> The default dupload target for debian is described this way in
>> /etc/dupload.conf:
If I install dput, I do not have an /etc/dupload.conf, and rather I see
this in /etc/dput.conf:
[DEFAULT]
login
Package: wnpp
Severity: wishlist
Owner: Micah Anderson
* Package name: golang-github-getlantern-systray
Version : 0.0~git20181206.eaad711-1
Upstream Author : Lantern
* URL : https://github.com/getlantern/systray
* License : Apache-2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Micah Anderson
* Package name: golang-github-oxtoacart-bpool
Version : 0.0~git20150712.4e1c556-1
Upstream Author : Percy Wegmann
* URL : https://github.com/oxtoacart/bpool
* License : Apache-2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Micah Anderson
* Package name: riseup-vpn
Version : 0.18.12
Upstream Author : LEAP Encryption Access Project
* URL : https://0xacab.org/leap/bitmask-vpn
* License : GPLv3
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Micah Anderson
* Package name: golang-github-protonmail-go-autostart
Version : 0.0~git20181114.c527205-1
Upstream Author :
* URL : https://github.com/ProtonMail/go-autostart
* License : MIT
Programming Lang: Go
Hello Sergio,
I'm reviewing bugs that are currently release critical at our local bug
squashing party, and I stumbled on yours.
I'm not disputing this bug exists, I'm just trying to determine why it
is you set the severity to "Serious". As you are probably aware, this
severity indicates that th
Hello Marc,
I'm checking up on RC bugs, because we are working on a Bug Squashing
Party here.
Back in November, you were saying you were going to combine this fix
with a bump of upstream's version:
> I was planning to combine this with an update from upstream.
I'm wondering if you are plannin
Actually, I was wrong in my previous message. The package
`leap-archive-keyring` Depends on gnupg because its .postinst has a
clean-up process from a previous package (2016.03.03) that removes keys
from the old /etc/apt/trusted.gpg.
In order to do that clean-up, gpg is necessary, thus the Depend
Julien Cristau writes:
> On Tue, Apr 03, 2018 at 01:00:41PM -0400, micah anderson wrote:
>> I went with 2017.11.24~deb9u1 because indeed, the changes since the
>> current version in stretch are appropriate for a stable update, namely:
>>
>> 1. Providing keys in a sec
Package: wnpp
Severity: wishlist
Owner: mi...@debian.org
* Package name: deltachat-core
Version : 0.24.0
Upstream Author : Delta.chat
* URL : https://github.com/deltachat/deltachat-corecode
* License : GPL
Programming Lang: C
Description : Delta.chat d
I believe the issue has to do with multiple tun/tap devices. The first
one works, but any further ones after fail. You can experience this with
multiple KVM guests, or trying to run openvpn listening on UDP and
TCP. Only one will work, the rest will fail.
It seems like Ben has already found the s
"Adam D. Barratt" writes:
> Control: tags -1 + moreinfo
>
> On Wed, 2018-03-21 at 14:07 +0100, micah wrote:
>> "Adam D. Barratt" writes:
>>
>> > Control: tags -1 + moreinfo
>> >
>> > On Tue, 2018-03-20 at 16:32 -0400, micah wrote:
>> > > The leap-archive-keyring is a simple archive keyring pac
This memory leak is real. I've hit it many times, it ate up all my
memory, and filled up all my disks with logs like:
LOG4[218498]: Possible memory leak at ../crypto/asn1/asn1_lib.c:277:
33195 allocations
I ended up getting 4 log files of 14gig each, because of the severity of
the logging.
I've
Version: 2007.11.08
thanks
This issue was resolved in the most recent upload,
micah
That fix works, I've done a NMU fixed package and uploaded it to
DELAYED-3.
Micah
I've confirmed this bug, as reported:
I installed lighttpd:
The following NEW packages will be installed:
lighttpd spawn-fcgi
0 upgraded, 2 newly installed, 0 to remove and 326 not upgraded.
Need to get 299 kB of archives.
After this operation, 1,019 kB of additional disk space will be used.
D
I changed the order in the Build-dep so that it was:
libssl1.0-dev|libssl-dev
instead of:
libssl-dev|libssl1.0-dev
It built fine, and used libssl1.0-dev instead. I think that this would
solve lighttpd being in error state for this transition:
https://release.debian.org/transitions/html/ssl1.0
Package: stunnel4
Version: 3:5.39-2
Severity: wishlist
Hello,
The following options in the man page do not indicate their defaults. I had to
dig into the source to find them:
sessionCacheSize: 1000
sessionCacheTimeout: 300
TIMEOUTbusy: 300
TIMEOUTclose: 60
TIMEOUTidle: 43200
TIMEOUTconnect: 10
Julian Andres Klode writes:
>> deb http://deb.leap.se/debian sid main Signed-By:
>> 2f483BbCE87BEE2F7DFE99661E34A1828E203901
>
> That's invalid syntax. It should look like these:
>
> deb [signed-by=BBEBDCB318AD50EC6865090613B00F1FD2C19886]
> http://repository.spotify.com stable non-free
Th
Apollon Oikonomopoulos writes:
> On 09:29 Thu 02 Feb , micah wrote:
>> Apollon Oikonomopoulos writes:
>>
>> ...
>> > - As soon as 4.8.2-1 enters testing, I intend to upload 4.8.2-2, with
>> >the following changes:
>> ...
>> >It will go through NEW for puppet-terminus-puppetdb, vim
Otto Kekäläinen writes:
> 2017-01-31 0:27 GMT+02:00 micah :
>> I upgraded a machine from jessie to stretch today and then when I went
>> to reboot, I had to wait 10 minutes for mysql to fail to shutdown.
>
> Looking at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800588 I
> don't see Micah i
Hello,
intrigeri writes:
> Hi Micah,
>
> Adrian Bunk:
>> Can you anyway NMU this package?
>
>> The alternative is that it will get removed from stretch soon.
>
> Well, it's not a goal of mine to include as many packages in Stretch
> as possible. So I really don't want to be the one who decides
Antonio Terceiro writes:
>> Relevant part (hopefully):
>> > Failure/Error: response = http.request(request)
>> >
>> > OpenSSL::SSL::SSLError:
>> >SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert
>> > unsupported certificate
Hmm, I built the reverse depends on r
Hi,
This bug is pretty annoying, because it makes it impossible to recover
from problems in a scriptable way. I thought maybe things would be
better in 'apt', but it turns out its still the case that you will get a
'0' result code:
root@muck:/home/micah# apt update
Hit:1 http://deb.leap.se/debia
Package: python3-pyqt5
Version: 5.6+dfsg-1
Severity: normal
Hello,
The current Sid version of Qt5 5.6 for python3 has problems with decoration
signatures as in: `TypeError: decorated slot has no signature compatible with
mapped(QString)`. Other platforms with python3 and Qt5 5.6 do not have this
Package: nginx
Version: 1.9.10-1
Severity: normal
Tags: patch
Hello,
It turns out that the way that Debian implements stopping nginx is by
sending it, through the start-stop-daemon's --retry option a SIGQUIT to
nginx, which is interpreted by nginx as a "gradeful shutdown", but it
turns out is not
Hi,
> (If you don't have time to maintain this package anymore, I'm willing
> to help out. I'm already a member of the DPMT and can prepare an
> updated package if you want).
The maintainer for this package is the Python Modules Team
, it seems you are already
a member of that team, the
https://
Chris Knadle writes:
> micah:
>> Chris Knadle writes:
>
>>> I'm currently updating my 1.2.10-1 prepared upload for Debian with a patch
>>> for #787384, which I just did for the package in my repo only for Sid,
>>> because the new zeroc-ice hasn't transitioned to Stretch yet AFAIK.
>>
>> The rea
Hi,
If you aren't ready to upload the new mumble packages yet, would you
make the ones you've prepared available? I'd like to test them as soon
as possible.
thanks!
micah
Hi Chris,
It looks like the gcc5 transition is no longer affecting mumble. Maybe
you can upload the new version now?
I'd really like this available as a jessie backport, so I'd love to see
it transition soon!
micah
Hi,
I hear the argument that Colin is making, and understand and respect the
use-case he describes for the setting, and wouldn't argue that this
option should be removed. However, I feel like the comparison that is
being setup doesn't make sense for justifying that the setting is the
default.
Th
ngelog 2014-10-17 20:16:29.0 -0300
+++ sqlcipher-3.2.0/debian/changelog 2015-04-22 17:03:50.0 -0300
@@ -1,3 +1,11 @@
+sqlcipher (3.2.0-1.1) unstable; urgency=high
+
+ [ Ben Carrillo ]
+ * Non-maintainer upload.
+ * use a separate variable to track SQLCIPHER version (Closes: #
> In my opinion it's very good when backports is default in sources.list.
>My opinion is that I don't want to push ticking time bombs into the
>hands of our users. And that's exactly what defaulting to enabling
>backports was.
You pointed out that apt will happily install a package from backport
Package: initramfs-tools
Version: 0.119
Severity: wishlist
I have an encrypted USB drive that is not always attached to my
system. With the default cryptsetup configuration, when the system
boots, it asks me for the passphrase and everything is fine. If the
device is not connected, then booting ta
Package: cryptsetup
Version: 2:1.6.6-5
Severity: wishlist
Homepage: http://code.google.com/p/cryptsetup/ <-- is no longer valid,
the project is now at: https://gitlab.com/cryptsetup/cryptsetup
micah
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubs
I just tried to do a database update with 0.19.1-1.1 and it churned for
a while and then spit out this in the log:
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
and it killed the mpd daemon :(
micah
--
To UNSUBSCRIBE, e
Package: duplicity
Version: 0.7.01-1
Severity: minor
Hi,
The new version of duplicity does not support --ssh-backend, but the manpage
details that option. It seems that this should be removed from the docs.
micah
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (5
I ran into this as well, I can't sign a key because one of the subkeys
is expired. The key holder has deliberately let that key expire, but it
makes it so I can't use monkeysign to sign any uids for this user.
micah
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a s
severity 768094 important
tags 768094 patch
thanks
This is also happening to me. I can't update the database without it
crashing. I thought I had a few malformed mp3s, so I moved several out
of the way, which would cause it to work a little further and then crash
again, but it quickly became clear
Package: rsyslog
Version: 8.4.2-1
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of
Package: mpd
Version: 0.19.1-1
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of thi
Package: anacron
Version: 2.3-22
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of t
Package: haveged
Version: 1.9.1-1
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of
Package: network-manager
Version: 0.9.10.0-3
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the
Package: gdm3
Version: 3.14.1-3
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of th
Package: cron
Version: 3.0pl1-127
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of
Package: dnsmasq
Version: 2.72-2
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of t
Package: openvpn
Version: 2.3.4-4
Severity: wishlist
Hello,
If you add the option ProtectSystem=yes to the service file, then the
daemon will not have the ability to write to /usr.
There is no reason why it needs to write there, so enabling this
option should not cause any problems.
This option
Package: alsa-base
Version: 1.0.27+1
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome
Package: bluez
Version: 5.23-1
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of thi
Package: openssh-server
Version: 1:6.7p1-3
Severity: wishlist
Hello,
If you add the option ProtectSystem=yes to the service file, then the
daemon will not have the ability to write to /usr.
There is no reason why it needs to write there, so enabling this
option should not cause any problems.
Th
Hi,
I'm sorry I didn't reply to your earlier mail, I was not CC'd on it and not
subscribed to the bug. I've just subscribed to the bug so I will get further
replies without the need for the CC.
On Tue, Jul 08, 2014 at 06:33:34PM +0200, André Gaul wrote:
> Am 08.07.2014 08:39, schrieb László Bösz
I merged these bugs, but it seems that automatically tagged 760347 as
wontfix, because the other bug was marked that. I didn't intentionally
do that. I guess if the old status is no longer relevant, then perhaps
re-opening the bug would be in order.
I'll step out of the way of this as I think I'v
Package: openssh-server
Version: 1:6.6p1-7
Severity: wishlist
It suddenly dawned on me today, after doing this for the millionth time, that
when you install the openssh-server package, and it generates the ssh-host keys,
it would be super helpful if it simply ran ssh-keygen -lf against those
gener
hangelog 2014-07-10 00:49:54.0 -0400
+++ network-manager-0.9.10.0/debian/changelog 2014-08-11 12:37:33.0 -0400
@@ -1,3 +1,11 @@
+network-manager (0.9.10.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Pull patch from upstream to fix checks for default
+routes
+
+ -- Mic
Michael Biebl writes:
> Am 11.08.2014 19:06, schrieb micah anderson:
>> Control: tags 755015 + patch
>> Control: tags 755015 + pending
>>
>> Hello!
>>
>> I've prepared an NMU for network-manager (versioned as 0.9.10.0-1.1) and
>> uploaded it
micah writes:
> I do know that this patch did resolve the issue I was experiencing,
> however your email has caused me to question if the issue that was
> originally reported in 755015 was the same issue as the one I was
> experiencing. I should have that figured out relatively soon and get
> bac
Package: ftp.debian.org
Severity: normal
The pyopenssl package was switched from Arch:any to Arch:all, and the
auto-decrufting process did not work, as a result it is not installable and has
not been for over a week:
muck# apt-get install python-openssl
Reading package lists... Done
intrigeri writes:
> Hi,
>
> micah anderson wrote (14 Aug 2014 21:12:03 GMT) :
>> Also - we have a package ready to upload for it.
>
> Where can I find this package?
It is available at:
deb http://deb.leap.se/debian sid main
as well as the git repository:
git clon
ebian/changelog
@@ -1,3 +1,10 @@
+bird (1.4.4-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Install birdcl
+
+ -- Micah Anderson Sat, 16 Aug 2014 15:45:29 -0400
+
bird (1.4.4-1) unstable; urgency=medium
* New upstream version 1.4.4
to /bin/dash
Versions of packages bird depends on:
ii adduser 3.113+nmu3
ii libc6 2.19-7
ii libreadline6 6.3-8
ii libtinfo5 5.9+20140712-2
bird recommends no packages.
Versions of packages bird suggests:
ii bird-doc 1.4.4-1
diff --git a/debian/changelog b/debian/changelo
> Why exactly should shell=True be necessary?
It turns out that shell=True (basically what started the fork) is not
needed now. Vinay changed it in the latest release of the "original"
python gnupg, which came after a bunch of CVEs and some comments in this
thread as a result of python-gnupg-ng:
micah anderson writes:
I just tried to build this and I had to remove two symbols from the
libsodium10.symbols file to get it to build, on 386.
- _crypto_stream_salsa20@Base 0.6.0
- _crypto_stream_salsa20_xor_ic@Base 0.6.0
+#MISSING: 0.6.1-1# _crypto_stream_salsa20@Base 0.6.0
ainer upload.
+ * Pull patch from upstream to fix checks for default
+routes (Closes: #755015)
+
+ -- Micah Anderson Mon, 11 Aug 2014 12:08:31 -0400
+
network-manager (0.9.10.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru network-manager-0.9.10.0/debian/patches/000
Hello,
I am eager to have libsodium available in Debian.
From what I can tell, the last state is László asking Raúl:
> I've updated the packaging[2]. Will upload it with those changes if
>you don't mind.
>
> https://github.com/gcsideal/libsodium/commits/master
Raúl, it seems like there is just
Hi,
I'm having a similar issue. If I use openvpn externally, it will push a
default route, but network-manager immediately removes that route. This
is new behavior in 0.9.10, in fact I confirmed that by trying the
previous version by pulling packages from snapshots, previous versions
did not have
Hello,
I ran into this issue when I upgraded to the backport version. I found
http://www.redmine.org/issues/16710 which detailed the issue and the
fixes.
I tried to pull in the changes that were mentioned in that issue to
the ruby-mime-types that I have installed on wheezy, but found the code
w
Package: couchdb
Version: 1.4.0-3
Severity: wishlist
Hello,
It would be nice if we could have the most recent version of couchdb
available. I've imported the 1.6.0 upstream code and built a package from it, it
was quite easy to do!
If you like, I can upload this package for you.
micah
-- Syst
Micah Anderson writes:
> The way to do this is to have the package install a
> /etc/apt/apt.conf.d/90languages with the following:
>
> Acquire::Languages { "ca"; "cs"; "da"; "de"; "el"; "en"; "eo"; "es
Package: reprepro
Version: 4.14.0-1
Severity: minor
Hello,
I found the signhook implementation (from #469656) and am interested in using
that for offline signing. However, the manual.html seems to be truncated in the
description, it simply reads:
The script gets three arguments: The filename to
Package: apt-transport-tor
Version: 0.1.1-1
Severity: important
Hello,
Thanks for making apt-transport-tor, I was doing this via torsocks, but it was
sub-optimal. This is much better!
The only problem is that when you do an apt-get update, you are leaking some
important identifying bits, namely
Package: apt
Version: 1.0.1
Severity: normal
Hello,
It seems like from reading the code that the gpg signature verification process
doesn't
provide meaningful exit codes when bad things happen. This results in apt-get
update
providing an exit code of zero, even if there was a BADSIG. It would b
Source: redmine
Version: 2.4.2-1
Severity: normal
Hello,
It seems that in certain circumstances that I have not been able to adequitely
determine, Redmine gives a 500 Internal Server error, and the following in the
logs when viewing the repository:
ActionView::Template::Error (no suitable markdo
---
debian/changelog | 1 +
debian/login.postinst | 13 +
2 files changed, 14 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index ebf1e9c..cb9f338 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -39,6 +39,7 @@ shadow (1:4.2-1) UNRELEASED; urgency=low
1 - 100 of 1178 matches
Mail list logo
