Package: sbuild
Previous-Subject: Re: seccomp woes
Original-To: debian-de...@lists.debian.org
On Fri, Jul 19, 2019 at 11:28:36PM -0300, gregor herrmann wrote:
> On Sat, 20 Jul 2019 00:21:10 +0200, Christoph Biedl wrote:
>
> > * Centralize the list of supported archs in the seccomp packages. By
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission
Submission-Type: new
Site: repo.iut.ac.ir
Type: leaf
Archive-architecture: amd64 arm64
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: ITCenter Software Group
Country: IR Iran, Islamic
control: forcemerge 932199 932260
Am Donnerstag, den 18.07.2019, 12:44 + schrieb Dmitry Bogatov:
> control: forcemerge 932199 932266
I guess you actually meant #932260 which is my filed bug.
#932266 is an ITP.
>
>
> [...]
> By the way, lightdm seems (according to apt-file) to not
Update: Confirmed that enabling CSM does not solve this stolen memory
issue. Additionally, neither does i915.fastboot=1 <- that one was
only tried for the sake of completeness, because several forum posts
said it did the trick.
$ cat /proc/mtrr
reg00: base=0x0 (0MB), size=32768MB,
Package: olive-editor
Version: 20190502-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
After installing version 20190502-2 of the olive-editor package I found that
the program failed to
Source: squid-deb-proxy
Severity: important
Tags: patch
Dear Maintainer,
squid-deb-proxy fails to start due due to the conf file not being allowed by
apparmor:
Jul 20 16:28:48 Tardis squid: FATAL: Unable to open configuration file:
/etc/squid-deb-proxy/squid-deb-proxy.conf: (13) Permission
Control: affects -1 linux-image-4.19.0-5-amd64 linux-image-4.19.0-1-amd64
linux-image-4.9.0-9-amd64 linux-image-4.9.0-1-amd64
Adding the specific kernel packages as well as attaching /proc/iomem the
/proc/iomem output that is probably necessary to resolve this bug.
Cheers,
Nicholas
Package: node-mixin-deep
Version: 1.1.3-3
Severity: important
Dear Maintainer,
node-mixin-deep 1.1.3-3 is affected by a prototype pollution vulnerability:
https://snyk.io/vuln/SNYK-JS-MIXINDEEP-450212
https://github.com/jonschlinkert/mixin-deep/issues/6
Please upgrade to either 1.3.2 or 2.0.1.
On Tuesday, July 9, 2019 11:50:26 AM EDT Matthias Klose wrote:
> On 09.07.19 00:31, Scott Kitterman wrote:
> > Ben file:
> >
> > title = "python-defaults";
> > is_affected = .depends ~
> > /python|python-minimal|python-dev|libpython-dev|libpython-stdlib|python-d
> >
Package: tigervnc-standalone-server
Version: 1.9.0+dfsg-3
Severity: important
This is Armbian buster running on an Odroid-C2. Confirmed package is
working in an amd64 VM.
kjotte@donatello:~$ vncserver :1 -verbose -geometry 1024x600 -depth 16
/usr/bin/Xtigervnc :1 -desktop
intrigeri:
> the current code I have that does exactly this uses WWW::Curl
> instead
As Ian requested, here is that code:
https://git.tails.boum.org/perl5lib/tree/lib/Tails/Download/HTTPS.pm
(note that this code is a bit more complicated than you want because
IIRC it takes care of problems
hello.. .
After few days fighting with gnupg on Debian Strech to search and upload
fingerprints finally the solutions was upgrade the gnupg on my Debian
Strech using the repository of Debian Buster.
Thats solve all my problems...
Regards,
Pablo
signature.asc
Description: OpenPGP
Now properly formatted such that the html output is ok.
$ echo $XDG_SESSION_TYPE
wayland
$ echo $DESKTOP_SESSION
gnome
$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3
After taking a look at the reason why they dropped support for loading
.Xresources by default (cf.
$ echo $XDG_SESSION_TYPE
wayland$ echo $DESKTOP_SESSION
gnome$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3
After taking a look at the reason why they dropped support for loading
.Xresources by default (cf.
https://bugzilla.redhat.com/show_bug.cgi?id=1225384),
I decided to test whether
Package: iptables
Version: 1.8.2-4
Severity: critical
Tags: a11y
Justification: breaks the whole system
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale:
Package: wnpp
Severity: wishlist
Owner: Daniel Leidert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: ruby-jekyll-paginate-v2
Version : 1.9.4
Upstream Author : Sverrir Sigmundarson
* URL : https://github.com/sverrirs/jekyll-paginate-v2
* License
On Wed, 24 Oct 2018 06:03:21 +0200, Helmut Grohne said:
> Hi Hubert,
> On Tue, Oct 23, 2018 at 11:02:13PM -0400, Hubert Chathi wrote:
>> Thanks for filing this issue. Olm 3 was released today, which has
>> new Python bindings, and which will make python-olm arch-dependent.
>> I'll take a look
Package: amanda-client
Version: 1:3.5.1-2+b2
Severity: normal
Dear Maintainer,
Upgrade to 3.5.102+b2 from 3.3.9-5 changes /etc/amandahosts to root:root. This
breaks bsdtcp auth. Permissions need to remain backup:backup.
-- System Information:
Debian Release: bullseye/sid
APT prefers
Hi,
(after I've started to play with dgit today — and very much like it so
far! — a friend pointed me to this bug)
Ian Jackson:
> The ftpmaster api service is currently provided over HTTP over TLS,
> based on with a standard X.509 web PKI cert from Let's Encrypt.
> We want, instead, those API
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 :
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 :
"Debian Bug Tracking System" writes:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 932491:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932491.
I just checked and gzip.open has the same problem with python3, while
with python2 I get
Package: wnpp
Owner: Arthur Diniz
Severity: wishlist
* Package name: commit-helper
Version : 3.4.18
Upstream Author : Arthur Diniz
* URL : https://github.com/andre-filho/commit-helper
* License : GPL-3
Programming Lang: Python
Description : Helps you
Package: wnpp
Severity: wishlist
Owner: Arthur Diniz
* Package name: commit-helper
Version : 3.4.18
Upstream Author : Arthur Diniz
* URL : https://github.com/andre-filho/commit-helper
* License : GPL-3
Programming Lang: Python
Description : Helps you
What I'm seeing seems kind of related to the topic of XSA-300. Mainly
something ballooning out pages.
The Debian Wiki advises reducing the amount of memory used by Domain-0.
Perhaps the Debian Wiki should be advising to try to keep the Domain-0
maximum substantially higher than the actual
Package: python3-apt
Version: 1.9.0
Severity: normal
The following script segfaults if python3-apt is installed, but
completes if not. Replacing lzma.open with open (and replacing
Sources.xz with Sources) also makes the segfault go away. It seems to
be the same with python3-apt 1.8.4. I didn't
Control: reassign -1 libblockdev-crypto2
Control: found -1 2.20-7
Control: fixed -1 2.22-1
Control: affects -1 gnome-disk-utility
Control: affects -1 udisks2
Control: tag -1 + patch
Hi,
it turns out this is caused by a bug in libblockdev, which is fixed in
sid already (although it seems like
Package: bc
Version: 1.06.95-9+b3
Severity: minor
Steps to reproduce:
1. Run bc with no arguments
2. Type some decimal digits, "3939" say, and do not hit return.
3. Press ^C to cancel the half-written command
4. Press ^D to try to quit bc
Expected behaviour: bc silently exits.
Observed
Hi guys,
Thank you very much for filing this bug report and
trying to make Debian more reliable.
I agree with Patrick and Philipp.
When "apt-get update" fails, it should not return
an error status of 0.
Scripts routinely check the exit status of
command, and assume they worked if 0 was
On Saturday, 20 July 2019 1:09:11 AM AEST intrigeri wrote:
> Done (0.10.10-0.2). This was my first attempt at using dgit to NMU so
> let's hope I did not bork it.
>
> I'm attaching the 3 commits I did on top of 0.10.10-0.1.
Awesome, thank you. I've just realised that we had no _cachefilesd_ on
Package: wnpp
Severity: wishlist
Owner: Kartik Kulkarni
* Package name: node-solid-rest
Version : 1.0.7
Upstream Author : Jeff Zucker
* URL : https://github.com/jeff-zucker/solid-rest.git
* License : (MIT/X)
Programming Lang: javascript
Description :
Package: dh-lua
Version: 25+nmu1
Severity: wishlist
Tags: patch
Dear Maintainer,
Since Lua 5.4 recently landed in experimental it would be good if dh-lua
was aware of this.
The attached patch makes Lua 5.4 work as a target when building for
multiple Lua versions.
-- System Information:
Debian
Package: wnpp
Severity: wishlist
Owner: Kartik Kulkarni
* Package name: node-solid-rest
Version : 1.0.7
Upstream Author : Jeff Zucker
* URL : https://github.com/jeff-zucker/solid-rest.git
* License : (MIT/X)
Programming Lang: javascript
Description:
I think 2 makes a lot of sense.
On Fri, Jul 19, 2019, 8:27 PM Jesse Smith
wrote:
> This is an interesting issue. I think this is what is happening:
>
> 1. update-rc.d wants to disable the osspd service. To do this is creates
> a file called /etc/init/osspd.override.
>
> 2. update-rc.d then
Package: wnpp
Severity: wishlist
Owner: Daniel Leidert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
* Package name: ruby-jekyll-optional-front-matter
Version : 0.3.0
Upstream Author : Ben Balter
* URL : https://github.com/benbalter/jekyll-optional-front-matter
*
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 :
This is an interesting issue. I think this is what is happening:
1. update-rc.d wants to disable the osspd service. To do this is creates
a file called /etc/init/osspd.override.
2. update-rc.d then calls insserv. insserv sees that the osspd script
normally starts in runlevels "2 3 4 & 5", but
Package: isso
Version: 0.12.2-2
Severity: important
Dear Maintainer,
* What led up to the situation?
I tried to use isso by starting is via systemd.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I started isso via systemd (systemctl start isso) which then
The assumption here, that the user can run "make check
insserv=/sbin/insserv" and have it run the testsuite against the
installed binary is correct. This does work.
The problem encountered in the bug report is an older version of insserv
is installed at /sbin/insserv. The older copy does not
gregor herrmann writes ("Re: Bug#932465: dgit cowbuilder' fails with
"unrecognized option""):
> On Fri, 19 Jul 2019 19:56:32 +0100, Ian Jackson wrote:
> > In the meantime, gregor (and anyone else reading this):
> > I think a workaround is to pass this command-line option to dgit:
> >
> >
Control: tags 928759 pending
Peter Powell wrote...
> You are shipping version 2.0.27 of InspIRCd which is now outdated as
> version 3.0.1 of InspIRCd was recently released. The v2 branch of
> InspIRCd is now only receiving security updates and will be considered
> EOL from 2020-01-01.
Now
Package: gdisk
Version: 1.0.3-1.1
Severity: wishlist
Dear Maintainer,
A new upstream version 1.0.4 was released for gdisk more than a year
ago. Upstream's changelog suggest it's worth to pick it:
+1.0.4 (7/5/2018):
+-
+
+- Added some explicit copy constructors and made some
Hi,
since there is no bionic/train (etc), ubuntucloud_withdefault allows you
to say bionic:train and get bionic-updates/train ; I think this is a
handy shortcut, YMMV :)
The attached patch is the tip of ubuntucloud_withdefault against master,
mostly so anyone following this bug can see what I
Source: cloud-utils
Version: 0.29-1
Severity: normal
Dear Maintainer,
your package has an install dependency on the file package, and
checking the sources it seems file is called with one of the
-z/--uncompress-noreport or -Z/--uncompress options.
Now that the file program has seccomp support
Hello
If we don't receive more information on this bug, i would consider
closing this bug.
Greetings,
Marcos
Package: cracklib-runtime
Version: 2.9.6-2
Severity: normal
Dear Maintainer,
your package has an install dependency on the file package, and
checking the sources it seems file is called with one of the
-z/--uncompress-noreport or -Z/--uncompress options.
Now that the file program has seccomp
please move powerdot to -extra!
Moved for tonight's build. Thanks for doing the search. -k
Package: devscripts
Version: 2.19.5~bpo9+1
Severity: wishlist
$ gbp dch --since=dgit/dgit/sid && tagpending && git checkout debian/changelog
^ ouch
This would be more effectively and less messily done with some simple
search of git-log for Closes: tags.
If you think this is a good idea I may
On Fri, 25 Jan 2019 10:17:43 +0100 Paride Legovini wrote:
> Gürkan Myczko wrote on 25/01/2019:
> > Hello
> >
> > My collegues would like to know if this will make it into buster or not?
> >
> > Best,
>
> Hello Gürkan,
>
> I very much doubt it will, unfortunately: there are still a lot of
>
Source: dgit
Version: 9.3
Severity: wishlist
Now that we have split brain maybe we want a quilt mode "make linear
patches, split brain, my d/patches in maintainer view is empty". This
would be a variant on linear, smash, auto, and (the nonexistent)
debcherry.
This is most useful with
Package: git-debpush
Version: 9.3
It would be nice to check that the patches are right. (In
gbp/unapplied, that they apply and are up to date.)
This would involve git-apply, at the very least. Running gbp pq would
add an unwanted dependency and also it is very slow. The main
reason dgit and
Package: git-debpush
Version: 9.3
User: d...@packages.debian.org
Usertags: rsn
As I wrote in private email:
For gbp and unapplied, I think it would be very sensible to check that
the upstream files are treesame in master and upstream. (For gbp,
ignoring /.gitignore)
I think this may be a
Matthew Vernon writes ("Bug#932322: A different approach based on suite-map"):
> My revised approach is to apply aptget-suite-rmap before testing against
> suite_re, meaning that suite_re can be left untouched[0], which I think
> you think is desirable :). This is its own commit, common to both
Source: dgit
Version: 9.2
Control: affects -1 src:git
User: debian...@lists.debian.org
Usertags: needs-update
git changed
Couldn't find remote ref
to
couldn't find remote ref
and this broke our test case.
9.3 is still broken. Upload will follow shortly.
Ian.
--
Ian JacksonThese
Package: scdaemon
Version: 2.2.12-1
Severity: wishlist
Tags: patch
Dear Maintainer,
I would like to add a USB VID:PID pair to the scdaemon package, please find a
diff attached.
-- System Information:
Distributor ID: PureOS
Description:PureOS
Release:8
Codename: green
Package: shorewall6
Version: 5.2.3.2-1
Severity: normal
Tags: patch
Hi,
running sysvinit instead of systemd, I'm relying on the packages init script to
work. However:
8<--
# /etc/init.d/shorewall6 start
/etc/init.d/shorewall6: line 20: test: /sbin/shorewall: binary operator
Package: wnpp
Severity: wishlist
Owner: Enkelena Haxhiu
* Package name: node-ulid
Version : 2.3.0
Upstream Author : Alizain Feerasta
* URL : https://github.com/ulid/javascript.git
* License : Expat
Programming Lang: Nodejs
Description :
Control: reopen -1
The change was reverted in debhelper/12.2.3 (see #932073).
Hello Hugo,
Hugo Lefeuvre kirjoitti 19.7.2019 klo 21.21:
> I had a look at the changes, everything fine. Manual smoke tests fine as
> well. I'm pretty sure there are still bugs in there, pysolfc breaks very
> easily (that's the main reason why I kept delaying this update for such a
> long time).
On Fri, Jul 19, 2019 at 03:45:32PM +0200, Laurent Bigonville wrote:
> Source: shadow
> Version: 1:4.7-1
> Severity: normal
> Since 1:4.7-1, /etc/securetty is not present on the system anymore and
> since then pam_unix complains that the file is missing:
> sudo[11488]: pam_unix(sudo:auth):
close 912140 1:6.2.0~rc1-1
thanks
Hi,
On Fri, Jul 19, 2019 at 09:51:40PM +0200, Axel Beckert wrote:
> Rene Engelhard wrote:
> > On Sun, Nov 18, 2018 at 07:11:03PM +0100, Rene Engelhard wrote:
> > > But so we can remove --package $DPKG_MAINTSCRIPT_PACKAGE without a risk
> > > anyway:
> > > dpkg
Control: tags -1 patch
Hi
On 15-07-2019 04:24, Shannon Dealy wrote:
> After upgrading from Stretch to Buster, I was unable to use S3QL with any of
> my Amazon S3 buckets. All attempts to access gave errors like:
>
> ERROR: Can't connect to backend: unable to resolve hostname
>
> I was
>
> The CFITSIO support has been re-enabled in the gdal package and will be
> included in the next upload. Note that it has only been enabled on the
> experimental branch for GDAL 3.x, I don't think it's worth it to enable
> it for GDAL 2.x as it will be replaced by 3.x after the transition to
Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta
* Package name: speedtest
Version : 0.0~git20190115.3c3e16a-1
Upstream Author : Ruslan Lopatin
* URL : https://github.com/surol/speedtest-cli
* License : Expat
Programming Lang: Go
Description :
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-de...@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see its Vcs-Git entry.
The binary packages are:
Package: adminer
Architecture: all
Depends:
Hi Rene,
Rene Engelhard wrote:
> On Sun, Nov 18, 2018 at 07:11:03PM +0100, Rene Engelhard wrote:
> > But so we can remove --package $DPKG_MAINTSCRIPT_PACKAGE without a risk
> > anyway:
> > dpkg | 1.16.18 | oldoldstable | source, amd64, armel,
> > armhf, i386, ia64,
Source: ffmpeg
Version: 7:4.1.3-1
Severity: important
Tags: security upstream fixed-upstream
Hi,
The following vulnerability was published for ffmpeg, it is fixed in
the 4.4.1 release (and was previously fixed already in 3.2 series and
thus was already included in DSA-4449-1).
Control: tags -1 moreinfo
Hi Stefan
On 16-07-2019 11:12, Stefan Kangas wrote:
> Package: release-notes
> Severity: minor
>
> In Section 4.6.1 of the Release Notes for buster, this command is suggested:
>
> dpkg -l "linux-image*" | grep ^ii | grep -i meta
>
> I believe this should be:
>
>
El vie., 19 de jul. de 2019 a la(s) 16:20, Andrej Shadura (
andrew.shad...@collabora.co.uk) escribió:
> Hi,
>
> On 19/07/2019 16:15, eamanu15 . wrote:
> > Hello Andrej,
> >
> > I am updating to 36d6229 sha git version. I want to upload to
> experimental
> >
> > The error is because is compiled
Control: tags -1 pending
Hi Chiara,
Thanks for your work on the FITS driver and clarifying the license issue.
The CFITSIO support has been re-enabled in the gdal package and will be
included in the next upload. Note that it has only been enabled on the
experimental branch for GDAL 3.x, I don't
On Fri, Jul 19, 2019 at 12:05:12PM +0200, Diego M. Rodriguez wrote:
> * Package name: python-jellyfish
> Version : 0.6.1-1
> Changes since the last upload:
>
> [ Ondřej Nový ]
> * d/control: Set Vcs-* to salsa.debian.org
>
> [ Jelmer Vernooij ]
> * Remove unnecessary
On 19/07/2019 20.50, Christoph Biedl wrote:
> Étienne Mollier wrote...
>
>>ngIRCd tries to connect to to the other server on the
>> ^
> Thanks for reporting, this exists in a few more places as well.
Wow, you are right, according to `rgrep '\(\<[^
Hi,
On 19/07/2019 16:15, eamanu15 . wrote:
> Hello Andrej,
>
> I am updating to 36d6229 sha git version. I want to upload to experimental
>
> The error is because is compiled with Werror and fail
> for a warning:
>
> ../src/libcamera/process.cpp:74:13: error: ignoring return value of
>
On Fri, 19 Jul 2019 19:56:32 +0100, Ian Jackson wrote:
> In the meantime, gregor (and anyone else reading this):
>
> I think a workaround is to pass this command-line option to dgit:
>
> --cowbuilder!:--no-source-only-changes
I can confirm that
dgit --rm-old-changes
Hello Andrej,
I am updating to 36d6229 sha git version. I want to upload to experimental
The error is because is compiled with Werror and fail
for a warning:
../src/libcamera/process.cpp:74:13: error: ignoring return value of
‘ssize_t write(int, const void*, size_t)’, declared with attribute
Thanks. Looks pretty good. My review comments:
> +for c in "${force[@]}"; do
> +if [ "$c" = "$check" ]; then
> +check_is_forced=true
> +break
> +fi
> +done
It is possible, including here I think, to do something like this:
case " ${force[*]} "
On Thu, 2019-07-18 at 16:30 -0300, Herbert Fortes wrote:
> On 7/18/19 4:19 PM, Salvatore Bonaccorso wrote:
[...]
> > As discussed in the backlog of this bug, this should actually have
> > been 3:3.4.4.1-*5*+deb9u1, but I see
> >
> > gthumb | 3:3.4.4.1-6+deb9u1 | oldstable-new |
Control: retitle -1 gdnsd: CVE-2019-13952
Hi,
Wrong initial triage actually on my side, when checking the code.
CVE-2019-13951 only affects versions after 3.x so not affecting any
gdnsd version in Debian. Sorry about that.
Retitiling the bug accordingly.
Regards,
Salvatore
Control: tags -1 + moreinfo
On Fri, 2019-07-19 at 13:35 +0200, Santiago Vila wrote:
> Dear Release Managers:
>
> Please leave this package unapproved for now.
>
> It has some side-effects (like firefox FTBFS) which need to be
> investigated:
>
>
On 19.07.19 10:43, John Paul Adrian Glaubitz wrote:
> On 7/19/19 10:33 AM, Hilmar Preuße wrote:
Hi,
>> Yes, but I'm just a DM, hence I'd need to open an RT to get access. Last
>> time I did so, it took > 2 month to get access: [rt.debian.org #7752].
>
> I see. I can send the request for you if
Package: src:dgit
Severity: normal
Dear Maintainer,
Based on the discussion we’re having right now, to enable to use dgit
push with a repo where git-lfs has previously been used, the following
steps are needed:
* file a bug against git-lfs package
* communications *probably* need to be
Control: reassign -1 cowbuilder
Control: retitle -1 cowbuilder: Please implement --no-source-only-changes
gregor herrmann writes ("Bug#932465: dgit cowbuilder' fails with "unrecognized
option""):
> AFAIK, pbuilder knows about --no-source-only-changes but cowbuilder
> doesn't .. (So it can be
Source: exiv2
Version: 0.25-4
Severity: important
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/pull/943
Control: found -1 0.25-1
Control: found -1 0.25-3.1+deb9u1
Hi,
The following vulnerability was published for exiv2.
CVE-2019-13504[0]:
| There is an out-of-bounds read in
Control: tags 932462 confirmed upstream
Étienne Mollier wrote...
>ngIRCd tries to connect to to the other server on the
> ^
Thanks for reporting, this exists in a few more places as well.
Christoph
signature.asc
Description: PGP signature
On 19.07.19 17:41, Moritz Muehlenhoff wrote:
Hi,
> Please see:
> http://bugs.proftpd.org/show_bug.cgi?id=4372
> https://github.com/proftpd/proftpd/pull/816
>
The patch from upstream applies nicely to our master branch (and would
apply to the buster package too). I could upload the fix to Debian
Yes, rainloop is going to be modified soon
Le 19 juillet 2019 17:55:56 GMT+02:00, Luca Falavigna a
écrit :
>tags 931653 moreinfo
>thanks
>
>
>Il giorno lun 8 lug 2019 alle ore 23:09 Xavier Guimard
> ha scritto:
>> This package has no reverse dependencies, so it can safely be removed
>> from
Source: scheme-bytestructures
Version: 1.0.5-1
Severity: normal
Justication: Policy §12.5
X-Debbugs-CC: Vagrant Cascadian ,
ftpmas...@debian.org
Hi,
I just ACCEPTed scheme-bytestructures from NEW but noticed aligm.scm
has 2018 as the copyright year; this is not reflected in debian/
copyright.
Hi Juhani,
I had a look at the changes, everything fine. Manual smoke tests fine as
well. I'm pretty sure there are still bugs in there, pysolfc breaks very
easily (that's the main reason why I kept delaying this update for such a
long time).
Anyways, we can't delay this forever, so I went along
Package: dgit
Version: 9.3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
% dgit --gbp cowbuilder:(
Format `3.0 (quilt)', need to check/update patch stack
gzip: warning: GZIP environment variable is deprecated; use an alias or script
dgit: split brain
Helmut Grohne:
> Control: reopen -1
> Control: affects -1 + src:dropbear
>
> On Tue, Jul 16, 2019 at 08:42:09PM +, Debian Bug Tracking System wrote:
>>* dh_installinit: Fix regression where dh_installinit bailed
>> out on --name if only one of the acted on packages had an
>>
> - d/control: the list in Maintainers will receive bug reports and stuff
> related to the lifecycle of the package. Is that your intent?
Yes.
> - d/control: Vcs-* fields are for packaging. There is not issue to
> share upstream Git for that, but this means you should have some
> branch
https://mentors.debian.net/package/jool
How do I assign bug 931960 to this package?
Package: libgdal20
Severity: whishlist
Dear GDAL maintainers, libgdal20 is packaged in Debian 10 with the option
'--with-cfitsio=no' due to some license issues in CFITSIO (see [1]).
I have worked to an extension of the FITS driver in GDAL (see [2]), funded by a
European programme, aiming to
Source: suricata
Version: 1:4.1.4-2
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainers,
Your package has an autopkgtest, great. However, today it was reporting
a regression in systemd, because it failed to connect to
Package: ricochet-im
Version: 1.1.4-3
Followup-For: Bug #932150
Dear Maintainer,
I confirm, that Ricochet is working with these changes to it's apparmor
profile, despite some 'DENIED' messages in syslog.
Seems, this bug is fixed
Thanks.
-- System Information:
Debian Release: 10.0
APT
Package: ngircd
Version: 25-2
Severity: minor
Tags: patch
Dear Maintainer,
While reading ngircd.conf(5), I ran onto the following typo:
[SERVER]
Other servers are configured in [Server] sections. If
you configure a port for the connection, then this
ngIRCd tries
I confirm, that Ricochet is working with these changes to it's apparmor
profile, despite some 'DENIED' messages in syslog.
Seems, this bug is fixed
Best regards,
--
Constantin Dunayev
Package: pcmanfm
Version: 1.3.1-1
Distribution: stable
When xarchver is set as default archiver, and I try to compress files
in pcmanfm by right clicking over a file, and then click Compress, it
is not working.
The output in terminal is
xarchiver: Unknown option --add-to
This indicates the
On Fri, 2019-07-19 at 12:54 -0300, Herbert Fortes wrote:
> [...]
> > >>
> >
> > >> Uploaded.
> >
> > >
> >
> > > As discussed in the backlog of this bug, this should actually
> > have
> >
> > > been 3:3.4.4.1-*5*+deb9u1, but I see
> >
> > >
> >
> > > gthumb | 3:3.4.4.1-6+deb9u1 |
libvirt debug output:
Jul 19 19:07:25 pulsar libvirtd[12365]: EVENT_POLL_DISPATCH_HANDLE: watch=3
events=1
Jul 19 19:07:25 pulsar libvirtd[12365]: OBJECT_NEW: obj=0x5606e38e86f0
classname=virNetSocket
Jul 19 19:07:25 pulsar libvirtd[12365]: RPC_SOCKET_NEW: sock=0x5606e38e86f0
fd=40 errfd=-1
1 - 100 of 186 matches
Mail list logo