On Thu, 2023-11-30 at 14:14 +0100, Paul Gevers wrote:
> The tracker has been doing this for years now.
distro-tracker doesn't have per-maintainer pages
at all and neither does the QA excuses page AFAICT.
The DDPO kind of does, but doesn't list transitions etc.
The DMD kind of does too, but
On Sat, 2023-09-09 at 11:42 +0200, Bastian Blank wrote:
> The first one is the one with included size limitations, because those
> load the kernel from a pre-defined flash partition, whose size can't be
> easily changed by the user. This one is now overflowing for the second
> to last documented
On Sat, 2023-07-01 at 14:29 +0200, Andreas Tille wrote:
> I've filed Bug#1040038 with the patch for r-graphics-api and updated
> branch r-api-graphic branch of dh-r[1] to match the suggested patch
> immediately once uploaded.
I've sent a suggestion to bug #1040038 for not hard-coding the API
On Thu, 2023-03-30 at 08:41 +0200, Paul Gevers wrote:
> That is not the responsibility of this team. I'm also not sure what you
> mean with rootfs, but I think you mean how to bootstrap Debian. We have
> several tools in Debian that do that. I *think* debootstrap [1] is the
> one used for the
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: evolut...@packages.debian.org, Jeremy Bicha
Control: affects -1 + src:evolution
Please unblock package evolution
[ Reason ]
Due to a change in WebKitGTK, pressing the space
On Mon, 2022-11-14 at 00:05 +0800, meida...@foxmail.com wrote:
> I don't know much about Debian's messaging channels. It's been 2
> months since Debian 11.5 was released, and I was wondering if there
> are any plans to release Debian 11.6 in the next few days?
The Debian Release Team website
On Sat, 2022-11-12 at 14:10 +0300, Tanzeela Javid wrote:
> I am getting this error and I cannot understand how to resolve this
>
> EXPKEYSIG CBF8D6FD518E17E1 Jessie Stable Release Key
> 75DDC3C4A499F1A18CB5F3C8CBF8D6FD518E17E1
Please contact our support channels for help using Debian:
On Thu, 2022-08-25 at 19:21 +0300, Adrian Bunk wrote:
> Paul, please ACK/NAK whether you as maintainer consider this appropriate.
Looks good to me, thanks.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: bind-dyndb-l...@packages.debian.org, bi...@packages.debian.org
The bind9-dyndb-ldap binary package built from the bind-dyndb-ldap
source package has a strict dependency on
Control: close -1
On Sat, 2022-03-05 at 18:13 +0100, Sebastian Ramacher wrote:
> How did that happen? I'd prefer that memlockd is fixed so that this
> cannot happen again.
Looks like it builds correctly with debuild -b but not -B due to the
install target in debian/rules not getting used for
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
The current memlockd .deb does not contain /usr/sbin/memlockd, but
simply rebuilding the package fixes the issue. This was reported in
#1000229 and confirmed by me using debuild and
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 Fri, 2021-12-17 at 11:28 +0100, Moritz Mühlenhoff wrote:
> Could anyone who's using Chromium on Debian please create a page on
> wiki.debian.org which lists the alternative options to use a current
> Chromium (Flatpak, ungoogled Chromium from elsewhere, snap, whatever
> else there is)?
The
On Wed, Oct 6, 2021 at 11:30 AM Luca Boccassi wrote:
> On Tue, 2021-10-05 at 21:04 +0200, Sebastian Andrzej Siewior wrote:
> > Additionally OpenSSL is considered system library, see
> > https://bugs.debian.org/951780
> > https://bugs.debian.org/972181
>
> Even if that interpretation holds, and
On Sat, 18 Sep 2021 13:58:56 +0800 Paul Wise wrote:
> nmu ricochet-im_1.1.4-3+b5 . ANY . unstable . -m "Rebuild for the GCC 10
> transition (Closes #992668)"
This appears to have been completed.
> nmu ricochet-im_1.1.4-3+b5 . ANY . bullseye . -m "Rebuild for the GCC
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
The transition from GCC 9 to 10 seems to have changed the size of the
C++ type Type, which breaks a runtime check of this size. I have tested
that rebuilding ricochet-im fixes the runtime
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Control: affects -1 + ricochet-im
X-Debbugs-CC: ricochet...@packages.debian.org
Please rebuild ricochet-im in bullseye and unstable, the transition
from GCC 9 to 10 seems to have changed the
Package: reportbug
Severity: wishlist
Control: affects -1 + release.debian.org
X-Debbugs-CC: release.debian@packages.debian.org
Removals from unstable regularly end up being filed against the
release.debian.org psuedo-package (#994195 is the latest example).
It would be useful to have those
On Sun, Jul 25, 2021 at 12:24 PM Jonathan Carter wrote:
> It has been found today that when the sources.list were updated for the
> updated sources.list URI in bullseye, that the original bug for this contained
> an incorrect suggestion for the sources.list entry that is now present in the
>
On Wed, 2021-07-14 at 20:16 +0800, Shengjing Zhu wrote:
> That feels over-engineering/energy-wasting.
Another option would be to search the source code, and these findings
would need to be confirmed using grep, but looking at codesearch:
On Tue, Jul 13, 2021 at 6:12 AM Shengjing Zhu wrote:
> Sadly the std library are statically embedded in all packages built by Go
> compiler.
> So if there's security issue in std library, bunch of packages need to be
> rebuild.
>
> It may be possible to disassemble all Go binaries to see how
/changelog/ChangeLog 2021-07-14 07:44:15.0 +0800
@@ -1,4 +1,37 @@
+revno: 330
+committer: Paul Wise
+branch nick: bzr
+timestamp: Mon 2021-04-26 12:33:42 +0800
+message:
+ Only create the EPS formatted images for the DVI/PS formatted
Control: close -1
On Tue, Jun 22, 2021 at 8:39 AM Holger Levsen wrote:
> On Tue, Jun 22, 2021 at 09:57:02AM +0800, Paul Wise wrote:
> > [ Reason ]
> > The autoremoval will be before the fix for RC bug #989193 migrates.
>
> (I dont think so, but that's beside my point here.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-CC: apparmor-profiles-ex...@packages.debian.org
Please unblock package apparmor-profiles-extra
[ Reason ]
The autoremoval will be before the fix for RC bug #989193 migrates.
[
Control: tags -1 - moreinfo
On Wed, Jun 9, 2021 at 5:21 PM Sebastian Ramacher wrote:
> This appears to be a pre-approval request. Please remove the moreinfo
> tag once the new version is available in unstable.
Sponsored the package.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Tue, Mar 16, 2021 at 8:06 PM Luís Fernando Russo Alves wrote:
> Venho através desse caminho para suporte do Debian10 Buster ...
Please contact support for help using Debian.
[Tradução automática] Entre em contato com o suporte para obter ajuda
usando o Debian:
On Tue, Jan 26, 2021 at 9:21 AM Christoph Biedl wrote:
> Problem: The old limit turned out to be too strict, and instead of
> avoiding DoS this broke legitimate use of that feature. Also, Paul
> Wise (Cc:'ed), asked me repeatedly to backport this to buster, I
> trust he has good rea
On Wed, 2021-01-20 at 19:26 +0100, Paul Gevers wrote:
> Passing packages that are still shown are those where an update
> happened since the successful run, so they are more or less
> "pending". I realize that probably nobody realizes this.
It is very non-obvious from the output, I'd suggest
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: britney
The excuses page is often very verbose because of the autopkgtest
results, especially for packages with lots of reverse dependencies.
For packages where all the results are Pass, those
On Tue, Jan 5, 2021 at 10:24 PM Lou Poppler wrote:
> I would like to help.
...
> Please suggest any debian lists or IRC channels or webpages I should look at,
> or other steps to make myself useful. Thanks.
The general page for how to help Debian is here:
https://www.debian.org/intro/help
On Mon, Dec 14, 2020 at 11:36 PM Adrian Bunk wrote:
> A bigger worry for i386 would be the availability of microcode updates
This is also a big problem for amd64, since only the newest
generations of Intel processors get BIOS/UEFI and or microcode
updates, so lots of amd64 users (including
On Sat, 21 Nov 2020 01:51:27 + Paul Wise wrote:
> We are using libapache2-mod-auth-kerb at my workplace, I've raised an
> issue about taking over modauthkerb upstream or just switching to
> another module
We have decided to switch to the gssapi module.
I would recommend that libap
On Fri, Nov 20, 2020 at 7:45 PM Sam Hartman wrote:
> I note that libapache2-mod-auth-kerb seems to be QA maintained
> effectively in Debian.
> I haven't looked at upstream to see if they have a fix.
Upstream is basically unmaintained, despite still having users.
We are using
(Closes: #955635)
+
+ -- Paul Wise Sun, 26 Apr 2020 17:47:55 +0800
+
purple-discord (0.9.2019.02.07.git.e5d9627-1) unstable; urgency=medium
* New upstream snapshot
diff -Nru purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/series purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches
On Sun, 2020-03-29 at 08:45 +0200, Paul Gevers wrote:
> But wouldn't that be harder to find for tracker and other consumers?
There is a symlink testing -> bullseye so this works:
https://release.debian.org/testing/freeze-and-release-dates.yaml
I'm not sure when it gets updated but I assume
On Sat, 2020-03-28 at 22:21 +0100, Paul Gevers wrote:
> I have stripped some more from template in the other bug;
Looks good, but the quiet_period URL points at a buster mail.
> the first version should appear soon at
> https://release.debian.org/freeze-and-release-dates.yaml
I would suggest
On Thu, 2020-03-26 at 21:32 +0100, Paul Gevers wrote:
> maybe all the tracker needs is the freeze date and the release date.
I guess that would probably do it yeah.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
On Fri, 2020-03-13 at 22:56 +0100, Paul Gevers wrote:
> I assume you have read the current freeze_policy [1]. As you have seen,
> we have introduced a new phase, where the automatic migration depends on
> the package. I'm not sure how easy it is to cover that information into
> a this template.
On Thu, 2020-02-06 at 13:32 +0100, Paul Gevers wrote:
> That is mostly because they have not been settled 100% yet.
Sorry, I meant for the buster release, which is done now. There is
still data for the last wheezy point release but nothing for the freeze
for buster or bullsye; I thought the
On Thu, 2020-02-06 at 12:02 +0100, Paul Gevers wrote:
> We already have a maintained agenda for the team [1]. Would it make
> sense to use that somehow?
That doesn't appear to have enough info right now, it contains only the
unblock deadline and not the other freeze data.
> I fear that having
On Thu, Jan 9, 2020 at 8:45 AM Paul Gevers wrote:
> Did I just failed to spot it, or is there no bug against gpsd filed
> about this?
The bugs are filed against reverse dependencies (navit/foxtrotgps for eg).
PS: there are two complementary tools that could be used to detect ABI breakage:
On Mon, 2019-12-30 at 21:18 +, Adam D. Barratt wrote:
> Please go ahead.
Signed and uploaded.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
and return truncation
+
+ -- Paul Wise Wed, 11 Dec 2019 09:59:25 +0800
+
libpst (0.6.59-1) unstable; urgency=low
* [ec26e2d0] Imported Upstream version 0.6.59
diff -Nru libpst-0.6.59/debian/patches/07-use-system-extensions.patch libpst-0.6.59/debian/patches/07-use-system-extensions.patch
On Sun, Nov 10, 2019 at 8:11 AM Jay Berkenbilt wrote:
> I am the upstream author and the debian maintainer of qpdf.
Disclaimer: I'm not part of either of the teams you CCed.
> Do you have an opinion about which way I should go?
I would drop the native crypto code from qpdf. If the native
On Fri, 2019-11-08 at 22:06 +, Adam D. Barratt wrote:
> Please go ahead.
Signed and uploaded the source package.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
.4~deb10u1) buster; urgency=medium
+
+ * Rebuild for buster
+
+ -- Paul Wise Sun, 27 Oct 2019 13:58:04 +0800
+
+libapache-mod-auth-kerb (5.4-2.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply patch from upstream issue tracker to fix crash (Closes: #934043)
+
+ -- Paul Wise M
On Wed, Oct 23, 2019 at 3:35 PM Ricardo Mones wrote:
> There's a public roadmap for this?
Not AFAIK, please contact the GNOME team about it.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, 2019-10-23 at 11:39 +0900, Hideki Yamane wrote:
> Is there any link for it? It seems that it affects sylpheed package
> and I want to ask it to the upstream maintainer.
Not yet, I suggest talking to the GNOME team about it.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, Oct 23, 2019 at 7:03 AM Ricardo Mones wrote:
> The claws-mail package appears blocked from migrating to testing because
> of #885266 which removed 3.17.3-2 from it, but is already fixed in 3.17.4-2,
> in sid since 8 days ago…
It seems to be because claws-mail-python-plugin 3.17.3-1 is
On Mon, Sep 2, 2019 at 2:48 AM Ilari Jääskeläinen wrote:
> best wishes for debian stretch, I hope the best possible patience and
> discipline accomplishing the future.
According to the release team's website the stretch 9.10 release is
scheduled for 2019-09-07 (this weekend). If there is
On Mon, Jul 22, 2019 at 2:44 AM Paul Gevers wrote:
> So, now you've seen how I have perceived the freeze, do you have
> anything to add? We're looking for concrete notes and observations that
> we can use when we think about how to improve the bullseye release.
During the buster freeze period,
Holger Levsen wrote:
> package: tracker.debian.org
> severity: wishlist
> x-debbugs-cc: debian...@lists.debian.org
>
> On Thu, Jun 06, 2019 at 09:19:14PM +0800, Paul Wise wrote:
> > On Thu, Jun 6, 2019 at 6:20 PM Holger Levsen wrote:
> [tracker.d.o tells me that]
> >
On Mon, 2019-06-03 at 15:12 +0100, Adam D. Barratt wrote:
> Please go ahead.
Uploaded.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
to stretch
+
+ -- Paul Wise Mon, 20 May 2019 11:55:22 +0800
+
+corekeeper (1.7) unstable; urgency=medium
+
+ * Do not use a world-writable /var/crash with the dumper script
+and fix the permissions on upgrade as dpkg doesn't do that.
+(Closes: #924397) (See-also: #515211)
+ * Handle
Control: tags -1 - moreinfo
On Sat, 2019-05-11 at 16:36 +0200, Paul Gevers wrote:
> Please go ahead and upload to unstable and remove the moreinfo tag
> when it's build.
Uploaded and built by the buildds.
> For reference, if you're confident that an upload meets the freeze
> policy, i.e. it
On Wed, May 8, 2019 at 2:45 PM Paul Gevers wrote:
> With respect to binNMU'ing, static linking is not a problem, only
> arch:all is. Most haskell (4 vs 1048) and ocaml (21 vs 233) aren't
> arch:all. haskell and ocaml have a framework in place to at least know
> the status in unstable/testing. See
with spaces
+ * Update VCS URLs from alioth to salsa
+
+ -- Paul Wise Sat, 04 May 2019 14:53:44 +0800
+
corekeeper (1.6) unstable; urgency=medium
* Prevent installation with other core dump handlers:
diff -Nru corekeeper-1.6/debian/control corekeeper-1.7/debian/control
--- corekeeper-1.6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Please remove libwww-topica-perl from stable, the service
lists.topica.com is no longer available for the last year and
it does not look like it will be returning.
--
bye,
pabs
On Thu, Nov 29, 2018 at 2:21 PM Aurelien Jarno wrote:
> Thanks, I have just uploaded it.
I've just noticed that the glibc update has caused a regression in the
nocache package (details in #916415).
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Mon, Dec 10, 2018 at 1:00 AM 救贖靈魂 wrote:
> 您好，請問 Libreoffice 什麼時候會更新到 v6 版？謝謝！
[自动翻译]请联系Debian用户支持渠道寻求帮助：
Please contact Debian user support channels for help:
https://www.debian.org/support
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Sat, Jun 30, 2018 at 7:44 AM, Manuel A. Fernandez Montecelo wrote:
> People from DSA have also attempted to fix them in other ways over the
> last few months (thanks for that too!), but the solutions have been
> rejected. I am not aware of the full details (only part of them), but
> I assume
On Mon, 2018-05-21 at 07:53 +, Niels Thykier wrote:
> Based on your comments, I have made a branch on salsa:
>
> https://salsa.debian.org/release-team/britney2/tree/bug-899085-excuse-messages
Looks good to me.
> The patches are also attached (assuming it is easier for you to review
> them
On Mon, May 21, 2018 at 2:46 PM, Niels Thykier wrote:
> When I wrote the messages, I wanted to quickly high light the three
> basic states ("OK", "WAITING" or "BLOCKED"/rejected). The first two
> states implies that the contributor does not need to do anything at the
> moment, where as the
On Mon, May 21, 2018 at 1:53 PM, Niels Thykier wrote:
> """
> Migration status: OK: Will attempt migration (Any information below is
> purely informational)
> """
I'd remove the "OK:" from that unless there is a reason for it?
> So changing the wording to the proposed will simply make it
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: britney
In #898329, pochu had to clarify the meaning of "Valid Candidate":
Just to clarify things: being a valid candidate means britney will
try to migrate that package to testing. That can
:38.0 +0800
+++ libipc-run-perl-0.92/debian/changelog 2018-04-17 16:16:38.0 +0800
@@ -1,3 +1,9 @@
+libipc-run-perl (0.92-1+deb8u1) jessie; urgency=medium
+
+ * Backport upstream patch to fix memory leak
+
+ -- Paul Wise <p...@debian.org> Tue, 17 Apr 2018 16:16:38 +0800
+
libipc-ru
:50.0 +0800
+++ libipc-run-perl-0.94/debian/changelog 2018-04-17 16:24:46.0 +0800
@@ -1,3 +1,9 @@
+libipc-run-perl (0.94-1+deb9u1) stretch; urgency=medium
+
+ * Backport upstream patch to fix memory leak
+
+ -- Paul Wise <p...@debian.org> Tue, 17 Apr 2018 16:24:46 +0800
+
libipc-ru
On Thu, Mar 29, 2018 at 4:54 AM, John wrote:
> After upgrading I cannot transfer files reliably to my computer
Please ask on Debian support channels for help determining which
package is at fault and gathering the required debug information. Once
you have done that you can report a bug against
it.
--
bye,
pabs
https://wiki.debian.org/PaulWise
From ceca85e82f047e7763ea1102ccdbf6da548e9932 Mon Sep 17 00:00:00 2001
From: Paul Wise <p...@debian.org>
Date: Sat, 6 Jan 2018 11:28:21 +0800
Subject: [PATCH] Drop duplicate 'has new bugs' excuses item
The other item includes bug numb
On Tue, Dec 26, 2017 at 7:15 PM, Moritz Mühlenhoff wrote:
> Is that a temporary measure or permanently due to the state of
> the port?
https://lists.debian.org/debian-bsd/2017/12/msg8.html
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Sun, Nov 19, 2017 at 11:10 PM, Julien Cristau wrote:
> Above syntax is wrong, you're missing a . between package and
> architectures, and version should be source version. Also if any of
> those packages build multi-arch: same binaries, this would break them.
> Overall it doesn't sound like
Control: retitle -1 debhelper 10.10.7 dbgsym regression fix rebuilds
On Sat, 2017-11-18 at 14:17 +0800, Paul Wise wrote:
> There are probably several packages affected but I am not aware of
> any easy mechanism to determine which packages were built against
> debhelper 10.10.6
It wa
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
debhelper 10.10.7 fixed a regression in debhelper 10.10.6 that
prevented dbgsym packages from being generated. There are probably
several packages affected but I am not aware of any easy
On Thu, Jul 20, 2017 at 5:04 AM, gregor herrmann wrote:
> #867213: syslog-ng-incubator: one rdep (syslog-ng). No reaction on
> the bug report, unrelated build failure; I guess syslog-ng*
> can be removed from testing if noone fixes the problem in
> time.
I'd like to
On Fri, Jul 7, 2017 at 2:01 AM, Antoine Beaupré wrote:
> For what it's worth, my opinion is that we should attempt to synchronize
> certdata.txt (and blacklist.txt, for that matter) across all suites (but
> not other changes to the packaging). This would remove another decision
> point in our
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Please remove check-all-the-things from stretch.
It isn't suitable for stable at this time.
I've filed bug #862378 to keep it out.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, 2017-05-03 at 12:24 +0200, Moritz Schlarb wrote:
> - This has been the behavior of the Nagstamon package since forever
> (which is not a valid argumentation point - I know, but it's still a fact)
There are two serious bugs here:
1) that certificates are not verified at least using CAs
2017-04-27 20:34:00.0 +0800
@@ -1,3 +1,11 @@
+check-all-the-things (2017.01.15.1) unstable; urgency=high
+
+ * New release.
+- The "Check Shiny Things More Securely" release
+- Fix perlcritic to not execute code from the current dir
+
+ -- Paul Wise <p...@debian.org&
On Mon, 2017-04-24 at 22:12 +0100, Adam D. Barratt wrote:
> That sounds okay, although I wonder if it's worth mentioning the unusual
> version progression in the changelog.
I've rebuilt the package including this additional changelog entry:
* Use version -6+ instead of -5+ because samba-libs
es/fix-crash.patch
--- needrestart-session-0.3/debian/patches/fix-crash.patch 1970-01-01 08:00:00.0 +0800
+++ needrestart-session-0.3/debian/patches/fix-crash.patch 2017-03-14 15:35:06.0 +0800
@@ -0,0 +1,16 @@
+Description: fix crash when double-clicking on items in the list
+Author: Pau
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package needrestart-session, it creates the user needed
to run the dbus service which is needed for this package to work.
unblock needrestart-session/0.3-4
The maintainer
Control: tags 838671 + patch
On Tue, 17 Jan 2017 14:58:22 +0100 Andreas Beckmann wrote:
> openchange also FTBFS in stable:
FYI, I've a patch from upstream, waiting on release team approval:
https://bugs.debian.org/851678
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
On Mon, Feb 6, 2017 at 5:45 AM, Niels Thykier wrote:
> Here are two updated patches.
Committed.
Removed some trailing whitespace and moved your name to Patch-by.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Control: retitle -1 jessie-pu: package openchange/1:2.2-6+deb8u1
On Sat, 2017-01-21 at 10:13 +0100, Andreas Beckmann wrote:
> But openchangeproxy will still not be installable in jessie since
> samba-libs has
>
> Conflicts: openchangeproxy (<< 1:2.2-6)
I forgot about that. Since 1:2.2-6 was
Control: retitle -1 jessie-pu: package openchange/1:2.2-5+deb8u1
Control: release.debian@packages.debian.org
Control: usertags -1 - rm + pu
On Wed, 18 Jan 2017 07:21:49 +0800 Paul Wise wrote:
> This looks like the API issue in openchangeproxy mentioned in the
> samba changelog from the
On Tue, Jan 17, 2017 at 10:26 PM, Andreas Beckmann wrote:
> I'm not perfectly convinced about this RM request, but something should
> happen with openchange in stable:
At $work we rely on openchange but not openchangeproxy. We know it was
removed from stretch and later but were assuming we could
an - allow to run if installed
+- Update lrzip-test/zstd-test - add MIME types
+- Add lz4-test - check lz4 compressed files
+- Add path-max - check for non-portable path size macros
+- TODO items for deep-text-correcter sblint decopy
+
+ -- Paul Wise <p...@debian.org> Sun, 15 Jan
On Thu, Dec 29, 2016 at 9:36 PM, victory wrote:
> correction libraw ... fix memory objects are not intialized properly
> in*i*tialized
Fixed in CVS.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Mon, Dec 12, 2016 at 5:22 AM, Josh Triplett wrote:
> If we can get every package to handle this entirely at runtime, then
> ideally I'd suggest archive metadata downloaded by apt. That would have
> the advantage of automatically handling new sections, including for
> third-party archives.
On Thu, Sep 15, 2016 at 11:43 AM, Paul Wise wrote:
> Please introduce a copy of the old glew so that packages
> using GLEW MX can build and run on Debian stretch.
Since you declined I've now uploaded a glewmx source package to NEW.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, Sep 7, 2016 at 8:15 PM, Matteo F. Vescovi wrote:
> * quesoglc (0.7.2-5) -> FTBFS [G]
I'm disappointed that upstream completely removed GLEW MX support and
you did not notice that quesoglc and other packages use GLEW MX and
cannot build and work without it. Please introduce a copy of the
Control: reassign -1 qa.debian.org
Control: retitle -1 UDD/testing_autoremovals_gatherer.pl: Version in
autoremoval notice may not be version actually checked
On Fri, 2016-09-02 at 08:16 +0100, Rebecca N. Palmer wrote:
> That script looks like it gets version and bug information in one fetch
>
Control: reassign -1 release.debian.org
Control: retitle -1 Version in autoremoval notice may not be version
actually checked
As you can see in the headers of the mail, the autoremoval warnings
are sent by the release team not the QA infrastructure.
On Fri, Sep 2, 2016 at 5:33 AM, Rebecca N.
On Fri, Aug 26, 2016 at 9:49 AM, taro110 wrote:
> Hi, I am building some packages by myself
> and facing gpg verification error. e.g.,
Please ask your question on the mentors list instead:
https://lists.debian.org/debian-mentors/
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Sun, Aug 7, 2016 at 9:18 PM, Dirk Eddelbuettel wrote:
> Let me know if I should take this to debian-devel or some other list.
I'm not part of the release team, but I expect you probably should
read the documentation and then file a bug report, the release team
often emphasises bug reports
---
queue-viewer/overview.xslt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/queue-viewer/overview.xslt b/queue-viewer/overview.xslt
index 0ec63f0..d79127c 100644
--- a/queue-viewer/overview.xslt
+++ b/queue-viewer/overview.xslt
@@ -201,7 +201,7 @@
On Wed, 2016-06-15 at 01:37 +0300, Dimitri John Ledkov wrote:
> At the openmainframeproject EU meetup, it was indicated that SUSE
> joined with indication that Open Build Service might be able to use
> resources hosted by Marist.
>
> I wonder if it makes sense to reach out, and see if there are
Package: release.debian.org
Severity: wishlist
pixbros was removed from testing due to an RC bug. I have fixed the RC
bug but it is not migrating back into testing because it is an arch all
package that depends on an 32-bit-only package (fenix) that has never
been available on amd64 but britney
On Wed, Mar 9, 2016 at 5:24 PM, Holger Levsen wrote:
> I dont think doing thousands of sourceful uploads is realistic nor useful
Now that we have source-only uploads, it should be fairly easy to do
on a fast network. Just a for loop around apt-get source, dch, debuild
-S, debsign, dupload.
--
On Wed, Mar 2, 2016 at 3:34 AM, bancfc wrote:
> Hi. After the recent glibc debacle I came across a patch to harden this
> important library against common attack vectors. Please think about
> reviewing and adding in Debian. The author warned there may be some package
> breakage but nothing too
1 - 100 of 295 matches
Mail list logo
