Hi,
Le 14/08/2024 à 22:19, Adam D. Barratt a écrit :
On Wed, 2024-08-14 at 21:47 +0200, Clément Hermann wrote:
So I did the change (changes + debdiff attached), and tested on a
fresh bullseye install. Of course, obfs4proxy was pulled from
Recommends when I installed my version, but everything
mends, to allow removal of obfs4proxy
- See #1008164
+
+ -- Clément Hermann Wed, 14 Aug 2024 08:40:03 +0200
+
onionshare (2.2-3+deb11u1) bullseye; urgency=medium
* Backport upstream fix for CVE-2022-21690
diff -Nru onionshare-2.2/debian/control onionshare-2.2/debian/control
--- onionshar
ols Maintainers
Changed-By: Clément Hermann
Description:
Changes:
onionshare (2.2-3+deb11u2) bullseye; urgency=medium
.
* Demote obfs4proxy dependency to Recommends, to allow removal of obfs4proxy
- See #1008164
Checksums-Sha256:
922cebde2a08bbd8703daa401d07edf3330b8e93644f1d1033b87d16ce2ce584 2
Hi,
Sorry, the emails went to a strange filter. Pinging on IRC was a good
move. ;)
Le 12/08/2024 à 22:38, Adam D. Barratt a écrit :
Re-ping, given that we're less than three weeks from the final bullseye
point release.
Regards,
Adam
On Mon, 2024-07-08 at 19:24 +0100, Jonathan Wiltshire
Package: sq
Version: 0.37.0-1
Severity: normal
When running `sq key list`, I get only one of the keys managed by the
gpg-agent backend.
I do have several secret keys, on different hardware tokens, and I'd
like to be able to use other keys than the first one (e.g. with
gpg-from-sq).
gpg --list-se
Hi,
it seems fine in 0.37.0-1, at least on my machine. Bash completion
script is here and seem to work fine.
I guess this could be closed?
I tagged the bug as notfound for 0.37.0-1 meanwhile.
--
nodens
Package: lintian
Version: 2.117.0
Severity: normal
Hi,
as said in the title, and unless I'm mistaken, libexec directory
contains executables, not libraries, so it shouldn't trigger
arch-dependent-file-not-in-arch-specific-directory, just like *bin/.
I'll try to make a MR on Salsa soon.
Cheers,
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 fixes the FTBFS, but you were trying to fix a
>few lintian issues first.
Sorry about that, the issues that prevented
Hi,
Le 11/04/2024 à 22:23, micah anderson a écrit :
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?
Thanks for the heads up!
I'll try
Hi,
FYI I created a merge request at
https://salsa.debian.org/alsa-team/alsa-lib/-/merge_requests/4 to fix
this one, using upstream patch.
cheers!
--
nodens
Package: libasound2
Version: 1.2.10-1
Severity: normal
Tags: patch upstream
Dear Alsa team,
alsa-lib 1.2.10 implements UMP support for seq.
Unfortunately, it breaks chromium WebMIDI at least partially.
This is a chromium bug, actually, but since it is a regression, upstream
has implemented a wo
Package: alsa-ucm-conf
Version: 1.2.10-1
Severity: normal
Tags: upstream
Dear Alsa team,
Since 1.2.10, profiles using ucm2/common/pcm/split.conf won't load (at
least on Arturia Minifuse 1 and 2, and Motu M4). As a result, for cards
with more than 2 outputs, the default surround profile is loaded
Hi,
FYI, Upstream has started work on that in a branch
https://git.tuxfamily.org/wipetools/nautiluswipe.git/log/?h=nautilus-extension-4-wip.
There are "alpha release" but I'm not sure this will be ready for
bookworm. I can try to update it in experimental, though.
Cheers,
--
nodens
Package: torsocks
Version: 2.3.0-3
Severity: wishlist
Hi,
upstream has some interesting commits in the Master branch (but no
release).
Notably, it seems now to handle syscall passthrough instead of dropping
them with a warning. We might want that in Bookworm (but this need to
happen soon).
http
Hi,
Le 24/11/2022 à 07:44, Andres Salomon a écrit :
On Sat, 24 Sep 2022 12:39:08 +0200 =?utf-8?q?Cl=C3=A9ment_Hermann?=
wrote:
> Package: chrome-gnome-shell
> Version: 10.1-5
> Followup-For: Bug #1016881
>
> Hi,
>
> Not sure it's actually a bug on chrome-gnome-shell, since what we need
Hi
Le 25/10/2022 à 13:53, Clément Hermann a écrit :
Hi Moritz,
Le 25/10/2022 à 11:15, Moritz Muehlenhoff a écrit :
Given that the primary use case for onionshare will be tails, my
suggestion would be that CVE-2022-21689
and CVE-2022-21690 get backported fixes for the next Bullseye point
ackport upstream fix for CVE-2022-21689
+
+ -- Clément Hermann Sat, 12 Nov 2022 17:23:52 +0100
+
onionshare (2.2-3) unstable; urgency=medium
[ Ulrike Uhlig ]
diff -Nru onionshare-2.2/debian/gbp.conf onionshare-2.2/debian/gbp.conf
--- onionshare-2.2/debian/gbp.conf 2020-08-29 19:0
Hi Moritz,
Le 25/10/2022 à 11:15, Moritz Muehlenhoff a écrit :
Hi Clément,
Sadly, upstream rectified and confirms it affects 2.2 [0], and has been
tested and reproduced on Bullseye. We do need to fix it. Upstream has a few
suggestions, but I guess our choices are either uploading 2.5 to stable
Hi Georg,
Le 14/10/2022 à 11:12, Georg Faerber a écrit :
Control: forwarded -1 https://0xacab.org/jvoisin/mat2/-/issues/178
Control: tags -1 + fixed-upstream upstream
Hi Paul,
On 22-10-13 19:52:35, Paul Gevers wrote:
With a recent upload of libimage-exiftool-perl the autopkgtest of mat2
fails
Le 24/10/2022 à 20:41, Clément Hermann a écrit :
- CVE-2022-21694 <https://github.com/advisories/GHSA-h29c-wcm8-883h>
affects Bullseye, but that might be an acceptable risk ? The issue is
that CSP can only be turned on or off, not configured to allow js etc,
so it is only useful for
Le 24/10/2022 à 18:26, Clément Hermann a écrit :
Hi,
Le 23/10/2022 à 18:27, Clément Hermann a écrit :
Hi,
Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit :
To be on safe side, explicitly confirming by upstream would be great.
Agreed. And asked upstream:
https://github.com/onionshare
Package: onionshare
Version: 2.5-2
Severity: wishlist
Quoting
https://github.com/onionshare/onionshare/security/advisories/GHSA-jgm9-xpfj-4fq6
> Between September 26, 2021 and October 8, 2021, Radically Open
> Security conducted a penetration test of OnionShare 2.4, funded by the
> Open Technolo
Hi,
Le 23/10/2022 à 18:27, Clément Hermann a écrit :
Hi,
Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit :
Thanks for the quick reply! (much appreciated). I think it would be
good to get a confirmation from upstream and if possible to have
those advisories updates. E.g.
https
Hi,
have you seen the same issue with recent (2.x) versions?
(asking because I never had the issue, and I'm tempted to close this as
fixed in current testing version at least).
Cheers,
--
nodens
Hi,
Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit :
Thanks for the quick reply! (much appreciated). I think it would be
good to get a confirmation from upstream and if possible to have
those advisories updates. E.g.
https://github.com/onionshare/onionshare/security/advisories/GHSA-x7wr-28
Hi,
Le 22/10/2022 à 15:59, Vincent Lefevre a écrit :
Hi,
On 2022-10-22 14:31:24 +0200, Clément Hermann wrote:
I could reproduce your issue if I enable check_sigs option in CPAN
(which is _not_ the default).
OK, I forgot about that (though I think that it should be the default
for security
Hi Salvatore,
Le 22/10/2022 à 13:49, Salvatore Bonaccorso a écrit :
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2021-41867
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41867
[1] https://security-tracker.debian.org/tracker/CVE-2021-41868
Hi!
Thanks for your report.
I could reproduce your issue if I enable check_sigs option in CPAN
(which is _not_ the default).
Thing is, it's not a bug, really. Or not quite. It's a result of the
correction of a bug in CPAN < 2.29 who would succeed silently if there
is no signature/no way to
Source: openpgp-applet
Version: 1.1-3
Severity: normal
Hi,
Since some time, the debian/watch for opengpgp-applet can't get
signatures.
The signatures are in the /upload/ subdirectory, which is unpredicatable:
Looking at
https://salsa.debian.org/openpgp-applet-team/openpgp-applet/-/archive/OpenP
Package: ardour
Version: 1:6.9.0+ds0-2+b1
Severity: wishlist
Dear Maintainer,
In case you didn't notice yet, Ardour 7.0.0 has been released on October
15th. Since I wanted to give it a go, I thought I'd try to upgrade to
the last upstream release.
So I created a MR on salsa for you to review:
h
Package: chrome-gnome-shell
Version: 10.1-5
Followup-For: Bug #1016881
Hi,
Not sure it's actually a bug on chrome-gnome-shell, since what we need
is a new package that will replace this one for gnome >=42.
The bug here is it should depends on gnome-shell <42.0, I guess.
RFP for gnome-browser-ex
Package: wnpp
Severity: wishlist
* Package name: gnome-browser-connector
Version : 42.1
Upstream Author : Yuri Konotopov
* URL :
https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome
* License : GPLv3
Programming Lang: Python
Description : GNO
Package: pipewire
Version: 0.3.57-1
Tags: fixed-upstream
Dear pipewire maintainers,
I'm a happy user of pipewire since a few month, however since the
upgrade to 0.3.57, no node can output sound if pavucontrol is open.
When pavucontrol is open, pipewire log show the following error message
(3-
Hi,
Le 28/08/2022 à 20:42, Dmitry Shachnev a écrit :
Source: onionshare
Version: 2.2-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][
Hi,
So, my workaround for this annoying issue was to use gpg-agent instead.
As a nice side effect, you can then use a gpg key to authenticate.
The tricky part for me was to make sure gnome woudn't try to set
SSH_AUTH_SOCK to gnome keyring anyway.
In case others want to go this route, here i
Package: alsa-ucm-conf
Version: 1.2.6.3-1
Followup-For: Bug #990189
Dear Maintainer,
upstream is now at 1.2.7.1, and there are many interesting changes for
multichannel cards.
Thanks!
--
nodens
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unst
Source: alsa-lib
Version: 1.2.4-1.1
Severity: wishlist
Dear Maintainer,
the 1.2.7.1 upstream release is available.
It's especially interesting to me because of changes in the UCM
interface that allows to handle multichannel interfaces better (macros
for making splitting/joining channels easier i
On 10/02/2021 00:18, Jonathan Marquardt wrote:
> On Fri, Feb 05, 2021 at 12:08:49PM +0100, Clément Hermann wrote:
>> in a clean Buster virtual machine, I tried to pip3 install psutil then
>> install onioncircuits, and I didn't get this error (though I didn't try
>&g
On 04/02/2021 13:04, Jonathan Marquardt wrote:
> On Thu, Feb 04, 2021 at 12:23:17PM +0100, Clément Hermann wrote:
>> The error message reference stuff in /usr/local: this leads me to think
>> some python libs where locally installed without using the package
>> system. Can
Control: severity -1 normal
Control: tags -1 +moreinfo
Hi,
Thanks for reporting a bug in onioncircuit Debian package!
On 04/02/2021 10:39, Jonathan Marquardt wrote:
> Package: onioncircuits
> Version: 0.5-4
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
>
Hi,
On 08/01/2021 05:07, peylight wrote:
> Hi Dear Debian Developers,
> Can you check the 331th message of LXD packaging please:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768073#311
>
Thanks for your interest in LXD packaging - and sorry for the late reply.
The issue with said packa
the code is properly generated. I implemented this in
the debian package (to be uploaded soon).
Please, consider including this patch.
Cheers,
--
Clément Hermann (nodens)
(with my Tails contributor and Debian Privacy Packaging Team member hats
both on)
Description: Fix valac call generation in
Hi,
On 10/01/2021 23:46, Sebastian Ramacher wrote:
> On 2020-10-05 15:18:46 +0200, Clément Hermann wrote:
>>
>> Hi,
>>
>> Control: block 971299 with 886291
>> thanks
>>
>> On 28/09/2020 23:29, Sebastian Ramacher wrote:
>>> Source: onionsha
Hi Paul,
On 27/12/2020 07:12, Paul Gevers wrote:
> Source: golang-gopkg-lxc-go-lxc.v2
> Version: 0.0+git20190625.f4822c6-1
> Severity: serious
> Control: close -1 0.0+git20201012.d1943fb-1
> Tags: sid bullseye pending
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
> De
Hi,
On 27/09/2020 20:23, Kurt Kremitzki wrote:
> Hello,
>
> With the release of LXD 4.6 [1], it should now be a lot easier for it to be
> brought to Debian:
>
> "Dqlite changes
>
> Shortly after LXD 4.5 was released, a major change was made to upstream
> dqlite.
>
> Rather than relying on ou
Hi,
Control: block 971299 with 886291
thanks
On 28/09/2020 23:29, Sebastian Ramacher wrote:
> Source: onionshare
> Version: 2.2-2
> Severity: important
> Tags: sid bullseye
> Usertags: pycrypto
>
> Dear maintainer,
>
> onionshare currently Build-Depends or Depends on python3-crypto from
> PyC
retitle -1 ITP: libdqlite - High-availability SQLite with Raft consensus
thanks
On Tue, 31 Jul 2018 11:24:36 +0800 (CST) "Clement Hermann"
wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Clement Hermann
>
> * Package name: golang-github-canonicalltd-dqlite
> Version : 0.0~g
Package: timewarrior
Version: 1.2.0-1
Severity: normal
Tags: patch
Hi,
bash completion doesn't work, because the completion script is installed
in /usr/share/bash-completion/ instead of
/usr/share/bash-completion/completions/.
It would probably be better to use dh_bash-completion.
Please find a
Package: bash-completion
Version: 1:2.10-1
Severity: wishlist
Hi,
bash-completion dh sequence addon could benefit from providing the
virtual package dh-sequence-bash-completion.
It would allow to just add dh-sequence-bash-completion to the
build-depends of a package instead of adding bash-comple
Package: flatpak
Version: 1.6.1-1
Severity: normal
Hi,
I use Roboto Regular font for most of my interface (gnome).
When opening a file dialog in flatpak apps, All text in the dialog
appear as squares. It works if I switch to Cantarell Regular (or, apparently,
RobotoRegular Regular).
Steps to r
Package: wnpp
Severity: wishlist
* Package name: bandwhich
Version : 0.10.0
Upstream Author : Aram Drevekenin
* URL : https://github.com/imsnif/bandwhich
* License : MIT
Programming Lang: Rust
Description : Terminal bandwidth utilization tool
Bandwhich
On Sat, 18 Jan 2020 23:55:10 +0100 Marco d'Itri wrote:
> On Jan 07, Guillaume Brocker wrote:
>
> > janv. 06 11:10:46 sigismund sshd[27148]: /usr/sbin/sshd:
> > /lib/i386-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required
> > by /usr/sbin/sshd)
> Does purging libxcrypt1 make it w
Hi,
Le January 7, 2020 1:03:14 PM UTC, Bastian Germann a écrit
:
>Package: golang-bindata
>Version: 3.0.7+git20151023.72.a0ff256-3
>Severity: normal
>
>The jteeuwen/go-bindata repository is not maintained anymore, according
>to its README.md.
Thanks for reporting this !
>Please switch to http
On 01/09/2019 08:57, Niels Thykier wrote:
> Control: tags -1 moreinfo unreproducible
>
> On Thu, 22 Aug 2019 00:10:08 +0200 =?utf-8?q?Cl=C3=A9ment_Hermann?=
> wrote:
>> Package: debhelper
>> Version: 12.5.3
>> Severity: normal
>>
>> Hi,
>>
>> while working on a package, I had trouble finding out
Package: debhelper
Version: 12.5.3
Severity: normal
Hi,
while working on a package, I had trouble finding out why some file were
disapearing without any reason and no entry in build log, despite using
DH_VERBOSE.
Looking at the code, it's because
glob_expand_error_handler_silently_ignores is use
Hi,
closing this, since it was packaged after all (#932485). Sorry, while
packaging it I failed to check if there was already an RFP.
Cheers,
nodens.
On 21/07/2019 13:56, Dominique Dumont wrote:
> On Thu, 18 Jul 2019 18:45:26 -0300 =?utf-8?q?Cl=C3=A9ment_Hermann?=
> wrote:
>> while it is true that there is an issue on my system (I should have made
>> sure the latest policy version was installed), the message is quite
>> bizarre and unhelpful ;
Package: wnpp
Owner: Clément Hermann
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org
* Package name: libextutils-makemaker-dist-zilla-develop-perl
Version : 0.03
Upstream Author : Jesse Luehrs
* URL :
https
Package: wnpp
Owner: Clément Hermann
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org
* Package name: libextutils-hascompiler-perl
Version : 0.021
Upstream Author : Leon Timmermans
* URL : https://metacpan.org/release
Package: wnpp
Owner: Clément Hermann
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org
* Package name: libextutils-hascompiler-perl
Version : 0.021
Upstream Author : Leon Timmermans
* URL : https://metacpan.org/release
Package: libconfig-model-dpkg-perl
Version: 2.122
Severity: normal
While running dh-make-perl (0.106, not uploaded yet) for a new package,
with an out-of-date policy installed (4.3.0 instead of 4.4.0), I got the
following error:
```
Warning in 'source Standards-Version': Current standards version
Hi,
First, sorry for the late reply. A mail filter caught this message
before I had the chance to read it.
On 14/12/2018 12:15, Harald Dunkel wrote:
> Hi folks,
>
> how good are chances to get LXD into Buster?
As much as it pains me to say so, not very good at the moment, with the
soft freeze c
Source: golang-github-miekg-mmark
Severity: normal
Hi,
it was reported on the #debian-golang channel that this package's
upstream has moved.
Indeed, the README.md on https://github.com/miekg/mmark warns:
> !THIS REPOSITORY IS DEPRECATED!
>
> A new version of mmark can be found at
> https://github
Package: goaccess
Version: 1:1.2-4
Severity: wishlist
Tags: patch
Hi,
There is a new upstreame release of goaccess (1.3).
Since I wanted to test it, I made an updated package myself.
Please check https://salsa.debian.org/debian/goaccess/merge_requests/1
on salsa, review, merge, and upload if it'
Hi!
On 26/10/2018 15:41, Pierre-Elliott Bécue wrote:
> Le mardi 31 juillet 2018 à 11:24:36+0800, Clement Hermann a écrit :
>> Package: wnpp
>> Severity: wishlist
>> Owner: Clement Hermann
>>
>> * Package name: golang-github-canonicalltd-raft-membership
>> Version : 0.0~git20180413.3
On 9/14/18 3:11 PM, Martín Ferrari wrote:
> On 12/09/18 15:59, Martín Ferrari wrote:
>
>>> I'm not sure it warrants an upload right away, but it would be nice to
>>> have it before debhelper is updated.
>>>
>>> Could anyone sponsor that ?
>>
>> I would be happy to, but I have not been following dh
Hey,
thanks for the quick response!
On 9/14/18 2:24 PM, Free Ekanayaka wrote:
> Hey there,
>
> I do have the intention to submit the patches upstream, but since 1) the
> work is not fully complete 2) SQLite authors are *extremely*
> conservative when it comes to contributions, that won't happen
Hi!
On Tue, 31 Jul 2018 14:00:12 -0400 =?UTF-8?Q?St=C3=A9phane_Graber?=
wrote:
> On Tue, Jul 31, 2018 at 10:10 AM Free Ekanayaka wrote:
> >
> > Hey,
> >
> > I would think that Stéphane will want to backport these changes to the
> > 3.0.x series, as they improve performance considereably. It wo
On 9/12/18 6:38 PM, Niels Thykier wrote:
> Clément Hermann:
>>
>> On 12/09/2018 11:13, Clément Hermann wrote:
>>> Package: debhelper
>>> Version: 11.3.5
>>> Severity: wishlist
>>> Tags: patch
>>>
>>> Hi,
>>>
>>
On 10/09/2018 12:47, Clément Hermann wrote:
> The change is implemented (see [1]), and Niels is OK to add something to
> the compatibility notes of debhelper, as long as we provide the text and
> open a bug.
This is #908656.
> So, if no one objects, I'll merge the branch,
On 12/09/2018 11:13, Clément Hermann wrote:
> Package: debhelper
> Version: 11.3.5
> Severity: wishlist
> Tags: patch
>
> Hi,
>
> as discussed in #904261, we'd like to have an item in the
> compatibility notes about a non-backward compatible change in dh-gola
Package: debhelper
Version: 11.3.5
Severity: wishlist
Tags: patch
Hi,
as discussed in #904261, we'd like to have an item in the
compatibility notes about a non-backward compatible change in dh-golang.
A merge request will be done on salsa with a proposed text as soon as I have
a bug number. I'll
On 16/08/2018 17:37, Clément Hermann wrote:
> On 16/08/2018 17:13, Clément Hermann wrote:
>> On 16/08/2018 16:26, Martín Ferrari wrote:
>
>>> We could also change the default in the next debhelper compat mode;
>>> dunno how this is normally handled, but it would be
On 18/08/2018 11:03, Niels Thykier wrote:
> Clément Hermann:
>> How are we supposed to do this properly ? Not checking the compat level
>> and behaving accordingly, this is documented, but the communication
>> part: should we file a bug against debhelper too ?
>>
&
Hi,
We (go team) are considering changing a default behaviour of dh-golang
in the next compat level (see #904261 for the specifics details). That
would be compat level 12, if I'm not mistaken.
How are we supposed to do this properly ? Not checking the compat level
and behaving accordingly, this i
On 16/08/2018 17:13, Clément Hermann wrote:
> On 16/08/2018 16:26, Martín Ferrari wrote:
>> We could also change the default in the next debhelper compat mode;
>> dunno how this is normally handled, but it would be good to coordinate
>> so this change is documented.. In that
On 16/08/2018 16:26, Martín Ferrari wrote:
> Hi Clément,
>
> On 13/08/18 11:01, Clément Hermann wrote:
>
>> It happened after Debcamp, but here is the MR:
>> https://salsa.debian.org/go-team/packages/dh-golang/merge_requests/3
>
> I just took a look. I left a smal
On Tue, 10 Jul 2018 13:51:35 +0200 =?UTF-8?Q?Cl=c3=a9ment_Hermann?=
wrote:
> On 10/07/2018 12:40, Jonathan Dowland wrote:
> > Hey folks,
>
> > I was pleased to see the last LXD dependency that we were tracking has
> > finally made it into Debian, so the path is likely clear for LXD itself
> > now
On 22/07/2018 23:12, Clément Hermann wrote:
> Hi !
>
> On 22/07/2018 16:49, Shengjing Zhu wrote:
>> On Sun, Jul 22, 2018 at 10:34 PM Michael Stapelberg
>> wrote:
>>>
>>> There was a discussion on the pkg-go mailing list titled “honoring
>>> DH_G
Hello,
On 03/08/2018 04:23, Sean Whitton wrote:
> Hello,
>
> On Thu 02 Aug 2018 at 12:16PM +0800, Clément Hermann wrote:
>
>> "as verbose as reasonably possible" seems incompatible with "maximally
>> verbose
>> output", at least in some cases
Package: debian-policy
Version: 4.2.0.0
Severity: normal
Hi,
4.9 states:
The package build should be as verbose as reasonably possible.
This means that ``debian/rules`` should pass to the commands it
invokes options that cause them to produce maximally verbose
output.
"as verbose
Hi,
On 31/07/2018 17:28, Free Ekanayaka wrote:
> Hello Clement,
>
> dqlite upstream and LXD team member here.
>
> Please note that dqlite is going through a bit of change, which I
> started to merge yesterday. So a few of the ITPs you have filed will no
> longer make sense.
Thanks a lot for the
Package: sbuild
Version: 0.77.0-3
Severity: normal
Hi,
while following https://www.eyrie.org/~eagle/notes/debian/sbuild.html to
create a sbuild setup using btrfs, the sbuild creation on a btrfs
subvolume fails:
sbuild-createchroot --arch=amd64 --include=debhelper,eatmydata \
--components=mai
Package: apparmor-notify
Version: 2.12-5
Severity: normal
aa-notify refers to wiki.ubuntu.com in the notifications.
We should make sure it's using a debian page instead - this is actually
configurable via message_footer in latest upstream version (used to be
hardcoded).
Cheers,
-- System Inform
Hi !
On 22/07/2018 16:49, Shengjing Zhu wrote:
> On Sun, Jul 22, 2018 at 10:34 PM Michael Stapelberg
> wrote:
>>
>> There was a discussion on the pkg-go mailing list titled “honoring
>> DH_GOLANG_EXCLUDES for sources” a while ago, started by Clément (cc'ed).
>>
>
> Ah, right, I thought I've rea
Hi !
On 10/07/2018 12:40, Jonathan Dowland wrote:
> Hey folks,
> I was pleased to see the last LXD dependency that we were tracking has
> finally made it into Debian, so the path is likely clear for LXD itself
> now (unless we need to catch up on some newer dependencies since the
> analysis was d
Package: pkg-perl-tools
Version: 0.45
Severity: wishlist
Hi,
when trying to modify DPT_PACKAGES for some hacking on our meta.git, it
took me a while to figure out I had both ~/.dpt.conf and
~/.config/dpt.conf.
It's a trap! The vars in .config/dpt.conf have precedance over the ones
in ~/.dpt.conf
Hi,
On 06/04/2018 04:01, Hideki Yamane wrote:
> Hi Perl people,
>
> Could you help us to check patches for embedded Perl code in debootstrap?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871835
>
> It would improve to make debootstrap faster a lot, but we also afraid to
> break someth
Le February 17, 2018 10:48:38 PM UTC, Didier 'OdyX' Raboud a
écrit :
>Package: lists.debian.org
>Severity: wishlist
>
>The debian.ch association (recognized TO) uses the
>'commun...@lists.debian.ch'
>list since, on privately-owned infrastructure. It's General Assembly
>has
>concluded that a hosti
On 07/02/2018 11:39, Pete Heist wrote:
>
> Ah, ok. IRTT has an API, but it's not published yet. I think a
> binary-only package may be better at this point, and a separate source
> package later when that’s ready? If you agree, could you suggest a
> simple, current binary package hosted on github
On 03/02/2018 16:52, Clément Hermann wrote:
> Hi,
> Is there anything regarding lxc-team packaging style/workflow I should
> be aware of? From what I saw, the workflow seems to be using gbp with
> pristine star branch, UNRELEASED target distribution until the package
> is ready to
Hi,
I've resumed active work on LXD, the last dependency
(golang-gopkg-lxc-go-lxc.v2 - #883488) is almost done (pending review
and upload).
Regarding lxc-go, I suggest we archive the previous attemps, since it
will live in pkg-go repository (using gitlab Archive feature on Salsa).
Same for the l
Hi!
The last missing dependency for LXD should be ready to upload,
hopefully. If a DD could have a look at it and upload it that would be
awesome.
Martín, maybe preferably you since you already had a first look at it ?
Cheers!
--
nodens
Control: close 839748
On 28/12/2017 17:13, gregor herrmann wrote:
> On Thu, 28 Dec 2017 16:00:17 +0000, Clément Hermann wrote:
>
>> Format: 1.8
>> Date: Mon, 18 Dec 2017 19:33:18 +0100
>> Source: golang-gopkg-flosch-pongo2.v3
>> Binary: golang-gopkg-flosch-pongo2.
On 21/12/2017 10:31, Evgeni Golov wrote:
I also started working on golang-gopkg-lxc-go-lxc.v2-dev (ITP: #883488).
That's the last dependancy for LXD.
>>>
>>> And it's waiting for review and upload as well, in the pkg-go repository.
>>>
>>
>> I'm almost done, hopefully will have
On 17/12/2017 21:39, Clément Hermann wrote:
> On 04/12/2017 21:40, Clément Hermann wrote:
>> So, I did some work on golang-gopkg-flosch-pongo2
>> <https://anonscm.debian.org/cgit/pkg-go/packages/golang-gopkg-flosch-pongo2.git/>
>> (#839748), since I had no answer.
>
Hi,
Time for a new status update, I guess.
On 04/12/2017 21:40, Clément Hermann wrote:
> So, I did some work on golang-gopkg-flosch-pongo2
> <https://anonscm.debian.org/cgit/pkg-go/packages/golang-gopkg-flosch-pongo2.git/>
> (#839748), since I had no answer.
> It should be fit
On 17/12/2017 16:40, Clément Hermann wrote:
> Hi !
>
> On 03/12/2017 23:39, Clément Hermann wrote:
>
>> I just uploaded my fixes and pushed the missing branches/tags.
>>
>> All it needs now is rewiewing, signed tag and upload, hopefully.
>>
>
> I firs
Hi !
On 03/12/2017 23:39, Clément Hermann wrote:
> I just uploaded my fixes and pushed the missing branches/tags.
>
> All it needs now is rewiewing, signed tag and upload, hopefully.
>
I first did that, but discussion with Tincho and Jonathan on IRC made me
reset the repo complet
Hi !
Time for a status update on this one, hopefully !
On Fri, 13 Oct 2017 13:36:47 +0200 Clément Hermann
wrote:
>
> I see there are only a couple dependancies left on the wiki page. Do you
> need help ?
> I'm not a Go expert, but I would really like to see LXD in Debian.
>
1 - 100 of 124 matches
Mail list logo