[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#949120: marked as done (buster-pu: package quassel/1:0.13.1-1)

Your message dated Sat, 08 Feb 2020 14:21:36 +0000
with message-id <cf1cb2f35981916a86b98b83609df15c95aa378b.camel@adam-barratt.org.uk>
and subject line Closing requests included in 10.3 point release
has caused the Debian Bug report #949120,
regarding buster-pu: package quassel/1:0.13.1-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
949120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949120
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian.org@packages.debian.org
Usertags: pu

This update does two things:

1.  Corrects the provided apparmor profile so that user creation and
storage work with quassel-core.  Currently on  a new install or if a new
user is added to an existing install, the storage for the user
information will fail due to inadquate appamor permissions and some time
later, users will discover their information is gone (it works during
the initial session, but is not saved for subsequent use.

The most typical response of users that run into this problem is to give
up on using the package.  The second most typical response is to disable
apparmor.  Obviously neither of those are good.  The change is low risk.
I did test it on buster with a new setup to verify it works.

2.  Corrects default Debian channel.  I don't know when #debian-user got
replaced by #debian, but #debian is the standard support channel that we
want as the default for new users.  Currenlty new users will get an
error about being blocked from joinging #debian-user which recommends
joining #debian.  This is a very pooor first user experience.

The change is trivial and low risk (only affects new installs).

These changes are both already in Testing.

Scott K

diff -Nru quassel-0.13.1/debian/changelog quassel-0.13.1/debian/changelog
--- quassel-0.13.1/debian/changelog	2019-02-15 13:00:08.000000000 -0500
+++ quassel-0.13.1/debian/changelog	2020-01-16 23:28:02.000000000 -0500
@@ -1,3 +1,15 @@
+quassel (1:0.13.1-1+deb10u1) buster; urgency=medium
+
+  [ Felix Geyer ]
+  * Fix quasselcore AppArmor denials when the config is saved. (Closes:
+    #940482)
+
+  [ Scott Kitterman ]
+  * Correct default channel for Debian
+  * Add NEWS entry about reloading the quaseelcore AppArmor profile
+
+ -- Scott Kitterman <scott@kitterman.com>  Thu, 16 Jan 2020 23:28:02 -0500
+
 quassel (1:0.13.1-1) unstable; urgency=medium
 
   [ Scott Kitterman ]
diff -Nru quassel-0.13.1/debian/NEWS quassel-0.13.1/debian/NEWS
--- quassel-0.13.1/debian/NEWS	1969-12-31 19:00:00.000000000 -0500
+++ quassel-0.13.1/debian/NEWS	2020-01-11 19:58:20.000000000 -0500
@@ -0,0 +1,11 @@
+quassel (1:0.13.1-2) unstable; urgency=medium
+
+  * This revision of quassel contains an updated apparmor profile for quassel-
+    core.  To load the new profile, use the following command on the server
+    running the core:
+
+        apparmor_parser -r /etc/apparmor.d/usr.bin.quasselcore
+
+    This only applies to quaseelcore, no action is required for clients.
+
+ -- Scott Kitterman <scott@kitterman.com>  Sat, 11 Jan 2020 14:55:50 -0500
diff -Nru quassel-0.13.1/debian/patches/01_default_network_channel.patch quassel-0.13.1/debian/patches/01_default_network_channel.patch
--- quassel-0.13.1/debian/patches/01_default_network_channel.patch	2019-01-05 15:18:57.000000000 -0500
+++ quassel-0.13.1/debian/patches/01_default_network_channel.patch	2020-01-10 21:03:05.000000000 -0500
@@ -21,4 +21,4 @@
 +Servers=irc.debian.org:+6697
 +
 +Default=Yes
-+DefaultChannels=#debian-user
++DefaultChannels=#debian
diff -Nru quassel-0.13.1/debian/usr.bin.quasselcore quassel-0.13.1/debian/usr.bin.quasselcore
--- quassel-0.13.1/debian/usr.bin.quasselcore	2019-01-05 15:18:52.000000000 -0500
+++ quassel-0.13.1/debian/usr.bin.quasselcore	2020-01-10 21:02:22.000000000 -0500
@@ -13,7 +13,7 @@
   #include <abstractions/ssl_certs>
 
   /var/lib/quassel/ rw,
-  /var/lib/quassel/** rwk,
+  /var/lib/quassel/** rwkl,
 
   /var/log/quassel/* rw,
 
@@ -22,6 +22,13 @@
   /etc/ssl/openssl.cnf r,
   /usr/lib/ssl/openssl.cnf r,
 
+  # QSysInfo::machineUniqueId()
+  /var/lib/dbus/machine-id r,
+  /etc/machine-id r,
+
+  # QSysInfo::bootUniqueId()
+  @{PROC}/sys/kernel/random/boot_id r,
+
   # Site-specific additions and overrides. See local/README for details.
   #include <local/usr.bin.quasselcore>
 }

--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 10.3

Hi,

Each of the uploads referred to by these bugs was included in today's
stable point release.

Regards,

Adam

--- End Message ---
Reply to: