On Thu, 18 Jul 2013 03:45:29 +0200 Alois Mahdal wrote:
> Recently I discovered that Pixelizer from the Shutter editor does not
> reliably render the data unreadable.
A new version of shutter was reintroduced into Debian unstable. Please
install it and check if the issue still occurs. If it still
On Thu, 18 Jul 2013 03:36:49 +0200 Alois Mahdal wrote:
> I use shutter almost daily, and while it's really a great tool, there's
> one thing that has kept bugging me for a while:
>
> In the editor, it's really easy to "shoot yourself in the foot" by
> moving the base picture a few bits, which,
On Wed, 21 Oct 2009 16:32:38 +0200 Christoph Haas wrote:
> Shutter is the nicest screenshot program I have ever seen. But there is
> one little issue. I'm using two monitors and when I want to make a
> screenshot then shutter takes the contents of my left monitor, puts it
> onto the right monitor
Control: forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48
On Sat, 2022-02-19 at 07:31 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This appears to be caused by git 1:2.35.1-1 in unstable,
the autopkgtests regressed
Control: forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48
On Sat, 2022-02-19 at 07:31 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This appears to be caused by git 1:2.35.1-1 in unstable,
the autopkgtests regressed
Control: forwarded -1 https://github.com/mnauw/git-remote-hg/issues/48
On Sat, 2022-02-19 at 07:31 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This appears to be caused by git 1:2.35.1-1 in unstable,
the autopkgtests regressed
Paul Wise pushed to branch master at Debian Security Tracker / security-tracker
Commits:
def2c675 by Paul Wise at 2022-02-19T14:15:25+08:00
kvmtool hypervisor escape and host code execution
- - - - -
1 changed file:
- data/CVE/list
Changes:
=
data/CVE
Source: smartmontools
Version: 7.2-1
Severity: wishlist
Upstream has added some new configure and update-smart-drivedb options
that make the changes for #976696 (/usr vs /var split) more optimal.
I have included the upstream comments below, once the required upstream
version (not sure about the
Package: needrestart
Version: 3.5-5
Severity: serious
X-Debbugs-CC: syst...@packages.debian.org
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: cgroupv2
needrestart detects that user@1000.service needs to be restarted,
instead of that the pabs user sessions have outdated binaries.
Package: needrestart
Version: 3.5-5
Severity: serious
X-Debbugs-CC: syst...@packages.debian.org
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: cgroupv2
needrestart detects that user@1000.service needs to be restarted,
instead of that the pabs user sessions have outdated binaries.
Package: needrestart
Version: 3.5-5
Severity: serious
X-Debbugs-CC: syst...@packages.debian.org
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: cgroupv2
needrestart detects that user@1000.service needs to be restarted,
instead of that the pabs user sessions have outdated binaries.
On Wed, 2022-02-16 at 16:51 +, Simon McVittie wrote:
> If the maintainers of dak (our eternally overworked ftp team) want to
> pick up build logs as first-class artifacts produced by both failed
> and successful builds, they're welcome to do so (and then handling my
> prototype of test
Simon McVittie wrote:
> Relatedly, I would like to be able to capture some information about
> builds even if (perhaps especially if) the build fails.
That is a good point that I hadn't considered.
> so that failing builds can also produce artifacts, to help the
> maintainer and/or porters to
Simon McVittie wrote:
> Relatedly, I would like to be able to capture some information about
> builds even if (perhaps especially if) the build fails.
That is a good point that I hadn't considered.
> so that failing builds can also produce artifacts, to help the
> maintainer and/or porters to
by 1005780
Control: close 1005416 0.3.10-1
On Sun, 2022-02-13 at 09:58 +0800, Paul Wise wrote:
> The upgrade of libusb-1.0 from 2:1.0.24-3 to 2:1.0.25-1 means fwupd
> crashes with a SIGSEGV from one to two hours after it is started.
Upstream says that Debian needs to update libgusb to 0.3.9 or
On Sun, 2022-02-13 at 14:13 -0800, Vagrant Cascadian wrote:
> * Split build metadata into a separate file or archive
>
> Some of the debian-installer packages generate tarballs that are not
> .deb files and are included in the .changes files when uploading to
> the archive; making a similar
On Sun, 2022-02-13 at 14:13 -0800, Vagrant Cascadian wrote:
> * Split build metadata into a separate file or archive
>
> Some of the debian-installer packages generate tarballs that are not
> .deb files and are included in the .changes files when uploading to
> the archive; making a similar
Package: fwupd
Version: 1.7.4-2
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate
The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on
Control: reopen -1
On Sat, 2022-02-12 at 23:51 +, Nis Martensen wrote:
> * bin/reportbug, reportbug/debbugs.py: add option to browse archived bugs
> (Closes: #995231)
> * man/reportbug.1: document new --archive option
I guess my feature request wasn't clear enough, but I wanted
Package: fwupd
Version: 1.7.4-2
Severity: important
Usertags: crash
Control: found -1 1.5.7-5
X-Debbugs-CC: libusb-...@packages.debian.org
The upgrade of libusb-1.0 from 2:1.0.24-3 to 2:1.0.25-1 means fwupd
crashes with a SIGSEGV from one to two hours after it is started.
I am not sure if the
On Thu, 2022-02-10 at 12:36 -0800, Forest wrote:
> No comments? The site itself says to come here to report problems.
> Is there a better place to report this one?
Thanks for the report, but this issue is already known:
https://bugs.debian.org/992258
--
bye,
pabs
On Tue, 2022-02-08 at 15:57 +0100, Raphael Hertzog wrote:
> We should trim the base system to be more container friendly
IIRC Helmut Grohne etc have already been working on this for years:
https://wiki.debian.org/Proposals/EssentialOnDiet
--
bye,
pabs
https://wiki.debian.org/PaulWise
Control: close 1004111
On Thu, 2022-02-10 at 11:38 -0600, Judah Richardson wrote:
> Yeah I haven't had any error messages for a couple weeks now so
> apparently whatever the issue is has been cleared up.
OK, closing the bug with this mail.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, 2022-02-09 at 12:26 -0600, Judah Richardson wrote:
> Fair. The package in Raspberry Pi OS lists you and someone else (I
> forgot the name, my apologies) as the maintainers. So either the
> Raspberry Pi OS' repo records are wrong, or the Foundation is simply
> using the upstream package as
Source: boost1.74
Severity: normal
Usertags: embed
Unicode 14 was released and unicode-data 14.0.0-1.1 was uploaded.
The boost1.74 source package contains very very outdated embedded
data copies of several files from Unicode 5.2.0:
$ head -n1 libs/spirit/workbench/unicode/*.txt
==>
user pkg-multiemdia-maintain...@lists.alioth.debian.org
usertags 740831 - drop-slv2
usertags 740832 - drop-slv2
usertags 740830 - drop-slv2
usertags 740496 - drop-slv2
user pkg-multimedia-maintain...@lists.alioth.debian.org
usertags 740831 + drop-slv2
usertags 740832 + drop-slv2
usertags 740830 +
Vagrant Cascadian wrote:
> Over the last several months, I and others have found quite a few
> packages that embed build paths via rpath when building with cmake.
This seems like the sort of thing that will be an ongoing problem, so
if it is detectable statically then a lintian warning might be
Vagrant Cascadian wrote:
> Over the last several months, I and others have found quite a few
> packages that embed build paths via rpath when building with cmake.
This seems like the sort of thing that will be an ongoing problem, so
if it is detectable statically then a lintian warning might be
On Thu, 2022-02-03 at 08:24 +0100, Hans Kilian wrote:
> I was wondering if you could make it possible to set the user's
> preferred language on your site?
This is already possible, there are several ways to do this:
Set your preferred language in your desktop session and use a browser
that
Control: fixed -1 libtorrent-rasterbar/2.0.5-1
On Wed, 2022-02-02 at 15:50 +0100, Christian Marillat wrote:
> Subject: Bugs closed in libtorrent-rasterbar 2.0.5
> Cc: 969780-cl...@bugs.debian.org, 992575-cl...@bugs.debian.org,
> 856600-cl...@bugs.debian.org, 987120-cl...@bugs.debian.org,
>
Control: fixed -1 libtorrent-rasterbar/2.0.5-1
On Wed, 2022-02-02 at 15:50 +0100, Christian Marillat wrote:
> Subject: Bugs closed in libtorrent-rasterbar 2.0.5
> Cc: 969780-cl...@bugs.debian.org, 992575-cl...@bugs.debian.org,
> 856600-cl...@bugs.debian.org, 987120-cl...@bugs.debian.org,
>
Source: zxing-cpp
Version: 1.2.0+git20211228+ds1-1~exp1
Severity: wishlist
Since upstream commit 8db14ee, the blackbox tests can be built without
Internet access, by building against the libfmt-dev Debian package, so
please enable BUILD_BLACKBOX_TESTS. Unfortunately the ReaderTest test
from
On Sun, 2022-01-30 at 20:40 +0100, Paul Gevers wrote:
> But this is only useful if the test actually passes. We don't want
> people to add the field if the test is broken. So if this is
> implemented, make sure the priority/certainty/whatever is low enough
> that people will *not* just blindly
On Sun, 2022-01-30 at 20:40 +0100, Paul Gevers wrote:
> But this is only useful if the test actually passes. We don't want
> people to add the field if the test is broken. So if this is
> implemented, make sure the priority/certainty/whatever is low enough
> that people will *not* just blindly
Package: lintian
Severity: wishlist
Usertags: feature
X-Debbugs-CC: autod...@packages.debian.org
I noticed while packaging some Python modules recently that they were
not tested by debci. This is because debci only tests source packages
that contain a Testsuite field. The autodep8 tool is able to
Package: lintian
Severity: wishlist
Usertags: feature
X-Debbugs-CC: autod...@packages.debian.org
I noticed while packaging some Python modules recently that they were
not tested by debci. This is because debci only tests source packages
that contain a Testsuite field. The autodep8 tool is able to
Control: severity -1 normal
Control: tags -1 + moreinfo
Control: retitle -1 unattended-upgrades: upgrade of chromium-browser and others
skipped on Raspberry Pi OS
On Thu, 20 Jan 2022 16:42:21 -0600 Judah Richardson wrote:
> This bug has showing up on this end in unattended-upgrades 2.8 on my
>
Control: severity -1 normal
Control: tags -1 + moreinfo
Control: retitle -1 unattended-upgrades: upgrade of chromium-browser and others
skipped on Raspberry Pi OS
On Thu, 20 Jan 2022 16:42:21 -0600 Judah Richardson wrote:
> This bug has showing up on this end in unattended-upgrades 2.8 on my
>
Control: fixed -1 4.0.3
On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote:
> Per email by Graham from 14 Nov 2020 this has been resolved.
Resolved upstream in 2020 but not in Debian until 2021.
> By now we have an even newer version 4.0.3.
Please use a versioned -done message next
Control: fixed -1 4.0.3
On Fri, 2022-01-28 at 20:07 -0600, Dirk Eddelbuettel wrote:
> Per email by Graham from 14 Nov 2020 this has been resolved.
Resolved upstream in 2020 but not in Debian until 2021.
> By now we have an even newer version 4.0.3.
Please use a versioned -done message next
On Fri, 2022-01-28 at 20:23 +, Zoom Video Communications wrote:
> if a critical CVE is discovered at some point after we release, it’s
> best not to publish which specific Zoom client version contains the
> vulnerability, as that essentially gives a roadmap to exploitation
> for hackers.
Package: how-can-i-help
Version: 17
Severity: wishlist
When installed packages are proposed to be removed from unstable or
stable etc, it would be interesting to have a notification from the
how-can-i-help too. For architecture-specific removals, the
notification should only happen if the
Package: how-can-i-help
Version: 17
Severity: wishlist
Sometimes when a package isn't migrating to testing but is outside the
migration window for the urgency used, so should have migrated to
testing, there isn't an RC bug yet because no-one has noticed the issue
yet, which means the autoremoval
Package: pypy-lib
Version: 7.3.6+dfsg-2
Severity: normal
Usertags: warnings
A recent upgrade of pypy/pypy-lib gave a syntax error:
Log started: 2022-01-26 00:19:15
apt-listchanges: Reading changelogs...
apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo
apt-listchanges:
On Sun, 2022-01-23 at 17:43 -0500, Theodore Y. Ts'o wrote:
> That only works if there are no other packages depending on those
> shared libraries which are coming from other source packages.
I don't think that is true, I believe you can put multiple things in
the depends section of an shlibs
Control: reopen -1
On Sun, 2022-01-23 at 11:48 +, Hilko Bengen wrote:
> * Remove virt-builder conffiles (Closes: #1004076)
This doesn't seem to have worked, I think the version number should be
the version where the removal is happening, not the version where the
conffile was dropped
Package: libddccontrol0
Version: 0.6.0-7
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate
The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete
On Sat, 2022-01-22 at 21:21 -0500, Sandro Tosi wrote:
> no disrespect, according to https://ftp-master.debian.org/ you are not
> part of the FTP master team; we would really like the input from that
> team (CC'ed) on how to structure this: after all, these packages are
> coded for their
Package: reportbug
Version: 11.2.0
Severity: wishlist
X-Debbugs-CC: ftp.debian@packages.debian.org
Control: affects -1 ftp.debian@packages.debian.org
When filing bugs against ftp.debian.org there is a menu
asking what kind of request the bug report is about:
1 ANAIS Package
On Fri, 2022-01-21 at 13:55 -0500, Theodore Ts'o wrote:
> Can we have better automated tooling, either in Lintian, or in when
> source packages are rebuilt, that can take care of this?
>
> The other thing that's perhaps considering here is that unfortunately,
> there are some upstreams that are
On Fri, 2022-01-21 at 10:06 +0100, Markus Blatt wrote:
> I assume that this version dependency was added when the packages
> were built some time ago.
Correct, see the dh_shlibdeps, dpkg-shlibdeps, deb-shlibs,
deb-symbols and dpkg-gensymbols manual pages for details.
> What is the recommend way
Martin Møller: since my last post on this issue, Carl Byington has
suggested I take over the libpst project and I have done that and have
moved the project to GitHub.
https://github.com/pst-format/libpst/
Please file an upstream issue explaining the problem. Please ensure you
attach a PST file &
Package: libguestfs-tools
Version: 1:1.46.2-4
Severity: normal
File: /etc/xdg/virt-builder/repos.d/opensuse.gpg
File: /etc/xdg/virt-builder/repos.d/opensuse.conf
File: /etc/xdg/virt-builder/repos.d/libguestfs.gpg
File: /etc/xdg/virt-builder/repos.d/libguestfs.conf
User: debian...@lists.debian.org
Package: openjdk-11-jre-headless
Version: 11.0.14+9-1
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate
The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these
Package: iproute2
Version: 5.16.0-1
Severity: minor
File: /usr/lib/tc/m_ipt.so
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
Tags: patch
iproute2 5.16.0-1 introduced a broken symlink.
It looks like what happened is the upstream file that was the target of
the symlink got
On Mon, 2022-01-17 at 18:38 +0100, наб wrote:
> I don't disagree, but /e/p.d/* can't be symlinks to /u/s.
I don't think that is correct (since systemd symlinks from /etc to
/usr), but if it were then just copying the files would work instead.
> However, please consider new, simplified, patch
On Mon, 2022-01-17 at 18:38 +0100, наб wrote:
> I don't disagree, but /e/p.d/* can't be symlinks to /u/s.
I don't think that is correct (since systemd symlinks from /etc to
/usr), but if it were then just copying the files would work instead.
> However, please consider new, simplified, patch
On Wed, 2022-01-19 at 18:43 +0200, Thomas Koch wrote:
> My package ships two convenience copies from autoconf-archive in it's
> m4 folder. Should I
In my experience with libpst, it had embedded copies of Python/boost
macros from autoconf-archive that were modified and the modifications
hadn't
On Wed, 2022-01-12 at 19:00 -0500, M. Zhou wrote:
> I've had some discussions with several fellow developers on suggesting Debian
> to buy some GPUs to extend its infrastructures for better GPU support.
Was there a plan for what to use these GPUs for?
Were they needed for driver/other package
Package: libopenjp2-7-dev
Version: 2.4.0-5
Severity: normal
File: /usr/lib/x86_64-linux-gnu/libopenjp3d.so
File: /usr/lib/x86_64-linux-gnu/libopenjpip.so
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
Tags: patch
libopenjp2-7-dev 2.4.0-5 introduced two broken symlinks.
It
Package: libopenjp2-7-dev
Version: 2.4.0-5
Severity: normal
File: /usr/lib/x86_64-linux-gnu/libopenjp3d.so
File: /usr/lib/x86_64-linux-gnu/libopenjpip.so
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
Tags: patch
libopenjp2-7-dev 2.4.0-5 introduced two broken symlinks.
It
On Sat, 2022-01-15 at 22:19 +0800, Wenbin Lv wrote:
> I decided to add this information to /doc/index instead of /support,
> because this information is useful to users only when they have chosen
> a particular manual to read, so it's better to keep the section in
> /support short and make it
On Sat, 2022-01-15 at 12:25 +0100, Thomas Goirand wrote:
> Just please make sure it doesn't conflict with:
> packages.debian.org/openstack-cluster-installer-cli
AFAICT there is nothing that conflicts, except the OCI acronym, which
seems to also be shared with the Open Containers Images
On Sat, 2022-01-15 at 12:25 +0100, Thomas Goirand wrote:
> Just please make sure it doesn't conflict with:
> packages.debian.org/openstack-cluster-installer-cli
AFAICT there is nothing that conflicts, except the OCI acronym, which
seems to also be shared with the Open Containers Images
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cloud@lists.debian.org
Control: block -1 by 1003372
* Package name: oci-cli
Version : 3.4.1
Upstream Author : Mike Ross and others at Oracle
* URL :
https
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cl...@lists.debian.org
Control: block -1 by 1003372
* Package name: oci-cli
Version : 3.4.1
Upstream Author : Mike Ross and others at Oracle
* URL :
https
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-cl...@lists.debian.org
Control: block -1 by 1003372
* Package name: oci-cli
Version : 3.4.1
Upstream Author : Mike Ross and others at Oracle
* URL :
https
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cl...@lists.debian.org
Control: block -1 by 1003372
* Package name: oci-cli
Version : 3.4.1
Upstream Author : Mike Ross and others at Oracle
* URL :
https
On Thu, 2022-01-13 at 20:54 +, John Scott wrote:
> You might like to have a look at this mail from Ben Hutchings:
> https://lists.debian.org/msgid-search/179d6d32466dd13962a3aab251c45242fbf2d8ae.ca...@decadent.org.uk
> The reason that none of the other Wi-Fi firmware packages have them is
>
On Thu, 2022-01-13 at 20:54 +, John Scott wrote:
> You might like to have a look at this mail from Ben Hutchings:
> https://lists.debian.org/msgid-search/179d6d32466dd13962a3aab251c45242fbf2d8ae.ca...@decadent.org.uk
> The reason that none of the other Wi-Fi firmware packages have them is
>
On Thu, 2022-01-13 at 20:54 +, John Scott wrote:
> You might like to have a look at this mail from Ben Hutchings:
> https://lists.debian.org/msgid-search/179d6d32466dd13962a3aab251c45242fbf2d8ae.ca...@decadent.org.uk
> The reason that none of the other Wi-Fi firmware packages have them is
>
On Thu, 2022-01-13 at 21:25 +0100, Mechtilde Stehmann wrote:
> Are there any hints to upload newer versions?
There are some hints about this on the team git policy page:
https://wiki.debian.org/Python/GitPackaging
Probably some other wiki pages are helpful too.
--
bye,
pabs
On Fri, 2022-01-14 at 02:23 +0800, Wenbin Lv wrote:
> The page I intended to edit was /support, not /doc. The change is
> online now at https://www.debian.org/support.en.html#doc
That looks reasonable, please also mention the documentation installed
in packages and that the ones on the website
On Fri, 2017-07-07 at 14:45 +1200, Ben Caradoc-Davies wrote:
> thermald.service is the only place where options such as --poll-
> interval can be set, so this file should be considered a package
> conffile. Because thermald.service is not a conffile, local changes
> to the command line are
Package: adequate
Version: 0.15.6
Severity: normal
Control: clone -1 -2 -3
Control: retitle -2 adequate: check systemd files for invalid users/groups
Control: retitle -3 adequate: check init scripts for invalid users/groups
dbus files, systemd units and init scripts can reference users or
groups.
Package: adequate
Version: 0.15.6
Severity: normal
Control: clone -1 -2 -3
Control: retitle -2 adequate: check systemd files for invalid users/groups
Control: retitle -3 adequate: check init scripts for invalid users/groups
dbus files, systemd units and init scripts can reference users or
groups.
On Tue, 2022-01-11 at 11:20 +, Neil Williams wrote:
> I might need to brush up on my Perl and make a patch for lintian which
> downloads the sec tracker JSON and checks the CVE list in the .changes
> file - warnings from lintian are more likely to get fixed prior to
> upload. Depends if you
On Tue, 2022-01-11 at 11:20 +, Neil Williams wrote:
> I might need to brush up on my Perl and make a patch for lintian which
> downloads the sec tracker JSON and checks the CVE list in the .changes
> file - warnings from lintian are more likely to get fixed prior to
> upload. Depends if you
On Tue, 2022-01-11 at 19:37 +0100, Paul Gevers wrote:
> So, I guess the text could be updated to reflect this? I *guess* the
> reason that the e-mail was sent was because the bug was closed with the
> upload. That resets the autoremoval timer (until the issue is fixed *in
> testing*). The
On Tue, 2020-08-04 at 11:56 +0100, s...@debian.org wrote:
> his package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
> binary packages with a Depends on GTK 2.
This bug has been fixed upstream in version 0.95 of mtr in unstable,
which supports both GTK 2 and GTK 3. So this just needs
Package: systemd
Version: 250.2-1
Severity: normal
File: /lib/systemd/system/dbus-org.freedesktop.oom1.service
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
There is now a broken symlink in the systemd package.
It looks like some parts of systemd-oomd were split out into the
Package: systemd
Version: 250.2-1
Severity: normal
File: /lib/systemd/system/dbus-org.freedesktop.oom1.service
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
There is now a broken symlink in the systemd package.
It looks like some parts of systemd-oomd were split out into the
Control: forwarded -1 https://github.com/traviscross/mtr/pull/411
https://github.com/traviscross/mtr/commit/aeb493e08eabcb4e6178bda0bb84e9cd01c9f213
Control: tags -1 + upstream patch
On Sun, 28 Nov 2021 16:51:05 +0100 Sven Joachim wrote:
> In the meantime upstream has accepted a pull request
Control: forwarded -1 https://github.com/traviscross/mtr/pull/411
https://github.com/traviscross/mtr/commit/aeb493e08eabcb4e6178bda0bb84e9cd01c9f213
Control: tags -1 + upstream patch
On Sun, 28 Nov 2021 16:51:05 +0100 Sven Joachim wrote:
> In the meantime upstream has accepted a pull request
Control: forwarded -1 https://github.com/fail2ban/fail2ban/issues/3098
https://github.com/fail2ban/fail2ban/commit/5ac303df8a171f748330d4c645ccbf1c2c7f3497
Control: tags -1 + upstream fixed-upstream
On Sat, 23 Oct 2021 23:15:13 +0200 Lucas Nussbaum wrote:
> During a rebuild of all packages in
Control: forwarded -1 https://github.com/fail2ban/fail2ban/issues/3098
https://github.com/fail2ban/fail2ban/commit/5ac303df8a171f748330d4c645ccbf1c2c7f3497
Control: tags -1 + upstream fixed-upstream
On Sat, 23 Oct 2021 23:15:13 +0200 Lucas Nussbaum wrote:
> During a rebuild of all packages in
Control: forwarded -1 https://github.com/fail2ban/fail2ban/issues/3059
https://savannah.gnu.org/bugs/?60937
https://git.savannah.gnu.org/cgit/mailutils.git/commit/?id=4befcfd015256c568121653038accbd84820198f
On Fri, 23 Jul 2021 19:44:08 + (UTC) Thorsten Alteholz wrote:
> According to
Control: forwarded -1 https://github.com/fail2ban/fail2ban/issues/3059
https://savannah.gnu.org/bugs/?60937
https://git.savannah.gnu.org/cgit/mailutils.git/commit/?id=4befcfd015256c568121653038accbd84820198f
On Fri, 23 Jul 2021 19:44:08 + (UTC) Thorsten Alteholz wrote:
> According to
On Mon, 2022-01-10 at 20:57 +0100, Matthias wrote:
> Should this also be done, although the radiotray package is still removed?
Wait until after the package is accepted or at least in NEW.
https://ftp-master.debian.org/new.html
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Control: reopen -1
Control: found -1 3.21.8+dfsg0-2
On Mon, 2022-01-10 at 20:54 +, Brian Potkin wrote:
> Use of our limited, volunteer supported resources is best served by not
> keeping open inactive bugs any longer than desirable, especially in
> cases where the package concerned is older
Control: reopen -1
Control: found -1 3.21.8+dfsg0-2
On Mon, 2022-01-10 at 20:54 +, Brian Potkin wrote:
> Use of our limited, volunteer supported resources is best served by not
> keeping open inactive bugs any longer than desirable, especially in
> cases where the package concerned is older
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
Control: block 1003372 by -1
* Package name: python-circuitbreaker
Version : 1.3.2
Upstream Author : Fabian Fuelling
* URL : https
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org
Control: block 1003372 by -1
* Package name: python-circuitbreaker
Version : 1.3.2
Upstream Author : Fabian Fuelling
* URL : https
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
Control: block 1003372 by -1
* Package name: python-circuitbreaker
Version : 1.3.2
Upstream Author : Fabian Fuelling
* URL : https
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org
Control: block 1003372 by -1
* Package name: python-circuitbreaker
Version : 1.3.2
Upstream Author : Fabian Fuelling
* URL : https
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cl...@lists.debian.org
* Package name: oci-python-sdk
Version : 2.53.1
Upstream Author : Vyas Bhagwat and others
* URL : https://github.com/oracle/oci-python-sdk
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-cl...@lists.debian.org
* Package name: oci-python-sdk
Version : 2.53.1
Upstream Author : Vyas Bhagwat and others
* URL : https://github.com/oracle/oci-python-sdk
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cloud@lists.debian.org
* Package name: oci-python-sdk
Version : 2.53.1
Upstream Author : Vyas Bhagwat and others
* URL : https://github.com/oracle/oci-python-sdk
Package: wnpp
Severity: wishlist
Owner: Paul Wise
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cl...@lists.debian.org
* Package name: oci-python-sdk
Version : 2.53.1
Upstream Author : Vyas Bhagwat and others
* URL : https://github.com/oracle/oci-python-sdk
On Wed, 2022-01-05 at 16:08 -0600, Navtej Bhatti wrote:
> If I want Debian to boot with the stock firmware, I need a specific
> partition layout that is completely foreign to UEFI systems. I don't
> think this would integrate well in Linux distributions.
I note that the depthcharge-tools author
1201 - 1300 of 23278 matches
Mail list logo
