Bug#1068957: ITP: gnome-shell-extension-vertical-workspaces -- A GNOME Shell extension that lets you customize your GNOME Shell UX to suit your workflow, whether you like horizontally or vertically st

[Tobias Frost]

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

* Package name: gnome-shell-extension-vertical-workspaces
  Version : (tbd, likely a git snapshot)
  Upstream Contact: GdH 
* URL : https://github.com/G-dH/vertical-workspaces
* License : GPL-3.0
  Programming Lang: Javascript
  Description : A GNOME Shell extension that lets you customize your GNOME 
Shell UX to suit your workflow, whether you like horizontally or vertically 
stacked workspaces.

A GNOME Shell extension that lets you customize your GNOME Shell UX to suit 
your workflow, whether you like horizontally or vertically stacked workspaces.

Features:
  - Vertically or horizontally stacked workspaces
  - Adjust position, orientation, scale and visibility of overview content
  - Customizable profiles offer predefined configurations for GNOME
3.xx, GNOME 40+ and another 2 custom layouts
  - 2 overview modes with static windows/workspace. The Static Workspace
option allows you to use dash like a dock with auto-hide, but with
all advantages of the activities overview
  - Support for secondary monitors, workspace thumbnails can be placed
on the opposite side than on the primary monitor
  - Wallpaper background with adjustable blur effect and brightness in
the overview
  - Custom Dash icon size and on-click/scroll behavior
  - Optional workspace isolated Dash
  - Dash background transparency and corner radius adjustments
  - Adjustable app grid icon size, number of columns and rows, content,
optional active and draggable icons in folder preview in optional
3x3 grid
  - Custom search view width, app results icons size and number of
result lists rows, improved app search
  - Workspace thumbnails can show background wallpaper and labels
(always or on mouse hover) with combination of workspace index,
workspace name, name of the current application and current window
title
  - Title captions of window previews moved into the preview (originally
beneath the preview) and can be set as always visible. Adjustable
window preview icon
  - Static background in workspace switcher (outside overview). Keeps
Conky below, DING desktop icons stay visible (if not covered by
windows)
  - Control over transition animations, including speed
  - Recent files search provider with Ctrl + Space hotkey
  - Supports WSP (Window search provider) extension with Space hotkey
that allows quick window navigation
  - Supports ESP (Extensions search provider) with Ctrl + Shift + Space
hotkey that allows to search for installed extensions, open their
settings and enable or disable them
  - Reorder workspaces in overview using Shift + Scroll or Shift + Page
Up/Down
  - Adds Force Quit, Close Windows on Current Workspace and Move Windows
to Current Workspace items to app icon menu. The latter action can
be activated using Shift + click on app icon
  - Change notification banners and OSD popups position
  - Window attention handler options can activate the
attention-demanding window immediately or silence its notification
  - Optional position of the hot corner that can follow the dash and
expand to hot edge
  - Super key double-press options
  - Supports WTMB (Window Thumbnails) extension that allows you to
create Picture-in-Picture thumbnail of the window by clicking on its
preview in the overview (secondary mouse buttons or window preview
icon)

This is a replacement for gnome-shell-extension-vertical-overview, which
is dead-uptream and will stop working with GNOME 45.
gnome-shell-extension-vertical-overview will be removed from Debian once
this package is ready.

Re: Wolfram Research Debian Package Submission

[Tobias Frost]

Control: tags 1032150 wontfix

Hello Blake,

(Dropping several mails from CC, as those are the wrong adressees for
the topic; Adding the ITP bug though, as the discussion should happen
there.)

On Fri, Jan 12, 2024 at 09:42:18AM -0600, Blake Gilbert wrote:
> Hello, 
> 
> My name is Blake Gilbert and I work in the partnerships group at
> Wolfram Research. 
> 
> I am reaching out to you regarding a recent package submission by our
> Engine Connectivity Engineering team. We submitted the package CDImage
> M-LINUX-WolframEngine.DEB a few months ago to include Wolfram Engine
> in Debian packages, and I wanted to see if there was some way to help
> move this project forward. Would you be able to assist with this
> process or know the proper person to connect to? 

As elbrus mentioned already, please consult the resources on 
https://mentors.debian.net/intro-maintainers/ on packaing, and as
you are upstream, this page is important too:
https://wiki.debian.org/UpstreamGuide

After seeing your mail I was curious and downloaded the deb you've
linked in #1032150, and examined it's content.
Unfortunatly, your package will need a lots of refactoring until it
will be fit for inclusion into Debian. Please consult the linked
resources above, and the documents that are linked there, especially
the Debian Policy Manual)

Here are two examples:
 - you're shipping everyhing in /opt, 
 - the vendoring of system libraries (eg libssh, but it seems you are
   shipping everything you need vendored, as your package Depends:
   on nothing)

But there is even a more severe problem, I would even say this makes
this bug "wontfix" until this has been resolved. 

The package's d/copyright has:
  (...)
  Prohibited Uses
  All uses of the Software and other elements of the Free Engine not
  specifically allowed under these terms or otherwise set forth in
  alternative or supplemental license agreements or terms of use are
  prohibited, including, without limitation:
  (...)
  distributing, publishing, transferring, sublicensing, lending,
  leasing, renting or otherwise making available any portion of the
  Free Engine, including collections of data;
  copying or allowing copying of the Free Engine or any elements of the
  Free Engine, except as permitted for the maintenance of a single
  archival copy of the Engine; 

Please note the usual IANAL disclaimer, but doesn't this make it
legally impossible for Debian to include the package into our
archives? Even non-free requires *at least* the permission for
(re-)distribution and all those associated rights you need that you 
actually can, technically, do the (re)distribution?

I understand that your software is non-free and commercial in
nature, and that you do not want to publish the source code.
However, not having the source code will make it impossible for
Debian to properly maintain the software in Debian [1], especially if
Wolfram Alpha loses interest in maintaining it or if there are
urgent problems to be fixed. 

[1] even if non-free is not officially part of Debian, we still
want to give our users a good experience -- see our Social Contract.

To be honest with you: many people in Debian (including me) will not
sponsor packages, when there is no source available, so even if you
invest a lot of time into brining the package on a more
suitable-for-Debian quality level, there will be no guarantee that
your package will be accepted in the end. 

Other thoughts: 
- you can always host your own Debian archives, if you wish so, and
  maintain the package outside of Debian; 
- Another approach could be to have an package in Debian, which will
  download and install e.g to the users directory -- for example
  this is how the package "steam-installer" does it to install Steam.)

--
tobi

Re: reference Debian package of multiple binaries sharing one man page

[Tobias Frost]

On Fri, Nov 10, 2023 at 08:20:35PM +0100, Norwid Behrnd wrote:
> Hello,
> 
> I seek a maintained Debian package which provides multiple binaries sharing 
> one
> man page in common -- do you know an example?

devscripts - it links debchange.1 to dch.1 via debian/links  (dh_link)

$grep -r dch debian/links
/usr/bin/debchange  /usr/bin/dch

-- 
tobi

Re: Hyphens in man pages

[Tobias Frost]

Am 24. Oktober 2023 03:43:29 UTC schrieb Paul Wise :

>BTW: as a Debian member, you have access to a gratis subscription:
>
>https://wiki.debian.org/MemberBenefits#LWN

AFAIK this is no longer available.

Re: Bug#1053165: ITS: nunit

[Tobias Frost]

Hi Bastian,

I'd just want to chime in and confirm what David wrote aleady. When we
wrote the ITS procedure during Debconf Tawain, it was an explicitly designed
that way, that it must not be a way to fast-orphan packages, bypassing
the processes we have for that. This was intentional engineered that
way, e.g to balance the procedure and the maintainers expectations, e.g
to increase the acceptance of the "new procecure" in the project.

IF you are interested in the Some of the thought and rationales, I
encourage you to read the announcment back then [1]

[1] https://lists.debian.org/debian-devel/2018/07/msg00453.html

On Thu, Sep 28, 2023 at 05:22:20PM +0200, Bastian Germann wrote:
> Okay. What do you suggest for "team maintained" packages where there is no 
> active team member?
> File MIA processes for each of the uploaders? 

Yes, involve the MIA team.

> And then? The MIA team's bugs are not RC bugs,
> so you cannot even NMU them based on the MIA bug.

> I think, just letting such packages rot for one or two decades does not help 
> anybody, certainly not our users.

Orphaning will not magically cure bit-rot or fix the unmaintained
package problem. 

As written somewhere else in this thread, NMU needs to fix bugs, but if
something is bit-rotted, there should be reported bugs, the bugs need
*not* to be RC and even wishlist bugs can be (and I have done this) in
the the scope of an NMU, especially if they are reported since a while.

-- 
tobi (as MIA team member and author of the ITS process)


signature.asc
Description: PGP signature

Re: what about package for my simple program

[Tobias Frost]

Hi Oleg,

debian-devel is the wrong mailing list for your topic, may I re-suggest to move
this thread to the debian-mentors mailing list, which is more appropiate.
(I've set the Reply-To Header to hint your MUA accordingly.)

(For d-mentors readers, the original thread on debian-devel is starting at
https://lists.debian.org/debian-devel/2023/08/msg00016.html)

There is a FAQ on debian-mentors: https://wiki.debian.org/DebianMentorsFaq and
when reading it you will also find the link to the mailing list ;-)

Regarding how to contribute to Debian and get your software into Debian,
there are quite a few resources you should read, see the section
"How do I make my first package?" on the FAQ linked above and additionally
read https://mentors.debian.net/intro-maintainers/ to get you started.

Additionally, as you are the author of the software, this is a dedicated
resource for this case, please read carefully: 
https://wiki.debian.org/UpstreamGuide

-- 
Cheers,
tobi


On Thu, Aug 03, 2023 at 02:57:06PM +0600, Олег Пучинин wrote:
> I think it is necessary first correctly, through github, and only then .deb
> 
> чт, 3 авг. 2023 г. в 14:26, Олег Пучинин :
> 
> > Hi !
> > Ok !
> > how to commit to Github ?
> > I can't upload files
> > github.com/OlegPuchinin123/go_brut_x
> > I use SVN.
> > How to commit new version ?
> > Can you check ?
> >
> > Oleg.
> >
> > чт, 3 авг. 2023 г. в 14:15, Mechtilde Stehmann :
> >
> >> Please answer to the list address.
> >>
> >> What did you try?
> >>
> >> What doesn't work?
> >>
> >> Where can we see shat you try?
> >>
> >> Regards
> >>
> >> Mechtilde
> >>
> >>
> >>
> >>
> >> Am 03.08.23 um 08:55 schrieb Олег Пучинин:
> >> > I  tried :(
> >> >
> >> > чт, 3 авг. 2023 г. в 12:18, Mechtilde Stehmann :
> >> >
> >> >> Hello
> >> >>
> >> >> Am 02.08.23 um 16:40 schrieb Олег Пучинин:
> >> >>> sf.net/projects/go-brut-x
> >> >>>
> >> >>
> >> >> you can try to package it yourself.
> >> >>
> >> >> For questions about packaging use
> >> >>
> >> >> debian-ment...@lists.debian.org
> >> >> --
> >> >> Mechtilde Stehmann
> >> >> ## Debian Developer
> >> >> ## PGP encryption welcome
> >> >> ## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F
> >> >>
> >> >
> >>
> >> --
> >> Mechtilde Stehmann
> >> ## Debian Developer
> >> ## PGP encryption welcome
> >> ## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F
> >>
> >


signature.asc
Description: PGP signature

Re: Adding epoch to kworkflow package to correct a wrong upstream version

[Tobias Frost]

On Sat, Mar 11, 2023 at 06:35:39PM -0700, Rodrigo Siqueira wrote:
> Hi,
> 
> While working on a new version of the kworkflow package
> (https://tracker.debian.org/pkg/kworkflow), we noticed that the current
> version is 20191112-1.2, and the latest upstream version is 0.6.2.
> Version 20191112-1.2 was created because the upstream had no official
> release at that time; for this reason, the 20191112-1.2 was created and
> named based on a date.
> 
> This package did not get any update in a long time, and now the upstream
> release frequent versions. The latest version is 0.6.2
> (https://github.com/kworkflow/kworkflow/tags), and I'm trying to release
> a new version of this package
> (https://salsa.debian.org/siqueira/kworkflow/-/tree/master/debian). So,
> to do a clean update, we should add  1:0.6.2-1 as an epoch to fix the
> problem generated by the first version of this package.
> 
> Is that ok?

I've got recently a very similiar situtation with
gnome-shell-extension-autohidetopbar, as there it was considered ok to use an
epoch. [1]


[1] https://lists.debian.org/debian-devel/2022/03/msg00424.html

-- 
tobi

 
> Thanks
> -- 
> Rodrigo Siqueira
> https://siqueira.tech




signature.asc
Description: PGP signature

Re: SONAME bumps (transitions) always via experimental

[Tobias Frost]

On Thu, Jan 05, 2023 at 02:29:42PM +0100, Sebastian Ramacher wrote:
> 
> From recent memory and assuming there are no issues with d/copyright,
> binary-NEW uploads to experimental have been processed swiftly.

This is also my experience that binary-NEW uploads for
library SONAME bumps are handled very fast, (also) in experimental.
(Some time ago sponsored such a package, at is was even accepted within an hour 
:))

-- 
tobi

Bug#1024542: general: Add Budgie-Desktop to the software selection menu list

[Tobias Frost]

On Mon, Nov 21, 2022 at 04:31:45PM +0900, Green wrote:
> Package: general
> Severity: normal
> 
> Dear Maintainers,
> 
> I have filed a bug report, but I got a reply that it was posted at the wrong 
> section.

The bug (#1024529) has been closed because it was assigned to the wrong 
package, as Cyril
mentioned: this is not a topic for the debian-installer but for the tasksel
package and as there is already a bug from you on tasksel (#1024531), Cyril 
closed
the misfiled one.

> Therefore, this is a reminder for the previous report.

As there is already a appropiate bug report, closing this one as duplicate.
People will follow up on the original bug, no need to file multiple ones.

-- 
Cheers,
tobi

Re: libc6-dev have unmet dependencies in stable-bullseye

[Tobias Frost]

On Mon, Oct 31, 2022 at 04:42:00PM +0100, Markus wrote:
> Hi,
> 
> Thank you for your answer.
> 
> > If you used debootstrap or mmdebstrap to create your own chroot or
> > container that only includes bullseye, and not bullseye-security or
> > bullseye-updates, then you would get libc6 (= 2.31-13+deb11u4) in
> > the chroot/container, and libc6-dev (= 2.31-13+deb11u4) would install
> > successfully.
> >
> > However, because you're using a container image that has been made
> > by someone else, what you do with that container afterwards needs to
> > be consistent with the assumptions they made when they created the
> > image.
> 
> The Docker example was meant so that the problem could be reproduced
> quickly. I can see the same problem with the official image
> debian-11.5.0-amd64-netinst.iso. Sorry for the confusion.
> 
> Step to reproduce:
> 
> 1. Install Debian with debian-11.5.0-amd64-netinst.iso
> 2. echo 'deb http://deb.debian.org/debian bullseye main' >
> /etc/apt/sources.list
> 3. apt-get clean
> 4. apt-get update
> 5. apt-get install libc6-dev
> 
> Then I get the same message:
> 
> > The following packages have unmet dependencies:
> > libc6-dev : Depends: libc6 (= 2.31-13+deb11u4) but 2.31-13+deb11u5
> > is to be installed
> > E: Unable to correct problems, you have held broken packages.
> 
> You write:
> 
> > That means you can't assume that an apt source for plain bullseye
> > is sufficient to get a full set of matching packages.

netinst will by default enable security updates and stable updates [1]
and has installed *during installation* packages from there (namely at least
libc6 (= 2.31-13+deb11u5).
Your "2." from above disabled those repositories, so apt can't use
those repositories anymore and will not able to resolve the dependencies.
This is the problem you are seeing.

> Perhaps this is also the case for debian-11.5.0-amd64-netinst.iso. I was
> not sure at that point. Maybe that was a wrong assumption I made.

[1] See installation manual 6.3.6.1.
> 
> Best,
> Markus

-- 
tobi  

Re: wxWidgets update & opencpn.

[Tobias Frost]

Hi Alec,
On Fri, Oct 28, 2022 at 10:15:49AM +0200, Alec Leamas wrote:
> Dear list,
> 
> I'm maintaining the opencpn and libwxsvg packages. They both depend on
> wxWidgets which now is updated to version 3.2 in testing. Hence, I have two
> bugs [1], [2] requesting an update of my packages.
> 
> The core issue here is opencpn, wxsvg is a dependency. The problem with
> opencpn is that it has a plugin universe, and updating the current 5.6.2
> version to wxWidgets 3.2 would break the plugin ABI.

Is this breakage due to wxWidgets or due to other upstream changes?
If the latter, *it might be* possible to backport the wxWidgets patches,
however whether that is feasible I don't know…
 
> The upstream plan to handle the ABI break is to do it when releasing next
> version 5.8.0 which is going into beta in November and will be released
> before Christmas. My thinking has been that if opencpn 5.8.0 is uploaded
> before Christmas the update process should be ok, since the wxWidgets 3.2
> version will be uploaded before the freeze.
> 
> Opencpn (current master, upcoming 5.8.0) builds fine using wxWidgets 3.2.
> 
> However, I get nag messages that opencpn will be removed from testing at
> November 8 unless I update it to using 3.2. Obviously, this makes me
> nervous. Questions:
> 
> 1) Is my overall plan ok?

I guess this *might* work; Soft-Freeze is gonan be 2023-02-12, if they
package is not in testing at that day, it won't be in bookworm.
So there is some risk if any delays are happening with upstream release
timeline…

> 2) If so, how handle the threat of being removed from testing?

Don't see that as a threat. Sure it is annoying but testing removal
is temporary and as you package will be still in backports, people
should be able to install from there, if they are on stable…
If they are on testing, well, that is the peril of testing.

Evenutally the release team will force the removal of wxwidgets,
regardless of the bug; for exact timing you might want to reach
out to the people driving the transition and ask them…

More generally, any response to a release critical bug will restart
the removal timer. So if you reply to the bugs below, and document
the plan, this will reset the timer, so you can delay the automatic
removal a bit. However, that will not stop the release team for
manually removal; contrary, they might be unhappy if people using
this as tactic to delay autoremovals, as this creates work for them.

Said that, a reply to the bug laying out the plan should be done anyways,
because this is useful information for many… (If there is an upstream
discussion, set the Forwarded: BTS metainfo to link to that discussion)

-- 
tobi

> Cheers!
> --alec
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019769
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019765
> 

Re: Firmware GR result - what happens next?

[Tobias Frost]

On Thu, Oct 13, 2022 at 05:08:57PM +0200, Julien Cristau wrote:
> On Thu, Oct 06, 2022 at 05:13:22PM +0200, Tobias Frost wrote:
> > Maybe and idea would to do something like isa-support does for e.g 
> > sseX-support
> > on CPUs that does not have that feature: It fails on installation with an 
> > debconf message, IIRC.
> > So that would allow something like "new package" | 
> > "you-need-to-enable-nonfree-firmware-reminder-package"
> > 
> Failing on installation is a terrible user experience, let's not, pretty
> please.

I'd prefer failing loudly to failing silently.
 
> Cheers,
> Julien

Re: Firmware GR result - what happens next?

[Tobias Frost]

On Thu, Oct 06, 2022 at 05:03:20PM +0200, Julien Cristau wrote:
> On Thu, Oct  6, 2022 at 15:45:25 +0100, Steve McIntyre wrote:
> 
> > On Wed, Oct 05, 2022 at 10:11:27PM +0200, Julien Cristau wrote:
> > >On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote:
> > >> On Sun, Oct 02, 2022 at 11:08:47AM -0400, Michael Stone wrote:
> > >> >On Sun, Oct 02, 2022 at 03:53:00PM +0100, Steve McIntyre wrote:
> > >> >> On Sun, Oct 02, 2022 at 04:43:47PM +0200, Michael Biebl wrote:
> > >> >> > What's the plan for upgraded systems with an existing 
> > >> >> > /etc/apt/sources.list.
> > >> >> > Will the new n-f-f section added on upgrades automatically(if 
> > >> >> > non-free was
> > >> >> > enabled before)?
> > >> >> 
> > >> >> So this is the one bit that I don't think we currently have a good
> > >> >> answer for. We've never had a specific script to run on upgrades (like
> > >> >> Ubuntu do), so this kind of potentially breaking change doesn't really
> > >> >> have an obvious place to be fixed.
> > >> >
> > >> >Is there a reason to not continue to make the packages available in 
> > >> >non-free?
> > >> >I don't see a reason to force any change on existing systems.
> > >> 
> > >> Two things:
> > >> 
> > >>  1. I'm worried what bugs we might expose by having packages be in two
> > >> components at once.
> > >>  2. I really don't like the idea of leaving two different
> > >> configurations in the wild; it'll confuse people and is more
> > >> likely to cause issues in the future IMHO.
> > >> 
> > >> Plus, as Shengjing Zhu points out: we already expect people to manage
> > >> the sources.list anyway on upgrades.
> > >> 
> > >I think in the absence of a release upgrade script (which I very much
> > >doubt will happen, and be tested, and we can rely will be used, for
> > >bookworm), Michael's suggestion seems like a reasonable way forward.  I
> > >imagine we'll need to patch dak to allow that, but it seems like it
> > >should be tractable?
> > 
> > I'm also worried what effect this will have on other tools that have
> > to grok the archive (mirror tools, debian-cd, etc.). I'm not going to
> > try and veto having things in more than one component, but (ugh!) I
> > really think it's ugly. Actually, I think I'd much prefer Santiago's
> > idea:
> > 
> > > Couldn't we handle this via transitional firware* non-free packages,
> > > that depend on bookworm non-free-firmware packages?
> > 
> > We'd need to add some transitional binary packages for the small
> > number of n-f-f source packages. That way people would get errors from
> > apt if they don't read our warnings and update. Maybe this is a way
> > forward?
> > 
> I don't think that will work well, the packages will likely just be held
> at the old version if the new ones are uninstallable because the new
> component isn't enabled.

Maybe and idea would to do something like isa-support does for e.g sseX-support
on CPUs that does not have that feature: It fails on installation with an 
debconf message, IIRC.
So that would allow something like "new package" | 
"you-need-to-enable-nonfree-firmware-reminder-package"

> Cheers,
> Julien
> 

Re: packages expected to fail on some archs

[Tobias Frost]

On Mon, Sep 12, 2022 at 05:11:46PM +0200, Samuel Thibault wrote:
> Hello,
> 
> Tobias Frost, le lun. 12 sept. 2022 16:08:08 +0200, a ecrit:
> > The problem is that if you want to exclude an arch explicitly, you have to
> > list all archs you want to build it on. IOW,  I'm missing an easy way to say
> > "not on THIS architecture", somthing like "[!armel]"
> 
> Yes, but see below.
> 
> > There are a few packages I take care of which make trouble on some archs or
> > simply do not make much sense to run on those low-end archs.
> 
> If they make trouble, I would say just let the package FTBFS there.

Well, it compiles there… Of course I could fail it artifically, but that
isn't something I would say it would be appropiate.

> > I was spending siginifant time in the past weeks on such a package, to fix
> > autopkgtests issues specific to that arch -- unsuccessfully, I disabled the
> > tests in the end --,
> 
> Is it possible to get the same test be performed during package build
> time? That way, it will be just not built, not shipped, and the state
> will be clear on the buildd status page, and you can move on to more
> useful work. For instance in my pocketsphinx package case:

Would do that if it would be possible; The tests won't run properly without the
data installed properly.

-- 
tobi

Re: packages expected to fail on some archs

[Tobias Frost]

On Sun, Sep 11, 2022 at 11:07:13PM +0300, Adrian Bunk wrote:
> On Sun, Sep 11, 2022 at 05:08:57PM +0200, Samuel Thibault wrote:
> >...
> > The issue we see is that some DDs end up setting a hardcoded list in
> > the "Architecture" field, rather than just letting builds keep failing
> > on these archs (and then possibly succeeding after some time whenever
> > somebody contributes a fix upstream that gets propagated to Debian).
> >...
> 
> I'd say it is the best solution when a package needs non-trivial
> architecture-specific porting for every architecture it supports.
> 
> With "non-trivial" I mean not just adding a new architecture to a few 
> #ifdefs, but serious upstream porting efforts. E.g. valgrind does not
> support riscv64, and if it would ever gain the support in a new upstream
> version I'd expect the maintainer to add that to the Architecture field
> when upstream announces support for a new architecture.
> 
> But Architecture lists for expressing e.g. "64bit" or "little endian"
> are a real pain for everyone working on bringup of a new port.
> 
> Which happens far more often than most people realize.
> 
> There is not only riscv64 (64bit, little endian).
> 
> Ports is about to start building for arc (32bit, little endian).
> 
> There are people working on ports like arm64be (64bit, big endian),
> loongarch64 (64bit, little endian) and many other ports that might
> never end up being built in the Debian infrastructure (but some of
> them might get built by derivatives).
> 
> Architecture lists containing all 64bit ports or all little endian
> ports create much extra work for anyone adding support for a new 64bit
> little endian architecture.

The problem is that if you want to exclude an arch explicitly, you have to
list all archs you want to build it on. IOW,  I'm missing an easy way to say
"not on THIS architecture", somthing like "[!armel]"

There are a few packages I take care of which make trouble on some archs or
simply do not make much sense to run on those low-end archs.  They compile
there beautifully, or at least the usually do, (which then creates a lot
of maintainer overhead then, because out-of-date…)

I was spending siginifant time in the past weeks on such a package, to fix
autopkgtests issues specific to that arch -- unsuccessfully, I disabled the
tests in the end --, where noone will ever use that package. I was very close
just to do what Sam asked us not to do. (And I agree with him that this is not
good.)

I don't actually believe people are using them on that arch, because if they
would, I would get bug reports about them… Upstream agrees with that: Although
off-topic, I would be eager to know if there is anybody using $PACKAGE on an
s390/System Z?"

> > Samuel
> 
> cu
> Adrian
> 

Re: Epoch for node-markdown-it

[Tobias Frost]

On Fri, Aug 19, 2022 at 10:00:58PM +0530, Nilesh Patra wrote:
> On Fri, Aug 19, 2022 at 09:51:14PM +0530, Nilesh Patra wrote:
> > > As Jonas said, an epoch cannot be undone, +really can, regardless when 
> > > this is going to happen.
> > 
> > I think ignoring when it happens is not the right way to see it. Even if we 
> > assume that
> > upstream is going to work on this with the same effort, we will still end 
> > up waiting
> > for a _decade_ for the +really to go away.
> > 
> > Is tagging this along for so many years really is more worthy than an epoch?
> > Note that the package might even go stale in such a long time, thought.
> 
> BTW, Jonas also said, "is it unlikely that they will reach 22
> in the foreseeable future?"

Did you consider asking them to advance to 22+ with their next release?
Afterall, I read it that way that it that there was some issue with that 22
version, and they might have also interest in putting that into the past?

-- 
tobi

Bug#1016962: ITP: swift-im -- C++ library for implementing XMPP applications

[Tobias Frost]

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

* Package name: swift-im
  Version : 5.0~alpha2
  Upstream Author : Kevin Smith
* URL : https://swift.im
* License : GPL3
  Programming Lang: C++
  Description : C++ library for implementing XMPP applications and XMPP 
client

(reintroducing the package; swift-im has been previoulsy removed from Debian,
#950770)

Swiften is a robust, high-quality, standards-compliant, cross-platform,
and performant C++ library for implementing XMPP applications. Swiften
is used as the back-end library for the Swift Instant Messaging client.

Swift is a free instant messaging client. It concentrates on making
the most-used features easily accessible, supporting
internationalisation, private and group chats, together with features
for security-conscious organisations including Security Labelling.

Swift uses the XMPP protocol and so supports both the public Jabber
network and closed XMPP services, such as those found in many
organisations.

I'm Packaging swiften as a depdency for Spectrum2
(https://github.com/SpectrumIM/spectrum2)


Co-Maintainers welcome.

--
tobi

Bug#1016726: ITP: libcommuni -- A cross-platform IRC framework written with Qt

[Tobias Frost]

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

* Package name: libcommuni
  Version : 3.7.0
  Upstream Author : The Communi Project
* URL : https://communi.github.io/
* License : BSD-3-clause
  Programming Lang: C++
  Description : cross-platform IRC framework written with Qt

Communi is a cross-platform IRC framework written with Qt. Communi provides a
set of tools for enabling IRC connectivity in Qt-based C++ and QML
applications.

IRC (Internet Relay Chat protocol) is a simple text-based communication
protocol. IRC was created back in 1988 and is still popular particularly
amongst open source projects. The Communi project's own IRC channel #communi is
located on Libera.Chat.  Getting started


(I'm packaging communi as step towards be able to package spectrum2)

Epoch bump for gnome-shell-extension-autohidetopbar

[Tobias Frost]

Dear -devel,

gnome-shell-extension-autohidetopbar is currently packaged with a date/name 
version, eg.
20209, unfortunatly without a leading 0~...

I recently agreed [1] with upstream to tag their releases to
match the version as on extensions.gnome.org as this has been source of
confusion for the users of the extension and package*. The versions on
extensions.gnome.org is currently 107.

Therefor I'd like to bump the epoch for the pacakge to 1:
with the next upload.

Therefore I'd like to soliciate feedback as per Policy 5.6.12.

Cheers,
-- 
tobi

[1] https://github.com/mlutfy/hidetopbar/issues/350



signature.asc
Description: PGP signature

Re: Lost package?

[Tobias Frost]

On Thu, Jan 06, 2022 at 03:43:22PM +0100, Alec Leamas wrote:
> Dear list,
> 
> I had a bullseye backport of opencpn uploaded to the backports-new queue
> before Christmas (thanks, Tobi). This is the first backport I've done.
> 
> This morning the queue seems to be processed, it is (was) empty. But I don't
> find any trace of my backported opencpn package anywhere. Accepted?
> Rejected? In limbo? I have no idea about what to expect or how to check
> status.
> 
> Any clue, out there?

I've got the ACCEPTED message, 
Message-Id: 
Date: Thu, 23 Dec 2021 17:39:12 +0100 
Subject: opencpn_5.6.0+dfsg1-1~bpo11+1_amd64.changes ACCEPTED into 
bullseye-backports, bullseye-backports

 
> Cheers!
> --alec
> 

Re: Remove packages from NEW queue?

[Tobias Frost]

Am 18. November 2021 10:30:37 MEZ schrieb Stephan Lachnit 
:
>I tried to remove a package from NEW with `dcut rm package.deb`, `dcut
>rm package.changes` and `dcut cancel package.changes`, but nothing
>worked.
>Is there even a way to remove a package from NEW?
>
>Regards,
>Stephan
>

ask FTP Masters for a reject.

(speculatinng on the why you want it rejected: if you want to replace it with 
e.g. a newer version, you can just upload the new version)

--
tobi

Re: Re: sbuild/schroot: need to get .deb files internally downloaded as package dependencies

[Tobias Frost]

On Thu, Oct 28, 2021 at 07:11:05PM +0300, Uladzimir Bely wrote:
> Thanks for the answer
> 
> > You have not explained why you don't want to use a caching proxy like apt-
> cacher-ng.
> 
> The question appeared while developing for Isar, a tool build create debian-
> based distro for embedded systems. In two words, it's similar to Buildroot, 
> Yocto and others, but it uses official Debian packages plus allows to build 
> own customer packages.
> 
> Currently it uses some own set of scripts to download dependencies, install 
> them is build chroot and build the package. Every .deb that was downloaded 
> during system build is cached internally. So, for the second build it's 
> possible to create a local repo from these stored files and do everything 
> (e.g 
> bootstrapping, building custom packages, rootfs generation) not from some 
> remote repo (e.g. http://ftp.debian.org), but from this local one (file://
> foo).

> I'm currently trying to switch our custom build system to sbuild one, but I 
> faced a problem that the dependencies downloaded by sbuild scripts are not 
> available in form of .deb files.

If it does not need to be sbuild, my pbuilder setup has an hook that
allows me to have a local directory as apt repo for pbuilder. Any deb placed
in this directory will be available during pbuilder build...
Kind of 
https://wiki.debian.org/PbuilderTricks#How_to_include_local_packages_in_the_build,
but my setup uses just one directory, not a per-project one..

-- 
tobi

Bug#996556: ITP: gnome-shell-extension-vertical-overview -- GNOME shell extension for vertical stacked workspaces

[Tobias Frost]

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

* Package name: gnome-shell-extension-vertical-overview
  Version : 8
  Upstream Author : Rens Althuis 
* URL : https://github.com/RensAlthuis/vertical-overview
* License : GPL-3
  Programming Lang: Javascript
  Description : GNOME shell extension for vertical stacked workspaces

GNOME has had vertically stacked workspaces for a long time. The GNOME 40
update made the switch to a horizontal layout.

This extension aims to replace the new GNOME overview with something that
resembles the old style.

(The package will be maintained in the debian group on salsa)

Re: Q: Use https for {deb,security}.debian.org by default

[Tobias Frost]

On Sat, Aug 21, 2021 at 10:40:32AM +0200, Wouter Verhelst wrote:
> On Fri, Aug 20, 2021 at 07:20:22PM +, Jeremy Stanley wrote:
> > Yes transparent proxies or overridden DNS lookups could be used to
> > direct deb.debian.org and security.debian.org to your alternative
> > location,
> 
> I've been thinking for a while that we should bake a feature in apt
> whereby a network administrator can indicate somehow that there is a
> local apt mirror and that apt should use that one in preference to
> deb.debian.org.
>
> This could be useful for both the "I've got a slow uplink and would like
> it to not be overwhelmed at the BSP I'm hosting for my Debian friends"
> type as well as the "I'm an ISP and I want to provide a mirror to Debian
> users so we can reduce our uplink connection a bit" type of situations.
> 
> However, I've not been able to come up with a scheme which is simple
> enough to be doable on a LAN while at the same time be usable by larger
> network providers, *and* which can't also be abused by MitM attackers.
> 
> Perhaps it's just not something we would be able to do?

https://tracker.debian.org/pkg/squid-deb-proxy sparks into my mind,
but I cant tell which of those use cases it could tackle, did not investiage 
enough for it.
(eg  for sure wont help at ISP level) 

-- 
tobi

Bug#982087: ITP: timg -- terminal image and video viewer

[Tobias Frost]

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

* Package name: timg
  Version : 0.9.9
  Upstream Author : Henner Zeller 
* URL : https://github.com/hzeller/timg
* License : GPL-2
  Programming Lang: C++
  Description : terminal image and video viewer

timg is a viewer that uses 24-Bit color capabilities and unicode character 
blocks to
display images in the terminal.

It displays regular images, plays animated gifs, scrolls static images and plays
videos.

Very useful if you want to have a quick visual check without starting a bulky
image viewer ... and don't care about resolution.

Re: Making Debian available

[Tobias Frost]

Am Sun, Jan 24, 2021 at 07:28:07PM +0100 schrieb Philipp Kern:
> On 24.01.21 17:08, John Scott wrote:
> > Changing the firmware on an EEPROM is far less practical for the user or 
> > manufacturer (they're on similar footing), and if it's not electronically 
> > erasable, it's merely an object that can't be practically changed of which 
> > you'd need to make a new one anyway.
> 
> LVFS is a thing now (kudos to Richard Hughes) and firmware updates can
> nowadays be pretty seamless, even on Linux. So I don't think I agree
> that EEPROM updates are far less practical. And I think I'd still prefer
> if the kernel pushes the (driver-)appropriate firmware to the device as
> it sees fit rather than having explicit EEPROM update cycles independent
> from driver updates.
> 
> > 1. Unlike with SSD firmware, there are wireless cards that use libre 
> > firmware 
> > and some are still manufactured and quite easy to attain. The goalpost for 
> > free software moves with what has been achieved.
> 
> I guess to make your point stronger you could also have linked to those
> products that work with libre firmware. A brief research then finds two
> abgn cards from Atheros that is not available through normal retail
> channels anymore, because they are 8 to 10 years old (at least) and do
> not support contemporary wifi standards. And the same research turns up
> that it took many years from the point were it existed (2013) until it
> got uploaded to Debian (2017) and released (2019). I think its existence
> is super interesting from a research point of view. But I don't think it
> makes a strong case for availability of libre firmware for wifi cards.
> Especially if you care about spectral efficiency, i.e. using a shared
> medium efficiently.

AFAIK those adapters are of the past. Nowerdays (FCC) regulations require
some tamper protection, so people can no longer operate their Wifi with
illegal parameters. [1]. All those parameters are usually controlled by the
firmware of the device.

[1] 
https://assets.documentcloud.org/documents/2339685/fcc-software-security-requirements.pdf

Regardless, our potential users will very likely not have those devices in
their laptop.

I guess the will just swear, saying Debian sucks, and move along to some other
distribution which potentially does not give user freedoms the same priority.

At least that was some feedback I've received IRL.

IMHO this is a lost opportunity, as we can't educate those about the importance
of FLOSS anymore*. Users also regularily start spreading the word, maybe even
starting contributing to the project and possibly becoming a part of the
movement and project.** Shouldn't be that our ulitmate goal?***

* (e.g I didn't know much about FLOSS when I started using Debian. With limited
  budget as student, "free as in beer" it was.

** That reads a lot like my personal story, because this is how it happened. If
 I couldn't get Debian installed at that time (pre Wifi-times), I probably would
 not be here typing this.

*** to be clear: this does not mean that people not wanting to touch
 non-free-stuff with a 3m pole should be forced to do so. Of course,
 this should be opt-in not opt-outM but we currentyl at "almost impossible
 [for novice users] to find the non-free images / or almost impossible to use
 the firmware loading feature of the free one.)

Just my 2 cents.

-- 
tobi

Re: How much data load is acceptable in debian/ dir and upstream

[Tobias Frost]

On Wed, Sep 16, 2020 at 04:55:41PM +0200, Andreas Tille wrote:
> 
>   Provided that license and copyright of the data in question is OK
>   is there any size limit for data to be stored under debian/?

my 2 cents: debian/ should not be used for much data: It will be duplicated by 
the upload
of every package revision. So (being extreme now), having several hundreds of 
MiB would
be quite expensive in terms of storage overheade.

I have not idea how much "much data" is, for sure to be defined by FTP masters.

For another 2 cents, if data would exceed the size of the debian.tar.gz by a
magnitude or two, I would go for a source package.

Summing up to 6 cents, my feeling is that storing data in debian/ is not the 
best
approach. Have you talked to upstream to include the data in their source. 
After all,
this would benefit the whole community if upstream has a good test suite?

Cheers,
-- 
tobi


signature.asc
Description: PGP signature

Re: How much data load is acceptable in debian/ dir and upstream (Was: edtsurf_0.2009-7_amd64.changes REJECTED)

[Tobias Frost]

On Mon, Sep 14, 2020 at 03:32:54PM -0500, Richard Laager wrote:

> >> Don't forget to mention the copyright information.
> > 
> > In principle yes, but these data are not copyrightable as far as I know.
> > Nilesh has mentioned the origin of data in debian/tests/README to
> > provide a reference.  If you consider this information not sufficient
> > please let us know a better way.

Note, IANAL;
I don't know if DATA itself is copyrightable, however, the act of collecting
data can to my understanding constitute copyright.

--
tobi

Re: Building Debian source packages reproducibly (was: Re: [RFC] Proposal for new source format)

[Tobias Frost]

Hi Ian,

On Mon, Oct 28, 2019 at 05:53:00PM +, Ian Jackson wrote:

(...)
 
> For example, you would not be able to do this:
>git clone salsa:something
>cd something
>make some straightforward change
>git tag# } [1]
>git push   # }
> Instead you would have to download the .origs and so on, and wait
> while your machine crunched about unpacking and repacking tarballs,
> applying patches, etc.


I'm missing a "and then I test my package to ensure it still works before
upload" step…

I wonder how someone should test their packages when they do
not build it locally.
And if they do (as they should), the advantages you line
out are simply not there.


-- 
 tobi
 


signature.asc
Description: PGP signature

Accepted gnome-shell-extension-autohidetopbar 20190913-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Oct 2019 18:05:57 +0100
Source: gnome-shell-extension-autohidetopbar
Architecture: source
Version: 20190913-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Changes:
 gnome-shell-extension-autohidetopbar (20190913-1) unstable; urgency=medium
 .
   * New upstream git snapshot.
   * Drop d/compat in favour of BD'ing on debhelper-compat.
   * Bump S-V, no changes required
Checksums-Sha1:
 b2b7c24ae6bbfe85d43f4f6154d7b3b0371f97a8 2177 
gnome-shell-extension-autohidetopbar_20190913-1.dsc
 c9fd48cd6564f3f7fd5149c5fd6c703043e11ea8 15788 
gnome-shell-extension-autohidetopbar_20190913.orig.tar.xz
 999db3c0506a9023dc0e9955ebdf9f7b76e48cca 4088 
gnome-shell-extension-autohidetopbar_20190913-1.debian.tar.xz
 55791961fe1d8877d7392a5890ec61316b402169 5698 
gnome-shell-extension-autohidetopbar_20190913-1_amd64.buildinfo
Checksums-Sha256:
 75f290b93d998bbced98792474202303b957cd7f2c7ae92be764dcb39748ce6a 2177 
gnome-shell-extension-autohidetopbar_20190913-1.dsc
 822d5dad995e24177bb1a93af491e002974b33959510382c1e90d9953cc25d71 15788 
gnome-shell-extension-autohidetopbar_20190913.orig.tar.xz
 cbd8a15e82e9f473cb7c722f8a805fa66d54683ee8728dde4566b9f1c401d8ed 4088 
gnome-shell-extension-autohidetopbar_20190913-1.debian.tar.xz
 ef4c04c927b2f1a1d9b42c5a321baff17e695a08ec16fa08d47989e2a1b0e8de 5698 
gnome-shell-extension-autohidetopbar_20190913-1_amd64.buildinfo
Files:
 9c971c424dbf640501a0ddea97233646 2177 gnome optional 
gnome-shell-extension-autohidetopbar_20190913-1.dsc
 87fae1304af2e3622e70fa7ce06a02bb 15788 gnome optional 
gnome-shell-extension-autohidetopbar_20190913.orig.tar.xz
 c6633112c967a55f7ffa64b2d290ad77 4088 gnome optional 
gnome-shell-extension-autohidetopbar_20190913-1.debian.tar.xz
 748a05d25dff7c743d3d3b58b3150511 5698 gnome optional 
gnome-shell-extension-autohidetopbar_20190913-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl21z/MACgkQkWT6HRe9
XTbB5A/9GtnyBP7Vh3MmcI2qcX7dJrYCanfdQotD4CdSyIdPC9/KBlQ3uXVsTAks
ecLezaIOM6dYfFBhTw6lFlp85Zdr4mn5GeUw9Xk3ChQirtzTWDoFkFhj+q7yzFSd
ihmJs0RsYxejmGSZyd9j2Wrmecu+6Le5AZaEGjFUA4ys1lIh0O/gb0RbQBzEWw5R
zal2d7DZAvrHmr8wQvDxG8Cd8ouQVmBWTcw1bYI4np33bT7/6DWYDM784CA++Aa3
iXK22lmRG3dIJvJjfwoE9GtQ7THy8CA1ufZZD0PHgHXsYWVwud6B5A59OMcv0XQ2
JAzb6rpWBArcHgzwvsFl1FLlgh1zE/OXX+P+WMHonmuZIpYCcrAOrt6jradhQtYe
oW7F7BIUF/p0mw7+frn67DO00+InyzxzfzxziuDyhh/EuB8a57UQ6Z0ReieBoeOw
I5o1shB/0/nUKE8xHs10K98j2naoaDYchwq/As43vh5UpPiJUd8vP4i05rwOU6rN
XaGtzIEwmodmXgsKIAE6no6bWGi1IIF9/1m7Ujx1MKu8HEfjnRIS2C3IV1BEubXk
WdapZWYPkQuMUWYIzZ9eMeL2qhRL1kKegIqSt1KyIWTFyL/X1H8qDR6cBRxU4tH9
TljRN5bNUQZ6BPPPpy4kcVwIewJi0ZKPMeHkM6WADhtfShGCEII=
=hCBh
-END PGP SIGNATURE-

Accepted gmrender-resurrect 0.0.8-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 23 Oct 2019 17:19:14 +0200
Source: gmrender-resurrect
Architecture: source
Version: 0.0.8-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Changes:
 gmrender-resurrect (0.0.8-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update watch file to catch released versions only.
   * Drop fix-libupnp18.patch -- Upstream has now support for libupnp18
   * Drop d/compat in favour for B-Ding on debhelper-compat.
   * Fix some lintian stuff that pops up with newer compat level.
   * Bump S-V, no changes required
   * Update d/copyright
Checksums-Sha1:
 03263b472b0b9e5c87e24b14d7d4ace11b3c5982 1991 gmrender-resurrect_0.0.8-1.dsc
 8bbabfecc237a7b5b99e7b939fa74c72ab24aa16 107083 
gmrender-resurrect_0.0.8.orig.tar.gz
 da83cefaac3e54b44a926e59ac20c1001cd25599 6180 
gmrender-resurrect_0.0.8-1.debian.tar.xz
 57d2df28f6d1bdeeb0f82864fccb555a2b6bbdd3 6587 
gmrender-resurrect_0.0.8-1_source.buildinfo
Checksums-Sha256:
 141b78b2790520de3508cc5cc52dcd28cd6b4cc21286fbdf533cfcc02662bc9e 1991 
gmrender-resurrect_0.0.8-1.dsc
 1f0cef76e4543879c9cd31cad73d6c4f778b965884c586405efcf63f2bdbb06f 107083 
gmrender-resurrect_0.0.8.orig.tar.gz
 3b72621282b12d14fe6f15c3628c2228957805d81986ea5c3fc596f5eefbdcfb 6180 
gmrender-resurrect_0.0.8-1.debian.tar.xz
 c0af59a27c633603637089e22a76922e5723d318288aff2b3ded9eac9d0f860d 6587 
gmrender-resurrect_0.0.8-1_source.buildinfo
Files:
 8bfe4120d899d913d242502edaf4044e 1991 sound optional 
gmrender-resurrect_0.0.8-1.dsc
 8b65d36b51e15f82080ce30f42ec10fa 107083 sound optional 
gmrender-resurrect_0.0.8.orig.tar.gz
 b8b5390c3a73b86df38354b3b7b8dcd2 6180 sound optional 
gmrender-resurrect_0.0.8-1.debian.tar.xz
 642c4e086148086370ac0f3fc9ff3a4d 6587 sound optional 
gmrender-resurrect_0.0.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl2wb4wACgkQkWT6HRe9
XTYNng//XD3BYZstg+Nw3r+Cum36+FCa305mAnfDN8oNa77YZ9BIzQ3DAMN7vDq4
OQwWl7gCmK0YrYsmwkZivTjWfr8m2eGNIjeSgdZNnP28U8dJd4udOkmo14eWcqU5
fnGKmBY4cZ2W4q8iSLT2S7fMghbA4hJcbgh09piQ5xdj9X80yrxsMrBdmpad5vok
GBhPA47prczzcQdYXbQavDkeb11tv82HlTcFn5GJGBVnNqWefwRBGdwRLgGVCh3G
TUhtry4/BU13KYsRmo2m1M9TXsDq9lbfn6F/pqyQMq5Bwnq8ndo8iDEbt6tkmCUv
1yeM472PG9+woN9zKqyQsrRq5zdosFcaZrQ9uVqmj+e/27lIxOj43HpMf5m9Gepd
wDzDKOnwmkB2FQrpyf2AyETyCPQUMhQZkCgd0mllPWSmcidiljIFEkg5Kg6IhPVV
ahK3fku7TSLTy9ygz5gjQsvjRFVZm6IcZ8/kQLYkZq07lfx19687yY3+KpvavTHU
eAUCJo2jSkwcM9zYgpDRD0WiALZwlB4XDDWGOBT1x2XAZOWN5QVaO9HbrIV7+4mT
rXag3xfbK5NJYPDIG8W1CYZgzbh+KCEXv93BuVHF7ekl5QuivgwH15eERQQnlYlN
V7JRSAxSuNHvIFIAZH6AlrT+5BzbmqKnADrqAoRJ84eHEg/G7mY=
=EXlI
-END PGP SIGNATURE-

Accepted rbdoom3bfg 1.2.0+dfsg~git20191014-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Oct 2019 20:30:51 +0200
Source: rbdoom3bfg
Architecture: source
Version: 1.2.0+dfsg~git20191014-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Changes:
 rbdoom3bfg (1.2.0+dfsg~git20191014-1) unstable; urgency=medium
 .
   * New upstream release, upstream versioned it as 1.2.0-preview1.
   * Refresh patches as needed to remove fuzz.
   * New patch 90-fix-include-path to fix FTBFS with new upstream source.
   * Fix new typo found by lintian in the spelling error patch.
   * Delete 30-init-sdl2.patch, unapplied since a few versions.
   * Drop 70-disable-hdr-by-default.patch, underlaying issue has been
 fixed upstream.
   * Bump S-V to 4.4.1 -- no changes required except specifying
 rules-requires-root=no.
   * Drop d/compat in favour of debhelper-compat (=12) as B-D.
Checksums-Sha1:
 25880feb10cc454630cd7a1657e54e48502572f2  
rbdoom3bfg_1.2.0+dfsg~git20191014-1.dsc
 54bbd7828971278a8d303ed0b6287dfadb57d20f 2513764 
rbdoom3bfg_1.2.0+dfsg~git20191014.orig.tar.xz
 ce2b5e26cf6035f8478f67e352ee146c1eea8879 17624 
rbdoom3bfg_1.2.0+dfsg~git20191014-1.debian.tar.xz
 34e35bc39f31de58062a176b834dcbab8c4bfac0 14401 
rbdoom3bfg_1.2.0+dfsg~git20191014-1_source.buildinfo
Checksums-Sha256:
 b0a3b47900cc6e9519a445bfea688b57df9597c0f98aed623f0bf73088a13657  
rbdoom3bfg_1.2.0+dfsg~git20191014-1.dsc
 78f13886c57acca99ca87d1809f00e459e2489efab75a9afb7addfb32577528b 2513764 
rbdoom3bfg_1.2.0+dfsg~git20191014.orig.tar.xz
 c00183a9bb88719aa6e514d875b549ba2e59218ba7938ce98a8ac057a46872b0 17624 
rbdoom3bfg_1.2.0+dfsg~git20191014-1.debian.tar.xz
 515850c557d3d500dc5643f315d57931ce1cea6e7b714f01c6458eb7605aec07 14401 
rbdoom3bfg_1.2.0+dfsg~git20191014-1_source.buildinfo
Files:
 9e243ab7dcdc634d8c9b64ec7f335094  games optional 
rbdoom3bfg_1.2.0+dfsg~git20191014-1.dsc
 de5a96132aa8aff5afa3fbcf7f45e432 2513764 games optional 
rbdoom3bfg_1.2.0+dfsg~git20191014.orig.tar.xz
 21031dd1805071e1f1d0c04ae45aac3d 17624 games optional 
rbdoom3bfg_1.2.0+dfsg~git20191014-1.debian.tar.xz
 f77d8148f4cc0b9c47b31688290472a5 14401 games optional 
rbdoom3bfg_1.2.0+dfsg~git20191014-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl2mEJ8ACgkQkWT6HRe9
XTa7dA//UwtwTpo8WklWkjab8IiBIEw2wHOWERHfy6bR3so0oHCiYmA2kgGsOpNc
hNBaGGUzEpGCUt/+NGi6FxiSTgM/qqyKztbe7ViZ9SynbW5b2XosLrFSafLUOEjN
vZ3KyrZrky2orLoq/SlCfSEyf7/RHKXmDg+cmK62p7xpMZSyD34i5CZMsBt6WxEp
F4IfbgGNCVzUu5t5/nFf61Hp/gFYvAy/g7U3p+0E18wrLW46P0ApYuHH01wl9p2i
xeRqyDIfjm4CY9goB6YRMhk3Wgr/hIUCh1ySx5YmwehE9dQbPlWNVQ2yUfDtiAgP
5w0KxPImZ2ONF7bSJ8149zhfhN/i/HavsB7rgY5qLyygjdP1B857djePEWJAUA3l
wjG6kEZag4gcKSz3tLmcqTHNxTbMLidgtfBOPzsxofG4LIkKep8DvSiEeTzjf6b9
xG3ozJFet35bPewmck8Rw2HAHr7p2GK39NN5Xgv/jTOBfVlB0DMbnEPtl6MYJC3j
SY5++TaLQrsFMFiEk+w/mv3lp+4XM420xFQPRJU0NvluGZ+KB1RMh28DMaz810+3
fxLZNtsdaveyeJ9kT8p21HbhRfKTS6jOPRwn5eUTKFeL5vsRBH3G4cikY828WgJw
Q+lbJMOuLzBlSEEWcj9V/ZTHQr5Kl2f+K+Z4ExuqkF3aMCPHuD0=
=xXjO
-END PGP SIGNATURE-

Accepted png++ 0.2.10-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Oct 2019 20:55:05 +0200
Source: png++
Architecture: source
Version: 0.2.10-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Tobias Frost 
Changes:
 png++ (0.2.10-1) unstable; urgency=medium
 .
   * New upstream release.
   * d/watch: Enable upstream tarball signature check.
   * d/control overhaul:
 - Specify Rules-Requires-Root
 - Drop d/compat in favour of B-D'ing on debhelper-compat. And go to level
   12.
 - Bump S-V to 4.4.1 -- no changes needed.
   * drop linitian override for doxygen's jquery.js, as no longer needed.
Checksums-Sha1:
 586b8b70b5a5e00eb4b0bd6f4b7dd87eb93e0915 2147 png++_0.2.10-1.dsc
 96081689a56037df183100d19fcb1f52dc4ca6ce 592203 png++_0.2.10.orig.tar.gz
 504d0ec5885256c2f93107cd93bff797adea 691 png++_0.2.10.orig.tar.gz.asc
 dc57d7ca2d497db0b193841ecd8542b5dc781a9c 7528 png++_0.2.10-1.debian.tar.xz
 8327827e25b80d8d991beb2e995e9624db49385e 7262 png++_0.2.10-1_source.buildinfo
Checksums-Sha256:
 913f4f150d56ce5a4b940645b7a6cbdf3151179917ec1d4a520b7f876bf19a6d 2147 
png++_0.2.10-1.dsc
 998af216ab16ebb88543fbaa2dbb9175855e944775b66f2996fc945c8444eee1 592203 
png++_0.2.10.orig.tar.gz
 dca51a096b02a8a4127cf94e7a334624062de65f5ce1e53072e40d0dd14ad3ff 691 
png++_0.2.10.orig.tar.gz.asc
 5b4f2183590202b741fb1fff2a354ee0cbff69900952940415bc9fa1a56b5cf0 7528 
png++_0.2.10-1.debian.tar.xz
 5d764fe9dbceb1d69ab148bd96a2b9421a61e3ef0ac5d572cd18b71172783172 7262 
png++_0.2.10-1_source.buildinfo
Files:
 5a17d00467649ad876edb564efdede3a 2147 libs optional png++_0.2.10-1.dsc
 bcca7438bb1b55edd0156687f0259c82 592203 libs optional png++_0.2.10.orig.tar.gz
 e9875d6a5ad0e3e662a812d3a0b0bbf1 691 libs optional png++_0.2.10.orig.tar.gz.asc
 ab388ffdd2bf82597e8d62a2bcdd5755 7528 libs optional 
png++_0.2.10-1.debian.tar.xz
 05c11359b7d1cf582418922d8ebf359e 7262 libs optional 
png++_0.2.10-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl2blWUACgkQkWT6HRe9
XTYrzQ//dR1Yc45i/2qODhd4IgLJyUF3pV22IH4KCw1ZD6AKt+Hng82CwJw7jo3W
v0XZ5UUaxNqassIhof3VXZIvgWfqO1GgNbcLbMqB4htZoZoVkgk6yzKUOHn3WL/k
P8mPBF/UN7Ay09PJiG11zXg7puDNeeRnFEnA+/B67/Y8jL23hOPjk2trDhAaFvlU
Vj1YfACQts2mxxPNTOvMxsJDBGrKCaNvvHA3+4Qfj/7Fakw6fsB/OxkBsVDmXFQV
nWp1Ej8mE4RYTsWszFEuYw8YICuBxwv22XW0biGkWEzYhX1aGwIyrq3YDLBMQhl7
sG5/1XTJZ2z5Xv/zVUei3laStggq/uDsh0MjXOz6Trvl+gDdO72/bDh9kV8FRNt3
abhB2e5bFjTocqevQav+CLXLz1nPZ/t93Fz4PetElUE2m+M7g1YulPLDtdRUoGRj
9p820ZrfJ5CsAJZvzFpo0/b0GmU0TZdRGAp1I1UfPj3tB5Pde/p5RyEbgKWNhgnz
90C1MhkNgXQJiF6t8LRav9mkFsVFFYair7YkTcT0ICnxwE6KqCQ53wexxqyIMBcD
Y96HGdADsRB1haiCYM5ftSlfjbSVWRQMJT9sI0zUoMAU4S756XB7SH6qiyR/htCV
VE6NXCEedcAzaMKQBBa6FXbJBk8J7mvqsC+wmXRgdrkydi7dMls=
=RlXv
-END PGP SIGNATURE-

Accepted gnome-shell-extension-suspend-button 0~git20191005-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Oct 2019 22:31:57 +0200
Source: gnome-shell-extension-suspend-button
Architecture: source
Version: 0~git20191005-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Closes: 941892
Changes:
 gnome-shell-extension-suspend-button (0~git20191005-1) unstable; urgency=medium
 .
   * New upstream git snapshot. (Closes: #941892).
Checksums-Sha1:
 d6b65586c9a7a67ea238fdb644a15359b8e49583 2227 
gnome-shell-extension-suspend-button_0~git20191005-1.dsc
 643c504072352402af92632c66504fa780d4cc11 12736 
gnome-shell-extension-suspend-button_0~git20191005.orig.tar.xz
 29e8f597ed1b3eec67cda8ea712f8f086aa63e43 3772 
gnome-shell-extension-suspend-button_0~git20191005-1.debian.tar.xz
 91e62227eb15cc7c13fd62b20df2f6d953a5c364 6218 
gnome-shell-extension-suspend-button_0~git20191005-1_source.buildinfo
Checksums-Sha256:
 40bfba6ba7c8c64d7df77428dfc8303ce0a8f5f35cce40b1aa32a910be5bf2ff 2227 
gnome-shell-extension-suspend-button_0~git20191005-1.dsc
 bb22b257277b26f60baf9a5604ffea88fa345376ad5ee042c64aa606afb004fd 12736 
gnome-shell-extension-suspend-button_0~git20191005.orig.tar.xz
 2ab76b5934d7cec3a9426f03cab8abf726300db44c3d1aeed88c4d8aeba26d1e 3772 
gnome-shell-extension-suspend-button_0~git20191005-1.debian.tar.xz
 ba624e088d786226e6f67e41bac2f85d29266e93b6e758f60197c3b9e4c8d367 6218 
gnome-shell-extension-suspend-button_0~git20191005-1_source.buildinfo
Files:
 30a6c6fdc9d684bf2294ab0fcebaaea1 2227 gnome optional 
gnome-shell-extension-suspend-button_0~git20191005-1.dsc
 6a9d3716093d2091175acd26047b27c3 12736 gnome optional 
gnome-shell-extension-suspend-button_0~git20191005.orig.tar.xz
 7ea400e1c180a563bd71456df812b80a 3772 gnome optional 
gnome-shell-extension-suspend-button_0~git20191005-1.debian.tar.xz
 4ca21e01617bd29a614921417dcd5491 6218 gnome optional 
gnome-shell-extension-suspend-button_0~git20191005-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl2boPMACgkQkWT6HRe9
XTa+6g//X4kNTR9le0T5MMrcZ4Y4c5Cp4NqSWOV/jx0kOONo8jWUXPBhdmplz2dI
wGpKRTnmd5ndHvD0jMTmqzb7/+ectMtJuuVxJYMxOmki+FMaMAhg2/Fxc+ZTJHFQ
KqZhoytRuqI7hq81a1bX8xkeM2dewH24vQO8a8bWyRZnqPtmRw4yAQon0dn1ySxM
3FHLu6oUCyyH5v78Y3Mz1d+2chDiUzw01jZ1yf9n1Ewj6vM0tH6X2Rnb+An29QQF
iax/2dgB8AA5EN2jrqTD0E2ncpsD36IPg6gxSHSLi+FwjIu0mrN4r9/NHkoCw7Be
90M+A5ybT0owyWKFGz4VgFvdqW0FDz0APY4F8/NH6fxqhd/DekOfIhUFKrxCK746
UP7mbdgsbYcl2LQGZPHpGQHxs6cYOcmSAGYM7yLxUFDCoP98fTz7Aols2fP2L5Wi
53oUKsSJOxeqxyoJQc8OekvQbbGl8lMirz5xRcc6Qr6ESZ6cqnEn8TpqyvQmPndI
rXitGMEwJEmMafXpvX7B3Yd41SgHlqgdhTFGa2fzL3kbGG1KD03RnmVYUOk3QsK4
3NsyzEQZENnX1c8jDqNqKxg54FwVWgCRw5kuWTUR5v6mGNr5PsiANwORHf7WfUPl
C9ZfpCTLE91erDg+LdAuuANmQR73PI+hGC3jlOLKo1Ks+m0snxc=
=z9AJ
-END PGP SIGNATURE-

Accepted darkradiant 2.6.0-4 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Oct 2019 11:41:11 +0200
Source: darkradiant
Architecture: source
Version: 2.6.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Tobias Frost 
Closes: 933419
Changes:
 darkradiant (2.6.0-4) unstable; urgency=medium
 .
   * d/control:
 - Build against libwxgtk3.0-gtk3-dev instead of libwxgtk3.0-dev
   (Closes: #933419). See #900678 for details why it needs at least
   the specified version.
 - Drop d/compat and replace it by depending on debhelper-compat. Go to
   level 12.
 - Drop all versions from B-Ds that are already fulfilled in oldstable.
 - Bump S-V to 4.4.1 -- no changes required.
   * d/rules:
 - Drop gcc warning on date/time usage, no longer needed.
 - Drop unused include for pkg-info.mk.
Checksums-Sha1:
 5a195fc82decb657a17e302dc99088b2cd9ee523 2374 darkradiant_2.6.0-4.dsc
 bb9e17fabb7abbf7e5522868c2a9257b14c33e39 7952 darkradiant_2.6.0-4.debian.tar.xz
 5920de6a6fee05172301583b10673038af98a0c7 13316 
darkradiant_2.6.0-4_source.buildinfo
Checksums-Sha256:
 00c43dc6dcb6dab9fcf455c52d9643963254bf99bf6312682c53c10a46e27f91 2374 
darkradiant_2.6.0-4.dsc
 2d2370e7512812394fad3cdb368861374fa197d5081534478e0d5bb99202ddc8 7952 
darkradiant_2.6.0-4.debian.tar.xz
 d7893deb00caedcb4b56af21a31e80673b2cc4b479a09f2c9f9779e6fd3e6382 13316 
darkradiant_2.6.0-4_source.buildinfo
Files:
 fe409e0a4bec3c4c7a30ebc1e236fe52 2374 graphics optional darkradiant_2.6.0-4.dsc
 77646131f9526df08b0ab63857afbada 7952 graphics optional 
darkradiant_2.6.0-4.debian.tar.xz
 c4292cc55e6db81b7518b42c5e3531ba 13316 graphics optional 
darkradiant_2.6.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl2YZiEACgkQkWT6HRe9
XTZCTw//TvIn1xLbUq0OJYun1AZ/qgLZ/ylNQQ0v+sIARkLTF8ZbXkOC70DMgL8r
eaE8sRixnbVLsrMaYH5T0pe3dX4n4VBOx3ZQyKbcBz/uSTDprFsRr29g7T6KxpmD
dL4eFFf/5pT+t9wwpPErJgnHDO+V725aNXugCc/Uq5zf5TB5RGlECcmGxT/HfGuH
4GCJ4x7p74Pkud5xlM8NBxAywVGmXzM/pzJhaU3Hkub03C3CappQ16t8PZb+SwJf
zX7uyKDr2kJwOtrQcSz5C2cdPP5YGmEwE2UVJyLOsSv0i2BlZbxCm0q4rFadWPuW
snNcHwOtVFn5gHb4Qp9pk79Kiwl4GCLlbrhGQy6A9zB2wskKGHgW4CVqIiakyS+s
rqd+X/xUn7n5GUcFKyZXUHmUjF233VFMyCJ+ksWqtTerVZWsxAJiLktEf8NBmFpI
by6dOSUWRvTlJ6ZxVfMgOD0kV2IRwWJ1mQxUGpaGzmpebwELDOS7wu14VKMqN2ij
sf8t+1jAf5XUgKW3bKzFAoSSCRa8j7wzniJBA7Ih585zAcLx2DkiBYditTMolHS9
Mhag7moNrQ2OKbFd3D9PfjTdBrN6nR045dzw5INu4PDz5KH0jvEOT6QtjAy8mGF9
BqJrDGs3ehmTaLRTEhvgL2NVEDDiaWcteA3Xfg5Bc+1YJ16A968=
=FUAK
-END PGP SIGNATURE-

Accepted widelands 1:20-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 04 Oct 2019 19:18:04 +0200
Source: widelands
Architecture: source
Version: 1:20-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Tobias Frost 
Closes: 853052 928325 938824
Changes:
 widelands (1:20-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release. (Closes: #928325, #853052)
 - system-wide_minizip.patch:
   - refresh patch
   - remove embedded source via d/clean to ensure no code leakage.
   - ensure that right file is included.
 - refresh hurd_MAX_PATH patch.
 - refresh dbg_symbols patch
   - build with O1, as with higher optimization the game will segfault.
 - drop gcc7.patch, no longer needed.
 - drop widelands_ICU_63.1.patch, applied upstream.
 - new patch to link against GL, fix-SDL-linking.patch.
 - new patch to fix different spelling of a packagedfont name,
   system-font.patch
   * d/control:
 - add new B-Ds and drop no longer needed ones.
 - B-D against python3, instead of python2. (Closes: #938824)
 - Drop doxygen from B-D -- we are not using it for the packaging.
 - Make VCS-* point to salsa.d.o.
 - Bump S-V to 4.4.1 -- no changes needed.
 - Use debhelper-compat in B-D to drop d/compat and bump it to level 12.
 - Specify Build-Requires-Root as no.
   * d/rules:
 - Do not build the website tools in the first place, as later they'd just
   be rm'ed again.
 - Drop get-orig-source (as dropped in policy)
 - use dh_missing instead of dh_install --fail-missing.
 - use d/clean to clean fonts instead of rm them after installation.
   * Update d/copyright (years) and take add fonts copyright information (by
 cherry picking upstream's d/copyright)
   * Cherry-pick desktop file from upstreams debian directory
   * Cherry-pick widelands.appdata.xml from upstreams's debian directory
   * Fix d/watch -- new upstream scheme omits -src.
Checksums-Sha1:
 9e4c0839f0d6c0dfcf36bac8b23759883510b85c 2221 widelands_20-1.dsc
 a2fdedf81c08fd08809b8556c955a6a7f32c1eed 232364340 widelands_20.orig.tar.bz2
 8a114689bfaa1edca7214f9687020da3201dd0ad 34900 widelands_20-1.debian.tar.xz
 ebe279791802a31646882f48d6d9b110a69d80de 13251 widelands_20-1_source.buildinfo
Checksums-Sha256:
 d0c7d895a7e3c0c589f68214aa7e6b05264cc697f75a4e618e572ebb245e1386 2221 
widelands_20-1.dsc
 38594d98c74f357d4c31dd8ee2b056bfe921f42935935af915d11b792677bcb2 232364340 
widelands_20.orig.tar.bz2
 4f68c0569f7905a5ac44f799d2755a24d1917a5fe30fa14195af0f2a5cc15ecb 34900 
widelands_20-1.debian.tar.xz
 612b35a917108d5b1893217c0bce24b4943d6ff588f94edddf6192258eb13cb9 13251 
widelands_20-1_source.buildinfo
Files:
 2ec97b91d4badcbdc0d51aa8ed6e7f49 2221 games optional widelands_20-1.dsc
 add6644d288564a589384e2a484555e1 232364340 games optional 
widelands_20.orig.tar.bz2
 256f3eb9d57c4e3c492f978e49ef6282 34900 games optional 
widelands_20-1.debian.tar.xz
 79dc9bacc78a39945de6ef64ab1b5ee5 13251 games optional 
widelands_20-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl2Xf0MACgkQkWT6HRe9
XTaTMA//Wd+nnW7+p3ID+wae6hDwc1+22Cj2Q/kqZvyhWs66goaaoWb2AAp0Ajgg
z7c0hT1YK7RZtzO6UcTg7WcQ95rHDryy3OeM8qzEztEn6aotaMiLI1N6xzPpr8Gh
LHVK9RHS73dE0f2JrLEQwtF+xF1LZFZpbC53CYngh0H8VGt1s+cSTgZI2V1g5hiC
hFpoz2II1qa2kAQG6WFbzuBj4cORE7gNg+b/PONmC8ngGUd9BfdW47QQ+r0IeFVw
cNNd+9sVG1YKiZnBkcr5EzL9f/0rIxAcSyl3yZo3akpM8X8H5wQVzfDawfooNghX
YkNMCsCVWDK6JYniIE/06lBpw5e/AqSs5+C7EhCsWRL5rUxamXZ51j+Fly0XoLnz
PH1W79C7wnBPLX9yYWONqRMKK3n7lbAE08Q9lSwvlrVjadk4M00+teZmongLR32q
QMG2Qmnw/Z1yPxIPW77tDEUVX1UhSXCNaxTjG4yn5jgxDqO29gqw8B6pqsZ73My4
/4lKV62M4tyCp7NiDhLaLuJILqWeuVRSByoAx3bMd235y+yDG+mFRFndMcDGqe38
K8ldPh7jX92tNh03Kt9/Zu8A4KBjKM96wq6vxt+CqPi7Pw/WclOIXy6xc8xA+426
Cyinz7eP1lg5HauqD+TD2yQd4vFD6iWWL4/4FHlDs5NE1cTf3as=
=lwWT
-END PGP SIGNATURE-

Re: tag2upload service architecture and risk assessment - draft v2

[Tobias Frost]

On Tue, Aug 27, 2019 at 05:04:06PM -0700, Russ Allbery wrote:
> Scott Kitterman  writes:
> 
> > As an example, I recall concerns about there not being an uploader
> > signature on the source anymore, so we would lose the ability to verify
> > from the archive who was responsible for the upload.
> 
> Does anyone do this?  Does it work today?
> 
> I'm dubious that you would be able to successfully verify all of the
> archive from *.dsc signatures now.  Maybe you would be able to verify the
> pieces that are the most important to you, though?
> 
> I think this requirement is a bit incomplete, in that I don't understand
> the use case that would lead you to want to do this.  It's more of a
> description of an implementation strategy than a use case, which makes it
> hard to find other ways of accomplishing the same use case.

Not sure if I understood this correctly, but the MIA team (via echolon?)
uses the information to tell us if there is an upload from a prossible
MIA person. (IOW the person is still active.)
I also use who-uploads occasionally to see if a sponsor knows about
where-abouts of some possible MIA persons.

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

Re: Question about embedded Lua

[Tobias Frost]

Hi Kyle,

On Thu, Jul 25, 2019 at 10:27:42AM -0400, Kyle Edwards wrote:
> Hi all,
> 
> As per Debian policy, programs and libraries are generally not allowed
> to embed their own copies of libraries that are present in another
> package, in order to avoid duplication of code and to enable security
> updates by updating shared libraries. In general, this is a good rule,
> but I'm wondering if an exception can be made in certain circumstances.
> Specifically, I'm thinking about Lua.
> 
> New versions of Lua aren't backwards compatible with old ones. In other
> words, Lua 5.3 is as different from Lua 5.2 as Python 3 is from Python
> 2. If someone wants to include Lua in their program, they have several
> options:
> 
> 1. Always embed the latest version of Lua, breaking backwards
> compatibility as it gets upgraded
> 2. Pick a single version of Lua and stick with it forever, missing out
> on the benefits of newer versions but retaining backwards compatibility
> 3. Embed *multiple* versions of Lua, allowing the end user to select
> the version they want, which allows them to reap the benefits of the
> upgrade while still retaining backwards compatibility

I think there is another option, as embedding lua is a bad idea for the reason
you have already quoted: There are currently two (three with experimental) lua
versions available in Debian, so you should run one of those. This is especially
true if the to-embedded-library is someting like the caliber of lua.

This is not different like the python people are doing: There is python3 and
python2 in Debian, noone would embed python itself in python packages.

(Disclaimer: I'm not maintaining lua $stuff, so there might be details I'm not
aware of. It might be that there is a single preferred version for bullseye
which you
should aim for.)

If you really need to embedd lua (prepare to have strong arguments for that,
the one you've listed are likely not), please talk to the security people 

> Let's say someone goes with the 3rd option. I don't see how that could
> be made to work without embedding a copy of Lua inside the program
> itself, mangling the symbol names to avoid a conflict. In other words,
> such a program could not link against the system versions of Lua, since
> trying to link against liblua5.2 and liblua5.3 at the same time would
> cause a symbol conflict. (I know there are versioned symbols, but does
> this allow a program to link against multiple versions of the same
> symbol? Even if it does, this seems very error prone.)

> If such a program chose to embed multiple, modified copies of Lua for
> symbol mangling, and did not provide the option to build against an
> external Lua, would such a program still be eligible for inclusion in
> Debian even though it violates the "don't include your own copies of
> libraries" rule? Could an exception be made for this circumstance?

The 3rd option would mutiply the problems imposed by embedding lua and
also mulitply the efforts on your side (you have to test every combination…
So I'm think you do not want this one only because of that already.
Also, this would multiply work on other teams (e.g security), so I guess
this one be the least preferred one.
 
-- 
tobi

 

Re: Packaging Games with In-App Purchases

[Tobias Frost]

On Sun, Jul 14, 2019 at 08:50:54AM -0400, Sam Hartman wrote:
> >>>>> "Tobias" == Tobias Frost  writes:
> 
> Tobias> Well, if it is GPL3, you can patch out the
> Tobias> real-money-purchasing thing, I guess, can't you?
> 
> Tobias> On the other side: Can you actually play (and win) the game
> Tobias> without any purchase? Because any IAP will have pricacy
> Tobias> concerns… (Desert Island Test, Dissident test)
> 
> You can, but I don't think you are under an obligation to do so.

The intention of this question was to re-ensure that this is really
free, nothing more, not to imply any obligations to do so. (It wouldn't
be the first time that upstreams do "ammend" the GPL3 in an incompatible
way)

> I think you should make the privacy issues here.

(EPARSE) Sorry, I don't understand what you mean…

> But free software is not inherently against capitalism, making money, or
> any of that.

Yes, never disputed.

> You could of course patch the game to redirect it (and the purchases) to
> your servers rather than the original servers.
> Doing that might involve writing servers.
> 
> --Sam
> 

Re: Packaging Games with In-App Purchases

[Tobias Frost]

On Sun, Jul 14, 2019 at 12:37:52PM +0700, Bagas Sanjaya wrote:
> Hello,
> 
> Let's imagine that I will package a city-building game titled
> makaecity. 

Can you share a link? My $searchengine vodoo failed on me...

The game is licensed under GPL(v3), but it has virtual
> currency which can be purchased by real money, that is the currency is
> "premium currency" (which is hard or impossible to get freely except
> by purchasing). However, premium currency and in-app purchases (IAP)
> is integral in the game, because some features and items can only be
> bought by premium currency.

Well, if it is GPL3, you can patch out the real-money-purchasing thing,
I guess, can't you?

On the other side: Can you actually play (and win) the game without
any purchase? Because any IAP will have pricacy concerns… (Desert Island
Test, Dissident test)

> Any suggestion on packaging makecity and other programs/games with
> IAPs?

> Cheers, Bagas
> 
> -- 
> An old man doll... just what I always wanted! - Clara
> 


signature.asc
Description: PGP signature

Re: Uninformative hyperlink in O: (package orphaning) bug reports

[Tobias Frost]

On Thu, Jun 27, 2019 at 03:38:48PM -0400, Boyuan Yang wrote:
> Dear -devel list,
> 
> (Please forward this email to proper mailing lists if there's other lists that
> this email would suit in better.)
> 
> I noticed that for all bug reports that orphan a package in Debian, a semi-
> standard paragraph of words will be provided like this:
> 
> 
> 
> ...Maintaining a package requires time and skills. Please only adopt this
> package if you will have enough time and attention to work on it.
> 
> If you want to be the new maintainer, please see
> https://www.debian.org/devel/wnpp/#howto-o for detailed
> instructions how to adopt a package properly
> 
> 

This text comes from a template we use in the MIA-Team.
You can find it here: 
https://salsa.debian.org/qa/qa/blob/master/mia/templates/wnpp-orphan.mia

> However, https://www.debian.org/devel/wnpp/#howto-o provides almost zero
> information for an enthusiast that want to adopt the package, i.e. there's no
> detailed instruction on how to actually upload a package for a person not
> quite familiar with Debian's packaging workflow.
> 
> I'd suggest some kind of rewording on the website given that this link has
> been posted everywhere in different BTS bug reports. Including a link to 
> https://mentors.debian.net/intro-maintainers might be a good idea. Anyway any
> kind of improvement would be appreciated.

A MR would be indeed very welcome! ;-)

-- 
Cheers,
tobi

Accepted metapixel 1.0.2-8 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 09 Jun 2019 01:53:30 +0200
Source: metapixel
Architecture: source
Version: 1.0.2-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Tobias Frost 
Closes: 824229
Changes:
 metapixel (1.0.2-8) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to QA Team.
   * Switch to dpkg-source 3.0 (quilt) format
 - The patch had also created files which where already there, with
   identical content, just lowercased filename. Those are dropped from the
   patch.
 - Splitted the patch in two parts: one for libgif, one for libpng
   * Do not set palette and other optional metadata when writing png files.
 (Closes: #824229)
   * Convert to short debhelper format.
   * Bump compat level to 12 (and B-D on debhelper >=12).
   * Apply wrap-and-sort, remove trailing whitespaces from d/changelog
   * Add Homepage field in d/control.
   * Bump S-V to 4.3.0 -- no changes required
   * Add packaging repository at salsa.d.o.
Checksums-Sha1:
 a29b9743c0e051a6728b2ea0016de6d710620089 1924 metapixel_1.0.2-8.dsc
 e48460de6d730d26c233f124e8b8513fc9bce336 4456 metapixel_1.0.2-8.debian.tar.xz
 12ca9a151768c54e9509e4eaf77ceff189e6aa24 6035 
metapixel_1.0.2-8_source.buildinfo
Checksums-Sha256:
 46031c38d84ce5cb56c02bac490b2e0a7c4df4315d90c43bbaab6b9dbe907f0d 1924 
metapixel_1.0.2-8.dsc
 2d43daeefded662fc86ea151fd1a35f7a40087d4d6c225a8e679ce1ccf89d5c7 4456 
metapixel_1.0.2-8.debian.tar.xz
 0f0faf3bb5d80f802715ad1c95ddb2e9473aed75ea993caa9910941e3037dc02 6035 
metapixel_1.0.2-8_source.buildinfo
Files:
 876bf6f61a7463474b9363a3e6dc2d16 1924 graphics optional metapixel_1.0.2-8.dsc
 a6dc12658bf263a3f11de85d825090c6 4456 graphics optional 
metapixel_1.0.2-8.debian.tar.xz
 5619984d7fcc02aa31fac9b213eab520 6035 graphics optional 
metapixel_1.0.2-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlz8qV4ACgkQkWT6HRe9
XTYU4RAAtmO6zggqdpyvDleRGqAo99Y48Dl6d0PPQmDq/Bl06nnULkRfiHj3TFHD
VL1zpbVFZwAn3xaNbco5f3zmu02HoFEP+568ssaxPcJ+j0IOCkZsKTdCjwOVmSm7
ADhaqHpId+i9da7Wqk3z34GS4N7YPUglo2jpQE0Vd+UbSDaNVjpqP6XJf06nVlof
QbF5YYvFEby5Xml4FUIViwBYWlaOW/MrLSgotQjKIVf5HltJqPJA7Dn/uhBGVdPy
Eagg0rWRae+r3Va5AtnktTcfFW4uAbFy/YiVHvcfNUE0h5h1dLkDjFdqOyb3grj7
zNzwdz6SYQdzpj8qWcIOu2KRAf8alLXfHrucnFDDwDW2+yvtkvG0ZdKty0J5saoQ
H0Q03oRZPli3bovp2o3s4LVNFB/n5lgZ8bfPyLuuscmjYU4w7KKgq4U3CjqfPHuE
5Tw+V2tlXxz+GxcgIu3IzNVjlbfnxwhBLeywRQ1TMYW9jI32zhZQSgqmoNFmO1ek
xPijdIWFfezZR8DBJQ85Wotp7l5KypRiq+wIpbUDf7UfqgQZSVDIM2KcrCs8Uz1s
ZkEBxJ1y0pSoDEGbtkplt9UMSvIJD7GFEGa15+zJ/yYMNIXBzRrNHWTfUzi7K57n
VEXkp1+CncwRWdUWAyJq1/QQc94PZmz2TAqsX5vm98NfNiOinE4=
=yooO
-END PGP SIGNATURE-

Re: Suspending Offer to Reimburse Expenses for Attending Future Bug Squashing Parties

[Tobias Frost]

On Fri, Jun 07, 2019 at 11:10:12PM +, Holger Levsen wrote:
> On Wed, Jun 05, 2019 at 09:19:03AM -0400, Sam Hartman wrote:
> > Handling reimbursements for BSPs has significantly crossed my threshhold
> > for not being fun with our current procedures.  We absolutely should
> > reimburse developers attending BSPs
> 
> yes! why don't you just say 'yes' to all requests written with somewhat
> proper grammar^w^w^w^wfrom people with a bit of searchable debian
> activity?! that would cost, what 10k a year, and would just be yay.
> 
> i'd be very surprised if it would raise to more than 20k even if we
> announced this *everywhere allthetime*. and if/when that happens, more
> yay, we increased contributors and contributions!
> 
> i'd be in favor. go BSPs!

+1

I think also that BSPs are good to "aquire" new contributors or get them
wetted enough to get even more involved into Debian.

(I think that is also something we need to take care off, I have the
impression that Debian is shrinking in people, not growing -- disclaimer that
could be also a MIA-team-member-view, offseted by an subjective
impression you get when you do MIA.)

-- 
tobi


> 
> -- 
> tschau,
>   Holger
> 
> ---
>holger@(debian|reproducible-builds|layer-acht).org
>PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C




signature.asc
Description: PGP signature

Re: Cdbs Features

[Tobias Frost]

On Tue, May 14, 2019 at 05:35:21AM -0700, Mo Zhou wrote:
> Hi,
> 
> On 2019-05-14 07:59, IOhannes m zmölnig wrote:
> > i've migrated many of my packages from cdbs to dh, but there's one
> > feature which cdbs sports and which i miss strongly (at least: the last
> > time i checked) in dh (so much, that i haven't converted a couple of
> > packages): building of multiple "flavours".
> > that is: building the same code-base multiple times, with differing
> > configurations.
> 
> Could you please provide some examples about the case you mentioned?
> I need exactly the "multiple flavours" feature for at least 2 packages:

"check" is compiling 2 flavours with dh:
https://tracker.debian.org/media/packages/c/check/rules-0.12.0-0.1
> 

Accepted epsilon 0.7.1-1.1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Apr 2019 12:38:25 +0200
Source: epsilon
Architecture: source
Version: 0.7.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Tobias Frost 
Closes: 924650
Changes:
 epsilon (0.7.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from BTS to fix, thanks doko for the patch (Closes: #924650)
Checksums-Sha1:
 a405adcac1a19c7604082156f2db7bbdbcd74b82 2217 epsilon_0.7.1-1.1.dsc
 44a43e483c6d2cb47f40825c3d6a8edc2a24d46c 20004 epsilon_0.7.1-1.1.debian.tar.xz
 a76b4607f5beb8e8075b6ff9de77ed9f7f721e7e 6046 
epsilon_0.7.1-1.1_source.buildinfo
Checksums-Sha256:
 d446ec62bc0e795d1c740d9d06a4e36218fb42fd54e812a07b1e58a626081695 2217 
epsilon_0.7.1-1.1.dsc
 95ce6d48f5169cca3fab70dbc078adff0a6d92d0f9491daf8f6ad46fa7892a95 20004 
epsilon_0.7.1-1.1.debian.tar.xz
 aed0822bc3f069085541ad689e77518c82c9d41db837506822045f88fb4c0fc1 6046 
epsilon_0.7.1-1.1_source.buildinfo
Files:
 e6bda486dd31fcdfaedea32705a15f3c 2217 python optional epsilon_0.7.1-1.1.dsc
 132e1b590ddb261689825bd58db07027 20004 python optional 
epsilon_0.7.1-1.1.debian.tar.xz
 4f7a0781ee37fe25f836771ddaaed9d8 6046 python optional 
epsilon_0.7.1-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlyogxYACgkQkWT6HRe9
XTYVnBAA4vwq9HxH1U5Gx7ax13Q6j2NSQdT1V0l7iAcZLcQOgaL9iRW+CfyJHCbt
k3ayYDKwksRmDI57H9HnWFOFP9G0Isjid0O/V+T4SaAgjSEQ9MZJ2sSt++QypG+/
lcgZ0MT+PSZG7VYkC6ais9ZiYgMsRgr5h5VL1nXIw2AKpbnewY0k2ZQsgRvX+j5l
4GjHDfaJ68CX0xa46Ahw5BI7bvVy6b0eUMZrM6ngnSh5eev2if8MshXnGY6IKC1Z
VKSlDGiLO2LeDycYb1AWd9pgk3LaJBVPZ2A0FNnDy9teGLCx/ZmkoLJSpcPms3J8
Q0OwfaFHoS6B3kjabXIisAgmtEiF4of2WS1NpWMZJSOCCQXqjwsoKv6tf3k+Tdib
Fhl+3DRgkPjKMo+F54ZfeYQHp5Se6n8XdJ4acHPw8X9Dx5+amBDd2ZKS9zovYW9z
2R1I4Zz6yfTLrO8Y9NNMxaZJDQz3yeRigjUoKKfNtUqERaHhrlLpGzUGbE6wAL8q
l5QTVCm6ATM+ci4nmbb0GkOtAa8kT6aboBZCyCfnv5UAl055J670A2s06ksJwHND
WQOfUZtEpRx/LDCqi1/X9OTzU2+XF5Ew1zfxICcV9v4JzGKa4QIrdeWtheyRXQYl
Hc0gUiB4AdZtxF5kxmaZAHBb7kaHXmxw1qETqQQv2Voah0/lBrs=
=orF8
-END PGP SIGNATURE-

Accepted aptly 1.3.0+ds1-2.1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 05 Apr 2019 17:19:14 +0200
Source: aptly
Architecture: source
Version: 1.3.0+ds1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Tobias Frost 
Closes: 923866
Changes:
 aptly (1.3.0+ds1-2.1) unstable; urgency=medium
 .
   [ Shengjing Zhu ]
   * Non-maintainer upload.
   * Add patch to fix UUID struct field not encoded in msgpack (Closes: #923866)
 .
   [ Tobias Frost ]
   * Prepare upload.
Checksums-Sha1:
 2d0641910157673e58e41c63b174c5f721266ead 2858 aptly_1.3.0+ds1-2.1.dsc
 b42f457f50c89d96a30a21e57d934b62ae0d21ac 7400 aptly_1.3.0+ds1-2.1.debian.tar.xz
 ab0e501750df841c1b248ba2c592685f72ab8be6 5683 
aptly_1.3.0+ds1-2.1_source.buildinfo
Checksums-Sha256:
 eaf3baafeb9dec469105e88fe3dcf8e5dd28a67cc10dd77c5f8d0466f2a346a3 2858 
aptly_1.3.0+ds1-2.1.dsc
 0fe29b4ae3f1bcdaf63e666453b94464de5256387de05740daaece8395ad5f01 7400 
aptly_1.3.0+ds1-2.1.debian.tar.xz
 ef7978ba614604b703cfce3e7a755ea6abd92c5e5aa780f2924bb6458fd23609 5683 
aptly_1.3.0+ds1-2.1_source.buildinfo
Files:
 acfa375cdd801166c024a637988c7104 2858 utils optional aptly_1.3.0+ds1-2.1.dsc
 76b8a2b6054023afe8cc1291492562fa 7400 utils optional 
aptly_1.3.0+ds1-2.1.debian.tar.xz
 146b83063eb82acf2fe19f8b2d2dfb90 5683 utils optional 
aptly_1.3.0+ds1-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlyncrYACgkQkWT6HRe9
XTYzuw//T5Y0+XZmiZZ0tZRc4zmmGwsEXlWjwuxofClWLqfaZkzsYh1BWPIWb9nh
8FQK/aOzBMm7EGIWAxBK7W6R9O84Wvxwxb36iF+p1qN24il0kPZEwzOnmyOu55oD
mAzrme+G9/cz9qx8PiUeSg2QQcLRmKd/ClH+cGkh7jZywKNj8lqgabOdbxiv0QGf
QsYNRc/jXrVTzSkT91aTGBmZ44aybf6CnLVDWZqE1EYl2YGswczhIjujKW/u0aXS
p49M9uH6zBuIKYG5c4KnaGQR3GR9PsAOkNLgE5VUBaawYXbcCR+cAzclCRFzjUtr
QH1tTvRiIdCd6laepqM0KGkrsbpYm5jYuGP2iTbZWExRfq3QsuBK6h+Ob+IiaQW0
mJu0ysEupq+zE6lUW4shbC+eAGBFSlj27dh3BlUbQ4MU56Q52xRV/gIa5cfI8rM/
sU6IS0zJ7XAI7BBnMts8/WBkbw34itfDiMfkM8X9P1VTxtwfFUFdNFpmYACpiwb4
MXcoQ9HY9lZH8nGvPdRXQZWw3PUm+/O7bmoJmO90CE6tXhZdgAnKXY21oMeISRab
glexH9E9vxYhb8i7RLT4m0evhh76Rg2+GAB1g4Z0MQeCkGxD8c8rhffy55xk7/Tg
iw7htFK57eYlq4TEgBH+sS497qZUg21SjLvak0yjy+f95uXsyC8=
=DaHB
-END PGP SIGNATURE-

Accepted libcaca 0.99.beta19-2.1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Apr 2019 22:18:41 +0200
Source: libcaca
Architecture: source
Version: 0.99.beta19-2.1
Distribution: unstable
Urgency: medium
Maintainer: Sam Hocevar 
Changed-By: Tobias Frost 
Closes: 917807
Changes:
 libcaca (0.99.beta19-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Cherry-Pick fixes from upstream git repository:
 - CVE-2018-20545, CVE-2018-20546, CVE-2018-20547,CVE-2018-20548 and
   CVE-2018-20549 (Closes: #917807)
Checksums-Sha1:
 2e1614dd299b7b7c39425e48b2d31c63ca9f7754 2224 libcaca_0.99.beta19-2.1.dsc
 2d1ec4d5c49f78ed4348484c5c32c9dc8c10dc3a 12624 
libcaca_0.99.beta19-2.1.debian.tar.xz
 25dd46f63e4c858645423de74a5c337694e82e6a 8416 
libcaca_0.99.beta19-2.1_source.buildinfo
Checksums-Sha256:
 952f7ad2716b6c227597298ffc7d37b0ce199e18b58a5a810019473299e72b99 2224 
libcaca_0.99.beta19-2.1.dsc
 7e2e265972d56c9aeb46686378a25543c6a3d2810cc1649102884dbe9aaf947a 12624 
libcaca_0.99.beta19-2.1.debian.tar.xz
 429ca726810739703e22cd18e6e1c01bbb1798024eaef596739091708199eaba 8416 
libcaca_0.99.beta19-2.1_source.buildinfo
Files:
 436e73482e570ec80763d4839ea6aa3a 2224 libs optional libcaca_0.99.beta19-2.1.dsc
 c7b52b38fcf26c2fcbc8bdef5cc99928 12624 libs optional 
libcaca_0.99.beta19-2.1.debian.tar.xz
 414a1cc1b23fc0acc6bd653c86be9151 8416 libs optional 
libcaca_0.99.beta19-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlypCjIACgkQkWT6HRe9
XTYHZBAA0WPV2UWce3+bRaq6uUYOARUiW3bplW1JdNeDbh4po5LIgUJlyqYDk+3d
/5cBuK+5M0Xz8KVn/2TYIKYW8RM6E5/6atWiNWHaWFwOqUr4n2juaMy3WyuMxb/c
qp/m4VPgYyfMz7CSsnQS3CiEgD0ZVq2MCMFSDfnz6h5RffHNunHW1rz4aNS9kjP1
qIRNMThJY6PqygrIez4tP7lhBPYBvaj8DSZlsrkm4jV2RfxHvWTOfZzpgB6jvFWl
/CkqX+wLDiXM/Vh3kJKV5f+MkAvd7UnWqCq/+qRe0j+oj28RsbQ6DdrEVU9zZQA5
NGGqsyr/2sd8Fi7BQzazR//rWlg4S1fRiukihuTaPv7GNMaDi7/Cv4UBTpb3FmQs
BeLRgSxEeM6xoi7RuDw65BZunaJWLxrSiMwwImW98n2p6MgQaX8wvid7rHBnp4Rl
rCoFV+aadzdn+TzleFLQMkBlCHSv1zIMcTn2l+MQommOmLe+BcS1x7TfzPyrehW1
hLLz7Qu5M5swlISpA04OErCEx7y6uPqwPK4s8RALQNR5WPpYjTVuHRa1jeVG0w/8
+jjpyYD2IpKGEeSi+Csok6LVcQu65UMleGnayjpjxKh4GO/wNsh+zNuxxUal0JwF
QrAgy+gpLCIdp0HzUv4X6OPKp25SxD4/bEIm6sCcALCsuASsI3Y=
=MvhB
-END PGP SIGNATURE-

Accepted golang-github-mailru-easyjson 0.0~git20161103.0.159cdb8-1.1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Apr 2019 17:59:30 +0200
Source: golang-github-mailru-easyjson
Architecture: source
Version: 0.0~git20161103.0.159cdb8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Tobias Frost 
Closes: 854743
Changes:
 golang-github-mailru-easyjson (0.0~git20161103.0.159cdb8-1.1) unstable; 
urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS (32-bit): constant 4294967295 overflows int" with patch from
 BTS, thanks to Ritesh Raj Sarraf for providing it. (Closes: #854743)
Checksums-Sha1:
 b90093df443a1a028c1d7c98913199b42afe1098 2432 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1.dsc
 3059f08915f94487301082b30c472065b832a7a1 3244 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1.debian.tar.xz
 ae01e517699dea8b2d30c209edfc646a30ea9479 5847 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1_source.buildinfo
Checksums-Sha256:
 ba12c0065cad63d2976933110bdde72434c9b32b775dba8c039426a7c0160eae 2432 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1.dsc
 15488ccb0c3feed73a96545b300ae2b14b0638427903cc884621b38c75bdde75 3244 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1.debian.tar.xz
 8eaf377b2bc66265c9b0a4d779ea5e9ae1c43c69a044419aa5b242ceb864be4b 5847 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1_source.buildinfo
Files:
 d972075af30457c0ec063b63754887b8 2432 devel extra 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1.dsc
 1db3d970cd93ae32b22973b7315403c5 3244 devel extra 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1.debian.tar.xz
 a1f00f18aa63af3ed170fb7b08e02f0d 5847 devel extra 
golang-github-mailru-easyjson_0.0~git20161103.0.159cdb8-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlyozO4ACgkQkWT6HRe9
XTaPnQ//ed0YDfp4A+Wb0Iqde/G/x+r6bjAvAxazQHn2N7+IOraJjUXTB1zFmjex
liPQ9CNT7Q+qEiY7v4Jx80oavRhL3f1c3iLMT8qJiGwnZcCyq5m+B9jzdcFG56wb
QGs2PFV4IKRH4iBt4I1a3RJY/0tFT70ELmVRsYFxFhwa/q2EcXsx2NfnZFqcPBmj
geft7cywr4CTmqTV9fM15oQCkhnvZVxlakfUgAjMclbaoOxbvcPKcKeBcLRVVOFN
l6pEFe6EFyKepAfJHBs523TQt3X3F8P3AeMVkN2Xpyb2eVXI9ZMJSKJCKa86lqmh
vbCy5YrtwVDYBAGHXd3VOgyF5N81Xp4od5KjWNdnlqSOu6auoK/e4sK1QCDtDVvM
AETH1AVovvXQyHNrKyObq9RXd/gOT0BWZAYJXaYcTASrVfM6LcTY/FCP4HTSZp+Z
L0IL6ftTHpI1+DQ6f51Ap1JendKUThcWEf7l5WCJvOIoHoUA9fFEXJtFrWkWuVN8
kTOri64NIPmLRASwe22sidfflrzEMEtBy8L8kqLv8wjFTmnYNT/xj8yAZ0Xy9K1D
rIo3p5iy/K90Bq0e+2FTndQb8EjO8kwPqVLcsT5Is1+98RuHA8OqB5uaxppt01c/
V/RiW+5p6g6k79UyTP7djqvB54a6DqK80l0URhaqCdOufuSyY0U=
=aznk
-END PGP SIGNATURE-

Accepted lirc 0.10.1-5.2 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Apr 2019 15:12:52 +0200
Source: lirc
Architecture: source
Version: 0.10.1-5.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team 
Changed-By: Tobias Frost 
Closes: 925066 925477
Changes:
 lirc (0.10.1-5.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Revert removal of liblircclient{0,-dev} (Closes: #925477)
   * Revert "Do not install conffiles in a dummy location" (Closes: #925066)
Checksums-Sha1:
 7626db2ea8c24a7cc1f1f659e2267a3f2dd3ed84 2663 lirc_0.10.1-5.2.dsc
 e930a028201f4e026a490fc96e3c094ff811c6cd 35876 lirc_0.10.1-5.2.debian.tar.xz
 599c95061ac76936790888f7a1b59509161a2d7c 7930 lirc_0.10.1-5.2_source.buildinfo
Checksums-Sha256:
 4452146d09caa7ea18c2cde432b01d21d92c5b14e36deaafab1a64bfb0e785e1 2663 
lirc_0.10.1-5.2.dsc
 ef2dcc608e63baf20fe5df9ebe82ee98ea0526730e5001916dfb112fc399387a 35876 
lirc_0.10.1-5.2.debian.tar.xz
 67ff05b37b7b9f2da273496e12142b91503c90d737d0407b35957ea9fae95878 7930 
lirc_0.10.1-5.2_source.buildinfo
Files:
 680f5f24e4d3e648ea67fb2a787e3250 2663 utils optional lirc_0.10.1-5.2.dsc
 5c33ee654207b8b938967652720479e2 35876 utils optional 
lirc_0.10.1-5.2.debian.tar.xz
 b1bb1124dac7490ee052e77bd213b631 7930 utils optional 
lirc_0.10.1-5.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlyophAACgkQkWT6HRe9
XTbXLxAAgHKFc1dTnf4HjAAadNFXiNoXHy+zorgGcJjTKGvovydjCF0U5P9aYLmw
EFn9y7n0u0b9DfoaMegKwlziy9drVPP+nB1WK8J1TRgOMz5pnV6vfZqq7PeXaREF
y6Y2anvcn7WqsWCjDcqzAUT/VTds50C0ceIiCBfq+ojQObb7/1/KDXPOZnNiMPHw
XP9xuNcffEJ3Cpz6m2QTkhUe6WdIzXY0TrbPZG/klkhhpNA/KPlF+lgIt4SD9SZT
yVcCWHcrVABzGAoSqQOIxhg2DLIFpeDJq97dfBjkh7KolqswfaBLgznEINJ2yALL
9w9R5E+NSms3/+EJpsLsEt6uDR6wmQptxwbAdJQBPuY8j76GdJh0x+IZ2PJy6rP2
ScHTXffmTJlb9OgS1qXOAKD+dTuIX1FLsHQNbFUE2uAHU3CEssQNgGPnN8zlWg2t
MtOYbyuu2IhlvEKVOjmWqpo5dGAJ0w4dhz+ItvAbkhPMlfedKbNM40ZbEd/7ar72
MHY7ESpVu8+jbtdySOWRPM7cxsQ93V4s0kp1o9KGnlTf9Pt4S78vIJ8P+tvhUZzt
oNkLyhTjqeUhSCec11O8y9QYGqKcglDj8PmO7jFNfMhh4Y9yU/GjW67vun6HZ8kL
IjsWq15FPL4GpknzsxAdsXfSP5nUJwEfC7XeBJq40xwr9SRuaGk=
=xz4H
-END PGP SIGNATURE-

Accepted amavisd-new 1:2.11.0-6.1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 05 Apr 2019 18:04:57 +0200
Source: amavisd-new
Architecture: source
Version: 1:2.11.0-6.1
Distribution: unstable
Urgency: medium
Maintainer: Brian May 
Changed-By: Tobias Frost 
Closes: 882324
Changes:
 amavisd-new (1:2.11.0-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix to honor "originating" configuration flag, by cherry-picking upstream
 patch. (Closes: #882324)
Checksums-Sha1:
 3377fe0271e049fb9fb22520363bb7e3ad6d64cd 1979 amavisd-new_2.11.0-6.1.dsc
 ea2ad48b01d7bfcdb301702b335e5c82a269681e 58680 
amavisd-new_2.11.0-6.1.debian.tar.xz
 edea31da0b3efac9772e16fc637c3052c912c6cf 5663 
amavisd-new_2.11.0-6.1_source.buildinfo
Checksums-Sha256:
 b6c5971ee2a4d846335d0ac1837a4953c309fb3bec55835556dddff17bf0fed5 1979 
amavisd-new_2.11.0-6.1.dsc
 4181accb4994c42c44a24daf3fc083cd43c1c6fd637ccebff8661a979bf8f7fb 58680 
amavisd-new_2.11.0-6.1.debian.tar.xz
 dced985262d09bb7aa00e20843d2eeea1fb960e41f2b0276dc7f2c384019d2c5 5663 
amavisd-new_2.11.0-6.1_source.buildinfo
Files:
 5825312a0c7b4966de0a891b86979c67 1979 mail optional amavisd-new_2.11.0-6.1.dsc
 0b1dc77fcd447964d26a8da0fd38dd70 58680 mail optional 
amavisd-new_2.11.0-6.1.debian.tar.xz
 2a07d14614e175bde8f5973fb0278a66 5663 mail optional 
amavisd-new_2.11.0-6.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlynfLsACgkQkWT6HRe9
XTaRohAA2Dx3VFynK97rzwNCNKokxm/8BEoZ71ti141BDnWW7JMLGsZIBjvG1eM9
WOgsxB6wUIJf0W4W7ksQEl4xqlM88I7EQVlFy2cx+BWJrZ/bAZGelBHPmDjAJVjG
qzppakGG6+w52KcuXJl9yUoeBWiCW02Fc0IxWkz2p73onXbmoNVrgPAtMV0QYrQ6
1DxMczUHj7t9CVuqiE/tLAwu5KzpZWMXr0etn79BHytvmyiR0j9X5nH0g/NI/L9q
VVYZ1fXISyC+pnfhoDpxEDHZIQPUtKhioc9il0BUzk81bi3b/fn+GPWLywMom1Qx
OG0ylgTveBE10wESE2libnoZffVfX/UtkVmP4/JYxKaD/nvTnnxY0Kj2t1U6nMMB
VUk9xZd3gbKP+jlCvSTlP65e7cMNzFcDjPKEB0pn4G9pHm6UhjAJq3M7QwXU5Wb9
nDVMqn5QACE1x4F9UgWsZ5yHqK/V4BN/zC3HB03LLNGMjBCrMEfsM4bN0/egVz38
gmhzzhs8VoKfztmqE1CrP6qCyFWX7huMiL5AW0Vif/ibkB/5uG/gN3zOGqN1aj0j
BJsnfBxpkNvaXWjPuX6WYA+IYk8HumarnQtc/1lhz4vaX9Jk+5NjcCF3BmSmvWxC
GzZv54/7e0CSqn6SVzd2TqWJ75k0oTyQOvjCQhrloRiFMrGyp5Y=
=EPvg
-END PGP SIGNATURE-

Accepted tvtime 1.0.11-5 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 05 Apr 2019 20:27:01 +0200
Source: tvtime
Architecture: source
Version: 1.0.11-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Tobias Frost 
Closes: 924076
Changes:
 tvtime (1.0.11-5) unstable; urgency=medium
 .
   * QA upload.
   * Create repository on salsa.
   * Refresh patches
   * Fix "insecure use of /tmp" by only using the fall back to $HOME.
 This is patch 0002-disable-insecure-temp-file.patch
 (Closes: #924076)
Checksums-Sha1:
 40180436dcfd99044e9e6c164be1a20ae02acc99 2040 tvtime_1.0.11-5.dsc
 79e075865f7b39ba644910858d3ee2dff81687bb 40124 tvtime_1.0.11-5.debian.tar.xz
 fbe846051c552c186fb2dde0363ebe9be91db3a4 8304 tvtime_1.0.11-5_source.buildinfo
Checksums-Sha256:
 f57131a0f39f82263c6fb202251395a3e6a1e63156c3dd55e8e8a832f0085731 2040 
tvtime_1.0.11-5.dsc
 40db0a5383112d658d10d1de1e924a604bdad1815e24fde3d3d0e6cb18f663dd 40124 
tvtime_1.0.11-5.debian.tar.xz
 40e74103c54c04599524e246e5e56a4857c5ac5e8776f4ecd57e810a50d49a3c 8304 
tvtime_1.0.11-5_source.buildinfo
Files:
 81943ab3cde05fc3f079b102a4ddb739 2040 video optional tvtime_1.0.11-5.dsc
 308255039bd830f4294cc14a4289a0a5 40124 video optional 
tvtime_1.0.11-5.debian.tar.xz
 c53005d21d2c9acf5647297fe1f62f16 8304 video optional 
tvtime_1.0.11-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlynnoYACgkQkWT6HRe9
XTaiVRAAiIehS5iuw7Bm3Cn6s0WL29NrfP/BFDOaWfTkdcIDK6+POq6AyP91VaZy
0ll36UP6NXaIsc8z/FM7aW+X/wI3znWd6hrGBSRj4cdghDH8+fWpe1DuOT+Pi3b1
38NAo7mVOnMRlqvJWWPKmIhCsC9dWBe1zd3CEWxLtrPHXXwKIugc6a9htfor+X97
/n1QR7FJ0LJeSpDBC5x5ig4T71jYnDFsbgOdLKWyXlA3kHd6SMHs5Qbq2x5B4lZ+
B1+ukNDVbI+pxoPf0eMYe73dPi18l0eoT+LljMLgT7CpjsnUC/3bghni1IR0j2JZ
gS5Op5LZDx4ateLVcXOt1Q+2So7v4OgKP9zUErA3h32O1MgnloCZeO8QI3st91IA
rQJkaSwbuugX+WvFvlnWvjefKaVe8vm6srcBwwnc6I1MPs4zarjr7xmRYcuZMeXk
BRzUYQJH63+Kv8fB9vfuojvjgT08ZQ2Q5BsDJ8yD819AL78uNOcTLqRaUByBKwQa
+Oz6t2WowbbcEt1z6PIkZDesQpLwz0nJs+l+aK1xlFpWiyynfqmFl+1n2DrelN5A
vOmYjekyOH8GQvqOYFffgVRkWefbbJxHPbR/aWwI70TQc1x90v0P9TrA3IxPnFJ+
JmH1o6z8Fgy6DyEIg/Bv794tR/z9z16eG1P1kgEUxj2OsUWHd4I=
=b9Tu
-END PGP SIGNATURE-

Accepted gnome-shell-extension-autohidetopbar 20180908-2 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Dec 2018 12:14:50 +0100
Source: gnome-shell-extension-autohidetopbar
Binary: gnome-shell-extension-autohidetopbar
Architecture: source
Version: 20180908-2
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gnome-shell-extension-autohidetopbar - GNOME shell automatic topbar hider
Closes: 917783
Changes:
 gnome-shell-extension-autohidetopbar (20180908-2) unstable; urgency=medium
 .
   * Recommend gnome-tweaks instead of gnome-tweak-tool. (Closes:
 #917783)
Checksums-Sha1:
 960962cb2b7f8d9339438eaa23bed15c10d9ec06 2171 
gnome-shell-extension-autohidetopbar_20180908-2.dsc
 43911be1e24d6c94b17629c5192d0534cc245953 4064 
gnome-shell-extension-autohidetopbar_20180908-2.debian.tar.xz
 18f2dba4d1aa47db513139b3f583e6524c9ce764 5572 
gnome-shell-extension-autohidetopbar_20180908-2_source.buildinfo
Checksums-Sha256:
 150fd16628727504d8ffeaba1cbc8ed5e6de8b810a0f3d5885aac7b09a147b18 2171 
gnome-shell-extension-autohidetopbar_20180908-2.dsc
 c42ea14dd6dfae49a2e3aa7a2adddb09a5a690fea7f5ede6e816e7b89cb0c538 4064 
gnome-shell-extension-autohidetopbar_20180908-2.debian.tar.xz
 d71bee41ea4f7e9fd863722c211fbf7a166e854d2cbbead71905fd6f4b1b1583 5572 
gnome-shell-extension-autohidetopbar_20180908-2_source.buildinfo
Files:
 ffe1f5034514f1864f2ed394688897cc 2171 gnome optional 
gnome-shell-extension-autohidetopbar_20180908-2.dsc
 fc869b4f3d9308492780cf6b8ea6f38f 4064 gnome optional 
gnome-shell-extension-autohidetopbar_20180908-2.debian.tar.xz
 1d2963de4761d1897b6794c61dc3a1e6 5572 gnome optional 
gnome-shell-extension-autohidetopbar_20180908-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlwoqVQACgkQkWT6HRe9
XTbMOQ/+Iz1TeumSJJBkUh0jjrdchowXTofgGu1EFwa6ns7qcybMVWhstb4emFql
13wlNS0z+VnE7R7K5dY2vqDWSC+ptnHMirYvxkmnFWQfbVUJPaCXEcgrlaxCjfwH
yyfp1hkrVNXuFDolVhUdrdtpWj8awnrj7XSn0NTvIKJMRcaNQ3bXJSEER8Uh2VHm
9zgmBjlmO4AtfneqoqtKF04/6YRrjc4SPHt6dvDxqegXq0tIdWCbcuzja/uFKAiY
DPfsbdSMnS2RJJj399FSD0nVGjtKeDFNmJw7+gGMFsB/s/sMDKl1ms90LxRPZUBE
ccn8GS2Yd3cyyzEZH+5oFuvQ2zATtB/tUenFJZx7k92QHiHFWC2KD8HyzNDWlWHl
D7kKknAmCoZoEj/I1sNnNhRqCJ05RHyhEhcMd9GSwafLhKbrZVi7Ed2LAFczQRkH
WqvffklC2He4bPiiMaiTP8SH/wTX8o4yr7kpDmvTv7x3KUmxxnTwnI+9BlEfZWW/
G5jgwzrvQ4FowdQhqYUUlQEdcYG6HuaD6Yg4P8wZ+UzzgVjPcah9xExc8eX+YxnO
jg3stoLJCsi0vyxgjLaHHQU3uElVR6Ik2dajldTo3BRxqV+zKjlOx8t4ZoBZJG0F
h7a3KKksSzY7iVC3FO7S18U/gVLRgVGh6zEkn+g+IezeF/9ssBQ=
=WGez
-END PGP SIGNATURE-

Accepted gnome-shell-extension-suspend-button 0~git20180827-2 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Dec 2018 12:11:19 +0100
Source: gnome-shell-extension-suspend-button
Binary: gnome-shell-extension-suspend-button
Architecture: source
Version: 0~git20180827-2
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gnome-shell-extension-suspend-button - Gnome-shell extension to modify the 
suspend/shutdown buttons
Closes: 917785
Changes:
 gnome-shell-extension-suspend-button (0~git20180827-2) unstable; urgency=medium
 .
   * Recommend gnome-tweaks instead of gnome-tweak-tool. (Closes: #917785)
Checksums-Sha1:
 2b145056f42b3a02a240a8846ed1144aba42041e 2227 
gnome-shell-extension-suspend-button_0~git20180827-2.dsc
 11e895678821a013e1d872198a3b405120a1c0b8 3620 
gnome-shell-extension-suspend-button_0~git20180827-2.debian.tar.xz
 d8e72fdc78c3b716fffe81da4c8a7acacb60c979 5572 
gnome-shell-extension-suspend-button_0~git20180827-2_source.buildinfo
Checksums-Sha256:
 0a3defc9d6014796aeae0a7f7c12169c7b3c7f125b11828f87f36179ca409042 2227 
gnome-shell-extension-suspend-button_0~git20180827-2.dsc
 ad7b7809ec4465ea3e083f1123d0d64a423d37868ad00a1e8366b2841c2e4549 3620 
gnome-shell-extension-suspend-button_0~git20180827-2.debian.tar.xz
 d02b213b514ed5e07e10575a351c5b727d5a68882c5380242a15fef86d8d631e 5572 
gnome-shell-extension-suspend-button_0~git20180827-2_source.buildinfo
Files:
 9d284ef0a815aa6144530e9f193ded7a 2227 gnome optional 
gnome-shell-extension-suspend-button_0~git20180827-2.dsc
 598a85873796e9de3fe1cc827a75cefa 3620 gnome optional 
gnome-shell-extension-suspend-button_0~git20180827-2.debian.tar.xz
 60cb21ffd348fc55191fddf59ac82c7f 5572 gnome optional 
gnome-shell-extension-suspend-button_0~git20180827-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlwoqBYACgkQkWT6HRe9
XTYtfA/9GRq+JXIvDrM/C3bwFZg9XoVZvRokMz8Me2B0mE+5QkbGr8BKVdq0T7wb
a8kICk0DmDp4XBFdnZpjnAxCnmvgB4b9S/9tH7KabmA8FpWWTjZam3G0fOGzYI1p
huDzwCK/D+I+49tES6q1e4xzkDn4KzpV7mVsEF0e83OaqtWygr+8T+zKMAKwRZss
Do5sSgyqIkAB74o7095BwVtQ1YmRFYyyqLzfpWSm24yclBR5dmUrN0UFQ68ypjCE
CV64o4GafUFO/yz3sUO9qAsdZmZxnf2nUEJirMSamesqRu0tMlr0F/aGrUJEdwAr
tCS3lHj4MMEVCPssUhIv40eLoFkK9lPAkgPyZ36Yb1IsMImZf78YtBHahTH9lFAg
f3rTIpx8ZJtFXF+voUNIDHrQUp5e24DoG3L2GJwdbzU0w+rApFjHagXVZMY2uIXV
9PuTA/zHSbnKsTq/Eb1DM4ryAj96r0nzhPLLHprrkBophRUY2fNnmidxrZccRAfW
uT7dbsL1Z2kiQRPB3G+hnPDZ4y3Yv+jUr270heYdkFxxv0/uKpOU4u0SNyV6znFM
0pBILrY7Donkfiv7CwOhnO4Xw5m3mzuTsCbxnb/YnKWqHEM6gNgWhfO5CvBYT+7h
eK1ePacBD6sd6kNxW05huEEzvPA22TxlUh2OLNZzg+d0zP8T6qE=
=J0K7
-END PGP SIGNATURE-

Accepted rbdoom3bfg 1.2.0+dfsg~git20181013-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Dec 2018 01:40:24 +0100
Source: rbdoom3bfg
Binary: rbdoom3bfg
Architecture: source
Version: 1.2.0+dfsg~git20181013-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 rbdoom3bfg - Doom3 BFG edition game engine
Changes:
 rbdoom3bfg (1.2.0+dfsg~git20181013-1) unstable; urgency=medium
 .
   * New upstream git snaphot.
 - Removing applied patches: 50-system-rapidjson and 90-gcc-fix.
 - Refresh patch 10-lowercase-executable.
   * Bump SV to 4.3.0 -- no changes required
Checksums-Sha1:
 de0490c90f21b26d62fd2e2039f8fd92293c15ee 2216 
rbdoom3bfg_1.2.0+dfsg~git20181013-1.dsc
 7c761d8e7e6481d3f672ac4ddd8d7f09025280b9 2463356 
rbdoom3bfg_1.2.0+dfsg~git20181013.orig.tar.xz
 43605fa74c766bd59bb19aea1ea80d6f8dfb8401 18312 
rbdoom3bfg_1.2.0+dfsg~git20181013-1.debian.tar.xz
 95ed29caed7f466e442161f9710fbf083a29fecc 6862 
rbdoom3bfg_1.2.0+dfsg~git20181013-1_source.buildinfo
Checksums-Sha256:
 5dbb1663b33de9544965ab44aaa38fb183493bab143847c9ae3167993576797a 2216 
rbdoom3bfg_1.2.0+dfsg~git20181013-1.dsc
 541e26b98dc1b6951e35c22eb228331664c97df6cec894d1a91be04423083246 2463356 
rbdoom3bfg_1.2.0+dfsg~git20181013.orig.tar.xz
 7a54ae2db0fa7ca942d38a270a571c1f1916e82864765134a42976dc2023fc4a 18312 
rbdoom3bfg_1.2.0+dfsg~git20181013-1.debian.tar.xz
 5f76b505c7ad7ad1daaf8326a7176f541edf6f86e2b794cc750e94378d8c8468 6862 
rbdoom3bfg_1.2.0+dfsg~git20181013-1_source.buildinfo
Files:
 6ecd192bd84a34db15a6dd6bf0e90ca4 2216 games optional 
rbdoom3bfg_1.2.0+dfsg~git20181013-1.dsc
 d6992eb0312fe369479183aa0e55f9b0 2463356 games optional 
rbdoom3bfg_1.2.0+dfsg~git20181013.orig.tar.xz
 dd4e6561003ca19e8379c477cea9e358 18312 games optional 
rbdoom3bfg_1.2.0+dfsg~git20181013-1.debian.tar.xz
 9995b962b5a2502bda051cf50440d1dc 6862 games optional 
rbdoom3bfg_1.2.0+dfsg~git20181013-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlwoFEEACgkQkWT6HRe9
XTZd/RAAortCdi5qCvJpoabfL0K5CKzr3VMzE6k8LS2VJAnMlw+nWNETSr8qYpXe
+GnTBXJsbqHuF5/SpNrL7It+KIHOp2lAEpzB7BvbKGNT+f1T1PqbPhIfFMPyZdWI
QjY0VoX5ygm+pxfLuR/xYBaCVwSmVjjha97iPaTFz9Bs7q8skBS4xYI4z5OfIPET
6J4dlpGfjfmcd5yx0P4UIVdDB9CDn52eyM20WbL0rykeHoxfATFWfI+Kn6JwedKE
gpCbxDIb3nwNhGivYDPFl9Fs5bq9tEqDVzv+kHcIc5M14q9fVzgJ0iFzfXawMbpc
Et7rU5DRwBTUHc0kDtPI+mM3W3LcTd0pfXBdbDsv8eQaaWNujIAUydhhed+s6Wrb
5kHazWpOcwAqp5tAPcST/fRRYRcvhpYwXqUBK+CTh9oc8sq6FN0JsN8uzzA6n/M5
rPwq0uXCDPPSt2+ddSdPwGVpXL/5Dzox1O6Xe19w8yE008+azS9aM1HlJrUPwpKc
eSOwEK1P3nh+xJixfeA5TOyJLKRhWgCDVmtcgAM5JgJIEPV3PMtwHHLURjiaJt4D
bq7d9LvbeWGGEvT0sJEaxzfsLKpu9q9bwy27KwqPFDbHj+Ded5VqSagOPSl3sZA1
4EV0ukwMSYrZgUGPbmIxpcg0J8r7sId15eFQ8y0RRKVEbD0g1OA=
=90m7
-END PGP SIGNATURE-

Accepted gnome-shell-extension-autohidetopbar 20180908-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Dec 2018 23:40:17 +0100
Source: gnome-shell-extension-autohidetopbar
Binary: gnome-shell-extension-autohidetopbar
Architecture: source
Version: 20180908-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gnome-shell-extension-autohidetopbar - GNOME shell automatic topbar hider
Changes:
 gnome-shell-extension-autohidetopbar (20180908-1) unstable; urgency=medium
 .
   * New upstream git snapshot.
   * Remove patch Adapt-to-removal-of-MetaScreen-in-mutter-3.29.x,
 applied upstream
   * Bump SV to 4.3.0 -- no changes required
Checksums-Sha1:
 81865a0162816b48b68403351b504f8beac5fe02 2171 
gnome-shell-extension-autohidetopbar_20180908-1.dsc
 bc95d3ba1355f58449b2f3c0efcd19274d6819ab 15704 
gnome-shell-extension-autohidetopbar_20180908.orig.tar.xz
 7dcdc04e662b1c9949dc12a7afe903a385bccb95 4028 
gnome-shell-extension-autohidetopbar_20180908-1.debian.tar.xz
 50f501bf2e5a0d37081a57f1e375dffd0bf86d2e 5572 
gnome-shell-extension-autohidetopbar_20180908-1_source.buildinfo
Checksums-Sha256:
 efab932e0b2f71e5d3fb5af9940f26078b38e69b03eda55e59fae63e938f01db 2171 
gnome-shell-extension-autohidetopbar_20180908-1.dsc
 5d45528ed79b4fc9da9e592f593bca3e6b2d5d5983cc9a5e4494c7b96c3f5680 15704 
gnome-shell-extension-autohidetopbar_20180908.orig.tar.xz
 9b82a2de6f7034da3952c5aa58c28efac9858743baa3811556a7d269e6dbb19a 4028 
gnome-shell-extension-autohidetopbar_20180908-1.debian.tar.xz
 8afe836cd0365814140467d2ce6afeb9c1a181d7de13e7d221efafd47156cbcf 5572 
gnome-shell-extension-autohidetopbar_20180908-1_source.buildinfo
Files:
 a774f604ea07c91f55006fe7a5a9e598 2171 gnome optional 
gnome-shell-extension-autohidetopbar_20180908-1.dsc
 0a047fd914fd2078c1b579326a87f828 15704 gnome optional 
gnome-shell-extension-autohidetopbar_20180908.orig.tar.xz
 fe12784afcf3a585be92a3103a62e75e 4028 gnome optional 
gnome-shell-extension-autohidetopbar_20180908-1.debian.tar.xz
 4b7b9e7f081dcdc0729a5bae471be743 5572 gnome optional 
gnome-shell-extension-autohidetopbar_20180908-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlwn+DEACgkQkWT6HRe9
XTbTCRAA0X5JEoWGDApSFGcoljW9vdI98kaS6G4VV/XBEBIEwdXUOCtRzc5Tt94k
Jas0xSo+20qs/9BB9xlz3J30amYQcEXcX7tUNdEnNtumOodC4YxLtgz9bUJGuDpa
5s0LX0s+367a3YgbB9IrXg9zGR2DF72Bozq+xb2mO4bq2gX392U0cS6OoOPbo162
jNCpUYBuwOYD73NSVuPJjeC4RR5UaWuuRVJC9VKA9Yas63+y/lgh/LOvNm+Aqyur
6z6B9ufv1i20WKAdYPwh6KWwOLNjo0VzBa2KwkO3rmWmpPpF3I2RPmgimNtaQdbq
A2FdNaEyNJcQcI8ikfJ+Zn6VwY2YNdG/VFczh92bGYgpIH2S+cZYEReTz9wHZBSu
9G+CTFWoorbznlZ1eMiP23vZQ9Ku41limT65kEHMLAzqEExfhYSde4QO8G8EhDMV
Ox/11KDTDHc2aOBhatR+7WaOe46HVC8rIzvWfd/CfsqEe2o2mLk5t5QAwm64COjy
b5SU6cryZ3RBe99LnATIUqxJA3JvWayk1Hs9t+tPraFisa0RBO+HogZwII5DaVQy
QdUWu8gjKcbCAwSvvzwR3ocyZ3+nHWDRzwkC5P1zorPJOmV/YiQIXiT8xNgYxuAQ
uv6fSv+T3vXY3ZYYHTlGggi/PnMnVcIEfI8iITl74TgwE08owRc=
=TXdb
-END PGP SIGNATURE-

Accepted gnome-shell-extension-suspend-button 0~git20180827-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Dec 2018 23:50:34 +0100
Source: gnome-shell-extension-suspend-button
Binary: gnome-shell-extension-suspend-button
Architecture: source
Version: 0~git20180827-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gnome-shell-extension-suspend-button - Gnome-shell extension to modify the 
suspend/shutdown buttons
Changes:
 gnome-shell-extension-suspend-button (0~git20180827-1) unstable; urgency=medium
 .
   * New upstream git snapshot.
   * Bump SV to 4.3.0 -- no changes required
Checksums-Sha1:
 cad7104dc643004baed5dd63fc73c378786e8ab9 2227 
gnome-shell-extension-suspend-button_0~git20180827-1.dsc
 9e93be4ebc5c529a32fcbbef486728b5b1ec6fca 11976 
gnome-shell-extension-suspend-button_0~git20180827.orig.tar.xz
 3ef5878de2d466d514f5f377a4e8348c824e518b 3580 
gnome-shell-extension-suspend-button_0~git20180827-1.debian.tar.xz
 0226b5bb61e8beb64b46aaddc8f4852e4f8826b4 5572 
gnome-shell-extension-suspend-button_0~git20180827-1_source.buildinfo
Checksums-Sha256:
 0f913b63a1b7c5193af263296fdc97a48bcedf3c7e0a5485a996cc872d187d66 2227 
gnome-shell-extension-suspend-button_0~git20180827-1.dsc
 6a3b68b8358fa48d2f6427fc973b22f556892262ec703674788e9a1f4d8c2b9d 11976 
gnome-shell-extension-suspend-button_0~git20180827.orig.tar.xz
 5d71b31a961241bbe2025af01d01b016240d20915614d5372719dfb732dee9a9 3580 
gnome-shell-extension-suspend-button_0~git20180827-1.debian.tar.xz
 4d6e0f35698546676c57ce67c1e9b3cb1daf9f909576ae598a6b1e511378a53e 5572 
gnome-shell-extension-suspend-button_0~git20180827-1_source.buildinfo
Files:
 a18c4cde295b94b863c1fcc5919772eb 2227 gnome optional 
gnome-shell-extension-suspend-button_0~git20180827-1.dsc
 e2960a32d3c0332e60316ca897992ab5 11976 gnome optional 
gnome-shell-extension-suspend-button_0~git20180827.orig.tar.xz
 e01723e7e2e8c5419d7db4aac8bceb6e 3580 gnome optional 
gnome-shell-extension-suspend-button_0~git20180827-1.debian.tar.xz
 6b9350c9d24966299d64d55ca5a9f448 5572 gnome optional 
gnome-shell-extension-suspend-button_0~git20180827-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlwn+mMACgkQkWT6HRe9
XTY2+hAAu+eeuuT97PNLxZJXSL7gAPBxcUDa21cdz1Xm6fdXNUrtciJzvGw167fG
g5rUFwbG40UUEL3VYTl3KMoel/qBQNqGFXwjbFRWYej4QXp3n9XrWzRa1WgAaRHs
tyopL31UiMoijmZ1gxWdfBrzX2pDfY7CXdkzGRnmeoF8fD06pXyro14rmg6QM0ye
z9iyNky5tM0EyEPe7FST8ZYM3CSVjqy261Lzx79JwRJRUwRDAuwJjXjR451ahJ5I
RGaTP5gRcUnHQba3ELbaEXmADejDMT/pNPqIYGJmrkRALW6LFiMucopuLfBszVA2
+rr4sl+TusSu1b53FtKdT+rlyEasXV7FHdY5LPOHlo50lOc5PcVwHTA9x+GMATzt
cfN7uJ5rTD+QPxHvzmlBtYyCkgNVvaun3wdyKb3lBtXOX47EHKJnnNSXVhdLck1j
SF9Lc3qZfXmJSAg5q0KeYTQUfqj1kVccYOkPGlJtsmZ6ZS+GsYcwpOuT6RjVTYqk
97OLPfU+45gRNqaXzUdmrEHp8hAeX9tasVhH3ckGITfzT2TBkiazzz2yq5of5/Qj
02wAimVqRgCs3foOIS0jRPSYu/FSMKWg0JmbUCI5rLlxSEni0uXOJz36oz8TZ2OU
QiiMAsf1DkXqoTYzBdf/k0Ys4waKhApXm5oy73kzoFF8tLTTfPg=
=0Cw0
-END PGP SIGNATURE-

Accepted gmrender-resurrect 0.0.7~git20180818.a7b0b1b-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Dec 2018 21:43:02 +0100
Source: gmrender-resurrect
Binary: gmediarender
Architecture: source
Version: 0.0.7~git20180818.a7b0b1b-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gmediarender - Small headless UPnP media renderer
Changes:
 gmrender-resurrect (0.0.7~git20180818.a7b0b1b-1) unstable; urgency=medium
 .
   * New upstream git snapshot.
   * Refresh fix-libupnp18.patch
   * Bump S-V to 4.3.0, no changes required
Checksums-Sha1:
 b7f6f41e7df7b05b35bb4770d5c7c90a07e8447e 2122 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1.dsc
 2b79459a31b576a3296446c164a89b1bb5a3fc28 90820 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b.orig.tar.xz
 b00a1a1dcada4d37b3fe7b25ab04e13bcbff32c2 8828 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1.debian.tar.xz
 4b7cf5a288c7aed401b4b41a66649293c415ae94 6497 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1_source.buildinfo
Checksums-Sha256:
 8edc254761415ba9a42a5e0ee59df9093441887f604935f76019a9d4832b2edb 2122 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1.dsc
 2da3b1633f4e713fd0267ab0a51d09df411de47e9617f99b48cbcae49c350bfe 90820 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b.orig.tar.xz
 c5dada5aaba4ec6691507d0a558278f6ea90e253dc6f209c0ba7ee00a7e5ec0e 8828 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1.debian.tar.xz
 6d560a4accf082d82fe4abb3b882330b113a1f7c43e3bb7dec76f2d559e572d1 6497 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1_source.buildinfo
Files:
 328c8d54bceb998d9cc01487cb5f231c 2122 sound optional 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1.dsc
 f98ec6ca95d03d9792bbf3b2bddb2821 90820 sound optional 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b.orig.tar.xz
 0c1a1bc92da4dc2004f9e837a87fe53d 8828 sound optional 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1.debian.tar.xz
 7a2e8ad0a09d35b056964b07f80a16b6 6497 sound optional 
gmrender-resurrect_0.0.7~git20180818.a7b0b1b-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlwn6yAACgkQkWT6HRe9
XTYo8w/8CJPlUfsEOHyUssll+F52ZtdNqTNrKNJ89GfO1sn98THR/uPZzO5uR5au
x5C9nOvcdAY3Z5brpdx3EYX2PDpbl6mZtkhEQfRhq5Bo80zxEv92L+qlHG0ROIdV
/Mn9m6Un7P9FVlcyWT1c9v3n+/wMCzs/cWFHpj2wob3gxzKCE/iK0xoPLqMH7Fwq
LeMPwNSJ1BArxlxN/RufqhGJ9l880c04Zx9/tguSif/qhUWqnJVjz40KneFYmNXa
fI7W/lchsWZqN/o7SQn6POcbL9ZATyjpDlkRYBzugwoIZfrBSga3XYiWzEtXqpB/
HxL30G4jGc/zU/T2mcxzB4THSE1Z+JlXDnLZyypvpHCipJUc+96k5MoNdeR2VicD
RS8Tl3WUTwXILb0j1R1jZt/0jiVmt+nGBrTpBQGsTtbwoSYuLmCJ5T0Yd5h937XZ
LmQpd0dl8UfWOHF40THWdFfZJOQlFYr2QNKLu6MM92lXrBYCva7v6C1ZAlazb8xS
/yTtkFZ8EXQ1EFxVGFA/OqoWJvsk3ntAHL+P0Kj7V8eMpYC9hI5d3QgZHC+AIUr8
8062DTMR20bAe1/emqH0MHDxE+dsH3ZFD9mVOfzzm0s2F8ahoA2mWzCVMlzQwS95
cFM3s3PJ6eTI/U9UtQRXT2gnnBioK7ncM5ZbzdBm9s/Sa0I+E2o=
=fFQF
-END PGP SIGNATURE-

Accepted dhewm3 1.5.0+git20181221+dfsg-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Dec 2018 17:16:34 +0100
Source: dhewm3
Binary: dhewm3-doom3 dhewm3-d3xp dhewm3
Architecture: source
Version: 1.5.0+git20181221+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Tobias Frost 
Description:
 dhewm3 - GPL Doom 3 game engine
 dhewm3-d3xp - dhewm3's gamelibrary for the title DOOM³: Resurrection of Evil
 dhewm3-doom3 - dhewm3's gamelibrary for the title DOOM³
Changes:
 dhewm3 (1.5.0+git20181221+dfsg-1) unstable; urgency=medium
 .
   * New upstream git snapshot. (Upstream marked this as version 1.5.0)
 - remove patch with spelling errors -- applied upstream.
   * Bump SV to 4.3.0 -- no changes required
Checksums-Sha1:
 234109b59dd25b46edb3811eb30d93b1c6f3f854 2210 
dhewm3_1.5.0+git20181221+dfsg-1.dsc
 6b8ac46d4a7746ed8a9e42f2a33f8cb2b2bf4b57 2189540 
dhewm3_1.5.0+git20181221+dfsg.orig.tar.xz
 0cd60763c419ee94a946286075655c02b5ba3370 10568 
dhewm3_1.5.0+git20181221+dfsg-1.debian.tar.xz
 2ecd7af6c4c260d69363d2c686123a916ee5898e 6570 
dhewm3_1.5.0+git20181221+dfsg-1_source.buildinfo
Checksums-Sha256:
 ce1fe1432075431ff7a3f9dc49bda3fa07efc1583dca599e6d8c3dffba0dd939 2210 
dhewm3_1.5.0+git20181221+dfsg-1.dsc
 ca34619400eedee5151cd92247aa3c1497b16dd9b17460ce83a13e80642b1b25 2189540 
dhewm3_1.5.0+git20181221+dfsg.orig.tar.xz
 507b95a435710bfcf00b4276d88f6047c41038b85b82573ff59e1409755a5692 10568 
dhewm3_1.5.0+git20181221+dfsg-1.debian.tar.xz
 d9ab189b3d71bc768e5f6492440aece5625868e70673c1607c9c3c53e60253fd 6570 
dhewm3_1.5.0+git20181221+dfsg-1_source.buildinfo
Files:
 a864f8f0457621b3b4cf6fe48c2b5a9c 2210 contrib/games optional 
dhewm3_1.5.0+git20181221+dfsg-1.dsc
 38c81edb95c2123e8203a3544fb52d3a 2189540 contrib/games optional 
dhewm3_1.5.0+git20181221+dfsg.orig.tar.xz
 1c68c8a4629d15b84fa37ff0f572d549 10568 contrib/games optional 
dhewm3_1.5.0+git20181221+dfsg-1.debian.tar.xz
 57cfeb33e1d4835767bb49f9c115e05a 6570 contrib/games optional 
dhewm3_1.5.0+git20181221+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlwnnoIACgkQkWT6HRe9
XTZRDg/3QTPwznYlLQUuEMSgbsXtC+T0loHKb73tyOsnnX4r4ZVhb2xxex9qz9to
HMIEFjVOhdLF3R833PUBeid7qrz/rVmqA0vZSYw8unfvZoHDZHfkSG8miNpyjJcP
Tb2AnmaHsyzUbTxLMLf6ZCrOGshdbXw56Cro9wnisaec82eoCHPUmCsgNn4BFSqa
62ZheJUGp2OhgLIAiXkdxafF+0aIRqMd5cNE8PAa53jWZn9gV3it71l6SHMXIfkr
PVp1moxZeENMzN8CVk/4abrE5Qe0Z4dtFXV1D6cXqqlhnV3OgXW8BjXb6Cq5KFNK
8OWTghgx0Kh7Hd+RRupdtzug+0l1Zd7/Ll5/bTskMPdAK6YsnsOt8eoJa/gyReP5
eJ4m+TIKfENOmeMkHAgdMoxtr8jK5NFdGlNx8JuSYyE7bJmt1rrbgFBK1zVaEdMn
la2OlRBccZrPEHgwZvkmzdD8jDAimNfneSbwsudvF3M8O0XyAv9m9xFM3FMMFsUo
i3PDnqv0IKyKEhAI4ZuoYlUqCdVv22BtyFD0OmmCLufs/yjp3lxkvfhnBKIZFUp8
mQOdF13/b4k+27cBvXG6+vcfuWLlRC+exeOIttBCV4W9HJTAlzL+0weyHjAlxQMr
zijpj/jL809oOzePzxnbjFPxMNqg+/n+z3/Qd56Oa3W7QFYC8w==
=qRvY
-END PGP SIGNATURE-

Accepted solarpowerlog 0.24-8 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 01 Nov 2018 20:08:03 +0100
Source: solarpowerlog
Binary: solarpowerlog
Architecture: source
Version: 0.24-8
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 solarpowerlog - photovoltaic data logging
Closes: 911952
Changes:
 solarpowerlog (0.24-8) unstable; urgency=medium
 .
   * Make github repo the primary one and update d/control with its URL.
   * Fix FTBFS with boost1.67", thanks Giovanni Mascellani for the patch.
 (Closes: #911952)
   * Update d/control -- it had still my non-debian email in it.
   * Bump compat level to 11. This allows to remove some B-Ds and to simplify
 d/rules a bit.
   * Bump S-B to 4.2.1, no changes required, execpt adding Rules-Required-Root.
Checksums-Sha1:
 86dec20b17e611adef6c81cc6556e62c4794b79f 2070 solarpowerlog_0.24-8.dsc
 95888081202d74682d5272b64b43a09e00cb1314 13548 
solarpowerlog_0.24-8.debian.tar.xz
 c8028f60665502f97a46c95a57988dc7e80f344c 7379 
solarpowerlog_0.24-8_source.buildinfo
Checksums-Sha256:
 f6d891835e25fd5c0317bc36927ba7e5c3603d06f2a2511ae85ff2c653d54fe5 2070 
solarpowerlog_0.24-8.dsc
 59829d8fe754ff0ab7f06fb24e34d13a6634fada1a1620e37af4578f5023c1d6 13548 
solarpowerlog_0.24-8.debian.tar.xz
 fe0ddc7805194a7227cbe160df95ec43652d1f959c1ca0e7cba42ba9b6c6621f 7379 
solarpowerlog_0.24-8_source.buildinfo
Files:
 a4f8f4d058481561c84b1c175e886ff0 2070 utils optional solarpowerlog_0.24-8.dsc
 1747fd2b35fbd38eb95a9fa19654c0b2 13548 utils optional 
solarpowerlog_0.24-8.debian.tar.xz
 75910cefa7d4cf6b95eb0626a0f5e00f 7379 utils optional 
solarpowerlog_0.24-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlvbT5IACgkQkWT6HRe9
XTbN8hAAkrsdjQo9rQhZ8ZziI5pZAZNi9zxnyubSlwxjrfqZVe/tevrr3jmfsjwW
5CEpxH7JMU7/dTsPQ62Tdo03oyEHareJqhfQP5g8TDrkmw//iUMrdb2NJ/GwXgOA
sCm/9lLnpQCxX/IcvUgQOGqNNTUsVW7ib4dsJn96zgzURXrTyXsEN6KJPKyhFwM+
AvTmuS0UZ2yzT2HmGuv3E2rxvKyM7jdFU1bwN7kJxp8fENOvHy90eoeQwEGliEQE
n8VnQUDnsFDUikOdHD/PnuZ0NruadfseiLVzpuy5Rz/E/M6qt43nKc10nbF6hrZk
e6dNeJtdl/hdSMnu+UqMXNxolqqcijioG3A6Zi27GMRP87yAs1D7YrQjcKFxvNIw
THgsa2gA2Xv5AFWqoIw8cAlCoPvIi4DVSmRVoU/S9Elyjb4Err+O8Ei4m74BahJ6
sDZ6daTB0cGHToVGTIjrgoibIAcFPOjiTB0FF0j22Mqb+9IANPG+8dc7ARJXUYlV
nPOo0/z+JHbGaz0jePe6kDJQoSNYq5+EDnX21k8wsLecjEIvkeypjpQXFW9Y66+D
6rE9kpVa0U8CKBE4dxkd2j7N4QS4KJTyBQCzh75qSDWsF3eGlqUEWMvNkVAATDPg
zp8wLDCOgNDV10HaLWpvCDIbg2Wqy51RFFQiQgK/hd/8U91M1GU=
=Giuu
-END PGP SIGNATURE-

Accepted opencascade 7.3.0+dfsg1-4 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 23 Oct 2018 22:50:46 +0200
Source: opencascade
Binary: libocct-foundation-7.3 libocct-foundation-dev libocct-modeling-data-7.3 
libocct-modeling-data-dev libocct-modeling-algorithms-7.3 
libocct-modeling-algorithms-dev libocct-visualization-7.3 
libocct-visualization-dev libocct-ocaf-7.3 libocct-ocaf-dev 
libocct-data-exchange-7.3 libocct-data-exchange-dev libocct-draw-7.3 
libocct-draw-dev occt-draw occt-misc libocct-doc
Architecture: source
Version: 7.3.0+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Tobias Frost 
Description:
 libocct-data-exchange-7.3 - Open CASCADE Technology module for CAD data format 
interoperabili
 libocct-data-exchange-dev - Open CASCADE Technology module for CAD data format 
interoperabili
 libocct-doc - Open CASCADE Technology CAE platform documentation
 libocct-draw-7.3 - Open CASCADE Technology command interpreter & graphical 
test libr
 libocct-draw-dev - Open CASCADE Technology interpreter & graphics test library 
- dev
 libocct-foundation-7.3 - OCCT module underlying all other OCCT classes
 libocct-foundation-dev - Open CASCADE Technology module underlying all other 
OCCT classes
 libocct-modeling-algorithms-7.3 - Open CASCADE Technology geometrical & 
topological algorithms modu
 libocct-modeling-algorithms-dev - Open CASCADE Technology geometrical & 
topological algorithms modu
 libocct-modeling-data-7.3 - Open CASCADE Technology 2D/3D geometric primitives 
data structure
 libocct-modeling-data-dev - Open CASCADE Technology 2D/3D geometric primitives 
data structure
 libocct-ocaf-7.3 - Open CASCADE Technology application-specific data and 
functionali
 libocct-ocaf-dev - Open CASCADE Technology application-specific data and 
functionali
 libocct-visualization-7.3 - Open CASCADE Technology graphical data 
visualization module
 libocct-visualization-dev - Open CASCADE Technology graphical data 
visualization module - dev
 occt-draw  - Open CASCADE Technology command interpreter and graphical test sy
 occt-misc  - OCCT CAE platform shared library miscellaneous files
Closes: 911554
Changes:
 opencascade (7.3.0+dfsg1-4) unstable; urgency=medium
 .
   * Drop .symbols files -- they are simply not sustainable. (Closes: #911554)
   * Bump S-V to 4.2.1 -- Add Rules-Requires-Root: no.
Checksums-Sha1:
 c2ad59c0bc9859adab379c078d0937b95284ba0b 3482 opencascade_7.3.0+dfsg1-4.dsc
 002066c66819d19f3255754e05cfb8c16cdda9fa 60840 
opencascade_7.3.0+dfsg1-4.debian.tar.xz
 58f45e2504da1cfb78458a53335e5b3ca6cfc3d6 8 
opencascade_7.3.0+dfsg1-4_source.buildinfo
Checksums-Sha256:
 b6d3acf6b86f138d87379fd6a75a824fb7b66ac77230c8ce730c3539da2216bd 3482 
opencascade_7.3.0+dfsg1-4.dsc
 c5052957126ba44ea0f4b6226354c8b266821f4761f12ed0867723565e6895ca 60840 
opencascade_7.3.0+dfsg1-4.debian.tar.xz
 d7a6da357b36b3cd7d473f1bf2a23a5f3c9867e589cb78681d7bff9b163ea55c 8 
opencascade_7.3.0+dfsg1-4_source.buildinfo
Files:
 8088e5f14e032ce5453eb5bcea449e78 3482 science optional 
opencascade_7.3.0+dfsg1-4.dsc
 7d7f49d62e154866b2b2afa305158e73 60840 science optional 
opencascade_7.3.0+dfsg1-4.debian.tar.xz
 d0243be91c28224b38f520e41de2dee0 8 science optional 
opencascade_7.3.0+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlvPifEACgkQkWT6HRe9
XTZH7hAAyF8sVh/EEmciHAnRhuWzHeXX/xFdmD44MEIXKTIxgLKOnnzIcPs9l25c
4+iFutn9c8cJquKwK7icSEOp7NV3cJ5yYfsWOZ6fHjPpgAvdxWHuurW1J2o+4mn0
gbJd88W1NCKidIX0wAqYz4CqGdhNN1lmrVWigbb6dlNipPVpSRZ6H/MdLqRa2Usm
eijEAwlKxhplvYXxrmfMIM1ggs5K1uUcJQIb3YiHvr5HcC6u4G8o3oWVbr9otVfk
k++BZ2fiUneo5zrSC95gliiunZlm9FJM5TGSiXGhlpqQ//ja/MWkyHTL2TePRBm1
x9AMxeWB/fJUq8Vpd81OvJX4bys26ctWkd+2HQ6YU00YWt6lZrRj+34x8G+BzjWe
EDi9HM1oUGXnkwCassWx47XLIYTvsCxgRwV8zoTkyf5HWkESRcUWHXVa9ES7bQwM
q65RtLhC95+UJavflKTmot6XuMOmbwEjCEmVPEBj7d9Sxy+4YOD5jOXCDeIqbkoX
mQDfLmwnKhTvgM4bTz3XZcPZY/YXLTVnQD8dbfgkybTg+k863/Xqem5eJ/sDylo9
ckk1fdh9nvJAsXdPi0GI1HTd2ZffJRpWFVYtXv+ezT3jySr/br3Do1My5jHFqgdu
j5iDzcTVp2nVR0JqEV76mF3LN6kkhfWziTTwOJzKt2m8Q4KVxyE=
=sZq5
-END PGP SIGNATURE-

Accepted avarice 2.13+svn375-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Oct 2018 09:40:28 +0200
Source: avarice
Binary: avarice
Architecture: source
Version: 2.13+svn375-1
Distribution: unstable
Urgency: medium
Maintainer: Christian Kastner 
Changed-By: Tobias Frost 
Description:
 avarice- use GDB with Atmel AVR debuggers
Changes:
 avarice (2.13+svn375-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
   * d/watch: Use https protocol
 .
   [ Tobias Frost ]
   * New upstream SVN snapshot.
 - Refresh manpage patches.
   * Update d/copyright.
   * Bump compat level to 11.
   * Bump S-V to 4.2.1 -- add Rules-Requires-Root to d/control.
Checksums-Sha1:
 e572a3cb1fc613107c56d17a3fc19544c4b4865a 2010 avarice_2.13+svn375-1.dsc
 a1ddbe169172109a99f75f8dfa6a55e42d07c043 219908 avarice_2.13+svn375.orig.tar.xz
 bc951d1d87b7d9107cc01d9110c7d158b9950f68 8412 
avarice_2.13+svn375-1.debian.tar.xz
 61fa4f993cf6fba3393f0dbe163ccb0f9d81fb30 5502 
avarice_2.13+svn375-1_source.buildinfo
Checksums-Sha256:
 3a7d240b58a12c9389fc9d9dc5cd9771d6fd480a87d8804dd39546bed169ebed 2010 
avarice_2.13+svn375-1.dsc
 512d1fa0b53e282ace29acc3b7a118451d131a944856a0f80388bf8c9a640885 219908 
avarice_2.13+svn375.orig.tar.xz
 ff4744528bacf135fe8b207ffa53a0fd8eb70484590de35dca8d5e1f6df02170 8412 
avarice_2.13+svn375-1.debian.tar.xz
 e96e9691c5455505c6fd8e09274401bc6f2e72c2d8c3483c13a17bd6305a 5502 
avarice_2.13+svn375-1_source.buildinfo
Files:
 1d5a0a4f7679063410c535b958518f03 2010 electronics optional 
avarice_2.13+svn375-1.dsc
 88d87e422c61bac872b8100dc7d7a57d 219908 electronics optional 
avarice_2.13+svn375.orig.tar.xz
 089f7a31683b83e25049b24ef044510b 8412 electronics optional 
avarice_2.13+svn375-1.debian.tar.xz
 260dca747929c31164ff37b206894810 5502 electronics optional 
avarice_2.13+svn375-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlvMLg0ACgkQkWT6HRe9
XTZTyg//ZOyaDrsU5K2dXQPa+xowX/0fvPlAlio+ghUvjiGNF9p4K1Q8z46EN9P0
A3IcNyLNa5rmBz+8FGvRlNybL49zZFBhInX3PSn4xSs5GMBr4Lg5mJ0MsPeEA+jb
beDRyeGAhSPAweYj5XpTj3+pKc701ISvcYGBh3aGvdABct0sZBwc+uCyjChniSVr
C5UAvh4Lb6DYWwbFv4QgXnZzDoC1ambOKDNil8Xb4s5ZparA1r8urbUEGAKUTGfT
Ccuba/GhOueC34v9R+Sz+EZnD3pMrwITJ/tho/m0UygBEsPB7I1ufx0m+U33Ft4O
qFBHNuX9+maP5uG0eG9e5CFksB5Rm0BFt1ZJjdi4KIzcvRE6z5WHD+D2SQG0jacy
zzLZMB7kOgJ4xbDcwx/F26/kqjl4SVzBqh7PvsMem103jutCl/rsC6CVTO981vdZ
Z4JrKTG7LcLoB54zPCxvSrc4zJ4OQE1qU8Yng/ZQTaYBkZ5hg2SsLNiiDv6QV6L1
vSgQcQCHE6119RsbGXSX9uK3wdWN91cLjgBMga7mcow9mbbiX6cWmY8ehYvZjsIB
eobFA4CgYvds5Wn8lnvXRYdFqMI4KYtlCWZ8Uag1Q/aeUo7ao4EqHWM4wkGOHEf5
wGQtS5MYE2atw2V/sZxLz/ti6MeSfOz2FVeaAmE36zYoA/6Vw9s=
=V/pF
-END PGP SIGNATURE-

Accepted dhewm3 1.4.2~pre+git20180930+dfsg-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 20 Oct 2018 10:12:31 +0200
Source: dhewm3
Binary: dhewm3-doom3 dhewm3-d3xp dhewm3
Architecture: source
Version: 1.4.2~pre+git20180930+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Tobias Frost 
Description:
 dhewm3 - GPL Doom 3 game engine
 dhewm3-d3xp - dhewm3's gamelibrary for the title DOOM³: Resurrection of Evil
 dhewm3-doom3 - dhewm3's gamelibrary for the title DOOM³
Changes:
 dhewm3 (1.4.2~pre+git20180930+dfsg-1) unstable; urgency=medium
 .
   * New upstream git snapshot.
 - Adapt d/watch for upstrem version 1.4.2~pre.
 - Project has a new homepage
 - Update d/copyright.
   * Revise patch 20-spelling-errors.patch after upstream feeback.
   * Bump S-V to 4.2.1 -- no changes required
Checksums-Sha1:
 5bd75e6d161fb42955423f0d1392cf29249e5b75 2238 
dhewm3_1.4.2~pre+git20180930+dfsg-1.dsc
 ec6f2af9c830c64a8ee77744b28bff5b07350175 2186984 
dhewm3_1.4.2~pre+git20180930+dfsg.orig.tar.xz
 17fb43e95a1202649aa8c80c47db6f7e643d56e3 10876 
dhewm3_1.4.2~pre+git20180930+dfsg-1.debian.tar.xz
 d4eae539275f3772b9b32209489c0369e04bc067 6682 
dhewm3_1.4.2~pre+git20180930+dfsg-1_source.buildinfo
Checksums-Sha256:
 0b2c864e66b831056f5cc9d38c71086550dd37327459c2df463770431480604e 2238 
dhewm3_1.4.2~pre+git20180930+dfsg-1.dsc
 e7281f11b3e8e439f0f0f5bb1b3d88cae366edc96985c55ea7423930cc2f405b 2186984 
dhewm3_1.4.2~pre+git20180930+dfsg.orig.tar.xz
 dbf82a16db86bac52869107fc4a0b1c43830f584d5dd794288093406a8732a6a 10876 
dhewm3_1.4.2~pre+git20180930+dfsg-1.debian.tar.xz
 92b325144b4dce1b25c407508199d96d1486965f266865e377cadb8790a05b9e 6682 
dhewm3_1.4.2~pre+git20180930+dfsg-1_source.buildinfo
Files:
 97b669f9c914a6224ed969ab9e157b7b 2238 contrib/games optional 
dhewm3_1.4.2~pre+git20180930+dfsg-1.dsc
 4419de943b0ef16305d4d0835a4eb650 2186984 contrib/games optional 
dhewm3_1.4.2~pre+git20180930+dfsg.orig.tar.xz
 726bd9bcc01030c8bb2c82888e72f0ee 10876 contrib/games optional 
dhewm3_1.4.2~pre+git20180930+dfsg-1.debian.tar.xz
 54f54992234dcfe8928ae3f37b5701b3 6682 contrib/games optional 
dhewm3_1.4.2~pre+git20180930+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlvK44wACgkQkWT6HRe9
XTbBTxAAnVNoUuqc6C+WkL7as+cLNpDO6qe+rKB70fxdMbibohcQpNi5yx89c5VY
a0mC/9t7Wg99Vsb9xruAHryDAN3TXXwRSwV/FFk+JdMp9ND1XgSQ6pWwLSkoKzkf
uOMifm9eh3j7RcXZMVClNHaP08vDfhBxXYRwQJXw4Waeo+xuqat9LHBSiwVErVJ0
WTnqctqL6Eoa9pYen/rcbtaGu53V8lcVH9bA/I7Kh0UjkoFY2Hi0FMM+X5L1OU0O
T3w3ochs7/i8nVMLDGEV6GOhSZpz6t/RsCc83pEghO6XrSpbYnHo3FhiC2sLSEwW
Y/dqH9SHaynvRVF7jUrJM+3hiKrRSf1iSPm/fFXC8aZ/b7H7YiIofL55aMYjvVjZ
jvxwb8ZTdDQTPPGLWOsON/lEw3jXppXXCQ/5LzTsan3l85fybF2fFpZhtiOMaRPj
ysiF22Px4c33/NfqYknAo//Oe4O9h3KKeS7DjNkSEQtLcw/9XclcTCviB59tC4Sq
chWSvxcvk+1s5scrhy4OGNtKxNdEwfyRjWrEASHhg3JttSTjrGrHe8WcyMHTbjZY
RjAo5+sthY4FHwqwZCMOTO9zqNbfdnbdmFVvgoWtThLR7JIjwqqxk6N6JVmZX0Q7
aRQARXDOuNQWn4pUAEd5Dn5lBzTZxf05I9yhz2bz+S+o0nVeDsQ=
=gwas
-END PGP SIGNATURE-

Accepted gmrender-resurrect 0.0.7~git20180618.d0f46f5-2 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 19 Oct 2018 22:16:46 +0200
Source: gmrender-resurrect
Binary: gmediarender
Architecture: source
Version: 0.0.7~git20180618.d0f46f5-2
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gmediarender - Small headless UPnP media renderer
Closes: 884246
Changes:
 gmrender-resurrect (0.0.7~git20180618.d0f46f5-2) unstable; urgency=medium
 .
   * Fix "FTBFS against upnp 1.8", thanks to Uwe Klein-König for the patch.
 (Closes: #884246)
   * B-D against libupnp1.8-dev
   * Bump S-V to 4.2.1, only change is adding Rules-Requires-Root to d/control.
   * Execute wrap-and-sort.
Checksums-Sha1:
 215dbdf7bee1b85479a58dd813b17bedffa10f02 2128 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2.dsc
 9a982d030b19b1bdb488b530be593e8ffd2eea62 8944 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2.debian.tar.xz
 a72ec0c354b36ffd93ee38ae0ee23bb7f7750a6a 6511 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2_source.buildinfo
Checksums-Sha256:
 b8ad7f8f2e8a7bf3ddfd28aac0aa960f4f2537079f3c36b6f18928c86d8afb2a 2128 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2.dsc
 28eff32720ebe2fbf7ce39d8fea9e9eca52740422401c45c228ef66f3f751f74 8944 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2.debian.tar.xz
 17e59e5c70741e9af0a8ec3529a4b4f116f18216d2d48d8f7ced3f0679d8b754 6511 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2_source.buildinfo
Files:
 8123d1bf587fe3ac49d2c9b09aa3c008 2128 sound optional 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2.dsc
 9af5d9243048644df9a68c534b67e074 8944 sound optional 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2.debian.tar.xz
 f31b9e0cadb463f296c572f7fe1a777e 6511 sound optional 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlvKPAgACgkQkWT6HRe9
XTaSIQ//eNXsJag2blPMM07sjGPCJxJjwoP6aUmEDUDeiwD2ZUwVbhZYxgLYkuif
Z0wgxwfhTZFDjNwAuQ6afoiwkGNIXa+fgwI91DZPcUeVpuJGz3S/12RHVORjxPcP
UGVCIngkEvS0bch6G19IVwmORpOiTWMeM6bB/ca5Ii/TTuMz47RCtVmlbsis40Vj
DgpwQBFz9eQtWoJJhF7rUJ19SjBcOmivqKY/UjrkgqBzj8wOh52GZLy3esP+wMbV
O82oClIR3ikSN5rcrZyToPcCmmYJF6SkfgZldhLhVcTb8qFJyWOmODbUYjKeYUFK
rk9jIqu2hCYBYsbnfkYGl4GMKKqlA2u+1fPF/uItX9WaAevQHB7y7c5PODA81dSQ
+wDjF4iOe4ZBC6anVzbvptLs/8u4dJFCRt78eLaqEAL9y0ug+OKHk2nZqsIT3BaX
qAHfnnSIXrCk53ab4NLbcxPnNPdf+nFI5wriYFDglbd5F/LYjEP41Anj91vqbukc
mRTASBIj12dZhd/AQO8Iw9WrkwggoS5SyrTYMptowUHDtIEtSBf/s4y1El2ahkQ5
RLV3RWl9x9/3XDcKgtRcDco1V/gcyD9KexkQXFSRNhJn92nNod6cLKOr8K/5/8lN
DXvOeMT9LnsXFpOJoJRvFVmkzEZ/vF5XtmIfRX5Svj05uuydebw=
=jHd3
-END PGP SIGNATURE-

Accepted backuppc 3.3.1-6 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 17 Oct 2018 23:53:54 +0200
Source: backuppc
Binary: backuppc
Architecture: source
Version: 3.3.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Tobias Frost 
Description:
 backuppc   - high-performance, enterprise-grade system for backing up PCs
Closes: 488098 820980 876188 876193 905761
Changes:
 backuppc (3.3.1-6) unstable; urgency=medium
 .
   * QA upload.
   * Imported package to salsa.debian.org and set VCS-* fields accordingly.
   * Execute wrap-and-sort.
   * Convert to 3.0 (quilt) package format. The changes to the upstream
 sources have been put into 01-debian.patch.
   * Fix "FTBFS with merged /usr" by specifying all binary paths and not letting
 configure.pl letting them guess them. (Closes: #905761)
   * Modernize Package:
 - compat level 11 (d/compat and add B-D on debhelper >=11)
 - migrate to short debhelper.
 - drop the versioned conflict against libfile-rsyncp-perl, version
   in old-old-stable is already new enough.
 - remove versions specifier from dependencies, all are fulfilled in
   old-old-stable already. Tar and dpkg can be dropped, they are
   essential.
 - drop d/menu.
 - convert d/copyright to the Machine-readable copyright file format.
 - modify d/watch to point to (new) github project site.
 - S-V bumped to 4.2.1:  required.
 - postinst: do not check existence of executables with absolute path,
   but using which. (lintian command-with-path-in-maintainer-script).
   * Add patch to fix some spelling errors found by lintian.
   * Fix "Wrong path in BackupPC_deleteFile", patch from madduck (Closes:
 #876188)
   * Fix "BackupPC_deleteFile uses deprecated defined @{array}", patch from
 madduck. (Closes: #876193)
   * Do only recommmend smbclient and samba-common-bin, do not depend on it
 (Closes: #488098, #820980)
   * Change homepage in d/control to new upstream location.
Checksums-Sha1:
 22df487e26b030731134ccefa6872db4b2b6a69a 1847 backuppc_3.3.1-6.dsc
 538a2901adfbcd75a11e1013aa679645421e171a 45144 backuppc_3.3.1-6.debian.tar.xz
 ffe29cfced6be1dd8d0a97a24f48c78cb31d0154 5469 backuppc_3.3.1-6_source.buildinfo
Checksums-Sha256:
 e34cefbbabaad26dd24b23b62a61c471268ea009b60a28e6a2641b21a02bf8ef 1847 
backuppc_3.3.1-6.dsc
 c9fb97927df6eb804373e378b476f1324d49aa12a0e174399f27382bd794819d 45144 
backuppc_3.3.1-6.debian.tar.xz
 6c05abf287fdc0aab2f619e0bf4e00d820cee45308909cb1d2a45d1b57bef5a7 5469 
backuppc_3.3.1-6_source.buildinfo
Files:
 a15eb367caf963cf210d812b85f16cba 1847 utils optional backuppc_3.3.1-6.dsc
 254bd39960dd5e21160b4984ac8cfc25 45144 utils optional 
backuppc_3.3.1-6.debian.tar.xz
 1d4acb0921d24d65c9a9a572459df976 5469 utils optional 
backuppc_3.3.1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlvII1AACgkQkWT6HRe9
XTalLg//f9MraAQrr5lAtMh0v8mO8NIWci5/+Tmv+X6i40AHycuhlE9rwb+nC1B7
ShW/YrifbFZKDEIGVPQ9BSA05gRs5Goviybldm5Ly1LOIhpVIL2Za6k56miAfVbY
sNCILxnOAgzFKo8c+f08j7o2ehrOCw74T8GdlYH5m6fHkcrURFvIrlOyrif0HBkb
2GWuKnLoGn/9XHqS3Lq1oGEITcZmPTOC69YAaNFW5a76o1zfA1QiMzyHszafW9ai
kdMa5r5Mvf2xsOpwT4jEWyQ2U9Nw8VRHY28Z7mDxjAInu4nlhldbNMJ2Wxuod6QS
obeIMpXdDv9Dp5bGRl9ndUwRgBECWY3yH9/ZfmnKgNkNU/3fU76yfP9yHOln+2Qx
ueEVNwRIE6SqwQH16OtTAswQdxLmjQkZkkQ9ZPjEVUTl0CmT7KW/SWtQhjMT8euL
txx3+AP/SGywXc9g1BzKJv4W8VLdr+eiJhJiGSXRxDPRMwIfktLsUgqPpQioAe8b
FlQ0MsjX/TOAWFFGmAr/P18dg81UGN54BT4nVURc0rlFwkFyBs3OezvMxv8Whn8X
t0Uq/wvtOXj9llBL5UMrqVr60ooOZlRlNohgWGJRSy4DiKXQD7Gp4z7pgfrlhT79
N1qftVX+nyIZfFtFzldm1KFVKvKT5szNJLV5jgAxmDL6kYXTwWU=
=4NLY
-END PGP SIGNATURE-

Accepted faketime 0.9.7-2.1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Sep 2018 16:35:04 +0200
Source: faketime
Binary: faketime libfaketime
Architecture: source
Version: 0.9.7-2.1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Tobias Frost 
Description:
 faketime   - Report faked system time to programs (command-line tool)
 libfaketime - Report faked system time to programs (preload library)
Closes: 897747
Changes:
 faketime (0.9.7-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Cherry-Pick fixes for the FTBFS with gcc-8 from upstream git
 repository. (Closes: #897747)
Checksums-Sha1:
 ec2615155ce66d554e691d9d4b875463792d45c4 1930 faketime_0.9.7-2.1.dsc
 c4ac34ae07629d9696107745749c09e3ffc2bf0b 7136 faketime_0.9.7-2.1.debian.tar.xz
 04c7aac35e56b5ab56427cd155923d165284c256 5526 
faketime_0.9.7-2.1_source.buildinfo
Checksums-Sha256:
 f91b3daa8cb832629c2537fd639f9f1083b04b16b6e00b8f533e531cae5abe12 1930 
faketime_0.9.7-2.1.dsc
 50001346518468173181830b67d1bfdf9f627d950f7b583e03182e9f7e23164e 7136 
faketime_0.9.7-2.1.debian.tar.xz
 a11da736a380a4c7e7a7031db15f282a1b7b86157e86260fd6db8274b0fdac3f 5526 
faketime_0.9.7-2.1_source.buildinfo
Files:
 1cb3e029752a31b2faebf237066b2e0b 1930 utils optional faketime_0.9.7-2.1.dsc
 5f81050a4b979c4b9791ce0c52c00227 7136 utils optional 
faketime_0.9.7-2.1.debian.tar.xz
 db82e44e38f6e6a17705dc735d40b478 5526 utils optional 
faketime_0.9.7-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAluvj5kACgkQkWT6HRe9
XTb9mg/9H+p64411iVjM551UCq6FV7hGyIkeedrVCegZ9RqlAmS6tq1sJopKaIfS
+7cCIWo1lVbnaFEwRIrMc4ysS1yyTEetZlwNrLE0krlb4wg6fBHYrUgTw12ABRF0
WT4mE3s7Tqh6wH1uY1r9jjaAY3wXRd8aiiaF5rvH+QqVwIJVYGJkNaPinV9n90uI
hprB1k8Ek2vRlWZFs3+MXw0TTvrN7kxGBVjuN87OmgIwETMaQFdI614iPqsjfepX
GgUewrm7Nxu000R9iZQzH3fcoNvVyCDiwYu/CMG5a7/Qxxbv8F9f1avbnJv2GagM
vcZxo408P/+BmBCv58XlQTVExvZM7H94oCW3+gvA4gm1ouvVWQ0weMlnGT/NzVsb
GKQCz8yRFuKHNjykUb5lSzWRWOocwXXZeonDtqLsbzLNF2W4ufsk/rcEEJUYZHlj
HIvuwdfbvfm1QJipzIZ4Q1Bf8kdBCEbAC9zo75DlehVxUmNanmKy+YeFv+nsAcCI
/UvDAPF4HHCLdW2tnrohL/q9HQYl9Qj5I9i4oNCChI3hKTi4FPjVlcJWQOZrnnB0
NWE6A8hotjZSASlxLWz8sZtuQ4GNa1S5BXPjwUDS94yhed4F/bPHbHg3K/auxC+G
VuXRGnRGThFQpl3DbmZc5msbd186GXb8O/8MI4Ckdl8l0tfKKNE=
=nhXm
-END PGP SIGNATURE-

Accepted quixote 2.7~b2-1.3 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Sep 2018 09:27:43 +0200
Source: quixote
Binary: python-quixote python-quixote-doc
Architecture: source
Version: 2.7~b2-1.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Tobias Frost 
Description:
 python-quixote - A highly Pythonic Web application framework
 python-quixote-doc - Quixote web application framework documentation
Changes:
 quixote (2.7~b2-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Really fix #820132 and really remove Oleksandr from Uploaders.
Checksums-Sha1:
 ae7056a6edc751eb101dd4d860d90672913e38c2 2137 quixote_2.7~b2-1.3.dsc
 952144d819caf838c29b44d1103ffabcc4113ece 8128 quixote_2.7~b2-1.3.debian.tar.xz
 4699c663dac3f30078afcec2bf12a070a7931f7e 6308 
quixote_2.7~b2-1.3_source.buildinfo
Checksums-Sha256:
 9bb9007105bf237d6ed7fc418f01a750c05c9e06f48590d169d7f83dfb04f8d5 2137 
quixote_2.7~b2-1.3.dsc
 dd9f750e694e381057dd034bb48b17f3d4788bd3eb4167cec822cbdc688e2a3e 8128 
quixote_2.7~b2-1.3.debian.tar.xz
 6da0a2d04557746c07a49d4eccf6f3194c2ecdffd83471f1859e0452c6d60f01 6308 
quixote_2.7~b2-1.3_source.buildinfo
Files:
 7b69159ba038393211248dcfc5e415c4 2137 python optional quixote_2.7~b2-1.3.dsc
 88786ba697c779d02dea5eb30af31873 8128 python optional 
quixote_2.7~b2-1.3.debian.tar.xz
 84bd6d9ccb7609afdec3736fe95b3310 6308 python optional 
quixote_2.7~b2-1.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAluwe1gACgkQkWT6HRe9
XTanzxAAtCDuEEEesulIYsHhmbNRltnQYUI6bjrFBSiPqtDIj6Yu2hUFda0f0j/w
W2akwKYnMZLRFAaj9XhLLZ1Iol4RMbtXZuBGPh4kmeJMnS4g7bqgGFlZTlm7UxYp
PzDx2yaw0GR6OS3rxcdBOxIrAwHT5hxQ+4QTWsWfr+se9RGzY8i1IDzE7N8uu0zV
i8pPrAmq0S9wzAoRiflGmT4rVTN1jQTFyytBJsnRh84JX5LrWEyCrY+LVdShcyVG
WHzHqUw9mn7xXqcMMxEG8YQsuRpyKHrCl64CxwDF9aO+1LAuIVViKkDSCP6V9p65
jrye/rq/ZqSqlQJ//bWt1RL71AgU45Hv1Z4Nf+YMG7EV6s1iPHM2x688KqBazEhe
0kqKtqhIH6w+Cd9+HpxrKjrqZsBNcZQ1/SPa5OUwnmb6kO85AX5Z0YdUVTbfbspf
H773n1XtSXFFz4j6frabWuWxeDTrIuKWIpwJMd1VNgn0cPxGAV4ZkfPRtlaPV7Tb
jECPHFA8nvqP4aRvklPhSYVg6dbuP6BM86+p4tWF2tvBx4a2Dt+rJM5JgMGnvJAm
XArECRQZwSFdZ9C+4ITSHrjt5ktjct69vRx2ktms4AM46PrqErW9wPHtE47sL/jO
jg0iTClRmudy0nGdEZ4T1nIFyKArxh6KamRqbzcaoybJRREHMg0=
=Jq1d
-END PGP SIGNATURE-

Accepted quixote 2.7~b2-1.2 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Sep 2018 23:26:25 +0200
Source: quixote
Binary: python-quixote python-quixote-doc
Architecture: source
Version: 2.7~b2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Tobias Frost 
Description:
 python-quixote - A highly Pythonic Web application framework
 python-quixote-doc - Quixote web application framework documentation
Closes: 820132 822020
Changes:
 quixote (2.7~b2-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply patch from BTS to add missing "build-arch" and "build-indep"
 targets. Thanks to Santiago Vila for the patch. (Closes: #822020)
   * Remove Oleksandr Moskalenko from Uploaders, thanks for your contributions.
 (Closes: #820132)
Checksums-Sha1:
 595f6b95f6d3764748b90a720a7231398b09e80b 2178 quixote_2.7~b2-1.2.dsc
 90162e75973948f94da6f2bea3193244da44d99f 8096 quixote_2.7~b2-1.2.debian.tar.xz
 31629d1ef1214e2b0e51872f0baae26cfd0314c4 6308 
quixote_2.7~b2-1.2_source.buildinfo
Checksums-Sha256:
 79e80e54866728a17759aa5044d1581b2521dd9f546cf53375e92204d98f6adf 2178 
quixote_2.7~b2-1.2.dsc
 26c926d84840314e2c1dfa5a6c3e2429201f0588eeea687110dcb158754f4dd6 8096 
quixote_2.7~b2-1.2.debian.tar.xz
 770ac9d57a53114fd9cfdbefc6c9841465de6b5cb167a0b0357bd029f7dd0ab4 6308 
quixote_2.7~b2-1.2_source.buildinfo
Files:
 fadf7b128ef54f7573bf7aad158002cc 2178 python optional quixote_2.7~b2-1.2.dsc
 5c3146edcfaec7305a55bb67879ad165 8096 python optional 
quixote_2.7~b2-1.2.debian.tar.xz
 a5e4b0e08cb2501d3d21fbde22ff4dbf 6308 python optional 
quixote_2.7~b2-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAluv7wUACgkQkWT6HRe9
XTb61xAAm2LdBHOloSGV6Hj83xXA1RWYPooqw9Q82xHtSLY86YhoN6IZesuGt9jX
KLUheglRwsvVW0lF0UrQnzDvaVuMCaufuzqMSnhY5T3bau0D1/fsIy/HxhMBxaEd
6JDYd8yt3DmTECQyYr7kaF/6RU/RsKT8cHN3aUSzIk+S0FBWMUdp9WXIrsoa4iMZ
qR+TzvAGls245yLt4MfLm8hh4gCUThwj/Wv3CIh+NDncjJnzkG3S8QAZaxzA+bqt
fZ2xdz1Uc5+24l22XprDDKCnNDEpWZpAetEu66Fcv0jRzffh2FFmATo2x/gY0wHk
+rlFe8TOA6zNziXJbXyt7k9FLacvyQCQ6y09zjqTIKWmm5JOPgdHQM5BzBBAzfEW
7dj4llrH8kuLCkbGUn5whn2saopUCcjLYdKeqiDUqvR2tBO7NIEHB5abAohSfmqz
kuhQSDxXONjiypeoBzyzcGkV79sUzuAspd58t21j8B+onMHwuEb/seyX3cZtqYDS
XD+TQT+0PruYevbLNw4/abAs8f6ZhBOrwbLHerdQJ2u4g1kx6aE+qXzx5cpz58En
FGXStHAtStHAzp0nsppgAgL56903ZIwCpm5m610tUD7SNWtXoNnSyFvrKvUBDa3p
wVJ2aG3hZfVBg0zxvT9msAEDtSG9IX71d4p4iRUBX1rBhja8FEo=
=5FGf
-END PGP SIGNATURE-

Re: Let's start salvaging packages!

[Tobias Frost]

Hallo everyone,

The yesteday uploaded Developer's Reference has now got a chapter
about "Package Salvaging". [1]

So, package salvaging is now implemented and ready to be used,
and whenever you find some package in need, you can now consider to
salvage it for the benefit of Debian and our users.

[1] 
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#package-salvaging

-- 
tobi



signature.asc
Description: PGP signature

Accepted developers-reference 3.4.21 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Sep 2018 23:21:04 +0200
Source: developers-reference
Binary: developers-reference developers-reference-de developers-reference-fr 
developers-reference-ja developers-reference-ru developers-reference-it
Architecture: source
Version: 3.4.21
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers 
Changed-By: Tobias Frost 
Description:
 developers-reference - guidelines and information for Debian developers
 developers-reference-de - guidelines and information for Debian developers, in 
German
 developers-reference-fr - guidelines and information for Debian developers, in 
French
 developers-reference-it - guidelines and information for Debian developers, in 
Italian
 developers-reference-ja - guidelines and information for Debian developers, in 
Japanese
 developers-reference-ru - guidelines and information for Debian developers, in 
Russian
Closes: 681833 879863 907535 907605 908867
Changes:
 developers-reference (3.4.21) unstable; urgency=medium
 .
   [ Tobias Frost ]
   * Team upload.
   * Fix Alioth references in README-contrib (Closes: #907605)
   * Add package-salvaging text (Closes: #681833, #907535).
   * Move shell snippet in §6.4 to common.ent.
   * Update German translation. (Closes: #908867)
 .
   [ Nicholas D Steeves ]
   * Change priority extra to optional in §6.7.7 (Closes: #879863).
Checksums-Sha1:
 ca6921080acc2685ee4ec30df92c9d5ed22f186f 2401 developers-reference_3.4.21.dsc
 fb8ffd8e407332c3c31d4e0933adbb9daf7a7065 662040 
developers-reference_3.4.21.tar.xz
 6e8913f5490eed60c21697d1eebb2958b60ab881 5658 
developers-reference_3.4.21_source.buildinfo
Checksums-Sha256:
 6aad631876340abb61cfefe64646614662e384f96683c165d7cccd1174edcc6f 2401 
developers-reference_3.4.21.dsc
 c088401811702a83a8bebc079fac58c47da9da8da3e7d6e96dc1e39e9fb9007e 662040 
developers-reference_3.4.21.tar.xz
 36049a5a27abfe2577fe69d4e5502024cc5ccf02d2c3572c40fc3bf8bf3dc013 5658 
developers-reference_3.4.21_source.buildinfo
Files:
 3147202685fd1b2d603081dfa117c80e 2401 doc optional 
developers-reference_3.4.21.dsc
 3c76053d94159add6f5dd6f86953d183 662040 doc optional 
developers-reference_3.4.21.tar.xz
 31b15b65df7fd490a2c3f8fb05788d29 5658 doc optional 
developers-reference_3.4.21_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAluqp/oACgkQkWT6HRe9
XTb0vhAAhJKZgYpSDbzM9V58FnRz+u2xoDAqJNa5OSlVZZF5JCmkz2ANI9CPTdRr
jJOR+OdMo88yQUFtm4VUyvjPyC6IzQ4X9W1pGmlJpT5fbyWAJIR/emmX3XTPgJjw
HF7OIJdA5qp8LQcGkWSjgEciPwWN6Et+d4ExGMIj9Qb7+EsVOguHxYBI5cIW7Igs
SmuWB1+O7MhRAxuF4JuVT20n/v7QK0jvSrsEnPQS36ltP2jvGFuYZhGXK45Oxwuw
KlNDXNbsxHzEfhf0WYp6eLNkMRTcyT9gIdHQS4qTy6zWximIYtV/AaCW1dAC0oMI
qBaurhFGlubPt25HjMR6vMoJASsKIcP8V5qzAscWtPtGUOJxqRDjJlLShpB8ZRUN
Za4fLgRKqrixmF6VbRxnVJgPaOOBsTCjILm07x6kMyNmzpYLmpMjYbOlocdQl7Fs
OvDU8X6ZiYH6Qph9jkAqIpXEM6dX39UxysMxoJ53dg5D7JIqL5cnGbNJ1cNvvLWJ
1K+3aTG9Ct1MGFwk2FBwvUAXrzjKC7HEK98mj4qim/89r++pedAKRESeGmDssR7L
jCSpkYz29LSBAZw4eSX4S0aypWozS4mi4i+waoUy/eDg7AyRj4MiIb3c4Z/lDQQO
JvVu5bzqbTXXjo5sNODMb4MRr34UmaFdYi7BILKktHrjKdWK5Ec=
=qQgj
-END PGP SIGNATURE-

Re: Let's start salvaging packages! -- disucssion phase closing soon.

[Tobias Frost]

Hi,

Merge-request for developers-reference is now available:
https://salsa.debian.org/debian/developers-reference/merge_requests/5

Kudos to all who helped me making this possible!

-- 
tobi



signature.asc
Description: PGP signature

Re: Let's start salvaging packages! -- disucssion phase closing soon.

[Tobias Frost]

On Mon, Sep 03, 2018 at 08:17:24AM -0300, David Bremner wrote:
> Tobias Frost  writes:
> 
> >
> > The split was actually thought to be a feature [1] :)
> > It was to make the process itself less normative about the actual
> > (concrete) figures/criterias, but still give safe figures to e.g
> > necomers they can rely on, and on the other side enable more advanced
> > people to reasonably deviate from it
> > (but with a strong documentation/justification requirement).
> >
> 
> OK, I understand the reasoning, but I hope we can improve the wording on
> both sides a bit so it's clear that the rule is "use your judgement, and
> if you're not sure about your judgement, refer to these numbers in the
> wiki, which represent a current concensus". Assuming my summary is
> correct, of course.

Yes, your summary is correct. I'm happy to make the wording a bit more
clearer and start by shamelessly stealing your sentence as a base for it
;-)

Cheers,
-- 
tobi



signature.asc
Description: PGP signature

Re: Let's start salvaging packages! -- disucssion phase closing soon.

[Tobias Frost]

Dear all,

so, I think we are now ready to proceed in the topic of the salaving
process...

The changes on the text on the etherpad and wiki were mostly only of
editorial nature, like spelling, grammar and wiki syntax fixes and
rewordings to make it less awkyard for native speakers. Again, thanks to
all the editors!

The only exception is, that I've added a clause to the wiki, that
changes to the conservative criteria needs discussion and consent with
debian-devel as discussion platform.

As a consequence that there was not too much changes to be incorporated,
we are quite in ahead of the anticipated schedule [1], because due to
that "adapting text to input received" is already done and as there were
no substantional changes, there'd be not much to review either.
So I propose that I start working on the patch against dev-ref in the
next few days, latest next weekend. (If you see that different and
object, let me know).

For the Wiki, you can see the changes here:
https://wiki.debian.org/PackageSalvaging?action=diff=19=11
For the etherpad, I paste the diff below.

[1] https://lists.debian.org/debian-devel/2018/08/msg00207.html

Cheers,
-- 
tobi

For your convenience, links to the texts:
https://pad.riseup.net/p/debian-salvaging-packages-keep
https://wiki.debian.org/PackageSalvaging

Diff of the etherpad (between revision 5826 and latest, which is 6161)
--- debian-salvaging-packages-keep-5826.txt 2018-09-02 18:22:11.581817797 
+0200
+++ debian-salvaging-packages-keep-6161.txt 2018-09-02 18:19:51.127549284 
+0200
@@ -1,5 +1,7 @@
 # Package Salvaging
 
+
+
 # Links:
 BoF: https://debconf18.debconf.org/talks/149-lets-start-salvaging-packages/
 Thread: https://lists.debian.org/debian-devel/2018/07/msg00453.html
@@ -56,71 +58,71 @@
 Package Salvaging
 
 
-Package salvaging is the process by which, one attempts to save a
-package that, while not officially orphaned, appear poorly maintained or
+Package salvaging is the process by which one attempts to save a
+package that, while not officially orphaned, appears poorly maintained or
 completely unmaintained.  This is a weaker and faster procedure than
-orphaning a package officially through powers of the MIA team.
-Salvaging a package is not meant to replace MIA handling, and in
-contrast to it, it does not comment about the overall activity of a
+orphaning a package officially through the powers of the MIA team.
+Salvaging a package is not meant to replace MIA handling, and differs
+in that it does not imply anything about the overall activity of a
 maintainer. Instead, it handles a package maintainership transition for
 a single package only, leaving any other package or Debian membership or
 upload rights (when applicable) untouched.  
 
  Note that the process is only intended for actively taking over
-maintainership. Do not do salvaging, when you do not intend to maintain
+maintainership. Do not do salvaging when you do not intend to maintain
 the package for a prolonged time. If you only want to fix certain
-things, but not taking over the package, you must use the NMU process,
-even if the package would be eligble for salvaing.  The NMU process is
+things, but not take over the package, you must use the NMU process,
+even if the package would be eligble for salvaging.  The NMU process is
 explained in  
 
  Another important thing to remember: It is not acceptable to
 hijack others' packages.  If followed, this salvaging process will help
-you to ensure that your endaveour is not a hijack, but a (legal)
-salvaging procedure and you can counter any allegations of hijack with a
-reference to this process.  This ensurance should especially help new
+you to ensure that your endeavor is not a hijack but a (legal)
+salvaging procedure, and you can counter any allegations of hijacking with a
+reference to this process.  This should especially help new
 maintainers to Debian to have confidence taking over packages by
 salvaging. 
 
  The process is split into two phases: In the first phase you
 determine whether the package in question is
-eligble for the salvaging process.  Only when the
-eligbiliy has been determined, you can enter the second phase, the
-actual package salvalging. 
+eligible for the salvaging process.  Only when the
+eligibiliy has been determined can you enter the second phase, the
+actual package salvaging. 
 
- For an addtional informations, rationales and FAQs on package
+ For additional information, rationales and FAQs on package
 salvaging, please visit the Salvaging Packages page on the Debian
 wiki. 
 
 
-When a package is eligble for package salvaging
+When a package is eligible for package salvaging
 
 
-A package becomes elible for salvaging when it has been neglected by the
+A package becomes eligible for salvaging when it has been neglected by the
 current maintainer. To determine that a package has really been
-negelected by the maintainer, the following coarse indicators might give
+neglected by the maintainer, the 

Re: Let's start salvaging packages! -- draft text now available

[Tobias Frost]

On Fri, Aug 31, 2018 at 03:23:53PM +0100, Jonathan Dowland wrote:
> On Sun, Aug 19, 2018 at 06:06:47PM +0200, Tobias Frost wrote:
> > [2] https://wiki.debian.org/PackageSalvaging
> 
> Please consider adding a content license to this page. See the bottom of
> [1] for an example of how to do this. It would make moving stuff to/from
> this page to other things like the dev-ref easier, and opens up the
> possibility of this material being incorporated into a package/the
> archive one day. It will be very hard to do once there are multiple
> authors to the page.

Done.

I've used GPL2+ on it, the same license as dev-ref.

At the moment I've put only my name on it, anyone thinking they
should/want be added as well, please just do so yourself!

> [1] https://wiki.debian.org/DebianMaintainer [2]
> [2] Yes this approach really sucks, but it's the best we have right now.
>I've been wanting to pick back up sorting out wiki content licensing
>after a long haitus but haven't had the time or spoons yet.
> 
> 
> -- 
> Jonathan Dowland
> 


signature.asc
Description: PGP signature

Re: Let's start salvaging packages! -- disucssion phase closing soon.

[Tobias Frost]

Hi David,

On Thu, Aug 30, 2018 at 10:43:01PM -0300, David Bremner wrote:
> Tobias Frost  writes:
> 
> > Hallo everyone,
> >
> > This is a gentle reminder regarding the Salvaging Process discussion!
> >
> > For all of those, who did not yet have read the proposal, but still want
> > to participate in the discussion, please step forward now, as I plan to
> > start to work on finalizing the text after Saturday, September 1st.
> 
> Hi Tobi;
> 
> I'm not sure it's a good idea to have the definitive criteria for
> salvaging in the wiki. I guess partly I'm not too comfortable with the
> lack of definition of an process to change those criteria in the
> wiki. It's also strange to me to have the salvaging description split
> across two locations.  I'd suggest that whatever the "real" conditions
> are (even if the concensus is to use a less formal set of conditions
> like those given here), that they go in the same document as the
> procedure they enable.

The split was actually thought to be a feature [1] :)
It was to make the process itself less normative about the actual
(concrete) figures/criterias, but still give safe figures to e.g
necomers they can rely on, and on the other side enable more advanced
people to reasonably deviate from it
(but with a strong documentation/justification requirement).

Yes, you're right, there should be a process documented how to change
this text, e.g the process should include an manadatory discussion on
e.g -devel; Beside that our Wiki records every change and who did the
change, so we get also an audit trail for free. (I've just added some
language to the Wiki for it now)

Not sure if that would adress your concerns well enough; Let me CC
enrico to get also his thoughts.

-- 
tobi

[1] The idea picks up this quote from the BoF summary:
  Gregor's mail [1], with input from enrico: Vagueness could be a good
  thing, and the worst that can happen if someone does a bad call on
  salvaging is that an ITS bug gets opened and closed, and something
  that was unclear gets documented.  The number of months and so on that
  are currently in the proposal are still useful to empower a new
  maintainer to make the call without fear, and could be put as an
  example reference in the wiki, rather than in the dev-ref.



signature.asc
Description: PGP signature

Re: Let's start salvaging packages! -- draft text now available

[Tobias Frost]

Subject: developers-reference: Announcement for adding "Package Salvaging" 
process to dev-ref
Source: developers-reference
Severity: normal

Dear dev-ref maintainers,

as you've probably saw on -dev, I'm currently working to implement the
Package Salvaging process. The discussion is still ongoing but planed to
be closed on Saturday, September 1st. You can find the discussion here:

The thread starts at:
https://lists.debian.org/debian-devel/2018/07/msg00453.html,

You can find the proposal and call for discussion here:
https://lists.debian.org/debian-devel/2018/08/msg00277.html

I'm filing this bug report to make you aware of it, along with the
announcement that I will start finalizing the text on the weekend to be
able to provide a merge request shortly afterwards. My original timeline
was proposed in this message [1] , but I might not need the "adaption
period", as the input received was only on typos and grammar, not asking
for changes with regards to the process, so atm I think I ll be able to
come up with the patch to final discussion on Sunday, if that does not
change. (so this would accelerate the timeline by one week)

[1] https://lists.debian.org/debian-devel/2018/08/msg00207.html

Cheers,
-- 
tobi



signature.asc
Description: PGP signature

Re: Let's start salvaging packages! -- disucssion phase closing soon.

[Tobias Frost]

Hallo everyone,

This is a gentle reminder regarding the Salvaging Process discussion!

For all of those, who did not yet have read the proposal, but still want
to participate in the discussion, please step forward now, as I plan to
start to work on finalizing the text after Saturday, September 1st.

Many have already edited and tweaked the proposed text to correct typos
and weird (for non native speakers) formulations, which is a very good
thing. A BIG THANKS for that!

Cheers,

--
tobi
 
On Tue, Aug 21, 2018 at 03:05:57PM +0200, Tobias Frost wrote:
> Dear fellow Debinites,
>
> many of you know already that there is currently a discussion about
> establishing a package salvaging process within Debian.  The discussion
> is taking place at debian-devel, but I'd like make people aware which
> are not subscribed to -devel.
>
> For those who did not knew about it, the thread starts at:
> https://lists.debian.org/debian-devel/2018/07/msg00453.html,
>
> You can find the proposal and call for discussion here:
> https://lists.debian.org/debian-devel/2018/08/msg00277.html
>
> Pleases use the -devel thread for the discussion!
>
> Thanks for your attention!
> --
> tobi



signature.asc
Description: PGP signature

Accepted log4cxx 0.10.0-15 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Aug 2018 16:43:21 +0200
Source: log4cxx
Binary: liblog4cxx-dev liblog4cxx10v5 liblog4cxx-doc
Architecture: source
Version: 0.10.0-15
Distribution: sid
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 liblog4cxx-dev - Logging library for C++ (development files)
 liblog4cxx-doc - Documentation for log4cxx
 liblog4cxx10v5 - Logging library for C++
Closes: 901615
Changes:
 log4cxx (0.10.0-15) sid; urgency=medium
 .
   * Make the build reproducible, thanks lamby for the patch. (Closes: #901615)
   * Bump S-V to 4.2.1 -- no changes required
Checksums-Sha1:
 ba201726ba04dea1869f8135778112ab1c276e01 2101 log4cxx_0.10.0-15.dsc
 5242191e3e26e09cd40ce30a817b1046858464fc 15028 log4cxx_0.10.0-15.debian.tar.xz
 ba8fe03dc9496053abe072dbad238da9ffe2c802 5551 
log4cxx_0.10.0-15_source.buildinfo
Checksums-Sha256:
 68773229acef3fc0e02dee65ae881489be6c26d7c62a34c07904b9bf933c0c69 2101 
log4cxx_0.10.0-15.dsc
 22ebc3e80c3eab56b400c72ccd9916fa290a22efbe94ed4bb518d4ee4c027f62 15028 
log4cxx_0.10.0-15.debian.tar.xz
 fcd2393f0c9e772bf0fbf580675fc34294bd3f9edcf96813ac5feeec80455ed6 5551 
log4cxx_0.10.0-15_source.buildinfo
Files:
 40f81072fd082fe5b2c131d15a3dca47 2101 devel optional log4cxx_0.10.0-15.dsc
 a2727d5e3adaeb1823e86d6357fe3629 15028 devel optional 
log4cxx_0.10.0-15.debian.tar.xz
 60204caaa7a353d66b57ab4c4bd91d39 5551 devel optional 
log4cxx_0.10.0-15_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAluCvMQACgkQkWT6HRe9
XTa3QRAAsMX0WuxLJSqQcuiL84GjQ333LguUVDFieuw60asV2dyvU5GGoeXVb4qI
3CBd9f5ezYiD25/1U0ICQGcNAu1EKGJ4/y5/YNv5rL6a6aaPjTf8tf1ojg+HAddN
Sz+XutvKSqP0VxjCyXUHCqT7KQ2BDlwA+xxtP6BNRrgqL/raEHZQl/tqcSC02VBm
CTVCwtYmnRY/J6T7dzko65H7lmeD3IZulbYgtJxXc4h5BnvOaUmXYpuyfvAk+xWn
PJaB4CPpmbfsayZ3xr8NDmBIrGIDCdwypz4Cw3GHJh/W7mZVFlTk5sxxI4trf9So
9sZ6mQkmQ2KnRIrv1I9kZPXBv07nz7f2bxkxs9joYI8AIZVPI7Oeiyq08Y4AHOKV
AT9PMrAQFKAcfP70dc3dfo/G+IIEThL4CDRrnVn+yw7m9Nu3tsKfCWI2Rn0eogup
uLUK3RXTjzUfJnNLb6Jhi/f8AQeJhkMwytx1Z7jRidN3Le0awLIL/mMOw1oAjXNq
zf4IITpxVDHC39si4gO8IvBMDcij9qfZY0Xu2YF66/HAEXwaczFXks1OCQMdvbBX
cxvECh8TnEh0JPhwRvAKgaSu7BRgII3dFbMEdPVIO5cc3LOr5UhL5oN9M2klXsWx
grHSbyc0TYCRuez2qpB9FgO2CRgPfF4A256O2JxbTad6efrfiyQ=
=nXU6
-END PGP SIGNATURE-

Accepted pdfsandwich 0.1.7-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Aug 2018 21:20:30 +0200
Source: pdfsandwich
Binary: pdfsandwich
Architecture: source
Version: 0.1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 pdfsandwich - Tool to generate "sandwich" OCR pdf files
Changes:
 pdfsandwich (0.1.7-1) unstable; urgency=medium
 .
   * New upstream release.
 - remove 02-fix-903026.patch -- implemented by upstream in new version
 - Rework 03-spelling-fixes.patch -- applied upstream partially.
   * Bump S-V to 4.2.0 (added Requires-Root to d/control).
Checksums-Sha1:
 f06632ecb9d95b30946be7fafc9a7ee75bc35a6c 1879 pdfsandwich_0.1.7-1.dsc
 926c047db0c3c146fb4de7997a0cace776955b64 17461 pdfsandwich_0.1.7.orig.tar.bz2
 3e9668ac1b6b16b1331d13e5781ad74933c99e6a 3824 pdfsandwich_0.1.7-1.debian.tar.xz
 7f4b19097199201eac08f37fcfcc167082134e96 5735 
pdfsandwich_0.1.7-1_source.buildinfo
Checksums-Sha256:
 879960c8a06e622bd51102ba00f4bfa4261da28ffb71c00239209cfa76676796 1879 
pdfsandwich_0.1.7-1.dsc
 9795ffea84b9b6b501f38d49a4620cf0469ddf15aac31bac6dbdc9ec1716fa39 17461 
pdfsandwich_0.1.7.orig.tar.bz2
 e5cbcd36e8dea6b76e3c59263b6c37bf38f9495f4a7527aa0bca76ee96c1a22b 3824 
pdfsandwich_0.1.7-1.debian.tar.xz
 615fcb369c67f8206990b2201d910af6c92cb9bc82a01482a9084141edd1c4da 5735 
pdfsandwich_0.1.7-1_source.buildinfo
Files:
 c78638eae6d01dea8e2dc15893b35bd4 1879 text optional pdfsandwich_0.1.7-1.dsc
 60e617cc398251cec5f42b870b1fccb4 17461 text optional 
pdfsandwich_0.1.7.orig.tar.bz2
 56d76cc3a44f9c4b5a3436996edf85f4 3824 text optional 
pdfsandwich_0.1.7-1.debian.tar.xz
 77a9e4189c47b5059e342e0d742f373b 5735 text optional 
pdfsandwich_0.1.7-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlt/CWgACgkQkWT6HRe9
XTa5ng//RUfgO20nCPrKGCLqBVXLXTXIcDmkYVZjKj7OYNHT6HLfX4fsjZDDEGlv
vD027W7IOert5xIEOst64BJToSP7IpOD9JDBCl0m74uGQTInjYToEd9NvLdSoNyJ
wMuaOMsYQ8Pw1IpckocB3DaNmVzvKUzK3ML9uIuTcAQ3P9AriKqMvu832N2W3uNQ
9aFspQrbDBuGOOu6lRLCuLSHOnQ3IG3DV9G0r4moMfKcWSC117GVtVQ8WKv0Ko02
kwZxtqou1Xn5wy3UJXCqbbIYdzVsbeNEoXfSH3n65RaqTO+bKM8dFTeHi3lEz1PB
Jr27nF55ESiKneuc8z6TX1oXsULY8lXR3BV995UH6a9xMvbFOsi0nBu1SayWcMup
HKeuL0nuGnSx3o6Qjzkn+Eqh+9i4fKrwTVo2ffyd0hGOQN4EsRYep6RQX7MFHluj
9GBtVWjztIMGWMGiAKrV6tM2XX6mwSM7dPw30gnNxfzhDX7hVgAk91o1ePwTWSAM
7aw8NegALiihlSJ3WdPTwWoUkk4B/r/y0YtIJxsODllRaVywXRjqA41tlqiRBz4C
Mv8R5R+nCxAlFBChYAqIjA1WHCuoxEqJRCyC4ugBQrqtBM1JgB8pXWcBVR1pKecQ
w29KvA5IR4BHN3z5fVaIi4h3c+vyGYppoM2eYncRFYzbi9gJhK8=
=69s8
-END PGP SIGNATURE-

Accepted cppdb 0.3.1+dfsg-8 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 23 Aug 2018 19:55:38 +0200
Source: cppdb
Binary: libcppdb-dev libcppdb0 libcppdb-mysql0 libcppdb-sqlite3-0 
libcppdb-postgresql0 libcppdb-odbc0
Architecture: source
Version: 0.3.1+dfsg-8
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 libcppdb-dev - SQL Connectivity Library (development files)
 libcppdb-mysql0 - SQL Connectivity Library (MySQL backend)
 libcppdb-odbc0 - SQL Connectivity Library (odbc backend)
 libcppdb-postgresql0 - SQL Connectivity Library (PostgreSQL backend)
 libcppdb-sqlite3-0 - SQL Connectivity Library (sqlite3 backend)
 libcppdb0  - SQL Connectivity Library (core library)
Closes: 906456
Changes:
 cppdb (0.3.1+dfsg-8) unstable; urgency=medium
 .
   * Drop the symbols files again. It is just not sustainable.
 (Closes: #906456)
   * Adding lintian overrides for the missing symbol files.
   * Bump S-V to 4.2.0 (adding Rules-Requires-Root)
Checksums-Sha1:
 41c5b37214b061ce8e34288f3af72979850f1bfc 2234 cppdb_0.3.1+dfsg-8.dsc
 667adf8efb0cc4bf634ed3dd3ef064c06f59032e 5032 cppdb_0.3.1+dfsg-8.debian.tar.xz
 8a9a8f3dcd3588aa1abc2b7b5a6f34a1224c0f6c 7028 
cppdb_0.3.1+dfsg-8_source.buildinfo
Checksums-Sha256:
 34bd2d6874917192af150d9e56ef11fd0d1dee1d851ea747d7384c4c67b46c6e 2234 
cppdb_0.3.1+dfsg-8.dsc
 e98362b71ec8a912fff6dfc046724e7682f396d6d26a7ac56dc49310356b0a80 5032 
cppdb_0.3.1+dfsg-8.debian.tar.xz
 1e07e819b584688cbe381288d800916f46274b0412ee349c1d418a4acf8510b7 7028 
cppdb_0.3.1+dfsg-8_source.buildinfo
Files:
 6549b53b0ff307fe5d0d158ff5a7135d 2234 libs optional cppdb_0.3.1+dfsg-8.dsc
 a04e888251b6304fc86c7dd95d9b34f6 5032 libs optional 
cppdb_0.3.1+dfsg-8.debian.tar.xz
 ca4508093b08a3927e397801427ff542 7028 libs optional 
cppdb_0.3.1+dfsg-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlt+90oACgkQkWT6HRe9
XTb/fw/7BVZ/+I0MR8wjZEqsBU9zh7j4Ub78R6V2SYh0Gk3qSaBmtWe7bBm1/F53
A0dT3sNgFO0Lnv1aa/heqvJuuMfOkq6VdTpTyPEwbU0y6oblOPsMkhloF7UFVrYM
ibpP1pni72WkYnKFPu9mk8740s5ap0EfraE2PeCni4mBnkoP9vdv2JKLzBJ/UNBZ
uSbfyv2e/w83kplgOsgB4FTfFAVMslwpRWsa7j4x01oEo3MAaAqlWOEnb7d9SODG
2eOtAzWtK1b6zpkERnMv3Y43/HglH3wogGsLbtQ2BHSFaQeHO3euL8HFrKbZ8vhX
K4eJuarA+fDzK69/CLMCFeiTcBCI/XZROfIGQlHn8rmHuGOXrSia0dORNmgCaBE/
nU94wTXYyVQW9KRfkVQOd+lEElZjj42iJsYhgLnSVCubivbJOd09R24z+T+MQXcC
iQKvdc4NQMS9UwuxmfIHZCUsQHRDTN8kRfRhvnQU/3qYlGfwbvpF/kLwtyZHCSwA
j9ISJAQkCUQrQyq3eTWhrFNyJNNXgQGDSvIHMycr3nLmpiiwai+H6kE1pVwLl3R2
DS338QXTpfiVPtLVYIiyso8nZxj2SfWiIqWkYDGpfI4/dd5HgoEM8NcAF346YYa0
KOTJRw+dXl6NcIUpGyJ7Wcl3hgla9YYsJh4FYHRpbthSL1WXaC4=
=9ESv
-END PGP SIGNATURE-

Let's start salvaging packages! -- draft text now available

[Tobias Frost]

Dear fellow Debinites,

many of you know already that there is currently a discussion about
establishing a package salvaging process within Debian.  The discussion
is taking place at debian-devel, but I'd like make people aware which
are not subscribed to -devel.

For those how did not knew about it, the thread starts at:
https://lists.debian.org/debian-devel/2018/07/msg00453.html,

The forwarded mail is the call for discussion and sent to
-devel last Sunday: (I've updated the Wiki text as some people already
contributed with some language fixes to the text)
You can find the original mail here:
https://lists.debian.org/debian-devel/2018/08/msg00277.html

Note that I've set Reply-To to -devel to avoid having too much noise on
-announce. Please reply to -devel, (I hope I have set the email headers
correctly ;-))

Thanks for your attention!
-- 
tobi
- Forwarded message from Tobias Frost  -

Date: Sun, 19 Aug 2018 18:06:47 +0200
From: Tobias Frost 
To: debian-devel@lists.debian.org
Subject: Let's start salvaging packages! -- draft text now available
User-Agent: Mutt/1.10.1 (2018-07-13)

Dear -devel,

as announced earlier, I have together with worked on the text for the
salvaging process. You can find the texts here: Titanpad [1] for dev-ref
and the accompanying Wikipage [2]. Credits to Pierre-Elliott Bécue, as
he wrote the first draft and thereby helped me a lot.

For the timeline, as earlier communicated I think we should discuss this
until Sepember 1st and then I will start incooporating received intput
to have a final text available soon.

[1] https://pad.riseup.net/p/debian-salvaging-packages-keep
[2] https://wiki.debian.org/PackageSalvaging

For your convenience (and for easier replies) here is the full text
for bith parts (the dev-ref part and the wiki raw text).
(The dev-ref needs modification in 5.9.5, therefore this is provided as
a patch.)

Cheers,
-- 
tobi

Patch for section 5.9.5: ("Adopting a package")
---
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -1471,15 +1471,20 @@ packages listed in the WNPP, please take a look at the 
aforementioned page for
 information and procedures.
 
 
-It is not OK to simply take over a package that you feel is neglected — that
-would be package hijacking.  You can, of course, contact the current maintainer
-and ask them if you may take over the package.  If you have reason to believe a
-maintainer has gone AWOL (absent without leave), see .
+It is not OK to simply take over a package without assent
+of the current maintainer — that would be package hijacking.
+You can, of course, contact the current maintainer and ask them for
+permission to you take over the package.
 
 
-Generally, you may not take over the package without the assent of the current
-maintainer.  Even if they ignore you, that is still not grounds to take over a
-package.  Complaints about maintainers should be brought up on the developers'
+However, when a package has been neglected by the maintainer, you might
+be able to take over package maintainership by following the package
+salvaging process as described in .
+If you have reason to believe a maintainer is no longer active at all,
+see .
+
+
+Complaints about maintainers should be brought up on the developers'
 mailing list.  If the discussion doesn't end with a positive conclusion, and
 the issue is of a technical nature, consider bringing it to the attention of
 the technical committee (see the 
Package Salvaging


Package salvaging is the process by which, one attempts to save a
package that, while not officially orphaned, appear poorly maintained or
completely unmaintained.  This is a weaker and faster procedure than
orphaning a package officially through powers of the MIA team.
Salvaging a package is not meant to replace MIA handling, and in
contrast to it, it does not comment about the overall activity of a
maintainer. Instead, it handles a package maintainership transition for
a single package only, leaving any other package or Debian membership or
upload rights (when applicable) untouched.  

 Note that the process is only intended for actively taking over
maintainership. Do not do salvaging, when you do not intend to maintain
the package for a prolonged time. If you only want to fix certain
things, but not taking over the package, you must use the NMU process,
even if the package would be eligble for salvaing.  The NMU process is
explained in  

 Another important thing to remember: It is not acceptable to
hijack others' packages.  If followed, this salvaging process will help
you to ensure that your endaveour is not a hijack, but a (legal)
salvaging procedure and you can counter any allegations of hijack with a
reference to this process.  This ensurance should especially help new
maintainers to Debian to have confidence taking over packages by
salvaging. 

 The process is split into two phases: In the first phase you
determine whether the package in question is
eligble for the

Accepted rbdoom3bfg 1.2.0+dfsg~git20180605-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 20 Aug 2018 19:44:17 +0200
Source: rbdoom3bfg
Binary: rbdoom3bfg
Architecture: source
Version: 1.2.0+dfsg~git20180605-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 rbdoom3bfg - Doom3 BFG edition game engine
Changes:
 rbdoom3bfg (1.2.0+dfsg~git20180605-1) unstable; urgency=medium
 .
   * Imported new upstream git snapshot.
   * Change to version 4 watch file to directly track the upstream git repo.
 This also makes the get-orig-source target in d/rules obsolete.
   * Prepare the watchfile for version 1.2 already, as upstream bumped version
 to 1.2 (but not yet officially released)
   * Add patch for the FTBFS with gcc 8.1 (Closes: ##906558)
Checksums-Sha1:
 7a6f080c10b4a8e862915c871d95876e4bb3c120 2216 
rbdoom3bfg_1.2.0+dfsg~git20180605-1.dsc
 38b959a859cf69030211b445b2fc668751bb4e83 2418544 
rbdoom3bfg_1.2.0+dfsg~git20180605.orig.tar.xz
 dd6c834f64780f51e1836bf10be02bfe0bf343e5 19740 
rbdoom3bfg_1.2.0+dfsg~git20180605-1.debian.tar.xz
 33efd5a133dc061c8f05e925c5adae2b4c2a2be7 13593 
rbdoom3bfg_1.2.0+dfsg~git20180605-1_source.buildinfo
Checksums-Sha256:
 77d166a3f6b1dc2356ae872be2a806271fc6251418f8eec8045cd21c72c41311 2216 
rbdoom3bfg_1.2.0+dfsg~git20180605-1.dsc
 77d11a79382c9f7fc18c2361ab76e6a8047ae71a6e81add631561978fea8483a 2418544 
rbdoom3bfg_1.2.0+dfsg~git20180605.orig.tar.xz
 3fef6a4758ebbd0501c27a856fb94118572f44683ff31241a0d2f1861bb851c7 19740 
rbdoom3bfg_1.2.0+dfsg~git20180605-1.debian.tar.xz
 26ef1133821564a8cc6612f9de87df0b753fedc9dd553181bd9fc442ac9992ac 13593 
rbdoom3bfg_1.2.0+dfsg~git20180605-1_source.buildinfo
Files:
 aa5de4e28072073d0d7e9558500df354 2216 games optional 
rbdoom3bfg_1.2.0+dfsg~git20180605-1.dsc
 12fe169961238ed3d6c184f22c36637f 2418544 games optional 
rbdoom3bfg_1.2.0+dfsg~git20180605.orig.tar.xz
 433c4c94d16b7487f05bdbdb9259e08c 19740 games optional 
rbdoom3bfg_1.2.0+dfsg~git20180605-1.debian.tar.xz
 ef3b1c4b82f74822bb253a46f021fa42 13593 games optional 
rbdoom3bfg_1.2.0+dfsg~git20180605-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlt6/noACgkQkWT6HRe9
XTanYhAA0Yu8SreLLWkkfBrQBm7Q0PRpZjFZ3Wx4alG3fzsdr/mV5T8csZEGG2Q0
tHIf6fqglUZqhkra548DuzVbtXuxnFuYvcqYxp9x/JzosmU2pLKvkv0aoPdlQuUo
eMxbea+S5j8+4ACtVQ8KRn0dhHAnTi80ycnaC6yRgyxLZ+zzwacchWiR5WLObfqg
b1sEzHdNNtzEGpcYMcvW6shJiAx8kdsZTNZAVaph6cjQ3QgBrAuyMXXjVPrTn9lm
tOSgnonAql4LPikOTGVwWgCzdG74bvALPgms/bUKicA8zAAEQx713jFSQ+1TwmXl
U472fsK900DQrSVN/59/IyNiJBdMp06/+eV6zx36/zgUbrgfJM+LPKxFWtVUsd/l
XoAe3F43KAqH67Qz4HgkdIdQ0eBy8znmnpEIiLatymR03OtItxHxf6rBG68Ed4UY
Vj8gqnhlY8GVEmw6lkSJW2zNZtnAXqMrpF/OYfqB8I2YSGWoU3Fx6MA/OpaU5lHU
HNneZDdF7AFpokGqwL8BocusP6h85cWSdAoATASWcmJgEegLzqden5aOqOSgX0Cs
MeEyZmNSx0aVCYEWzYIOqeHlJvNfHXesUZHSDOoL0DMznPQfJHCIxFGkuHBAtjnd
ENcukLw1f8UxAUt+2Q8Tm/blWLoVy3OLfA4O/WGr6SZPkX0kHDA=
=+eQG
-END PGP SIGNATURE-

Let's start salvaging packages! -- draft text now available

[Tobias Frost]

Dear -devel,

as announced earlier, I have together with worked on the text for the
salvaging process. You can find the texts here: Titanpad [1] for dev-ref
and the accompanying Wikipage [2]. Credits to Pierre-Elliott Bécue, as
he wrote the first draft and thereby helped me a lot.

For the timeline, as earlier communicated I think we should discuss this
until Sepember 1st and then I will start incooporating received intput
to have a final text available soon.

[1] https://pad.riseup.net/p/debian-salvaging-packages-keep
[2] https://wiki.debian.org/PackageSalvaging

For your convenience (and for easier replies) here is the full text
for bith parts (the dev-ref part and the wiki raw text).
(The dev-ref needs modification in 5.9.5, therefore this is provided as
a patch.)

Cheers,
--
tobi

Patch for section 5.9.5: ("Adopting a package")
---
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -1471,15 +1471,20 @@ packages listed in the WNPP, please take a look at the 
aforementioned page for
 information and procedures.
 
 
-It is not OK to simply take over a package that you feel is neglected — that
-would be package hijacking.  You can, of course, contact the current maintainer
-and ask them if you may take over the package.  If you have reason to believe a
-maintainer has gone AWOL (absent without leave), see .
+It is not OK to simply take over a package without assent
+of the current maintainer — that would be package hijacking.
+You can, of course, contact the current maintainer and ask them for
+permission to you take over the package.
 
 
-Generally, you may not take over the package without the assent of the current
-maintainer.  Even if they ignore you, that is still not grounds to take over a
-package.  Complaints about maintainers should be brought up on the developers'
+However, when a package has been neglected by the maintainer, you might
+be able to take over package maintainership by following the package
+salvaging process as described in .
+If you have reason to believe a maintainer is no longer active at all,
+see .
+
+
+Complaints about maintainers should be brought up on the developers'
 mailing list.  If the discussion doesn't end with a positive conclusion, and
 the issue is of a technical nature, consider bringing it to the attention of
 the technical committee (see the 
Package Salvaging


Package salvaging is the process by which, one attempts to save a
package that, while not officially orphaned, appear poorly maintained or
completely unmaintained.  This is a weaker and faster procedure than
orphaning a package officially through powers of the MIA team.
Salvaging a package is not meant to replace MIA handling, and in
contrast to it, it does not comment about the overall activity of a
maintainer. Instead, it handles a package maintainership transition for
a single package only, leaving any other package or Debian membership or
upload rights (when applicable) untouched.  

 Note that the process is only intended for actively taking over
maintainership. Do not do salvaging, when you do not intend to maintain
the package for a prolonged time. If you only want to fix certain
things, but not taking over the package, you must use the NMU process,
even if the package would be eligble for salvaing.  The NMU process is
explained in  

 Another important thing to remember: It is not acceptable to
hijack others' packages.  If followed, this salvaging process will help
you to ensure that your endaveour is not a hijack, but a (legal)
salvaging procedure and you can counter any allegations of hijack with a
reference to this process.  This ensurance should especially help new
maintainers to Debian to have confidence taking over packages by
salvaging. 

 The process is split into two phases: In the first phase you
determine whether the package in question is
eligble for the salvaging process.  Only when the
eligbiliy has been determined, you can enter the second phase, the
actual package salvalging. 

 For an addtional informations, rationales and FAQs on package
salvaging, please visit the Salvaging Packages page on the Debian
wiki. 


When a package is eligble for package salvaging


A package becomes elible for salvaging when it has been neglected by the
current maintainer. To determine that a package has really been
negelected by the maintainer, the following coarse indicators might give
an idea what to look for: 


   NMUs, especially if there have been more than one NMU
in a row. 
   Bugs filed against the package do not have answers
from the maintainer. 
   Upstream has released several versions, but despite
a bug entry exists asking for it, it has not been packaged

   There are QA issues with the package
   



As said, the above list is only a very coarse. The wiki page Salvaging Packages expands on
eligbility criterias for package salvaging, you are recommended follow
them to determine eligbility.  Though you are allowed to deviate from
the guidlines 

Re: Let's start salvaging packages! -- let's start working on the text.

[Tobias Frost]

On Mon, Aug 13, 2018 at 07:39:24AM +0100, Chris Lamb wrote:
> Dear Tobias,
> 
> > [1] https://pad.riseup.net/p/debian-salvaging-packages-keep
> 
> Thanks for moving forward with your proposal. I'll have a poke at the
> Etherpad in the upcoming days or so.
> 
> Whilst you outline a plan of sorts, do you have any rough timetable
> in your head that you would like to share? That might help focus or
> motivate deeper discussion to some degree.

Yes, a roughly thouht about having it ready to fly in a month or so.
Let me propose are more concrete timeline, (in the hope that no
free-time-eating-monster shows up in the meantime:)

- Draft on the etherpad: Sunday, Aug 19th
- Discussion period on this draft: 2 weeks, until Sep 1st.
- Adapting texts to the input received: until Sep 9th
- Review on -devel until Sep 16th
- Proposing patch to dev-ref: until Oct 1st.

- In parallel:
  - creating patches/texts for dev-ref.
  - creating a wiki page for the details.

> > The discussion can and should of course continue, especially as it is
> > vacation time atm.
> 
> Combined with post-Debconf tiredness/blues…

True. But luckily next DebCamp is only 11 months away... ;-)

--
tobi 

> 
> Best wishes,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-


signature.asc
Description: PGP signature

Re: Let's start salvaging packages! -- let's start working on the text.

[Tobias Frost]

Dear -devel,

seems so as the discussion is more quiet than I've anticipated...
So as an optimist, I'm assuming this is because the proposal has
kind of rough consensus, so I will plan now for the next steps.

The discussion can and should of course continue, especially as it is
vacation time atm.

So the next steps:
 - Editing Platform: To enable collaboration on the text (I have been
   approached by people wanting to help writing it) I've set up a
   etherpad at [1].
 - As I'm in favour of enrico's idea to split the text into two parts:
   1) description of the salvaging process for dev-ref
   2) carving-out all the details to a wiki-page.
 - I try to reserve some time the next days for a very rough outline of
   the text, to provide further sparks to ignite the discussion.

[1] https://pad.riseup.net/p/debian-salvaging-packages-keep

--
tobi


signature.asc
Description: PGP signature

Accepted gnome-shell-extension-autohidetopbar 20180511-2 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Aug 2018 17:50:00 +0200
Source: gnome-shell-extension-autohidetopbar
Binary: gnome-shell-extension-autohidetopbar
Architecture: source
Version: 20180511-2
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gnome-shell-extension-autohidetopbar - GNOME shell automatic topbar hider
Closes: 905111
Changes:
 gnome-shell-extension-autohidetopbar (20180511-2) unstable; urgency=medium
 .
   * d/p/Adapt-to-removal-of-MetaScreen-in-mutter-3.29.x.patch:
 If running under GNOME Shell 3.29.x, use display, layout manager or
 workspace manager (as appropriate) to replace uses of MetaScreen,
 which was removed in mutter 3.29.x. Thanks for Simon McVittie for the
 patch (Closes: #905111).
   * Bump S-V to 4.2.0, add Rules-Requires-Root: no to d/control
Checksums-Sha1:
 e117f9b9a5fdcf354df8f7441737adc0d08e5370 2171 
gnome-shell-extension-autohidetopbar_20180511-2.dsc
 06707712b6d04168a53acd59cf71a1e95e933cc0 4916 
gnome-shell-extension-autohidetopbar_20180511-2.debian.tar.xz
 e98de5581584f384841e7af90f4bc8e8a220d4f5 5715 
gnome-shell-extension-autohidetopbar_20180511-2_source.buildinfo
Checksums-Sha256:
 ed2add19f896aa24feba7a5f4747446ffd65559fb21c445c6a089012a13dbab3 2171 
gnome-shell-extension-autohidetopbar_20180511-2.dsc
 277d81e2456c3b937edfe8e2d354c40a0cf05048868e7be44a0c49919bff0eb8 4916 
gnome-shell-extension-autohidetopbar_20180511-2.debian.tar.xz
 2292b65fe104035e9f46bea1f395ad256d6d08277946335e1f56877b7758a2ea 5715 
gnome-shell-extension-autohidetopbar_20180511-2_source.buildinfo
Files:
 989c46c4ce4cb931887d1b8074ef06b5 2171 gnome optional 
gnome-shell-extension-autohidetopbar_20180511-2.dsc
 9a61eac46cf3d4474b8ef48215821a45 4916 gnome optional 
gnome-shell-extension-autohidetopbar_20180511-2.debian.tar.xz
 c8aafc7c8e823f43f645d34879ad71c1 5715 gnome optional 
gnome-shell-extension-autohidetopbar_20180511-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAltvB6EACgkQkWT6HRe9
XTaC1hAA2GW1qefgzvIEltCa8rXWHCtBwhldauL6I9Zy/FpbkxFO/rUXVEz8dIDI
BgQIe/rRQb6DKoDiLvNOywvYNx3d2DU3E2Sbsq9tBdHllrPTDogpGNpj4AghfcPI
WPnb2X8FFjCpTLz7QU3tfxXG3+PVuHnf62ndJl0R8kXIQ3nbg4A/CKi5rbQ/MySp
fcBQegrQph4fZxYjeXPJyUvMUiChY4qToIEJX6hv+6N2bay5hwawzqOE28NuvhGp
iY0JIEx/sqjh8Irlood46Z3v68FWXNhyQzkKH2p/jB5AYmGpu94aP4LRfJPz3Ksy
VTYiQVNHDO9C/2iYrPQESKcpYvWh/Q2DfQjCIJNB9I9Nv69AbYF0/j7PkL+lTN8v
QKx8qFy/S8oEoz0HgOW0TIGHUxWmrrdFgV8l/OF8CfWtI7aTtC1P/A7+WYj+spiq
WGm61SXLPYUfyt5RLVl2Oazo+CpurVMguH4mC9ZKoViWJTP1xJHImLNAvb9odWiY
iQSvI14qzyMh5WLyEho6ckZabqXEvKhOll/BJzmIte/iX+vMGRbTrcmfMu+l+d6N
fi8GpQbRPFl7xf6V8h9OygNiLPPS7lqlp090wQ+C+1u6Ayy9DL+J5R1Ba7qUeetA
on0Sml7SGP4XSspdEm9ob5MMDzLa3vyO6x0YyXZe4nxxMMEQARU=
=8MHS
-END PGP SIGNATURE-

Re: Let's start salvaging packages -- Summary of the BoF Session.

[Tobias Frost]

On Sun, Aug 05, 2018 at 01:20:47PM +, Scott Kitterman wrote:
> 
> 
> On August 5, 2018 7:41:41 AM UTC, Tobias Frost  wrote:
> >
> >Yes, the TC has the power to decide ultimately about maintainership
> >when
> >there is an dispute and if involved parties failed find consesus. The
> >proposed process does not change that.
> >
> >As an additional data point, we have processes in place to change
> >maintainership without involving the TC, e.g the MIA process.
> 
> Yes, that's sort of true, but not really.  The MIA process doesn't
> actually determine anything about who a maintains a package.  It
> determines who is no longer active in the project.  The impact on who
> the maintainer is is a secondary effect of the MIA process.

The MIA team orphans packages of inactive members.
The ITS just the chain of action from O -> ITA -> new maint to.
ITS -> new maint.

-- 
tobi

Re: Let's start salvaging packages -- Summary of the BoF Session.

[Tobias Frost]

On Sun, Aug 05, 2018 at 02:47:58PM +, Scott Kitterman wrote:
> 
> 
> On August 5, 2018 2:17:04 PM UTC, Adam Borowski  wrote:
> >On Sun, Aug 05, 2018 at 01:20:47PM +, Scott Kitterman wrote:
> >> Package 'salvaging' is about an involuntary change of maintainer
> >involving
> >> someone who is sufficiently active in the project not to be MIA. 
> >It's
> >> fundamentally different.
> >> 
> >> I suspect it's constitutionally sufficient for the TC to approve the
> >> salvaging process as long as the process allows them to resolve
> >related
> >> disputes.
> >
> >But there is _no_ dispute.  All the maintainer has to do is to close
> >the ITS
> >bug within a month.  Thus, if the bug remains unanswered, there is no
> >one
> >who would want to dispute the bug.  And not even a temporary
> >incapacitation
> >is a problem: for an ITS to be filed, you'd need to neglect the package
> >quite a while, thus the package was effectively unmaintained for much
> >longer
> >than a month.
> >
> >Involving the TC is a heavyweight process, and is fit for when there's
> >an
> >actual disagreement.  A disagreement requires two parties, with ITS one
> >of
> >them is gone.
> 
> So a maintainer misses one email and anything goes?  

No, they needs to miss >2 mails, but in reality more:
- Before the package becomes eligble, it'd have bugs reported against
  it.
- The ITS bug
- The NMUdiff.

(And even then, just talk wich each other; but this is a gerneal life
thing, not really related only to this process here).

> I have packages that look somewhat unmaintained that aren't.  I may
> seem somewhat oversensitive on this, but I recently discovered a
> 'maybe we should remove this package' bug on one of my packages that
> I'd missed the mail when it came in.

> TC is also supposed to set technical policy (including "contents of
> ... developers' reference materials").  I agree that invoking the TC
> for each salvaging decision is heavyweight, likely excessively so, but
> that isn't what I am suggesting.  I'm suggesting that they review and
> approve the salvaging POLICY (once and done, assuming they approve).

David Bremner co-authored the process. Gunnar was present in
the BoF. So, yes, TC members are already (informally) involved in this.

-- 
tobi


signature.asc
Description: PGP signature

Re: Let's start salvaging packages -- Summary of the BoF Session.

[Tobias Frost]

On Sun, Aug 05, 2018 at 06:50:28AM +, Scott Kitterman wrote:
> 
> Since it's explicitly in the Debian constitution that the TC is the
> decider of package maintainership, how does a dev-ref change overcome
> that?
> 

Yes, the TC has the power to decide ultimately about maintainership when
there is an dispute and if involved parties failed find consesus. The
proposed process does not change that.

As an additional data point, we have processes in place to change
maintainership without involving the TC, e.g the MIA process.

-- 
tobi

Let's start salvaging packages -- Summary of the BoF Session.

[Tobias Frost]

Hello everyone,

tl;dr: at the BoF the proposal seems to be uncontroversial at the
session.  So we will go forward with discussing it and propose a patch
to e.g dev-ref (if we're still aiming for dev-ref then)

Generally, the people at the BoF seemed to be supportive of the
proposal, but a few things needed a bit more of explaining or being more
explicit in wording:

- Team-maintained packages are not special and are covered by this
  process.

- dev-ref seems to be an appropriate place for this process.
  (similarities to the NMU)

- ITS as an abbreviation for Intend To Salvage seems to stick somehow...

- A clarification of what to be counted as activity on the package would
  be useful.  Example: If there is a new upstream version bug pending
  making it salvageable, a mail to the bug ("I've seen this mail, but I
  will not find only time in the next
  month" or a "this version is not suitable because of …") is to be
  counted as activity and invalidates the eligibility of salvaging.

- Salvaging timings should be balanced, so that (especially) new
  contributors can get attracted to salvage packages without being put
  off by a too long waiting time, but a (minimum) waiting time ensures
  some commitment from them; and we want them to maintain the package
  for a prolonged time.

- The time requirements fulfill also another purposes: New contributors
  will need guidelines, just to be on the safe side as they cannot tell
  otherwise what is acceptable in the project and what not.

- The guidelines will help new contributors to find sponsors more
  easily, once the ITS is established (like NMUs are today)

- Sponsorees could use the abbreviation ITS to mark the RFS bug (e.g as
  part of the RFS title)

- The process foundation is on "honest" maintainers and not wanting to
  harm Debian on purpose. (for which we'd have other kind of processes)

- We're talking about this problem already since a long time. Why has it
  not yet implemented? Is this because there are not enough salvageable
  packages, not enough people looking for new packages, or people afraid
  of doing so because of the traditional strong ownership of packages?
  IOW, What is holding us up to adopting this?

  One reason for this could be that we do not have at the moment a
  process for changing the maintainer of a package, except voluntarily
  or via the TC. But on the other hand, if we get only 10 new people one
  step into Debian, that'll be a win already.

- Gregor's mail [1], with input from enrico: Vagueness could be a good
  thing, and the worst that can happen if someone does a bad call on
  salvaging is that an ITS bug gets opened and closed, and something
  that was unclear gets documented.  The number of months and so on that
  are currently in the proposal are still useful to empower a new
  maintainer to make the call without fear, and could be put as an
  example reference in the wiki, rather than in the dev-ref.

  IMHO I'd avoid to remove the explicit rules altogether, as this will
  be difficult for new contributors to judge whether it is ok or not (as
  said above), but why not open it for the more experienced/thick
  skinned who want to take a shortcut? As enrico said: Worst thing that
  happens is an ITS opened and shortly closed afterwards when a package
  was over-eagerly selected.  (I hope this covers also Guillem's
  concerns at least partially)

[1] https://lists.debian.org/debian-devel/2018/08/msg8.html

Next steps:
- All: Please provide feedback.
- Draft the text for the dev-ref patch

-- tobi 


signature.asc
Description: PGP signature

Accepted log4cxx 0.10.0-14 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Aug 2018 18:07:05 +0800
Source: log4cxx
Binary: liblog4cxx-dev liblog4cxx10v5 liblog4cxx-doc
Architecture: source
Version: 0.10.0-14
Distribution: sid
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 liblog4cxx-dev - Logging library for C++ (development files)
 liblog4cxx-doc - Documentation for log4cxx
 liblog4cxx10v5 - Logging library for C++
Closes: 905331
Changes:
 log4cxx (0.10.0-14) sid; urgency=medium
 .
   * Update copyright years.
   * Replace dependency for autopkgtests on liblog4cxx10-dev with unversioned
 one. Thanks to Paul Genvers for the report. (Closes: #905331)
   * Also drop unneeded dependency for autopkgtest on build-essential.
   * Bump S-V 4.2.0
 - Add "Rules-Require-Root: no" to d/control.
Checksums-Sha1:
 877f3098746251a8b39e4ee0ceb45f1ed9c20036 2101 log4cxx_0.10.0-14.dsc
 64dcfc39753e5f742a7508744ca3bbc378547412 14960 log4cxx_0.10.0-14.debian.tar.xz
 9eabac3ed746da2e88a46f6bc2e8df90a023ff4b 5544 
log4cxx_0.10.0-14_source.buildinfo
Checksums-Sha256:
 747d40bd45692ce6a1fc673a09c154ddfdcf313f1a7d02386a9c1b38dc9314f2 2101 
log4cxx_0.10.0-14.dsc
 14c4e12ab18b6ec56f2699f7c4d5ec9cd4b50b4b466e81f37e103221554073de 14960 
log4cxx_0.10.0-14.debian.tar.xz
 946c52d428aca289e591f58fb66529a2c2df6a1e1e38244177b166a5b49b6791 5544 
log4cxx_0.10.0-14_source.buildinfo
Files:
 b8c98e2aabcb4b74fca2c73fb4e0aa9b 2101 devel optional log4cxx_0.10.0-14.dsc
 f5a7e0d16c694174bd82ab6f8346fd60 14960 devel optional 
log4cxx_0.10.0-14.debian.tar.xz
 bf1fbd5c332de2729e6ec1862a4f1fcb 5544 devel optional 
log4cxx_0.10.0-14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAltkKW4ACgkQkWT6HRe9
XTYoERAAkLMTJ8EyHbnXKfak5w+ZbI+vh+hwz0zD1mvYBHLLV1WZ7BVTPhlSSyix
QhdIzbhsAEMPs1pdhJpe7XOiQP4kH1ZvnUjgdExGt199b9TZyr36PB3amGRTwTz3
eC/N0egQwQXJg0bqqcDFF2bbu/chi1Mr7docxZYvuyuF4wh0ZTMmKxQ0Udp8rn6N
5/zX+/cglEaHlH9BMNz8O3zZemyD5/rm7Qj3eitKnBMol3BAw6LotZxnWpNg5nhi
UlR4JA0oX/IBsEwqtUHxlzNzI++hayfFcS+pyrdAhFbrjZqQn7wKNekBu88Y2Zw6
KP142/P5twOV/p7QPXbLeBEeJpuVhFOCtilLVAxRvlj2mbAXEps5mHAPj4M+dYRg
b96MwWMNvsXwdVa6j4bx3o6szQvIOFwFpuv8PCxWnsVlo56tVkeYvj40yHzQhsUR
cCXlYjwQ7+sm5Ui6kbAwSwTdZ6YFiyekHUcFyKJRauy+31wMF+obhlG9uIuQ+oES
tAqProZi0t8Y6etAV+IrWmRvaUFZCRRjQyFgBABgxMoxr+D7I2y7sBIhYGVJ1SNR
kvxkk0hGwK0ND/TmBQyAuityDPhshg/O7inqohmKNL2haod2jZiDSYZ/YM/Ap/wD
yAOz2e9xSJURKfPuWRxJ+vJ0Bn58IvPFPrCvmYQrWfJ+fEodsvE=
=LVOm
-END PGP SIGNATURE-

Re: Let's start salvaging packages!

[Tobias Frost]

Dear all,

The BoF has happened, thanks for your participation and all your
valuable input!

Thanks to the Video Team, the BoF recording is now available at [1], and
the html version of the gobby document can be found by following [2].

I did not yet find the time to condense the input from the BoF, but I
plan to do so in the next few days, but I wanted to share the links with
you already.

Best regards,
-- 
tobi

[1] 
https://meetings-archive.debian.net/pub/debian-meetings/2018/DebConf18/2018-08-02/let-s-start-salvaging-packages.webm
[2] https://gobby.debian.org/export/debconf18/bof/lets-start-salvaging-packages


signature.asc
Description: PGP signature

Re: Let's start salvaging packages!

[Tobias Frost]

On Mon, 2018-07-30 at 03:25 +0100, Chris Lamb wrote:
> Dear Tobi,
> 
> > There will be a BoF at DebConf18 Thursday, August 2nd 11:00 in Room
> > Xueshan [a]
> > for dicussion and fine tuning. (We will likely have video
> > coverage.)
> > 
> > I'm sending out our proposal draft already now so you will be able
> > to
> > come well-prepared to the to the BoF, as we want to have as much
> > time
> > as possible for the discussion.
> 
> Just as a point of order I would like to be 100% sure that enough
> notes
> are taken at the BoF and reposted here so that anyone "only" on
> debian-
> devel will be able to participate in any discussion.
> 
> DebConf is obviously a place where a lot of things can get done but
> naturally it cannot be the only venue for Project-wide consensus
> building. :)
> 
> Now, I'm sure this would happen anyway, but just to reassure.

Rest assured, we'll take plenty of notes on gobby, have video
recordings to revisit* everything then transfer the consensus finding
to -devel.

But just to avoid ambiguity: Use any channel avaible to you to
participate to the discussion! Whether in person, at the BoF, using
gobby, IRC, debian-devel, private email, etc… The important thing is
that the discussion takes place. This is absolutley not limited to
DebConf participants.

* very useful for a non-native English speaker like me ;-)

-- 
tobi


signature.asc
Description: This is a digitally signed message part

Let's start salvaging packages!

[Tobias Frost]

Dear fellow Debinites,

tl;dr: Let's bring the package salvage process discussed some years earlier to
life!

There will be a BoF at DebConf18 Thursday, August 2nd 11:00 in Room Xueshan [a]
for dicussion and fine tuning. (We will likely have video coverage.)

I'm sending out our proposal draft already now so you will be able to
come well-prepared to the to the BoF, as we want to have as much time
as possible for the discussion.

There will be a also a gobby document for the BoF [b].

[a] https://debconf18.debconf.org/talks/149-lets-start-salvaging-packages/
[b] gobby 
infinote://gobby.debian.org/debconf18/bof/lets-start-salvaging-packages

Why is a salvaging process necessary?
=

Most of the packages within Debian are well maintained and you -- our
maintainers do a tremendous job to keep it that way.  Let me start by
saying a big thanks for that!

However, we have to be honest: we've got also quite some packages which
are not so well cared for. For these packages, unpackaged upstream
versions and unreplied bugs are often seen.  As a result those packages
are not quite up to the quality level our users expect when using
Debian.

I'm not talking about orphaned packages, as we have processes for those,
but about packages that have fallen through the gaps, especially when
the maintainer is otherwise active.

As a project, we do not have effective processes to deal with such
"neglected" packages.

Even if someone shows up wanting to improve such a package, they are
usually not entitled to do so without explicit consent of the current
maintainer, which might be difficult to obtain.

Salvaging Process Proposal
==



Salvaging a package
---

Salvaging is the process by which, one attempts to save a package that,
while not officially orphaned, appear poorly maintained or completely
unmaintained.  This is a weaker and faster procedure than orphaning a
package officially through powers of the MIA team.  Salvaging a package
is not meant to replace MIA handling, and in contrast to it, it does not
comment about the overall activity of a maintainer. Instead, it handles
a package maintainership transition for a single package only, leaving
any other package or Debian membership or upload rights (when
applicable) untouched.

Reasons to salvage a package


A package is eligible for salvaging if it is in clear need of some love
and care, i.e. there are open bugs, missing upstream releases, or there
is work needed from a quality-assurance perspective; AND there is the
need to upload the package to deal with these issues; AND at least one
of these criteria applies:

* There is no visible activity regarding the package [c] for /six
  months/, OR

* A previous NMU was not acknowledged, and a bug justifying another NMU
  is pending for /one month/ [c,d], OR

* The last upload was an NMU and there was no maintainer upload within
  /one year/, OR

* Bugs exist for more than one major missing upstream version and the
  first bug is older than /one year/, OR

* The package blocks a sourceful transition for /six months/ after a
  transition bug was filed against the package in question.

Procedure to salvage a package
--

If the criteria described above are fulfilled, anyone interested can
start the following salvage procedure.

1) A bug with severity "important" against the package in question must
be filed, expressing the intent to take over maintainership of the
package.  The reporter may also offer to only take co-maintenance of the
package.  When filing the bug, all maintainers (incl. Team) and uploaders
should be put explicitly in X-Debuggs-CC.
(Note if the maintainer(s) seems to be generally inactive, it is
also a good idea to inform the MIA team in this step by X-Debbugs-CC'ing
m...@qa.debian.org )

2) The maintainer, any current uploader or any member of the associated
packaging team of the package in question may object publicly in
response to the bug filed within 21 days, and this terminates the
salvaging process.

The current maintainers may also agree to the intent to salvage a
package by filing a (signed) public response to the bug. The maintainer
also might offer the reporter co-maintainership instead.  On team
maintained packages, the associated team might also send out an signed
agreement notice to the reporter, inviting him to become Co-Maintainer
of the package if the team believes that this would beneficial for the
package and the the current maintainer does not object to it.  In those
three cases, a new package can be uploaded immediately by the new
(co-)maintainer(s).

3) The upload replacing the former maintainers of the package can be
made can be prepared already after 21 days, but needs to go to
DELAYED/7.  The salvage bug should be closed by the upload and an
nmudiff sent to the bug. The nmudiff should also explictly CC the
maintainer, the packaging team and all uploaders.


[c] 

Accepted gmrender-resurrect 0.0.7~git20180618.d0f46f5-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 28 Jul 2018 11:47:38 +0800
Source: gmrender-resurrect
Binary: gmediarender
Architecture: source
Version: 0.0.7~git20180618.d0f46f5-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gmediarender - Small headless UPnP media renderer
Changes:
 gmrender-resurrect (0.0.7~git20180618.d0f46f5-1) unstable; urgency=medium
 .
   * New upstream git snapshot.
   * Removing 01_spelling_corrections.patch -- applied upstream
   * Bump S-V to 4.1.5 -- no changes required.
Checksums-Sha1:
 a4c1e252648c4614988697c95ed49823fc114552 2125 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1.dsc
 c7063678442f8882baf4f3e8acda9ecd9385904e 104691 
gmrender-resurrect_0.0.7~git20180618.d0f46f5.orig.tar.gz
 624dbbe89b619651e0b6290eb65fd3aa8df4c091 5576 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1.debian.tar.xz
 62fcfdf3ad81ad5023e7e4c156fe9c6756f46805 6629 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1_source.buildinfo
Checksums-Sha256:
 2c6af4cb2f4bc5c0d1085d2bde862dcf2be2bd87ecebc16323b37a95f28a38d3 2125 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1.dsc
 19ebb85d0d65f731ec776f694350423c13214ae1cc472c08569db0dc66b7edec 104691 
gmrender-resurrect_0.0.7~git20180618.d0f46f5.orig.tar.gz
 25c1355436c7111fa4fd91dd8187bd095c5f01a3753c2cac248684f021517f5c 5576 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1.debian.tar.xz
 9293216ef97228d22455aafd9a3f36405028e69efe1d8efd17cab29fb4d79950 6629 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1_source.buildinfo
Files:
 012f81bef693e7b37d5e44d96052466a 2125 sound optional 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1.dsc
 debfb29b5805370c8d62d90cdaf1c6be 104691 sound optional 
gmrender-resurrect_0.0.7~git20180618.d0f46f5.orig.tar.gz
 11190b7adef0f73117bd8bb0640950a1 5576 sound optional 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1.debian.tar.xz
 7cbd021a6098de84a8d4196ee7b000fc 6629 sound optional 
gmrender-resurrect_0.0.7~git20180618.d0f46f5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAltb5+oACgkQkWT6HRe9
XTa8BQ//Uia4SNL3dlnRuyGnPluKwpU9Kod2/845b2R+j5PAA4y9cAANhV7PWBRK
hg8IA/JPxQ9sxBibuYVtxmQnZC+UAjRE/qLQ0ThdpR9I4iTImJ96FAHiKzYRs8Ej
L7JU3NZhyOVYXBiXC6ObFhipdETT75qj7qvu18Jwz1YJN+6LKalGeWchmyvEffDA
0g3hghTLRNY2wR+NforHfVDDcFS36c0onVTdsTyLP8N6LXnIDqJauQoe9RE59/Rd
3Ct483Y9ujIscsdhOvRHO1kp5bicl4uLv7hzR0IICWPaliYJAE2xeleNzxwSOuhv
6a4wYwyLUHtt21zRT7J82Wnbn+pPougOfqDEF+VqztepseujZ/gdZXpySQeGmJeE
8Y6nroKInlDed0Crxs6cp4unFHyGEY5youTaJinGDZXnM68HMkpPWwqqyD4fE0ap
8f2lwYGgbOhRTWL9vu9byVIujzeIKTMtSaImk+71zu7BgEWQFVTaZV5EZ732mAAc
8cQ9cuLfStFCgOV0wT08nqhffCZeE2UbOtIfm/BOnu5cBjIB2oz4j/7Q7kplNjwA
++IPHaH8OU40QAC7HkzmlCLrj1KzdXvzU8Xpt+m8wojaO6uc0QHs2pYyGVLKANU+
6Zpo2jfp6l3tNWkgLC9FRem3NUFHGaJc81jtZrEgXDsFx5x6l/0=
=vKuH
-END PGP SIGNATURE-

Accepted pdfsandwich 0.1.6-2 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Jul 2018 21:49:14 +0800
Source: pdfsandwich
Binary: pdfsandwich
Architecture: source
Version: 0.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 pdfsandwich - Tool to generate "sandwich" OCR pdf files
Closes: 868934 903026
Changes:
 pdfsandwich (0.1.6-2) unstable; urgency=medium
 .
   * d/control: repository moved to gitlab.
   * Add patch to put temporary files into own tmpdir with the proper
 permsissions. (Closes: #903026, #868934)
   * Bump S-V to 4.1.5 -- no changes
   * Update d/copyright: years and secure URI
   * Bump compat level to 11
   * Add spelling fixing patch
Checksums-Sha1:
 2c042b5c058983f1f23da149bbc7129aa622678a 1879 pdfsandwich_0.1.6-2.dsc
 07a2b2572c1c8babfa448d7e1fef153234e494e7 5376 pdfsandwich_0.1.6-2.debian.tar.xz
 2d58642c39263eca9ecc3d68c4e3361d671a0942 5747 
pdfsandwich_0.1.6-2_source.buildinfo
Checksums-Sha256:
 30ffcf6cf667fbf9f1e41a2f3d86a994d950aac9528a972496a4fc3f180fefff 1879 
pdfsandwich_0.1.6-2.dsc
 bc90a4eb0cf2146fd1fa0a717cbb3092e5f74cc85fa29ac60e2e2b92cf69e43d 5376 
pdfsandwich_0.1.6-2.debian.tar.xz
 06ef6c91030e5095db6216cb66a40d5efe55b0502d4b8431785039655d31759e 5747 
pdfsandwich_0.1.6-2_source.buildinfo
Files:
 90bdda94d68efa130283ae916b629cf1 1879 text optional pdfsandwich_0.1.6-2.dsc
 3dbf4d6a0fb4a22ff3f6539b58761125 5376 text optional 
pdfsandwich_0.1.6-2.debian.tar.xz
 1d749dddbfe4d6f3b434d8a9f647aec9 5747 text optional 
pdfsandwich_0.1.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAltbIycACgkQkWT6HRe9
XTZiJA//ZI3aDRhvkEwk+CNxw3FdUyjjd744CN7E0A3mnftbG22MNjcqAtQkm4Xd
+VMMqb1KDugrirFGQ5l/+nhDmnlTzQ71Dq8nD/P+ZgyXwvb2o3IKtgdFwrhV0IM1
g2XFCgbe9+//w0jBlZ9r4evtgDTejA96GJ4w16q8lrmCHqHjn2oMrTftFdAT0H2G
IvFxOqSELbdguT2zJ49dOZgYrHYX7WW2mgd43M7Axmh7Z9DumFScQ4oitnCY7rj2
WNRL8maCGBCaN9aT2IChYIZf2l1FIzq6gPY8kHm6IKmYDUSrFwuyaeilb4zSEPTO
qV78dbLdG/LWV0KC+a80PZGjSVw+40dbUMu5+ng13bt/YxQryZA/LClSAJWIM8FA
0K4jegzg6OGTJW5r5JLRyGMjLg5RZX2JG63tYhwiZZQz6ntA97SbmV417HB85hFb
/OFRBMlLVc69mJd8JCPC7ujyGghy7a7W5q34s4Th0QVrlzCod6jI1N6mVCf5vT0Y
BEzk4NU3hxe/2bThIjUrxls3ieTMX5IITooJ618VuwdjDaWj3MUpUQkr25p9Jgrp
CjpVE5sGVWxPdi58pkMrhd0sMmm21cMo+3Rdx1iYHszz9RaBaBDuq7SoF5PXp57b
R+BtmpuURC/7k/G70HZHLRZS9ii/pPIH9nTlAl+1B774HVCa8hw=
=SPPJ
-END PGP SIGNATURE-

Accepted gnome-shell-extension-autohidetopbar 20180511-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Jul 2018 22:27:36 +0800
Source: gnome-shell-extension-autohidetopbar
Binary: gnome-shell-extension-autohidetopbar
Architecture: source
Version: 20180511-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Description:
 gnome-shell-extension-autohidetopbar - GNOME shell automatic topbar hider
Changes:
 gnome-shell-extension-autohidetopbar (20180511-1) unstable; urgency=medium
 .
   * New upstream git snapshot.
   * Bump SV to 4.1.5 -- no changes
Checksums-Sha1:
 1fde672c0b4355e17839295390af276aec04 2171 
gnome-shell-extension-autohidetopbar_20180511-1.dsc
 42732cc18ea06d83f5faaa704d36724f6aa99485 15616 
gnome-shell-extension-autohidetopbar_20180511.orig.tar.xz
 ccafd7d4ca073ded10e0e0c5c327188b9e20e073 3768 
gnome-shell-extension-autohidetopbar_20180511-1.debian.tar.xz
 59e29e522c1b3d8147bbb69123219bb49533d136 5736 
gnome-shell-extension-autohidetopbar_20180511-1_source.buildinfo
Checksums-Sha256:
 dd41b1553e4fc8c113ddd0e9a2a38e0d30d1a4c23530b2600f2a57ec35938bb1 2171 
gnome-shell-extension-autohidetopbar_20180511-1.dsc
 0314024692c3115a26a34f93465f2eab38f11aff11824ff5bb4a612e63fb8169 15616 
gnome-shell-extension-autohidetopbar_20180511.orig.tar.xz
 d92717b00a9a6e9e0cf9487c918364f990117e1379cbe0c4c49cb03693727bfb 3768 
gnome-shell-extension-autohidetopbar_20180511-1.debian.tar.xz
 016b35e74a24a0fdce67b3f742fabf5a10c250f0f8eb1a9f17206384ee6fc037 5736 
gnome-shell-extension-autohidetopbar_20180511-1_source.buildinfo
Files:
 39972efdedf90c9485f25d58f99e7309 2171 gnome optional 
gnome-shell-extension-autohidetopbar_20180511-1.dsc
 7489840de555fab53ac7c29cf60feb33 15616 gnome optional 
gnome-shell-extension-autohidetopbar_20180511.orig.tar.xz
 98593a0a4e1253f0c3f70ea507e1226a 3768 gnome optional 
gnome-shell-extension-autohidetopbar_20180511-1.debian.tar.xz
 0bc0ab9991ba380ac9526638700d0698 5736 gnome optional 
gnome-shell-extension-autohidetopbar_20180511-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAltbLEAACgkQkWT6HRe9
XTYkHw//ay2StBOXMdtytKQf0JS3PjP8B2XCFmEbRbxhkpNuviBcWq4vKIAanXst
lSbOWPG1/PJajls666T4wXolYOiQIC2utgi6bwfImyoGiz/I5HPQ5eg/i1NKke0R
1Bv7518qroDdFuhVZW0jiR5YTP8F9HGSu/Us8rgDNZP9JnQFtNAiT/1p2KjbrtNn
q1JBPrgmaKmnccO7uP/PpczvmqLseFRW53PlTMdFBCHQCyv/x7w/lh4ifgCblCOO
xrshhAcGBVqJDAs8NRfy6oozfpqJdsq4BNtvz61M4oB59dfhU7xZavu6Rs0cCeSa
vqK5t7rjH4uhdF2wAJEuN/hyc+Ez2/sNIW9kY8wVDyz7kT15tfMPCeoxdFlT0Q6n
tPH0nzbTuDBMNSNrX7/W3IBz3/J1HgT4nelmILoCN9cEskyy6W1AdfQulgoVqAMV
RQJGc4owNXXLnevjHCU08vY/K3Mj2E4SwpLdnOQNTrBNBhlVHJZltZFRsjYQIbsA
Og0oqdEDY89JoD1zk2qepVfSYI+KbDDAA1M/nQGb0AFxSKxQXrJ4jnHlfujbvG9P
Hujo50pLqpc7UAMV+AphhlafpQc0dojIZHG9vEDQFXT9arJM7fec2ZkdP0wUwhWd
F9BXpYF9wSDZmVG8sT/gL2FAd+N6injGOVNlLN6KfYycl+M2cI4=
=q55b
-END PGP SIGNATURE-

Accepted darkradiant 2.6.0-3 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Jul 2018 01:45:17 +0800
Source: darkradiant
Binary: darkradiant darkradiant-plugins-darkmod
Architecture: source
Version: 2.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Tobias Frost 
Description:
 darkradiant - Level design toolchain for DOOM3 and The Dark Mod
 darkradiant-plugins-darkmod - DarkMod-specific plugins for DarkRadiant
Closes: 897734
Changes:
 darkradiant (2.6.0-3) unstable; urgency=medium
 .
   * New patch to fix FTBFS with GCC-8. thanks to Juhani Numminen for the
 patch. (Closes: #897734)
   * Bump S-V to 4.1.5
 - Set Rules-Requires-Root to "no".
 - no other changes required.
Checksums-Sha1:
 0bdc293c4847968ed87875278d080b8d6a38223f 2444 darkradiant_2.6.0-3.dsc
 3e2d9a8d547c06286ef8ca06e1f6a9c8eab77420 7544 darkradiant_2.6.0-3.debian.tar.xz
 f94c505812200c327f0ed74e51fa62c5951ffd99 15099 
darkradiant_2.6.0-3_source.buildinfo
Checksums-Sha256:
 773d914c493649850bee99f2ddc6a717d1e67b07f5ae5f420d2c1418bd8c4ab3 2444 
darkradiant_2.6.0-3.dsc
 adfd87a20b9b755f02c2bb45b666361138e7af36f9201d8ac8d877beb805cb41 7544 
darkradiant_2.6.0-3.debian.tar.xz
 d660dd96d94b24e8e0920da47a556515b850c1b662a282f8bd2d50851f52113c 15099 
darkradiant_2.6.0-3_source.buildinfo
Files:
 3815eb299f810f61e199844213dd0b56 2444 graphics optional darkradiant_2.6.0-3.dsc
 3771a6bdaed39e2c6ac64b53f0e21c92 7544 graphics optional 
darkradiant_2.6.0-3.debian.tar.xz
 e6d4e5e300065dbbf5ba76b12d644986 15099 graphics optional 
darkradiant_2.6.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAltYukoACgkQkWT6HRe9
XTZogBAApZz855mQxci0ObHxRTqmehwbCgoBz9r4bYVsEoKBlw0wEqJYMMJziDC2
fcHoPXkd9qJk6TmPY1qEPeZAHG8sARlAD+fD28GW7oOQ3DYGqclTANvmeladSllI
SuA+F6rCGOdf5JeSd/poghui5IeMKaG07FXPZ0CMKdNmqqAwRUKZIoT1z0YVo1A5
xISwb+qRhb34jlh7cC/2MNO+5nITOxzbpu2od6QC2D0i/eFkPZMfkJSvjwIG+6JK
+xMZ9g6L2ZWY804GHnTbmsg3fiOyeLpk1PnNfRYieHFWH6PwunVs1TfWZN7KuDji
UnRzV/hlAd8lDSWJa55DyMi6fGRgoDrCXtD3x81gYZFmIvqrYiXnVQ7joQh3hfFz
RnE2dx3MA0X3hBad1Yxm2Z0cHTefK+YpoGNJyza7fJFrlQqPswni15rnkq6YxdHk
BvS2rCB5v5/zGnoeUDFe/hyfJFajP3wW5ixNW57Rf1lilXJzdU8wN2qSIWg0j2pa
vkg2dTeXKQ3WXwUcmMMXTnTABa6n/F5dTWVMQLodu8TKnk6oFhUg+OgeTDPuNjs1
zHsTOU9jQEvEedqOo+jKU3shPiVYedUDPH97NTQ8iZWVNrrPdsQkDAqQPTUFTvLR
3Gf23ybEOBmDOO12Ipm3MixXUICKLMWrZ9n2Gw/rpEIhlV6NK/0=
=E+sw
-END PGP SIGNATURE-

Accepted dhewm3 1.4.1+git20180714+dfsg-1 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Jul 2018 00:15:00 +0800
Source: dhewm3
Binary: dhewm3-doom3 dhewm3-d3xp dhewm3
Architecture: source
Version: 1.4.1+git20180714+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Tobias Frost 
Description:
 dhewm3 - GPL Doom 3 game engine
 dhewm3-d3xp - dhewm3's gamelibrary for the title DOOM³: Resurrection of Evil
 dhewm3-doom3 - dhewm3's gamelibrary for the title DOOM³
Changes:
 dhewm3 (1.4.1+git20180714+dfsg-1) unstable; urgency=medium
 .
   * New upstream git snapshot.
 - Spelling error patch partially applied upstream, refreshing.
   * Bump SV to 4.1.5:
 - Set Rules-Requires-Root to "no"
 - no other changes required.
Checksums-Sha1:
 59bd29bca7c93d3c5264c6325873eb1ba2e4b11c  
dhewm3_1.4.1+git20180714+dfsg-1.dsc
 055404f933599c2132770286de6d7e754d4bc72a 2184348 
dhewm3_1.4.1+git20180714+dfsg.orig.tar.xz
 e95d208c8de6243681b683df8667a6e8655b9adf 11008 
dhewm3_1.4.1+git20180714+dfsg-1.debian.tar.xz
 f20f897fcab91e5ccf5bb80ab7455d4b2ce15992 11764 
dhewm3_1.4.1+git20180714+dfsg-1_source.buildinfo
Checksums-Sha256:
 887187a33e7da2f3851823d789b7676678121e32e65fa740f58c101bcfac128b  
dhewm3_1.4.1+git20180714+dfsg-1.dsc
 3627a77b8c47526d4753a59cfddc5c5d7a66f8e8381f6bb8d135fd34ca9d1b0f 2184348 
dhewm3_1.4.1+git20180714+dfsg.orig.tar.xz
 71a3310cbcbc8c08d47d53879803dbf50d1bcd1d898febd05fae65eb264d16cc 11008 
dhewm3_1.4.1+git20180714+dfsg-1.debian.tar.xz
 db12e34d5395fb6089699b01f80bed9297ae4795cb1c5c085e4de21284fa4391 11764 
dhewm3_1.4.1+git20180714+dfsg-1_source.buildinfo
Files:
 7a08ceaf68e0953a114ee814658b7f3f  contrib/games optional 
dhewm3_1.4.1+git20180714+dfsg-1.dsc
 1b87023ffe77590e4b827a467902e893 2184348 contrib/games optional 
dhewm3_1.4.1+git20180714+dfsg.orig.tar.xz
 b59b2196eeb41ad1a6982cf072bed7c3 11008 contrib/games optional 
dhewm3_1.4.1+git20180714+dfsg-1.debian.tar.xz
 c2ad31e97102e34c28608c419cd59d22 11764 contrib/games optional 
dhewm3_1.4.1+git20180714+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAltYokMACgkQkWT6HRe9
XTZ6tw//TRwivMda+3GhCzXCHIr062ZCdki6DL6EhwpB0/EkXpJdNogZ1xZq8e3u
KEbKqgYRsbvfT1Y7p9TnZiFoB/708Tlg5e9f4iPdE12V5fGVs+gGxWNFZMqzL6W8
XMgRBuK0xk4BJxetvAce+GxvU0v+u3HmkRrEXV2vaX1YpcbrneZudgXSpGCsUlBw
o5C7hsYjokkpSEVgGcO9qpKlUACgCueQyc9s0ioeZzLGbqKLlMvhMK3E0Uu3B7sF
tfU4/9xtsiZ2FEVpSBuAZxqyYy22dYiKyjasMsDR6P82XnwJoL+wEYAioZnKBvps
C+TNPYQC+d1W4aw8DmecWRS9iW+pgWRbfA6NZK9206lNvw2IKrgxRvhhrOqhoTpn
6JtX2K2vidHKCK8UGhWx2YkmEb+DB6swquLnC2oqIQShBGQEjjaUdPOg7w9+oG6s
DFF6flTyUWMZgPVtgXloT+woHZyMef/fV58HCaFoTFHvvajlHAVdu1qfqI32qBB9
s7q3gQv4AkXOn0q7CETPmE6KN/P584gHKas3bNJg5BjAQxGjH8KC68aWr6vSTHAz
yQArvoAP1Rt+QfFJpF8S1Ni5FSEXWG65wBQy0NNC0c6jB3sfy68ggPNIbs461Gtu
fiUAzMy39+n4pa4wJWNWmYmIav7tDyfZhs8ekXezlOB699W/gaA=
=laOz
-END PGP SIGNATURE-

Accepted opencascade 7.3.0+dfsg1-3 (source) into unstable

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 27 Jun 2018 08:13:20 +0200
Source: opencascade
Binary: libocct-foundation-7.3 libocct-foundation-dev libocct-modeling-data-7.3 
libocct-modeling-data-dev libocct-modeling-algorithms-7.3 
libocct-modeling-algorithms-dev libocct-visualization-7.3 
libocct-visualization-dev libocct-ocaf-7.3 libocct-ocaf-dev 
libocct-data-exchange-7.3 libocct-data-exchange-dev libocct-draw-7.3 
libocct-draw-dev occt-draw occt-misc libocct-doc
Architecture: source
Version: 7.3.0+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Tobias Frost 
Description:
 libocct-data-exchange-7.3 - Open CASCADE Technology module for CAD data format 
interoperabili
 libocct-data-exchange-dev - Open CASCADE Technology module for CAD data format 
interoperabili
 libocct-doc - Open CASCADE Technology CAE platform documentation
 libocct-draw-7.3 - Open CASCADE Technology command interpreter & graphical 
test libr
 libocct-draw-dev - Open CASCADE Technology interpreter & graphics test library 
- dev
 libocct-foundation-7.3 - OCCT module underlying all other OCCT classes
 libocct-foundation-dev - Open CASCADE Technology module underlying all other 
OCCT classes
 libocct-modeling-algorithms-7.3 - Open CASCADE Technology geometrical & 
topological algorithms modu
 libocct-modeling-algorithms-dev - Open CASCADE Technology geometrical & 
topological algorithms modu
 libocct-modeling-data-7.3 - Open CASCADE Technology 2D/3D geometric primitives 
data structure
 libocct-modeling-data-dev - Open CASCADE Technology 2D/3D geometric primitives 
data structure
 libocct-ocaf-7.3 - Open CASCADE Technology application-specific data and 
functionali
 libocct-ocaf-dev - Open CASCADE Technology application-specific data and 
functionali
 libocct-visualization-7.3 - Open CASCADE Technology graphical data 
visualization module
 libocct-visualization-dev - Open CASCADE Technology graphical data 
visualization module - dev
 occt-draw  - Open CASCADE Technology command interpreter and graphical test sy
 occt-misc  - OCCT CAE platform shared library miscellaneous files
Changes:
 opencascade (7.3.0+dfsg1-3) unstable; urgency=medium
 .
   * Upload to unstable.
   * Import symbols for powerpcspe.
   * Bump S-V to 4.1.4 -- no changes required
Checksums-Sha1:
 2a078c62bd96500821b8529ff2e3ff342ed9e626 3485 opencascade_7.3.0+dfsg1-3.dsc
 86c743abcf1f7bea848a831b7cfd9ee833d0c5a0 641216 
opencascade_7.3.0+dfsg1-3.debian.tar.xz
 d723bda3844889ceadd91f1dda392c29cf268991 10985 
opencascade_7.3.0+dfsg1-3_source.buildinfo
Checksums-Sha256:
 d7196303a21f2b7947fea9d10c92af961212adf964ebc7dbedad092fcf864a49 3485 
opencascade_7.3.0+dfsg1-3.dsc
 411213d1c77698b136d25b8a11177c1c2c611c339410406137735eda0bfe94c0 641216 
opencascade_7.3.0+dfsg1-3.debian.tar.xz
 333109f4b332cc2d1529950f1d54694eb8480430624738bce852f2b06a031c06 10985 
opencascade_7.3.0+dfsg1-3_source.buildinfo
Files:
 cb3e6c1392f519aebdba7ad0801c912c 3485 science optional 
opencascade_7.3.0+dfsg1-3.dsc
 208b61c55929392176bef9decb353629 641216 science optional 
opencascade_7.3.0+dfsg1-3.debian.tar.xz
 57bd439cd13567c3ac8feeb1067df554 10985 science optional 
opencascade_7.3.0+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlszK7UACgkQkWT6HRe9
XTb6cQ/+IB4ZcysJuup8NHPEDvUafSA8zgrwafPHw46i+Tz4sBr01JZfIB8V+weB
cL+xYgQq2SXPCzRd5I6QoowTODHdGhcZm2MypPkeWYSIszJGdjLTc4Udv+E82yBX
5xVT/MnYbd3g5JONDMleg/mqXebh/PR0mQ2iZW+Qo/ZlYgBnrEIKI74Az9JQvGBL
vO1/R98di0boTA/FXh0eAASCQOTzaSrVzh65lNOEHLzrmf7gUkHnuONHh5DLr2zj
E00jVka6JIYnTaACmvWheDxrhTYcuSGiT2qHBK0SjCEmZkcTkbyNKC+ulZizTAON
oEq0S1zE8ZCk6SstHMB8+pOhvqXMnwCrQS747bCbBwSMu7EKpDCo2qhNrGghe/fy
hCA7D0CXn0pgzOinXJlrjsI5Jncvp5aaS5Udq1+MhtsCj7qzh1i+QNCrpXgDpOmn
oFq63GPNWhmJ+zCEAV0i2Y5Iz7iF9DvhwsPnyWLkVpLjJSe00fczPa0ilSvnNA1H
sEbDZT0FhaOWrjjo6h63jO3y2dElD15euz2NvWbL2QdBUApqXVbzbucNuz9QBnN6
o2iLenVQ08K7lThP4TDglh3gvbxTEKLeAUJ8Q059B9Mzav+XM2JWKuHeCKaSc3EF
w1NsTHSWlLraBft8HH8MiJQrsuufw0SGk/fNDW5QZ7WdnKsGkgE=
=209Y
-END PGP SIGNATURE-

Accepted opencascade 7.3.0+dfsg1-2 (source) into experimental

[Tobias Frost]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 Jun 2018 12:27:11 +0200
Source: opencascade
Binary: libocct-foundation-7.3 libocct-foundation-dev libocct-modeling-data-7.3 
libocct-modeling-data-dev libocct-modeling-algorithms-7.3 
libocct-modeling-algorithms-dev libocct-visualization-7.3 
libocct-visualization-dev libocct-ocaf-7.3 libocct-ocaf-dev 
libocct-data-exchange-7.3 libocct-data-exchange-dev libocct-draw-7.3 
libocct-draw-dev occt-draw occt-misc libocct-doc
Architecture: source
Version: 7.3.0+dfsg1-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Tobias Frost 
Description:
 libocct-data-exchange-7.3 - Open CASCADE Technology module for CAD data format 
interoperabili
 libocct-data-exchange-dev - Open CASCADE Technology module for CAD data format 
interoperabili
 libocct-doc - Open CASCADE Technology CAE platform documentation
 libocct-draw-7.3 - Open CASCADE Technology command interpreter & graphical 
test libr
 libocct-draw-dev - Open CASCADE Technology interpreter & graphics test library 
- dev
 libocct-foundation-7.3 - OCCT module underlying all other OCCT classes
 libocct-foundation-dev - Open CASCADE Technology module underlying all other 
OCCT classes
 libocct-modeling-algorithms-7.3 - Open CASCADE Technology geometrical & 
topological algorithms modu
 libocct-modeling-algorithms-dev - Open CASCADE Technology geometrical & 
topological algorithms modu
 libocct-modeling-data-7.3 - Open CASCADE Technology 2D/3D geometric primitives 
data structure
 libocct-modeling-data-dev - Open CASCADE Technology 2D/3D geometric primitives 
data structure
 libocct-ocaf-7.3 - Open CASCADE Technology application-specific data and 
functionali
 libocct-ocaf-dev - Open CASCADE Technology application-specific data and 
functionali
 libocct-visualization-7.3 - Open CASCADE Technology graphical data 
visualization module
 libocct-visualization-dev - Open CASCADE Technology graphical data 
visualization module - dev
 occt-draw  - Open CASCADE Technology command interpreter and graphical test sy
 occt-misc  - OCCT CAE platform shared library miscellaneous files
Changes:
 opencascade (7.3.0+dfsg1-2) experimental; urgency=medium
 .
   [ Tobias Frost ]
   * Import symbols for 7.3.0 from buildlogs for archs:
   alpha arm64 armel armhf i386 m68k mips mips64el mipsel powerpc ppc64
   ppc64el s390x sh4
 .
   [ Kurt Kremitzki ]
   * Add patch to enable exception handling.
Checksums-Sha1:
 f1d40d74dabf090b644863f486d70cf88b406723 3485 opencascade_7.3.0+dfsg1-2.dsc
 9b1771c3846bf00c2854ba5a515a9e0b6315f0c0 641140 
opencascade_7.3.0+dfsg1-2.debian.tar.xz
 3481b130228ec9c5b54ee3209eec92bc49f8860b 10988 
opencascade_7.3.0+dfsg1-2_source.buildinfo
Checksums-Sha256:
 480ab4fa34198bd255f92f37e230ec0fc168f3e746c0a68fa8c7e1d37e0c08b2 3485 
opencascade_7.3.0+dfsg1-2.dsc
 695de76259bec3cb86610b80d46aba82a34b2e151680fddf5ca507ea0e8cb1d1 641140 
opencascade_7.3.0+dfsg1-2.debian.tar.xz
 cae0e40ecdd809aa746f7cf27a1b29401e71955bc4e1461d10f5c6e968345137 10988 
opencascade_7.3.0+dfsg1-2_source.buildinfo
Files:
 d01cd75bbb1ef8359e6b41f932af543e 3485 science optional 
opencascade_7.3.0+dfsg1-2.dsc
 bb148fd1adef537528b55be1c8511d71 641140 science optional 
opencascade_7.3.0+dfsg1-2.debian.tar.xz
 c0775b2a74c1aadf734f4e12d20f31e9 10988 science optional 
opencascade_7.3.0+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAlsuIK0ACgkQkWT6HRe9
XTbfQRAAyta9LPJvA60r6cuQeYhQYiBRMYL8+qJN4HN3N38FSsz9J4nJHAyaBXIE
dPmXQaU+0EJ+h8Y5BrRPZ8p3xkUVTctwrvCAiFP0p7w0+xv8hQrMtRgivc0lrmDZ
Tx3g7C7xHL3xoT/BCrwL1kNVOTRiPFA1gxPmD5OSi41JEWMKL196ael7Wr6VVJrv
qI2PjyeoFLs7EH4wwR368+ZTLWlVYDeisiGjG9UBvPD1zHudaTzkcHJ3oIrk6TfU
lFOAGWyECRMWOcSNoH7gl4hI6mfN5qjJP8RQpkcQ+Zhvl7DU9oEDeRMN9okRwwcT
7L26bgQmdZ+KkujzIr9gvyEymxAF2QAHJ7vUNAuEiCQI0lbOHd4lp9/fsts2FJdN
Ep+Hs2ik9ajdgTdnlApRiY1QFgfmdxGEKfKa0veroPFiQnJkgaghyJ1E8GaK2q68
JtlWLqy3sCiruvX3UbPQ4MflhlHdLkn6lwI8dPXzHlJTD6hgISUfYldXRpASau7U
VfryP7S02h6mUZLciJtxVAWLqnxl7bSpxuy1ZENbNlkuKwKXbSHHXNUDrJuD5wi6
sOwcLoXI+Ua37KcuSP1CKXBodWJTodcNn3qIW63KGKP+ZIwksFWmV37y4znUFuAO
5RyTLoMSqqHdSa65rILbmcM3w24OlaZPos5/AbvhGgHFlPUSUz8=
=IOR7
-END PGP SIGNATURE-