Re: Accepting / adopting DEP-14

[Christian Kastner]

On 2020-08-29 01:05, Raphael Hertzog wrote:
> But given that we recommend upstream/latest for the upstream branch, I'm now
> leaning towards using debian/latest as default as well.
I like this! There's a nice symmetry to it that makes it very intuitive,
I think.

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Andrea Bolognani]

On Sat, Aug 29, 2020 at 01:01:09AM +0200, Raphael Hertzog wrote:
> Hello,
> 
> following the recent discussions of June and of the last days, I'm
> proposing the changes below to DEP-14. Basically it replaces debian/master
> with debian/latest for all the reasons already discussed earlier. And
> it says that debian/unstable is preferred over debian/sid.
> 
> And it also marks the proposal as ACCEPTED given that it has gained
> traction over the years and that we didn't feel the need to make
> significant change to it.
> 
> I'm proposing debian/latest now because DEP-14 is already recommending
> upstream/latest and that makes the result a bit more consistent. But if
> enough person disagree with this choice, we can look into setting a poll
> to choose among all the names proposed so far.

We switched libvirt from debian/sid to debian/master a few days ago,
and honestly I was feeling a bit uncomfortable about the new name but
adopted it anyway on the basis that it is formalized in DEP-14, which
we have been following for a long time.

Using debian/latest removes this problem, and as you point out is
also entirely consistent with the existing upstream/latest. So, for
whatever it might be worth, you have my +1 for this change.

-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.


signature.asc
Description: PGP signature

Bug#966373: #966373: Higher version for uploads to stable and oldstable distributions

[Chris Hofstaedtler]

Control: reassign -1 release.debian.org

Hi,

versioning for (old)stable uploads is best discussed with the
Release team. Filing this against the `general` package does nothing
useful for this discussion, so I'm reassigning this bug.

I'd encourage a mail to debian-rele...@lists.debian.org instead,
though.

Chris

Processed: Re: #966373: Higher version for uploads to stable and oldstable distributions

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 release.debian.org
Bug #966373 [general] general: Higher version for uploads to stable and 
oldstable distributions
Bug reassigned from package 'general' to 'release.debian.org'.
Ignoring request to alter found versions of bug #966373 to the same values 
previously set
Ignoring request to alter fixed versions of bug #966373 to the same values 
previously set

-- 
966373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#966414: #966414: After upgrade to testing, VT1 is no longer usuable

[Chris Hofstaedtler]

Control: reassign -1 sddm

Per description this sounds like an ssdm issue, or at least
something the sddm maintainers could help diagnosing.

Chris

Processed: Re: #966414: After upgrade to testing, VT1 is no longer usuable

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 sddm
Bug #966414 [general] general: After upgrade to testing, VT1 is no longer 
usuable
Bug reassigned from package 'general' to 'sddm'.
Ignoring request to alter found versions of bug #966414 to the same values 
previously set
Ignoring request to alter fixed versions of bug #966414 to the same values 
previously set

-- 
966414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#967029: marked as done (reportbug: ThinkPad E595 trackpoint physical buttons stopped working after ipp-usb upgrade on 08/01)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 11:58:39 +0200
with message-id <20200830095839.dbfd6n7zrarqn...@percival.namespace.at>
and subject line Re: #967029: ThinkPad E595 trackpoint physical buttons stopped 
working after ipp-usb upgrade
has caused the Debian Bug report #967029,
regarding reportbug: ThinkPad E595 trackpoint physical buttons stopped working 
after ipp-usb upgrade on 08/01
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 ow...@bugs.debian.org
immediately.)


-- 
967029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.7.0
Severity: important
Tags: upstream
X-Debbugs-Cc: be...@protonmail.com

Dear Maintainer,

I made a routine upgrade on 08/01, since then my trackpoint physical buttons
stopped working.

Laptop model: Lenovo ThinkPad E595 20NF001YRT

OS: Debian GNU/Linux bullseye/sid x86_64

Desktop: Gnome 3.36.4 Wayland

08/01 update:

Start-Date: 2020-08-01  12:24:10
Commandline: apt upgrade -y
Install: ipp-usb:amd64 (0.9.10-2, automatic)
Upgrade: libqmi-proxy:amd64 (1.26.0-0.1, 1.26.2-0.1), exim4-base:amd64 (4.94-6,
4.94-7), libdevmapper1.02.1:amd64 (2:1.02.167-1+b1, 2:1.02.171-1),
dmsetup:amd64 (2:1.02.167-1+b1, 2:1.02.171-1), libcups2:amd64 (2.3.3-1,
2.3.3-2), libsystemd0:amd64 (245.6-2, 245.7-1), libqmi-glib5:amd64 (1.26.0-0.1,
1.26.2-0.1), python3-pysimplesoap:amd64 (1.16.2-2, 1.16.2-3), node-pump:amd64
(3.0.0-3, 3.0.0-4), exim4-daemon-light:amd64 (4.94-6, 4.94-7), udev:amd64
(245.6-2, 245.7-1), cups-server-common:amd64 (2.3.3-1, 2.3.3-2), libnss-
mymachines:amd64 (245.6-2, 245.7-1), cups-common:amd64 (2.3.3-1, 2.3.3-2),
libudev1:amd64 (245.6-2, 245.7-1), systemd-timesyncd:amd64 (245.6-2, 245.7-1),
cups-ppdc:amd64 (2.3.3-1, 2.3.3-2), exim4-config:amd64 (4.94-6, 4.94-7),
libnss-myhostname:amd64 (245.6-2, 245.7-1), systemd-sysv:amd64 (245.6-2,
245.7-1), libpam-systemd:amd64 (245.6-2, 245.7-1), systemd:amd64 (245.6-2,
245.7-1), libwebkit2gtk-4.0-37:amd64 (2.28.3-2, 2.28.4-1), libnss-systemd:amd64
(245.6-2, 245.7-1), gir1.2-webkit2-4.0:amd64 (2.28.3-2, 2.28.4-1), systemd-
container:amd64 (245.6-2, 245.7-1), cups-bsd:amd64 (2.3.3-1, 2.3.3-2), cups-
core-drivers:amd64 (2.3.3-1, 2.3.3-2), bison:amd64 (2:3.6.3+dfsg-1,
2:3.7+dfsg-1), cups-daemon:amd64 (2.3.3-1, 2.3.3-2), libcupsimage2:amd64
(2.3.3-1, 2.3.3-2), cups:amd64 (2.3.3-1, 2.3.3-2), cups-client:amd64 (2.3.3-1,
2.3.3-2), libjavascriptcoregtk-4.0-18:amd64 (2.28.3-2, 2.28.4-1), cups-ipp-
utils:amd64 (2.3.3-1, 2.3.3-2), nfs-common:amd64 (1:1.3.4-3, 1:1.3.4-4),
gir1.2-javascriptcoregtk-4.0:amd64 (2.28.3-2, 2.28.4-1)
End-Date: 2020-08-01  12:25:13

dmidecode -t 21 output:

# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.1.1 present.

Handle 0x0032, DMI type 21, 7 bytes
Built-in Pointing Device
   Type: Track Point
   Interface: PS/2
   Buttons: 3

Handle 0x0033, DMI type 21, 7 bytes
Built-in Pointing Device
   Type: Touch Pad


That's really weird, ipp-usb doesn't seem to be connected with trackpoint,
libinput whatsoever.

Also I noticed that my brightness became somewhat broken, since the 08/01
update it always defaults to max brightness after restart.



-- Package-specific info:
** Environment settings:
INTERFACE="gtk"

** /home/bebyx/.reportbugrc:
reportbug_version "7.7.0"
mode standard
ui gtk
email "be...@protonmail.com"
no-cc
list-cc-me
smtphost reportbug.debian.org

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt2.1.7
ii  python33.8.2-3
ii  python3-reportbug  7.7.0
ii  sensible-utils 0.0.12+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs-bin-common   
ii  exim4-daemon-light [mail-transport-agent]  4.94-7
ii  file   1:5.38-5
ii  gnupg  2.2.20-1
pn  python3-urwid  
pn  reportbug-gtk  
ii  xdg-utils  1.

Bug#776005: marked as done (general: After finished the installation, I rebooted and the initialization has been stopped)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:06:09 +0200
with message-id <20200830100608.d4hsj2pkzq5nf...@percival.namespace.at>
and subject line Re: Bug#776005: general: After finished the installation, I 
rebooted and the initialization has been stopped
has caused the Debian Bug report #776005,
regarding general: After finished the installation, I rebooted and the 
initialization has been stopped
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 ow...@bugs.debian.org
immediately.)


-- 
776005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: important

Dear Maintainer,


The initialization is stoped and the system does not do anything. I have to do
a hard reboot, and select the emergency bootup.

¿How can I send you more characterist about the motherboard?

It is a Shuttle SK21G, I send you the same error for Debian 7, some years ago.



-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report.

However, at this time it looks more like a support request, and the
bug tracker - especially the "general" package - is not well-suited
for this.

Please try getting help from other venues listed at
   https://www.debian.org/support

Especially IRC, the mailing lists or http://forums.debian.net/

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#854793: marked as done (general: debian jessie kde shutdown problem gui/acpi)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:07:19 +0200
with message-id <20200830100718.7sgwhjxrup4q2...@percival.namespace.at>
and subject line Re: Bug#854793: general: debian jessie kde shutdown problem 
gui/acpi
has caused the Debian Bug report #854793,
regarding general: debian jessie kde shutdown problem gui/acpi
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 ow...@bugs.debian.org
immediately.)


-- 
854793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Dear Maintainer,

i installed a completely fresh debian 64 bit with kde as desktop environment.
nearly everythink worked fine, but sometimes the poweroff/shutdown does not. To
be exact, if i run as root poweroff -h, it works without porblems, but if i
want to shutdown via the kde-menu or the acpi control (in settings adjusted ofc
via gui), it doesn't do anything. neither does the pc shut down nor do i get
the 30s wait logo.

during now i only saw this after the pc was on for more then 20 mins. if i
start it and try to shut down, i didnt see this problem until now.

so i think it has something to do with the kde control of the buttons in the
menu (the big blue K at the bottom left) depending what a command they call and
the acpi control mybe uses the same command.

to answer complete, log off or restart didnt work, too...the same behaviour:
nothing.

if you have more questions, i would be happy to help, if i can.



-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report.

However, at this time it looks more like a support request, and the
bug tracker - especially the "general" package - is not well-suited
for this.

Please try getting help from other venues listed at
   https://www.debian.org/support

Especially IRC, the mailing lists or http://forums.debian.net/

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#899349: marked as done (general: USB mouse disconnects and is reconnected every minute)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:18:14 +0200
with message-id <20200830101813.n6bngebrpp4p3...@percival.namespace.at>
and subject line Re: Bug#899349: general: USB mouse disconnects and is 
reconnected every minute
has caused the Debian Bug report #899349,
regarding general: USB mouse disconnects and is reconnected every minute
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 ow...@bugs.debian.org
immediately.)


-- 
899349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Dear Maintainer,

After 1 minute of inactivity on TTY1 appear this messages.
Mouse is: Logitech M100.

Aug 18 00:20:41 localhost kernel: [   64.225557] usb 1-1.4: new low speed USB 
device number 4 using ehci_hcd
Aug 18 00:20:41 localhost kernel: [   64.316417] input: Genius Optical Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input9
Aug 18 00:20:41 localhost kernel: [   64.316473] generic-usb 
0003:0458:003A.0002: input,hidraw0: USB HID v1.11 Mouse [Genius Optical Mouse] 
on usb-:00:1a.0-1.4/input0
Aug 18 00:21:41 localhost kernel: [  124.261211] usb 1-1.4: USB disconnect, 
device number 4

Aug 18 00:21:43 localhost kernel: [  125.722315] usb 1-1.4: new low speed USB 
device number 5 using ehci_hcd
Aug 18 00:21:43 localhost kernel: [  125.813042] input: Genius Optical Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input10
Aug 18 00:21:43 localhost kernel: [  125.813100] generic-usb 
0003:0458:003A.0003: input,hidraw0: USB HID v1.11 Mouse [Genius Optical Mouse] 
on usb-:00:1a.0-1.4/input0
Aug 18 00:22:43 localhost kernel: [  185.756780] usb 1-1.4: USB disconnect, 
device number 5

Aug 18 00:22:45 localhost kernel: [  187.219082] usb 1-1.4: new low speed USB 
device number 6 using ehci_hcd
Aug 18 00:22:45 localhost kernel: [  187.309663] input: Genius Optical Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input11
Aug 18 00:22:45 localhost kernel: [  187.309722] generic-usb 
0003:0458:003A.0004: input,hidraw0: USB HID v1.11 Mouse [Genius Optical Mouse] 
on usb-:00:1a.0-1.4/input0
Aug 18 00:23:45 localhost kernel: [  247.252457] usb 1-1.4: USB disconnect, 
device number 6

Aug 18 00:23:46 localhost kernel: [  248.712302] usb 1-1.4: new low speed USB 
device number 7 using ehci_hcd
Aug 18 00:23:46 localhost kernel: [  248.803287] input: Genius Optical Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input12
Aug 18 00:23:46 localhost kernel: [  248.803343] generic-usb 
0003:0458:003A.0005: input,hidraw0: USB HID v1.11 Mouse [Genius Optical Mouse] 
on usb-:00:1a.0-1.4/input0
Aug 18 00:24:47 localhost kernel: [  308.748075] usb 1-1.4: USB disconnect, 
device number 7


-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report. Since filing it, many USB autosuspend
changes have happened, and I hope this just works on current
versions.

If this is still a problem, please diagnose this further and file a
new report against the package having the bug (not "general"). 

You can get further help from othrer venues listed at 
   https://www.debian.org/support
... especially IRC, the mailing lists or http://forums.debian.net/

Thank you for your understanding,
Chris--- End Message ---

Bug#840897: general: framebuffer modules for non-dri graphics cards are not loaded

[Chris Hofstaedtler]

Control: reassign -1 systemd

* Michal Suchanek :
> So I would like the fbdev modules removed from whatever blacklist prevents
> loading them and have them loaded on systems that don't have dri modules to
> handle graphics.

AFAICT systemd ships the fbdev blacklist nowadays, reassigning
there.

(I understand there might not much that can be done conceptually
about this.)

Chris

Processed: Re: Bug#840897: general: framebuffer modules for non-dri graphics cards are not loaded

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd
Bug #840897 [general] general: framebuffer modules for non-dri graphics cards 
are not loaded
Bug reassigned from package 'general' to 'systemd'.
Ignoring request to alter found versions of bug #840897 to the same values 
previously set
Ignoring request to alter fixed versions of bug #840897 to the same values 
previously set

-- 
840897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 841293 is forwarded to https://bugzilla.mozilla.org/show_bug.cgi?id=1100658

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 841293 https://bugzilla.mozilla.org/show_bug.cgi?id=1100658
Bug #841293 [general] general: In some cases Fira Sans font doesn't render in 
browsers
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1100658'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
841293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841293: marked as done (general: In some cases Fira Sans font doesn't render in browsers)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:27:33 +0200
with message-id <20200830102732.xxqcycv3xtt5r...@percival.namespace.at>
and subject line Re: Bug#841293: general: In some cases Fira Sans font doesn't 
render in browsers
has caused the Debian Bug report #841293,
regarding general: In some cases Fira Sans font doesn't render in browsers
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 ow...@bugs.debian.org
immediately.)


-- 
841293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Dear developers,

in some cases "Fira Sans" font only displays blank glyphs in web browsers.
This was already reported in bug #800143 against Iceweasel (now closed and
archived) [1]

This bug still exists in Jessie. As the original report says, it is not
specific to any browser, but seems to be specific to Debian. I can't get "Fira
Sans" font to render on firefox-esr 45.3.0esr-1~deb8u1, firefox 49.0-4~bpo80+1
or google-chrome-stable 54.0.2840.59-1 on an up-to-date Jessie system using
GNOME. This font is somewhat popular on the web, which means that I often
encounter web pages where content is unreadable. Same browsers correctly
display the font on Ubuntu.

A HTML file with a simple test case is attached (at the moment also available
on-line [2]). Affected systems only display the second line "sans-serif" in
browsers, while the line "Fira Sans" is invisible.

This issue appears to be connected to some part of X11 session state, because
the same system will show different behavior depending on which desktop
environment is currently used. The bug manifests itself on GNOME, OpenBox and
Awesome WM, but not in XFCE.

As simple way to reproduce the bug is to boot the XFCE live CD [3]. In the
default XFCE session, the firefox-esr browser correctly displays the "Fira
Sans" font. If you apt-get install openbox, log-out and log-in using Openbox
session, the same browser will not render the font.

Since I can't determine which package specifically is causing this, I'm
reporting this bug against "general".

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800143
[2] https://www.tablix.org/~avian/firasans.html)
[3] 
http://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-8.6.0-amd64-xfce-desktop.iso

Best regards
Tomaž

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.1+ (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iceweasel depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3+deb8u1
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u6
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
pn  libffi5   
ii  libfontconfig12.11.0-6.3+deb8u1
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libglib2.0-0  2.42.1-1+b1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libhunspell-1.3-0 1.3.3-3
ii  libpango1.0-0 1.36.8-3
ii  libsqlite3-0  3.8.7.1-1+deb8u2
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.9-9
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages iceweasel recommends:
pn  gstreamer0.10-ffmpeg
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu4+b1

Versions of packages iceweasel suggests:
ii  fonts-lmodern  2.004.4-5
ii  fonts-stix [otf-stix]  1.1.1-1
ii  libcanberra0   0.30-2.1
ii  libgnomeui-0   2.24.5-3
ii  libgssapi-krb5-2   1.12.1+dfsg-19+deb8u2
pn  mozplugger 
Title: Test




Fira Sans
sans-serif


--- End Message ---
--- Begin Message ---
* Tomaž Šolc :
> The problem appears only with the WOFF2 "Fira Sans Regular" font file that is
> distributed by Google through t

Bug#911411: general: Computer freezes after suspend/hibernate

[Chris Hofstaedtler]

Control: reassign -1 src:linux-signed-amd64

Hi David, Adam, Vladimir,

you have reported a suspend/hiberate bug, against the "general"
package, indicating various kernel versions are affected and that
the problem might be getting worse.

I'm reassigning this bug to the linux source package, but please
try to gather additional help from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ , as the bug tracker
often is not very suitable for this.

Thank you for your understanding,
Chris

Processed: Re: Bug#911411: general: Computer freezes after suspend/hibernate

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux-signed-amd64
Bug #911411 [general] general: Computer freezes after suspend/hibernate
Bug reassigned from package 'general' to 'src:linux-signed-amd64'.
Ignoring request to alter found versions of bug #911411 to the same values 
previously set
Ignoring request to alter fixed versions of bug #911411 to the same values 
previously set

-- 
911411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#869115: marked as done (general: MAC address of wifi card always change)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:47:16 +0200
with message-id <20200830104715.eienjftbrs5pt...@percival.namespace.at>
and subject line Re: Bug#869115: general: MAC address of wifi card always change
has caused the Debian Bug report #869115,
regarding general: MAC address of wifi card always change
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 ow...@bugs.debian.org
immediately.)


-- 
869115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: important

Dear Maintainer,

Since I have installed Debian 9.0, the MAC address of my Wifi Card always
change. So, Network Manager cannot connect to it. Changing address with 
macchanger
or ip command is not efficient.
 
Thank you in advance. 


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
WiFi card: Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network 
Adapter
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report.

However, at this time it looks more like a support request, and the
bug tracker - especially the "general" package - is not well-suited
for this.

Please try getting help from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#882343: marked as done (general: Laptop crashing after suspend if device is plugged into headphone jack)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:47:48 +0200
with message-id <20200830104747.j6u7rxslehuug...@percival.namespace.at>
and subject line Re: Bug#882343: general: Laptop crashing after suspend if 
device is plugged into headphone jack
has caused the Debian Bug report #882343,
regarding general: Laptop crashing after suspend if device is plugged into 
headphone jack
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 ow...@bugs.debian.org
immediately.)


-- 
882343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: important

Dear Maintainer,


Laptop crashes if headphone device is left in when resume from suspend is
attempted or if it is suspended then taken out then resumed.




-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report.

However, at this time it looks more like a support request, and the
bug tracker - especially the "general" package - is not well-suited
for this.

Please try getting help from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#819662: marked as done (Deactivate laptop internal webcam when the LID is closed)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:51:42 +0200
with message-id <20200830105141.bkxi3dcfuyfag...@percival.namespace.at>
and subject line Re: Bug#819662: Deactivate laptop internal webcam when the LID 
is closed
has caused the Debian Bug report #819662,
regarding Deactivate laptop internal webcam when the LID is closed
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 ow...@bugs.debian.org
immediately.)


-- 
819662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unknown
Version: unknown

I have a debian 8 laptop with a docking station and an external
monitor, with a webcam.
When my laptop is in the docking station, with the LID closed, the
applications (like cheese) still detect my internal webcam.
Of course the webcam only displays a black screen because the LID is closed.
So my request is to deactivate the internal webcam when the LID is closed.
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report.

However, at this time it looks like this is a hardware issue, and
your hardware vendor should take care of this.

Thank you for your understanding,
Chris--- End Message ---

Bug#909347: marked as done (general: 9.5 GPU hardware acceleretion of my hardware is disable)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:54:54 +0200
with message-id <20200830105452.mrtob3qpdc45p...@percival.namespace.at>
and subject line Re: Bug#909347: general: 9.5 GPU hardware acceleretion of my 
hardware is disable
has caused the Debian Bug report #909347,
regarding general: 9.5 GPU hardware acceleretion of my hardware is disable
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 ow...@bugs.debian.org
immediately.)


-- 
909347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Dear Maintainer,



I don't know which package causes this problem. The thing is ugrading Debian 9 
disables
 my GPU hardware acceleration
I did:  sudo apt update && sudo apt upgrade -y
glxinfo -B after upgrade 
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 3.9, 128 bits) (0x)
Version: 13.0.6
Accelerated: no
Video memory: 7176MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.9, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 13.0.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

lspci -knn | grep -i VGA -A3
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Richland [Radeon HD 8570D] [1002:990e]
Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526]
Kernel driver in use: radeon
Kernel modules: radeon
sudo dmesg | grep -E 'drm|radeon' | grep -iE 'firmware|microcode'
[sudo] пароль до koral: 
[8.693169] [drm] Loading ARUBA Microcode
[8.786378] radeon :00:01.0: firmware: direct-loading firmware 
radeon/ARUBA_pfp.bin
[8.794635] radeon :00:01.0: firmware: direct-loading firmware 
radeon/ARUBA_me.bin
[8.794891] radeon :00:01.0: firmware: direct-loading firmware 
radeon/ARUBA_rlc.bin
[8.826982] radeon :00:01.0: firmware: direct-loading firmware 
radeon/TAHITI_uvd.bin
[9.016678] radeon :00:01.0: firmware: direct-loading firmware 
radeon/TAHITI_vce.bin
[9.018580] [drm] Found VCE firmware/feedback version 50.0.1 / 17!

   I expected that hardware acceleration mode work

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=uk_UA.utf8, LC_CTYPE=uk_UA.utf8 (charmap=UTF-8), 
LANGUAGE=uk_UA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report.

However, at this time it looks more like a support request, and the
bug tracker - especially the "general" package - is not well-suited
for this.

Please try getting help from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#819249: marked as done (general: Touchpad don't work correctly in MacBook 4.1 in Debian 9 with Gnome)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:54:35 +0200
with message-id <20200830105434.5k5knk7ro53e5...@percival.namespace.at>
and subject line Re: Bug#819249: general: Touchpad don't work correctly in 
MacBook 4.1 in Debian 9 with Gnome
has caused the Debian Bug report #819249,
regarding general: Touchpad don't work correctly in MacBook 4.1 in Debian 9 
with Gnome
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 ow...@bugs.debian.org
immediately.)


-- 
819249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Dear Maintainer,

I'm used Debian 9 stretch in MacBook 4.1 with Gnome, everything works fine
unless touchpad correctly, I don't have click right with two fingers and
I can't click with touchpad. This worked well in debian 8, I understand
that I'm using the version testing(alpha 5), but this will help.

Thank you so much.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report.

However, at this time it looks more like a support request, and the
bug tracker - especially the "general" package - is not well-suited
for this.

Please try getting help from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#935787: marked as done (general: RaLink RT2870 usb wifi cannot connect (worked on Jessie))

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 12:52:31 +0200
with message-id <20200830105230.cqf63x45yli3b...@percival.namespace.at>
and subject line Re: Bug#935787: general: RaLink RT2870 usb wifi cannot connect 
(worked on Jessie)
has caused the Debian Bug report #935787,
regarding general: RaLink RT2870 usb wifi cannot connect (worked on Jessie)
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 ow...@bugs.debian.org
immediately.)


-- 
935787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   I recently did a fresh upgrade from Debian 9 Stable to Debian 10 Stable. On 
Debian 9, my usb wifi (D-Link System DWA-140 RangeBooster N Adapter(rev.B1) 
[Ralink RT2870]) worked fine after installing firmware-misc-nonfree. However, 
on Debian 10 it can no longer make a connection to my wifi router. The system 
log reports that authentication and associated are successful, but the 
connection attempt times out report 'ip-config-unavailable'.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Package firmware-misc-nonfree was installed.
 
 I amended /etc/NetworkManager/NetworkManager.conf to add the lines:

 [device]
 scan-rand-mac-address=no

   * What was the outcome of this action?
   The above actions did not solve the problem - the same error message 
occurred.
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi,

thanks for filing this report.

However, at this time it looks more like a support request, and the
bug tracker - especially the "general" package - is not well-suited
for this.

Please try getting help from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#865067: general: Custom keyboard shortcuts combination issues

[Chris Hofstaedtler]

* Guilherme Paiva :
[..]
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> After the Debian upgrade some of my combinations are not working anymore such 
> as:
[..]
> /var/logs/messages shows this:
>  gnome-settings-[2285]: Could not find accelerator for accel id 138
>  gnome-settings-[2285]: Could not find accelerator for accel id 138

Reassigning to gnome-settings-daemon, as a best guess.

Please don't reassign back to general, as nothing useful will happen
to this bug report there.

Thanks,
Chris

Bug#538022: marked as done (PAGER as a pipeline)

[Debian Bug Tracking System]

Your message dated Sun, 30 Aug 2020 13:00:01 +0200
with message-id <20200830105959.q6npnd54jao4v...@percival.namespace.at>
and subject line Re: Bug#538022: PAGER as a pipeline
has caused the Debian Bug report #538022,
regarding PAGER as a pipeline
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 ow...@bugs.debian.org
immediately.)


-- 
538022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

I want to use vim as my man pager. On other distros, and on sarge, I use this 
line 
in my .bashrc

# Set vim as the man pager
export PAGER="col -b | view -c 'set ft=man nomod nolist titlestring=MANPAGE' -"

In those systems, it displays the man page properly in vim with full color. 
However, 
on using the same line on sid, the error given is 

[rohan@debian ~]$ man man
Reformatting man(1), please wait...
col: invalid option -- c
usage: col [-bfhpx] [-l nline]
man: command exited with status 256: /usr/bin/zsoelim /tmp/zmanGiFFlw | 
/usr/bin/tbl 
| /usr/bin/nroff -mandoc -rLL=89n -rLT=89n -Tutf8 | col -b | view -c set ft=man 
nomod nolist titlestring=MANPAGE -
[rohan@debian ~]$

I dont why it is passing -c to col, where it should pass it to "view" i.e. vim. 


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)

--- End Message ---
--- Begin Message ---
* Colin Watson :
> On Mon, Dec 21, 2009 at 06:21:02PM +0100, Holger Levsen wrote:
[..]
> > Else, please explain what's the general bug to track here.
> 
> The general bug is that not even sensible-pager implements $PAGER as a
> pipeline, and thus it seems to me that we systemically don't support
> this facility. If we want to support that, we're talking about changes
> to more than just man-db; I expect there are packages other than
> sensible-utils and man-db that have problems.

As nobody seems to have had interest in this in the last 11 years,
lets close this discussion for now. Interested parties who also
bring the drive to make the required changes can start a new
discussion in a better place.

Chris --- End Message ---

Bug#842854: general: Lenovo X220T rotate screen key works in Debian8/Gnome but not KDE

[Chris Hofstaedtler]

Hi,

thanks for filing this report.

However, at this time it looks more like a support request, and the
bug tracker - especially the "general" package - is not well-suited
for this.

Please try getting help from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Raphael Hertzog]

On Sat, 29 Aug 2020, Richard Laager wrote:
> That said, I do understand we give a lot of deference to developers'
> workflows. So I have no objection to DEP-14 supporting this workflow
> with debian/latest. But I would like to see it (debian/latest)
> recharacterized as the alternate approach rather than the recommended
> method.

Your approach is perfectly valid but I don't really believe that it should
be the recommended approach. It doesn't seem to match the most common
workflow.

Most package maintainers are not actively working on two different
development branches, instead the single development branch keeps moving
between:
- ready for unstable/upload to unstable
- work in progress on a new upstream release
- possible upload to experimental to gather feedback (buildd, users)
- back to ready for upload to unstable

In some rare cases, we will have to do some intermediary upload to
unstable because some RC bug popped up and we don't want to wait until
we're ready with the next upload. In that case, we will create a
debian/unstable branch starting from the last tag in debian/unstable.

IOW, while branches are cheap, I create them on request only when I need
them, I'm not using multiple branches until I have a real need for it.

But I might also do the opposite. If I know that the next upstream release
breaks backwards compatitibly and that it will have to mature a long time
in experimental until all other packages are ready, I might start to
package it rigth now in debian/experimental and continue to use
debian/latest for my unstable uploads.

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS


signature.asc
Description: PGP signature

Re: Accepting / adopting DEP-14

[Raphael Hertzog]

On Sat, 29 Aug 2020, Emmanuel Arias wrote:
> DEP-14 will recommend the use of debian/latest  for a package uploaded
> to sid/unstable?  or debian/latest is a pre work before uploaded to
> sid/unstable?

It is to be expected that debian/latest keeps switching between different
states:
- in sync with sid
- in some "develop/test/pre-work" state (as you put) because you are
  working on a new uptsream release
- possibly in sync with experimental for a short while

> So, I think  would be a good recommendation to use debian/latest as a
> default branch for "develop" reasons, then when the package is ready to
> upload move that change to other branch debian/experimental, debian/sid,
> etc..

Multiplicating the branches has a (cognitive) cost and should only be done
for a good reason.

You can surely have a private "develop" branch if you want but there's no
point to have so many branches if you are not actively maintaining all
those versions in parallel.

The point of debian/latest is to accomodate for the case where you are
usually not actively maintaining multiple versions in parallel.

Cheers,
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Processed (with 1 error): reassign 969263 to general, reassign 968647 to firefox-esr, reassign 966004 to general ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 969263 general
Bug #969263 [bugs.debian.org] bugs.debian.org: debian 10 does not let me 
install vmware tools
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #969263 to the same values 
previously set
Ignoring request to alter fixed versions of bug #969263 to the same values 
previously set
> reassign 968647 firefox-esr
Bug #968647 [bugs.debian.org] bugs.debian.org: GUI locks up when I launch web 
browser
Bug reassigned from package 'bugs.debian.org' to 'firefox-esr'.
Ignoring request to alter found versions of bug #968647 to the same values 
previously set
Ignoring request to alter fixed versions of bug #968647 to the same values 
previously set
> reassign 966004 general
Bug #966004 [bugs.debian.org] bugs.debian.org: .XCompose fails to  make long 
substitutions
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #966004 to the same values 
previously set
Ignoring request to alter fixed versions of bug #966004 to the same values 
previously set
> reassign 964940 general
Bug #964940 [bugs.debian.org] bugs.debian.org: After an upgrade and crash, the 
boot process say  ACPI error:  AE_NOT_FOUND.  I think that the problem was an 
upgrade not completed on the bios machine or similar.
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #964940 to the same values 
previously set
Ignoring request to alter fixed versions of bug #964940 to the same values 
previously set
> reassign 964115 general
Bug #964115 [bugs.debian.org] Web browser video playback broken in bullseye
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #964115 to the same values 
previously set
Ignoring request to alter fixed versions of bug #964115 to the same values 
previously set
> reassign 962350 initscripts
Bug #962350 [bugs.debian.org] /etc/init.d/checkfs.sh is not very robust, and 
fails on missing filesystems.
Bug reassigned from package 'bugs.debian.org' to 'initscripts'.
Ignoring request to alter found versions of bug #962350 to the same values 
previously set
Ignoring request to alter fixed versions of bug #962350 to the same values 
previously set
> reassign 949858 xfce4
Bug #949858 [bugs.debian.org] bugs.debian.org: Snap Application are not shown 
in the application finder and application menu in XFCE 4
Bug reassigned from package 'bugs.debian.org' to 'xfce4'.
Ignoring request to alter found versions of bug #949858 to the same values 
previously set
Ignoring request to alter fixed versions of bug #949858 to the same values 
previously set
> reassign 945866 util-linux
Bug #945866 [bugs.debian.org] bugs.debian.org: $PATH error with root (su 
command)
Bug reassigned from package 'bugs.debian.org' to 'util-linux'.
Ignoring request to alter found versions of bug #945866 to the same values 
previously set
Ignoring request to alter fixed versions of bug #945866 to the same values 
previously set
> forcemerge 945866 904988
Bug #945866 [util-linux] bugs.debian.org: $PATH error with root (su command)
Bug #945866 [util-linux] bugs.debian.org: $PATH error with root (su command)
Marked as found in versions util-linux/2.32-0.3.
Bug #904988 {Done: Gijs Hillenius } [util-linux] util-linux 
/bin/su $path is missing crucial dirs
Failed to forcibly merge 945866: Failure while trying to adjust bugs, please 
report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> reassign 949289 general
Bug #949289 [bugs.debian.org] bugs.debian.org: No wifi and no sound after 
suspend
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #949289 to the same values 
previously set
Ignoring request to alter fixed versions of bug #949289 to the same values 
previously set
> reassign 942698 general
Bug #942698 [bugs.debian.org] bugs.debian.org: Multiple Call Traces in dmesg
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #942698 to the same values 
previously set
Ignoring request to alter fixed versions of bug #942698 to the same values 
previously set
> reassign 942406 general
Bug #942406 [bugs.debian.org] bugs.debian.org: Dual Monitors - Full Screen 
behaviour
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #942406 to the same values 
previously set
Ignoring request to alter fixed versions of bug #942406 to the same values 
previously set
> reassign 936096 general
Bug #936096 [bugs.debian.org] bugs.debian.org: Wlan switch on and off after 
update 4.19 to 5.2 (normal Testing update)
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #936096 to the same values 
previously set
Ignoring request 

Processed: reassign 901008 to general, reassign 915964 to general, reassign 920318 to general ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 901008 general
Bug #901008 [bugs.debian.org] bugs.debian.org: Hibernation fails when RAM usage 
is high
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #901008 to the same values 
previously set
Ignoring request to alter fixed versions of bug #901008 to the same values 
previously set
> reassign 915964 general
Bug #915964 [bugs.debian.org] bugs.debian.org: Boot process with kernel 
4.18.0.3 fails and goes to black screen.
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #915964 to the same values 
previously set
Ignoring request to alter fixed versions of bug #915964 to the same values 
previously set
> reassign 920318 general
Bug #920318 [bugs.debian.org] bugs.debian.org: Keyboard and Touchpad Not 
working after Kernel Upgrade
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #920318 to the same values 
previously set
Ignoring request to alter fixed versions of bug #920318 to the same values 
previously set
> reassign 920391 general
Bug #920391 [bugs.debian.org] bugs.debian.org: Boot fails without acpi=off on 
HP ENVY 13-ah0003na
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #920391 to the same values 
previously set
Ignoring request to alter fixed versions of bug #920391 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
901008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901008
915964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915964
920318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920318
920391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 963846 to general, reassign 955189 to kde-plasma-desktop, reassign 951314 to general

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 963846 general
Bug #963846 [bugs.debian.org] bugs.debian.org: usb-audio : Lexicon Omega only 2 
analog inputs in Debian 10,  while showing 4 analog inputs in Debian 9
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #963846 to the same values 
previously set
Ignoring request to alter fixed versions of bug #963846 to the same values 
previously set
> reassign 955189 kde-plasma-desktop
Bug #955189 [bugs.debian.org] bugs.debian.org: the Tab key get stuck and repeat 
after it was pressed and released
Bug reassigned from package 'bugs.debian.org' to 'kde-plasma-desktop'.
Ignoring request to alter found versions of bug #955189 to the same values 
previously set
Ignoring request to alter fixed versions of bug #955189 to the same values 
previously set
> reassign 951314 general
Bug #951314 [bugs.debian.org] bugs.debian.org: Laptop does not resume when 
undocked while suspended.
Bug reassigned from package 'bugs.debian.org' to 'general'.
Ignoring request to alter found versions of bug #951314 to the same values 
previously set
Ignoring request to alter fixed versions of bug #951314 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
951314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951314
955189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955189
963846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Simon McVittie]

On Sun, 30 Aug 2020 at 15:36:53 +0200, Raphael Hertzog wrote:
> If I know that the next upstream release
> breaks backwards compatitibly and that it will have to mature a long time
> in experimental until all other packages are ready, I might start to
> package it rigth now in debian/experimental and continue to use
> debian/latest for my unstable uploads.

If that's your workflow (the same as src:dbus, where versions 1.13.x
are a development branch not recommended for general use), then I don't
think debian/latest is a good name for that branch, and I'd recommend
using debian/unstable for your unstable uploads.

Rationale: it seems very confusing if a branch with "latest" in its name
does not contain the newest available version :-)

(debian/master didn't have that problem because it's named by analogy
to the "master" branch used in upstream git repositories, which doesn't
really have a fixed meaning anyway.)

smcv

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[The Wanderer]

On 2020-08-30 at 10:02, Simon McVittie wrote:

> Rationale: it seems very confusing if a branch with "latest" in its
> name does not contain the newest available version :-)
> 
> (debian/master didn't have that problem because it's named by
> analogy to the "master" branch used in upstream git repositories,
> which doesn't really have a fixed meaning anyway.)

This would be the reason why I would have argued against choosing
'latest' for the name. If a replacement for 'master' is needed, the best
candidate I've encountered or come up with yet is generally 'primary'.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Richard Laager]

On 8/29/20 5:19 PM, Russ Allbery wrote:
> The problem in my case with not putting a branch name in Vcs-Git is that,
> for packages for which I'm also upstream, the default branch in the
> repository named in that header is the upstream development branch, which
> contains no Debian packaging files and thus would be a very confusing
> thing for debcheckout to clone.  So I have to name *some* branch, which
> right now is debian/master and would be debian/latest.

If the packaging is on Debian Salsa (which I would recommend), then I'd
set the default branch to the packaging branch. If upstream happens to
live there too, then people can switch to that explicitly.

Rationale: The packaging is the more relevant thing to Debian. While
there are Debian native packages and some people are both upstream and
packager, the common case is software packaged from another upstream.

Then you don't need a branch name in debian/control.

-- 
Richard



signature.asc
Description: OpenPGP digital signature

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Richard Laager]

On 8/29/20 5:16 PM, Simon McVittie wrote:
> On Sat, 29 Aug 2020 at 15:07:07 -0500, Richard Laager wrote:
>> However, this is still saying that one should prefer debian/latest over
>> debian/unstable, and that debian/unstable is (sort of) only for use when
>> you're also uploading to experimental.
> 
> The way I think of it phrases this a bit differently: whether or not you
> have a version targeting experimental right now, if you *were* uploading
> to experimental, what would you do?

I think that's a perfectly reasonable way to look at the issue. I don't
think that's what the DEP-14 language says, though.

> I think the workflow used in packaging dbus (with the newly proposed
> naming: debian/unstable as default, and a debian/experimental branch
> that runs ahead of it) is fine. This is good if you want to draw most
> attention to the version in unstable, with experimental being for early
> adopters and not recommended for general use.
> 
> I think the workflow used in packaging gnome-shell (with the newly
> proposed naming: debian/latest as default, and a debian/unstable branch
> that lags behind it) is *also* fine. This is good if you want to draw
> most attention to the version in experimental (when there is one).

In both cases, I would have debian/unstable and debian/experimental
branches.

I would draw attention to the main line of development by making that as
the default branch on the server: debian/unstable in the first case and
debian/experimental in the second. That way, someone who doesn't know
the package's branch style gets a hint on clone; someone who does
already knows which branch they want and can pick it explicitly. Of
course, the same server-side HEAD setting also works (and should be
used) if debian/latest is in use.

-- 
Richard



signature.asc
Description: OpenPGP digital signature

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Richard Laager]

I think I now have a better handle on how/why I disagree with the DEP-14
recommendation language.

On 8/30/20 8:36 AM, Raphael Hertzog wrote:
> On Sat, 29 Aug 2020, Richard Laager wrote:
>> That said, I do understand we give a lot of deference to developers'
>> workflows. So I have no objection to DEP-14 supporting this workflow
>> with debian/latest. But I would like to see it (debian/latest)
>> recharacterized as the alternate approach rather than the recommended
>> method.
> 
> Your approach is perfectly valid but I don't really believe that it should
> be the recommended approach. It doesn't seem to match the most common
> workflow.
> 
> Most package maintainers are not actively working on two different
> development branches, instead the single development branch keeps moving
> between:
> - ready for unstable/upload to unstable
> - work in progress on a new upstream release
> - possible upload to experimental to gather feedback (buildd, users)
> - back to ready for upload to unstable

So you are regularly using multiple releases (unstable and experimental)
where the DEP-14 language allows you to use either debian/latest or
debian/{unstable,experimental}, but you feel debian/latest makes the
most sense most of the time in that scenario.

I think I see your point. You don't always know a priori when you are
going to want to upload to experimental. (Where you do know that, it's
because you expect the experimental piece to live in parallel for a
while and you'll use a temporary debian/experimental branch.) So you
have one debian/latest branch that can upload to unstable or
experimental as needed.

You could use debian/experimental all the time and then merge down to
debian/unstable only when you're ready to upload and have chosen
unstable. But I suspect your objection would be: that's unnecessary
busywork. And I see that point. I would probably make the same
objection, which means I think I agree with the debian/latest concept in
your situation.

I'm not sure if most package maintainers are doing this or not. I've
always assumed that most people are targetting only unstable most of the
time and that use of experimental is relatively rare. I could easily be
wrong on that. But that is definitely _my_ practice:

My package branch typically moves between:
- ready for unstable/upload to unstable
- work in progress on a new upstream release
- back to ready for upload to unstable

That is, I'm generally always targetting unstable and _not_ regularly
using multiple releases, so the DEP-14 language "prohibits" me from
using debian/unstable. This is what feels backwards to me. If I'm always
targetting unstable, debian/latest (and previously debian/master) is
less clear than debian/unstable.

At a minimum, can we rework this in some way so the language does not
require me to be regularly using multiple releases to use
debian/unstable as a branch name?

Preferably, can we change this to convey the following (probably using
better language):

  1. If you (have one line of package development and) regularly
 alternate between uploading to unstable and experimental, use
 debian/latest.
  2. If you normally only upload to unstable, use debian/unstable.
  3. If you will have a separate line of package development for upload
 to experimental, name that debian/experimental.  If that is
 long-lived, the other branch should be debian/unstable.

#1 covers your use case. #1 is listed first per your view that this is
the common case. #2 covers my use case. #3 allows either a #1 or #2
style to add debian/experimental temporarily, while recommending the
debian/{unstable,experimental} pair if the experimental branch is
long-lived (because it's confusing for debian/latest to not be the
latest version).

-- 
Richard



signature.asc
Description: OpenPGP digital signature

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Sean Whitton]

Hello Raphael,

On Fri, 28 Aug 2020, at 4:01 PM, Raphael Hertzog wrote:
> diff --git a/web/deps/dep14.mdwn b/web/deps/dep14.mdwn
> index 0316fe1..beb96ea 100644
> --- a/web/deps/dep14.mdwn
> +++ b/web/deps/dep14.mdwn
> +In the interest of homogeneity and of clarity, we recommend the use of
> +`debian/unstable` over `debian/sid` as it better conveys its special nature
> +as opposed to other branches named after codenames which are used for
> +stable releases.

I think we should recommend debian/sid because for some years dgit has been 
generating branches called dgit/sid.  I think it would smooth the integration 
between branches on salsa and branches on dgit.debian.org if both always used 
codenames.

Thanks.

Sean

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Richard Laager]

On 8/30/20 12:02 PM, Sean Whitton wrote:
> Hello Raphael,
> 
> On Fri, 28 Aug 2020, at 4:01 PM, Raphael Hertzog wrote:
>> diff --git a/web/deps/dep14.mdwn b/web/deps/dep14.mdwn
>> index 0316fe1..beb96ea 100644
>> --- a/web/deps/dep14.mdwn
>> +++ b/web/deps/dep14.mdwn
>> +In the interest of homogeneity and of clarity, we recommend the use of
>> +`debian/unstable` over `debian/sid` as it better conveys its special nature
>> +as opposed to other branches named after codenames which are used for
>> +stable releases.
> 
> I think we should recommend debian/sid because for some years dgit has been 
> generating branches called dgit/sid.  I think it would smooth the integration 
> between branches on salsa and branches on dgit.debian.org if both always used 
> codenames.

Using debian/sid makes the branch name inconsistent with
debian/changelog, which traditionally uses "unstable" not "sid". It also
makes debian/experimental an outlier that cannot be made consistent
(because there is no character code name for experimental AFAIK).

-- 
Richard



signature.asc
Description: OpenPGP digital signature

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[The Wanderer]

On 2020-08-30 at 14:46, Richard Laager wrote:

> On 8/30/20 12:02 PM, Sean Whitton wrote:
>
>> Hello Raphael,
>> 
>> On Fri, 28 Aug 2020, at 4:01 PM, Raphael Hertzog wrote:
>>> diff --git a/web/deps/dep14.mdwn b/web/deps/dep14.mdwn
>>> index 0316fe1..beb96ea 100644
>>> --- a/web/deps/dep14.mdwn
>>> +++ b/web/deps/dep14.mdwn
>>> +In the interest of homogeneity and of clarity, we recommend the use of
>>> +`debian/unstable` over `debian/sid` as it better conveys its special nature
>>> +as opposed to other branches named after codenames which are used for
>>> +stable releases.
>> 
>> I think we should recommend debian/sid because for some years dgit
>> has been generating branches called dgit/sid. I think it would
>> smooth the integration between branches on salsa and branches on
>> dgit.debian.org if both always used codenames.
> 
> Using debian/sid makes the branch name inconsistent with 
> debian/changelog, which traditionally uses "unstable" not "sid". It
> also makes debian/experimental an outlier that cannot be made
> consistent (because there is no character code name for experimental
> AFAIK).

I thought the same at one point, but in fact, there is: it's called
rc-buggy.

https://wiki.debian.org/DebianReleases#Codenames
http://ftp.debian.org/debian/dists/rc-buggy/

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Geert Stappers]

On Sun, Aug 30, 2020 at 02:52:33PM -0400, The Wanderer wrote:
> On 2020-08-30 at 14:46, Richard Laager wrote:
> > On 8/30/20 12:02 PM, Sean Whitton wrote:
> >> On Fri, 28 Aug 2020, at 4:01 PM, Raphael Hertzog wrote:
> >>> diff --git a/web/deps/dep14.mdwn b/web/deps/dep14.mdwn
> >>> index 0316fe1..beb96ea 100644
> >>> --- a/web/deps/dep14.mdwn
> >>> +++ b/web/deps/dep14.mdwn
> >>> +In the interest of homogeneity and of clarity, we recommend the use of
> >>> +`debian/unstable` over `debian/sid` as it better conveys its special 
> >>> nature
> >>> +as opposed to other branches named after codenames which are used for
> >>> +stable releases.
> >> 
> >> I think we should recommend debian/sid because for some years dgit
> >> has been generating branches called dgit/sid. I think it would
> >> smooth the integration between branches on salsa and branches on
> >> dgit.debian.org if both always used codenames.

Yes,  DEP-14 is about providing guidelines for this.

And DEP-14  guides the URL for `debcheckout`

 
> > Using debian/sid makes the branch name inconsistent with 
> > debian/changelog, which traditionally uses "unstable" not "sid".

There no need to have consistency between a git branch name
and debian/changelog saying where to upload.


> > It also makes debian/experimental an outlier that cannot be made
> > consistent (because there is no character code name for experimental
> > AFAIK).
> 
> I thought the same at one point, but in fact, there is: it's called
> rc-buggy.
> 
> https://wiki.debian.org/DebianReleases#Codenames
> http://ftp.debian.org/debian/dists/rc-buggy/
> 


Learn from bikeshedding that it is just bikeshedding.



Regards
Geert Stappers
-- 
Silence is hard to parse

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Mathias Behrle]

* Simon McVittie: " Re: RFC: Final update of DEP-14 on naming of git packaging
  branches" (Sun, 30 Aug 2020 15:02:35 +0100):

> On Sun, 30 Aug 2020 at 15:36:53 +0200, Raphael Hertzog wrote:
> > If I know that the next upstream release
> > breaks backwards compatitibly and that it will have to mature a long time
> > in experimental until all other packages are ready, I might start to
> > package it rigth now in debian/experimental and continue to use
> > debian/latest for my unstable uploads.  
> 
> If that's your workflow (the same as src:dbus, where versions 1.13.x
> are a development branch not recommended for general use), then I don't
> think debian/latest is a good name for that branch, and I'd recommend
> using debian/unstable for your unstable uploads.
> 
> Rationale: it seems very confusing if a branch with "latest" in its name
> does not contain the newest available version :-)

+1

Additionally I think explicit is usually better than implicit. When all other
branches are named following their suites why should we diverge for this special
case?
 
> (debian/master didn't have that problem because it's named by analogy
> to the "master" branch used in upstream git repositories, which doesn't
> really have a fixed meaning anyway.)

BTW the same applies for me to the (re-)naming of the 'default' branch
(currently master). If it is the default branch the most plausible name is just
'default'.


-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6


pgppPckIukqb9.pgp
Description: Digitale Signatur von OpenPGP

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Adam D. Barratt]

On Sun, 2020-08-30 at 14:52 -0400, The Wanderer wrote:
> On 2020-08-30 at 14:46, Richard Laager wrote:
[...]
> > (because there is no character code name for
> > experimental AFAIK).
> 
> I thought the same at one point, but in fact, there is: it's called
> rc-buggy.
> 
> https://wiki.debian.org/DebianReleases#Codenames
> http://ftp.debian.org/debian/dists/rc-buggy/

Yes and no.

The suite doesn't officially have a codename, as examining the Release
files will show. There's a symlink in the dists directory, similarly to
dists/Debian10.5.

Regards,

Adam

Processed: reassign 865067 to gnome-settings-daemon

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 865067 gnome-settings-daemon
Bug #865067 [general] general: Custom keyboard shortcuts combination issues
Bug reassigned from package 'general' to 'gnome-settings-daemon'.
Ignoring request to alter found versions of bug #865067 to the same values 
previously set
Ignoring request to alter fixed versions of bug #865067 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#951314: marked as done (bugs.debian.org: Laptop does not resume when undocked while suspended.)

[Debian Bug Tracking System]

Your message dated Mon, 31 Aug 2020 00:31:13 +0200
with message-id <20200830223111.vuzbm6yjgz5ub...@percival.namespace.at>
and subject line Re: Bug#951314: bugs.debian.org: Laptop does not resume when 
undocked while suspended.
has caused the Debian Bug report #951314,
regarding bugs.debian.org: Laptop does not resume when undocked while suspended.
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 ow...@bugs.debian.org
immediately.)


-- 
951314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Undocking my suspended Laptop and resumed it in the train.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Suspended the laptop the night before (via the sleep button). Opened the lid a
day later after I unplugged it from the dock.
   * What was the outcome of this action?
Screen was blank. Switching to other virtual consoles did not work. No reaction
to alt+ctrl+del shortcut. Only reboot by pressing the power button for several
seconds worked for me.
   * What outcome did you expect instead?
Open the lid, see the lock screen, log in.



-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---

Hi Robin de Silva Jayasinghe,

thanks for your interest in making Debian better and filing
this report:

* Robin de Silva Jayasinghe  [200830 22:30]:
>* What led up to the situation?
> Undocking my suspended Laptop and resumed it in the train.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> Suspended the laptop the night before (via the sleep button). Opened the lid a
> day later after I unplugged it from the dock.
>* What was the outcome of this action?
> Screen was blank. Switching to other virtual consoles did not work. No 
> reaction
> to alt+ctrl+del shortcut. Only reboot by pressing the power button for several
> seconds worked for me.
[..]

However, at this time it looks more like a support request,
and the bug tracker is not well-suited for helping users
interactively.

Please try getting help first from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#969263: closed by Chris Hofstaedtler (Re: Bug#969263: bugs.debian.org: debian 10 does not let me install vmware tools)

[Paul Flaherty]

I still get the issue regarding this

Get Outlook for iOS

From: Debian Bug Tracking System 
Sent: Sunday, August 30, 2020 6:24:05 PM
To: Paul Flaherty 
Subject: Bug#969263 closed by Chris Hofstaedtler  (Re: 
Bug#969263: bugs.debian.org: debian 10 does not let me install vmware tools)

This is an automatic notification regarding your Bug report
which was filed against the general package:

#969263: bugs.debian.org: debian 10 does not let me install vmware tools

It has been closed by Chris Hofstaedtler .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Chris Hofstaedtler 
 by
replying to this email.


--
969263: 
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.debian.org%2Fcgi-bin%2Fbugreport.cgi%3Fbug%3D969263&data=02%7C01%7C%7Ca7c0ae45cd2146b9154b08d84d3368fb%7C84df9e7fe9f640afb435%7C1%7C0%7C637344230497128706&sdata=IaX43nNisUHbB57Vo0jxp737y5Grc1oocqQO%2FXjvYvg%3D&reserved=0
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#920391: marked as done (bugs.debian.org: Boot fails without acpi=off on HP ENVY 13-ah0003na)

[Debian Bug Tracking System]

Your message dated Mon, 31 Aug 2020 00:42:42 +0200
with message-id <20200830224241.6t4t6fz2cysma...@percival.namespace.at>
and subject line Re: Bug#920391: bugs.debian.org: Boot fails without acpi=off 
on HP ENVY 13-ah0003na
has caused the Debian Bug report #920391,
regarding bugs.debian.org: Boot fails without acpi=off on HP ENVY 13-ah0003na
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 ow...@bugs.debian.org
immediately.)


-- 
920391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: normal

Dear Maintainer,

I can only boot into Debian if I use the option acpi=off; this is from a fresh 
install. Using acpi=ht also fails to boot.

-- System Information:
Debian Release: 9.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi Jake P,

thank you for your interest in making Debian better and filing this
report:

* Jake P  [200830 22:39]:
> I can only boot into Debian if I use the option acpi=off; this is from a 
> fresh install. Using acpi=ht also fails to boot.

>From other discussions on the Internet it appears the Envy 13
hardware/firmware generally doesn't support non-Windows OS, and a
lot of hacks are required to make stuff work at all.

I don't consider this a bug in Debian, even if Debian or various
components can add workarounds to improve the situation. If
motivated Envy 13 owners can help with this, please coordinate the
work on the relevant upstream channels.

For now, I'm closing this bug as there won't be much we can do on
the Debian side.

Thank you for your understanding,
Chris--- End Message ---

Bug#969263: closed by Chris Hofstaedtler (Re: Bug#969263: bugs.debian.org: debian 10 does not let me install vmware tools)

[Paul Flaherty]

I still get issue

Get Outlook for iOS

From: Debian Bug Tracking System 
Sent: Sunday, August 30, 2020 6:24:05 PM
To: Paul Flaherty 
Subject: Bug#969263 closed by Chris Hofstaedtler  (Re: 
Bug#969263: bugs.debian.org: debian 10 does not let me install vmware tools)

This is an automatic notification regarding your Bug report
which was filed against the general package:

#969263: bugs.debian.org: debian 10 does not let me install vmware tools

It has been closed by Chris Hofstaedtler .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Chris Hofstaedtler 
 by
replying to this email.


--
969263: 
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.debian.org%2Fcgi-bin%2Fbugreport.cgi%3Fbug%3D969263&data=02%7C01%7C%7Ca7c0ae45cd2146b9154b08d84d3368fb%7C84df9e7fe9f640afb435%7C1%7C0%7C637344230497128706&sdata=IaX43nNisUHbB57Vo0jxp737y5Grc1oocqQO%2FXjvYvg%3D&reserved=0
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#942698: bugs.debian.org: Multiple Call Traces in dmesg

[Chris Hofstaedtler]

Control: reassign -1 linux-image-4.19.0-6-amd64
Control: retitle -1 i915 workqueue issue / i915_hotplug_work_func 
__flush_work.cold.53

Hi sanshu,

thank you for your interest in making Debian better and filing this
report:

* sanshu  [200830 22:46]:
> [2.158101] [ cut here ]
> [2.158108] WARNING: CPU: 0 PID: 13 at kernel/workqueue.c:2911
> __flush_work.cold.53+0x1f/0x29
> [2.158168] Workqueue: events i915_hotplug_work_func [i915]
[..]

Other discussions on f.e. the Fedora bug tracker suggest that this
has been fixed in Linux kernel 5.3 or 5.4. Can you please try with
one of those versions (or just the current Debian 4.19) and see if
the problem goes away?

If the problem persists in 4.19, but is gone in 5.3/5.4, it might be
useful to "git bisect" to find the fix. Maybe it can be included in
a buster update, then.

Chris

Processed: Re: Bug#942698: bugs.debian.org: Multiple Call Traces in dmesg

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 linux-image-4.19.0-6-amd64
Bug #942698 [general] bugs.debian.org: Multiple Call Traces in dmesg
Bug reassigned from package 'general' to 'linux-image-4.19.0-6-amd64'.
Warning: Unknown package 'linux-image-4.19.0-6-amd64'
Warning: Unknown package 'linux-image-4.19.0-6-amd64'
Ignoring request to alter found versions of bug #942698 to the same values 
previously set
Warning: Unknown package 'linux-image-4.19.0-6-amd64'
Warning: Unknown package 'linux-image-4.19.0-6-amd64'
Ignoring request to alter fixed versions of bug #942698 to the same values 
previously set
Warning: Unknown package 'linux-image-4.19.0-6-amd64'
> retitle -1 i915 workqueue issue / i915_hotplug_work_func __flush_work.cold.53
Bug #942698 [linux-image-4.19.0-6-amd64] bugs.debian.org: Multiple Call Traces 
in dmesg
Warning: Unknown package 'linux-image-4.19.0-6-amd64'
Changed Bug title to 'i915 workqueue issue / i915_hotplug_work_func 
__flush_work.cold.53' from 'bugs.debian.org: Multiple Call Traces in dmesg'.
Warning: Unknown package 'linux-image-4.19.0-6-amd64'

-- 
942698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Russ Allbery]

Richard Laager  writes:
> On 8/29/20 5:19 PM, Russ Allbery wrote:

>> The problem in my case with not putting a branch name in Vcs-Git is
>> that, for packages for which I'm also upstream, the default branch in
>> the repository named in that header is the upstream development branch,
>> which contains no Debian packaging files and thus would be a very
>> confusing thing for debcheckout to clone.  So I have to name *some*
>> branch, which right now is debian/master and would be debian/latest.

> If the packaging is on Debian Salsa (which I would recommend), then I'd
> set the default branch to the packaging branch. If upstream happens to
> live there too, then people can switch to that explicitly.

This is a good point.

I have to admit that I wrote and deleted three different progressively
less upset replies because I apparently have a lot of emotional baggage
about project Git hosting.  I think I'm realizing that part of what's
upsetting me is exactly that we're not standardizing on Salsa or some
other Git repository collection as the canonical place where as much of
Debian packaging as possible is stored.  And while I can't change that
reality, pushing all of my own packaging to Salsa certainly wouldn't hurt
the goal of moving us in that direction, so maybe I should do that.

I agree that then makes the issue of Vcs-Git branch names moot.

If we could upload a package to the archive by pushing a signed tag to
Salsa, that of course would be even better and would, at least for me,
make Debian a more delightful project on which to work.

-- 
Russ Allbery (r...@debian.org)  

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Russ Allbery]

Geert Stappers  writes:
> On 2020-08-30 at 14:46, Richard Laager wrote:

>> Using debian/sid makes the branch name inconsistent with 
>> debian/changelog, which traditionally uses "unstable" not "sid".

> There no need to have consistency between a git branch name and
> debian/changelog saying where to upload.

There is no *need* in the sense that the lack of correspondance will not
break anything technically, but these sorts of little inconsistencies and
arcana add friction, confusion, and irritation for people who don't work
with Debian regularly.  Making these sorts of things consistent does more
than it may appear at reducing the cognitive load and perceived fiddliness
of packaging, and therefore can help new packagers feel comfortable more
quickly.

It also creates the possibility for tools to observe inconsistencies like
"you're packaging in a branch named experimental but your upload is
targeting unstable," which would have caught some errors that I've made
even as an experienced packager.

-- 
Russ Allbery (r...@debian.org)  

Bug#872930: marked as done (general: reboots every time even when i shut it down)

[Debian Bug Tracking System]

Your message dated Mon, 31 Aug 2020 01:42:47 +0200
with message-id <20200830234246.y5kshnggn5in5...@percival.namespace.at>
and subject line Re: Bug#872930: general: reboots every time even when i shut 
it down
has caused the Debian Bug report #872930,
regarding general: reboots every time even when i shut it down
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 ow...@bugs.debian.org
immediately.)


-- 
872930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Dear Maintainer,

When I shut down my computer it reboots every time, but only when I use
Linux (debian). However, I don't have this problem with Windows. I have both of
the OSs on the same computer.
And only when debian reboots after I tried to suspend it, and error
message appears before. It says something like :
"* time is in the future ( by less than a day probably due to *'s clock...)"
This message doesn't appear after using Windows or turning off the computer by
removing the battery.

Thank you,



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
* Geert Stappers  [200830 23:42]:
> Who thinks that this bug should be closed.

Doing this, then.

Chris--- End Message ---

Bug#878259: marked as done (general: Image icons progressively becoming either absent or default placemat whatever settings)

[Debian Bug Tracking System]

Your message dated Mon, 31 Aug 2020 01:47:30 +0200
with message-id <20200830234729.ktvyqpkmtrtqf...@percival.namespace.at>
and subject line Re: Bug#878259: general: Image icons progressively becoming 
either absent or default placemat whatever settings
has caused the Debian Bug report #878259,
regarding general: Image icons progressively becoming either absent or default 
placemat whatever settings
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 ow...@bugs.debian.org
immediately.)


-- 
878259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Dear Maintainer,

Debian Sid/Buster loosing image icons for file browsers Nautilus, Nemo
(becoming default placemat tree image) and Dolphin (totally blank). Changing
the threshold value for displaying images in Nautilus had no effect. Only new
or modified files effected for Nautilus, Nemo but all files for Dolphin. Effect
noticed shortly after upgrade from Stretch to Buster 64bit.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi Jon,

thanks for your interest in making Debian better and filing
this report:

* Jon :
> Debian Sid/Buster loosing image icons for file browsers Nautilus, Nemo
> (becoming default placemat tree image) and Dolphin (totally blank). Changing
> the threshold value for displaying images in Nautilus had no effect. Only new
> or modified files effected for Nautilus, Nemo but all files for Dolphin. 
> Effect
> noticed shortly after upgrade from Stretch to Buster 64bit.

However, at this time it looks more like a support request,
and the bug tracker is not well-suited for helping users
interactively.

Please try getting help first from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Bug#964940: marked as done (bugs.debian.org: After an upgrade and crash, the boot process say ACPI error: AE_NOT_FOUND. I think that the problem was an upgrade not completed on the bios machine or

[Debian Bug Tracking System]

Your message dated Mon, 31 Aug 2020 01:48:50 +0200
with message-id <20200830234849.jezb7nkmm63uy...@percival.namespace.at>
and subject line Re: Bug#964940: bugs.debian.org: After an upgrade and crash, 
the boot process say  ACPI error:  AE_NOT_FOUND.  I think that the problem was 
an upgrade not completed on the bios machine or similar.
has caused the Debian Bug report #964940,
regarding bugs.debian.org: After an upgrade and crash, the boot process say  
ACPI error:  AE_NOT_FOUND.  I think that the problem was an upgrade not 
completed on the bios machine or similar.
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 ow...@bugs.debian.org
immediately.)


-- 
964940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: important

Dear Maintainer,

On the subject. Thank you.



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-9-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_VE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi Juan Alberto Zarate Sanoja,

thanks for your interest in making Debian better and filing
this report:

* Juan Alberto Zarate Sanoja :
> After an upgrade and crash, the
> boot process say  ACPI error:  AE_NOT_FOUND.  I think that the problem was
>  an upgrade not completed on the bios machine or similar.
> On the subject. Thank you.

However, at this time it looks more like a support request,
and the bug tracker is not well-suited for helping users
interactively.

Please try getting help first from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Processed: reassign 936096 to src:linux, found 936096 in 5.2.9-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 936096 src:linux
Bug #936096 [general] bugs.debian.org: Wlan switch on and off after update 4.19 
to 5.2 (normal Testing update)
Bug reassigned from package 'general' to 'src:linux'.
Ignoring request to alter found versions of bug #936096 to the same values 
previously set
Ignoring request to alter fixed versions of bug #936096 to the same values 
previously set
> found 936096 5.2.9-2
Bug #936096 [src:linux] bugs.debian.org: Wlan switch on and off after update 
4.19 to 5.2 (normal Testing update)
Marked as found in versions linux/5.2.9-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
936096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 920318 to src:linux, retitle 920318 to Quanta VZ1: keyboard, touchpad broken since 4.9.0-8

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 920318 src:linux
Bug #920318 [general] bugs.debian.org: Keyboard and Touchpad Not working after 
Kernel Upgrade
Bug reassigned from package 'general' to 'src:linux'.
Ignoring request to alter found versions of bug #920318 to the same values 
previously set
Ignoring request to alter fixed versions of bug #920318 to the same values 
previously set
> retitle 920318 Quanta VZ1: keyboard, touchpad broken since 4.9.0-8
Bug #920318 [src:linux] bugs.debian.org: Keyboard and Touchpad Not working 
after Kernel Upgrade
Changed Bug title to 'Quanta VZ1: keyboard, touchpad broken since 4.9.0-8' from 
'bugs.debian.org: Keyboard and Touchpad Not working after Kernel Upgrade'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
920318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#915964: marked as done (bugs.debian.org: Boot process with kernel 4.18.0.3 fails and goes to black screen.)

[Debian Bug Tracking System]

Your message dated Mon, 31 Aug 2020 01:55:09 +0200
with message-id <20200830235508.syobgdcnoir3n...@percival.namespace.at>
and subject line Re: Bug#915964: bugs.debian.org: Boot process with kernel 
4.18.0.3 fails and goes to black screen.
has caused the Debian Bug report #915964,
regarding bugs.debian.org: Boot process with kernel 4.18.0.3 fails and goes to 
black screen.
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 ow...@bugs.debian.org
immediately.)


-- 
915964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Standard terminal update of Debian Testing system that included the new kernel.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi alanscott221,

thanks for your interest in making Debian better and filing
this report:

* alanscott221 :
> Standard terminal update of Debian Testing system that included the new 
> kernel.

However, at this time it looks more like a support request,
and the bug tracker is not well-suited for helping users
interactively.

Please try getting help first from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Processed: reassign 943791 to src:linux ..., reassign 823124 to src:linux, reassign 901008 to src:linux

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 943791 src:linux
Bug #943791 [general] general: laptop HP 15_bw0xx does not power-off properly
Bug reassigned from package 'general' to 'src:linux'.
Ignoring request to alter found versions of bug #943791 to the same values 
previously set
Ignoring request to alter fixed versions of bug #943791 to the same values 
previously set
> forwarded 823124 
> https://github.com/linuxwacom/input-wacom/issues/110#issuecomment-557458801
Bug #823124 [general] general: Wacom stylus / touch screen no longer work after 
OS resumes from sleep mode.
Set Bug forwarded-to-address to 
'https://github.com/linuxwacom/input-wacom/issues/110#issuecomment-557458801'.
> reassign 823124 src:linux
Bug #823124 [general] general: Wacom stylus / touch screen no longer work after 
OS resumes from sleep mode.
Bug reassigned from package 'general' to 'src:linux'.
Ignoring request to alter found versions of bug #823124 to the same values 
previously set
Ignoring request to alter fixed versions of bug #823124 to the same values 
previously set
> reassign 901008 src:linux
Bug #901008 [general] bugs.debian.org: Hibernation fails when RAM usage is high
Bug reassigned from package 'general' to 'src:linux'.
Ignoring request to alter found versions of bug #901008 to the same values 
previously set
Ignoring request to alter fixed versions of bug #901008 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823124
901008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901008
943791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#963846: bugs.debian.org: usb-audio : Lexicon Omega only 2 analog inputs in Debian 10, while showing 4 analog inputs in Debian 9

[Chris Hofstaedtler]

Hi,

thanks for your interest in making Debian better and filing
this report:

* G Bradsly :
> In Debian 9 I had 4 analog inputs, 2 analog outputs, an in and out s/pdif and
> an in and out midi
> In Debian 10 I have only 2 analog inputs, the analog outputs, s/pdif i/o and
> midi i/o are the same.
> In short : I'm missing 2 analog inputs! What gives?

However, more diagnosing work is needed to identify where the
problem lies. Please try general troubleshooting: different audio
systems, check what ALSA has to say, try PulseAudio, and maybe try a
newer or older kernel version.

You can find help with these things at other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please reassign this bug to
the package having the bug.


Thank you for your understanding,
Chris

Bug#969302: ITP: bluez-alsa -- Bluetooth Audio ALSA Backend

[Nobuhiro Iwamatsu]

Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: bluez-alsa
  Version : 2.1.0
  Upstream Author : Arkadiusz Bokowy
* URL : https://github.com/Arkq/bluez-alsa
* License : Expat
  Programming Lang: C
  Description : Bluetooth Audio ALSA Backend


This project is a rebirth of a direct integration between BlueZ and
ALSA. Since BlueZ >= 5, the build-in integration has been removed in
favor of 3rd party audio applications. From now on, BlueZ acts as a
middleware between an audio application, which implements Bluetooth
audio profile, and a Bluetooth audio device.

Bug#942406: marked as done (bugs.debian.org: Dual Monitors - Full Screen behaviour)

[Debian Bug Tracking System]

Your message dated Mon, 31 Aug 2020 02:12:06 +0200
with message-id <20200831001205.3h3t6sucr4ans...@percival.namespace.at>
and subject line Re: Bug#942406: bugs.debian.org: Dual Monitors - Full Screen 
behaviour
has caused the Debian Bug report #942406,
regarding bugs.debian.org: Dual Monitors - Full Screen behaviour
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 ow...@bugs.debian.org
immediately.)


-- 
942406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: important

Dual identical monitors on Raspberry PI, 
and Intel machine with dual identical graphics cards 
and same two monitors. full screen expands only to a single monitor.

Desired behavior is to expand window to fill both monitors.


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Architecture: armv7l

Kernel: Linux 4.19.75-v7l+ (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi Duncan Hare,

* Duncan Hare :
[..]
> Distributor ID:   Raspbian
> Description:  Raspbian GNU/Linux 10 (buster)

You seem to have filed a bug about Raspbian in the Debian bug
tracker - please try the Raspbian support channels instead.

Thank you for your understanding,
Chris--- End Message ---

Bug#865771: marked as done (general: always stuck before reaching gui mode and can not reach text mode with ctrl + alt + f6 (debian 9 stable, asus rog552vx))

[Debian Bug Tracking System]

Your message dated Mon, 31 Aug 2020 02:13:22 +0200
with message-id <20200831001321.xibagugltsmqi...@percival.namespace.at>
and subject line Re: Bug#865771: general: always stuck before reaching gui mode 
and can not reach text mode with ctrl + alt + f6 (debian 9 stable, asus 
rog552vx)
has caused the Debian Bug report #865771,
regarding general: always stuck before reaching gui mode and can not reach text 
mode with ctrl + alt + f6 (debian 9 stable, asus rog552vx)
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 ow...@bugs.debian.org
immediately.)


-- 
865771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 9.0
Architecture: amd64 (x86_64)
Foreign Architectures: i382, i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=id_ID.UTF-8, LC_CTYPE=id_ID.UTF-8 (charmap=UTF-8), 
LANGUAGE=id_ID.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi agung vega,,

thanks for your interest in making Debian better and filing
this report:

> always stuck before reaching gui mode and
>can not reach text mode with ctrl + alt + f6 (debian 9 stable, asus
>rog552vx)

However, at this time it looks more like a support request,
and the bug tracker is not well-suited for helping users
interactively.

Please try getting help first from other venues listed at
   https://www.debian.org/support - especially IRC,
the mailing lists or http://forums.debian.net/ .

Once there is a clear bug identified, please file a new report
against the package having the bug.

Thank you for your understanding,
Chris--- End Message ---

Processed: Re: Bug#966004: bugs.debian.org: .XCompose fails to make long substitutions

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libx11-6
Bug #966004 [general] bugs.debian.org: .XCompose fails to  make long 
substitutions
Bug reassigned from package 'general' to 'libx11-6'.
Ignoring request to alter found versions of bug #966004 to the same values 
previously set
Ignoring request to alter fixed versions of bug #966004 to the same values 
previously set

-- 
966004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#966004: bugs.debian.org: .XCompose fails to make long substitutions

[Chris Hofstaedtler]

Control: reassign -1 libx11-6

XCompose appears to be a libX11 feature, reassigning there.

Best,
Chris

Re: RFC: Final update of DEP-14 on naming of git packaging branches

[Emmanuel Arias]

Hi,

From my point of view (newbie point of view) it's more natural use the
default branch as my "target" codename. I mean, if I'm working on a
package that I will upload to unstable I hope use debian/unstable branch
for that. If I want to test or for any reason upload package to
experimental (or backport) I will prefer use for that a
debian/experimental for instance.

Introducing the the debian/latest name, for me, it's more like the
latest version, maybe on development before upload, but don't give me
more information about the status of the package. I think could be more
appropriate the name debian/dev, thinking on package into a Team.


On 8/28/20 8:01 PM, Raphael Hertzog wrote:
> Hello,
> 
> following the recent discussions of June and of the last days, I'm
> proposing the changes below to DEP-14. Basically it replaces debian/master
> with debian/latest for all the reasons already discussed earlier. And
> it says that debian/unstable is preferred over debian/sid.
> 
> And it also marks the proposal as ACCEPTED given that it has gained
> traction over the years and that we didn't feel the need to make
> significant change to it.


0xFA9DEC5DE11C63F1.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature