Bug#1033953: unblock: gimp-help/2.10.34-1
Hi! El dl. 08 de 05 de 2023 a les 22:12 +0200, en/na Paul Gevers va escriure: > Control: tags -1 confirmed moreinfo > s this is a documentation only source package, you can go ahead. > Please > remove the moreinfo tag once it happens and don't wait too long > please. Paul, I checked the excuses today and I see it's still not setup. Just in case this is it: have in mind that the unblock request must be against 2.10.34-2, instead of -1, as -1 went through NEW via experimental. Thanks, Jordi -- Jordi Mallach Debian Project
Bug#1035868: unblock: kernelshark/2.2.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: sudipm.mukher...@gmail.com
Hi,
Please unblock package kernelshark
Its a simple change to rename the links which fixes the RC bug.
[ Reason ]
It fixes the RC bug.
[ Impact ]
User will not be able to use libkshark.
[ Tests ]
manual tests to confirm symlinks are pointing to the correct file.
[ Risks ]
No risk in unblocking it. :)
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
unblock kernelshark/2.2.0-2
--
Regards
Sudip
diff -Nru kernelshark-2.2.0/debian/changelog kernelshark-2.2.0/debian/changelog
--- kernelshark-2.2.0/debian/changelog 2023-02-05 00:47:33.0 +
+++ kernelshark-2.2.0/debian/changelog 2023-05-05 20:37:24.0 +0100
@@ -1,3 +1,9 @@
+kernelshark (2.2.0-2) unstable; urgency=medium
+
+ * Fix symlink names. (Closes: #1035449)
+
+ -- Sudip Mukherjee Fri, 05 May 2023 20:37:24
+0100
+
kernelshark (2.2.0-1) unstable; urgency=medium
* New upstream version 2.2.0
diff -Nru kernelshark-2.2.0/debian/libkshark2.links
kernelshark-2.2.0/debian/libkshark2.links
--- kernelshark-2.2.0/debian/libkshark2.links 2022-04-26 20:16:02.0
+0100
+++ kernelshark-2.2.0/debian/libkshark2.links 2023-05-05 20:05:16.0
+0100
@@ -1,2 +1,2 @@
-usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2.0.0
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2
-usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2.0.0
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2
+usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2.2.0
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-gui.so.2
+usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2.2.0
usr/lib/${DEB_HOST_MULTIARCH}/libkshark-plot.so.2
Bug#1031410: Closing p-u requests for fixes included in 11.7
Hi,
at our company we were quite surprised by this seemingly minor update
3.1.1+dfsg-1+deb11u1, because it completely broke an application: Due to
the change the x and y axis are now inverted when converting coordinates
to EPSG 31466:
Before (this output is from 11.19, but was like this on 13 before as well):
SELECT geometry,ST_AsGeoJSON(ST_Transform(ST_SetSRID(geometry, 3857),
31466)) FROM osm_car_sharing_node LIMIT 1;
geometry |
st_asgeojson
+
010120110F04F0844A1349264120ED527FE9DD5841 |
{"type":"Point","coordinates":[2539841.86185744,5586869.51937972]}
(1 row)
Now:
SELECT geometry, ST_AsGeoJSON(ST_Transform(ST_SetSRID(geometry, 3857),
31466)) FROM osm_car_sharing_node LIMIT 1;
-[ RECORD 1
]+--
geometry | 010120110F04F0844A1349264120ED527FE9DD5841
st_asgeojson |
{"type":"Point","crs":{"type":"name","properties":{"name":"EPSG:31466"}},"coordinates":[5586869.519378289,2539841.861857439]}
I understand the rationale for the change in general, but in my opinion
such a major change really should not be part of such a minor update.
Is there an option to fix this apart from changing all queries?
Regards,
Stephan Großberndt
Bug#1035879: unblock: mozjs102/102.10.0-1
Package: release.debian.org Control: affects -1 + src:mozjs102 X-Debbugs-Cc: mozjs...@packages.debian.org User: release.debian@packages.debian.org Usertags: unblock Please unblock package mozjs102 and reduce the days required to reach Testing. [ Reason ] The new mozjs102 stable point release includes multiple security fixes. - CVE-2023-32211: Content process crash due to invalid wasm code - CVE-2023-32215: Memory safety bugs I included more in debian/changelog but those affected Firefox ESR, not mozjs specifically. Sorry. [ Impact ] mozjs102 is only used by gjs which in turn is used by GNOME Shell and several GNOME apps written in JavaScript. [ Tests ] The build tests have passed successfully and the gjs autopkgtests triggered by this upload have passed too. (mozjs102 itself does not have autopkgtests yet). I also completed the manual test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs on Debian Testing. [ Risks ] [ Checklist ] [X] all changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in testing [ Other info ] mozjs102 is the SpiderMonkey JavaScript engine from the current Firefox ESR stable branch. There are monthly releases until the end of August. https://whattrainisitnow.com/calendar/ I am unaware of anyone using Firefox vulnerabilities to attack GNOME Shell, but I think it's good to be prudent and apply available security updates. I don't think the Debian Security Team has done security uploads for mozjs*, in part because Mozilla's lifecycle is so short that it's difficult for an upstream supported mozjs to be in a Debian stable release. For more info about the commits, see the Github mirror: https://github.com/mozilla/gecko-dev/commits/esr102/js unblock mozjs102/102.11.0-1 Thank you, Jeremy Bicha mozjs-102.11.debdiff Description: Binary data
Processed: unblock: mozjs102/102.10.0-1
Processing control commands: > affects -1 + src:mozjs102 Bug #1035879 [release.debian.org] unblock: mozjs102/102.10.0-1 Added indication that 1035879 affects src:mozjs102 -- 1035879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035882: nmu: pvpgn_1.8.5-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Control: block 1034224 by -1 nmu pvpgn_1.8.5-3 . ANY . unstable . -m "Rebuild with fixed debhelper installing pvpgn.service to the correct place" Files in second .deb but not in first - -rw-r--r-- root/root /lib/systemd/system/pvpgn.service -rwxr-xr-x root/root DEBIAN/preinst Files in first .deb but not in second - -rw-r--r-- root/root /usr/lib/systemd/system/pvpgn.service See #1034224 for background.
Processed: nmu: pvpgn_1.8.5-3
Processing control commands: > block 1034224 by -1 Bug #1034224 [pvpgn] pvpgn: dh_installsystemd doesn't handle files in /usr/lib/systemd/system 1034224 was not blocked by any bugs. 1034224 was not blocking any bugs. Added blocking bug(s) of 1034224: 1035882 -- 1034224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034224 1035882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1035757: unblock: org-mode/9.5.2+dfsh-5
Processing control commands: > tag -1 - moreinfo Bug #1035757 [release.debian.org] unblock: org-mode/9.5.2+dfsh-5 Removed tag(s) moreinfo. -- 1035757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035757: unblock: org-mode/9.5.2+dfsh-5
control: tag -1 - moreinfo Hello, Thanks for looking. On Mon 08 May 2023 at 09:33PM +02, Paul Gevers wrote: > What's the plan for the future? Is this a one-off exercise or do you > intent to pull this trick more often? We don't have a real plan for the future, aside from trying to keep these packages up-to-date. It would be good to have a script that we could run right after uploading new versions of Emacs, that would find addons that are now behind. So, we'd like it to be one-off, but due to limited manpower on the team, I can't pretend that it couldn't happen again. Ultimately I think that the correct fix is for Emacs to learn to load the version of the package that has the highest version number. So, I think this is, at bottom, an upstream limitation. But I might be wrong about that. > IIRC other ecosystems (like ruby) have the main package also > (versioned) Provides these add-ons, such that when packages Depend on > it, the main package can provide it without needing the add-on. That > way, you could prevent shipping the package in a stable release when > it's behind and have a newer version if it's available. Has such a > scheme been considered? If yes, what's the drawback? We haven't considered it. It would be a case of writing a script to generate the required Provides values from the Emacs source. -- Sean Whitton signature.asc Description: PGP signature
Bug#1031410: Closing p-u requests for fixes included in 11.7
Hi,
after further investigation this looks more like a bug in the backport.
At first I thought the change was about flipping x and y for all
coordinate systems except those containing "lat/lon", which did not make
much sense to me, but I would have been willing to accept this.
But apparently this flip is only in this PostGIS 3.1.1+dfsg-1+deb11u1
version, earlier and later PostGIS versions correctly return x as x and
y as y.
For this query:
SELECT
ST_AsGeoJSON(ST_Transform(ST_SetSRID('010120110F04F0844A1349264120ED527FE9DD5841'::geometry,
3857), 31466));
the following versions correctly return x=2539841,y=5586869:
- PostgresQL 11 with PostGIS 2.5.1+dfsg-1 from Debian Sources
- PostgresQL 11 with PostGIS 2.5.5+dfsg-1.pgdg100+2 from PostgreSQL Sources
- PostgresQL 13 with PostGIS 3.1.1+dfsg-1 from Debian Sources
- PostgresQL 13 with PostGIS 3.3.2+dfsg-1.pgdg110+1 from Debian Sources
Only
- PostgresQL 13 with PostGIS 3.1.1+dfsg-1+deb11u1 from Debian Sources
incorrectly returns x=5586869,y=2539841
Should I file another bug report for this?
Regards,
Stephan Großberndt
Bug#1035894: unblock: desktop-base/12.0.6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: desktop-b...@packages.debian.org, debian-desk...@lists.debian.org
Control: affects -1 + src:desktop-base
Dear Release Team,
please unblock package desktop-base.
[ Reason ]
It fixes a bug where Pymouth messages and prompts don’t get displayed
for some screen size and ratio combinations.
[ Impact ]
- Users won’t see the password prompt for LUKS encrypted volumes on boot
in certain screen configurations. (#1032412)
- The « remove media press enter to reboot » message isn’t shown after
initial installation.
[ Tests ]
I tested that there are no regression on single screen use cases and
both the original reporter and a second person confirmed the fix on
their multi-screen / multi-ratio configurations.
[ Risks ]
No risk identified, the patch is small and localised the new code
underwent more tests in more configurations that the one currently in
testing.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
Thanks for your work on the release !
unblock desktop-base/12.0.6
diff -Nru desktop-base-12.0.5/debian/changelog
desktop-base-12.0.6/debian/changelog
--- desktop-base-12.0.5/debian/changelog2023-03-01 23:22:32.0
+0100
+++ desktop-base-12.0.6/debian/changelog2023-04-13 21:58:23.0
+0200
@@ -1,3 +1,10 @@
+desktop-base (12.0.6) unstable; urgency=medium
+
+ * Fix LUKS password not being shown in multi-screen setup with mixed aspect
+ratios.
+
+ -- Aurélien COUDERC Thu, 13 Apr 2023 21:58:23 +0200
+
desktop-base (12.0.5) unstable; urgency=medium
* Make the GDM Debian footer slightly smaller.
diff -Nru desktop-base-12.0.5/emerald-theme/plymouth/emerald.script
desktop-base-12.0.6/emerald-theme/plymouth/emerald.script
--- desktop-base-12.0.5/emerald-theme/plymouth/emerald.script 2023-03-01
23:01:49.0 +0100
+++ desktop-base-12.0.6/emerald-theme/plymouth/emerald.script 2023-04-13
21:58:23.0 +0200
@@ -119,7 +119,8 @@
#Debug("y = " + y);
text_height = first_line_height * 7.5;
-min_height = window_max.height - 2 * first_line_height;
+# subtract Window.GetY() to show info also at smallest of dual srceens
+min_height = window_max.height - 2 * first_line_height - Window.GetY();
#Debug("text_height=" + text_height + "; min_height=" + min_height);
if (y + text_height > min_height)
@@ -131,8 +132,8 @@
#- Screen/window setup ---
# Compute screen/image ratio and scale the background accordingly
-window_max.width = Window.GetX() * 2 + Window.GetWidth();
-window_max.height = Window.GetY() * 2 + Window.GetHeight();
+window_max.width = Window.GetWidth();
+window_max.height = Window.GetHeight();
screen_ratio = window_max.width / window_max.height;
small_dimension = Math.Min(window_max.width, window_max.height);
#Debug("Window.GetX():" + Window.GetX() + ", Window.GetY():" + Window.GetY());
Processed: unblock: desktop-base/12.0.6
Processing control commands: > affects -1 + src:desktop-base Bug #1035894 [release.debian.org] unblock: desktop-base/12.0.6 Added indication that 1035894 affects src:desktop-base -- 1035894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035898: unblock: chrony/4.3-2+deb12u1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: chr...@packages.debian.org
Control: affects -1 + src:chrony
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Please unblock package chrony
[ Reason ]
This softens a rule in the AppArmor profile. Currently, the profile is way too
strict about allowed gpsd socket names.
[ Impact ]
Users may need to override the AppArmor profile (or put the profile in complain
mode) so that chronyd can consume time information from gpsd using sockets.
Overriding an AppArmor profile is acceptable when dealing with some exotic
configurations, but here even trying to feed chronyd with something as common
as PPS samples would be denied by the profile.
[ Tests ]
I checked that chronyd was able to receive PPS samples from gpsd through a
Unix socket driver using the '/run/chrony.pps0.sock' path. This is no longer
denied with chrony 4.3-2+deb12u1.
[ Risks ]
None that I know of.
[ Checklist ]
[✓] all changes are documented in the d/changelog
[✓] I reviewed all changes and I approve them
[✓] attach debdiff against the package in testing
[ Other info ]
I must admit that the version number is atypical for an upload to unstable but
chrony 4.3-3 is already in experimental.
unblock chrony/4.3-2+deb12u1
-BEGIN PGP SIGNATURE-
iHUEARYKAB0WIQSRJQjHKbAUfuoc+DAQn1qAt/bgAQUCZFv+fQAKCRAQn1qAt/bg
ATptAQDKB1vG2CXDXkwW1dGb9l3GFwua+oeoc1qOm3LNhqNfSgD/ZBld8s8e1XSD
QXFm/ZXjxKXIkU+1m8TaS5JL5oRWDwk=
=uMJh
-END PGP SIGNATURE-
diff -Nru chrony-4.3/debian/changelog chrony-4.3/debian/changelog
--- chrony-4.3/debian/changelog 2023-01-27 22:51:17.0 +0100
+++ chrony-4.3/debian/changelog 2023-05-08 22:05:00.0 +0200
@@ -1,3 +1,13 @@
+chrony (4.3-2+deb12u1) unstable; urgency=medium
+
+ * debian/usr.sbin.chronyd:
+- Modify the AppArmor profile to allow more gpsd socket names. This will
+avoid the need for users to override the profile to let chronyd consume PPS
+samples or serial time supplied by gpsd over a Unix-domain socket.
+Thanks to Ryan Govostes for the report. (Closes: #1034519)
+
+ -- Vincent Blut Mon, 08 May 2023 22:05:00 +0200
+
chrony (4.3-2) unstable; urgency=medium
* debian/control:
diff -Nru chrony-4.3/debian/usr.sbin.chronyd chrony-4.3/debian/usr.sbin.chronyd
--- chrony-4.3/debian/usr.sbin.chronyd 2023-01-27 22:51:17.0 +0100
+++ chrony-4.3/debian/usr.sbin.chronyd 2023-05-08 22:05:00.0 +0200
@@ -59,7 +59,7 @@
# Configs using a 'chrony.' prefix like the tempcomp config file example
/etc/chrony.* r,
# Example gpsd socket is outside @{run}/chrony/
- @{run}/chrony.tty{,*}.sock rw,
+ @{run}/chrony.*.sock rw,
# To sign replies to MS-SNTP clients by the smbd daemon
/var/lib/samba/ntp_signd/socket rw,
Processed: unblock: chrony/4.3-2+deb12u1
Processing control commands: > affects -1 + src:chrony Bug #1035898 [release.debian.org] unblock: chrony/4.3-2+deb12u1 Added indication that 1035898 affects src:chrony -- 1035898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035911: [pre-approval] unblock: dpkg/1.21.22
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: d...@packages.debian.org
Control: affects -1 + src:dpkg
Hi!
Please pre-approve the dpkg 1.21.22 upload.
[ Reason ]
I got a report for a segfault privately (as the reporter was unsure
whether this constituted a security issue, which IMO it does not),
which is rather easy to trigger for packages that are known to dpkg,
but are not installed, such as virtual packages or references from
Recommends or Suggests.
I've also cherry picked a translation addition that was already in git
HEAD (targeting 1.22.x).
[ Impact ]
An easy to trigger segfault, which also affects dpkg 1.20.x (for which
I'll be preparing a stable release request).
[ Tests ]
The test suite has been updated to cover this case. And it's also easy
to reproduce with dpkg-query, for example on a minimal chroot, with:
$ dpkg-query -f '${source:Upstream-Version}\n' -W firefox-esr
Segmentation fault (core dumped)
[ Risks ]
The fix is trivial, so the risk seems low to me.
[ Checklist ]
[√] all changes are documented in the d/changelog
[√] I reviewed all changes and I approve them
[√] attach debdiff against the package in testing
[ Other info ]
(I had in mind also including an addition for the riscv32 port, but
given that there's no consensus among the porters about its ABI or
even its mere existence, and time is running out, I'll postpone that,
and might include it instead in a future stable release if necessary.)
Attached the unfiltered debdiff, you might want to filterdiff with:
xzcat dpkg-1.21.21-1.21.22.debdiff.xz |
filterdiff --exclude '*.po' --exclude '*.pot' \
--exclude '*/man/*/*.pod' \
--exclude '*/testsuite' --exclude '*/at/*.m4' \
--exclude '*/configure'
unblock dpkg/1.21.22
Thanks,
Guillem
dpkg-1.21.21-1.21.22.debdiff.xz
Description: application/xz
Processed: [pre-approval] unblock: dpkg/1.21.22
Processing control commands: > affects -1 + src:dpkg Bug #1035911 [release.debian.org] [pre-approval] unblock: dpkg/1.21.22 Added indication that 1035911 affects src:dpkg -- 1035911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031410: Closing p-u requests for fixes included in 11.7
> Should I file another bug report for this?
Yes.
On unstable:
gis=# SELECT
ST_AsGeoJSON(ST_Transform(ST_SetSRID('010120110F04F0844A1349264120ED527FE9DD5841'::geometry,
3857), 31466));
st_asgeojson
---
{"type":"Point","crs":{"type":"name","properties":{"name":"EPSG:31466"}},"coordinates":[2539841.861857439,5586869.519378289]}
(1 row)
On bullseye:
bagv2=# SELECT
ST_AsGeoJSON(ST_Transform(ST_SetSRID('010120110F04F0844A1349264120ED527FE9DD5841'::geometry,
3857), 31466));
st_asgeojson
---
{"type":"Point","crs":{"type":"name","properties":{"name":"EPSG:31466"}},"coordinates":[5586869.519378289,2539841.861857439]}
(1 row)
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035710: doc-debian 11.0 changed /usr/share/doc-base/ paths
Package: doc-debian
Version: 11.0
Severity: normal
Hi,
On Mon, 8 May 2023 07:46:09 +0200 Joost van =?utf-8?Q?Baal-Ili=C4=87?=
wrote:
> [ Risks ] None. The doc-debian package is a key package due to Priority:
> standard. It acts as a leaf package: Its only true reverse depends is the
> live-task-standard package.[reverse-depends]
you are forgetting packages using doc-debian in their autopkgtests.
> [ Other info ] I made a mistake uploading doc-debian 11.0 to unstable; that
> got accepted. The version 11.1 is now available from
> http://mdcc.cx/tmp/doc-debian/ . I've incorporated some small cosmetic
> changes next to the much needed document updates. Attached is a 161 kB
> doc-debian_6.5-11.1.dsc-debdiff , as well as a summarizing 13kB
> doc-debian_6.5-11.1.dsc-debdiff-tldr .
Before your upload of 11.0, doc-debian contained:
/usr/share/doc-base/debian-constitution-text
/usr/share/doc-base/debian-mailing-lists
/usr/share/doc-base/debian-manifesto
/usr/share/doc-base/debian-reporting-bugs
/usr/share/doc-base/debian-social-contract
Then with 11.0 this became:
/usr/share/doc-base/doc-debian.debian-constitution-text
/usr/share/doc-base/doc-debian.debian-mailing-lists
/usr/share/doc-base/doc-debian.debian-manifesto
/usr/share/doc-base/doc-debian.debian-reporting-bugs
/usr/share/doc-base/doc-debian.debian-social-contract
This broke the autopkgtest of mmdebstrap which you can also see on the excuses
page for doc-debian: https://qa.debian.org/excuses.php?package=doc-debian
Since I noticed this breakage, I uploaded a new version of mmdebstrap that
works around this problem, assuming that this change was intentional. In
hindsight, I probably should've contacted you instead because when
investigating http://mdcc.cx/tmp/doc-debian/doc-debian_11.1_all.deb and
comparing it to the version from unstable I see:
diff -u <(curl --silent
http://ftp.de.debian.org/debian/pool/main/d/doc-debian/doc-debian_11.0_all.deb
| dpkg-deb -c - | awk '{print $6}' | sort) <(curl --silent
http://mdcc.cx/tmp/doc-debian/doc-debian_11.1_all.deb | dpkg-deb -c - | awk
'{print $6}' | sort)
--- /dev/fd/63 2023-05-11 08:18:34.782823397 +0200
+++ /dev/fd/62 2023-05-11 08:18:34.782823397 +0200
@@ -3,11 +3,11 @@
./usr/share/
./usr/share/doc/
./usr/share/doc-base/
-./usr/share/doc-base/doc-debian.debian-constitution-text
-./usr/share/doc-base/doc-debian.debian-mailing-lists
-./usr/share/doc-base/doc-debian.debian-manifesto
-./usr/share/doc-base/doc-debian.debian-reporting-bugs
-./usr/share/doc-base/doc-debian.debian-social-contract
+./usr/share/doc-base/debian-constitution-text
+./usr/share/doc-base/debian-mailing-lists
+./usr/share/doc-base/debian-manifesto
+./usr/share/doc-base/debian-reporting-bugs
+./usr/share/doc-base/debian-social-contract
./usr/share/doc/debian/
./usr/share/doc/debian/bug-log-access.txt
./usr/share/doc/debian/bug-log-mailserver.txt.gz
What are the intended paths. Should I revert my changes to mmdebstrap or not?
Also, these changes of paths in /usr/share/doc-base/ forth and back are not
recorded in debian/changelog. If the change was intended, please document it.
Thanks!
cheers, josch
signature.asc
Description: signature
Processed: unblock: node-asn1.js/5.4.1-4
Processing control commands: > affects -1 + src:node-asn1.js Bug #1035915 [release.debian.org] unblock: node-asn1.js/5.4.1-4 Added indication that 1035915 affects src:node-asn1.js -- 1035915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
