Bug#1071177: syslog-ng-core: typo in shebang of tty10.sh
Package: syslog-ng-core
X-Debbugs-Cc: baptiste.ca...@synacktiv.com
Version: 3.38.1-5
Severity: minor
Dear Maintainer,
* What led up to the situation?
Having the line `destination d_console_all { getvirtconsole(); };` in my
/etc/syslog-ng/syslog-ng.conf configuration file.
If I understand it correctly, this config calls, somehow,
/usr/share/syslog-ng/include/scl/getvirtconsole/plugin.conf which contains
'exec("`scl-root`/getvirtconsole/tty10.sh")' and therefore executes the
/usr/share/syslog-ng/include/scl/getvirtconsole/tty10.sh script.
* What exactly did you do (or not do) that was effective (or ineffective)?
I installed the syslog-ng-core package on a server with an auditd rule that
catches unusual execve errors, this rule triggered on the execution of
/usr/share/syslog-ng/include/scl/getvirtconsole/tty10.sh as shown in the
logs below:
```
type=PROCTITLE msg=audit(05/15/2024 00:00:15.740:644853) : proctitle=sh -c
/usr/share/syslog-ng/include/scl/getvirtconsole/tty10.sh
type=PATH msg=audit(05/15/2024 00:00:15.740:644853) : item=1
name=/usr/share/syslog-ng/include/scl/getvirtconsole/tty10.sh
inode=53505901 dev=fe:02 mode=file,755 ouid=root ogid=root rdev=00:00
nametype=NORMAL cap_fp=none cap_fi=none cap_fe=0 cap_fver=0 cap_frootid=0
type=PATH msg=audit(05/15/2024 00:00:15.740:644853) : item=0
name=/usr/share/syslog-ng/include/scl/getvirtconsole/tty10.sh inode=XXX
dev=fe:02 mode=file,755 ouid=root ogid=root rdev=00:00 nametype=NORMAL
cap_fp=none cap_fi=none cap_fe=0 cap_fver=0 cap_frootid=0
type=CWD msg=audit(05/15/2024 00:00:15.740:644853) : cwd=/
type=SYSCALL msg=audit(05/15/2024 00:00:15.740:644853) : arch=x86_64
syscall=execve success=no exit=ENOEXEC(Exec format error) a0=XXX a1=XXX
a2=XXX a3=XXX items=2 ppid=XXX pid=XXX auid=unset uid=root gid=root
euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=(none)
ses=unset comm=sh exe=/usr/bin/dash subj=unconfined
key=hids_execve_anormal_error
```
* What was the outcome of this action?
The execution returns a ENOEXEC code
* What outcome did you expect instead?
The execution should not fail
* Fix
Simply patch the shebang as shown below:
```
# diff tty10.orig.sh tty10.sh
1c1
< #/bin/sh
---
> #!/bin/sh
```
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-17-amd64 (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_SOFTLOCKUP
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages syslog-ng-core depends on:
ii libc6 2.36-9+deb12u3
ii libcap21:2.66-4
ii libglib2.0-0 2.74.6-2
ii libivykis0 0.42.4-1
ii libjson-c5 0.16-2
ii libnet11.1.6+dfsg-3.2
ii libpcre3 2:8.39-15
ii libssl33.0.11-1~deb12u2
ii libsystemd0252.19-1~deb12u1
ii libwrap0 7.6.q-32
ii sysvinit-utils [lsb-base] 3.06-4
Versions of packages syslog-ng-core recommends:
ii logrotate 3.21.0-1
Versions of packages syslog-ng-core suggests:
pn syslog-ng-mod-add-contextual-data
pn syslog-ng-mod-amqp
pn syslog-ng-mod-examples
pn syslog-ng-mod-geoip2
pn syslog-ng-mod-graphite
pn syslog-ng-mod-http
ii syslog-ng-mod-mongodb 3.38.1-5
pn syslog-ng-mod-python
pn syslog-ng-mod-rdkafka
pn syslog-ng-mod-redis
pn syslog-ng-mod-riemann
pn syslog-ng-mod-slog
pn syslog-ng-mod-smtp
pn syslog-ng-mod-snmp
ii syslog-ng-mod-sql 3.38.1-5
pn syslog-ng-mod-stardate
pn syslog-ng-mod-stomp
pn syslog-ng-mod-xml-parser
Thank you.
Bug#1071079: ipp-usb: Systemd service cannot be enabled manually
On 13-05-24, Baptiste Jonglez wrote: > Would it be possible to add the missing bits to the systemd service so that it > can be enabled? Something like the following: > > [Install] > WantedBy=multi-user.target This is incorrect, ipp-usb is still started in udev mode, so it exits immediately if no printer is found. To start it in standalone mode, it should rather be (here shown as an override): # /etc/systemd/system/ipp-usb.service.d/override.conf [Service] ExecStart= ExecStart=/sbin/ipp-usb standalone [Install] WantedBy=multi-user.target This is better since ipp-usb will not exit immediately. However, it doesn't react to plugging the USB printer or starting the printer... I'm afraid this points more at a problem with my setup, rather than a bug in ipp-usb or the Debian packaging. I will investigate more. Regards, Baptiste
Bug#1071079: ipp-usb: Systemd service cannot be enabled manually
Package: ipp-usb Version: 0.9.23-1+b4 Severity: normal Dear Maintainer, I am running ipp-usb in a LXC container, with USB passthrough. When starting the systemd service "ipp-usb.service" manually, everything works fine, the printer is detected and exported over the network. However, "ipp-usb.service" does not start automatically when booting the LXC container. It seems that the service is supposed to be started automatically through udev. But udev on this system does not define ID_USB_INTERFACES, so the udev rule shipped with ipp-usb does not match and thus does not start the service. It is somewhat a cornercase, but I would like to be able to enable the service regardless, and this is currently not possible: # systemctl enable ipp-usb.service The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. Would it be possible to add the missing bits to the systemd service so that it can be enabled? Something like the following: [Install] WantedBy=multi-user.target Thanks, Baptiste -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-0.deb10.28-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ipp-usb depends on: ii avahi-daemon 0.8-10 ii libavahi-client3 0.8-10 ii libavahi-common3 0.8-10 ii libc6 2.36-9+deb12u7 ii libusb-1.0-0 2:1.0.26-1 ipp-usb recommends no packages. ipp-usb suggests no packages. -- Configuration Files: /etc/ipp-usb/ipp-usb.conf changed [not included] -- no debconf information
Bug#1020989: trafficserver: failed to load plugin
Hello, Thanks for the detailled report. The only solution I got for now is to update /etc/trafficserver/record.config to disable dynamic reload for plugins: CONFIG proxy.config.plugin.dynamic_reload_mode INT 0 This way, dynamic plugin will be disable, as well as the copy and rename operations in the /run directory. Please note however that any update in remap.config will require a full service restart. I'm preparing a new package release to disable the dynamic reload by default. Best, Jean Baptiste On 12/29/23 4:21 PM, Yavor Doganov wrote: On Mon, Oct 24, 2022 at 10:39:45AM +0200, Jean Baptiste Favre wrote: Please provide some more details on you issue: * which plugin do you use? Is there any specific configuration? I am not YunQiang Su but I'm pretty sure we're talking about the same thing. Any remap plugin will fail to load; for example, add the following to /etc/trafficserver/remap.config (example from the manual): map http://a.com http://b.com @plugin=regex_remap.so @pparam=maps.reg With contents of /etc/trafficserver/maps.reg (again from the manual): ^/(ogre.*)/more http://www.ogre.com/$h/$0/$1 Global plugins are not affected by this issue. * do you have some trafficserver's logs to provide? Here you are (/var/log/trafficserver/diags.log): [Dec 28 20:00:59.369] traffic_server ERROR: plugin 'regex_remap.so' failed to load: /run/trafficserver/adb67a84-e739-4e8f-bc9d-c4797cec16e4/usr/lib/trafficserver/modules/regex_remap.so: failed to map segment from shared object [Dec 28 20:00:59.369] traffic_server ERROR: [ReverseProxy] failed to add remap rule at /etc/trafficserver/remap.config line 199: /run/trafficserver/adb67a84-e739-4e8f-bc9d-c4797cec16e4/usr/lib/trafficserver/modules/regex_remap.so: failed to map segment from shared objectfailed to remove runtime copy: Success [Dec 28 20:00:59.369] traffic_server WARNING: something failed during BuildTable() -- check your remap plugins! [Dec 28 20:00:59.369] traffic_server FATAL: remap.config failed to load [Dec 28 19:46:23.246] traffic_server ERROR: plugin 'cachekey.so' failed to load: /run/trafficserver/c4edf320-f56b-4193-8554-7db2dccfa0a7/usr/lib/trafficserver/modules/cachekey.so: failed to map segment from shared object [Dec 28 19:46:23.246] traffic_server ERROR: [ReverseProxy] failed to add remap rule at /etc/trafficserver/remap.config line 197: /run/trafficserver/c4edf320-f56b-4193-8554-7db2dccfa0a7/usr/lib/trafficserver/modules/cachekey.so: failed to map segment from shared objectfailed to remove runtime copy: Success [Dec 28 19:46:23.246] traffic_server WARNING: something failed during BuildTable() -- check your remap plugins! [Dec 28 19:46:23.246] traffic_server FATAL: remap.config failed to load There are errors from dlopen. As the OP said, the culprit is that it copies the plugins from /usr/lib to /run and tries to dlopen them there. This is doomed to fail because, exactly as the OP said, /run is mounted with the "noexec" option. Upstream logic behind this is to dynamically reload plugins that are changed while the server is running. I guess it makes sense with custom plugins and some other scenarios but there's no way for this to work on Debian systems. The attached dirty hack removes this code but also leads to test failures of two test programs where this dynamic reloading functionality is tested. It is not a proper fix but at least makes remap plugins load again. Like the OP, I also believe this bug deserves RC severity. Additionally (and this is an entirely separate issue, completely unrelated with the problem described above), some global plugins fail to load as well, for various reasons: [Dec 28 19:34:21.066] traffic_server NOTE: loading plugin '/usr/lib/trafficserve r/modules/prefetch.so' [Dec 28 19:34:21.066] traffic_server ERROR: unable to find TSPluginInit function in '/usr/lib/trafficserver/modules/prefetch.so': /usr/lib/trafficserver/modules/prefetch.so: undefined symbol: TSPluginInit [Dec 28 19:34:21.066] traffic_server FATAL: unable to find TSPluginInit function in '/usr/lib/trafficserver/modules/prefetch.so': /usr/lib/trafficserver/modules/prefetch.so: undefined symbol: TSPluginInit There is indeed no such function, and according to the plugin API there should be. [Dec 29 14:31:12.743] traffic_server ERROR: [geoip_acl] No Geo library available! [Dec 29 14:31:12.743] traffic_server ERROR: [ReverseProxy] failed to add remap rule at /etc/trafficserver/remap.config line 206: failed to initialize plugin geoip_acl.so: Unknown plugin errorfailed to remove runtime copy: Success [Dec 29 14:31:12.744] traffic_server WARNING: something failed during BuildTable() -- check your remap plugins! [Dec 29 14:31:12.744] traffic_server FATAL: remap.config failed to load I have tested only those that are pcre-based.
Bug#1068393: src:pytest-testinfra: unsatisfied build dependency in testing: ansible
Control: block -1 by 1061781 Hi Paul, On Thu, 2024-04-04 at 14:38 +0200, Paul Gevers wrote: > Dose [1] is reporting a build issue with your package, it's missing a > build dependency. Obviously your build dependencies shouldn't be > removed from testing, but unfortunately there are multiple scenarios > where that can happen nevertheless. To uphold our social contract, > Debian requires that packages can be rebuild from source in the suite > we are shipping them, so currently this is a serious issue with your > package in testing. > > Can you please investigate the situation and figure out how to resolve > it? Regularly, if the build dependency is available in unstable, > helping the maintainer of your Build-Depends to enable migration to > testing is a great way to solve the issue. If your build dependency is > gone from unstable and testing, you'll have to fix the build process > in some other way. Thanks for the hint. I'm not sure I can help ansible migrate (it would need an update to the latest upstream and that's not a trivial task), but I'll do the maintenance on this bug report, closing it once pytest- testinfra is removed from testing. Best, -- Baptiste Beauplat signature.asc Description: This is a digitally signed message part
Bug#1026587: cerealizer: TypeError: __dict__ must be set to a dictionary, not a 'NoneType'
Hello, I've just published a new version of cerealizer (0.8.4) that fixes these problems. Thank you for reporting, Best regards, Jean-Baptiste Lamy Chargé de Recherche INSERM, laboratoire LIMICS (informatique médicale) Public associate researcher at INSERM, LIMICS labs (medical informatics) > > De : Andreas Tille > Envoyé : Wed, 28 Feb 2024 11:25:18 +0100 > À : j...@lesfleursdunormal.fr > Objet : cerealizer: TypeError: __dict__ must be set to a dictionary, not a > 'NoneType' > > Control: tags -1 upstream > Control: forwarded -1 j...@lesfleursdunormal.fr > > > Hi Jean-Baptiste, > > the Debian packaged version of cerealizer recieved a bug > report about a build failure > >TypeError: __dict__ must be set to a dictionary, not a 'NoneType' > > You can read the relevant part of the build log inside the bug > report[1]. While this report is not about your latest upstream version > (it is against version 0.8.1 which was the packaged version at the time > of the bug report) I updated to version 0.8.3 in our packaging git. > When running our CI test with the latest tools I get the same error > unfortunately. You can find the full build log here: > >https://salsa.debian.org/python-team/packages/cerealizer/-/jobs/5375270 > > It would be great if you could find a fix for this issue. > > Kind regards > Andreas. > > > [1] https://bugs.debian.org/1026587 > > -- > http://fam-tille.de
Bug#1059937: fio crashes at runtime on kernel 6.6
Followup-For: Bug #1059937 Package: fio Version: 3.36-1 Hello, Now that Debian ships a 6.6 kernel on riscv64, this bug also manifests itself at runtime with the existing 3.36-1 fio package: # fio --name cfarm93 --rw=randwrite --filename=/home/500G.bin --direct=1 --blocksize=4K --iodepth=1 --numjobs=16 --ioengine=posixaio --runtime 3600 --group_reporting; fio --name cfarm93 --rw=randread --filename=/home/500G.bin --direct=1 --blocksize=4K --iodepth=1 --numjobs=16 --ioengine=posixaio --runtime 3600 --group_reporting cfarm93: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=posixaio, iodepth=1 ... fio-3.36 Illegal instruction # dmesg [ 937.305609] fio[6695]: unhandled signal 4 code 0x1 at 0x002aac37f468 in fio[2aac355000+bd000] [ 937.314529] CPU: 1 PID: 6695 Comm: fio Not tainted 6.6.0-starfive2 #1 [ 937.320973] Hardware name: StarFive VisionFive 2 v1.3B (DT) The kernel I run (see below) is slightly patched from Debian 6.6 kernel to add PCIe support on VisionFive 2, but should not be significantly different. Thanks, Baptiste -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: riscv64 Kernel: Linux 6.6.0-starfive2 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fio depends on: ii init-system-helpers 1.66 ii libaio1 0.3.113-5 ii libc62.37-13 ii libgfapi011.1-4 ii libibverbs1 48.0-1 ii libnbd0 1.18.2-1 ii libnuma1 2.0.16-1 ii librados216.2.11+ds-5 ii librbd1 16.2.11+ds-5 ii librdmacm1 48.0-1 ii python3 3.11.6-1 ii zlib1g 1:1.3.dfsg-3+b1
Bug#1055864: marked as pending in dh-make
Hi Faidon, On Mon, 2023-11-20 at 18:55 +, Baptiste Beauplat wrote: > https://salsa.debian.org/debian/dh-make/-/commit/0ff6224dfea6c4c1502bf62b2bf57702de77d7e7 I've made a mention of lowdown in the manpage example. Since it has very low adoption right now, I'll leave the reference to pandoc as well. I'll do a release of dh-make next week, including this modification. Thanks! -- Baptiste Beauplat signature.asc Description: This is a digitally signed message part
Bug#1042947: UDD: create a duck importer
Hi Lucas,
On Wed, 2023-10-25 at 20:57 +0200, Lucas Nussbaum wrote:
> On 08/08/23 at 06:42 +0200, Lucas Nussbaum wrote:
> > Hi Baptiste,
> >
> > On 07/08/23 at 22:07 +0200, Baptiste Beauplat wrote:
> > > Hi Lucas,
> > >
> > > On 2023-08-03 10:30, Lucas Nussbaum wrote:
> > > > duck-as-a-service (duck.debian.net) has been broken for a long
> > > > time,
> > > > and
> > > > the corresponding UDD importer is broken as well (see #949009,
> > > > #963887).
> > > > In the meantime, duck continued evolving (was rewritten?) and
> > > > is now
> > > > checking a lot more places for URLs.
> > > >
> > > > It would probably be useful to re-create a way to provide duck
> > > > results
> > > > as a service, based on UDD, similarly to what is done for
> > > > upstream or
> > > > lintian data.
> > > >
> > > > Ideally, this would be done in cooperation with the duck
> > > > maintainer
> > > > to
> > > > do the following changes:
> > > > - in duck, separate the logic to get URLs from sources, from
> > > > the
> > > > logic
> > > > to check those URLs (for example, allow dumping a list of
> > > > URLs, and
> > > > also using a list of URLs as source)
> > > > - in duck, provide machine-readable outputs (JSON?)
> > >
> > > Currently duck has two features which can help us:
> > >
> > > - The `-n` switch, which gets all URLs and prints them to stdout
> > > - The `-l filename` switch, which takes a file with one URL per
> > > line
> > > and checks them
> > >
> > > Theoretically, what's missing in only a `--json` switch, which
> > > would
> > > change the output from console/text to JSON.
> > >
> > > But, as I see it, the `-l` argument is limited in two aspects:
> > >
> > > - It provides only the URL, loosing the checker type which is
> > > used to
> > > select what kind of validation will be performed.
> > >
> > > For instance, a https://salsa.debian.org/rfrancoise/tmux.git of
> > > type
> > > VCS-Git would be tested as a standard URL in the `-l` context,
> > > instead
> > > of a git repository.
> > >
> > > - It requires a file
> > >
> > > I'm thinking of implementing a new JSON specific input format
> > > (`--input-json`?), including the two information, which would
> > > read from
> > > stdout instead of a file.
> > >
> > > The format would be as simple as:
> > >
> > > ```json
> > > [
> > > {"type": "VCS-Git",
> > > "url": "https://salsa.debian.org/rfrancoise/tmux.git;,
> > > "filename": "debian/control", # optional key
> > > "line_number": 10}, # optional key
> > > ...
> > > ]
> > > ```
> > >
> > > Following this logic, the output format for checking URLs would
> > > be the
> > > same, as to have `duck --json -n | duck --input-json` working.
> > >
> > > The JSON result would hold an additional dictionary for each URL
> > > entries
> > > named "result", described as follows:
> > >
> > > ```json
> > > [
> > > {"type": "VCS-Git",
> > > "url": "https://salsa.debian.org/rfrancoise/tmux.git;,
> > > "filename": "debian/control", # optional key
> > > "line_number": 10, # optional key
> > > "result": {
> > > "state": 0, # 0 for OK, 1 for Error, 2 for Information
> > > "detail": "Informative message",
> > > "certainty": "possible" # optional key
> > > }},
> > > ...
> > > ]
> > > ```
> > >
> > > Let me know what you think of it.
> >
> > That would be perfect!
> >
> > In the context of UDD, I will probably implement that as two
> > tables:
> > - one to store the mapping between source packages and urls
> > (source, version, url, type, filename, line_number)
> > which would be updated when a new source version gets uploaded
> > - one to store the status of urls
> > (url, type, result, timestamp of last check)
> > which would be updated with a retry policy to be defined
> >
> > I would not use (filename, line_number) in the input of the URL
> > testing part.
> > The reason for that design is that it will easily allow to gather
> > the
> > status for several versions of the package (testing + unstable +
> > experimental for example), while not duplicating the checks for
> > URLs.
>
> Just checking: did you make progress on this?
Sort of.
I could not see a clean way to add this feature without a total rewrite
of duck. So that's what I've started, and I'm making steady progress on
that front.
However, I have not started working on the json interface
implementation just yet.
I'll keep you posted once I have a working version of that.
Best,
--
Baptiste Beauplat
signature.asc
Description: This is a digitally signed message part
Bug#1020217: snapshot.debian.org: write a generic file driver supporting multiple backend (such as object-storage)
Hi Lucas, On Thu, 2023-09-21 at 18:26 +0200, Lucas Nussbaum wrote: > On 18/09/22 at 11:29 +0200, Baptiste Beauplat wrote: > > Having files stored into an object-like storage could improve cost > > and > > performence over the conventional storage that snapshot is > > currently > > using. (Currently using over 130 TB!) > > > > Multiple componants needs to access snapshot farm. The importer, > > the web > > app (if not redirected) and multiple other scripts. > > > > We should write a generic file driver to allow all those component > > to > > access/update/delete file from a config-defined backend. > > > > This driver would be usable in at least two langauges: ruby and > > python. > > I'm not sure what is the best course of action here. Some kind of > > bindings or maintaining two separate drivers. > > > > Note that there is also some C program as part for snapshot (the > > fsck > > program). > > > > I was thinking for writing at least two backend for the driver: > > > > - a standard flat filesystem storage (what we have currently) > > - an object-like storage. S3 would be a good candidate since a > > couple of > > opensource storage solution provide S3 compatible API. > > > > That would allow a two step transision: start using the driver, > > then > > switch the backend. > > I was wondering if you made some progress on this? > > Your plan looks very good. I agree that a S3 backend would make a lot > of > sense (usable both with self-hosted solutions like MinIO, or with > managed services). > > Let me know if I can help somehow. Unfortunately I have not made any progress regarding this feature, nor do I plan on working on it anytime soon (due to a lack of time). You're very welcome to have a go at it. Best, -- Baptiste Beauplat signature.asc Description: This is a digitally signed message part
Bug#1043317: duck: Please drop "parked domain" test
Hi Gregor, On Wed, 2023-08-09 at 03:21 +0200, gregor herrmann wrote: > I like duck and run it after each package build. > Unfortunately typically I get output from the wild-guess check for > some strings on websites where duck tells me that the upstream > homepage or the Debian BTS or a well-known license is a "parked > domain of for sale", and this test is almost always a false positive. > > Current example, package rex: > > I: debian/copyright:62: URL: > https://www.apache.org/licenses/LICENSE-2.0: INFORMATION > (Certainty:wild-guess) > Curl:0 HTTP:200 No error > Website seems to be outdated, is probably a parked domain or for > sale. Please update your links! > Matching regular expression(s): > m/\breplaced with\b/i > > I: debian/control: Homepage: https://www.rexify.org/: INFORMATION > (Certainty:wild-guess) > Curl:0 HTTP:200 No error > Website seems to be outdated, is probably a parked domain or for > sale. Please update your links! > Matching regular expression(s): > m/\breplace .* with\b/i > > I: debian/upstream/metadata:URL: https://github.com/RexOps/Rex.git: > INFORMATION (Certainty:wild-guess) > Curl:0 HTTP:200 No error > Website seems to be outdated, is probably a parked domain or for > sale. Please update your links! > Matching regular expression(s): > m/\breplace .* with\b/i > > I: debian/upstream/metadata:URL: https://github.com/RexOps/Rex: > INFORMATION (Certainty:wild-guess) > Curl:0 HTTP:200 No error > Website seems to be outdated, is probably a parked domain or for > sale. Please update your links! > Matching regular expression(s): > m/\breplace .* with\b/i > > > Checking for "deprecated" (on upstream websites which document > functions) or "replaced (by|with)" doesn't make any sense IMO … > Please just remove tese tests … There are a couple of different points I'd like to address in order to fix this issue. First, I agree with you, "replaced (by|with)" and "deprecated" are too generic not to trigger false positives. I'll be removing them from the list. Secondly, even if, as stated by the check certainty, the suggestion is at most a wild-guess, I would like to keep the test as it can still be useful to catch deprecated projets or links that moved on to another page. However, I want to have a way for users to filter the checks based on certainty. I'll be adding an option for that both in the cli arguments and the configuration file. Although, I'll keep the default to show all checks. Finally, the checks for obsoletes sites is currently at a certainty of wild-guess. I'll be bumping that to possible as, to the contrary of the parked test, its a list of well known deprecated sites, and virtually has no chance of false positive. Best, -- Baptiste Beauplat signature.asc Description: This is a digitally signed message part
Bug#1042947: UDD: create a duck importer
Hi Lucas,
On 2023-08-03 10:30, Lucas Nussbaum wrote:
> duck-as-a-service (duck.debian.net) has been broken for a long time,
> and
> the corresponding UDD importer is broken as well (see #949009,
> #963887).
> In the meantime, duck continued evolving (was rewritten?) and is now
> checking a lot more places for URLs.
>
> It would probably be useful to re-create a way to provide duck
> results
> as a service, based on UDD, similarly to what is done for upstream or
> lintian data.
>
> Ideally, this would be done in cooperation with the duck maintainer
> to
> do the following changes:
> - in duck, separate the logic to get URLs from sources, from the
> logic
> to check those URLs (for example, allow dumping a list of URLs, and
> also using a list of URLs as source)
> - in duck, provide machine-readable outputs (JSON?)
Currently duck has two features which can help us:
- The `-n` switch, which gets all URLs and prints them to stdout
- The `-l filename` switch, which takes a file with one URL per line
and checks them
Theoretically, what's missing in only a `--json` switch, which would
change the output from console/text to JSON.
But, as I see it, the `-l` argument is limited in two aspects:
- It provides only the URL, loosing the checker type which is used to
select what kind of validation will be performed.
For instance, a https://salsa.debian.org/rfrancoise/tmux.git of type
VCS-Git would be tested as a standard URL in the `-l` context, instead
of a git repository.
- It requires a file
I'm thinking of implementing a new JSON specific input format
(`--input-json`?), including the two information, which would read from
stdout instead of a file.
The format would be as simple as:
```json
[
{"type": "VCS-Git",
"url": "https://salsa.debian.org/rfrancoise/tmux.git;,
"filename": "debian/control", # optional key
"line_number": 10}, # optional key
...
]
```
Following this logic, the output format for checking URLs would be the
same, as to have `duck --json -n | duck --input-json` working.
The JSON result would hold an additional dictionary for each URL
entries
named "result", described as follows:
```json
[
{"type": "VCS-Git",
"url": "https://salsa.debian.org/rfrancoise/tmux.git;,
"filename": "debian/control", # optional key
"line_number": 10, # optional key
"result": {
"state": 0, # 0 for OK, 1 for Error, 2 for Information
"detail": "Informative message",
"certainty": "possible" # optional key
}},
...
]
```
Let me know what you think of it.
> Then UDD could process source packages to extract URLs, check those
> URLs
> on a regular basis (similarly to what is done for lintian), and
> publish/export the results in all relevant places.
Best,
--
Baptiste Beauplat
signature.asc
Description: This is a digitally signed message part
Bug#963887: UDD: 'duck' importer broken since 2020-05-25
Hi Lucas, On Thu, 2023-08-03 at 10:38 +0200, Lucas Nussbaum wrote: > I submitted #1042947 to discuss re-creating a UDD duck importer, > using the same model as the lintian importer. > > @Baptiste: could you take a look? There would be a few changes on the > duck side that would make it much easier. Sure, I'll have a look before next week. Best, -- Baptiste Beauplat signature.asc Description: This is a digitally signed message part
Bug#1040992: Add support for oldoldstable
Package: distro-info Severity: wishlist Dear Maintainer, It would be nice to have support for getting the associated codename for oldoldstable as already implemented for oldstable, stable, testing and unstable. Let me know if you would be willing to include this feature into distro-info, I would be interested in providing the associated patch/MR. Best, -- Baptiste Beauplat signature.asc Description: This is a digitally signed message part
Bug#1035761: grub2: French translation
Package: grub2 Version: N/A Severity: wishlist Tags: patch l10n Dear Maintainer, Please find attached the french debconf template translation, proofread by the debian-l10n-french mailing list contributors. This file should be put as debian/po/fr.po in your package build tree. Thanks for maintaining grub2. Baptiste -- System Information: Debian Release: 11.6 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-21-amd64 (SMP w/2 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled # translation of fr.po to French # Translation of grub2 debconf templates to French # Copyright (C) 2008-2010 Debian French l10n # This file is distributed under the same license as the grub2 package. # # Christian Perrier , 2007, 2008, 2009, 2010, 2011, 2014. # Baptiste Jammet , 2017, 2023. msgid "" msgstr "" "Project-Id-Version: fr\n" "Report-Msgid-Bugs-To: gr...@packages.debian.org\n" "POT-Creation-Date: 2023-04-23 20:27+\n" "PO-Revision-Date: 2023-04-26 19:30+0200\n" "Last-Translator: Baptiste Jammet \n" "Language-Team: French \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Lokalize 20.12.0\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid "Chainload from menu.lst?" msgstr "Faut-il enchaîner le chargement depuis menu.lst ?" #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid "GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub." msgstr "Une installation ancienne de GRUB a été détectée dans /boot/grub." #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid "" "In order to replace the Legacy version of GRUB in your system, it is " "recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot image " "from your existing GRUB Legacy setup. This step can be automatically " "performed now." msgstr "" "Afin de remplacer cette installation, il est recommandé de modifier /boot/" "grub/menu.lst pour charger GRUB 2 depuis l'installation standard de GRUB " "(« chainload »). Veuillez choisir si vous souhaitez effectuer cette " "modification." #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid "" "It's recommended that you accept chainloading GRUB 2 from menu.lst, and " "verify that the new GRUB 2 setup works before it is written to the MBR " "(Master Boot Record)." msgstr "" "Il est recommandé de choisir cette option pour pouvoir confirmer le bon " "fonctionnement de GRUB 2 avant de l'installer directement sur le secteur " "d'amorçage (MBR : « Master Boot Record »)." #. Type: boolean #. Description #: ../grub-pc.templates.in:2001 msgid "" "Whatever your decision, you can replace the old MBR image with GRUB 2 later " "by issuing the following command as root:" msgstr "" "Quel que soit votre choix, vous pourrez, plus tard, remplacer l'ancien " "secteur d'amorçage par GRUB 2 avec la commande suivante, exécutée avec les " "privilèges du superutilisateur :" #. Type: multiselect #. Description #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001 msgid "GRUB install devices:" msgstr "Périphériques sur lesquels installer GRUB :" #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 msgid "" "The grub-pc package is being upgraded. This menu allows you to select which " "devices you'd like grub-install to be automatically run for, if any." msgstr "" "Le paquet grub-pc est en cours de mise à jour. Ce menu permet de choisir " "pour quels périphériques vous souhaitez exécuter la commande grub-install " "automatiquement." #. Type: multiselect #. Description #: ../grub-pc.templates.in:3001 msgid "" "Running grub-install automatically is recommended in most situations, to " "prevent the installed GRUB core image from getting out of sync with GRUB " "modules or grub.cfg." msgstr "" "Il est en général recommandé d'exécuter grub-install automatiquement, afin " "d'éviter la situation où l'image de GRUB est désynchronisée avec les modules " "de GRUB ou le fichier grub.cfg." #. Type: multiselect #. Descrip
Bug#1033666: icinga2-common: wrong executable in /usr/share/icinga2/include/plugins-contrib.d/systemd.conf
Control: forwarded -1 https://github.com/Icinga/icinga2/issues/9547 On 2023-03-29 20:32, Sebastiaan Couwenberg wrote: > On 3/29/23 20:07, Andreas B. Mundt wrote: >> the configuration in >> '/usr/share/icinga2/include/plugins-contrib.d/systemd.conf' >> contains a wrong executable in line 4: >> >> command = [ PluginContribDir + "/check_systemd.py" ] >> >> The plugin's path is '/usr/lib/nagios/plugins/check_systemd' (no .py) >> [1]. > > That's a divergence from upstream in the Debian package: > > > https://salsa.debian.org/python-team/packages/monitoring-plugins-systemd/-/blob/debian/master/debian/monitoring-plugins-systemd.install The monitoring-plugins-systemd package is actually following upstream, check_systemd.py is supposed to be installed as check_systemd. > > We'll have to patch the CheckCommand like check_postgres: > > > https://salsa.debian.org/nagios-team/icinga2/-/blob/master/debian/patches/postgres-checkcommand.patch There is an upstream issue for that, but unfortunately, both yayayayaka and myself refused to sign Icinga2 CLA, leaving the trivial fix for someone else. -- Baptiste Beauplat - lyknode
Bug#1031335: lintian: Please backport 2.116.3 to bullseye
Package: lintian Severity: wishlist Dear maintainer, At mentors.debian.net, we use the bpo version of lintian to run on uploaded packages. But this 2.115.1 version report the latest standards-version as unknown. Could we please have a bpo build for 2.116.3? Thanks, -- Baptiste Beauplat - lyknode
Bug#1020531: dia: creating a text element kills all GUI fonts
Hello, I am facing the same bug on bookworm, and removing ~/.dia/ does *not* solve the issue for me. Sometimes simply opening and selecting a text element causes this problem, that is, all text disappear in the GUI / menus. Sometimes there is an additional consequence: several text elements of the diagram also disappear, but I just have to zoom or unzoom to get them back. It's somewhat random and not always reproducible, but it happens very often (typically within 15 seconds of opening the document and working in it). Information on my system: - dia version: 0.97.3+git20220525-5 - libfreetype6 version: 2.12.1+dfsg-4 - Desktop environment: i3 It looks related to bug #1025239 (same effect but different cause). Below are example errors spewed out by Dia: (dia:641138): Pango-WARNING **: 14:21:06.557: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 57994.88671875' (dia:641138): Pango-WARNING **: 14:21:06.557: font_face status is: error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:06.557: scaled_font status is: error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:07.012: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 50745.3642578125' (dia:641138): Pango-WARNING **: 14:21:07.012: font_face status is: error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:07.012: scaled_font status is: error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:07.014: failed to create cairo scaled font, expect ugly output. the offending font is 'FreeSerif 50745.3642578125' (dia:641138): Pango-WARNING **: 14:21:07.014: font_face status is: error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:07.014: scaled_font status is: error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:1067, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:408, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:513, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:408, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:513, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:460, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:434, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:984, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:408, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:513, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:460, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:677, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:408, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:513, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:408, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:513, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:460, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:07.014: ../lib/renderer/diacairo-renderer.c:539, error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:08.799: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 50745.3642578125' (dia:641138): Pango-WARNING **: 14:21:08.799: font_face status is: error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:08.799: scaled_font status is: error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:08.801: failed to create cairo scaled font, expect ugly output. the offending font is 'FreeSerif 50745.3642578125' (dia:641138): Pango-WARNING **: 14:21:08.801: font_face status is: error occurred in libfreetype (dia:641138): Pango-WARNING **: 14:21:08.801: scaled_font status is: error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:08.805: ../lib/renderer/diacairo-renderer.c:1067, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **: 14:21:08.805: ../lib/renderer/diacairo-renderer.c:408, error occurred in libfreetype (dia:641138): DiaCairo-WARNING **:
Bug#1023540: snapshot.debian.org: 504 Gateway Time-out
Hi,
The observed 504 errors are coming from either haproxy or varnish,
stopping the request because snapshot take too much time to reply
(typically a query on gcc or linux take over a minute to complete).
While investigating this issue, I discovered that snapshot is doing way
too much SQL queries to reply to /packages/{package}/{version}
requests, especially on packages with a lot of binary files.
I've optimized the code and got very promising results (down from ~2000
SQL queries to 4 and from over a minute to 2s).
I've created an MR here:
https://salsa.debian.org/snapshot-team/snapshot/-/merge_requests/9
I'll let you know when this is merged and deployed.
--
Baptiste Beauplat
signature.asc
Description: This is a digitally signed message part
Bug#1025722: duck fails with 'Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at /usr/share/duck/lib/checks/patch_files.pm line 101'
Hi Gregor,
Thanks for catching this.
On Thu, 2022-12-08 at 00:45 +0100, gregor herrmann wrote:
> As of today, duck (called in any source package directory) fails with
>
> Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at
> /usr/share/duck/lib/checks/patch_files.pm line 101'
>
> 92 # iterate over all patchdirs, process all files found
> 93 foreach my $patchdir (@patchdirs) {
> 94 my $dirhandle = dir($patchdir)->open;
> 95
> 96 while (my $patchfile = $dirhandle->read) {
> 97 open my $pf, "<", $patchdir . "/" .
> $patchfile;
> 98
> 99 my @pf_raw = <$pf>;
> 100
> 101 close($pf);
>
> This may or may not be caused by a recent change in src:perl [0],
> hence
> cc'in the perl maintainers
Regardless of if it's indeed a problem introduced by the new perl
upload, I'll fix it in the code. The read() will always return at the
very least `.` and `..`, and those should definitly be skipped in that
context.
--
Baptiste Beauplat
signature.asc
Description: This is a digitally signed message part
Bug#1020989: trafficserver: failed to load plugin
Waiting for your answer, I lower the severity of this bug to avoid it being removed from archive. Without any further news, this bug might be closed by the end of the month Best, Jean Baptiste On 10/24/22 10:39, Jean Baptiste Favre wrote: Hello, Made some tests today: loading plugin works well for me, with a default Debian install. Please provide some more details on you issue: * which plugin do you use? Is there any specific configuration? * do you have some trafficserver's logs to provide? A possible workaround would be to tune the RUNDI variable in /etc/default/trafficserver. Please try this and update this bug. Best, Jean Baptiste On 10/21/22 16:51, Jean Baptiste Favre wrote: Hello, Thanks for your report. After a quick look, I couldn't find any easy solution to this issue. Will have a deeper as soon as possible. Best, Jean Baptiste On 9/30/22 09:05, YunQiang Su wrote: Package: trafficserver Version: 9.1.3+ds-2 Severity: grave Since ATS 9, it tries to load plugins to /run/trafficserver, and then load them, and it asks for the plugins to have execution permission. While the /run filesystem on Debian is mounted with noexec option.
Bug#1020989: trafficserver: failed to load plugin
Hello, Made some tests today: loading plugin works well for me, with a default Debian install. Please provide some more details on you issue: * which plugin do you use? Is there any specific configuration? * do you have some trafficserver's logs to provide? A possible workaround would be to tune the RUNDI variable in /etc/default/trafficserver. Please try this and update this bug. Best, Jean Baptiste On 10/21/22 16:51, Jean Baptiste Favre wrote: Hello, Thanks for your report. After a quick look, I couldn't find any easy solution to this issue. Will have a deeper as soon as possible. Best, Jean Baptiste On 9/30/22 09:05, YunQiang Su wrote: Package: trafficserver Version: 9.1.3+ds-2 Severity: grave Since ATS 9, it tries to load plugins to /run/trafficserver, and then load them, and it asks for the plugins to have execution permission. While the /run filesystem on Debian is mounted with noexec option. OpenPGP_signature Description: OpenPGP digital signature
Bug#1020989: trafficserver: failed to load plugin
Hello, Thanks for your report. After a quick look, I couldn't find any easy solution to this issue. Will have a deeper as soon as possible. Best, Jean Baptiste On 9/30/22 09:05, YunQiang Su wrote: Package: trafficserver Version: 9.1.3+ds-2 Severity: grave Since ATS 9, it tries to load plugins to /run/trafficserver, and then load them, and it asks for the plugins to have execution permission. While the /run filesystem on Debian is mounted with noexec option. OpenPGP_signature Description: OpenPGP digital signature
Bug#1020219: snapshot.debian.org: change db schema to allow NULL value representing current run on node.last
Package: snapshot.debian.org Severity: normal Transcribing weasel suggestion from IRC: Snapshot could use NULL value on node.last to represent the current run. Since most files do not change between runs, that would significantly reduce the number of UPDATE needed for an import run, speeding up the process. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#1020217: snapshot.debian.org: write a generic file driver supporting multiple backend (such as object-storage)
Package: snapshot.debian.org Severity: normal Having files stored into an object-like storage could improve cost and performence over the conventional storage that snapshot is currently using. (Currently using over 130 TB!) Multiple componants needs to access snapshot farm. The importer, the web app (if not redirected) and multiple other scripts. We should write a generic file driver to allow all those component to access/update/delete file from a config-defined backend. This driver would be usable in at least two langauges: ruby and python. I'm not sure what is the best course of action here. Some kind of bindings or maintaining two separate drivers. Note that there is also some C program as part for snapshot (the fsck program). I was thinking for writing at least two backend for the driver: - a standard flat filesystem storage (what we have currently) - an object-like storage. S3 would be a good candidate since a couple of opensource storage solution provide S3 compatible API. That would allow a two step transision: start using the driver, then switch the backend. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#1020216: snapshot.debian.org: move to a stronger hash
Package: snapshot.debian.org Severity: normal Snapshot uses SHA-1 hash to refer and deduplicate files. That hash is considered insecure and should be deprecated from snapshot. It should be replaced by secure hash function such as SHA-256, SHA-512 or BLAKE2. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#1019553: FTBFS: ts_file_io
Hello Adam, Thanks for your report. I've unable to reproduce the build failure as of now, using both a docker image and sbuild on my laptop (amd64 only). The failing test simply tries to open /etc/hosts (which should be present inside chroot), read it and look for the string localhost inside. I reported the issue upstream [1] [1]: https://github.com/apache/trafficserver/issues/9088 On 9/11/22 21:51, Adam Borowski wrote: Source: trafficserver Version: 9.1.3+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: kilob...@angband.pl Hi! I'm afraid that your package fails to build with a test failure; confirmed on amd64 arm64. FAIL: test_tscore = sizeof(string) = 32 sizeof(Derived) = 40 ~~~ test_tscore is a Catch v2.13.8 host application. Run with -? for options --- ts_file_io --- unit_tests/test_ts_file.cc:49 ... unit_tests/test_ts_file.cc:54: FAILED: REQUIRE( ec.value() == 0 ) with expansion: 2 == 0 === test cases: 90 | 89 passed | 1 failed assertions: 1325 | 1324 passed | 1 failed FAIL test_tscore (exit status: 1) -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (490, 'testing'), (250, 'unstable'), (201, 'experimental') merged-usr: no Architecture: arm64 (aarch64) Kernel: Linux 5.19.0-1-arm64 (SMP w/6 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) OpenPGP_signature Description: OpenPGP digital signature
Bug#1017836: python-debian: Copyright doesn't throw NotMachineReadableError anymore
Source: python-debian
Version: 0.1.46
Severity: normal
Dear Maintainer,
When passing a non-dep5 copyright file to Copyright, it use to throw
NotMachineReadableError, which is quite useful to categorise the file as
such. It doesn't do that anymore, throwing instead a generic ValueError.
To reproduce:
$ curl -SLO https://sources.debian.org/data/main/h/hello/2.10-2/debian/copyright
$ python3 -c "from debian.copyright import Copyright;
Copyright(open('copyright'))"
With python3-debian from bullseye:
```
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/debian/copyright.py", line 155, in
__init__
raise NotMachineReadableError('no paragraphs in input')
```
With python3-debian from unstable and testing:
```
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/debian/copyright.py", line 165, in
__init__
self.__file = parse_deb822_file(sequence=sequence, encoding=encoding)
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/parsing.py", line
3091, in parse_deb822_file
deb822_file = Deb822FileElement(LinkedList(tokens))
File "/usr/lib/python3/dist-packages/debian/_util.py", line 159, in __init__
self.extend(values)
File "/usr/lib/python3/dist-packages/debian/_util.py", line 272, in extend
for v in values:
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/_util.py", line
103, in _impl
for token in token_stream:
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/_util.py", line
103, in _impl
for token in token_stream:
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/parsing.py", line
2968, in _build_field_with_value
for token_or_element in buffered_stream:
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/_util.py", line
142, in __next__
return next(self._stream)
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/_util.py", line
103, in _impl
for token in token_stream:
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/parsing.py", line
2904, in _build_value_line
for token in buffered_stream:
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/_util.py", line
142, in __next__
return next(self._stream)
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/_util.py", line
103, in _impl
for token in token_stream:
File "/usr/lib/python3/dist-packages/debian/_deb822_repro/parsing.py", line
3027, in _abort_on_error_tokens
raise ValueError('Syntax or Parse error on the line:
"{error_as_text}"'.format(
ValueError: Syntax or Parse error on the line: "This is the Debian GNU
prepackaged version of the FSF's GNU hello\n"
```
Best,
--
Baptiste Beauplat - lyknode
signature.asc
Description: PGP signature
Bug#1017479: python-django-celery-beat: Missing unpackaged python3-tzdata dependency
Source: python-django-celery-beat Version: 2.3.0-1 Severity: normal Dear Maintainer, django-celery-beat declares a dependency to tzdata[1] in its requirements/default.txt however this package is not available in Debian. Because of this, tzdata will be downloaded from the internet if a project declare a dependency to django-celery-beat even if already installed using Debian packages. From what I can see, tzdata is only a copy of the timezone info, already available from the tzdata package and it is only used by upstream to ensure tzdata info are installed on the target system (no trace of an import in the source). Rather than packaging the python version of tzdata, I think asking upstream to remove the "obvious" dependency could be a cleaner solution. Patching the requirement to drop the dependency could also work fine, IMHO. Best, -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled [1]: https://pypi.org/simple/tzdata/ -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#1016412: dh-make: manpage.1.ex: Incorrect formatting for dash
On 2022/07/31 02:04 PM, Alejandro Colomar (man-pages) wrote:
> On 7/31/22 13:49, Baptiste Beauplat wrote:
> > Hi Alejandro,
> >
> > On 2022/07/31 12:35 PM, Alejandro Colomar wrote:
> > > The template page 'manpage.1.ex' uses '-' instead of '\-' for a
> > > dash that should be a Latin minus sign (as it's in the context of
> > > command options). Using '-' would produce a hyphen, which if
> > > copy, wouldn't be interpreted correctly by a command.
> > >
> > > The offending line in the file is 41:
> > >
> > > options starting with two dashes ('-')
> >
> > When I run the following command on the manpage :
> >
> > man ./manpage.1.ex | xxd
> >
> > The resulting text from the dash line 41 is converted to the correct 2d
> > minus ascii char.
> >
> > The same is true for the two examples following that text, which are
> > correctly shown as \-\- in the source.
> >
> > I am missing something? Or maybe the fact that this text is in a .SH
> > section make it work correctly?
>
> Upstream groff(1) renders '-' and '\-' differently, as they should.
> However, since many manual pages in existence are incorrect, and they use
> '-' when they should use '\-', Debian modifies the behavior by downgrading
> hyphens into Latin minus sign.
>
> Let's fix the page in the hope that Debian can some day remove that
> workaround.
>
> See the relevant part of :
>
> . \" Debian: Strictly, "-" is a hyphen while "\-" is a minus sign, and the
> . \" former may not always be rendered in the form expected for things like
> . \" command-line options. Uncomment this if you want to make sure that
> . \" manual pages you're writing are clear of this problem.
> . if '\*[.T]'utf8' \
> .char - \[hy]
Oh wow, I was not aware of this Debian-specific behaviour. Sure, let's
do this the correct way :)
--
Baptiste Beauplat - lyknode
signature.asc
Description: PGP signature
Bug#1016412: dh-make: manpage.1.ex: Incorrect formatting for dash
Hi Alejandro,
On 2022/07/31 12:35 PM, Alejandro Colomar wrote:
> The template page 'manpage.1.ex' uses '-' instead of '\-' for a
> dash that should be a Latin minus sign (as it's in the context of
> command options). Using '-' would produce a hyphen, which if
> copy, wouldn't be interpreted correctly by a command.
>
> The offending line in the file is 41:
>
> options starting with two dashes ('-')
When I run the following command on the manpage :
man ./manpage.1.ex | xxd
The resulting text from the dash line 41 is converted to the correct 2d
minus ascii char.
The same is true for the two examples following that text, which are
correctly shown as \-\- in the source.
I am missing something? Or maybe the fact that this text is in a .SH
section make it work correctly?
Best,
--
Baptiste Beauplat - lyknode
signature.asc
Description: PGP signature
Bug#1006724: network-manager: DNS information not cleaned correctly when switching of networks
Hello, I can confirm that this bug still happens with Network-Manager 1.38.2 in bookworm. Upstream has recently merged the fix mentioned by Visti, and has backported it to 1.36 and 1.38. So, here is the recap: - the bug has been introduced in 1.35.1-dev - the bug has been fixed in 1.39.8-dev - the backported fix will be released in 1.38.4 (not yet released) - the backported fix will be released in 1.36.6 (not yet released) For bookworm, Debian can either backport the patch manually, or wait for 1.38.4 to be released and pull that in. I notice that bullseye-backports has 1.38.0, it will probably also need an update or a manual backport. Thanks, Baptiste
Bug#1013812: (no subject)
Control: fixed 1013812 9.1.2+ds-13 OpenPGP_signature Description: OpenPGP digital signature
Bug#1013671: (no subject)
Setting video output to X11 video solve the issue. In terms of configuration file, you have to add following line in ~/.config/vlc/vlcrc vout=xcb_x11 Best, Jean Baptiste OpenPGP_signature Description: OpenPGP digital signature
Bug#1013921: RM: trafficserver [ppc64el] -- ANAIS; build-dependency missing for ppc64el
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear ftp-master, trafficserver depends on libluait which is broken for ppc64el. I can't circumvent this dependency and would like to drop trafficserver from unstable and testing for this architecture. The removal will also allow to close an RC bug #1013812 Note: this was a request for a partial removal from testing, converted in one for unstable -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAmK5nZZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99 hzdVSA//UG6SCYJ7MYhH7FMapXFNcayEsZFGEHk4lwBeVOIAIbOSzRc2ZukbGF0L TsNCUIBFtBgmqv7gFwKQas2UOPw0kVb+bURaQHZ298xXczxh40HvpVpZTZNeyGeh 1qOBpKJpRebMPJDKigUr/SQOviPvQt8TNLvxGP/bEgHtuTIqb1NsVw1181LWqYRQ ra32o7Zo7DtE0o+JiFVar7LkejEoTP+fNxaqJX7DOkzRIYW2NmGg175nAXERW4CK FvHQ1LieAG6LL2bvFVk0nIkkd975nBbo5GF5HD6kMPOn2fFNxTUf0ORFkz2ZBd1Z MEvLeggB5eG1/KyGNaL1NpJ047mGZg8L1mRrZZ09BBtFokmc2capUZtPO7UL+mWh 8GGh3bTpUerjEELR7XZskNZqhHjIJfONI+SfgOhxcefzCWvZ3vaRQ00Mwu+pNOrk HNwdhwHRe33hxtCxRCPX27Oc9eYapR1ESuxBa12LUFf2O3th4Bn9OWhOCK/d7XHG 7oJKhBuJ26VjRCTramBbET4QssAKp+5+FEe9CwNKVx+jT1EtFOfR4RFhGB/lZgjK wcZnGL1Ojm0rtx/iskDKS1CecUXnD8iv5pxORorQhZXvdNe6E9TUCsq1g/5pMVW0 HDQpRD+AMrusB7eAMntYMRUyJogDjqun6UA+4WGc/NOjtvZZyj4= =mJ4A -END PGP SIGNATURE-
Bug#1013671: vlc: Video display in a separate window, even if 'integrate video in main video' is enabled
Package: vlc Version: 3.0.17.4-4 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, After upgrading vlc in unstable, video is always displayed in a separate window, even if the 'Integrate video in interface' is ticked. It looks like this option isn't taken into account at all in 3.0.17.4-4. Downgrading vlc to 3.0.17.4-3 restores the normal behaviour. - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vlc depends on: ii vlc-bin 3.0.17.4-4 ii vlc-plugin-base 3.0.17.4-4 ii vlc-plugin-qt3.0.17.4-4 ii vlc-plugin-video-output 3.0.17.4-4 Versions of packages vlc recommends: ii vlc-l10n 3.0.17.4-4 ii vlc-plugin-access-extra3.0.17.4-4 ii vlc-plugin-notify 3.0.17.4-4 ii vlc-plugin-samba 3.0.17.4-4 pn vlc-plugin-skins2 ii vlc-plugin-video-splitter 3.0.17.4-4 ii vlc-plugin-visualization 3.0.17.4-4 Versions of packages vlc suggests: pn vlc-plugin-fluidsynth pn vlc-plugin-jack pn vlc-plugin-pipewire pn vlc-plugin-svg Versions of packages libvlc-bin depends on: ii libc62.33-7 ii libvlc5 3.0.17.4-4 Versions of packages libvlc5 depends on: ii libc62.33-7 ii libvlccore9 3.0.17.4-4 Versions of packages libvlc5 recommends: ii libvlc-bin 3.0.17.4-4 Versions of packages vlc-bin depends on: ii libc6 2.33-7 ii libvlc-bin 3.0.17.4-4 ii libvlc5 3.0.17.4-4 Versions of packages vlc-plugin-access-extra depends on: ii libc62.33-7 ii libsrt1.4-gnutls 1.4.4-4+b1 ii libvlccore9 [vlc-plugin-abi-3-0-0f] 3.0.17.4-4 ii libvncclient10.9.13+dfsg-4 ii libxcb-composite01.14-3 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 Versions of packages vlc-plugin-base depends on: ii liba52-0.7.4 0.7.4-20 ii libarchive13 3.6.0-1 ii libaribb24-0 1.0.3-2 ii libasound2 1.2.6.1-2+b1 ii libass9 1:0.16.0-1 ii libavahi-client3 0.8-6 ii libavahi-common3 0.8-6 ii libavc1394-0 0.5.4-5 ii libavcodec58 7:4.4.2-1+b3 ii libavformat587:4.4.2-1+b3 ii libavutil56 7:4.4.2-1+b3 ii libbluray2 1:1.3.1-2 ii libc62.33-7 ii libcairo21.16.0-5 ii libcddb2 1.3.2-7 ii libchromaprint1 1.5.1-2+b1 ii libdav1d61.0.0-2 ii libdbus-1-3 1.14.0-1 ii libdc1394-25 2.2.6-4 ii libdca0 0.0.7-2 ii libdvbpsi10 1.3.3-1 ii libdvdnav4 6.1.1-1 ii libdvdread8 6.1.3-1 ii libebml5 1.4.2-2 ii libfaad2 2.10.0-2 ii libflac8 1.3.4-2 ii libfontconfig1 2.13.1-4.4 ii libfreetype6 2.12.1+dfsg-3 ii libfribidi0 1.0.8-2.1 ii libgcc-s112.1.0-4 ii libgcrypt20 1.10.1-2 ii libglib2.0-0 2.72.2-2 ii libgnutls30 3.7.6-2 ii libgpg-error01.45-2 ii libharfbuzz0b2.7.4-1+b1 ii libixml101:1.8.4-2 ii libjpeg62-turbo 1:2.1.2-1 ii libkate1 0.4.1-11 ii liblirc-client0 0.10.1-7 ii liblua5.2-0 5.2.4-2 ii libmad0 0.15.1b-10 ii libmatroska7 1.6.3-2 ii libmpcdec6 2:0.1~r495-2 ii libmpeg2-4 0.5.1-9 ii libmpg123-0 1.29.3-1 ii libmtp9 1.1.19-1 ii libncursesw6 6.3+20220423-2 ii libnfs13 4.0.0-1 ii libogg0 1.3.5-1 ii libopenmpt-modplug1 0.8.9.0-openmpt1-2 ii libopus0 1.3.1-2 ii libpng16-16 1.6.37-5 ii libpostproc557:4.4.2-1+b3 ii
Bug#1012808: git-review 2.2 is not compatible with OpenSSH 9.X (scp breaking change)
Package: git-review Version: 2.2.0-1 Severity: important Dear Maintainer, While using git-review on Bookworm, I couldn't perform the initial setup: $ git review -s -v Running: scp -P29418 usern...@review.opendev.org:hooks/commit-msg .git/hooks/commit-msg Problems encountered installing commit-msg hook The following command failed with exit code 255 "scp -P29418 usern...@review.opendev.org:hooks/commit-msg .git/hooks/commit-msg" --- subsystem request failed on channel 0 scp: Connection closed --- Running the scp command manually yields the same error. This is likely caused by a breaking change in scp behaviour introduced in OpenSSH 9.X The upstream project already has a fix for this issue: https://opendev.org/opendev/git-review/commit/5bfaa4a6f355a6820fe16c1aea77a01ba7b97eaa Updating the git-review package to version 2.3 should be enough to fix this issue. Thanks, Baptiste -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git-review depends on: ii git 1:2.35.1-1 ii python3 3.10.4-1+b1 ii python3-requests 2.27.1+dfsg-1 ii python3-six 1.16.0-3 git-review recommends no packages. git-review suggests no packages. -- no debconf information
Bug#1011308: Your mail
Hello Paul, Thanks for the info. I just uploaded a new release of the package using libluajit2-5.1-dev as build-deps. Best, Jean Baptiste On 6/9/22 12:45, Paul Gevers wrote: Control: severity -1 normal Hi Jean, On Thu, 2 Jun 2022 21:19:14 +0200 Jean Baptiste Favre wrote: The bug is currently fixed in trafficserver 9.1.2+ds-7 into unstable. Due to the ongoing openssl transition, its migration to testing is however blocked. I'll continue to monitor package status to prevent it from being removed from testing if possible. Thanks for fixing this bug. However, in the mean time the maintainer of luajit found an alternative solution (by introducing an alternative luajit source package called luajit2). See transition bug #1012362). So, if you want to you can add support for luajit on ppc64el back to your package. Sorry for the extra work this bug caused, but when I filed it it wasn't clear on what timescale this would happen and if it would work out. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1011308: (no subject)
The bug is currently fixed in trafficserver 9.1.2+ds-7 into unstable. Due to the ongoing openssl transition, its migration to testing is however blocked. I'll continue to monitor package status to prevent it from being removed from testing if possible. Best, Jean Baptiste OpenPGP_signature Description: OpenPGP digital signature
Bug#1012051: ITP: python-qpageview -- qpageview provides a page based document viewer widget for Qt5/PyQt5
Package: wnpp Severity: wishlist Owner: Jean Baptiste Favre X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-qpageview Version : 0.6.2 Upstream Author : Wilbert Berendsen * URL : https://github.com/frescobaldi/qpageview * License : GPL Programming Lang: Python Description : qpageview provides a page based document viewer widget for Qt5/PyQt5 qpageview is a versatile View widget with many optional mixin classes to cater for anything between basic or powerful functionality while preserving performances displaying large PDF document, rendering in a background thread with smart priority control. Qpageview was previously part of Frescobaldi. It has been removed from Frescobaldi 3.2 to be managed as a separate project and will become a dependency for future Frescobaldi Debian packages. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAmKTZIdfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99 hzdycA//Tzrzyol1eQB/azQc4AC/Mad33gJKKG7hoAmeLgXtUPZ/1F3YlD3fywFV iYHnxtSNXsRmmIFYKOkzd78sV0EpM0FDzMCHRkm35Kgz8A04D93H1CG3a4QbFA0D vX9Z8OkDbiE/ifEqfB9xe7zdtjKX+YIDa9zRvKEAaGB9spW71vwTQvmQIctqoZkj inJNbeVl0j490A3e1cLlF+i6iMyfacQChn6QrG+2qQt5JrXV+Gj074ymW+D//GLs Xd776oiwa4BuWPHe9wfGV5T3dJh0RrmbUYU6kaSn2YHXaifOhwxUYaihv5g7FQLr cwQdai6DHFsHKHK05YFmDrrp9an0iKvMQNaJgISeSxLh9hEVTfn8JuUnSbZd5bUK N1lGFW86zo957pACPz5yRjMmWy3gntyq3Wm24CXkqFsBKsPY6evRoJJsIPvGvoAs DnqGiZt8nLwsYh9AxUiOISIU4xEPTtZWBJseetPcauDV8wgdOwtwaZJ1Nqp18u3m OGrOCQ3W34NcYegAQJWhV+NENDw8S+P4VBR7hOsLNUkOb8YZKKbCGyNrK6t53beW s206itcAdN2Qdcf3u4btkXrIfLpdArwhu9AUJRXPsYYcJPGuXmjtWVHsdYCWE/cc tu1h1Yi+FUdyLO/hcq6mlQYhrbc+Ym+FmK9oOn3mPjg76gi/PyM= =+5ZH -END PGP SIGNATURE-
Bug#1011308: Bug#1004511 closed by Debian FTP Masters (reply to Jean Baptiste Favre ) (Bug#1004511: fixed in trafficserver 9.1.2+ds-2)
reopen 1004511 fixed 1011308 9.1.2+ds-3 On Sat, 21 May 2022 13:18:09 +0200 Paul Gevers wrote: Control: reopen 1004511 Control: fixed 1011308 9.1.2+ds-2 On 21-05-2022 11:51, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the ftp.debian.org package: > > #1004511: RM: luajit [ppc64el] -- ROP; segfaults > > It has been closed by Debian FTP Masters (reply to Jean Baptiste Favre ). The upload of trafficserver closed the wrong bug. Paul Referenced the wrong bug again (missed the first reopen message). Sorry for the noise Jean Baptiste OpenPGP_signature Description: OpenPGP digital signature
Bug#1008655: debconf: French translation
Package: debconf
Version: 1.5.79
Severity: wishlist
Tags: patch l10n
Dear Maintainer,
Please find attached the updated debconf french translation,
proofread by the debian-l10n-french mailing list contributors.
This file should be put as po/fr.po in your package build tree.
Thanks for maintaining debconf.
Baptiste
# translation of fr.po to French
# debconf fr.po
# Copyright (C) 2000, 2005 Free Software Foundation, Inc.
#
# Vincent Renardias , 2000.
# Martin Quinson , 2000,2001,2002.
# Steve Petruzzello , 2012.
# Christian Perrier , 2013.
# Baptiste Jammet , 2017, 2019, 2021.
msgid ""
msgstr ""
"Project-Id-Version: debconf_1.5.79\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-10-24 12:27+\n"
"PO-Revision-Date: 2021-11-27 08:20+0100\n"
"Last-Translator: Baptiste Jammet \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: Lokalize 2.0\n"
#: ../Debconf/AutoSelect.pm:89
#, perl-format
msgid "falling back to frontend: %s"
msgstr "Utilisation de l'interface %s en remplacement"
#: ../Debconf/AutoSelect.pm:97
#, perl-format
msgid "unable to initialize frontend: %s"
msgstr "Impossible d'initialiser l'interface : %s"
#: ../Debconf/AutoSelect.pm:103
#, perl-format
msgid "Unable to start a frontend: %s"
msgstr "Impossible de démarrer l'interface : %s"
#: ../Debconf/Config.pm:131
msgid "Config database not specified in config file."
msgstr ""
"Le fichier de configuration n'indique pas l'emplacement de la base de "
"données des réglages."
#: ../Debconf/Config.pm:135
msgid "Template database not specified in config file."
msgstr ""
"Le fichier de configuration n'indique pas l'emplacement de la base de "
"données des messages (« templates »)."
#: ../Debconf/Config.pm:140
msgid ""
"The Sigils and Smileys options in the config file are no longer used. Please "
"remove them."
msgstr ""
"Les options Sigils et Smileys ne sont plus utilisées dans le fichier de "
"configuration. Veuillez les supprimer."
#: ../Debconf/Config.pm:157
#, perl-format
msgid "Problem setting up the database defined by stanza %s of %s."
msgstr ""
"Problème pendant la configuration de la base de données définie au "
"paragraphe %s sur %s."
#: ../Debconf/Config.pm:232
msgid ""
" -f, --frontend\t\tSpecify debconf frontend to use.\n"
" -p, --priority\t\tSpecify minimum priority question to show.\n"
" --terse\t\t\tEnable terse mode.\n"
msgstr ""
" -f, --frontend\t\tindique l'interface debconf à utiliser ;\n"
" -p, --priority\t\tindique la priorité minimale à afficher ;\n"
" --terse\t\t\tactive le mode laconique (« terse »).\n"
#: ../Debconf/Config.pm:312
#, perl-format
msgid "Ignoring invalid priority \"%s\""
msgstr "La priorité « %s » non valable sera ignorée"
#: ../Debconf/Config.pm:313
#, perl-format
msgid "Valid priorities are: %s"
msgstr "Les priorités valables sont : %s"
#: ../Debconf/Element/Editor/Boolean.pm:30
#: ../Debconf/Element/Editor/Multiselect.pm:31
#: ../Debconf/Element/Editor/Select.pm:31
msgid "Choices"
msgstr "Choix"
#: ../Debconf/Element/Editor/Boolean.pm:30
#: ../Debconf/Element/Editor/Boolean.pm:36
#: ../Debconf/Element/Editor/Boolean.pm:59
#: ../Debconf/Element/Teletype/Boolean.pm:28
msgid "yes"
msgstr "oui"
#: ../Debconf/Element/Editor/Boolean.pm:30
#: ../Debconf/Element/Editor/Boolean.pm:39
#: ../Debconf/Element/Editor/Boolean.pm:62
#: ../Debconf/Element/Teletype/Boolean.pm:29
msgid "no"
msgstr "non"
#: ../Debconf/Element/Editor/Multiselect.pm:32
msgid ""
"(Enter zero or more items separated by a comma followed by a space (', ').)"
msgstr ""
"Indiquez zéro ou plusieurs éléments séparés par une virgule suivie d'un "
"espace : ', '."
#: ../Debconf/Element/Gnome.pm:184
msgid "_Help"
msgstr "_Aide"
#: ../Debconf/Element/Gnome.pm:186
msgid "Help"
msgstr "Aide"
#: ../Debconf/Element/Noninteractive/Error.pm:40
msgid ""
"Debconf is not confident this error message was displayed, so it mailed it "
"to you."
msgstr ""
"Le message d'erreur n'a pas forcément été affiché, il vous a donc été envoyé "
"par courrier électronique."
#: ../Debconf/Element/Noninteractive/Error.pm:67
ms
Bug#969463: rsync: fails reproducible but unexplained on a specific volume, breaks horribly when started by BackupPC
Hello Bastian, Many thanks for the link, it does indeed look like the exact same bug! So, this turns out to be a longstanding bug in libfile-rsyncp-perl. I see two ways to fix this problem in Debian: - update libfile-rsyncp-perl to 0.76 in buster. This seems quite unlikely but I'm not 100% familiar with Debian policies. - wait for upstream rsync to (possibly) revert the default behaviour of rsync, that is, disable --msgs2stderr by default. And then wait for this updated version of rsync to land in bullseye. See https://github.com/WayneD/rsync/issues/95#issuecomment-700424731 It also looks quite unlikely. So I guess we need the workarounds for now :/ Baptiste
Bug#969463: rsync: fails reproducible but unexplained on a specific volume, breaks horribly when started by BackupPC
On Wed, Nov 17, 2021 at 04:14:23PM +0100, Baptiste Jonglez wrote: > Given this behaviour, it seems likely that rsync ends up running the > "noop_io_until_death()" function and loops there forever. > > Reverting f9bb8f76ee on top of the Debian package indeed fixes the issue > for us on this machine. Actually, both these assertions were red herrings :/ Reverting f9bb8f76ee worked for a few backups, but now it's back to the same hanging issue. And rsync is not stuck in noop_io_until_death() as I thought: it's actually stuck trying to read some data from backuppc through the SSH connection. I have added more details in the upstream bug report: https://github.com/WayneD/rsync/issues/256 In any case, I believe it's completely unrelated to Philipp's issue with rsync taking 100% CPU. But it's definitely the same issue as the one reported by Andreas at the beginning of this bug report. Baptiste
Bug#969463: rsync: fails reproducible but unexplained on a specific volume, breaks horribly when started by BackupPC
Hello,
TL;DR: we experience the same bug using backuppc, and found upstream rsync
commit f9bb8f76ee is the culprit. Unfortunately the bug only occurs on
some debian 11 machines, not all.
We are seeing the same problem when using backuppc to backup a debian 11
machine: the backup never finishes, because the rsync process on the target
machine ends up doing nothing at all (not using any CPU). Rsync on the
target machine is version 3.2.3-4+deb11u1 (standard debian package).
Debugging with strace on the target debian 11 machine, rsync scans the
whole filesystem as expected, but then it gets stuck doing nothing in a
select loop, forever:
strace: Process 4104384 attached
select(1, [0], [], [0], {tv_sec=52, tv_usec=637639}) = 0 (Timeout)
select(1, [0], [], [0], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(1, [0], [], [0], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(1, [0], [], [0], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(1, [0], [], [0], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
Given this behaviour, it seems likely that rsync ends up running the
"noop_io_until_death()" function and loops there forever.
Thanks to a previous comment from Andre, I focused on the git history
between 3.2.2 and 3.2.3 and found this commit:
f9bb8f76ee ("Change daemon variable & simplify some option code")
and specifically this change that introduces a new condition to keep
running noop_io_until_death():
https://github.com/WayneD/rsync/commit/f9bb8f76ee728bd1391a2b4890ce0281457a7bf2#diff-92194f057884b3287a3a6bf84e6e3b2bf433a556b68562799252a091744e7854L920-L921
Reverting f9bb8f76ee on top of the Debian package indeed fixes the issue
for us on this machine.
The strange thing is: on another debian 11 machine that is configured very
similarly (same rsync version, same backuppc server) but has different
data, we could not reproduce the bug at all.
I'm not familiar with rsync internals, but my guess from reading the code is:
- for some reason, possibly due to the way rsync is started by backuppc,
daemon_connection is sometimes set to -1 ("daemon via socket")
- when rsync has finished working, it goes into the noop_io_until_death()
loop because of the new condition in 3.2.3, waiting for a signal
- but the signal never comes, so rsync never exits
- this causes backuppc to wait forever for rsync to finish
For reference, this is how rsync is started by backupppc through SSH:
/usr/bin/ssh -q -x -o StrictHostKeyChecking=no -l backup $CLIENT_HOSTNAME
nice -n 19 sudo /usr/bin/rsync --server --sender --numeric-ids --perms --owner
--group -D --links --hard-links --times --block-size=2048 --recursive
--checksum-seed=32761 . /
I have opened an upstream bug report here:
https://github.com/WayneD/rsync/issues/256
Thanks,
Baptiste
Bug#998836: RM: trafficserver [armhf i386 mips64el mipsel] -- ANAIS; 32 bits architecture support dropped upstream
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear ftp-master, Since version 9.0.0, trafficserver doesn't build anymore for 32 bits architectures. Please remove trafficserver 8.1.1+ds-1.1 from testing to allow 9.1.1+ds-1 transition from unstable 9.1.1+ds-1 targets relevant architectures only. Best, Jean Baptiste Note: this was a request for a partial removal from testing, converted in one for unstable -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAmGJFWpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99 hzfjTBAAuSiGQGJ29mpWzKLi2h7YO1+LutU3jgL/81jJPUrc9OtGN/sg6/37iL/Q jt95GX5ldtcFzN3KYraL3Wyss0Q3U3MsCq0JeCQdJ4RA0i26cbVrSAIKIfLCjoD8 l8d9/U1GD0H7edipM0Sdp5zgo5+s8eaKfYtG+LCH8a7NUWEMn5v1+FqDB2NE5n1W hzNM/3pjEP3YA5LLXkw/G9ctQO0zQ5uMXlL8NhKTJM9DlJmCTJkNYomHmPg/xmtC R20m3ZP64dK1uIz4+pi0HIQhjcvr5d8khZzZOA814D1uCSytydfnCkDesZ4x8/dn UCKE5Y2S7mRX3mW8xMT4gESQMnAub87T9eGEbC5XAxOktItVfRlLIN7q+sNseS7y oo4R1b3HEcKTRSex/421HHn34R+lj6Xwft5Ls5jxz+n8viKvSpWGxT1gG7rBqjfr IiqHrWCpvkZYDCNnP4bXl9b0LINJN8SUicWbbCniWmDmsTJO4p6saAUKlQs8x41O cEHJlj0xocNTPT/KBm0taj2IV69UpcBRmfnmt8221kAm1scHNSn39twYQfJ4grZG B0n1diVH+a6pCBaoWoS+embMTKWrQ74PbKIhT4y+x7c6yJhJFNB2OSwRCy0kB1ev kIthHOH7t1tuuzc+5SubGwVqcfdS0lBmPvlK8FcCYfqubxGsVfk= =ll1+ -END PGP SIGNATURE-
Bug#995365: (no subject)
Dear maintainer, The fix you added solve the ImportError: cannot import name 'ENOENT'. However, it still prevent manpages build for trafficserver package. Using the latest release of sphinxcontrib.plantuml allows the build. Version 0.5 of the package is now 7 years old. Please consider packaging last release ? Thanks, Jean Baptiste OpenPGP_signature Description: OpenPGP digital signature
Bug#996636: trafficserver FTBFS on 32bit
Hello ADrian,
Thanks for reporting the issue.
Unfortunatly, it's a well known issue since upstream decided some years
ago to drop 32 bits architecture support.
I've luckily been able to still offer trafficserver for x86 since then,
but it's not the case any more from trafficserver 9.0.0.
I've asked ftp master for their advice about the opportunity of keeping
the package in Debian or not.
Best,
Jean Baptiste Favre
On 16/10/2021 17:50, Adrian Bunk wrote:
Source: trafficserver
Version: 9.1.0+ds-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=trafficserver=9.1.0%2Bds-1
...
Log.cc: In static member function ‘static void Log::trace_va(bool, const
sockaddr*, uint16_t, const char*, va_list)’:
Log.cc:1276:14: error: invalid cast from type ‘ink_thread’ {aka ‘long unsigned
int’} to type ‘uint64_t’ {aka ‘long long unsigned int’}
1276 | reinterpret_cast(ink_thread_self()), in ? "RECV" :
"SEND", ip, peer_port);
| ^
...
Bug#679905: RFP: cctbx -- Computational Crystallography Toolbox
Hi, thanks for caring about Debian packaging efforts! This one is an old one, it must have been 2012 or 2013, and salsa was called alioth :-) What I remember was a rather inflexible packaging system, that forced us to duplicate existing code. And an effort that, well, slowly lost steam. Then I lost track of it due to real life commitments (my first child was born 2014). I also gratefully remember that Luc Bourhis was very helpful from the upstream side. I wouldn't want to bother him again, though, until we have something concrete to put on the table. Best regards, Baptiste Le 06/10/2021 à 10:13, Andreas Tille a écrit : > Hi, > > I've got a hint about cctbx and realised that there is an RFP (degraded > from ITP) as well as a salsa repository[1]. I took the freedom to > inject the latest upstream source and updated *parts* of the packaging > to recent standards. I have no idea whether this might give some new > inspiration for those who want to catch up with this package, which is > interesting for several teams (in CC). So I simply make some noise for > anybody who might want to continue from here. > > Kind regards > > Andreas. > > [1] https://salsa.debian.org/science-team/cctbx >
Bug#994133: libc-bin: [iconv] [fr] Missing word in the French output of iconv
control: reassign -1 libc-bin control: retitle -1 libc-bin: [iconv] [fr] Missing word in the French output of iconv --help control: tags -1 upstream Hi all, >It’s in the output of iconv --help. So it's not in the manpage, but in the po/fr.po file of the iconv source : https://sources.debian.org/src/glibc/2.32-2/po/fr.po/#L42 introduced in upstream by: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=0ffaa7be6ea3649f883248f41a2bea5065383976#patch11 Sorry for the ping-pong and thank you all for the translation work! Baptiste pgpFbulrUofsc.pgp Description: Signature digitale OpenPGP
Bug#994049: libhwloc-contrib-plugins: hwloc displays misleading CUDA and NVML errors when running MPI programs
Hi Samuel, On Sat, Sep 11, 2021 at 12:41:04AM +0200, Samuel Thibault wrote: > Hello, > > Would it be possible to backport this patch to Debian stable or, > > as an alternative, publish hwloc 2.5.0 in bullseye-backports? > > I was waiting for a good reason to take the time to backport hwloc 2.5, > that was one, it's now in backports-NEW :) Perfect, thanks :) > That said perhaps we can ask d-release for a stable upload, Brice what > do you think? The bullseye-backports package will be enough for us, but of course having the fix in stable is also nice (if it's not considered too intrusive). Thanks, Baptiste
Bug#994049: libhwloc-contrib-plugins: hwloc displays misleading CUDA and NVML errors when running MPI programs
Package: libhwloc-contrib-plugins
Version: 2.4.1+dfsg-2
Severity: important
Dear Maintainer,
When the libhwloc-contrib-plugins package is installed, running any MPI
program on a Debian 11 host with no GPU produces the following errors:
$ mpirun hostname
CUDA: Failed to get number of devices with cudaGetDeviceCount(): no
CUDA-capable device is detected
NVML: Failed to initialize with nvmlInit(): Driver Not Loaded
CUDA: Failed to get number of devices with cudaGetDeviceCount(): no
CUDA-capable device is detected
NVML: Failed to initialize with nvmlInit(): Driver Not Loaded
dahu-28.grenoble.grid5000.fr
For complex programs, it is quite hard to understand where these messages
come from and what the exact problem is. After investigation, it turns out
that these messages are "warnings" and don't prevent the program from
executing, so they can be ignored. But when the program fails for unrelated
reasons, these messages can mislead the user into thinking the problem is
CUDA-related, while it's actually not.
The expected behaviour is that hwloc should not print warnings about
hardware detection when nothing is actually wrong.
This bug has already been fixed upstream in version 2.5.0rc1:
835dfbe577fcd7 ("core: don't display "less critical" error messages by
default")
https://github.com/open-mpi/hwloc/issues/453
Would it be possible to backport this patch to Debian stable or,
as an alternative, publish hwloc 2.5.0 in bullseye-backports?
Thanks for your time,
Baptiste
-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libhwloc-contrib-plugins depends on:
ii libc6 2.31-13
ii libcudart11.0 5000.0g5k1
ii libhwloc15 2.4.1+dfsg-1
ii libnvidia-ml1 5000.0g5k1
libhwloc-contrib-plugins recommends no packages.
libhwloc-contrib-plugins suggests no packages.
-- no debconf information
Bug#993963: ITP: centreon-plugins -- Collection of nagios plugins to monitor OS, services and network devices
Package: wnpp Severity: wishlist Owner: Baptiste Beauplat X-Debbugs-Cc: debian-de...@lists.debian.org, pkg-nagios-de...@lists.alioth.debian.org * Package name: centreon-plugins Version : 0.0~20210520-1 Upstream Author : Centreon (https://www.centreon.com) * URL : https://github.com/centreon/centreon-plugins * License : Apache-2.0 Programming Lang: Perl Description : Collection of Nagios plugins to monitor OS, services and network devices Free and open source project to monitor systems. The project can be used with Centreon and all monitoring software compatible with Nagios plugins. The following can be monitored: * application: Apache, Asterisk, Elasticsearch, Github, Jenkins, Kafka, Nginx, Pfsense, Redis, Tomcat, Varnish... * cloud: AWS, Azure, Docker, Office365, Nutanix, Prometheus... * database: Firebird, Informix, MS SQL, MySQL, Oracle, Postgres, Cassandra * hardware: printers (rfc3805), UPS (Powerware, Mge, Standard), Sun Hardware, Cisco UCS, SensorIP, HP Proliant, HP Bladechassis, Dell Openmanage, Dell CMC, Raritan... * network: Aruba, Brocade, Bluecoat, Brocade, Checkpoint, Cisco AP/IronPort/ASA/Standard, Extreme, Fortigate, H3C, Hirschmann, HP Procurve, F5 BIG-IP, Juniper, PaloAlto, Redback, Riverbed, Ruggedcom, Stonesoft... * os: Linux (SNMP, NRPE), Freebsd (SNMP), AIX (SNMP), Solaris (SNMP)... * storage: EMC Clariion, Netapp, Nimble, HP MSA p2000, Dell EqualLogic, Qnap, Panzura, Synology... I intend to maintain this package as part of the Nagios team. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#993531: lintian: doesn't know about conffile remove-on-upgrade tag
Package: lintian Version: 2.104.0 Severity: normal Dear Maintainer, I was building my package (chkboot 1.3-8) when lintian reported the following tags: ``` E: chkboot: conffile-is-not-in-package remove-on-upgrade /etc/kernel/postinst.d/zzz-chkboot E: chkboot: conffile-is-not-in-package remove-on-upgrade /etc/kernel/postrm.d/zzz-chkboot E: chkboot: non-etc-file-marked-as-conffile remove-on-upgrade /etc/kernel/postinst.d/zzz-chkboot E: chkboot: non-etc-file-marked-as-conffile remove-on-upgrade /etc/kernel/postrm.d/zzz-chkboot E: chkboot: relative-conffile remove-on-upgrade /etc/kernel/postinst.d/zzz-chkboot E: chkboot: relative-conffile remove-on-upgrade /etc/kernel/postrm.d/zzz-chkboot ``` Based on the following conffile generated by dpkg 1.20.9 and debhelper 13.5.1: ``` remove-on-upgrade /etc/kernel/postinst.d/zzz-chkboot remove-on-upgrade /etc/kernel/postrm.d/zzz-chkboot /etc/apt/apt.conf.d/05chkboot /etc/default/chkboot /etc/init.d/chkboot /etc/profile.d/chkboot-profilealert.sh ``` The remove-on-upgrade tag is a new feature from dpkg 1.20.6 as stated in deb-conffiles(5): ``` There is currently only one flag supported, remove-on-upgrade, to mark that a conffile needs to be removed on the next upgrade (since dpkg 1.20.6). These files must not exist in the binary package, as both dpkg(1) and dpkg-deb(1) will not accept building nor processing such binary packages. ``` Lintian should skip the tag if present while checking for the given tags. Best, -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#992694: reprotest: kernel variation makes ldconfig abort with message "FATAL: Kernel too old"
On 2021/08/26 04:25 PM, Mattia Rizzolo wrote: > > What would you say about this patch: > > |--- a/README.rst > |+++ b/README.rst > |@@ -378,9 +378,9 @@ mechanism to vary the system time. > | Kernel > | -- > | > |-The "kernel" variation is currently not working for RPM based packages. > While > |-building with this variation enabled, the tool > `/usr/lib/rpm/redhat/brp-ldconfig` > |-compains about `FATAL: kernel too old` and aborts the build. > |+The "kernel" variation is currently not working for RPM based packages and > other > |+build process requiring `ldconfig`. While building with this variation > enabled, > |+`ldconfig` complains about `FATAL: kernel too old` and aborts the build. > | > | Avoid sudo(1) password prompts > | == Looks good to me. > Besides potentially better identifying which versions of ldconfig are > effectively broken, I don't think we could do much else. IIRC, the change was introduced by https://salsa.debian.org/glibc-team/glibc/-/commit/2d7aa68d5d30a203b61b551432efcefac7413885#98f7bc9994884d56cdc1b30b364e50f8800dbc07_147_147 which was packaged with glibc-2.25. I agree. A possibility would be to introduce a '--uname-3.2' to setarch and I don't think, for the number of packages using ldconfig at build time, this is worth the trouble (specially since upstream might not be interested by it). -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#992694: reprotest: kernel variation makes ldconfig abort with message "FATAL: Kernel too old"
Package: reprotest Version: 0.7.16 Severity: normal Dear Maintainer, While trying to debug https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/191, I found out that the kernel variation makes ldconfig abort with the following message: "FATAL: Kernel too old" This bug can be reproduced using two methods: The low level: `setarch --uname-2.6 ldconfig -v` The high level: ``` cd /tmp; (mkdir -p test-0.1; cd test-0.1; dh_make -n -s -c mit -y; echo -e "override_dh_auto_install:\n\tldconfig --version" >> debian/rules) sudo reprotest --vary=-all,kernel --auto-build /tmp/test-0.1 -- schroot unstable-amd64-sbuild ``` This behavour is partially documented in the manpage under: ``` Kernel -- The "kernel" variation is currently not working for RPM based packages. While building with this variation enabled, the tool `/usr/lib/rpm/redhat/brp-ldconfig` compains about `FATAL: kernel too old` and aborts the build. ``` However all version of ldconfig (at least since 2017) require a kernel 3.2, not just the RPM ldconfig. I think the documentation should be updated to warn users about ldconfig not working in all cases. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#991481: unblock: openntpd/1:6.2p3-4.2 (pre-approval)
Control: retitle -1 unblock: openntpd/1:6.2p3-4.2 Asking for a pre-approval on a trivial 3 line targeted RC fix doesn't seems like a good use of the release team's time. I've uploaded the fix to unstable and I'm converting this bug into a standard unblock. Sorry for the waste of time. unblock openntpd/1:6.2p3-4.2 -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#987321: openntpd: if-up.d script uses SysV command instead of systemd and blocks boot
Control: tags -1 + pending Ended-up uploading to DELAY/0. After a quick exchange on IRC #debian-release, asking for pre-approval for a targeted RC fix is a waste of time for the release team. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#987321: openntpd: diff for NMU version 1:6.2p3-4.2
Control: tags 987321 + patch Dear maintainer, I've prepared an NMU for openntpd (versioned as 1:6.2p3-4.2) and created an pre-approval unblock request for it. Once given the go-ahead by the release team, I'll upload it to DELAYED/0. Pre-approval request: https://bugs.debian.org/991481 Regards. -- Baptiste Beauplat - lyknode diff -Nru openntpd-6.2p3/debian/changelog openntpd-6.2p3/debian/changelog --- openntpd-6.2p3/debian/changelog 2020-10-26 18:10:47.0 +0100 +++ openntpd-6.2p3/debian/changelog 2021-07-25 14:37:54.0 +0200 @@ -1,3 +1,11 @@ +openntpd (1:6.2p3-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * Ensure that openntpd is running before restarting it from the if-up.d +hook. (Closes: #987321) + + -- Baptiste Beauplat Sun, 25 Jul 2021 14:37:54 +0200 + openntpd (1:6.2p3-4.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru openntpd-6.2p3/debian/config/openntpd openntpd-6.2p3/debian/config/openntpd --- openntpd-6.2p3/debian/config/openntpd 2020-10-26 15:52:50.0 +0100 +++ openntpd-6.2p3/debian/config/openntpd 2021-07-25 11:33:18.0 +0200 @@ -7,4 +7,6 @@ exit 0 fi -invoke-rc.d openntpd force-reload || true +if pidof -q ntpd; then +invoke-rc.d openntpd force-reload || true +fi signature.asc Description: PGP signature
Bug#991481: unblock: openntpd/1:6.2p3-4.2 (pre-approval)
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, this is a request for pre-approval of an openntpd upload. [ Reason ] Openntpd makes networking configuration fail when running its if-up hook. https://bugs.debian.org/987321 The upload would fix this issue by checking if openntpd is running before restarting it. Openntpd depending on systemd network target, it would be skipped on boot but correctly executed on ifdown/ifup. [ Impact ] High: this bug is effectively holding the boot sequence to the networking service timeout (5 minutes) and preventing any interfaces after the first one to be configured. [ Tests ] Autopkgtest is superficial. I've manually tested the fix in both systemd and sysv setup. I've validated that the patch fixes the booting issue and that openntpd restart on interface reconfiguration (if already started). [ Risks ] Low: the changeset is quite small and self-contained. This is a non-key leaf package. It has a popcorn of ~1350. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] This is an NMU. On approval, I'll upload with DELAY/0. unblock openntpd/1:6.2p3-4.2 -- Baptiste Beauplat - lyknode diff -Nru openntpd-6.2p3/debian/changelog openntpd-6.2p3/debian/changelog --- openntpd-6.2p3/debian/changelog 2020-10-26 18:10:47.0 +0100 +++ openntpd-6.2p3/debian/changelog 2021-07-25 14:37:54.0 +0200 @@ -1,3 +1,11 @@ +openntpd (1:6.2p3-4.2) unstable; urgency=medium + + * Non-maintainer upload. + * Ensure that openntpd is running before restarting it from the if-up.d +hook. (Closes: #987321) + + -- Baptiste Beauplat Sun, 25 Jul 2021 14:37:54 +0200 + openntpd (1:6.2p3-4.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru openntpd-6.2p3/debian/config/openntpd openntpd-6.2p3/debian/config/openntpd --- openntpd-6.2p3/debian/config/openntpd 2020-10-26 15:52:50.0 +0100 +++ openntpd-6.2p3/debian/config/openntpd 2021-07-25 11:33:18.0 +0200 @@ -7,4 +7,6 @@ exit 0 fi -invoke-rc.d openntpd force-reload || true +if pidof -q ntpd; then +invoke-rc.d openntpd force-reload || true +fi signature.asc Description: PGP signature
Bug#987321: openntpd: if-up.d script uses SysV command instead of systemd and blocks boot
Control: severity -1 critical On 2021/04/21 07:42 PM, François Cerbelle wrote: > openntpd installs a smart if-up.d script to reload the configuration > when an interface is started. It blocks the boot process until a timeout > occurs at the "Raise network interfaces" step. This effectively prevent systems from configuring multiple interfaces when using 'auto' in /etc/network/interfaces. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#961142: snapshot.debian.org: python3 migration
g the `tox` command. It will take care of settings up an isolated environment to test with (postgresql is still a requirement) - Pushing commits to the repository, that will trigger the CI Deployment == Although, it requires some adjustments, I haven't touched the deployments files (speaking of `etc/apache.conf` and `web/deploy`). From what I can gather, the current frontend setup is split between several directories: - /srv/snapshot.debian.org/web/public/static/, for static files - /srv/snapshot.debian.org/web/public/, for web root - /srv/snapshot.debian.org/bin/, for the WSGI script - /srv/snapshot.debian.org/web-app/, for the actual frontend app It looks like public/ and the WSGI script are actually links to the web-app subtree. All of that is split from the local copy of the repository (living in `/srv/snapshot.debian.org/code/`). Do you want to use the same setup for the new version? I usually expose directly the git repository, aliasing /robots.txt, /static and / (to the wsgi script) and it works. However, that technique might not fit security requirements for snapshot.d.o. In any case, I've removed the egg-info directory from the repository (being generated files), so they would have to be generated by the deploy script using a `setup.py sdist`. What's next === Let me know how to proceed from here. I suppose you will want to review the code; I'm looking forward to your feedback on that. Then, do you want to host that version, parallel to the previous one for a couple of weeks to allow testing by other people, before switching? Let me know how can I be of any help. I do intend to address bugs listed for snapshot.debian.org in the BTS and build on this new version of snapshot. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#989018: unblock: imv/4.2.0-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package imv [ Reason ] - Non-key package - No autopkgtest - Fixes RC bug (#987536) [ Impact ] Low, this is a trivial fix for a FTBFS without internet access (one B-D added). [ Tests ] The fix only affects generated manpages. I've confirmed, using diffoscope that there is no changes to the previous version of the binary package, except from some build metadata embeded in the manpage (timestamp and version). [ Risks ] Very low: - Changes are trivial - Leaf package - No functional changes - Patch is taken from ubuntu [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] - Non-maintainer upload unblock imv/4.2.0-1.1 -- Baptiste Beauplat - lyknode diff -Nru imv-4.2.0/debian/changelog imv-4.2.0/debian/changelog --- imv-4.2.0/debian/changelog 2021-01-31 13:03:12.0 +0100 +++ imv-4.2.0/debian/changelog 2021-05-18 13:51:05.0 +0200 @@ -1,3 +1,12 @@ +imv (4.2.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build-depend on docbook-xsl so that xsltproc doesn't try to access +the internet for the stylesheet. Works around #980930. Thanks to Logan +Rosen for the patch. (Closes: #987536) + + -- Baptiste Beauplat Tue, 18 May 2021 13:51:05 +0200 + imv (4.2.0-1) unstable; urgency=medium * New upstream version 4.2.0. diff -Nru imv-4.2.0/debian/control imv-4.2.0/debian/control --- imv-4.2.0/debian/control2021-01-31 13:01:39.0 +0100 +++ imv-4.2.0/debian/control2021-05-18 13:49:39.0 +0200 @@ -6,6 +6,7 @@ Build-Depends: asciidoc-base, debhelper-compat (= 13), + docbook-xsl, libcmocka-dev, libegl1-mesa-dev, libfreeimage-dev, signature.asc Description: PGP signature
Bug#987536: imv: diff for NMU version 4.2.0-1.1
Dear maintainer, I've prepared an NMU for imv (versioned as 4.2.0-1.1). The diff is attached to this message. I'll open an unblock request of it too. Regards. -- Baptiste Beauplat - lyknode diff -Nru imv-4.2.0/debian/changelog imv-4.2.0/debian/changelog --- imv-4.2.0/debian/changelog 2021-01-31 13:03:12.0 +0100 +++ imv-4.2.0/debian/changelog 2021-05-18 13:51:05.0 +0200 @@ -1,3 +1,12 @@ +imv (4.2.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build-depend on docbook-xsl so that xsltproc doesn't try to access +the internet for the stylesheet. Works around #980930. Thanks to Logan +Rosen for the patch. (Closes: #987536) + + -- Baptiste Beauplat Tue, 18 May 2021 13:51:05 +0200 + imv (4.2.0-1) unstable; urgency=medium * New upstream version 4.2.0. diff -Nru imv-4.2.0/debian/control imv-4.2.0/debian/control --- imv-4.2.0/debian/control 2021-01-31 13:01:39.0 +0100 +++ imv-4.2.0/debian/control 2021-05-18 13:49:39.0 +0200 @@ -6,6 +6,7 @@ Build-Depends: asciidoc-base, debhelper-compat (= 13), + docbook-xsl, libcmocka-dev, libegl1-mesa-dev, libfreeimage-dev, signature.asc Description: PGP signature
Bug#987536: imv FTBFS without internet access
Control: tags -1 + patch On 2021/04/25 12:22 PM, Adrian Bunk wrote: > The Ubuntu patch seems to contain a fix/workaround. As Adrian stated, the ubuntu patch fixes the issue. Please find attached the patch to apply (Credit to Logan Rosen ) I intend to NMU in a couple of days if the bug is still open by then. Best, -- Baptiste Beauplat - lyknode diff -Nru imv-4.2.0/debian/control imv-4.2.0/debian/control --- imv-4.2.0/debian/control2021-01-31 13:01:39.0 +0100 +++ imv-4.2.0/debian/control2021-05-18 13:49:39.0 +0200 @@ -6,6 +6,7 @@ Build-Depends: asciidoc-base, debhelper-compat (= 13), + docbook-xsl, libcmocka-dev, libegl1-mesa-dev, libfreeimage-dev, signature.asc Description: PGP signature
Bug#988641: unblock: fenix/0.92a.dfsg1-12.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package fenix
[ Reason ]
- Non-key package
- Autopkgtest does not cover all architectures (but does cover all built
architectures)
- Fixes RC bug (#987637)
[ Impact ]
- Low, the fix is a trivial (one-liner) change for a FTBFS. No
user/behavior changes.
- A change has been made to the test suite to:
* Run only on built architectures
* Cover the fix
[ Tests ]
I've run the program and built a fenix source file (taken from the
source examples) in order to cover the fix. Additionally, the fix is
covered by autopkgtest.
I've also successfully rebuilt all (3) reverse B-D.
[ Risks ]
Low:
- Changes covered by autopkgtest
- Trivial change
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
- Non-maintainer upload
unblock fenix/0.92a.dfsg1-12.1
--
Baptiste Beauplat - lyknode
diff -Nru fenix-0.92a.dfsg1/debian/changelog fenix-0.92a.dfsg1/debian/changelog
--- fenix-0.92a.dfsg1/debian/changelog 2019-02-13 15:35:24.0 +0100
+++ fenix-0.92a.dfsg1/debian/changelog 2021-05-14 14:13:28.0 +0200
@@ -1,3 +1,14 @@
+fenix (0.92a.dfsg1-12.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add a patch to fix FTBFS with gcc 10, declaring debug as an external
+variable (Closes: #987637)
+ * Modify autopkgtest to assert fenix debug output
+ * Only run autopkgtest on architectures where binary package fenix is built
+(required by the test suite)
+
+ -- Baptiste Beauplat Fri, 14 May 2021 14:13:28 +0200
+
fenix (0.92a.dfsg1-12) unstable; urgency=medium
[ Peter Pentchev ]
diff -Nru fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch
fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch
--- fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch 1970-01-01
01:00:00.0 +0100
+++ fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch 2021-05-11
21:08:56.0 +0200
@@ -0,0 +1,19 @@
+From: Baptiste Beauplat
+Date: Tue, 11 May 2021 21:06:15 +0200
+Subject: Fix FTBFS with gcc 10 (Closes: #987637)
+
+Declare debug as an external variable.
+Declaration and assignation is done in main.c.
+---
+
+--- a/fxc/src/c_main.c
b/fxc/src/c_main.c
+@@ -182,7 +182,7 @@
+ #ifdef TARGET_MAC
+ static int debug ;
+ #else
+-int debug;
++extern int debug;
+ #endif
+
+ void compile_init ()
diff -Nru fenix-0.92a.dfsg1/debian/patches/series
fenix-0.92a.dfsg1/debian/patches/series
--- fenix-0.92a.dfsg1/debian/patches/series 2019-02-12 10:40:57.0
+0100
+++ fenix-0.92a.dfsg1/debian/patches/series 2021-05-10 21:39:02.0
+0200
@@ -35,3 +35,4 @@
fxc-cmdline-crash.patch
fxi-cmdline-title.patch
map-gif-256-colors.patch
+fix_ftbfs_gcc10.patch
diff -Nru fenix-0.92a.dfsg1/debian/tests/control
fenix-0.92a.dfsg1/debian/tests/control
--- fenix-0.92a.dfsg1/debian/tests/control 2019-02-12 15:47:50.0
+0100
+++ fenix-0.92a.dfsg1/debian/tests/control 2021-05-14 14:13:28.0
+0200
@@ -1,3 +1,19 @@
Test-Command: env TESTDIR="$(pwd)/debian/tests/t"
TEST_FENIX_MAP=/usr/bin/fenix-map TEST_FENIX_FXC=/usr/bin/fenix-fxc
TEST_FENIX_FXI=/usr/bin/fenix-fxi TERM=dumb prove -v -r debian/tests/t
Depends: @, libgd-perl, libpath-tiny-perl, libtest-command-perl, perl
Restrictions: allow-stderr
+Architecture: arm
+ armel
+ armhf
+ hppa
+ hurd-i386
+ i386
+ kfreebsd-i386
+ m68k
+ mips
+ mipsel
+ mipsn32
+ mipsn32el
+ powerpc
+ s390
+ sh4
+ sparc
diff -Nru fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm
fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm
--- fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm 2019-02-12
15:47:50.0 +0100
+++ fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm 2021-05-11
22:17:32.0 +0200
@@ -41,12 +41,11 @@
Test::More::plan tests => 4;
my $cmd = Test::Command->new(cmd => [
- $fxc, $test->{test}{src}->basename,
+ $fxc, '-d', $test->{test}{src}->basename,
]);
$cmd->exit_is_num(0);
- # Yeah, this is backwards, I know...
- $cmd->stdout_is_eq('');
- $cmd->stderr_isnt_eq('');
+ $cmd->stdout_like(qr/END/);
+ $cmd->stderr_like(qr/- Main procedure/);
Test::More::ok -f $test->{test}{exe},
'the compiled program exists';
signature.asc
Description: PGP signature
Bug#988534: unblock: zsnes/1.510+bz2-10.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package zsnes
[ Reason ]
- Non-key package without autopkgtest
- Fix a RC bug (#987640)
[ Impact ]
Low, the bug is a FTBFS. User experience in running the program is not
affected.
[ Tests ]
The fix has been tested manually both by building the program (on the
targeted i386 architecture) and running it. The test run was to launch
the program and load a rom. The game started correctly.
[ Risks ]
Low:
- Fix is trivial
- No functionality changes
- Leaf package
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
- Non-maintainer upload
unblock zsnes/1.510+bz2-10.1
--
Baptiste Beauplat - lyknode
diff -Nru zsnes-1.510+bz2/debian/changelog zsnes-1.510+bz2/debian/changelog
--- zsnes-1.510+bz2/debian/changelog2019-12-14 16:03:00.0 +0100
+++ zsnes-1.510+bz2/debian/changelog2021-05-14 14:46:32.0 +0200
@@ -1,3 +1,11 @@
+zsnes (1.510+bz2-10.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to fix FTBFS with GCC 10, declaring HacksDisable as an extern
+variable and fixing its type (Closes: #987640)
+
+ -- Baptiste Beauplat Fri, 14 May 2021 14:46:32 +0200
+
zsnes (1.510+bz2-10) unstable; urgency=high
* Team upload.
diff -Nru zsnes-1.510+bz2/debian/patches/0018-Fix-ftbfs-with-gcc-10.patch
zsnes-1.510+bz2/debian/patches/0018-Fix-ftbfs-with-gcc-10.patch
--- zsnes-1.510+bz2/debian/patches/0018-Fix-ftbfs-with-gcc-10.patch
1970-01-01 01:00:00.0 +0100
+++ zsnes-1.510+bz2/debian/patches/0018-Fix-ftbfs-with-gcc-10.patch
2021-05-05 23:28:51.0 +0200
@@ -0,0 +1,25 @@
+From: Baptiste Beauplat
+Date: Wed, 5 May 2021 23:18:27 +0200
+Subject: Fix FTBFS with gcc 10 (Closes: #987640)
+
+Declare HacksDisable as external unsigned char in initc.c.
+Declaration and assignation is done in cfg.c. This file is generated at
+build time by parsegen from cfg.psr. The generated variable is an
+unsigned char.
+---
+ src/initc.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/initc.c b/src/initc.c
+index 3096240..56b02bc 100644
+--- a/src/initc.c
b/src/initc.c
+@@ -1496,7 +1496,7 @@ Would be nice to trash this section in the future
+ extern unsigned char ENVDisable, cycpb268, cycpb358, cycpbl2, cycpblt2,
cycpbl;
+ extern unsigned char cycpblt, opexec268, opexec358, opexec268b, opexec358b;
+ extern unsigned char opexec268cph, opexec358cph, opexec268cphb, opexec358cphb;
+-bool HacksDisable;
++extern unsigned char HacksDisable;
+
+ void headerhack()
+ {
diff -Nru zsnes-1.510+bz2/debian/patches/series
zsnes-1.510+bz2/debian/patches/series
--- zsnes-1.510+bz2/debian/patches/series 2019-12-14 16:02:16.0
+0100
+++ zsnes-1.510+bz2/debian/patches/series 2021-05-05 23:28:51.0
+0200
@@ -15,3 +15,4 @@
fortify-source-load.patch
hurd.patch
privacy-breach.patch
+0018-Fix-ftbfs-with-gcc-10.patch
signature.asc
Description: PGP signature
Bug#987640: zsnes: diff for NMU version 1.510+bz2-10.1
Dear maintainer,
I've prepared an NMU for zsnes (versioned as 1.510+bz2-10.1). The diff
is attached to this message.
Once the package is built and installed, I'll open an unblock request.
Regards.
--
Baptiste Beauplat - lyknode
diff -Nru zsnes-1.510+bz2/debian/changelog zsnes-1.510+bz2/debian/changelog
--- zsnes-1.510+bz2/debian/changelog 2019-12-14 16:03:00.0 +0100
+++ zsnes-1.510+bz2/debian/changelog 2021-05-14 14:46:32.0 +0200
@@ -1,3 +1,11 @@
+zsnes (1.510+bz2-10.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to fix FTBFS with GCC 10, declaring HacksDisable as an extern
+variable and fixing its type (Closes: #987640)
+
+ -- Baptiste Beauplat Fri, 14 May 2021 14:46:32 +0200
+
zsnes (1.510+bz2-10) unstable; urgency=high
* Team upload.
diff -Nru zsnes-1.510+bz2/debian/patches/0018-Fix-ftbfs-with-gcc-10.patch zsnes-1.510+bz2/debian/patches/0018-Fix-ftbfs-with-gcc-10.patch
--- zsnes-1.510+bz2/debian/patches/0018-Fix-ftbfs-with-gcc-10.patch 1970-01-01 01:00:00.0 +0100
+++ zsnes-1.510+bz2/debian/patches/0018-Fix-ftbfs-with-gcc-10.patch 2021-05-05 23:28:51.0 +0200
@@ -0,0 +1,25 @@
+From: Baptiste Beauplat
+Date: Wed, 5 May 2021 23:18:27 +0200
+Subject: Fix FTBFS with gcc 10 (Closes: #987640)
+
+Declare HacksDisable as external unsigned char in initc.c.
+Declaration and assignation is done in cfg.c. This file is generated at
+build time by parsegen from cfg.psr. The generated variable is an
+unsigned char.
+---
+ src/initc.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/initc.c b/src/initc.c
+index 3096240..56b02bc 100644
+--- a/src/initc.c
b/src/initc.c
+@@ -1496,7 +1496,7 @@ Would be nice to trash this section in the future
+ extern unsigned char ENVDisable, cycpb268, cycpb358, cycpbl2, cycpblt2, cycpbl;
+ extern unsigned char cycpblt, opexec268, opexec358, opexec268b, opexec358b;
+ extern unsigned char opexec268cph, opexec358cph, opexec268cphb, opexec358cphb;
+-bool HacksDisable;
++extern unsigned char HacksDisable;
+
+ void headerhack()
+ {
diff -Nru zsnes-1.510+bz2/debian/patches/series zsnes-1.510+bz2/debian/patches/series
--- zsnes-1.510+bz2/debian/patches/series 2019-12-14 16:02:16.0 +0100
+++ zsnes-1.510+bz2/debian/patches/series 2021-05-05 23:28:51.0 +0200
@@ -15,3 +15,4 @@
fortify-source-load.patch
hurd.patch
privacy-breach.patch
+0018-Fix-ftbfs-with-gcc-10.patch
signature.asc
Description: PGP signature
Bug#987637: fenix: diff for NMU version 0.92a.dfsg1-12.1~exp1
Dear maintainer,
I've prepared an NMU for fenix (versioned as 0.92a.dfsg1-12.1~exp1). The diff
is attached to this message.
I'm uploading to experimental before unstable in order to validate that
autopkgtest works.
Regards.
--
Baptiste Beauplat - lyknode
diff -Nru fenix-0.92a.dfsg1/debian/changelog fenix-0.92a.dfsg1/debian/changelog
--- fenix-0.92a.dfsg1/debian/changelog 2019-02-13 15:35:24.0 +0100
+++ fenix-0.92a.dfsg1/debian/changelog 2021-05-14 14:13:28.0 +0200
@@ -1,3 +1,14 @@
+fenix (0.92a.dfsg1-12.1~exp1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Add a patch to fix FTBFS with gcc 10, declaring debug as an external
+variable (Closes: #987637)
+ * Modify autopkgtest to assert fenix debug output
+ * Only run autopkgtest on architectures where binary package fenix is built
+(required by the test suite)
+
+ -- Baptiste Beauplat Fri, 14 May 2021 14:13:28 +0200
+
fenix (0.92a.dfsg1-12) unstable; urgency=medium
[ Peter Pentchev ]
diff -Nru fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch
--- fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch 1970-01-01 01:00:00.0 +0100
+++ fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch 2021-05-11 21:08:56.0 +0200
@@ -0,0 +1,19 @@
+From: Baptiste Beauplat
+Date: Tue, 11 May 2021 21:06:15 +0200
+Subject: Fix FTBFS with gcc 10 (Closes: #987637)
+
+Declare debug as an external variable.
+Declaration and assignation is done in main.c.
+---
+
+--- a/fxc/src/c_main.c
b/fxc/src/c_main.c
+@@ -182,7 +182,7 @@
+ #ifdef TARGET_MAC
+ static int debug ;
+ #else
+-int debug;
++extern int debug;
+ #endif
+
+ void compile_init ()
diff -Nru fenix-0.92a.dfsg1/debian/patches/series fenix-0.92a.dfsg1/debian/patches/series
--- fenix-0.92a.dfsg1/debian/patches/series 2019-02-12 10:40:57.0 +0100
+++ fenix-0.92a.dfsg1/debian/patches/series 2021-05-10 21:39:02.0 +0200
@@ -35,3 +35,4 @@
fxc-cmdline-crash.patch
fxi-cmdline-title.patch
map-gif-256-colors.patch
+fix_ftbfs_gcc10.patch
diff -Nru fenix-0.92a.dfsg1/debian/tests/control fenix-0.92a.dfsg1/debian/tests/control
--- fenix-0.92a.dfsg1/debian/tests/control 2019-02-12 15:47:50.0 +0100
+++ fenix-0.92a.dfsg1/debian/tests/control 2021-05-14 14:13:28.0 +0200
@@ -1,3 +1,19 @@
Test-Command: env TESTDIR="$(pwd)/debian/tests/t" TEST_FENIX_MAP=/usr/bin/fenix-map TEST_FENIX_FXC=/usr/bin/fenix-fxc TEST_FENIX_FXI=/usr/bin/fenix-fxi TERM=dumb prove -v -r debian/tests/t
Depends: @, libgd-perl, libpath-tiny-perl, libtest-command-perl, perl
Restrictions: allow-stderr
+Architecture: arm
+ armel
+ armhf
+ hppa
+ hurd-i386
+ i386
+ kfreebsd-i386
+ m68k
+ mips
+ mipsel
+ mipsn32
+ mipsn32el
+ powerpc
+ s390
+ sh4
+ sparc
diff -Nru fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm
--- fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm 2019-02-12 15:47:50.0 +0100
+++ fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm 2021-05-11 22:17:32.0 +0200
@@ -41,12 +41,11 @@
Test::More::plan tests => 4;
my $cmd = Test::Command->new(cmd => [
- $fxc, $test->{test}{src}->basename,
+ $fxc, '-d', $test->{test}{src}->basename,
]);
$cmd->exit_is_num(0);
- # Yeah, this is backwards, I know...
- $cmd->stdout_is_eq('');
- $cmd->stderr_isnt_eq('');
+ $cmd->stdout_like(qr/END/);
+ $cmd->stderr_like(qr/- Main procedure/);
Test::More::ok -f $test->{test}{exe},
'the compiled program exists';
signature.asc
Description: PGP signature
Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
On 2021/05/11 11:00 PM, Baptiste Beauplat wrote: > The issue may be related to this upstream issue: > > https://gitlab.gnome.org/GNOME/vala/-/issues/1167 > > I'll test using a patched version of vala and reassign if needed. The pachted version of vala in sid works and libunity build correctly with it. This is a regression in vala, reassigning the bug. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#987637: fenix FTBFS with gcc 10
Control: tags -1 + patch
Dear maintainer,
The following patch fixes the FTBFS. I've added a specific check in the
test suite and I've tested it manually.
Without feedback, I'll NMU the package and request an unblock in a
couple of days.
Best,
--
Baptiste Beauplat - lyknode
diff -Nru fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch
fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch
--- fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch 1970-01-01
01:00:00.0 +0100
+++ fenix-0.92a.dfsg1/debian/patches/fix_ftbfs_gcc10.patch 2021-05-11
21:08:56.0 +0200
@@ -0,0 +1,19 @@
+From: Baptiste Beauplat
+Date: Tue, 11 May 2021 21:06:15 +0200
+Subject: Fix FTBFS with gcc 10 (Closes: #987637)
+
+Declare debug as an external variable.
+Declaration and assignation is done in main.c.
+---
+
+--- a/fxc/src/c_main.c
b/fxc/src/c_main.c
+@@ -182,7 +182,7 @@
+ #ifdef TARGET_MAC
+ static int debug ;
+ #else
+-int debug;
++extern int debug;
+ #endif
+
+ void compile_init ()
diff -Nru fenix-0.92a.dfsg1/debian/patches/series
fenix-0.92a.dfsg1/debian/patches/series
--- fenix-0.92a.dfsg1/debian/patches/series 2019-02-12 10:40:57.0
+0100
+++ fenix-0.92a.dfsg1/debian/patches/series 2021-05-10 21:39:02.0
+0200
@@ -35,3 +35,4 @@
fxc-cmdline-crash.patch
fxi-cmdline-title.patch
map-gif-256-colors.patch
+fix_ftbfs_gcc10.patch
diff -Nru fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm
fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm
--- fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm 2019-02-12
15:47:50.0 +0100
+++ fenix-0.92a.dfsg1/debian/tests/t/lib/Test/Fenix/Compile.pm 2021-05-11
22:17:32.0 +0200
@@ -41,12 +41,11 @@
Test::More::plan tests => 4;
my $cmd = Test::Command->new(cmd => [
- $fxc, $test->{test}{src}->basename,
+ $fxc, '-d', $test->{test}{src}->basename,
]);
$cmd->exit_is_num(0);
- # Yeah, this is backwards, I know...
- $cmd->stdout_is_eq('');
- $cmd->stderr_isnt_eq('');
+ $cmd->stdout_like(qr/END/);
+ $cmd->stderr_like(qr/- Main procedure/);
Test::More::ok -f $test->{test}{exe},
'the compiled program exists';
signature.asc
Description: PGP signature
Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
The issue may be related to this upstream issue: https://gitlab.gnome.org/GNOME/vala/-/issues/1167 I'll test using a patched version of vala and reassign if needed. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#988295: glabels: Maintainer email is not reachable
Source: glabels Severity: serious Justification: Policy 3.3 Dear Maintainer, The maintainer email ubuntu-devel-disc...@lists.ubuntu.com is a moderated mailing list. Mail sent from the BTS and submitters are not guaranteed to be delivered. (See the attached notification) Please use another reachable email as maintainer. Best, -- Baptiste Beauplat - lyknode --- Begin Message --- Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: https://lists.ubuntu.com/mailman/confirm/ubuntu-devel-discuss/7a82633fb9b2d298ac25c2c751cb765f617d0a22 --- End Message --- signature.asc Description: PGP signature
Bug#988294: libunity: Maintainer email is not reachable
Source: libunity Severity: serious Justification: Policy 3.3 Dear Maintainer, The maintainer email ubuntu-devel-disc...@lists.ubuntu.com is a moderated mailing list. Mail sent from the BTS and submitters are not guaranteed to be delivered. (See the attached notification) Please use another reachable email as maintainer. Best, -- Baptiste Beauplat - lyknode --- Begin Message --- Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: https://lists.ubuntu.com/mailman/confirm/ubuntu-devel-discuss/7a82633fb9b2d298ac25c2c751cb765f617d0a22 --- End Message --- signature.asc Description: PGP signature
Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
I started a bit of digging up on that FTBFS and I found that libunity build correctly with vala <= 0.48.13-1. A changed introduced in 0.48.14 must be at the origin of the bug. (I don't have sufficient knowledge of vala to get to the bottom of this issue, I just wanted to share this info) -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#987640: zsnes FTBFS with gcc 10
Control: tags -1 + patch
Dear maintainer,
The following patch fixes the FTBFS. I've tested it and I can run the
program and load a rom successfully.
Without feedback, I'll NMU the package and request an unblock in a
couple of days.
Best,
--
Baptiste Beauplat - lyknode
From: Baptiste Beauplat
Date: Wed, 5 May 2021 23:18:27 +0200
Subject: Fix FTBFS with gcc 10 (Closes: #987640)
Declare HacksDisable as external unsigned char in initc.c.
Declaration and assignation is done in cfg.c. This file is generated at
build time by parsegen from cfg.psr. The generated variable is an
unsigned char.
---
src/initc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/initc.c b/src/initc.c
index 3096240..56b02bc 100644
--- a/src/initc.c
+++ b/src/initc.c
@@ -1496,7 +1496,7 @@ Would be nice to trash this section in the future
extern unsigned char ENVDisable, cycpb268, cycpb358, cycpbl2, cycpblt2, cycpbl;
extern unsigned char cycpblt, opexec268, opexec358, opexec268b, opexec358b;
extern unsigned char opexec268cph, opexec358cph, opexec268cphb, opexec358cphb;
-bool HacksDisable;
+extern unsigned char HacksDisable;
void headerhack()
{
signature.asc
Description: PGP signature
Bug#983140: closed by Debian FTP Masters (reply to Lee Garrett ) (Bug#983140: fixed in ansible 2.10.7+merged+base+2.10.8+dfsg-1)
Hi Lee,
On 2021/04/19 11:06 PM, Debian Bug Tracking System wrote:
> #983140: ansible: Does not detect correct python interpreter on bullseye
> target
>
> It has been closed by Debian FTP Masters
> (reply to Lee Garrett ).
Glad to hear this will be fixed by this new version.
I was also working on a patch for 2.9.16 but I guess it's a bit late of
that :)
I'll attach it anyway for reference because I managed to have all unit
tests working by avoiding the user home directory. You might be
interested to have a look at that.
Thanks again for maintaining ansible!
Best,
--
Baptiste Beauplat - lyknode
diff -Nru ansible-2.9.16+dfsg/debian/changelog
ansible-2.9.16+dfsg/debian/changelog
--- ansible-2.9.16+dfsg/debian/changelog2021-01-06 11:56:22.0
+0100
+++ ansible-2.9.16+dfsg/debian/changelog2021-04-17 15:27:02.0
+0200
@@ -1,3 +1,11 @@
+ansible (2.9.16+dfsg-1.2) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Use python3.9 as default interpreter (Closes: #983140)
+ * Add autopkgtest to run a working subset of ansible test suite
+
+ -- Baptiste Beauplat Sat, 17 Apr 2021 15:27:02 +0200
+
ansible (2.9.16+dfsg-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru
ansible-2.9.16+dfsg/debian/patches/0007-fix-interpreter-fallback.patch
ansible-2.9.16+dfsg/debian/patches/0007-fix-interpreter-fallback.patch
--- ansible-2.9.16+dfsg/debian/patches/0007-fix-interpreter-fallback.patch
1970-01-01 01:00:00.0 +0100
+++ ansible-2.9.16+dfsg/debian/patches/0007-fix-interpreter-fallback.patch
2021-04-17 15:27:02.0 +0200
@@ -0,0 +1,33 @@
+Description: Fix python interpreter discovery (Closes: #983140)
+ On machines upgrade from buster to bullseye, the wrong interpreter will be
+ discovered and used, causing the playbook run to fail. Update the fallback
list
+ so it correctly picks python3.9 on bullseye when both 3.9 and 3.7 are present,
+ which usually is the case on freshly upgrade machines.
+Origin: backport,
https://github.com/ansible/ansible/commit/c986cbb9961bfaedf1a6ae7f0c2e34be26d9ab12
+Forwarded: not-needed
+Applied-Upstream:
https://github.com/ansible/ansible/commit/c986cbb9961bfaedf1a6ae7f0c2e34be26d9ab12
+Reviewed-by: Lee Garrett
+Last-Update: 2021-03-23
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/lib/ansible/config/base.yml
b/lib/ansible/config/base.yml
+@@ -1523,6 +1523,8 @@
+ name: Ordered list of Python interpreters to check for in discovery
+ default:
+ - /usr/bin/python
++ - python3.9
++ - python3.8
+ - python3.7
+ - python3.6
+ - python3.5
+--- a/test/lib/ansible_test/_internal/util.py
b/test/lib/ansible_test/_internal/util.py
+@@ -110,6 +110,7 @@
+ '3.6',
+ '3.7',
+ '3.8',
++'3.9',
+ )
+
+
diff -Nru ansible-2.9.16+dfsg/debian/patches/0008-fix-tests.patch
ansible-2.9.16+dfsg/debian/patches/0008-fix-tests.patch
--- ansible-2.9.16+dfsg/debian/patches/0008-fix-tests.patch 1970-01-01
01:00:00.0 +0100
+++ ansible-2.9.16+dfsg/debian/patches/0008-fix-tests.patch 2021-04-17
15:27:02.0 +0200
@@ -0,0 +1,44 @@
+From: Baptiste Beauplat
+Date: Mon, 19 Apr 2021 20:41:09 +0200
+Subject: Fix test suite
+
+* Mark two tests depending on pycrypto with the correct skipif
+* Inject remote_tmp configuration to point to /tmp to handle testbed without
+ HOME
+* Truncate output check on test_build_requirement_from_path_no_version due to
an
+ issue with text wrapping
+--- a/test/units/parsing/vault/test_vault.py
b/test/units/parsing/vault/test_vault.py
+@@ -528,6 +528,7 @@
+ b_key_pycrypto = self.vault_cipher._create_key_pycrypto(b_password,
b_salt, key_length=32, iv_length=16)
+ self.assertEqual(b_key_cryptography, b_key_pycrypto)
+
++@pytest.mark.skipif(not vault.HAS_PYCRYPTO, reason='Not testing
cryptography known key as pycrypto is not installed')
+ def test_create_key_known_cryptography(self):
+ b_password = b'hunter42'
+
+@@ -555,6 +556,7 @@
+ self.assertEqual(b_key_3, b_key_4)
+ self.assertEqual(b_key_1, b_key_4)
+
++@pytest.mark.skipif(not vault.HAS_PYCRYPTO, reason='Not testing pycrypto
known key as pycrypto is not installed')
+ def test_create_key_known_pycrypto(self):
+ b_password = b'hunter42'
+
+--- /dev/null
b/test/lib/ansible_test/_data/ansible.cfg
+@@ -0,0 +1,2 @@
++[defaults]
++remote_tmp = /tmp/ansible
+--- a/test/units/galaxy/test_collection_install.py
b/test/units/galaxy/test_collection_install.py
+@@ -242,8 +242,7 @@
+ assert mock_display.call_count == 1
+
+ actual_warn = ' '.join(mock_display.mock_calls[0][1][0].split('\n'))
+-expected_warn = "Collection at '%s' does not have a valid version set,
falling back to '*'. Found version: ''" \
+-% to_text(collection_artifact[0])
++expected_warn = "does not have a valid version set, falling back to '*'.
Found version:
Bug#983140: closed by Debian FTP Masters (reply to Lee Garrett ) (Bug#983140: fixed in ansible-base 2.10.5+dfsg-2)
Hi Lee, On 2021/03/23 08:51 PM, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the ansible package: > > #983140: ansible: Does not detect correct python interpreter on bullseye > target > > It has been closed by Debian FTP Masters > (reply to Lee Garrett ). This bug is still affecting bullseye and it will be autoremoved if no further action is taken. I saw that your unblock request [1] was rejected. As an alternative, you could do an upload with a minimal changeset to testing-proposed-updates as described in the devref [2]. That would allow ansible to remain in bullseye (and all other packages depending on it). Best, [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984557 [2]: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#direct-updates-to-testing -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#983641: network-manager-gnome: Wireguard connections cannot be enabled or disabled
Package: network-manager-gnome
Version: 1.20.0-2
Severity: important
Tags: patch
Dear Maintainer(s),
The network-manager-applet version in Debian bullseye has support to edit
Wireguard connections, which is a good thing (it was introduced upstream
in version 1.18.0).
However, it is not possible to enable or disable a Wireguard connection in
the applet. This is currently only possible through nmcli (a command-line
tool), which defeats the purpose of using a graphical tool like nm-applet.
This has been fixed upstream but didn't make it in time for the recent
1.20.0 release that Debian is currently using.
Since the fix involves only minor code changes on top of 1.20.0, I suggest
backporting the upstream patch in Debian. This will ensure that Wireguard
support is complete and that it can be used fully graphically in Debian
bullseye.
I am attaching the upstream patch, here are the upstream references:
https://gitlab.gnome.org/GNOME/network-manager-applet/-/commit/514d033b8d0b9e411ba7e878ddbfa338c6720e6f
https://gitlab.gnome.org/GNOME/network-manager-applet/-/merge_requests/95
Thank you,
Baptiste
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages network-manager-gnome depends on:
ii dbus-user-session [default-dbus-session-bus] 1.12.20-1
ii dbus-x11 [dbus-session-bus] 1.12.20-1
ii gnome-shell [polkit-1-auth-agent] 3.38.3-2
ii libatk1.0-0 2.36.0-2
ii libayatana-appindicator3-10.5.5-2
ii libc6 2.31-9
ii libcairo2 1.16.0-5
ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii libglib2.0-0 2.66.7-1
ii libgtk-3-03.24.24-1
ii libjansson4 2.13.1-1.1
ii libmm-glib0 1.14.10-0.1
ii libnm01.28.0-2+b1
ii libnma0 1.8.30-1
ii libnotify40.7.9-3
ii libpango-1.0-01.46.2-3
ii libpangocairo-1.0-0 1.46.2-3
ii libsecret-1-0 0.20.4-2
ii libselinux1 3.1-3
ii network-manager 1.28.0-2+b1
Versions of packages network-manager-gnome recommends:
ii gnome-keyring 3.36.0-1
ii gnome-shell [notification-daemon] 3.38.3-2
ii iso-codes 4.5.0-1
ii mobile-broadband-provider-info 20201225-1
ii notification-daemon3.20.0-4
Versions of packages network-manager-gnome suggests:
pn network-manager-openconnect-gnome
ii network-manager-openvpn-gnome 1.8.12-2
pn network-manager-pptp-gnome
pn network-manager-vpnc-gnome
-- no debconf information
>From 514d033b8d0b9e411ba7e878ddbfa338c6720e6f Mon Sep 17 00:00:00 2001
From: Beniamino Galvani
Date: Thu, 11 Feb 2021 09:45:00 +0100
Subject: [PATCH] applet: support activating WireGuard connections as VPNs
Display WireGuard connections in the VPN submenu and allow
[de]activating them.
https://gitlab.gnome.org/GNOME/network-manager-applet/-/issues/77
---
src/applet.c | 65
1 file changed, 45 insertions(+), 20 deletions(-)
diff --git a/src/applet.c b/src/applet.c
index 8ebac755..8cf6dc43 100644
--- a/src/applet.c
+++ b/src/applet.c
@@ -875,6 +875,13 @@ applet_is_any_device_activating (NMApplet *applet)
return FALSE;
}
+static gboolean
+connection_is_vpn (NMConnection *connection)
+{
+ returnnm_connection_is_type (connection,
NM_SETTING_VPN_SETTING_NAME)
+ || nm_connection_is_type (connection,
NM_SETTING_WIREGUARD_SETTING_NAME);
+}
+
static gboolean
applet_is_any_vpn_activating (NMApplet *applet)
{
@@ -1062,10 +1069,13 @@ nma_menu_vpn_item_clicked (GtkMenuItem *item, gpointer
user_data)
return;
}
- active = applet_get_default_active_connection (applet, , FALSE);
- if (!active || !device) {
- g_warning ("%s: no active connection or device.", __func__);
- return;
+ if (nm_connection_is_type (connection, NM_SETTING_VPN_SETTING_NAME)) {
+ active = applet_get_default_active_connection (applet, ,
FALSE);
+ if (!active || !device) {
+ /* FIXME: show a UI notification ? */
+ g_warning ("%s: no active connection or d
Bug#963025: firmware-iwlwifi: Microcode SW error detected / 9000-pu-b0-jf-b0-46.ucode
Hello, Just add another error this morning. You can find my dmesg -T output as attachement. Some context: * the error occured right after laptop boot * My Wifi setup: AP was forced to use frequency of 5240GHz and offered 20/40/80MHz channel width. Moving AP to 5180GHz solve the issue. My understanding: It *seems* that iwlwifi could have issues with DFS frequencies, not with channel width. My last report was also linked to DFS channels being used. Moving away from DFS channel solve the issue, at least for me. Have a nice day, Jean Baptiste [Fri Feb 19 08:52:32 2021] wlo1: authenticate with cc:2d:e0:97:99:de [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: Start IWL Error Log Dump: [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: Status: 0x0040, count: 6 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: Loaded firmware version: 46.4d093a30.0 9000-pu-b0-jf-b0-46.ucode [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x14FD | ADVANCED_SYSASSERT [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x00A022F0 | trm_hw_status0 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | trm_hw_status1 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x00488876 | branchlink2 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x00478E36 | interruptlink1 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | interruptlink2 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x002E | data1 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0xDEADBEEF | data2 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0xDEADBEEF | data3 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | beacon time [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0049D5BB | tsf low [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | tsf hi [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | time gp1 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0049D5BD | time gp2 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0001 | uCode revision type [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x002E | uCode version major [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x4D093A30 | uCode version minor [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0312 | hw version [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x00489008 | board version [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x803EF405 | hcmd [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x00022000 | isr0 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | isr1 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x08201802 | isr2 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x00413C80 | isr3 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | isr4 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x003E019F | last cmd Id [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0001AE22 | wait_event [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x00B4 | l2p_control [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | l2p_duration [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x000F | l2p_mhvalid [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | l2p_addr_match [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x000D | lmpm_pmg_sel [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x01102344 | timestamp [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x7098 | flow_handler [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: Start IWL Error Log Dump: [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: Status: 0x0040, count: 7 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | umac branchlink1 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0xC0088BBE | umac branchlink2 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x010195B4 | umac interruptlink1 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0101B68C | umac interruptlink2 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0800 | umac data1 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0101B68C | umac data2 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x002E | umac major [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x4D093A30 | umac minor [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x0049D5D8 | frame pointer [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0xC0887530 | stack pointer [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x003F0108 | last host cmd [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | isr status reg [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: Fseq Registers: [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x23D682E2 | FSEQ_ERROR_CODE [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [Fri Feb 19 08:52:32 2021] iwlwifi :00:14.3
Bug#982878: aspell-hsb: diff for NMU version 0.02.0-1.2
Control: tags 982878 + patch
Dear maintainer,
I've prepared an NMU for aspell-hsb (versioned as 0.02.0-1.2). The diff
is attached to this message.
I'm Cc'ing Andreas for review and upload in a the DELAYED/10 queue.
Regards.
--
Baptiste Beauplat - lyknode
diff -Nru aspell-hsb-0.02.0/debian/changelog aspell-hsb-0.02.0/debian/changelog
--- aspell-hsb-0.02.0/debian/changelog 2021-01-03 14:24:26.0 +0100
+++ aspell-hsb-0.02.0/debian/changelog 2021-02-15 20:38:43.0 +0100
@@ -1,3 +1,18 @@
+aspell-hsb (0.02.0-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Leave rws and compat file generation to aspell-autobuildhash
+(Closes: #982878):
+- Bump dictionaries-common-dev version to 1.23 in Build-Depends, required
+ to automatically create symlinks and clean files
+- Replace aspell and dictionaries-common Depends by ${aspell:Depends}
+- Drop .rws and .compat files and links from the package, now generated
+ at installation time, by aspell-autobuildhash trigger
+- Add Auto-Compat field in info-aspell to trigger .compat file
+ generation
+
+ -- Baptiste Beauplat Mon, 15 Feb 2021 20:38:43 +0100
+
aspell-hsb (0.02.0-1.1) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru aspell-hsb-0.02.0/debian/control aspell-hsb-0.02.0/debian/control
--- aspell-hsb-0.02.0/debian/control 2010-04-23 11:25:22.0 +0200
+++ aspell-hsb-0.02.0/debian/control 2021-02-15 20:37:46.0 +0100
@@ -2,12 +2,12 @@
Section: text
Priority: optional
Maintainer: Jan Jeroným Zvánovec
-Build-Depends: debhelper (>= 7), cdbs (>= 0.4.0), dictionaries-common-dev (>= 1.4.0)
+Build-Depends: debhelper (>= 7), cdbs (>= 0.4.0), dictionaries-common-dev (>= 1.23.0)
Standards-Version: 3.8.4
Package: aspell-hsb
Architecture: all
-Depends: aspell (>= 0.60.6-2), dictionaries-common (>= 1.4.0), ${misc:Depends}
+Depends: ${aspell:Depends}, ${misc:Depends}
Provides: aspell-dictionary
Description: Upper Sorbian dictionary for GNU Aspell
This package contains all the required files to add support for the
diff -Nru aspell-hsb-0.02.0/debian/info-aspell aspell-hsb-0.02.0/debian/info-aspell
--- aspell-hsb-0.02.0/debian/info-aspell 2010-04-23 11:25:22.0 +0200
+++ aspell-hsb-0.02.0/debian/info-aspell 2021-02-15 20:37:24.0 +0100
@@ -1,2 +1,3 @@
Language: hornjoserbsce (Upper Sorbian)
Hash-Name: hsb
+Auto-Compat: hsb
diff -Nru aspell-hsb-0.02.0/debian/rules aspell-hsb-0.02.0/debian/rules
--- aspell-hsb-0.02.0/debian/rules 2010-04-23 11:25:22.0 +0200
+++ aspell-hsb-0.02.0/debian/rules 2021-02-15 20:37:05.0 +0100
@@ -5,9 +5,6 @@
install/aspell-hsb::
gzip -9 -c hsb.cwl > "$(DEB_DESTDIR)/usr/share/aspell/hsb.cwl.gz";\
- touch "$(DEB_DESTDIR)/var/lib/aspell/hsb.rws"
- dh_link "/var/lib/aspell/hsb.rws" "/usr/lib/aspell/hsb.rws"
- touch $(DEB_DESTDIR)/var/lib/aspell/hsb.compat
echo "hsb" >> "$(DEB_DESTDIR)/usr/share/aspell/hsb.contents"
installdeb-aspell
signature.asc
Description: PGP signature
Bug#982878: aspell-hsb: packaged files modified after unpacking
Package: aspell-hsb Version: 0.02.0-1.1 Severity: normal Dear Maintainer, Your package fails to pass piuparts with the following error: 1m14.5s DEBUG: Command failed (status=2), but ignoring error: ['debsums', '--root', '/var/run/schroot/mount/unstable-amd64-sbuild-bf8a8b28-6fc3-11eb-a4c5-4574f60a5b4f-piuparts', '-ac', '--ignore-obsolete'] 1m14.5s ERROR: FAIL: debsums reports modifications inside the chroot: /var/lib/aspell/hsb.compat /var/lib/aspell/hsb.rws Those shipped files are modified after unpacking, see https://piuparts.debian.org/sid/debsums_mismatch_error.html Using recent version of dictionary-common-dev will allow you to generate compat and rws automatically by triggering aspell-autobuildhash and get rid of this error. I'll be working on proposing an NMU for this bug. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#963025: (no subject)
Got the same issue with latest kernel and iwlwifi firmware from sid > cat /proc/version Linux version 5.10.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.10.12-1 (2021-01-30) > dpkg -l firmware-iwlwifi ii firmware-iwlwifi 20201218-3 all Binary firmware for Intel Wireless cards As far as I can tell, it only happens when trying to connect to a 5GHz wifi network using 80mhz wide channel. I updated my AP configuration to use only 20 or 40mhz channels and everything works fine now. I also found an old bug [1] describing the same issue, but it's stated to be solved and has been closed. Hope this can help, Cheers, Jean Baptiste [1]: https://bugzilla.kernel.org/show_bug.cgi?id=205055 OpenPGP_signature Description: OpenPGP digital signature
Bug#979641: src:kboot-utils: invalid maintainer address
On 2021/02/03 07:10 PM, Antonio Ospite wrote: > On Wed, 3 Feb 2021 09:43:30 +0100 > Baptiste Beauplat wrote: > > [...] > > > > I could open the RM bug on your behalf if you want me to. > > > > Thank you, I would appreciate that. Created as #981795 https://bugs.debian.org/981795 -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981795: RM: kboot-utils -- ROM; RC-buggy, unmaintained, low popcon
Package: ftp.debian.org Severity: normal I'm requesting removal of kboot-utils in unstable on behalf of its maintainer. See #979641 for details. This package has no rdepends. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#979641: src:kboot-utils: invalid maintainer address
On 2/3/21 9:37 AM, Antonio Ospite wrote: > On Tue, 2 Feb 2021 20:51:24 +0100 > Baptiste Beauplat wrote: > >> Hi Antonio, >> >> On 2021/01/25 09:23 AM, Baptiste Beauplat wrote: > [..] >>> >>> Well, installation stats for kboot-utils are close to 0 [1]. A possible >>> solution would be to request its removal [2]. If it appears that it was >>> actually needed, it could be re-introduced at a later point (not for the >>> next stable but I don't think that's a problem). >>> >>> [1]: https://qa.debian.org/popcon.php?package=kboot-utils >>> [2]: >>> https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removing-packages >> >> Have you decided the course of action for kboot-utils yet? >> > > Hi Baptiste, > > I would be fine with having it removed, I just haven't had the time to > read through your links. I could open the RM bug on your behalf if you want me to. -- Baptiste Beauplat - lyknode
Bug#980844: libbiblio-isis-perl: diff for NMU version 0.24-1.3
Control: tags 980844 + patch Control: tags 980844 + pending Dear maintainer, I've prepared an NMU for libbiblio-isis-perl (versioned as 0.24-1.3). The diff is attached to this message. I'm cc'ing my usual sponsor for upload. Regards. -- Baptiste Beauplat - lyknode diff -u libbiblio-isis-perl-0.24/debian/changelog libbiblio-isis-perl-0.24/debian/changelog --- libbiblio-isis-perl-0.24/debian/changelog +++ libbiblio-isis-perl-0.24/debian/changelog @@ -1,3 +1,10 @@ +libbiblio-isis-perl (0.24-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * Fix Maintainer email address (Closes: #980844) + + -- Baptiste Beauplat Tue, 02 Feb 2021 21:03:11 +0100 + libbiblio-isis-perl (0.24-1.2) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -u libbiblio-isis-perl-0.24/debian/control libbiblio-isis-perl-0.24/debian/control --- libbiblio-isis-perl-0.24/debian/control +++ libbiblio-isis-perl-0.24/debian/control @@ -3,7 +3,7 @@ Priority: optional Build-Depends: debhelper (>= 5.0.0) Build-Depends-Indep: perl (>= 5.8.8-7) -Maintainer: Jose Parrella +Maintainer: Jose Parrella Standards-Version: 3.7.2 Package: libbiblio-isis-perl signature.asc Description: PGP signature
Bug#979641: src:kboot-utils: invalid maintainer address
Hi Antonio, On 2021/01/25 09:23 AM, Baptiste Beauplat wrote: > On 2021/01/25 12:18 AM, Antonio Ospite wrote: > > On Sun, 24 Jan 2021 21:12:54 +0100 > > Baptiste Beauplat wrote: > > > > > Hi Antonio, > > > > > > kboot-utils, one of the packages you maintain in Debian has an old, > > > unreachable > > > Maitainer address. Could you please update it to prevent it from getting > > > removed? > > > > > > See below the original bug report. > > > > > > > Thank you for reporting this Baptiste. > > > > I am actually not sure how useful kboot-utils is nowadays, it was mainly > > developed to make it easier to boot kernels on the Sony PS3, but I don't > > think the PS3 is supported by Debian directly anymore. > > > > However I would be happy to update the package anyway if there was > > someone interested to sponsor it, since I cannot upload packages > > myself and the I doubt my usual sponsor would be interested in it. > > Well, installation stats for kboot-utils are close to 0 [1]. A possible > solution would be to request its removal [2]. If it appears that it was > actually needed, it could be re-introduced at a later point (not for the > next stable but I don't think that's a problem). > > [1]: https://qa.debian.org/popcon.php?package=kboot-utils > [2]: > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removing-packages Have you decided the course of action for kboot-utils yet? -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981676: O: hunt -- Advanced packet sniffer and connection intrusion
Package: wnpp The current maintainer of hunt, Angel Ramos , is apparently not active anymore. Therefore, I orphan this package now. 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. Some information about this package: Package: hunt Binary: hunt Version: 1.5-6.1 Maintainer: Angel Ramos Build-Depends: debhelper (>= 5.0.0) Architecture: any Standards-Version: 3.8.0 Format: 1.0 Files: b64eb3ba7c9c085c94b148b2c0f65a50 1707 hunt_1.5-6.1.dsc 5a8886784d1668a8518d5562bfd01ae7 99241 hunt_1.5.orig.tar.gz f98718b41f1960a351e3a6231fe2a12e 4556 hunt_1.5-6.1.diff.gz Checksums-Sha256: 45f83b5821093023791bc8505150a37d1f4b98beb7835d79a5448e34fe9a2408 1707 hunt_1.5-6.1.dsc a8a1978f3bd05ca3f01c168c13c9a09b1e1e9038c14fdfe43694c07fe3a0e328 99241 hunt_1.5.orig.tar.gz 91996bfdb25656b3ea02072a47754ae19dc43fb605da0df89c73231c6fd57207 4556 hunt_1.5-6.1.diff.gz Package-List: hunt deb net optional arch=any Directory: pool/main/h/hunt Priority: source Section: net Package: hunt Source: hunt (1.5-6.1) Version: 1.5-6.1+b1 Installed-Size: 178 Maintainer: Angel Ramos Architecture: amd64 Depends: libc6 (>= 2.14) Description: Advanced packet sniffer and connection intrusion Description-md5: 9c7e9f0b4f1d0eda85455deadab35262 Tag: interface::commandline, network::scanner, role::program, scope::utility Section: net Priority: optional Filename: pool/main/h/hunt/hunt_1.5-6.1+b1_amd64.deb Size: 83936 MD5sum: 1ffd6a9005a0e5770ecf5291458c08af SHA256: 5a9a902fb011f6a5d37119e5977d6f261dd819cca11c6ab4c186395cb258e855 -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981675: O: cvsdelta -- Summarize differences in a CVS repository
Package: wnpp The current maintainer of cvsdelta, Angel Ramos , is apparently not active anymore. Therefore, I orphan this package now. 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. Some information about this package: Package: cvsdelta Binary: cvsdelta Version: 1.7.0-6.1 Maintainer: Angel Ramos Build-Depends: debhelper (>= 4.1), cdbs Build-Depends-Indep: ruby (>> 1.6) Architecture: all Standards-Version: 3.8.1 Format: 1.0 Files: e333c594e86f8f4fa68aa5c556f7f4dc 1803 cvsdelta_1.7.0-6.1.dsc 6cde56d286d2bbde51b85996416bb12f 20303 cvsdelta_1.7.0.orig.tar.gz 935672e0303060e51099757630877f03 2070 cvsdelta_1.7.0-6.1.diff.gz Vcs-Browser: http://git.debian.org/?p=collab-maint/cvsdelta.git Vcs-Git: git://git.debian.org/git/collab-main/cvsdelta.git Checksums-Sha256: fda652ba1efa3b00ccdd20b16b764de8cabf73d52e0fa12aa76627e8088b6476 1803 cvsdelta_1.7.0-6.1.dsc 6d1f373af970499b61d623028a3e67a68ec5180579674e65fe4a60118279f064 20303 cvsdelta_1.7.0.orig.tar.gz 60668a753f7bcffc18ae8e1b641d6dabedb5851becf2db7f0b6274b7b9e1724a 2070 cvsdelta_1.7.0-6.1.diff.gz Package-List: cvsdelta deb vcs optional arch=all Directory: pool/main/c/cvsdelta Priority: source Section: vcs Package: cvsdelta Version: 1.7.0-6.1 Installed-Size: 67 Maintainer: Angel Ramos Architecture: all Description: Summarize differences in a CVS repository Description-md5: 6b81034d2df8c98cccbf54913ce07db9 Tag: devel::rcs, interface::commandline, role::program, scope::utility, use::monitor, use::synchronizing Section: vcs Priority: optional Filename: pool/main/c/cvsdelta/cvsdelta_1.7.0-6.1_all.deb Size: 20304 MD5sum: d66eaf5d1ed55024268de142b6eea4cb SHA256: c8210b8fea6f9165e2fc154069a9a0bc626a839e00669886fb2c8afc8856a6b3 -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981674: O: abicheck -- binary compatibility checking tool
Package: wnpp The current maintainer of abicheck, Angel Ramos , is apparently not active anymore. Therefore, I orphan this package now. 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. Some information about this package: Package: abicheck Binary: abicheck Version: 1.2-5.1 Maintainer: Angel Ramos Build-Depends: debhelper (>> 5.0.0) Build-Depends-Indep: perl Architecture: all Standards-Version: 3.8.1 Format: 1.0 Files: 6648d17b58508b49f982ecd4698b3b18 1655 abicheck_1.2-5.1.dsc 57097ed1f8c20d974b0b1a9850e61f08 53543 abicheck_1.2.orig.tar.gz d00e3854689fc3a86c52dddf95b1b1e7 2383 abicheck_1.2-5.1.diff.gz Checksums-Sha256: 0d4e7fef97ffa94b55540a19a835fdcf6fdd5525a472e946fc2be4e5f63c8d0c 1655 abicheck_1.2-5.1.dsc b53a2e08da609e8d2fe13d7f9c2966598d2b4991e0d473572010eb39d151d803 53543 abicheck_1.2.orig.tar.gz e79e924a9173c7e847f746c335bb8fa997facc22a329f3820c57db9124695659 2383 abicheck_1.2-5.1.diff.gz Package-List: abicheck deb devel optional arch=all Directory: pool/main/a/abicheck Priority: source Section: libs Package: abicheck Version: 1.2-5.1 Installed-Size: 107 Maintainer: Angel Ramos Architecture: all Depends: perl Description: binary compatibility checking tool Description-md5: a38281f070a37064c10336aabb05a83f Tag: devel::buildtools, devel::lang:c, devel::lang:perl, devel::library, devel::testing-qa, implemented-in::c, implemented-in::perl, interface::commandline, role::devel-lib, role::program, scope::utility, use::checking Section: devel Priority: optional Filename: pool/main/a/abicheck/abicheck_1.2-5.1_all.deb Size: 31752 MD5sum: ed12e9075e096f6af80eed44d995a439 SHA256: e1180e8b8a31bf9597ef34f88c2ea48ad94eb9c734fd7c6da93b438b99f712e1 -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#979052: nam: diff for NMU version 1.15-5.2
Control: tags 979052 + patch Control: tags 979052 + pending Dear maintainer, I've prepared an NMU for nam (versioned as 1.15-5.2). The diff is attached to this message. I'm cc'ing my usual sponsor for upload. Regards. -- Baptiste Beauplat - lyknode diff -Nru nam-1.15/debian/changelog nam-1.15/debian/changelog --- nam-1.15/debian/changelog 2021-01-02 01:09:06.0 +0100 +++ nam-1.15/debian/changelog 2021-02-02 19:55:11.0 +0100 @@ -1,3 +1,10 @@ +nam (1.15-5.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix Maintainer email address (Closes: #979052) + + -- Baptiste Beauplat Tue, 02 Feb 2021 19:55:11 +0100 + nam (1.15-5.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru nam-1.15/debian/control nam-1.15/debian/control --- nam-1.15/debian/control 2016-11-02 15:37:23.0 +0100 +++ nam-1.15/debian/control 2021-02-02 19:55:07.0 +0100 @@ -1,7 +1,7 @@ Source: nam Section: net Priority: optional -Maintainer: Debian Network Simulators Team +Maintainer: Debian Network Simulators Team Uploaders: YunQiang Su Build-Depends: debhelper (>= 8), quilt (>= 0.46-7~), cmake, tcl-dev (>=8.6), tk-dev (>=8.6), libxt-dev, libxmu-headers, signature.asc Description: PGP signature
Bug#979246: fonts-ddc-uchen: diff for NMU version 1.0-1.2
Control: tags 979246 + patch Control: tags 979246 + pending Dear maintainer, I've prepared an NMU for fonts-ddc-uchen (versioned as 1.0-1.2). The diff is attached to this message. I'm cc'ing my usual sponsor for upload. Regards. -- Baptiste Beauplat - lyknode diff -Nru fonts-ddc-uchen-1.0/debian/changelog fonts-ddc-uchen-1.0/debian/changelog --- fonts-ddc-uchen-1.0/debian/changelog 2021-01-04 15:18:46.0 +0100 +++ fonts-ddc-uchen-1.0/debian/changelog 2021-02-02 18:21:19.0 +0100 @@ -1,3 +1,10 @@ +fonts-ddc-uchen (1.0-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix Maintainer email address (Closes: #979246) + + -- Baptiste Beauplat Tue, 02 Feb 2021 18:21:19 +0100 + fonts-ddc-uchen (1.0-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. diff -Nru fonts-ddc-uchen-1.0/debian/control fonts-ddc-uchen-1.0/debian/control --- fonts-ddc-uchen-1.0/debian/control 2016-10-09 19:19:48.0 +0200 +++ fonts-ddc-uchen-1.0/debian/control 2021-02-02 18:20:51.0 +0100 @@ -1,7 +1,7 @@ Source: fonts-ddc-uchen Section: fonts Priority: optional -Maintainer: Sruthi Chandran +Maintainer: Sruthi Chandran Vcs-Git: https://anonscm.debian.org/git/debian-in/ddc-uchen.git Vcs-Browser: https://anonscm.debian.org/cgit/debian-in/fonts-ddc-uchen.git Homepage: http://www.dzongkha.gov.bt/IT/download/fonts/ signature.asc Description: PGP signature
Bug#979980: lintian: Please backport 2.104.0 to buster
On 2021/01/21 12:58 PM, Felix Lechner wrote: > Hi Chris, > > On Tue, Jan 12, 2021 at 6:45 AM Baptiste Beauplat wrote: > > > > Could we please have a bpo build for 2.104.0? > > Hope all is well! Can you please help? Hi Chris, any update on this? mentors.d.n still warns users about the unknown last version of the std-ver. -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981055: O: john -- active password cracking tool
On 2021/01/26 05:15 PM, Axel Beckert wrote: > Hi Julián, > > cool to hear from you! (Actually didn't expect a that quick reaction. :-) > > Julián Moreno Patiño wrote: > > I will continue maintaining john the ripper package, but please go > > ahead with the QA Upload. > Mmm, I should I checked with you first before orphaning the package. Sorry about that Julián, I'll be more thorough next time :) -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981060: O: blag-fortune -- anarchist quotes for fortune
Package: wnpp The current maintainer of blag-fortune, Valerie R Young , is apparently not active anymore. Therefore, I orphan this package now. 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. Some information about this package: Package: blag-fortune Binary: fortune-anarchism Version: 1.2-1.1 Maintainer: Valerie R Young Build-Depends: debhelper (>= 9), fortune-mod Architecture: all Standards-Version: 4.0.1 Format: 3.0 (quilt) Files: ed62f16bef39c13f16365aad5c1341de 1777 blag-fortune_1.2-1.1.dsc a095c94c55eabece0b6c40410849e6eb 36734 blag-fortune_1.2.orig.tar.gz c0e0046965f77dd46f51cefa409b9308 1888 blag-fortune_1.2-1.1.debian.tar.xz Checksums-Sha256: dc7f4fd4f5414417d8f421d0513727e671d9e9ddf9bc2a700dc454bd0090b456 1777 blag-fortune_1.2-1.1.dsc 4b0829abe4c8bf761fb8451669a2bb150086f7d4ef49d9ad26c2c41aee8796be 36734 blag-fortune_1.2.orig.tar.gz 0917c511843626dd4aa9db568530bb196021e9cd56a497840e567d7bba279c03 1888 blag-fortune_1.2-1.1.debian.tar.xz Homepage: https://notabug.org/PangolinTurtle/BLAG-fortune Package-List: fortune-anarchism deb games optional arch=all Directory: pool/main/b/blag-fortune Priority: extra Section: misc Package: fortune-anarchism Source: blag-fortune Version: 1.2-1.1 Installed-Size: 100 Maintainer: Valerie R Young Architecture: all Recommends: fortune-mod Suggests: anarchism Description: anarchist quotes for fortune Description-md5: 55d68a63ebf7964185e78bb2768142f8 Multi-Arch: foreign Homepage: https://notabug.org/PangolinTurtle/BLAG-fortune Section: games Priority: optional Filename: pool/main/b/blag-fortune/fortune-anarchism_1.2-1.1_all.deb Size: 28876 MD5sum: f551a8280ca41deba8cd02c3ccbb285e SHA256: 73e91afa703f4298febb3bb4cb3fb7be0ef45466c9463ce63291e286830898e7 -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981056: O: aspell-hr -- The Croatian dictionary for GNU Aspell
Package: wnpp The current maintainer of aspell-hr, Vedran Furač , is apparently not active anymore. Therefore, I orphan this package now. 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. Some information about this package: Package: aspell-hr Binary: aspell-hr Version: 0.51-4.1 Maintainer: Vedran Furač Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 5), dictionaries-common-dev (>= 0.9.1) Architecture: all Standards-Version: 3.7.2 Format: 1.0 Files: 245621118e86b6a0a8b0119190eb1047 1702 aspell-hr_0.51-4.1.dsc dc5ec4fad05b2fa2e16ca6fcac00fe5a 292768 aspell-hr_0.51.orig.tar.gz aefd79e4ff3979ab4b601241c0e51527 1776 aspell-hr_0.51-4.1.diff.gz Checksums-Sha256: 61f7b19685d7ba0dbaa7ea2bd18aea6d9cc4104861725d654b630955f819c20a 1702 aspell-hr_0.51-4.1.dsc 6bf263e1f0e1d6fd97fcd3e3e1455a19feb7f0ec79e5de0f00e66638f6f765bf 292768 aspell-hr_0.51.orig.tar.gz c9e137f860240feeef926e4d97e99f4cd13555a1e0da18c21bc990ab206fb157 1776 aspell-hr_0.51-4.1.diff.gz Package-List: aspell-hr deb text optional arch=all Directory: pool/main/a/aspell-hr Priority: source Section: text Package: aspell-hr Version: 0.51-4.1 Installed-Size: 300 Maintainer: Vedran Furač Architecture: all Provides: aspell-dictionary Depends: aspell (>= 0.60.3-3), dictionaries-common (>= 0.49.2) Description: The Croatian dictionary for GNU Aspell Description-md5: dd71d8327ff9d0ab0412b5fa4e610dc1 Tag: culture::croatian, made-of::dictionary, role::app-data, suite::gnu, use::checking Section: text Priority: optional Filename: pool/main/a/aspell-hr/aspell-hr_0.51-4.1_all.deb Size: 282800 MD5sum: f8ec0adb67f9d476b5195203f21be4b9 SHA256: 88547bb8796008ff015a410591bc31eb8fd3b6842ccd01f45077b0d4e06383a8 -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981055: O: john -- active password cracking tool
Package: wnpp The current maintainer of john, Ruben Molina , is apparently not active anymore. Therefore, I orphan this package now. 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. Some information about this package: Package: john Binary: john, john-data Version: 1.8.0-2.1 Maintainer: Ruben Molina Uploaders: Julián Moreno Patiño Build-Depends: debhelper (>= 9.0.0~), dpkg-dev (>= 1.16.1~) Architecture: any all Standards-Version: 3.9.5 Format: 3.0 (quilt) Files: 073487403cea377fe69b766c6b0f4be7 1817 john_1.8.0-2.1.dsc f73cb34f35f300535f9f77213f4199a9 5450412 john_1.8.0.orig.tar.gz f9c123f52a3e788f4b83a155e75350f7 28364 john_1.8.0-2.1.debian.tar.xz Checksums-Sha256: d78186f3af858ade0796231c506189b3e6f9382e0a605e58825b2133c338a701 1817 john_1.8.0-2.1.dsc 1222738c7829ce3014177ca9bd26c41573426f883c6b22527ee9bde363d84bda 5450412 john_1.8.0.orig.tar.gz a101cef35e1065cc7f86a77931088c2e833c44a985cf323aa8856d87d3628f8d 28364 john_1.8.0-2.1.debian.tar.xz Homepage: http://www.openwall.com/john/ Package-List: john deb admin optional arch=any john-data deb admin optional arch=all Directory: pool/main/j/john Priority: source Section: admin Package: john Version: 1.8.0-2.1 Installed-Size: 452 Maintainer: Ruben Molina Architecture: amd64 Depends: libc6 (>= 2.14), libcrypt1 (>= 1:4.1.0), john-data (= 1.8.0-2.1) Suggests: wordlist Description: active password cracking tool Description-md5: 2ffcaf0da9fa0a8266bfe4aa906d4742 Homepage: http://www.openwall.com/john/ Tag: implemented-in::c, interface::commandline, role::program, scope::utility, security::authentication, use::checking Section: admin Priority: optional Filename: pool/main/j/john/john_1.8.0-2.1_amd64.deb Size: 204428 MD5sum: b83b6a7de191cecf236cba0b5406fb24 SHA256: af355fd9c17740a567fee425b1e6bca5030af37c9f2f5a9a3154ede7c6539b99 Package: john-data Source: john Version: 1.8.0-2.1 Installed-Size: 7255 Maintainer: Ruben Molina Architecture: all Enhances: john Breaks: john (<= 1.7.2-1) Description: active password cracking tool - character sets Description-md5: a3317ed0e06a264c46ef425d9336ae80 Homepage: http://www.openwall.com/john/ Tag: made-of::dictionary, role::app-data, security::cryptography, use::checking Section: admin Priority: optional Filename: pool/main/j/john/john-data_1.8.0-2.1_all.deb Size: 4286680 MD5sum: a8261c44b7383bb89bd7229e4de505e5 SHA256: 34413d71a52f16ab783ee45bd5d8bb0195a8cfe8f73f29f11c3ff19db3807e5a -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#976832: src:crashmail: invalid maintainer address
Hi, The maintainer email of your packages is not reachable anymore. Could you please update it so your packages make it into the next stable release? If you do not intend to maintain those you also have the possibility to orphan them. Best, On 2020/12/08 12:30 PM, Ansgar wrote: > Source: crashmail > Version: 1.7-1.1 > Severity: serious > X-Debbugs-Cc: Sudip Mukherjee > > The maintainer address is invalid, see below. > > Ansgar > > Forwarded Message > Subject: Mail delivery failed: returning message to sender > Date: Fri, 04 Dec 2020 22:21:08 + > > > This message was created automatically by mail delivery software. > > > > A message that you sent could not be delivered to one or more of its > > recipients. This is a permanent error. The following address(es) > > failed: > > > > j...@rocasa.us > > host a585612.mx.mailhop.org [54.191.214.36] > > SMTP error from remote mail server after RCPT > > TO:: > > 554 5.7.1 We do not relay rocasa.us > > Reporting-MTA: dns; mailly.debian.org > > Action: failed > Final-Recipient: rfc822;j...@rocasa.us > Status: 5.0.0 > Remote-MTA: dns; a585612.mx.mailhop.org > Diagnostic-Code: smtp; 554 5.7.1 We do not relay rocasa.us > -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
Bug#981053: O: libloki -- C++ library of generic design patterns
Package: wnpp The current maintainer of libloki, Petr Baranov , is apparently not active anymore. Therefore, I orphan this package now. 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. Some information about this package: Package: libloki Binary: libloki0.1.7, libloki0.1.7-dbg, libloki-dev, libloki-doc Version: 0.1.7-3.1 Maintainer: Petr Baranov Build-Depends: debhelper (>= 7) Architecture: any all Standards-Version: 3.9.2 Format: 1.0 Files: 1842491da261ce30ddeefe39b7677a39 1858 libloki_0.1.7-3.1.dsc af532c24a7f2e12d0829be8201934d92 546329 libloki_0.1.7.orig.tar.gz 47849371f239884c6403e10d9111d766 5108 libloki_0.1.7-3.1.diff.gz Checksums-Sha256: 30ce97c77485fdb7237698fe93c1c73d62df00985b399b344148b67d92a2b740 1858 libloki_0.1.7-3.1.dsc 0c2094ce916b106731c8be61c32f538a22e1c0f8398bd5d6295b13d08e0c41a3 546329 libloki_0.1.7.orig.tar.gz 28f5658c302487b65e34b75fcdd7e8b8d0632a35bcf22a5bd315b0f73a80d7a7 5108 libloki_0.1.7-3.1.diff.gz Homepage: http://loki-lib.sourceforge.net/ Package-List: libloki-dev deb libdevel optional arch=any libloki-doc deb doc optional arch=all libloki0.1.7 deb libs optional arch=any libloki0.1.7-dbg deb debug extra arch=any Directory: pool/main/libl/libloki Priority: source Section: libs Package: libloki0.1.7 Source: libloki Version: 0.1.7-3.1 Installed-Size: 83 Maintainer: Petr Baranov Architecture: amd64 Depends: libc6 (>= 2.14), libgcc-s1 (>= 3.4), libstdc++6 (>= 5.2) Description: C++ library of generic design patterns Description-md5: 6739a39161c88b23811b4ba1dab21de3 Homepage: http://loki-lib.sourceforge.net/ Tag: role::shared-lib Section: libs Priority: optional Filename: pool/main/libl/libloki/libloki0.1.7_0.1.7-3.1_amd64.deb Size: 28184 MD5sum: e1c8f22f8bff4240e48f6926904265ff SHA256: 22fad5a9b5ce3417892b646668cb850e151e9435f2eebd2cf66cc9c807337d87 Package: libloki0.1.7-dbg Source: libloki Version: 0.1.7-3.1 Installed-Size: 608 Maintainer: Petr Baranov Architecture: amd64 Depends: libloki0.1.7 (= 0.1.7-3.1) Description: C++ library of generic design patterns (debug information) Description-md5: fdb9bc54831b9595d89b58b8ba1359e7 Homepage: http://loki-lib.sourceforge.net/ Tag: role::debug-symbols Section: debug Priority: optional Filename: pool/main/libl/libloki/libloki0.1.7-dbg_0.1.7-3.1_amd64.deb Size: 156112 MD5sum: ac4cb1a6b516b90e496284808c192cf0 SHA256: 455753bd73e9c50227fa9599b61a6953f443a5a685c27f333ecea53359f79911 Package: libloki-dev Source: libloki Version: 0.1.7-3.1 Installed-Size: 1030 Maintainer: Petr Baranov Architecture: amd64 Depends: libloki0.1.7 (= 0.1.7-3.1) Suggests: libloki-doc Description: C++ library of generic design patterns (development files) Description-md5: 515a69925b158edce917033e8077cf32 Homepage: http://loki-lib.sourceforge.net/ Tag: devel::library, role::devel-lib Section: libdevel Priority: optional Filename: pool/main/libl/libloki/libloki-dev_0.1.7-3.1_amd64.deb Size: 132472 MD5sum: 9be2dbb3bdfe774a44f743da222cc0d0 SHA256: cfd30f44ce60edb8d2d3fa1ad3bd319564346e1ab87cbbf79ba566b1c9a1cfcc Package: libloki-doc Source: libloki Version: 0.1.7-3.1 Installed-Size: 1604 Maintainer: Petr Baranov Architecture: all Description: C++ library of generic design patterns (documentation) Description-md5: 1186419a4f5aacc6ee86f9d477e52003 Homepage: http://loki-lib.sourceforge.net/ Tag: role::documentation Section: doc Priority: optional Filename: pool/main/libl/libloki/libloki-doc_0.1.7-3.1_all.deb Size: 94040 MD5sum: 0cd3a8e2a152dd20978debe65163a4eb SHA256: f4fac0de4479d117389f3fee0bbb697189e6f71e68e1064b7d0493319bc79355 -- Baptiste Beauplat - lyknode signature.asc Description: PGP signature
